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-W38-Thu-4kind threadweek W38date 2026-09-24campaign thread · Thupillar staff_trainingbeat Thuasset videoduration 62.9sground 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-W38-Thu-4 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 · 62.9s · 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.3sspatial-parallaxicon·wireframe♪ bed_in
Old way: you typed a question and the model answered, one turn, no memory, no follow-up.
on-screen: AI answered, never asked
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→AI answered, never asked
2s2
matches intent
shared field
signature-3d
hook6.3–13.6skinetic-buildicon·ember-fill♪ node_lock
Here is the limit: a single answer is a fact, not a job done. Real work takes many steps.
on-screen: One turn is not a worker
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→One turn is not a worker
3s3
matches intent
NumberedList
template
teach13.6–21.7skinetic-buildicon·wireframe♪ node_lock
New way: hand the model a few tools and a loop, so it can act, check the result, and try again.
on-screen: Give the model tools and a loop
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→Give the model tools and a loopcurate items, nodes
4s4
matches intent
RankList
template
proof21.7–28.299999999999997sreceipts-counticon·white-knockout♪ node_lock
Now the model chases a goal across steps instead of stopping at the first sentence it produces.
on-screen: It works toward a goal
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape knotground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→It works toward a goalcurate rows, statsLabels
5s5
matches intent
CodeWindow
template
diff28.3–35.3scrossfade-8ficon·liquid-chrome♪ node_lock
An answering model talks. An acting model does, and the difference is the tools you let it touch.
on-screen: Answering vs acting
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape knotground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Answering vs actingcurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template
teach35.3–43.0skinetic-buildicon·ember-fill♪ node_lock
Teach the rule: give it only the tools it needs, with hard limits, so a wrong step cannot wreck things.
on-screen: Fence the tools tightly
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Fence the tools tightlycurate items, nodes
7s7
matches intent
StatScoreboard
template
proof43.0–48.9sreceipts-counticon·wireframe♪ node_lock
Tight fences are what let you trust a loop you are not watching every second.
on-screen: Guardrails make it safe
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Guardrails make it safecurate pillar, stats, statsLabels
8s8
matches intent
WireframeMock
template
step48.9–55.9skinetic-buildicon·white-knockout♪ node_lock
Your step: pick one safe tool, give a model access, and let it complete one small multi-step task.
on-screen: Wire one tool to a model
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual pipelineshape knotground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Wire one tool to a modelcurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve55.9–62.9scoalescenceicon·wireframe♪ bed_out
Now the model acts, not just answers. The Big T-M builds the loop and the fences around it.
on-screen: From answers to action
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→From answers to action

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)

tiktokAI is moving from answering to acting. Give the model tools and a loop so it works toward a goal, then fence the tools tightly. (AI-assisted) #ai #aiagents #automation
instagramAn answer is a fact. A job done takes many steps. Give the model tools, a loop, and tight fences. #ai #aiagents #automation #futuretech #tech
linkedinAI is shifting from answering to acting. A single answer is a fact, not a job done, and real work takes many steps. The move: give the model a few tools and a loop so it can act, check the result, and try again toward a goal. The difference between a model that talks and one that does is simply the tools you let it touch. Which is exactly why you fence them tightly: give it only what it needs, with hard limits, so a wrong step cannot cause damage. Tight guardrails are what let you trust a loop you are not watching.
xAI is moving from answering to acting. Give the model tools and a loop to chase a goal, then fence the tools tightly. Method:
facebookAI is moving from answering questions to actually doing tasks. Give the model a few tools and a loop so it works toward a goal, but fence those tools tightly so a wrong step cannot cause harm. Comment for the safe starter setup.
threadsAI is shifting from answering to acting. A single answer is a fact, not a job done. Give the model tools and a loop so it can act, check, and retry toward a goal. Then fence those tools tightly, because tight guardrails are what let you trust a loop you are not watching.
pinterestAI agents explained: how to move from one-turn answers to acting by giving a model tools and a loop to work toward a goal, with tight guardrails so a wrong step cannot cause harm. AI agents, automation, future tech, AI tools.
blueskyAI is moving from answering to acting. Give the model tools and a loop to chase a goal, then fence the tools tightly. Method:
youtubeFrom Answering to Acting: How AI Agents Actually Work A single AI answer is a fact, not a job done. This covers giving a model a few tools and a loop so it can act, check the result, and retry toward a goal, and why fencing those tools tightly with hard limits is what lets you trust a loop you are not watching. AI agents, automation, future tech. AI-assisted production.

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