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-Wed-1kind threadweek W32date 2026-08-12campaign thread · Wedpillar emerging_techbeat Wedasset videoduration 54.9sground whitescenes 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-Wed-1 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 · 54.9s · 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
A normal app lives on one company's server, and that company holds the off switch.
on-screen: Old apps live on one company's server
expected on screen: white 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 whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Old apps live on one company's server
2s2
matches intent
shared field
signature-3d
hook5.9–12.2skinetic-buildicon·color♪ node_lock
A DApp runs on shared rails, so no single owner can flip the switch on you.
on-screen: A DApp runs on shared rails
expected on screen: white ground · cone hero in the shared Signal Field · Augur leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape coneground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→A DApp runs on shared rails
3s3
matches intent
NumberedList
template
teach12.2–18.799999999999997skinetic-buildicon·color♪ node_lock
The move is putting the rules in a public contract anyone can read before they trust it.
on-screen: Logic lives in a public contract
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape coneground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Logic lives in a public contractcurate items, nodes
4s4
matches intent
RankList
template
proof18.8–25.4sreceipts-counticon·color♪ node_lock
You can read exactly what the app will do, instead of taking a terms page on faith.
on-screen: Read the code before you trust it
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape coneground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Read the code before you trust itcurate rows, statsLabels
5s5
matches intent
CodeWindow
template
diff25.4–31.299999999999997scrossfade-8ficon·color♪ node_lock
A normal app can change its rules overnight; an open contract changes in the open.
on-screen: Normal apps change rules quietly
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Augur leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape coneground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Normal apps change rules quietlycurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template
teach31.3–37.2skinetic-buildicon·color♪ node_lock
Start small: build a read-only DApp that just shows public data, no money at risk.
on-screen: Start with a read-only DApp
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Start with a read-only DAppcurate items, nodes
7s7
matches intent
StatScoreboard
template
proof37.2–43.1sreceipts-counticon·color♪ node_lock
Read-only first means you learn the rails before a single dollar is on the line.
on-screen: Read-only first means low stakes
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape coneground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Read-only first means low stakescurate pillar, stats, statsLabels
8s8
matches intent
NodeGraphCard
template
step43.1–49.0skinetic-buildicon·color♪ node_lock
Read public data first, add the write steps later once you trust your own code.
on-screen: Read public data, then add writes
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Augur leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape coneground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Read public data, then add writescurate hub, nodes, stages, steps
9s9
matches intent
shared field
signature-3d
resolve49.0–54.9scoalescenceicon·wireframe♪ bed_out
That is the promise of a DApp: software no single hand can quietly switch off.
on-screen: Apps no one can switch off
expected on screen: white 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 whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Apps no one can switch off

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)

tiktokDApps explained without the crypto-bro energy (AI-assisted). A normal app lives on one company's server — they hold the off switch. A DApp runs on shared rails, and the rules live in a PUBLIC contract you can read before you trust it. No quiet overnight rule changes. Start small: build a read-only DApp that just shows public data, no money at risk. #dapps #web3 #blockchain
instagramDApps, minus the hype. Normal app = one company holds the off switch. DApp = shared rails, public rules. Start read-only, no money at risk. #dapps #web3 #blockchain #decentralized #tech
linkedinDApps, explained without the hype: A normal app lives on one company's server — and that company holds the off switch and can change the rules overnight. A DApp runs on shared rails, with its logic in a public contract anyone can read before they trust it. The rules can still change, but they change in the open. If you want to learn this without risk: build a read-only DApp first — one that just displays public on-chain data, no money involved. You learn the rails before a single dollar is on the line, then add write operations once you trust your own code. Takeaway: read-only first is the safe on-ramp.
xDApps minus the hype: a normal app lives on one company's server (they hold the off switch). A DApp runs on shared rails with rules in a public contract you can read. Start read-only, no money at risk. temerarii.com
facebookA DApp, in plain words: a normal app lives on one company's server, and that company holds the off switch. A DApp runs on shared rails, with its rules in a public contract anyone can read before they trust it — no quiet overnight changes. Want to learn it safely? Build a read-only DApp first that just shows public data, with no money at risk. Here's the on-ramp.
threadsDApps minus the hype: a normal app lives on one company's server (they hold the off switch). A DApp runs on shared rails, with rules in a public contract you can read before you trust it. Start read-only — just show public data, no money at risk — then add writes later.
pinterestWhat is a DApp? A plain-language guide to decentralized apps: how they run on shared rails instead of one company's server, why their logic lives in a public smart contract you can read, and how to start safely with a read-only DApp. Web3 and blockchain basics for beginners.
blueskyDApps minus the hype: a normal app lives on one company's server (off switch theirs). A DApp runs on shared rails with rules in a public contract. Start read-only, no money at risk. temerarii.com
youtubeDApps Explained: Apps No Single Company Can Switch Off A normal app lives on one company's server, and that company holds the off switch and can change the rules overnight. This short explains DApps: software that runs on shared rails, with its logic in a public contract anyone can read before they trust it. The safe way to learn it: build a read-only DApp first — one that just displays public on-chain data, no money involved — then add write operations once you trust your own code. More at temerarii.com.

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