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-st-systemskind topicweek date campaign staff-training-pillarpillar staff_trainingbeat asset videoduration 61.4sground blackscenes 9

Checklist the per-video bar — engine/sim

97.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-st-systems 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 9 scenes · 61.4s · 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.8sspatial-parallaxicon·wireframe♪ —
Most teams keep the how-to in one person's head. When they leave, the system leaves with them. We write the system down, with AI.
on-screen: Train the team once
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
SchematicCard
template
legacy7.8–14.0scrossfade-8ficon·wireframe♪ —
The old way was shadowing a senior for a month and hoping you caught the important parts before they got busy.
on-screen: Old way: shadow and pray
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Magister leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardshape knotground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate nodes
3s3
matches intent
NumberedList
template
teach14.0–20.6skinetic-buildicon·wireframe♪ —
We start by recording your best person actually doing the task, screen and voice, one real run-through.
on-screen: Step 1: record the expert
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template
teach20.6–27.3skinetic-buildicon·wireframe♪ —
Then we diagram it: every decision point and branch laid out, so the process is visible instead of assumed.
on-screen: Steps mapped as a flow
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
JsonDiff
template
teach27.3–34.2skinetic-buildicon·wireframe♪ —
We run the recording through Whisper and hand the transcript to Claude, which drafts a step-by-step SOP in plain language.
on-screen: Transcript -> draft SOP
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate fileName, lines, nodes
6s6
matches intent
BuildLog
template
teach34.2–42.7skinetic-buildicon·wireframe♪ —
It flows from there: the expert corrects the draft, and the approved version becomes onboarding docs, a checklist, and quiz prompts.
on-screen: SOP -> review -> training set
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate lines, nodes
7s7
matches intent
StatScoreboard
template
proof42.7–49.2sreceipts-counticon·wireframe♪ —
New hires reach competence faster because the knowledge is written, searchable, and consistent every time.
on-screen: Ramp time, cut down
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate pillar, stats, statsLabels
8s8
matches intent
shared field
signature-3d
futurist49.2–55.1sspatial-parallaxicon·wireframe♪ —
Soon every process change just gets re-recorded once, and the whole training set updates with it.
on-screen: A system that updates itself
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape knotground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
9s9
matches intent
shared field
signature-3d
resolve55.1–61.4scoalescenceicon·wireframe♪ swell
Worried about what walks out the door? We'll capture it into a system. Start at temerarii.xyz.
on-screen: Capture your team's knowledge
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment wireframemotion 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)

tiktokMost teams keep the how-to in one person's head. When they leave, the system leaves with them. (AI-assisted) Write it down, with AI. Record your best person actually doing the task, screen and voice, one real run-through. Diagram every decision point and branch so the process is visible. Run the recording through Whisper, hand the transcript to Claude, and it drafts a step-by-step SOP in plain language. The expert corrects the draft, and the approved version becomes onboarding docs, a checklist, and quiz prompts.
instagramThe how-to lives in one person's head. They leave, it leaves with them. Fix it, with AI: Record your best person doing the task Diagram every decision and branch Whisper the audio, Claude drafts the SOP Expert corrects, it becomes onboarding Knowledge that stays. #SOP #Onboarding #Knowledge #AItools #Temerarii
linkedinMost teams keep the how-to in one person's head. When they leave, the system leaves with them. Here is how to write it down, with AI. The old way was shadowing a senior for a month and hoping you caught the important parts before they got busy. The method: 1. Record your best person actually doing the task, screen and voice, one real run-through. 2. Diagram every decision point and branch, so the process is visible instead of assumed. 3. Run the recording through Whisper and hand the transcript to Claude, which drafts a step-by-step SOP in plain language. 4. The expert corrects the draft, and the approved version becomes onboarding docs, a checklist, and quiz prompts. New hires reach competence faster because the knowledge is written, searchable, and consistent every time. Worried about what walks out the door? We will capture it into a system. Start at temerarii.xyz
xThe how-to lives in one head. They leave, it leaves. Write it down with AI: Record your best person doing the task Diagram every branch Whisper the audio, Claude drafts the SOP Expert corrects, it becomes onboarding temerarii.xyz
facebookMost teams keep the how-to in one person's head. When they leave, the system leaves with them. Here is how to write it down, with AI. Record your best person actually doing the task, screen and voice. Diagram every decision and branch so the process is visible. Run the recording through Whisper, hand the transcript to Claude, and it drafts a step-by-step SOP in plain language. The expert corrects it, and the approved version becomes onboarding docs, a checklist, and quizzes. Worried about what walks out the door? temerarii.xyz
threadsThe how-to lives in one person's head. They leave, it leaves with them. Write it down, with AI. Record your best person doing the task. Diagram every decision and branch. Whisper the audio, Claude drafts the SOP. The expert corrects it, and it becomes onboarding docs and a checklist. Knowledge that stays.
pinterestHow to capture a team's tribal knowledge before it walks out the door: record your best person doing the task, diagram every branch, transcribe with Whisper, draft the SOP with Claude, then have the expert review. A plain method to turn one expert into onboarding docs and checklists.
blueskyThe how-to lives in one head. They leave, it leaves with them. Write it down with AI. Record your best person doing the task. Diagram every branch. Whisper the audio, Claude drafts the SOP. Expert corrects it into onboarding docs. Knowledge that stays. temerarii.xyz
youtubeTurn One Expert Into an SOP: Capture Team Knowledge Before It Walks Out the Door Most teams keep the how-to in one person's head. When they leave, the system leaves with them. This walks the full method and gives it away. The old way was shadowing a senior for a month and hoping you caught the important parts before they got busy. The method: 1. Record your best person actually doing the task, screen and voice, one real run-through. 2. Diagram every decision point and branch, so the process is visible instead of assumed. 3. Run the recording through Whisper and hand the transcript to Claude, which drafts a step-by-step SOP in plain language. 4. The expert corrects the draft, and the approved version becomes onboarding docs, a checklist, and quiz prompts. New hires reach competence faster because the knowledge is written, searchable, and consistent every time. And every process change just gets re-recorded once. Worried about what walks out the door? We will capture it into a system. Start at temerarii.xyz

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