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-W44-Tuekind longformweek W44date 2026-11-03campaign longform-youtubepillar strategic_relationsbeat asset videoduration 126.5sground redscenes 6

Checklist the per-video bar — engine/sim

100.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W44-Tue good|bad)
✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)

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 6 scenes · 126.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–22.0sspatial-parallaxicon·liquid-chrome♪ bed_in
Today is about content creation, the part people dread. Building presence in public sounds like a lot of posts, and it is. But you do not write each one cold. You start with one idea and let a model spread it across the week. Here is how we turn a single thought into a full slate without losing our voice.
on-screen: One idea, many posts
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→One idea, many posts
2s2
matches intent
NumberedList
template
teach22.0–42.2skinetic-buildicon·white-knockout♪ node_lock
First step. A model with no rules writes mush. So we hand the agent the brand rails as plain instructions: short sentences, plain words an eleven-year-old gets, no empty hype words, and always teach the real method instead of selling. The model now drafts inside our fence instead of wandering off into generic marketing slop.
on-screen: Give the model your real rules
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Give the model your real rulescurate items, nodes
3s3
matches intent
ChecklistCard
template
teach42.2–62.400000000000006skinetic-buildicon·liquid-chrome♪ node_lock
Second step. We take one idea and ask the model to reshape it for each platform at once. A threaded version for one feed, a short punchy version for another, a caption for a vertical video. Same spine, different body. You wrote one thing. You now have five, each cut to fit where it lives.
on-screen: One source idea, reshaped per platform
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→One source idea, reshaped per platformcurate items, nodes
4s4
matches intent
DiffCard
template
teach62.4–84.7skinetic-buildicon·white-knockout♪ node_lock
Third step. The model never gets the last word. It drafts, you cut. You read each version out loud, kill the lines that sound like a robot, and keep the ones that sound like a person. The work shifts from staring at a blank page to trimming a full one. That is a much easier day, and a much better post.
on-screen: You edit, the model drafts
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→You edit, the model draftscurate lines, nodes
5s5
matches intent
ListCard
template
proof84.7–106.0sreceipts-counticon·liquid-chrome♪ node_lock
The honest proof. Every post we shipped this week, across every platform, came from the same handful of source ideas in one file, reshaped by the agent and cut by us. No team of twelve. One person and one machine. You can scroll the whole slate and see how it ties together at office dot temerarii dot xyz.
on-screen: Every post traces to one file
expected on screen: red ground · a ListCard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Every post traces to one filecurate items, statsLabels
6s6
matches intent
shared field
signature-3d
resolve106.0–126.5scoalescenceicon·liquid-chrome♪ bed_out
The takeaway. Stop writing a fresh post for every box. Write the idea once, give the model your real rules, let it reshape, then you do the cutting. That is how a small shop posts like a big one. Try it on your next idea, and see ours laid out at office dot temerarii dot xyz.
on-screen: Write once, ship everywhere
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Write once, ship everywhere

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)

youtubeWrite One Idea Once, Then Let a Model Reshape It Into a Week of Posts Building a presence sounds like a lot of posts, and it is. But you do not write each one cold. In this video we show how to start with one idea and let a model spread it across the week without losing your voice. What we walk through: - Give the model your real rules. A model with no rules writes mush, so we hand the agent the brand rails as plain instructions: short sentences, plain words an eleven-year-old gets, no empty hype words, and teach the real method instead of selling. Now it drafts inside our fence. - One idea, reshaped per platform. We take one idea and ask the model to reshape it for each platform at once. A threaded version for one feed, a short punchy version for another, a caption for a vertical video. Same spine, different body. - You edit, the model drafts. The model never gets the last word. It drafts, you cut. You read each version out loud, kill the lines that sound like a robot, and keep the ones that sound like a person. The honest proof: every post we shipped this week, across every platform, came from the same handful of source ideas in one file, reshaped by the agent and cut by us. No team of twelve, one person and one machine. You can scroll the whole slate at office.temerarii.xyz. The takeaway: stop writing a fresh post for every box. Write the idea once, give the model your real rules, let it reshape, then you do the cutting. That is how a small shop posts like a big one. Keywords: content repurposing, AI writing, brand voice, social media workflow, one idea many posts.

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