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-W30-Sun-3kind threadweek W30date 2026-07-26campaign thread · Sunpillar performancebeat Sunasset videoduration 55.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-W30-Sun-3 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.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·white-knockout♪ bed_in
Most custom dashboards end up being a wall of charts nobody reads after week one.
on-screen: The dashboard everyone ignored
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→The dashboard everyone ignored
2s2
matches intent
shared field
signature-3d		hook5.9–10.9skinetic-buildicon·wireframe♪ node_lock
It looked busy and decided nothing, because it answered no real question.
on-screen: It looked busy and said nothing
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→It looked busy and said nothing
3s3
matches intent
NumberedList
template		teach10.9–17.2skinetic-buildicon·wireframe♪ node_lock
Build backward from one question, like which channel actually paid this month, then show only that.
on-screen: Start from one question, not the data
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Start from one question, not the datacurate items, nodes
4s4
matches intent
ComparisonTable
template		proof17.2–23.799999999999997sreceipts-counticon·wireframe♪ node_lock
A page that earns its keep has one number, one trend line, and one clear next action.
on-screen: One number, one trend, one action
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→One number, one trend, one actioncurate colA, colB, rows, statsLabels
5s5
matches intent
CodeWindow
template		diff23.8–30.1scrossfade-8ficon·wireframe♪ node_lock
Plenty of dashboards count clicks. We tie every metric back to money, or we cut it.
on-screen: We tie every metric to revenue
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→We tie every metric to revenuecurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template		teach30.1–36.7skinetic-buildicon·wireframe♪ node_lock
Stamp UTMs on every link the second you publish, so the source is never a guess later.
on-screen: Tag links with UTMs at publish
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Tag links with UTMs at publishcurate items, nodes
7s7
matches intent
KpiGrid
template		proof36.7–43.300000000000004sreceipts-counticon·wireframe♪ node_lock
With clean tags you can finally point at a channel and say this one earned its spot.
on-screen: Now you can defend the budget
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Now you can defend the budgetcurate kpis, statsLabels
8s8
matches intent
WireframeMock
template		step43.3–49.199999999999996skinetic-buildicon·wireframe♪ node_lock
Your move: delete half your charts and keep only the ones that change a decision.
on-screen: Your move: delete half the charts
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual pipelineshape dodecaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Your move: delete half the chartscurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve49.2–55.800000000000004scoalescenceicon·white-knockout♪ bed_out
A real dashboard does not just report the week. It tells you what to do on Monday.
on-screen: A dashboard should pick the next move
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→A dashboard should pick the next move

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)

tiktokYour custom dashboard is a wall of charts nobody reads. Fix: build backward from ONE question, tie every metric to revenue, stamp UTMs at publish. Then delete half the charts. (AI-assisted analysis.)
instagramOne number. One trend. One next action. A dashboard should pick your Monday move. #analytics #dashboards #marketingdata #datadriven #temerarii
linkedinMost custom dashboards are a wall of charts nobody reads after week one. They look busy and decide nothing. The fix is to build backward from one question, like which channel actually paid this month, then show only the number, the trend, and the next action. Tie every metric to revenue or cut it, and stamp UTMs on links at publish so source is never a guess. Takeaway: a dashboard should tell you what to do Monday.
xYour dashboard is a wall of charts nobody reads. Build backward from one question, tie every metric to revenue, stamp UTMs at publish. Delete the rest. temerarii.xyz
facebookMost custom dashboards look busy and decide nothing. Build backward from one real question (which channel actually paid this month?), show one number, one trend, one next action, and tie everything to revenue. Stamp UTMs on links at publish so the source is never a guess. Full approach on the site.
threadsDashboard truth: most are a wall of charts nobody reads. Build backward from one question, tie every metric to revenue, stamp UTMs at publish, and delete half the charts. It should pick your Monday move.
pinterestHow to build a custom analytics dashboard that actually gets used: start from one business question, show one number plus one trend and one next action, tie every metric to revenue, and tag links with UTMs at publish. Marketing analytics, dashboard design, data-driven decisions.
blueskyDashboards: build backward from one question, tie every metric to revenue, stamp UTMs at publish, delete half the charts. It should pick your Monday move. temerarii.xyz
youtubeWhy Your Custom Dashboard Is Useless (And How to Fix It) Most custom dashboards are a wall of charts nobody reads after week one. They look busy and decide nothing. We break down the fix: build backward from one question (which channel actually paid this month?), show one number, one trend, one next action, and tie every metric to revenue. Stamp UTMs on links at publish so the source is never a guess. Delete half your charts and keep only the ones that change a decision. Made with The Big T-M. AI-assisted analysis. more at temerarii.xyz

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

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