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-W49-Thukind longformweek W49date 2026-12-10campaign longform-youtubepillar staff_trainingbeat asset videoduration 129.9sground whitescenes 7

Checklist the per-video bar — engine/sim

96.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W49-Thu good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_genericcustom_element_dup · 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 7 scenes · 129.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–20.5sspatial-parallaxicon·3d-extrude♪ bed_in
The week says secure it, so today we mean it. We open cyber security, but the version a normal business can actually do. By the end you will know a handful of moves that block most of the trouble, without buying scary software or hiring a whole team. Most breaks are simple. So are the locks.
on-screen: Secure it, plainly
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Secure it, plainly
2s2
first render · fix pending
NumberedList
templatecustom_element_dup
teach20.5–41.0skinetic-buildicon·wireframe♪ node_lock
The first move is to stop putting passwords and keys inside your code. Move them into a secrets file the code reads at run time, and never commit that file. You can ask your agent to scan the project for keys hiding in plain sight. A key in your code is a key on the sidewalk.
on-screen: Get your secrets out of the code
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Get your secrets out of the codecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach41.0–58.7skinetic-buildicon·wireframe♪ node_lock
The second move is least access. When a tool or a person needs a key, give the smallest one that does the job. Read-only when they only need to read. One folder, not the whole drive. If that key leaks, the damage is a room, not the building.
on-screen: Give the least key that works
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Give the least key that workscurate items, nodes
4s4
matches intent
LogStream
template
teach58.7–78.2skinetic-buildicon·wireframe♪ node_lock
The third move is two-step login everywhere it is offered. A password plus a code from your phone. It is dull, it takes ten seconds, and it stops the most common attack cold, where someone has your password but not your phone. Turn it on for every account that touches money or customers.
on-screen: Turn on the second lock
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Turn on the second lockcurate nodes, rows
5s5
matches intent
TerminalRun
template
teach78.2–97.0skinetic-buildicon·wireframe♪ node_lock
The fourth move is updates. Old software is the open window. Put your updates on a clock, the same cron habit from earlier this week, and let the agent list what is out of date. You do not have to be fast and fancy. You have to be current and boring.
on-screen: Patch on a schedule, not a whim
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Patch on a schedule, not a whimcurate nodes
6s6
matches intent
KpiGrid
template
proof97.0–113.6sreceipts-counticon·wireframe♪ node_lock
Here is the honest proof. We run a security pass on our own studio, looking for keys in the code and doors left open, before we ever talk to a client about theirs. We will not sell a lock we have not turned on ourselves.
on-screen: We audit our own house
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape knotground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We audit our own housecurate kpis, statsLabels
7s7
matches intent
shared field
signature-3d
resolve113.6–129.9scoalescenceicon·3d-extrude♪ bed_out
So securing it is mostly habits: hide your secrets, give small keys, add the second lock, stay updated. None of it is clever. All of it works. Tomorrow we turn raw data into something you can actually read. See the public studio at office.temerarii.xyz.
on-screen: Lock it like we do, office.temerarii.xyz
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Lock it like we do, office.temerarii.xyz

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 a normal business can actually do: four simple locks Most breaks are simple, and so are the locks. This video covers a handful of moves that block most of the trouble, without buying scary software or hiring a whole team. The four moves: - Get your secrets out of the code. Stop putting passwords and keys inside your code. Move them into a secrets file the code reads at run time, and never commit that file. Ask your agent to scan the project for keys hiding in plain sight. A key in your code is a key on the sidewalk. - Give the least key that works. When a tool or a person needs a key, give the smallest one that does the job. Read-only when they only need to read. One folder, not the whole drive. If that key leaks, the damage is a room, not the building. - Turn on the second lock. Two-step login everywhere it is offered, a password plus a code from your phone. It is dull, it takes ten seconds, and it stops the most common attack cold, where someone has your password but not your phone. - Patch on a schedule, not a whim. Old software is the open window. Put your updates on a clock and let the agent list what is out of date. You do not have to be fast and fancy, you have to be current and boring. The honest proof: we run a security pass on our own studio, looking for keys in the code and doors left open, before we ever talk to a client about theirs. We will not sell a lock we have not turned on ourselves. Securing it is mostly habits. None of it is clever. All of it works. See the public studio at office.temerarii.xyz Keywords: small business cyber security, secrets management, least privilege, two factor authentication, software updates, security basics

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