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 social-W24-Fri-2kind threadweek W24date 2026-06-19campaign thread · Fripillar it_devbeat Friasset videoduration 57.1sground whitescenes 9

Checklist the per-video bar — engine/sim

98.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W24-Fri-2 good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
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 9 scenes · 57.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–5.9sspatial-parallaxicon·color♪ bed_in
AI can write the code now, but somebody still has to own what it wrote.
on-screen: AI writes code, but who owns it
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→AI writes code, but who owns it
2s2
matches intent
shared field
signature-3d		hook5.9–12.9skinetic-buildicon·wireframe♪ node_lock
Here is how The Big T-M builds software with a model in the loop without losing the plot.
on-screen: How dev works with AI in the
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→How dev works with AI in the loop
3s3
matches intent
NumberedList
template		teach12.9–20.2skinetic-buildicon·wireframe♪ node_lock
Write the test that proves the feature first, then let the model write code until the test goes green.
on-screen: Write the test before the code
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the test before the codecurate items, nodes
4s4
matches intent
RankList
template		proof20.2–27.5sreceipts-counticon·wireframe♪ node_lock
The proof is the passing test: it does not care how clever the code looks, only that it works.
on-screen: Green tests are the real proof
expected on screen: white 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 whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Green tests are the real proofcurate rows, statsLabels
5s5
matches intent
LogStream
template		diff27.5–33.0scrossfade-8ficon·wireframe♪ node_lock
The old way shipped on a Friday and prayed nothing broke over the weekend.
on-screen: Old way: ship it and pray
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Old way: ship it and praycurate codeLines, rows
6s6
matches intent
ChecklistCard
template		teach33.0–40.7skinetic-buildicon·wireframe♪ node_lock
Now you ship in small pieces you can read in one sitting, so any bad change is easy to undo.
on-screen: Small commits, easy to undo
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Small commits, easy to undocurate items, nodes
7s7
matches intent
StatScoreboard
template		proof40.7–46.6sreceipts-counticon·wireframe♪ node_lock
The receipt is maintenance: code a human can read beats code only the machine understood.
on-screen: Readable beats clever
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Readable beats clevercurate pillar, stats, statsLabels
8s8
matches intent
ProcessFlow
template		step46.6–52.1skinetic-buildicon·wireframe♪ node_lock
Read every line the model wrote, because owning the bug means owning the code.
on-screen: Review the diff like a hawk
expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Review the diff like a hawkcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve52.1–57.1scoalescenceicon·color♪ bed_out
The model drafts fast, but the engineer still answers for it.
on-screen: AI drafts, the engineer answers
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→AI drafts, the engineer answers

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

Social captions supplemental published copy · per channel (comp_id level)

tiktokAI can write the code now, but someone still owns what it wrote. AI-assisted: write the TEST first, let the model code until it's green, ship small commits you can undo, and review every line. Owning the bug means owning the code. Method below.
instagramAI writes code. You still own it. Write the test first. Let AI code till green. Small, undoable commits. Review every line. #softwaredevelopment #coding #ai #engineering #temerarii
linkedinAI can write the code now, but somebody still has to own what it wrote. How we build with a model in the loop: write the test that proves the feature first, then let the model write code until the test goes green; ship in small commits you can read in one sitting so any bad change is easy to undo; and review every line, because owning the bug means owning the code. Takeaway: readable beats clever, and the engineer still answers for it.
xAI writes the code. You still own it. Write the test first → let AI code till green → small undoable commits → review every line. Owning the bug means owning the code. temerarii.com
facebookAI can write the code now, but somebody still has to own what it wrote. Here's how we build with a model in the loop: write the test that proves the feature first, let the model write code until it goes green, ship in small commits you can undo, and review every line. Readable beats clever. Want the workflow? It's on the site.
threadsAI writes the code, but you still own it. Write the test first, let the model code till green, ship small undoable commits, review every line. Owning the bug means owning the code.
pinterestAI-assisted software development: how to write tests first, let AI code to green, ship small reviewable commits, and own the code. Plain-language engineering workflow guide for developers using AI.
blueskyAI writes the code, but you still own it. Write the test first, let AI code till green, small undoable commits, review every line. Owning the bug means owning the code. temerarii.com
youtubeSoftware Development With AI In The Loop (Without Losing The Plot) AI can write the code now, but somebody still has to own what it wrote. This walkthrough shows how we build: write the test that proves the feature first, let the model write code until the test goes green, ship in small commits you can read in one sitting, and review every line because owning the bug means owning the code. Readable beats clever. AI-assisted production. Give-it-away method from The Big T-M. Chapters: who owns the code · test first · green is proof · small commits · review the diff.

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

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