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 longform-W51-Tuekind longformweek W51date 2026-12-22campaign longform-youtubepillar staff_trainingbeat —asset videoduration 144.5sground whitescenes 7

Checklist the per-video bar — engine/sim

98.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W51-Tue good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
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 7 scenes · 144.5s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–23.4sspatial-parallaxicon·3d-extrude♪ bed_in
This week is about training teams to use AI for go-to-market, and today is one slice: content, social, and brand as a system. Most teams make one post at a time and burn out. By the end of this you will know how to set up a small machine that turns one idea into a week of on-brand content your team can run themselves.
on-screen: Build a content system, not posts
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Build a content system, not posts
2s2
matches intent
NumberedList
template		teach23.4–46.8skinetic-buildicon·wireframe♪ node_lock
First move: teach the model your voice by writing it down. List the words you never use and the tone you want, in plain language, in one short file. Feed that file to the model as its rulebook. Now every draft starts on-brand instead of generic. The lesson for the team is that brand is a written rule, not a vibe in someone's head.
on-screen: Write the brand rules down
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the brand rules downcurate items, nodes
3s3
matches intent
ChecklistCard
template		teach46.8–67.3skinetic-buildicon·wireframe♪ node_lock
Second move: take one real idea and ask the model to reshape it for each place it lives. The same point becomes a short caption, a longer post, and a script outline. You are not making three ideas, you are making one idea wear three outfits. The team learns to multiply work without thinning it out.
on-screen: One idea, many shapes
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→One idea, many shapescurate items, nodes
4s4
matches intent
PipelineMap
template		teach67.3–88.19999999999999skinetic-buildicon·wireframe♪ node_lock
Third move: save what worked. When a post lands, drop it into a folder the model can read. Next time you ask for drafts, you point it at that folder and say, more like these. The model copies your real winners, not the internet average. Your team is training a house style that gets sharper every week.
on-screen: Keep a swipe file of winners
expected on screen: white ground · a PipelineMap panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Keep a swipe file of winnerscurate nodes, stages
5s5
matches intent
NodeGraphCard
template		teach88.2–108.7skinetic-buildicon·wireframe♪ node_lock
Fourth move: wire the model to your posting tool through an adapter, so it can queue the approved drafts itself. A person still reads and approves every line, but the busywork of posting to each platform is gone. The skill the team gains is keeping the human on judgment and handing the typing to the machine.
on-screen: Schedule it from one place
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Schedule it from one placecurate hub, nodes
6s6
matches intent
KpiGrid
template		proof108.7–127.5sreceipts-counticon·wireframe♪ node_lock
Honest proof: the posts you are seeing across the week came out of exactly this system. One source file, one set of brand rules, reshaped into every format on the calendar. We did not buy a content tool and hope. We built the small machine and ran it on ourselves first.
on-screen: This week proves the method
expected on screen: white 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 whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→This week proves the methodcurate kpis, statsLabels
7s7
matches intent
shared field
signature-3d		resolve127.5–144.5scoalescenceicon·3d-extrude♪ bed_out
So the takeaway: write your brand rules down, reshape one idea many ways, save your winners, and let the model queue the work for a human to approve. That is a content system your team owns. Watch the whole thing run on live jobs at office.temerarii.xyz.
on-screen: Set up your own machine
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Set up your own machine

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

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

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

youtubeA content system, not posts: one idea into a week of on-brand work Most teams make one post at a time and burn out. By the end of this video you will know how to set up a small machine that turns one idea into a week of on-brand content your team can run themselves. The moves: - Write the brand rules down. Teach the model your voice by writing it down: the words you never use and the tone you want, in plain language, in one short file. Feed that file to the model as its rulebook. Now every draft starts on brand. Brand is a written rule, not a vibe in someone's head. - One idea, many shapes. Take one real idea and ask the model to reshape it for each place it lives. The same point becomes a short caption, a longer post, and a script outline. You are not making three ideas; you are making one idea wear three outfits. - Keep a swipe file of winners. When a post lands, drop it into a folder the model can read. Next time you ask for drafts, point it at that folder and say more like these. The model copies your real winners, not the internet average. The house style gets sharper every week. - Schedule it from one place. Wire the model to your posting tool through an adapter, so it can queue the approved drafts itself. A person still reads and approves every line, but the busywork of posting to each platform is gone. Keep the human on judgment and hand the typing to the machine. The honest proof: the posts you are seeing across the week came out of exactly this system. One source file, one set of brand rules, reshaped into every format on the calendar. We did not buy a content tool and hope; we built the small machine and ran it on ourselves first. Write your brand rules down, reshape one idea many ways, save your winners, and let the model queue the work for a human to approve. Watch the whole thing run on live jobs at office.temerarii.xyz Keywords: content system, brand rules file, repurpose one idea, swipe file, scheduled posting, human approval, on-brand content

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

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