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-W32-Thu-2kind threadweek W32date 2026-08-13campaign thread · Thupillar emerging_techbeat Thuasset videoduration 55.4sground blackscenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W32-Thu-2 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · 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 · 55.4s · 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.2sspatial-parallaxicon·white-knockout♪ bed_in
Anyone can claim their system works; a screenshot of a dashboard proves nothing.
on-screen: Anyone can claim their system works
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape coneground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Anyone can claim it works
2s2
matches intent
shared field
signature-3d
hook5.2–11.5skinetic-buildicon·ember-fill♪ node_lock
So we just show the machine running live, with the receipts on screen as it goes.
on-screen: So we show the machine running
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape coneground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→So we show the machine running
3s3
matches intent
NumberedList
template
teach11.5–17.4skinetic-buildicon·wireframe♪ node_lock
The move is logging every step with a timestamp you can scroll back through later.
on-screen: Log every step with a timestamp
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Log every step with a timestampcurate items, nodes
4s4
matches intent
ComparisonTable
template
proof17.4–24.4sreceipts-counticon·white-knockout♪ node_lock
A running log is far harder to fake than a tidy slide that was built after the fact.
on-screen: A real log can't be faked easily
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape coneground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→A real log can't be faked easilycurate colA, colB, rows, statsLabels
5s5
matches intent
JsonDiff
template
diff24.4–30.7scrossfade-8ficon·liquid-chrome♪ node_lock
A polished demo can quietly hide every failure; a live log shows the ugly parts too.
on-screen: A polished demo can hide failures
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Augur leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual codeshape coneground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→A polished demo can hide failurescurate codeLines, fileName, lines
6s6
matches intent
ChecklistCard
template
teach30.7–37.7skinetic-buildicon·ember-fill♪ node_lock
Then expose a simple health endpoint anyone can hit to see if it is truly up right now.
on-screen: Expose a health check anyone can hit
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Expose a health check anyone can hitcurate items, nodes
7s7
matches intent
KpiGrid
template
proof37.7–43.6sreceipts-counticon·wireframe♪ node_lock
A check a stranger can run beats any promise you make in a meeting room.
on-screen: Public proof beats private promises
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape coneground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Public proof beats private promisescurate kpis, statsLabels
8s8
matches intent
BlueprintGrid
template
step43.6–49.5skinetic-buildicon·white-knockout♪ node_lock
Log the runs, expose the check, and let people verify instead of trusting your word.
on-screen: Log it, expose it, let people check
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Augur leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape coneground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Log it, expose it, let people checkcurate rows, stages, steps
9s9
matches intent
shared field
signature-3d
resolve49.5–55.4scoalescenceicon·white-knockout♪ bed_out
It actually works, and the proof is on screen, not buried in a slide deck.
on-screen: Proof on screen, not slides
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape coneground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Proof on screen, not slides

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)

tiktokIt actually works — here's the proof on screen (AI-assisted). Anyone can CLAIM their system runs; a screenshot proves nothing. So we log every step with a timestamp you can scroll back through, and expose a health check anyone can hit to see if it's truly up RIGHT NOW. A check a stranger can run beats any promise in a meeting. #buildinpublic #devops #proof
instagramProof on screen, not slides. Log every step with a timestamp. Expose a health check anyone can hit. Public proof > private promises. #buildinpublic #devops #proof #ai #automation
linkedin"It works" is a claim. Here's how we make it verifiable: Anyone can say their system runs, and a screenshot of a dashboard proves nothing — a polished demo can quietly hide every failure. So we do two things instead. First, log every step with a timestamp you can scroll back through. A running log is far harder to fake than a slide built after the fact, and it shows the ugly parts too. Second, expose a simple health endpoint anyone can hit to confirm the system is up right now. Takeaway: a check a stranger can run beats any promise you make in a meeting room. Proof on screen, not in a deck.
x"It works" is a claim. Make it verifiable: log every step with a timestamp you can scroll back, and expose a health check anyone can hit to see it's up right now. A check a stranger can run beats any promise. temerarii.com
facebookAnyone can claim their system works — a screenshot proves nothing. So we show the machine running live: every step logged with a timestamp you can scroll back through, plus a simple health check anyone can hit to confirm it's up right now. A polished demo can hide every failure; a running log shows the ugly parts too. Proof on screen, not in a slide deck. See it for yourself.
threads"It works" is a claim. We make it verifiable: log every step with a timestamp you can scroll back through, and expose a health check anyone can hit to see it's truly up right now. A polished demo hides failures; a live log shows the ugly parts. Proof on screen, not slides.
pinterestHow to prove your system actually works: log every step with timestamps and expose a public health check endpoint anyone can hit. A guide to verifiable, transparent software — why running logs beat polished demos and how public proof builds trust. Build-in-public and devops basics.
bluesky"It works" is a claim. Make it verifiable: log every step with a timestamp you can scroll back, expose a health check anyone can hit. A check a stranger can run beats any promise. temerarii.com
youtubeIt Actually Works: Proof on Screen, Not in a Slide Deck Anyone can claim their system works, and a screenshot of a dashboard proves nothing — a polished demo can quietly hide every failure. This short shows how we make "it works" verifiable: log every step with a timestamp you can scroll back through (a running log is far harder to fake than a slide built after the fact), and expose a simple health endpoint anyone can hit to confirm the system is up right now. A check a stranger can run beats any promise. More at temerarii.com.

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