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-W50-Frikind longformweek W50date 2026-12-18campaign longform-youtubepillar brandbeat asset videoduration 142.8sground redscenes 6

Checklist the per-video bar — engine/sim

100.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W50-Fri good|bad)
✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)

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 6 scenes · 142.8s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–23.0sspatial-parallaxicon·white-knockout♪ bed_in
Today is the live dashboard, the other half of data for marketers. Pulling a number once is good. Seeing the right few numbers update on their own is better. By the end your team will have one simple screen that anyone can glance at and know how things are going. Open the workspace. We start by deciding what does not go on it.
on-screen: Build a dashboard people read
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Build a dashboard people read
2s2
matches intent
NumberedList
template
teach23.0–46.0skinetic-buildicon·white-knockout♪ node_lock
First move: pick the few numbers that matter. A dashboard with fifty boxes tells you nothing. We have your team choose at most five: the leads, the cost, the replies, the one or two things tied to money. If a number would not change a decision, it stays off the screen. Cutting is the hard part, so we do it together, out loud.
on-screen: Choose five numbers, not fifty
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Choose five numbers, not fiftycurate items, nodes
3s3
matches intent
ChecklistCard
template
teach46.0–70.5skinetic-buildicon·liquid-chrome♪ node_lock
Second move: have the agent build it. We connect your data sources through MCP servers, then ask the model to make one plain web page that shows those five numbers, big and clear. It writes the page and pulls the live data. Your team does not need to be coders. They describe the screen they want, and they watch the model assemble it in front of them.
on-screen: Let the agent build the page
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Let the agent build the pagecurate items, nodes
4s4
matches intent
SchematicCard
template
teach70.5–95.3skinetic-buildicon·white-knockout♪ node_lock
Third move: make it refresh and stay honest. We set the page to pull fresh numbers on a schedule, so it is never stale, and we add the date it last updated right on the screen. We also show one row of the raw data so the team can spot-check it. A dashboard you cannot trust is worse than none, so we build trust in from the start.
on-screen: Keep it honest and current
expected on screen: red ground · a SchematicCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Keep it honest and currentcurate nodes
5s5
matches intent
RankList
template
proof95.3–119.8sreceipts-counticon·liquid-chrome♪ node_lock
Honest proof: The Big T-M keeps its own work on a public screen. Our whole calendar and every asset are visible online, built and tracked from one source file, with no hidden numbers. We do not report progress in a slide once a month. We put it on the wall where anyone, including you, can look at it any day. That is the standard we are teaching.
on-screen: Our work is on the wall in
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our work is on the wall in publiccurate rows, statsLabels
6s6
matches intent
shared field
signature-3d
resolve119.8–142.8scoalescenceicon·white-knockout♪ bed_out
The takeaway: a dashboard is five honest numbers, kept current, that anyone on the team can read in ten seconds. Build that and your meetings get shorter and your decisions get faster. Your team now has the screen and the way to keep it alive. See ours running at office dot temerarii dot xyz, and tomorrow we package your brand so it travels.
on-screen: One screen, the whole team aligned
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→One screen, the whole team aligned

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 live dashboard your whole team can read in ten seconds Pulling a number once is good. Seeing the right few numbers update on their own is better. This video shows how to build one simple screen anyone on the team can glance at and know how things are going. The three moves: - Choose five numbers, not fifty. A dashboard with fifty boxes tells you nothing. Pick at most five: the leads, the cost, the replies, the one or two things tied to money. If a number would not change a decision, it stays off the screen. Cutting is the hard part. - Let the agent build the page. Connect your data sources through MCP servers, then ask the model to make one plain web page that shows those five numbers, big and clear. It writes the page and pulls the live data. You do not need to be a coder; you describe the screen and watch it get built. - Keep it honest and current. Set the page to pull fresh numbers on a schedule so it is never stale, and put the last-updated date right on the screen. Show one row of raw data so the team can spot-check it. A dashboard you cannot trust is worse than none. The honest proof: our whole calendar and every asset are visible online, built and tracked from one source file, with no hidden numbers. We do not report progress in a slide once a month. We put it on the wall where anyone, including you, can look any day. A dashboard is five honest numbers, kept current, that anyone can read in ten seconds. Build that and your meetings get shorter. See ours running at office.temerarii.xyz Keywords: live marketing dashboard, five key metrics, MCP data sources, honest reporting, refresh on schedule, dashboard for small teams

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