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-W43-Monkind longformweek W43date 2026-10-26campaign longform-youtubepillar multimediabeat —asset videoduration 147.7sground whitescenes 7

Checklist the per-video bar — engine/sim

98.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W43-Mon 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 7 scenes · 147.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–24.8sspatial-parallaxicon·wireframe♪ bed_in
Today we are on screenwriting, and the question is simple. How do you write seven different video scripts in a week without them all sounding the same and without losing your mind. The week is about the plan behind the proof, so this is the part of the plan where words get made. We will give away the actual method The Big T-M uses to write at volume.
on-screen: Scripts before cameras
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Scripts before cameras
2s2
matches intent
NumberedList
template		teach24.8–47.5skinetic-buildicon·wireframe♪ node_lock
The first step is to never let the model invent the topic. We hand it a brief: the campaign, the headline, the service for the day, and the beat list. The model does not brainstorm from nothing. It writes against facts that already exist in the plan. A script is just those facts turned into plain spoken lines, in the right order.
on-screen: Feed the model the facts first
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Feed the model the facts firstcurate items, nodes
3s3
matches intent
ChecklistCard
template		teach47.5–70.5skinetic-buildicon·wireframe♪ node_lock
Here is the rule that kills filler. Each teaching chapter gets exactly one concrete move, named out loud. Not three vague tips. One real step. We tell the model: pick the tool, pick the action, say it like you would to a friend. When every chapter carries one solid step, the script teaches instead of selling, and there is nothing left to pad.
on-screen: One method per chapter
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→One method per chaptercurate items, nodes
4s4
matches intent
FlowSchematic
template		teach70.5–94.6skinetic-buildicon·wireframe♪ node_lock
Next, give the model a list of words it may never write. The empty hype words every agency reaches for, the ones that mean nothing. We keep that list in the brief and a checker scans every line for them. If one slips in, the script fails and gets rewritten. Plain words survive. An eleven-year-old should follow every sentence, or it is too clever to keep.
on-screen: Ban the empty words
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Ban the empty wordscurate nodes, stages
5s5
matches intent
ListCard
template		teach94.6–115.89999999999999skinetic-buildicon·wireframe♪ node_lock
You are hearing the result right now. This script was written by feeding a model the W43 brief and that one-step-per-chapter rule. No invented numbers, no borrowed buzzwords. The proof is that it holds together and tells you something you can use. If the method did not work, this video would sound like every other ad you skip.
on-screen: This script proves the method
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→This script proves the methodcurate items, nodes
6s6
matches intent
StatScoreboard
template		proof115.9–138.9sreceipts-counticon·wireframe♪ node_lock
So to write at volume: hand the model real facts, force one named step per chapter, ban the hollow words, and let a checker enforce it. That is screenwriting as a system, not a mood. The whole calendar of scripts is public, so you can read how each one differs. Go see them at office dot temerarii dot xyz and steal the structure.
on-screen: Write it down, give it away
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape octaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Write it down, give it awaycurate pillar, stats, statsLabels
7s7
matches intent
shared field
signature-3d		resolve138.9–147.70000000000002scoalescenceicon·wireframe♪ bed_out
Chapter six. Creative workflows: the give-it-away method, end to end. We hand the model real facts and force one named step per part.
on-screen: Chapter 6
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Chapter 6

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)

youtubeHow to write seven video scripts in a week without sounding the same How do you write seven different video scripts in a week without them all sounding the same and without losing your mind. This video gives away the method for writing at volume while keeping each script real. The method: Feed the model the facts first. Never let it invent the topic. Hand it a brief: the campaign, the headline, the service for the day, and the beat list. The model writes against facts that already exist in the plan, not from nothing. A script is those facts turned into plain spoken lines, in the right order. One method per chapter. This is the rule that kills filler. Each teaching chapter gets exactly one concrete move, named out loud. Not three vague tips, one real step. Tell the model to pick the tool, pick the action, and say it like you would to a friend. Keep each day's facts different, so the scripts cannot blur together. Because every brief carries its own service, headline, and beats, the seven scripts pull apart on their own instead of converging on the same safe lines. Read every draft for the fake note. The model drafts fast, but the taste is still yours. The lines that sound like a brochure get cut, and the plain ones stay. That split, machine speed plus a human ear, is why writing seven scripts stops being a wall. The model drafts, you decide, against a brief full of real facts. That is how a small team writes at volume without the scripts collapsing into one voice. Read the actual scripts behind our videos at office.temerarii.xyz. Keywords: screenwriting, batch content, video scripts, AI writing, content at scale, plain language.

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

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