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 W48-it-dev-pillar-beat-1kind cellweek W48date 2026-11-29campaign it-dev-pillarpillar it_devbeat 1asset videoduration 37.0sground blackscenes 6

Checklist the per-video bar — engine/sim

97.3/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review W48-it-dev-pillar-beat-1 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 CodeWindow
9:16 Reelrendered1:1 Squarerendered16:9 Widerendered9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 3/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 6 scenes · 37.0s · 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.1sspatial-parallaxicon·liquid-chrome♪ bed in
Underneath every campaign is plumbing nobody sees until it leaks. We build the plumbing on purpose.
on-screen: The operating layer
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→The operating layer
2s2
matches intent
KpiGrid
template
subservice6.1–12.1stype-onicon·wireframe♪ —
We design the site and write the software so the front door and the back office speak the same language.
on-screen: Web and software, built right
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground blacktreatment wireframemotion type-onpower summoninstrument laser-trace→Web and software, built rightcurate kpis, statsLabels
3s3
matches intent
RankList
template
subservice12.1–19.0stype-onicon·wireframe♪ —
Repetitive work gets handed to automated workflows on Claude Code, so people stop doing what a script can do.
on-screen: Automations that run themselves
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion type-onpower summoninstrument laser-trace→Automations that run themselvescurate rows, statsLabels
4s4
matches intent
StatScoreboard
template
subservice19.0–24.9stype-onicon·wireframe♪ —
Systems get hardened and monitored, because the cheapest breach is the one you designed out before it happened.
on-screen: Secured and watched
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion type-onpower summoninstrument laser-trace→html-in-canvas-receiptscurate pillar, stats, statsLabels
5s5
matches intent
BuildLog
template
subservice24.9–30.599999999999998stype-onicon·wireframe♪ —
Dashboards turn your scattered data into one screen a person can read and act on.
on-screen: Dashboards you can read
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · receipts · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual receiptsshape boxground blacktreatment wireframemotion type-onpower summoninstrument laser-trace→Dashboards you can readcurate lines, statsLabels
6s6
matches intent
shared field
signature-3d
resolve30.6–37.0scoalescenceicon·liquid-chrome♪ bed out
Build it, secure it, see it, open it. That is the operating layer — come look at the hub.
on-screen: temerarii.xyz
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→temerarii.xyz

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)

tiktokEvery campaign sits on plumbing nobody sees until it leaks. We build the front door, the software, the automations, and the dashboards as one system you own. Build it, secure it, see it. (AI-assisted)
instagramThe operating layer. Site + software, built to speak the same language. Work a script can do, handed to a script. Hardened and watched. One dashboard a human can read. You own the code and the IP. #operatinglayer #automation #claudecode #BI #ownyourstack
linkedinMost teams buy the front-end and rent the back-end, then wonder why the two never talk. We build the operating layer as one system: the site and the software share a language, repetitive work runs on automated workflows in Claude Code, systems are hardened and monitored, and the data lands on one screen a person can act on. You own the code and the IP. The cheapest breach is the one you designed out before it happened.
xUnderneath every campaign is plumbing nobody sees until it leaks. We build it on purpose: site, software, automations, security, dashboards. One layer, you own it. temerarii.xyz
facebookUnderneath every campaign is plumbing nobody sees until it leaks. We build that plumbing on purpose: the site and the software speak the same language, the boring work runs itself, the system is hardened and watched, and your data lands on one readable screen. Come look at the hub.
threadsUnderneath every campaign is plumbing nobody sees until it leaks. So we build it on purpose. Site and software speaking the same language. Boring work handed to a script. Hardened and watched. One screen you can actually read. Build it, secure it, see it, own it.
pinterestThe operating layer for a small business: web design and custom software built together, automated workflows on Claude Code, hardened and monitored systems, and business intelligence dashboards on one readable screen. Own your code and your IP. A plain guide to building the back-end the right way.
blueskyEvery campaign sits on plumbing nobody sees until it leaks. So we build it on purpose: site, software, automations, security, one readable dashboard. One layer, and you own it.
youtubeTitle: The Operating Layer — Build It, Secure It, See It, Own It Underneath every campaign is plumbing nobody sees until it leaks. In this walkthrough we show the operating layer we build for clients: web design and custom software that speak the same language, repetitive work handed to automated workflows on Claude Code, systems hardened and monitored, and business intelligence that turns scattered data into one screen a person can act on. You own the code and the IP. Come look at the hub at temerarii.xyz.

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