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-st-datakind topicweek —date —campaign staff-training-pillarpillar staff_trainingbeat —asset videoduration 85.1sground blackscenes 14

Checklist the per-video bar — engine/sim

96.1/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-st-data good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · 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 · 85.1s · 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.7sspatial-parallaxicon·white-knockout♪ —
You are drowning in dashboards and still cannot answer the one question your boss keeps asking.
on-screen: You have data. Now what?
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
ProcessFlow
template		legacy5.7–11.3scrossfade-8ficon·wireframe♪ —
The old way was a Monday spreadsheet stitched together by hand, stale by the time anyone read it.
on-screen: The spreadsheet swamp
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Magister leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowshape knotground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate steps
3s3
matches intent
NumberedList
template		teach11.3–17.5skinetic-buildicon·wireframe♪ —
We start from the decision, not the data: what will you actually do differently based on the answer?
on-screen: Step 1: the one question
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template		teach17.5–24.5skinetic-buildicon·wireframe♪ —
Then we define the metric precisely, because half of marketing arguments are two people meaning different things by conversion.
on-screen: Step 2: name the metric
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
BlueprintGrid
template		teach24.5–32.2skinetic-buildicon·wireframe♪ —
We connect straight to the source, GA4, the ad platform, the CRM, so the number is live, not retyped.
on-screen: Step 3: pull from the source
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, rows
6s6
matches intent
WireframeMock
template		teach32.2–38.6skinetic-buildicon·wireframe♪ —
An agent turns your plain-English question into the actual query, then shows you the query it ran.
on-screen: Step 4: agent writes the query
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes
7s7
matches intent
CheatSheet
template		teach38.6–44.9skinetic-buildicon·wireframe♪ —
We sanity-check the result against a number you already know, so a wrong query gets caught before the meeting.
on-screen: Step 5: trust but check
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, points, uses
8s8
matches intent
JsonDiff
template		teach44.9–50.199999999999996skinetic-buildicon·wireframe♪ —
We pick the chart the eye reads fastest, because a confusing graph is worse than a clean table.
on-screen: Step 6: chart for the eye
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate fileName, lines, nodes
9s9
matches intent
StackTrace
template		teach50.2–56.2skinetic-buildicon·wireframe♪ —
Every spike gets a note explaining the cause, so future-you is not guessing what happened in March.
on-screen: Step 7: annotate the why
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate errMsg, errType, fix, frames, nodes
10s10
matches intent
StepFlow
template		teach56.2–62.2skinetic-buildicon·wireframe♪ —
The report rebuilds itself on a schedule, so the dashboard is never the thing someone forgot to update.
on-screen: Step 8: refresh on schedule
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, steps
11s11
matches intent
ListCard
template		teach62.2–67.60000000000001skinetic-buildicon·wireframe♪ —
We end every report with the single metric the team should act on this week, not forty they will
on-screen: Step 9: one number that matters
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
12s12
matches intent
ComparisonTable
template		proof67.6–73.5sreceipts-counticon·wireframe♪ —
That is a question asked in English and answered from the live source, checked, charted, and dated.
on-screen: Question to answer, live
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate colA, colB, rows, statsLabels
13s13
matches intent
shared field
signature-3d		futurist73.5–79.2sspatial-parallaxicon·wireframe♪ —
When anyone can ask the data a question in plain words, the whole team stops waiting on the analyst.
on-screen: What this unlocks
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape knotground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
14s14
matches intent
shared field
signature-3d		resolve79.2–85.10000000000001scoalescenceicon·white-knockout♪ swell
Bring the question your dashboards never answer. We will wire it to the source. temerarii.xyz.
on-screen: Bring the question
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment white-knockoutmotion 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)

tiktokYou have a hundred dashboards and still cannot answer the one question your boss keeps asking. (AI-assisted) Start from the decision, not the data: what would you do differently based on the answer? Name the metric exactly, because half of marketing fights are two people meaning different things by conversion. Connect straight to the source so the number is live, not retyped. Let an agent turn your plain-English question into the query, and show you the query it ran. Then sanity-check it against a number you already know before the meeting.
instagramDrowning in dashboards. Still can't answer the one question. Fix it: Start from the decision, not the data Name the metric exactly Pull from the live source Let an agent write the query Check it against a known number End with one metric to act on this week. #Analytics #GA4 #DataDriven #Marketing #Temerarii
linkedinYou are drowning in dashboards and still cannot answer the one question your boss keeps asking. Here is the method, given away. The old way was a Monday spreadsheet stitched together by hand, stale by the time anyone read it. The better way: 1. Start from the decision, not the data: what will you actually do differently based on the answer? 2. Define the metric precisely, because half of marketing arguments are two people meaning different things by conversion. 3. Connect straight to the source, GA4, the ad platform, the CRM, so the number is live, not retyped. 4. Let an agent turn your plain-English question into the query, then show you the query it ran. 5. Sanity-check the result against a number you already know, so a wrong query gets caught before the meeting. 6. Pick the chart the eye reads fastest, and annotate every spike with its cause. End every report with the single metric the team should act on this week. Bring the question your dashboards never answer. We will wire it to the source. temerarii.xyz
xDrowning in dashboards, still can't answer the one question? Start from the decision, not the data Name the metric exactly Pull from the live source Agent writes the query, shows its work Check vs a known number temerarii.xyz
facebookYou are drowning in dashboards and still cannot answer the one question your boss keeps asking. Here is the method. Start from the decision, not the data: what would you do differently based on the answer? Name the metric exactly. Connect straight to the live source so the number is not retyped. Let an agent turn your plain question into the query and show you the query it ran. Then check it against a number you already know before the meeting. Bring the question your dashboards never answer. temerarii.xyz
threadsDrowning in dashboards, still can't answer the one question your boss keeps asking? Start from the decision, not the data. Name the metric exactly. Pull from the live source. Let an agent write the query and show its work. Check it against a number you already know. End with the one metric to act on this week.
pinterestHow to answer a data question without the Monday spreadsheet swamp: start from the decision, define the metric exactly, pull from the live source like GA4, let an agent write and show the query, then check it against a known number. A plain analytics method for marketing teams.
blueskyDrowning in dashboards, still can't answer the one question? Start from the decision, not the data. Name the metric exactly. Pull from the live source. Agent writes the query and shows its work. Check vs a known number. Bring the question. temerarii.xyz
youtubeAnswer the One Question Your Dashboards Never Could (Live From the Source) You are drowning in dashboards and still cannot answer the one question your boss keeps asking. This walks the full method and gives it away. The old way was a Monday spreadsheet stitched together by hand, stale by the time anyone read it. The method: 1. Start from the decision, not the data: what will you do differently based on the answer? 2. Define the metric precisely, because half of marketing arguments are two people meaning different things by conversion. 3. Connect straight to the source, GA4, the ad platform, the CRM, so the number is live, not retyped. 4. An agent turns your plain-English question into the query, then shows you the query it ran. 5. Sanity-check the result against a number you already know, so a wrong query gets caught before the meeting. 6. Pick the chart the eye reads fastest. Annotate every spike with its cause. 7. Refresh on a schedule so nothing is forgotten. End every report with the single metric the team should act on this week. Bring the question your dashboards never answer. We will wire it to the source. 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