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-W37-Tue-2kind threadweek W37date 2026-09-15campaign thread · Tuepillar emerging_techbeat Tueasset videoduration 56.8sground 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-W37-Tue-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 · 56.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–5.9sspatial-parallaxicon·wireframe♪ bed_in
For years an app meant trusting one company's server with all your data and rules.
on-screen: Apps trusted one company's server
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape coneground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Apps trusted one company's server
2s2
matches intent
shared field
signature-3d		hook5.9–11.8skinetic-buildicon·wireframe♪ node_lock
The risk people ignore: if that server changes the rules quietly, you would never know.
on-screen: If the server lies, you cannot tell
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape coneground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→If the server lies, you cannot tell
3s3
matches intent
NumberedList
template		teach11.8–19.5skinetic-buildicon·wireframe♪ node_lock
Here is what a dapp does: it puts the rules in open code anyone can read, running on shared infrastructure.
on-screen: A dapp puts rules in the open
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→A dapp puts rules in the opencurate items, nodes
4s4
matches intent
RankList
template		proof19.5–26.1sreceipts-counticon·wireframe♪ node_lock
So you do not have to trust a promise; you can check the code that actually runs.
on-screen: Anyone can verify, not just trust
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape coneground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Anyone can verify, not just trustcurate rows, statsLabels
5s5
matches intent
StackTrace
template		diff26.1–31.3scrossfade-8ficon·wireframe♪ node_lock
The old way said trust me; the new way says read it yourself.
on-screen: Old way: trust. New way: verify
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Augur leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape coneground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Old way: trust. New way: verifycurate codeLines, errMsg, errType, fix, frames
6s6
matches intent
ChecklistCard
template		teach31.3–39.7skinetic-buildicon·wireframe♪ node_lock
Now we do it with AI: a model reads the contract and explains in plain words what it can and cannot do.
on-screen: Now AI explains the contract plainly
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Now AI explains the contract plainlycurate items, nodes
7s7
matches intent
StatScoreboard
template		proof39.7–44.7sreceipts-counticon·wireframe♪ node_lock
Plain-language review beats blind faith and beats a forty-page document nobody reads.
on-screen: Plain words beat blind faith
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape coneground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Plain words beat blind faithcurate pillar, stats, statsLabels
8s8
matches intent
NodeGraphCard
template		step44.7–51.300000000000004skinetic-buildicon·wireframe♪ node_lock
Your move: read the open rules, have AI flag the risky ones, then decide with eyes open.
on-screen: Steps: read rules, verify, then trust
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Augur leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape coneground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: read rules, verify, then trustcurate hub, nodes, stages, steps
9s9
matches intent
shared field
signature-3d		resolve51.3–56.8scoalescenceicon·wireframe♪ bed_out
That is how The Big T-M builds apps you can audit, not just believe.
on-screen: Build apps you can audit
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape coneground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Build apps you can audit

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)

tiktokWhat a dapp actually is (plain version): a normal app trusts one company's server. A dapp puts its rules in OPEN code anyone can read. You verify instead of trust. We use AI to explain the contract in plain words. AI-assisted. #dapps #web3 #blockchain #crypto #tech
instagramApps say: trust me. Dapps say: read it. Verify, don't believe. #dapps #web3 #blockchain #crypto #decentralized
linkedinA decentralized app changes the trust model. A normal app runs on one company's server, and if the rules change quietly, you'd never know. A dapp puts its rules in open code anyone can read, running on shared infrastructure, so you verify instead of trust. The practical upgrade: use AI to read the contract and explain in plain language what it can and cannot do, because a forty-page document nobody reads protects no one. Read the rules, flag the risky ones, then decide with eyes open.
xNormal app: trust one company's server. Dapp: rules in open code anyone can read. Verify instead of trust. AI explains the contract in plain words. temerarii.com
facebookA normal app trusts one company's server, and if the rules change quietly you'd never know. A dapp puts its rules in open code anyone can read. We use AI to explain the contract in plain words so you verify instead of trust. More at temerarii.com.
threadsApps say trust me. Dapps say read it. A dapp puts its rules in open code anyone can check, running on shared infrastructure. We use AI to explain the contract in plain words, because a 40-page document nobody reads protects nobody.
pinterestDecentralized apps explained: dapps put rules in open code you can verify instead of trusting one company's server. Use AI to read contracts in plain language. Web3 basics, blockchain apps, dapp fundamentals.
blueskyApps say trust me. Dapps put rules in open code anyone can read. Verify instead of trust, and use AI to explain the contract plainly. temerarii.com
youtubeDapps Explained: Verify Instead of Trust (Plain Language) A normal app trusts one company's server. A dapp puts its rules in open code anyone can read. We cover the trust model shift and using AI to explain a contract in plain words so you can audit risk instead of believing a promise. AI-assisted. More at temerarii.com. #Dapps #Web3 #Blockchain

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

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