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-Mon-2kind threadweek W31date 2026-08-03campaign thread · Monpillar it_devbeat Monasset videoduration 60.0sground whitescenes 9

Checklist the per-video bar — engine/sim

98.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W31-Mon-2 good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · 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 · 60.0s · 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·ember-fill♪ bed_in
Automation used to mean a brittle script that broke the moment a website changed a button.
on-screen: Automation meant brittle scripts
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Automation meant brittle scripts
2s2
matches intent
shared field
signature-3d		hook6.3–12.899999999999999skinetic-buildicon·wireframe♪ node_lock
Dark truth: an automation with no log is a ghost you can't catch when it haunts you.
on-screen: A flow with no log is a
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→A flow with no log is a ghost
3s3
matches intent
NumberedList
template		teach12.9–20.6skinetic-buildicon·wireframe♪ node_lock
So we do it now by handing a model real tools, each with a name and a strict input shape.
on-screen: Give the model real tools
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Give the model real toolscurate items, nodes
4s4
matches intent
ComparisonTable
template		proof20.6–27.200000000000003sreceipts-counticon·wireframe♪ node_lock
Define the inputs as a typed schema, so the model can't pass garbage and pretend it worked.
on-screen: Typed inputs stop the chaos
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Typed inputs stop the chaoscurate colA, colB, rows, statsLabels
5s5
matches intent
DiffCard
template		diff27.2–34.2scrossfade-8ficon·wireframe♪ node_lock
Old way was one fixed path. Now the model picks the tool and adapts when the world shifts.
on-screen: Old: script. Now: a worker
expected on screen: white ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Old: script. Now: a workercurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach34.2–41.2skinetic-buildicon·wireframe♪ node_lock
Log every tool call with its inputs, so when it breaks you read the story, not the ashes.
on-screen: Log every tool call
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Log every tool callcurate items, nodes
7s7
matches intent
KpiGrid
template		proof41.2–48.2sreceipts-counticon·wireframe♪ node_lock
We build this at The Big T-M, and the agent bends without snapping, with a full paper trail.
on-screen: It adapts, you can audit
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→It adapts, you can auditcurate kpis, statsLabels
8s8
matches intent
NodeGraphCard
template		step48.2–54.5skinetic-buildicon·wireframe♪ node_lock
Your move: name the tools, type the inputs, log every call, then let the model drive.
on-screen: Steps: tools, types, logs
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: tools, types, logscurate hub, nodes, stages, steps
9s9
matches intent
shared field
signature-3d		resolve54.5–60.0scoalescenceicon·ember-fill♪ bed_out
Now your automation adapts to change instead of dying at the first redesigned button.
on-screen: Automation that bends
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Automation that bends

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)

tiktokAutomation that doesn't break the second a button moves: give the AI real named tools with TYPED inputs so it can't pass garbage. (AI-assisted) Log every tool call so you read the story, not the ashes. #automation #AI #nocode
instagramNamed tools. Typed inputs. Logged calls. It adapts instead of dying. #automation #AI #agents #buildinpublic #temerarii
linkedinWhy most automations break: they are one brittle path. The durable approach: give a model real tools, each with a typed input schema so it can't pass garbage and pretend it worked, and log every tool call with its inputs. The agent adapts when the world shifts, and you keep a full audit trail.
xAutomation that doesn't snap: give the model named tools with typed inputs, log every call. It adapts instead of dying at the first redesigned button. temerarii.com
facebookBuild automation that adapts: give the AI real named tools with typed inputs so it can't pass garbage, and log every call so you can debug from the story, not the ashes. Full method free on the site.
threadsAn automation with no log is a ghost you can't catch when it haunts you. Give the model named tools with typed inputs, log every call. It bends when the world shifts instead of snapping at the first moved button.
pinterestAI automation architecture: give models named tools with typed input schemas, log every tool call for auditing, and let the agent adapt to change. Resilient automation that survives website redesigns and breaking changes.
blueskyAutomation that doesn't snap: named tools, typed inputs, logged calls. The agent adapts instead of dying at the first moved button. temerarii.com
youtubeAI Automation That Adapts: Named Tools, Typed Inputs, Logged Calls Most automations break because they are one brittle path. Give a model real tools, each with a typed input schema so it can't pass garbage, and log every tool call. The agent bends when the world shifts and you keep a full audit trail. AI-assisted, free method 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