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 longform-W27-Thukind longformweek W27date 2026-07-09campaign longform-youtubepillar performancebeat asset videoduration 122.9sground redscenes 6

Checklist the per-video bar — engine/sim

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

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 6 scenes · 122.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–18.8sspatial-parallaxicon·white-knockout♪ bed_in
The hub is opening, which means it is also a target. Anything online is. So today is only about cyber security, and not the scary kind. Most break-ins are simple. Today you learn the few plain locks that stop almost all of them, the same ones we run on the hub.
on-screen: Cyber security, the locks
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Cyber security, the locks
2s2
matches intent
NumberedList
template
teach18.8–40.400000000000006skinetic-buildicon·white-knockout♪ node_lock
First lock. Never write passwords or keys directly in your code. People paste code to a public spot and hand a stranger the keys. Instead, put secrets in a vault or an environment file the app reads when it runs. The code says fetch the key, not here is the key. That one habit closes the most common door.
on-screen: Keep secrets out of the code
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Keep secrets out of the codecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach40.4–60.599999999999994skinetic-buildicon·liquid-chrome♪ node_lock
Second lock. Every tool and every person gets the smallest permission that lets them do their job, and nothing more. The posting tool can post and that is all. It cannot delete. If that key leaks, the damage is tiny because the key barely opens anything. A master key for everything is a master mistake.
on-screen: Give the smallest key that works
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Give the smallest key that workscurate items, nodes
4s4
matches intent
CodeWindow
template
teach60.6–82.6skinetic-buildicon·white-knockout♪ node_lock
Third lock. Turn on a log that records who did what and when, then actually look at it. A log nobody reads is just storage. The move is a quick weekly check, or better, an alert that pings you when something odd happens, like a login from a place you have never been. You cannot stop what you never see.
on-screen: Read the logs, on purpose
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Read the logs, on purposecurate codeLines, nodes, windowTitle
5s5
matches intent
ComparisonTable
template
proof82.6–102.39999999999999sreceipts-counticon·liquid-chrome♪ node_lock
The proof is plain. The hub holds no secret inside its code. The keys live in a vault, each tool carries the smallest key it needs, and the logs get watched. We are not claiming we are unbreakable, because nobody honest claims that. We are claiming we left no key on the welcome mat.
on-screen: Our keys live in a vault
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our keys live in a vaultcurate colA, colB, rows, statsLabels
6s6
matches intent
shared field
signature-3d
resolve102.4–122.9scoalescenceicon·white-knockout♪ bed_out
So those are the locks. Secrets in a vault, smallest keys, logs you read. Your step today is one search. Look through your own code and config for any password sitting in plain text. If you find one, move it to a vault and rotate it. Then go see how the hub does it at office.temerarii.xyz.
on-screen: Check your code for keys today
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Check your code for keys today

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

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

youtubeCyber Security Basics: Three Plain Locks That Stop Most Break-Ins Anything online is a target. Most break-ins are not clever, someone left a key in the open. This walkthrough covers the few plain locks that stop almost all of them, the same ones we run on the hub. Not the scary kind of security. The locks: - Keep secrets out of the code: never write passwords or keys directly in your files. Put them in a vault or an environment file the app reads when it runs. The code says fetch the key, not here is the key. That one habit closes the most common door. - Smallest key that works: every tool and person gets the least permission needed and nothing more. The posting tool can post and that is all, it cannot delete. If that key leaks, the damage is tiny. A master key for everything is a master mistake. - Read the logs on purpose: turn on a record of who did what and when, then actually look. A log nobody reads is just storage. A quick weekly check, or an alert when something odd happens like a login from a place you have never been. The move today: search your own code and config for any password sitting in plain text. If you find one, move it to a vault and rotate it. We hold no secret inside the hub's code, each tool carries the smallest key, and the logs get watched. Nobody honest claims they are unbreakable, but you can refuse to leave a key on the welcome mat. See how the hub does it at office.temerarii.xyz. Keywords: cyber security basics, API key security, environment variables, least privilege, audit logs, secrets management.

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