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 thread-minus-the-hype-W25-Monkind threadweek W25date 2026-06-22campaign thread · Monpillar strategic_relationsbeat Monasset videoduration 29.4sground whitescenes 5

Checklist the per-video bar — engine/sim

78.3/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-minus-the-hype-W25-Mon good|bad)
⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template BoldStatement
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 5 scenes · 29.4s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–7.0skinetic-buildicon·wireframe♪ node_lock
They say point AI at your data and a perfect dashboard appears. Then it charts vanity numbers nobody decides on.
on-screen: "Dashboards build themselves"
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→"Dashboards build themselves"
2s2
matches intent
StackTrace
template
diff7.0–14.4scrossfade-8ficon·wireframe♪ node_lock
What actually works: name the one decision you make weekly, then we query GA4 for the two metrics that drive it.
on-screen: Define the decision first
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape tetraground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Define the decision firstcurate codeLines, errMsg, errType, fix, frames
3s3
first render · fix pending
ChecklistCard
templatedead_air
teach14.4–19.4skinetic-buildicon·wireframe♪ node_lock
The cost is the thinking, not the charting. You still have to pick the one number that decides what you do next.
on-screen: The cost: knowing the number
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→The cost: knowing the numbercurate items, nodes
4s4
first render · fix pending
RankList
templatedead_airgeneric_scene
proof19.4–24.4sreceipts-counticon·wireframe♪ node_lock
Minus the Hype
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Minus the Hypecurate rows, statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve24.4–29.4scoalescenceicon·3d-extrude♪ bed_out
Minus the Hype
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Minus the Hype

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)

tiktokThey say point AI at your data and a perfect dashboard appears. Then it charts numbers nobody acts on. The real move: name the one decision you make weekly, then pull the two metrics that drive it from GA4. The cost is the thinking, not the charting. (AI-assisted)
instagram"Dashboards build themselves." Then they chart numbers nobody acts on. The real move: name the one weekly decision first. Pull the two GA4 metrics that drive it. The cost is the thinking, not the charting. #analytics #ga4 #dataviz #aimarketing #thebigtm
linkedinThe pitch: point AI at your data and a perfect dashboard appears. The reality: it charts vanity numbers nobody decides on. Here is the method we actually use. Name the one decision you make every week. Then query GA4 for the two metrics that drive that decision. That is the whole dashboard. The hard part was never the charting. It is knowing which number matters. Do that thinking first and the build is trivial.
x"AI builds your dashboard for you." Then it charts numbers nobody acts on. The move: name the one weekly decision, then pull the 2 GA4 metrics that drive it. The cost is the thinking, not the charting. temerarii.xyz/build
facebookThey say point AI at your data and a perfect dashboard appears. Then it charts numbers nobody decides on. Here is what works: name the one decision you make every week, then pull the two GA4 metrics that drive it. The cost is the thinking, not the charting. Try it on your own dashboard this week.
threads"Dashboards build themselves." Sure, and then they chart numbers nobody acts on. The real move: name the one decision you make weekly. Then pull the two GA4 metrics that drive it. The cost is the thinking, not the charting.
pinterestHow to build a useful analytics dashboard with AI: skip the auto-generated vanity charts. First name the one decision you make each week, then query GA4 for the two metrics that drive it. A decision-first method for GA4 reporting from The Big T-M.
bluesky"Dashboards build themselves." Then they chart numbers nobody acts on. The move: name your one weekly decision, then pull the 2 GA4 metrics that drive it. The cost is the thinking, not the charting.
youtubeTitle: Why AI Dashboards Chart the Wrong Numbers | Minus the Hype The pitch says point AI at your data and a perfect dashboard appears. In practice it charts vanity numbers nobody acts on. The method that works: name the one decision you make every week, then query GA4 for the two metrics that drive it. The cost is the thinking, not the charting. The Big T-M, method-only, no hype.

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