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-W46-Frikind longformweek W46date 2026-11-20campaign longform-youtubepillar it_devbeat asset videoduration 143.1sground 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-W46-Fri good|bad)
⚠ 1 flag(s) — not yet ship-ready: generic_scene · 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 · 143.1s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–19.1sspatial-parallaxicon·white-knockout♪ bed_in
This week is access into advantage, but access cuts both ways. A bad review, a quiet complaint, a post that catches fire. Today, the public relations move nobody teaches, handling the moment things go sideways with an AI agent that listens fast and helps you answer like a human, not a lawyer.
on-screen: When the story goes wrong
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→When the story goes wrong
2s2
matches intent
ChecklistCard
template
teach19.1–40.0skinetic-buildicon·wireframe♪ node_lock
First. Set the agent to watch where people talk about you. Point it at Reddit and the web through its MCP servers and have it pull mentions every morning and flag the angry ones. You hear the problem while it is small, when a calm reply still fixes it, instead of finding out a week too late.
on-screen: Listen before you speak
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Listen before you speakcurate items, nodes
3s3
matches intent
NumberedList
template
teach40.0–58.0skinetic-buildicon·wireframe♪ node_lock
Second. Not every complaint deserves a reply. Have the model sort mentions into three buckets. A real customer with a real issue. A misunderstanding you can clear up. And noise you should leave alone. The agent reads the tone so you spend your energy only where it changes something.
on-screen: Sort heat from noise
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Sort heat from noisecurate items, nodes
4s4
matches intent
BuildLog
template
teach58.0–80.7skinetic-buildicon·wireframe♪ node_lock
Third. For the real ones, tell the model to draft a reply that admits the part you got wrong, says what you will do, and skips the corporate fog. Plain words, owned mistake, clear fix. You read it, you make it sound like you, you post it yourself. The agent gives you a calm first draft when your own pulse is up.
on-screen: Draft the human reply
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Draft the human replycurate lines, nodes
5s5
matches intent
DiffCard
template
teach80.7–98.0skinetic-buildicon·wireframe♪ node_lock
Fourth. Once a month, have the agent group every complaint by theme. Three people mad about the same thing is not a public relations problem, it is a product problem. The model shows you the pattern so you fix the cause and stop refighting the same fire.
on-screen: Find the pattern, fix the cause
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Find the pattern, fix the causecurate lines, nodes
6s6
matches intent
StackTrace
template
teach98.0–116.8skinetic-buildicon·wireframe♪ node_lock
The honest part. We run this listening loop on The Big T-M ourselves, every morning, built from the same source file behind this video. We are not pretending we never get a hard comment. We are showing you the exact machine we use to catch it early and answer like people.
on-screen: We watch our own name too
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→We watch our own name toocurate errMsg, errType, fix, frames, nodes
7s7
matches intent
RankList
template
proof116.8–138.1sreceipts-counticon·wireframe♪ node_lock
So crisis-side public relations, four moves. Listen daily. Sort heat from noise. Draft a human, honest reply. Fix the pattern, not just the post. Let the agent watch while you stay the calm voice. The whole studio runs in public at office dot temerarii dot xyz. Set up one daily mention scan this week, before you need it.
on-screen: See it run at office.temerarii.xyz
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→See it run at office.temerarii.xyzcurate rows, statsLabels
8s8
first render · fix pending
shared field
signature-3dgeneric_scene
resolve138.1–143.1scoalescenceicon·white-knockout♪ bed_out
Custom apps + dashboards: own the code and the IP
on-screen: Chapter 7
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion 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)

youtubeCrisis PR With an AI Agent: Listen Fast, Sort the Heat, and Answer Like a Human A bad review, a quiet complaint, a post that catches fire. In this video we cover the public relations move nobody teaches, handling the moment things go sideways with an agent that listens fast and helps you answer like a person, not a lawyer. The moves: - Listen before you speak. Set the agent to watch where people talk about you. Point it at Reddit and the web through its MCP servers and have it pull mentions every morning and flag the angry ones. You hear the problem while it is small. - Sort heat from noise. Have the model sort mentions into three buckets: a real customer with a real issue, a misunderstanding you can clear up, and noise you should leave alone. The agent reads the tone so you spend your energy where it changes something. - Draft the human reply. For the real ones, tell the model to draft a reply that admits the part you got wrong, says what you will do, and skips the corporate fog. Plain words, owned mistake, clear fix. You make it sound like you and post it yourself. - Find the pattern, fix the cause. Once a month, have the agent group every complaint by theme. Three people mad about the same thing is not a PR problem, it is a product problem. Fix the cause and stop refighting the same fire. The honest part: we run this listening loop on our own studio every morning, built from the same source file behind this video. We are not pretending we never get a hard comment. We are showing you the exact machine we use to catch it early. The takeaway: listen daily, sort heat from noise, draft an honest reply, fix the pattern not just the post. Set up one daily mention scan before you need it. See it at office.temerarii.xyz. Keywords: crisis PR, reputation management, social listening, MCP, AI agent.

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