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-W48-Satkind longformweek W48date 2026-12-05campaign longform-youtubepillar performancebeat asset videoduration 194.3sground blackscenes 8

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W48-Sat 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 8 scenes · 194.3s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–25.2sspatial-parallaxicon·wireframe♪ bed_in
The last piece of the operating layer is the one most people skip: accessibility. That means building so a person who cannot see well, or cannot use a mouse, can still use what you made. It is not charity and it is not red tape. It is reaching more customers. Today you learn how to let an agent find the barriers in your site that you walked right past.
on-screen: Built for everyone, on purpose
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Built for everyone, on purpose
2s2
matches intent
NumberedList
template
teach25.2–50.4skinetic-buildicon·wireframe♪ node_lock
Step one. Use an automated accessibility checker. The agent can run a tool like axe against your live page through a headless browser and get back a plain list of problems: this image has no description, this text is too faint to read, this form field has no label. You stop guessing what might be wrong. The tool hands you the actual list, ranked by how much it hurts.
on-screen: Run a real audit, not a guess
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Run a real audit, not a guesscurate items, nodes
3s3
matches intent
ChecklistCard
template
teach50.4–78.1skinetic-buildicon·wireframe♪ node_lock
Step two. Every image needs alt text, a short written description a screen reader speaks aloud for someone who cannot see it. Writing it for a hundred images is a dull afternoon. Hand the images to the agent and let it write the descriptions, then you read and fix the few it got wrong. The big T-M does this on every asset, because an image with no words is just a blank to a blind visitor.
on-screen: Let the model write alt text
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the model write alt textcurate items, nodes
4s4
matches intent
FlowSchematic
template
teach78.1–103.6skinetic-buildicon·wireframe♪ node_lock
Step three. Faint gray text on a white page looks clean to a designer and is invisible to a lot of real eyes. There is a measured rule for this called contrast ratio. Tell the agent to check every text color against its background and flag any pair that fails the rule. It does the math on every combination at once, which no one is going to do by hand.
on-screen: Check the colors can be read
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Check the colors can be readcurate nodes, stages
5s5
matches intent
TerminalRun
template
teach103.6–127.0skinetic-buildicon·wireframe♪ node_lock
Step four. Many people never touch a mouse. Have the agent drive your site using only the keyboard, tabbing through every button and link, and report anything it cannot reach or any place the focus disappears. If the agent gets stuck, a real person would too. This catches the trap doors, the menus and pop-ups that quietly lock out anyone who navigates by key.
on-screen: Drive it with the keyboard only
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Drive it with the keyboard onlycurate nodes
6s6
matches intent
NodeGraphCard
template
teach127.0–151.1skinetic-buildicon·wireframe♪ node_lock
Step five. Tell the agent to read your page in the order a screen reader would, top to bottom, by the underlying structure. If the order is a jumble, the page makes no sense out loud even when it looks fine on screen. Fixing the structure so it reads in a sensible order is the move that turns a page from technically allowed into actually usable.
on-screen: Read it the way a screen reader
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Read it the way a screen reader doescurate hub, nodes
7s7
matches intent
RankList
template
proof151.1–170.9sreceipts-counticon·wireframe♪ node_lock
Our honest proof: we run these same checks on our own pages, the audit, the alt text, the contrast math, the keyboard pass, the read-aloud order. No claim about how many people it reached, just the plain practice of testing the way real visitors actually arrive, including the ones most sites quietly leave out.
on-screen: We test our own pages this way
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We test our own pages this waycurate rows, statsLabels
8s8
matches intent
shared field
signature-3d
resolve170.9–194.3scoalescenceicon·wireframe♪ bed_out
So accessibility is a set of checks, not a debate. Run an audit. Let the model write your alt text. Check the contrast. Drive the site by keyboard. Read it aloud in order. Pick one page and run all five today. The fewer people you lock out, the more you get to serve. See how we check ours at office dot temerarii dot xyz.
on-screen: See the checks at office.temerarii.xyz
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→See the checks at 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)

youtubeAccessibility Is Reaching More Customers: Five Checks an Agent Can Run for You The last piece of the operating layer is the one most people skip: accessibility. That means building so a person who cannot see well, or cannot use a mouse, can still use what you made. It is not charity and it is not red tape, it is reaching more customers. In this video an agent finds the barriers you walked right past. The checks: - Run a real audit, not a guess. The agent can run a tool like axe against your live page through a headless browser and get back a plain list of problems, ranked by how much they hurt: this image has no description, this text is too faint, this field has no label. - Let the model write alt text. Every image needs alt text, a short description a screen reader speaks aloud. Hand the images to the agent, let it write the descriptions, then read and fix the few it got wrong. An image with no words is a blank to a blind visitor. - Check the colors can be read. Faint gray text looks clean and is invisible to a lot of real eyes. There is a measured rule called contrast ratio. The agent checks every text color against its background and flags any pair that fails. - Drive it with the keyboard only. Many people never touch a mouse. Have the agent tab through every button and link and report anything it cannot reach. This catches the menus and pop-ups that lock people out. - Read it the way a screen reader would. Tell the agent to read your page top to bottom by the underlying structure. If the order is a jumble, the page makes no sense out loud even when it looks fine. The honest proof: we run these same checks on our own pages, the audit, the alt text, the contrast math, the keyboard pass, the read-aloud order. No claim about how many people it reached, just testing the way real visitors actually arrive. The takeaway: pick one page and run all five today. The fewer people you lock out, the more you get to serve. See how we check ours at office.temerarii.xyz. Keywords: web accessibility, axe, alt text, contrast ratio, keyboard navigation, screen reader.

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