Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post social-W31-Fri-1kind threadweek W31date 2026-08-07campaign thread · Fripillar staff_trainingbeat Friasset videoduration 65.6sground blackscenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W31-Fri-1 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 9 scenes · 65.6s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–6.6sspatial-parallaxicon·white-knockout♪ bed_in
Content used to be whatever the one free person posted on a Friday with a tired thumb.
on-screen: Content by whoever was free
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Content by whoever was free
2s2
matches intent
shared field
signature-3d		hook6.6–13.6skinetic-buildicon·wireframe♪ node_lock
Dark truth: a content engine that lives in one person's habits dies the week they take a holiday.
on-screen: No system means it dies on vacation
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→No system means it dies on vacation
3s3
matches intent
NumberedList
template		teach13.6–21.3skinetic-buildicon·wireframe♪ node_lock
So we do it now by writing the brand rules into one file, the voice, the words you never use.
on-screen: Write the rules down as a file
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the rules down as a filecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof21.3–29.0sreceipts-counticon·wireframe♪ node_lock
Feed that rules file to the model with every draft, so a new helper sounds like you on day one.
on-screen: Feed the rules to the model
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Feed the rules to the modelcurate colA, colB, rows, statsLabels
5s5
matches intent
DiffCard
template		diff29.0–36.3scrossfade-8ficon·wireframe♪ node_lock
Old way leaned on a habit. The future way is a system anyone can run without copying your gut.
on-screen: Old: a habit. Now: a system
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape knotground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Old: a habit. Now: a systemcurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach36.3–42.9skinetic-buildicon·wireframe♪ node_lock
Keep one calendar as the single source, so nobody guesses what ships on which day, ever again.
on-screen: One calendar, one source
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→One calendar, one sourcecurate items, nodes
7s7
matches intent
KpiGrid
template		proof42.9–50.6sreceipts-counticon·wireframe♪ node_lock
We run this at The Big T-M, and the brand sounds the same whether or not the founder is awake.
on-screen: It runs without the founder
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→It runs without the foundercurate kpis, statsLabels
8s8
matches intent
WireframeMock
template		step50.6–57.9skinetic-buildicon·wireframe♪ node_lock
Your move: write the rules file, feed it to every draft, keep one calendar, then let the team run.
on-screen: Steps: rules, feed, calendar
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual pipelineshape knotground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: rules, feed, calendarcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve57.9–65.6scoalescenceicon·white-knockout♪ bed_out
Now the brand is a system, not a mood, and it keeps its voice even on the founder's day off.
on-screen: A brand that runs itself
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→A brand that runs itself

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

Social captions supplemental published copy · per channel (comp_id level)

tiktokIf your content lives in one person's habits, it dies the week they take a holiday. Write the brand rules into ONE file (voice + banned words), feed it to AI with every draft, keep ONE calendar. (AI-assisted) #contentstrategy #branding
instagramRules in one file. Feed it to every draft. One calendar, one source. A brand that runs itself. #contentstrategy #branding #systems #marketing #temerarii
linkedinA content engine that lives in one person's habits dies the week they take a holiday. Write the brand rules into one file, the voice and the words you never use, feed that file to the model with every draft so a new helper sounds like you on day one, and keep one calendar as the single source. The brand becomes a system, not a mood.
xIf your content lives in one person's habits, it dies on their vacation. Rules in one file. Feed it to every draft. One calendar. temerarii.com
facebookBuild a content system that runs without you: write the brand rules into one file, feed it to AI with every draft, and keep one calendar as the single source. The brand becomes a system, not a mood. Free method on the site.
threadsA content engine that lives in one person's habits dies the week they take a holiday. Write the brand rules into one file, feed it to every draft, keep one calendar. The brand becomes a system, not a mood.
pinterestContent and brand systems best practices: write brand rules and voice into one file, feed it to AI with every draft for consistency, and keep one shared content calendar. Repeatable brand system that runs without the founder.
blueskyIf your content lives in one person's habits, it dies on their vacation. Rules in one file. Feed it to every draft. One calendar. temerarii.com
youtubeContent Systems That Run Without You: Rules File, Fed to AI, One Calendar A content engine that lives in one person's habits dies the week they take a holiday. Write the brand rules into one file, voice and the words you never use, feed it to the model with every draft so new helpers sound like you on day one, and keep one calendar as the single source. The brand becomes a system, not a mood. Free at temerarii.com

Cross-links every lens is a view on this one record

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view