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-W30-Sat-1kind threadweek W30date 2026-08-01campaign thread · Satpillar strategic_relationsbeat Satasset videoduration 58.9sground blackscenes 9

Checklist the per-video bar — engine/sim

84.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W30-Sat-1 good|bad)
⚠ 4 flag(s) — not yet ship-ready: copy_generictoo_complexdup_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 · 58.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.6sspatial-parallaxicon·liquid-chrome♪ bed_in
Coordinating an event used to be a swamp of spreadsheets, group chats, and one person quietly panicking.
on-screen: Running an event was a spreadsheet swamp
expected on screen: black 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 blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Running an event was a spreadsheet swamp
2s2
matches intent
shared field
signature-3d		hook6.6–13.2skinetic-buildicon·wireframe♪ node_lock
Now the busywork runs itself, so the human can spend energy on the moments that actually matter.
on-screen: Now the busywork runs itself
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Now the busywork runs itself
3s3
matches intent
NumberedList
template		teach13.2–18.7skinetic-buildicon·wireframe♪ node_lock
Trigger the confirmation, the calendar invite, and the reminder off a single RSVP, hands-free.
on-screen: Wire confirmations to the RSVP
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Wire confirmations to the RSVPcurate items, nodes
4s4
matches intent
RankList
template		proof18.7–25.7sreceipts-counticon·wireframe♪ node_lock
One yes fires the whole chain, and every guest gets the same clean flow without you touching it.
on-screen: One RSVP fires the whole chain
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→One RSVP fires the whole chaincurate rows, statsLabels
5s5
matches intent
CodeWindow
template		diff25.7–32.0scrossfade-8ficon·wireframe♪ node_lock
Most try to automate everything. We automate the boring and keep the welcome warm and human.
on-screen: We automate the boring, not the welcome
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape tetraground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→We automate the boring, not the welcomecurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template		teach32.0–40.1skinetic-buildicon·wireframe♪ node_lock
Tell a model the goal and the hours, and let it draft a runsheet you can then cut down to real.
on-screen: Let a model draft the schedule from
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let a model draft the schedule from the goalcurate items, nodes
7s7
matches intent
StatScoreboard
template		proof40.1–46.0sreceipts-counticon·wireframe♪ node_lock
Automate the reminders and far fewer guests no-show, because nobody simply forgot it was today.
on-screen: Less chaos, fewer dropped balls
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Less chaos, fewer dropped ballscurate pillar, stats, statsLabels
8s8
matches intent
AnnotatedDiagram
template		step46.0–52.6skinetic-buildicon·wireframe♪ node_lock
Your move: pick one step, the reminder, and wire it to fire off the RSVP this week.
on-screen: Your move: automate one reminder
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape tetraground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Your move: automate one remindercurate callouts, stages, steps
9s9
matches intent
shared field
signature-3d		resolve52.6–58.9scoalescenceicon·liquid-chrome♪ bed_out
Good event coordination frees the human for the human parts. Let the chain handle the rest.
on-screen: Free the human for the human parts
expected on screen: black 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 blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Free the human for the human parts

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)

tiktokEvent planning chaos? Wire the confirmation + calendar invite + reminder to fire off ONE RSVP, hands-free. Let a model draft the runsheet. Automate the boring, keep the welcome human. (AI-assisted.)
instagramAutomate the boring. Keep the welcome warm. One RSVP → the whole chain fires. #eventplanning #eventcoordination #automation #productivity #temerarii
linkedinCoordinating an event used to be a swamp of spreadsheets, group chats, and one person quietly panicking. The futurist move: automate the busywork so the human can focus on what matters. Trigger the confirmation, calendar invite, and reminder off a single RSVP, hands-free, so every guest gets the same clean flow. Let a model draft a runsheet from your goal and hours, then cut it down. Takeaway: automate the boring and keep the welcome warm and human.
xEvent planning chaos? Wire the confirmation + calendar invite + reminder to fire off one RSVP, hands-free. Automate the boring, keep the welcome human. temerarii.xyz
facebookCoordinating an event used to be a swamp of spreadsheets and group chats. Now the busywork runs itself: trigger the confirmation, calendar invite, and reminder off a single RSVP, hands-free, so every guest gets the same clean flow. Let a model draft a runsheet from your goal and hours. Automate the boring, keep the welcome warm. Full method on the site.
threadsEvent coordination: wire the confirmation, calendar invite, and reminder to fire off one RSVP, hands-free. Let a model draft the runsheet. Automate the boring, keep the welcome human.
pinterestHow to coordinate events without the chaos: trigger the confirmation, calendar invite, and reminder automatically off a single RSVP, and let an AI model draft your runsheet from the goal and hours. Event coordination, event planning automation, productivity workflow.
blueskyEvent coordination: wire the confirmation, calendar invite, and reminder to fire off one RSVP, hands-free. Automate the boring, keep the welcome human. temerarii.xyz
youtubeEvent Coordination: Automate the Boring, Keep the Welcome Human Coordinating an event used to be a swamp of spreadsheets, group chats, and one person quietly panicking. We show the futurist move: automate the busywork so the human can spend energy on the moments that matter. Trigger the confirmation, calendar invite, and reminder off a single RSVP, hands-free, so every guest gets the same clean flow. Let a model draft a runsheet from your goal and hours, then cut it down to real. Free the human for the human parts. Made with The Big T-M. AI-assisted. more at temerarii.xyz

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

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