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-W37-Frikind longformweek W37date 2026-09-18campaign longform-youtubepillar emerging_techbeat —asset videoduration 151.9sground blackscenes 8

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W37-Fri 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 8 scenes · 151.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–20.5sspatial-parallaxicon·liquid-chrome♪ bed_in
This one is about the harder side of public relations: watching your reputation before a small problem becomes a loud one. Turning listening into decisions also means deciding when to step in. You will learn how to build a quiet alarm from your own mentions, so you hear the first angry voice instead of the hundredth.
on-screen: Catch the storm early
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape coneground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Catch the storm early
2s2
matches intent
NumberedList
template		teach20.5–43.2skinetic-buildicon·wireframe♪ node_lock
First move. Have Claude read each fresh mention and mark it calm, annoyed, or angry, with a short reason. One angry post is noise. A cluster of them about the same thing in one day is a signal. The model gives you a daily temperature, so you are reacting to a pattern, not to the one loud person who is always loud.
on-screen: Score the mood, not just the words
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Score the mood, not just the wordscurate items, nodes
3s3
matches intent
ChecklistCard
template		teach43.2–62.0skinetic-buildicon·wireframe♪ node_lock
Second move. When the mood drops, ask the model to find the common cause across the angry posts. Usually it is one thing: a broken page, a confusing price, a missed promise. People describe it ten different ways. The model collapses those ten into the single root you can actually fix.
on-screen: Find the root, not the symptom
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Find the root, not the symptomcurate items, nodes
4s4
matches intent
AnnotatedDiagram
template		teach62.0–82.9skinetic-buildicon·wireframe♪ node_lock
Third move. Before you post anything, have the model write a short, plain, non-defensive reply you could give publicly. Calm beats clever in a tense moment. Drafting it first, while you are still steady, keeps you from typing something at midnight you cannot take back. You can always choose not to send it. You cannot un-send it.
on-screen: Draft the calm reply first
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Draft the calm reply firstcurate callouts, nodes
5s5
matches intent
WireframeMock
template		teach82.9–102.4skinetic-buildicon·wireframe♪ node_lock
Honest proof: we run this mood read on our own mentions, because saying we operate in public means hearing it when people are unhappy in public. The same file that finds our partners also tells us when we have a mess to clean. We do not get to only read the nice comments.
on-screen: We watch our own mood line
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→We watch our own mood linecurate nodes
6s6
matches intent
ListCard
template		teach102.4–122.9skinetic-buildicon·wireframe♪ node_lock
The honest outcome here is boring, and that is the point. Most days the line stays calm and you do nothing. The system earns its keep on the rare day it does not, by giving you a head start measured in hours, not in damage. A quiet alarm you never had to use is still working.
on-screen: Most days are quiet
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Most days are quietcurate items, nodes
7s7
matches intent
ComparisonTable
template		proof122.9–143.8sreceipts-counticon·wireframe♪ node_lock
The takeaway: reputation management is mostly listening for the first crack. Score the mood, find the root, draft the calm reply before you need it. Your next step is small. Tag one day of your mentions calm, annoyed, or angry, and see if a pattern is hiding. The method is live at office dot temerarii dot xyz.
on-screen: Wire yours at office.temerarii.xyz
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape coneground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Wire yours at office.temerarii.xyzcurate colA, colB, rows, statsLabels
8s8
matches intent
shared field
signature-3d		resolve143.8–151.9scoalescenceicon·liquid-chrome♪ bed_out
Emerging tech: what is next, tested in public. We try the new tool on a real task and report what broke.
on-screen: Chapter 7
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape coneground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Chapter 7

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)

youtubeBuild a quiet reputation alarm from your own mentions This is the harder side of public relations: watching your reputation before a small problem becomes a loud one. The goal is to hear the first angry voice instead of the hundredth. The method: - Score the mood, not just the words. Have Claude read each fresh mention and mark it calm, annoyed, or angry, with a short reason. One angry post is noise. A cluster about the same thing in one day is a signal. - Find the root, not the symptom. When the mood drops, ask the model for the common cause across the angry posts. People describe one broken thing ten ways; the model collapses them into the single root you can fix. - Draft the calm reply first, while you are still steady. Calm beats clever in a tense moment. You can always choose not to send it. You cannot un-send it. The honest proof: we run this mood read on our own mentions, because operating in public means hearing it when people are unhappy in public. The same file that finds our partners also tells us when we have a mess to clean. The honest outcome is boring, and that is the point. Most days the line stays calm and you do nothing. The system earns its keep on the rare day it does not, by giving you a head start measured in hours. Tag one day of your mentions calm, annoyed, or angry, and see if a pattern is hiding. The method is live at office.temerarii.xyz. Keywords: reputation monitoring, sentiment analysis, PR crisis early warning, brand mentions.

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

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