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-Satkind longformweek W27date 2026-07-11campaign longform-youtubepillar it_devbeat asset videoduration 164.7sground blackscenes 8

Checklist the per-video bar — engine/sim

96.7/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W27-Sat good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_genericgeneric_scene · 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 8 scenes · 164.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–21.6sspatial-parallaxicon·white-knockout♪ bed_in
The hub opens soon, and a door only works if everyone can use it. Today is only about accessibility, which means building so people with different bodies and senses can use your site too. It is not charity and it is not extra. Today you learn the plain moves, the ones we baked into the hub from the start.
on-screen: Accessibility, built in not bolted on
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Accessibility, built in not bolted on
2s2
matches intent
NumberedList
template
teach21.6–43.6skinetic-buildicon·wireframe♪ node_lock
First move. Every image gets a short text description, called alt text, that says what the image shows. A person using a screen reader hears that text instead of seeing the picture. It takes one line. The move is to never ship an image with the description left blank. Empty alt text is a locked door for a real person.
on-screen: Describe every image
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Describe every imagecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach43.6–63.8skinetic-buildicon·wireframe♪ node_lock
Second move. Check that your text stands out from its background enough to read. There are free contrast checkers online. Paste your two colors in, it tells you pass or fail. Light gray on white looks classy and shuts out anyone with tired eyes or a bright screen outdoors. Readable beats pretty when they fight.
on-screen: Make sure text can be read
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Make sure text can be readcurate items, nodes
4s4
matches intent
CheatSheet
template
teach63.8–85.8skinetic-buildicon·wireframe♪ node_lock
Third move. Try using your whole site with only the keyboard. Tab to move, enter to click. Many people cannot use a mouse. If you can fill a form and press every button with the keyboard alone, you are most of the way there. If the tab key gets stuck in a corner, you just found a wall to remove.
on-screen: Everything works by keyboard
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Everything works by keyboardcurate nodes, points, uses
5s5
first render · fix pending
StepFlow
templategeneric_scene
teach85.8–106.69999999999999skinetic-buildicon·wireframe♪ node_lock
Fourth move. Every input and button gets a clear label that a screen reader can announce. Not a gray placeholder that vanishes when you type. An actual label that says what this box is for. A button that says send, not just an arrow icon with no name. Labels turn a guessing game into a usable form.
on-screen: Label your forms and buttons
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Label your forms and buttonscurate nodes, steps
6s6
matches intent
NodeGraphCard
template
teach106.7–125.80000000000001skinetic-buildicon·wireframe♪ node_lock
The proof is honest. The hub gets run through accessibility checks before it ships. Images carry descriptions, colors pass contrast, the keyboard reaches everything, forms have real labels. We do not claim a perfect score, because the work is never finished. We claim we test for it on purpose instead of hoping.
on-screen: The hub passes its own checks
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→The hub passes its own checkscurate hub, nodes
7s7
matches intent
RankList
template
proof125.8–143.1sreceipts-counticon·wireframe♪ node_lock
So that is accessibility, built in from the start. Alt text on images, readable contrast, full keyboard use, real labels. Your step is one free check. Run your homepage through an accessibility checker today and fix the first thing it flags. See the hub's version at office.temerarii.xyz.
on-screen: Run one check today
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Run one check todaycurate rows, statsLabels
8s8
matches intent
shared field
signature-3d
resolve143.1–164.7scoalescenceicon·white-knockout♪ bed_out
Last thought. A site that only works for the average visitor is a site that is quietly broken for a lot of people. Accessibility is just refusing to leave anyone at the door. Do it from the first line and it costs almost nothing. Bolt it on later and it costs you twice. The hub chose the first way.
on-screen: Built for everyone, or it is broken
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Built for everyone, or it is broken

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)

youtubeWeb Accessibility Basics: Alt Text, Contrast, Keyboard, and Form Labels A door only works if everyone can use it. This walkthrough covers the plain moves that make a website usable for people who browse with a screen reader, a keyboard, or tired eyes on a bright screen. No charity framing, no extra budget, just building it right from the first line. What you learn: - Alt text: every image gets a short written description so a screen reader can say what the picture shows. Never ship a blank one. - Color contrast: run your text and background colors through a free contrast checker so light gray on white does not lock people out. Readable beats pretty when they fight. - Keyboard use: try your whole site with only the keyboard, tab to move and enter to click, so people who cannot use a mouse get through. If tab gets stuck in a corner, you found a wall to remove. - Real labels: every input and button gets a clear label a screen reader can announce, not a gray placeholder that vanishes when you type. The method is simple: run your homepage through an accessibility checker today and fix the first thing it flags. We test the hub for these on purpose before it ships. We do not claim a perfect score, because the work is never finished. A site that only works for the average visitor is quietly broken for a lot of people. See the live hub at office.temerarii.xyz. Keywords: web accessibility, alt text, color contrast, keyboard navigation, screen reader, form labels, WCAG basics.

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