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 topic-perf-analyticskind topicweek —date —campaign performance-pillarpillar performancebeat —asset videoduration 89.9sground blackscenes 14

Checklist the per-video bar — engine/sim

98.9/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-perf-analytics good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel
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 14 scenes · 89.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–6.0sspatial-parallaxicon·wireframe♪ —
Analytics. Most of it is a dashboard nobody opens. Let us fix that, in the open.
on-screen: Analytics
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
ComparisonTable
template		legacy6.0–12.1scrossfade-8ficon·wireframe♪ —
The old way was a monthly report built by hand from five tabs, half-stale by the time it landed.
on-screen: The old way: guesswork
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTableshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate colA, colB, rows
3s3
matches intent
NumberedList
template		teach12.1–19.5skinetic-buildicon·wireframe♪ —
Step one, decide the single event that equals money for you, a booking, a signup, a sale. Everything hangs off that.
on-screen: Step 1: define the event
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→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template		teach19.5–27.2skinetic-buildicon·wireframe♪ —
Step two, fire that event into GA4 with the Measurement Protocol, server-side, so ad blockers cannot lie to you.
on-screen: Step 2: tag with GA4
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→three-diagramcurate items, nodes
5s5
matches intent
BlueprintGrid
template		teach27.2–34.2skinetic-buildicon·wireframe♪ —
Step three, pull it back out with the GA4 Data API into a sheet on a schedule, no more clicking export.
on-screen: Step 3: pull the API
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, rows
6s6
matches intent
JsonDiff
template		teach34.2–40.5skinetic-buildicon·wireframe♪ —
Step four, join those events to ad spend so you see cost per real outcome, not cost per impression.
on-screen: Step 4: join to spend
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate fileName, lines, nodes
7s7
matches intent
ListCard
template		teach40.5–47.2skinetic-buildicon·wireframe♪ —
Step five, segment by source so you know which channel actually carried the result, not which one took credit.
on-screen: Step 5: segment the source
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
8s8
matches intent
StepFlow
template		teach47.2–53.2skinetic-buildicon·wireframe♪ —
Step six, set a threshold for action, the ratio at which you scale and the one at which you
on-screen: Step 6: set the threshold
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, steps
9s9
matches intent
LogStream
template		teach53.2–60.0skinetic-buildicon·wireframe♪ —
Step seven, alert on drift. When a number moves past the line, a message hits you, you do not go hunting.
on-screen: Step 7: alert on drift
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, rows
10s10
matches intent
TerminalRun
template		teach60.0–65.9skinetic-buildicon·wireframe♪ —
Step eight, one short weekly review where you only look at the numbers tied to decisions you can actually
on-screen: Step 8: weekly review
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes
11s11
matches intent
SchematicCard
template		teach65.9–71.80000000000001skinetic-buildicon·wireframe♪ —
Step nine, write down why you made each call, so next quarter you are reasoning, not re-guessing.
on-screen: Step 9: archive the why
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes
12s12
matches intent
KpiGrid
template		proof71.8–77.2sreceipts-counticon·wireframe♪ —
That is the whole loop, no black box. We run it for ourselves and show the wiring.
on-screen: Receipts, in the open
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→html-in-canvas-receiptscurate kpis, statsLabels
13s13
matches intent
shared field
signature-3d		futurist77.2–84.0sspatial-parallaxicon·wireframe♪ —
What is next is the dashboard answering questions in plain language, so you ask why revenue dipped and it tells you.
on-screen: Next: it answers back
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape dodecaground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
14s14
matches intent
shared field
signature-3d		resolve84.0–89.9scoalescenceicon·wireframe♪ swell
Analytics that drive decisions, not decoration. The build is at temerarii dot com.
on-screen: temerarii.com
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→three-coalescence

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 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

Social captions supplemental published copy · per channel (comp_id level)

tiktokMost analytics is a dashboard nobody opens. AI-assisted way to fix it: decide the single event that equals money, a booking, a signup, a sale. Fire that event into GA4 with the Measurement Protocol, server-side, so ad blockers cannot lie to you. Pull it back out with the GA4 Data API into a sheet on a schedule. Join those events to ad spend so you see cost per real outcome. Segment by source. Set a threshold for action and alert on drift. One short weekly review. No black box. temerarii.com
instagramMost analytics is a dashboard nobody opens. Fix it. Pick the single event that equals money. Fire it into GA4 server-side, past ad blockers. Pull it back with the GA4 Data API into a sheet. Join events to ad spend for cost per real outcome. Set a threshold, alert on drift, review weekly. No black box. temerarii.com #analytics #ga4 #datadriven #marketinganalytics #temerarii
linkedinMost analytics is a dashboard nobody opens. The old way was a monthly report built by hand from five tabs, half-stale by the time it landed. Here is the loop we use instead, in the open. Decide the single event that equals money for you, a booking, a signup, a sale. Everything hangs off that. Fire that event into GA4 with the Measurement Protocol, server-side, so ad blockers cannot lie to you. Pull it back out with the GA4 Data API into a sheet on a schedule, no more clicking export. Join those events to ad spend so you see cost per real outcome, not cost per impression. Segment by source so you know which channel actually carried the result, not which one took credit. Set a threshold for action, alert on drift so a message hits you instead of you going hunting, and hold one short weekly review on the numbers tied to decisions. Write down why you made each call, so next quarter you are reasoning, not re-guessing. No black box. We run it for ourselves and show the wiring. temerarii.com
xMost analytics is a dashboard nobody opens. Pick the one event that equals money, fire it into GA4 server-side past ad blockers, pull it back via the Data API, join to ad spend, segment by source, alert on drift. temerarii.com
facebookMost analytics is a dashboard nobody opens. The old way was a monthly report built by hand from five tabs, half-stale by the time it landed. Here is the loop. Decide the single event that equals money, a booking, a signup, a sale. Fire it into GA4 with the Measurement Protocol, server-side, so ad blockers cannot lie to you. Pull it back out with the GA4 Data API into a sheet on a schedule. Join those events to ad spend so you see cost per real outcome. Segment by source. Set a threshold for action, alert on drift, and hold one short weekly review. No black box. We run it ourselves and show the wiring at temerarii.com
threadsMost analytics is a dashboard nobody opens. Pick the one event that equals money, fire it into GA4 server-side past ad blockers, pull it back with the Data API into a sheet, join to ad spend for cost per real outcome, segment by source, alert on drift, review weekly. No black box. temerarii.com
pinterestAnalytics that drive decisions, not decoration: define the single event that equals money, fire it into GA4 server-side with the Measurement Protocol past ad blockers, pull it back with the GA4 Data API into a sheet, join events to ad spend, segment by source, set a threshold, and alert on drift. Save this marketing analytics method.
blueskyMost analytics is a dashboard nobody opens. Pick the one event that equals money, fire it into GA4 server-side past ad blockers, pull it back via the Data API, join to ad spend, segment by source, alert on drift, review weekly. No black box. temerarii.com
youtubeAnalytics That Drive Decisions: GA4 Server-Side Events to a Weekly Review Most analytics is a dashboard nobody opens. The old way was a monthly report built by hand from five tabs, half-stale by the time it landed. Here is the whole loop, in the open, no black box. Step one: decide the single event that equals money for you, a booking, a signup, a sale. Everything hangs off that. Step two: fire that event into GA4 with the Measurement Protocol, server-side, so ad blockers cannot lie to you. Step three: pull it back out with the GA4 Data API into a sheet on a schedule, no more clicking export. Step four: join those events to ad spend so you see cost per real outcome, not cost per impression. Step five: segment by source so you know which channel actually carried the result. Step six: set a threshold for action. Step seven: alert on drift, so a message hits you instead of you going hunting. Step eight: one short weekly review on the numbers tied to decisions. Step nine: write down why you made each call, so next quarter you are reasoning, not re-guessing. What is next: the dashboard answering questions in plain language, so you ask why revenue dipped and it tells you. We run it for ourselves and show the wiring. 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