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-it-bikind topicweek —date —campaign it-dev-pillarpillar it_devbeat —asset videoduration 94.7sground blackscenes 14

Checklist the per-video bar — engine/sim

95.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-it-bi good|bad)
⚠ 1 flag(s) — not yet ship-ready: too_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 · 94.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–7.2sspatial-parallaxicon·white-knockout♪ —
Business intelligence is just turning your scattered data into answers a human can act on. The Big T-M teaches the build.
on-screen: Business intelligence, plain
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
BuildLog
template		legacy7.2–13.2scrossfade-8ficon·wireframe♪ —
The old way was five people exporting five spreadsheets and arguing about whose number was right.
on-screen: The old way: dueling spreadsheets
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate lines
3s3
matches intent
NumberedList
template		teach13.2–19.9skinetic-buildicon·wireframe♪ —
Start by piping every source into a single warehouse like BigQuery, so there is exactly one place numbers live.
on-screen: One warehouse, one truth
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template		teach19.9–26.7skinetic-buildicon·wireframe♪ —
Use a connector like Fivetran or Airbyte to load data on a schedule, so nobody is copy-pasting at midnight.
on-screen: Pipe data in automatically
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
ProcessFlow
template		teach26.7–34.2skinetic-buildicon·wireframe♪ —
Clean and join the raw tables with dbt, so your definitions of revenue and customer are written down once and reused.
on-screen: Model it with dbt
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, steps
6s6
matches intent
StepFlow
template		teach34.2–41.6skinetic-buildicon·wireframe♪ —
Agree on what active user means before you draw anything, because a chart of the wrong metric is just decorated confusion.
on-screen: Define the metric, not the chart
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, steps
7s7
matches intent
CheatSheet
template		teach41.6–47.5skinetic-buildicon·wireframe♪ —
Build dashboards in something like Metabase or Looker that answer one question per screen, not forty.
on-screen: Dashboards people open
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, points, uses
8s8
matches intent
WireframeMock
template		teach47.5–54.2skinetic-buildicon·wireframe♪ —
Wire alerts that ping you when a number breaks its band, so the dashboard works even when nobody is staring at it.
on-screen: Alert, don't just display
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
9s9
matches intent
TerminalRun
template		teach54.2–60.6skinetic-buildicon·wireframe♪ —
Put a query layer on top so a manager can ask in plain English and a model writes the SQL underneath.
on-screen: Let people ask in English
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
10s10
matches intent
StackTrace
template		teach60.6–68.1skinetic-buildicon·wireframe♪ —
Add data tests in dbt that fail loudly when a row count looks wrong, because silent bad data is the real enemy.
on-screen: Trust it by testing it
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate errMsg, errType, fix, frames, nodes
11s11
matches intent
NodeGraphCard
template		teach68.1–75.19999999999999skinetic-buildicon·wireframe♪ —
Keep your models and dashboards in git, so when a number changes you can see exactly who changed the definition and when.
on-screen: Version everything
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate hub, nodes
12s12
matches intent
ComparisonTable
template		proof75.2–81.0sreceipts-counticon·wireframe♪ —
One client went from a three-day reporting scramble to a three-minute glance, on the same raw data.
on-screen: From 3 days to 3 minutes
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate colA, colB, rows, statsLabels
13s13
matches intent
shared field
signature-3d		futurist81.0–87.8sspatial-parallaxicon·wireframe♪ —
Soon the dashboard writes its own summary of what moved and why, and you read a paragraph instead of squinting at lines.
on-screen: The dashboard explains itself
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape boxground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
14s14
matches intent
shared field
signature-3d		resolve87.8–94.7scoalescenceicon·white-knockout♪ swell
Stop arguing about numbers and start trusting one. The Big T-M builds the stack at temerarii.xyz.
on-screen: temerarii.xyz
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground 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)

tiktokFive people, five spreadsheets, arguing about whose number is right. (AI-assisted.) That's the problem BI fixes. The build: pipe every source into one warehouse like BigQuery, so numbers live in exactly one place. Load it on a schedule with a connector. Clean and join the raw tables with dbt, so revenue is defined once. Agree on what active user means before you draw a chart. Build dashboards that answer one question per screen. Then add tests that fail loudly on bad data. temerarii.xyz.
instagramFive people. Five spreadsheets. One argument about whose number is right. Business intelligence fixes that. The build: One warehouse, one truth. Load data on a schedule. Model it with dbt. Define the metric before the chart. Test it so bad data fails loud. Build the stack at temerarii.xyz #BusinessIntelligence #DataStack #dbt #BuildInPublic #Temerarii
linkedinBusiness intelligence is just turning your scattered data into answers a human can act on. The old way was five people exporting five spreadsheets and arguing about whose number was right. The build: 1. Pipe every source into a single warehouse like BigQuery, so there is exactly one place numbers live. 2. Use a connector like Fivetran or Airbyte to load data on a schedule, so nobody is copy-pasting at midnight. 3. Clean and join the raw tables with dbt, so your definitions of revenue and customer are written down once and reused. 4. Agree on what "active user" means before you draw anything, because a chart of the wrong metric is decorated confusion. 5. Build dashboards that answer one question per screen, and wire alerts that ping you when a number breaks its band. 6. Add data tests that fail loudly on a bad row count, and keep models and dashboards in git so every definition change is traceable. Stop arguing about numbers and start trusting one. We build the stack. temerarii.xyz
xFive people, five spreadsheets, one argument about whose number is right. BI fixes it: one warehouse, load on a schedule, model with dbt, define the metric before the chart, dashboards that answer one question, tests that fail loud. temerarii.xyz
facebookBusiness intelligence is just turning your scattered data into answers a human can act on. The old way was five people exporting five spreadsheets and arguing about whose number was right. The build: pipe every source into one warehouse like BigQuery, so numbers live in exactly one place. Load it on a schedule with a connector so nobody is copy-pasting at midnight. Clean and join the raw tables with dbt, so revenue is defined once and reused. Agree on what active user means before you draw a chart. Build dashboards that answer one question per screen, and add tests that fail loudly when the data looks wrong. Stop arguing about numbers and start trusting one. We build the stack. temerarii.xyz.
threadsFive people, five spreadsheets, one argument about whose number is right. BI fixes it: one warehouse, load on a schedule, model with dbt, define the metric before the chart, dashboards that answer one question per screen, tests that fail loud. Build the stack at temerarii.xyz
pinterestHow to build a business intelligence stack the right way: pipe every source into one warehouse like BigQuery, load data on a schedule with a connector, model and clean it with dbt, define your metrics before drawing charts, build dashboards that answer one question per screen, and add data tests that fail loudly. A plain-language guide to trusting one number instead of arguing across five spreadsheets. temerarii.xyz
blueskyFive people, five spreadsheets, one argument about whose number is right. BI fixes it: one warehouse, load on a schedule, model with dbt, define the metric before the chart, dashboards that answer one question, tests that fail loud. Build the stack at temerarii.xyz
youtubeBuild a Business Intelligence Stack: From Dueling Spreadsheets to One Truth Business intelligence is just turning your scattered data into answers a human can act on. The old way was five people exporting five spreadsheets and arguing about whose number was right. This video walks the full build. The steps: - Pipe every source into a single warehouse like BigQuery, so there is exactly one place numbers live. - Use a connector like Fivetran or Airbyte to load data on a schedule, so nobody is copy-pasting at midnight. - Clean and join the raw tables with dbt, so your definitions of revenue and customer are written down once and reused. - Agree on what active user means before you draw anything, because a chart of the wrong metric is decorated confusion. - Build dashboards that answer one question per screen, and wire alerts that ping you when a number breaks its band. - Add data tests that fail loudly on a bad row count, and keep models and dashboards in git so every definition change is traceable. Stop arguing about numbers and start trusting one. We build the stack. 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