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-W42-Sunkind longformweek W42date 2026-10-18campaign longform-youtubepillar performancebeat asset videoduration 258.8sground blackscenes 10

Checklist the per-video bar — engine/sim

98.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W42-Sun good|bad)
⚠ 1 flag(s) — not yet ship-ready: custom_element_dup · 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 10 scenes · 258.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–32.0sspatial-parallaxicon·wireframe♪ bed_in
This week is about one thing: showing you are real instead of saying it. Most brands talk a big talk and have nothing to point at. We are going to fix that with multimedia, and we are going to build it the way we build everything here, with AI running the boring parts. By the end of this you will know how to plan a whole week of video, audio, and photos from one short brief, with a machine doing the heavy lifting and you keeping the taste.
on-screen: Proof you are real
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Proof you are real
2s2
matches intent
NumberedList
template
teach32.0–60.4skinetic-buildicon·wireframe♪ node_lock
First move: write one plain text file that says what the week is about. Not a deck, not a meeting, a file. We use a small YAML file with the topic, the promise, and the days. Then we hand that file to Claude Code in the terminal. The model reads it and treats it as the single source of truth, so every clip we make traces back to the same words. One file in, a whole week out.
on-screen: Start with one brief file
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Start with one brief filecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach60.4–86.7skinetic-buildicon·wireframe♪ node_lock
Second move: ask the model to turn that file into a content plan. We tell it the rule, deep teach one method per day, no hype, plain language. The model writes a draft schedule, one long video per day plus the short cuts. You read it like an editor. You are not typing every line, you are catching the lines that sound fake and sending them back. The machine drafts, you judge.
on-screen: Let the model draft the plan
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the model draft the plancurate items, nodes
4s4
matches intent
CheatSheet
template
teach86.7–113.0skinetic-buildicon·wireframe♪ node_lock
Third move: the narration. We send the script to ElevenLabs through its API, one fixed voice id so every video sounds like the same person. You do not record anything. The text becomes a clean audio file in seconds. If a line is wrong, you fix the text and run it again, not re record a whole take. That is the trick, the voice is now just another file you can edit.
on-screen: Generate the voice with one API
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Generate the voice with one APIcurate nodes, points, uses
5s5
matches intent
LogStream
template
teach113.0–138.2skinetic-buildicon·wireframe♪ node_lock
Fourth move: the moving picture. We build the visuals in Remotion, which is video written as code, so a shape, a caption, and a beat are all just numbers we can change. The model writes the composition, we render it to a file. Because it is code, making a hundred videos is the same work as making one. You change the brief, you press render, you get the set.
on-screen: Render the picture in code
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Render the picture in codecurate nodes, rows
6s6
matches intent
BuildLog
template
teach138.2–163.7skinetic-buildicon·wireframe♪ node_lock
Fifth move: stills. Not every brand can book a studio every week. So for the photo slots we generate images with a model like Flux through Replicate, lock a style so they all match, and treat the best ones as your library. When you do have real photos, even better, you drop them in the same folder. The point is you never have an empty grid waiting on a shoot.
on-screen: Photos without a photoshoot day
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Photos without a photoshoot daycurate lines, nodes
7s7
matches intent
StepFlow
template
teach163.7–187.5skinetic-buildicon·wireframe♪ node_lock
Sixth move: captions that actually line up. We run the voice file through Whisper, which writes down every word with the exact time it was said. The model takes those timestamps and burns the caption track straight onto the video. No one sits there nudging text by hand. The words on screen match the words in your ear because they came from the same source.
on-screen: Captions pulled from the audio
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Captions pulled from the audiocurate nodes, steps
8s8
matches intent
AnnotatedDiagram
template
teach187.5–210.2skinetic-buildicon·wireframe♪ node_lock
Seventh move: get it out. We wire a posting tool, in our case Blotato, into the agent, so one command sends the same cut to every platform in the right shape. The model knows a vertical clip goes one place and a wide one goes another. You approve, it posts. The studio never opens a browser tab to upload a single thing.
on-screen: Post everywhere from the terminal
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Post everywhere from the terminalcurate callouts, nodes
9s9
first render · fix pending
ComparisonTable
templatecustom_element_dup
proof210.2–236.1sreceipts-counticon·wireframe♪ node_lock
Here is the honest part. This is not a theory we sell. The whole calendar you are watching, every week of it, came out of this exact pipeline, built from one source file and operated by the model in public. We do not have a secret team of editors. We have a file, a few API keys, and a machine that does what it is told. That is the whole proof.
on-screen: We run this on ourselves
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We run this on ourselvescurate colA, colB, rows, statsLabels
10s10
matches intent
shared field
signature-3d
resolve236.1–258.8scoalescenceicon·wireframe♪ bed_out
So that is the week in one sitting: one brief, a model to draft it, real APIs for voice, picture, photos, and captions, and one command to ship. Nothing here is hidden. You can watch the whole thing run at office.temerarii.xyz. Steal the method. The next step is small, write your own one page brief, and let the machine carry the rest.
on-screen: See the machine at office.temerarii.xyz
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→See the machine at office.temerarii.xyz

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 make a whole week of video, audio, and photos from one brief Most brands talk a big talk and have nothing to point at. This video shows how to plan a whole week of video, audio, and photos from one short brief, with a machine doing the heavy lifting and you keeping the taste. The full pipeline: Start with one brief file. A small YAML file with the topic, the promise, and the days. Hand it to a coding agent in the terminal, and the model treats it as the single source of truth, so every clip traces back to the same words. Let the model draft the plan, one long video per day plus short cuts. You read it like an editor, catching the lines that sound fake and sending them back. The machine drafts, you judge. Generate the voice with one API. Send the script to ElevenLabs with one fixed voice id so every video sounds like the same person. If a line is wrong, fix the text and run it again, no re recording. Render the picture in code with Remotion, where a shape, a caption, and a beat are all numbers you can change. Making a hundred videos is the same work as making one. Fill the photo slots with an image model like Flux through Replicate, with a locked style so they all match. Drop real photos in the same folder when you have them. Burn captions that line up by running the voice through Whisper for word level timestamps, so the words on screen match the words in your ear. Post everywhere from the terminal with a posting tool wired into the agent. You approve, it posts. The whole calendar you are watching came out of this exact pipeline. Steal the method at office.temerarii.xyz. Keywords: content pipeline, AI video, Remotion, ElevenLabs, Whisper, Flux, Replicate, automation.

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