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 social-W36-Mon-2kind threadweek W36date 2026-09-07campaign thread · Monpillar it_devbeat Monasset videoduration 46.7sground redscenes 9

Checklist the per-video bar — engine/sim

86.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W36-Mon-2 good|bad)
⚠ 3 flag(s) — not yet ship-ready: too_complexdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
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 9 scenes · 46.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–5.2sspatial-parallaxicon·liquid-chrome♪ bed_in
Cyber security used to be a yearly audit and a binder nobody opened.
on-screen: Security was a yearly checkbox
expected on screen: red 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 redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Security was a yearly checkbox
2s2
matches intent
shared field
signature-3d
hook5.2–10.2skinetic-buildicon·white-knockout♪ node_lock
Attackers never waited for the audit; they probed the gaps all year.
on-screen: Attackers don't wait for the audit
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Attackers don't wait for the audit
3s3
matches intent
NumberedList
template
teach10.2–15.2skinetic-buildicon·liquid-chrome♪ node_lock
Start where it actually matters: a password manager and two-factor on everything.
on-screen: Start with the boring basics
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Start with the boring basicscurate items, nodes
4s4
matches intent
RankList
template
proof15.2–20.2sreceipts-counticon·white-knockout♪ node_lock
Most breaches are just stolen logins, not some clever movie hack.
on-screen: Most breaches are stolen logins
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Most breaches are stolen loginscurate rows, statsLabels
5s5
matches intent
LogStream
template
diff20.2–25.4scrossfade-8ficon·liquid-chrome♪ node_lock
A static checklist goes stale the day after you tick the last box.
on-screen: A checklist alone goes stale
expected on screen: red ground · a LogStream panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape boxground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→A checklist alone goes stalecurate codeLines, rows
6s6
matches intent
ChecklistCard
template
teach25.4–31.299999999999997skinetic-buildicon·white-knockout♪ node_lock
So point a model at your access logs to flag the weird login each morning.
on-screen: Have AI read your logs daily
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Have AI read your logs dailycurate items, nodes
7s7
matches intent
StatScoreboard
template
proof31.3–36.5sreceipts-counticon·liquid-chrome♪ node_lock
An odd login from a strange place surfaces in minutes, not next quarter.
on-screen: Odd logins surface fast
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Odd logins surface fastcurate pillar, stats, statsLabels
8s8
matches intent
WireframeMock
template
step36.5–41.5skinetic-buildicon·white-knockout♪ node_lock
Try it: turn on two-factor everywhere, then summarize your logs daily.
on-screen: Turn on 2FA, then watch logs
expected on screen: red ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual pipelineshape boxground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Turn on 2FA, then watch logscurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve41.5–46.7scoalescenceicon·liquid-chrome♪ bed_out
Stay boring on the basics, and the attacker moves on to easier prey.
on-screen: Stay boring, stay un-breached
expected on screen: red 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 redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Stay boring, stay un-breached

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 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

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

tiktokMost breaches are not movie hacks, they are stolen logins. Here is the move: password manager plus two-factor on everything, then point a model at your access logs to flag the weird login each morning. Stay boring on the basics and attackers move on. #cybersecurity #infosec #aitools
instagramMost breaches are stolen logins. Use a password manager. Two-factor on everything. Let AI read your logs daily. Stay boring, stay un-breached. #cybersecurity #infosec #datasecurity #aitools #smallbusiness
linkedinSecurity used to be a yearly audit and a binder nobody opened, but attackers probe all year. The fundamentals still win: a password manager, two-factor everywhere, and a model summarizing your access logs daily to surface the odd login. The takeaway: most breaches are stolen logins, not clever hacks. Stay boring on the basics.
xCyber security move: most breaches are stolen logins. Password manager, 2FA on everything, then have AI flag the weird login in your logs daily. Stay boring. temerarii.com
facebookSecurity used to be a yearly audit and a binder nobody opened. The basics still win: password manager, two-factor everywhere, and a model reading your access logs daily to flag the odd login. Most breaches are stolen logins. See the method at temerarii.com.
threadsMost breaches are stolen logins, not movie hacks. Password manager, 2FA on everything, then let AI flag the weird login in your logs daily. Stay boring on the basics.
pinterestCyber security basics for small teams: how to stop the most common breach. Use a password manager, enable two-factor everywhere, and have AI summarize access logs daily to flag odd logins. Evergreen guide to infosec, account security, and log monitoring.
blueskyCyber security move: most breaches are stolen logins. Password manager, 2FA on everything, then let AI flag the weird login in your logs daily. temerarii.com
youtubeCyber Security Basics: Stop The Breach That Actually Happens Security used to be a yearly audit and a binder nobody opened, but attackers probe the gaps all year. The real method: a password manager, two-factor on everything, then point a model at your access logs to flag the weird login each morning. Most breaches are just stolen logins, not clever movie hacks. Turn on two-factor and start summarizing your logs daily. More at temerarii.com.

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