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-W31-Sun-2kind threadweek W31date 2026-08-02campaign thread · Sunpillar emerging_techbeat Sunasset videoduration 56.8sground redscenes 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-W31-Sun-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–6.3sspatial-parallaxicon·white-knockout♪ bed_in
The old internet of things was a shed full of sensors that beeped and got ignored.
on-screen: Sensors that just beeped
expected on screen: red 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 redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Sensors that just beeped
2s2
matches intent
shared field
signature-3d		hook6.3–12.2skinetic-buildicon·white-knockout♪ node_lock
Dark truth: a sensor nobody reads is just a battery slowly dying in a corner.
on-screen: Data nobody reads is junk
expected on screen: red ground · cone hero in the shared Signal Field · Augur leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape coneground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Data nobody reads is junk
3s3
matches intent
NumberedList
template		teach12.2–18.5skinetic-buildicon·liquid-chrome♪ node_lock
The old fix that still holds: make devices send events on change, not readings every second.
on-screen: Send events, not readings
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape coneground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Send events, not readingscurate items, nodes
4s4
matches intent
ComparisonTable
template		proof18.5–24.8sreceipts-counticon·white-knockout♪ node_lock
Give each device one named topic, like a mailbox, so you always know who said what.
on-screen: One topic per thing
expected on screen: red 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 redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→One topic per thingcurate colA, colB, rows, statsLabels
5s5
matches intent
JsonDiff
template		diff24.8–30.700000000000003scrossfade-8ficon·liquid-chrome♪ node_lock
Polling every second drowns the network. A device that speaks only when something changes scales.
on-screen: Old: poll. Right: notify
expected on screen: red 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 redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Old: poll. Right: notifycurate codeLines, fileName, lines
6s6
matches intent
ChecklistCard
template		teach30.7–37.0skinetic-buildicon·white-knockout♪ node_lock
Buffer readings on the device, so a dropped signal doesn't erase the last hour of life.
on-screen: Buffer at the edge
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Buffer at the edgecurate items, nodes
7s7
matches intent
KpiGrid
template		proof37.0–44.3sreceipts-counticon·liquid-chrome♪ node_lock
We hold this rule at The Big T-M. The edge keeps a small memory so the cloud can nap.
on-screen: No lost hour of data
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape coneground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→No lost hour of datacurate kpis, statsLabels
8s8
matches intent
SchematicCard
template		step44.3–50.199999999999996skinetic-buildicon·white-knockout♪ node_lock
Your move: send on change, name one topic each, buffer at the edge, then forward.
on-screen: Steps: events, topics, buffer
expected on screen: red ground · a SchematicCard panel over a dimmed Signal Field · Augur leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual pipelineshape coneground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Steps: events, topics, buffercurate nodes, stages, steps
9s9
matches intent
shared field
signature-3d		resolve50.2–56.800000000000004scoalescenceicon·white-knockout♪ bed_out
Now the network is quiet, the signal is loud, and the dying batteries finally get a rest.
on-screen: Quiet network, loud signal
expected on screen: red 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 redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Quiet network, loud signal

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)

tiktokWhy your IoT setup is drowning: it polls every second. Fix it the old reliable way, devices send events ONLY on change, one named topic each, buffer at the edge so a dropped signal doesn't erase an hour. #IoT #embedded
instagramStop polling every second. Send events on change. One named topic per device. Buffer at the edge. #IoT #embedded #engineering #devtips #temerarii
linkedinA durable rule for IoT that predates the AI hype: devices should send events on change, not readings on a timer. Give each device one named topic so the source is always clear, and buffer locally so a dropped connection doesn't erase the last hour. Quiet network, loud signal.
xYour IoT is drowning because it polls every second. Send events on change. One topic per device. Buffer at the edge. Quiet network, loud signal. temerarii.com
facebookThe old, reliable way to do the internet of things: devices send events when something changes, each gets one named topic, and they buffer locally so a dropped signal never erases an hour of data. Full method, free on the site.
threadsA sensor nobody reads is a battery dying in a corner. Send events on change, not readings on a timer. One named topic per device. Buffer at the edge. The network gets quiet and the signal gets loud.
pinterestInternet of Things best practices: event-driven messaging instead of polling, one named MQTT-style topic per device, and edge buffering so dropped connections never lose data. Reliable IoT architecture that scales without flooding the network.
blueskyYour IoT drowns because it polls every second. Send events on change, one topic per device, buffer at the edge. Quiet network, loud signal. temerarii.com
youtubeInternet of Things Done Right: Event-Driven, Named Topics, Edge Buffering The old reliable method still wins: devices send events on change instead of polling on a timer, each device gets one named topic so the source is clear, and they buffer locally so a dropped connection never erases an hour of data. Quiet network, loud signal. Free deep-dive at temerarii.com

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

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