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-W27-Sun-4kind threadweek W27date 2026-07-05campaign thread · Sunpillar it_devbeat Sunasset videoduration 63.1sground blackscenes 9

Checklist the per-video bar — engine/sim

98.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W27-Sun-4 good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · 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 · 63.1s · 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.9sspatial-parallaxicon·white-knockout♪ bed_in
For years, accessibility was the thing teams bolted on the week before launch, then forgot.
on-screen: Accessibility was an afterthought
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 was an afterthought
2s2
matches intent
shared field
signature-3d
hook5.9–12.9skinetic-buildicon·wireframe♪ node_lock
Here is the blunt part. Skipping it is a lawsuit waiting, and a whole market you locked out.
on-screen: It's a lawsuit and a market
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→It's a lawsuit and a market
3s3
matches intent
NumberedList
template
teach12.9–19.5skinetic-buildicon·wireframe♪ node_lock
Drop the axe-core checker into your build, and it fails the deploy when contrast or labels break.
on-screen: Run axe in your pipeline
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→Run axe in your pipelinecurate items, nodes
4s4
matches intent
ComparisonTable
template
proof19.5–26.8sreceipts-counticon·wireframe♪ node_lock
Now every push gets scanned, so a missing alt tag is caught by a robot, not an angry customer.
on-screen: Catch it before users do
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Catch it before users docurate colA, colB, rows, statsLabels
5s5
matches intent
LogStream
template
diff26.8–34.1scrossfade-8ficon·wireframe♪ node_lock
But a scanner only catches about half. The rest needs a human tabbing through with the screen reader on.
on-screen: Checkers find half the bugs
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Checkers find half the bugscurate codeLines, rows
6s6
matches intent
ChecklistCard
template
teach34.1–41.800000000000004skinetic-buildicon·wireframe♪ node_lock
Feed each image to a vision model and have it draft real alt text, then a person approves the list.
on-screen: Let AI write the alt text
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→Let AI write the alt textcurate items, nodes
7s7
matches intent
KpiGrid
template
proof41.8–48.4sreceipts-counticon·wireframe♪ node_lock
Same site, suddenly usable by people on screen readers, on phones in the sun, on bad connections.
on-screen: Same site, twice the reach
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Same site, twice the reachcurate kpis, statsLabels
8s8
matches intent
SchematicCard
template
step48.4–56.5skinetic-buildicon·wireframe♪ node_lock
So the move is scan in CI, gate the deploy, draft alt text with AI, then verify with a real reader.
on-screen: Step: scan, gate, draft, verify
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual pipelineshape boxground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Step: scan, gate, draft, verifycurate nodes, stages, steps
9s9
matches intent
shared field
signature-3d
resolve56.5–63.1scoalescenceicon·white-knockout♪ bed_out
Accessible by default, not by apology. The Big T-M bakes it into the pipe from day one.
on-screen: Built in, not bolted on
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 in, not bolted on

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)

tiktokAccessibility, baked in not bolted on (AI-assisted). Drop the axe-core checker into your build so it fails the deploy when contrast or labels break. Feed images to a vision model to draft alt text, then have a human approve it. Scanners catch ~half, so a person still tabs through with a screen reader. Same site, twice the reach.
instagramStop bolting accessibility on at the end. axe-core in your build pipeline. AI drafts the alt text. A human verifies with a screen reader. Same site, twice the reach. #accessibility #a11y #webdev #inclusivedesign #wcag
linkedinAccessibility is still treated as a pre-launch chore. That's both a legal risk and a market you've locked out. A pipeline that fixes it for good: 1. Run the axe-core checker inside CI so a broken contrast ratio or missing label fails the deploy, not the user. 2. Use a vision model to draft alt text for every image, then have a person approve the list. Drafting is the slow part; approval is fast. 3. Remember automated scanners catch roughly half. The rest needs a human tabbing through with a screen reader on. The payoff: the same site becomes usable by people on screen readers, on phones in bright sun, on poor connections. Accessible by default, not by apology. AI-assisted and disclosed.
xDrop axe-core into CI so a missing label fails the deploy, not the user. Let a vision model draft alt text, then a human approves it. Scanners catch ~half, so still test with a screen reader. temerarii.com
facebookAccessibility shouldn't be the thing you bolt on the week before launch. Drop the axe-core checker into your build so broken contrast or missing labels fail the deploy. Let a vision model draft alt text for every image, then have a person approve it. Automated scans catch about half, so a human still tabs through with a screen reader. Same site, far more reach. Learn more at temerarii.com.
threadsAccessibility shouldn't be a pre-launch chore. Put axe-core in CI so a missing label fails the deploy, not the user. Let a vision model draft alt text, then a human approves it. Scanners catch ~half, so still test with a screen reader.
pinterestWeb accessibility built into your pipeline: run axe-core in CI to fail broken deploys, use AI to draft alt text, and verify with a real screen reader. An evergreen WCAG workflow for inclusive, higher-reach websites.
blueskyPut axe-core in CI so a missing label fails the deploy, not the user. Let a vision model draft alt text, then a human approves it. Scanners catch ~half, so still test with a screen reader. temerarii.com
youtubeWeb Accessibility Built In, Not Bolted On: axe-core, AI Alt Text & Screen Readers Accessibility is still treated as a pre-launch chore, which is both a legal risk and a market you've locked out. This walks through a durable pipeline: run the axe-core checker inside CI so broken contrast or missing labels fail the deploy instead of the user, use a vision model to draft alt text for every image with human approval, and remember automated scanners only catch about half, so a person still tabs through with a screen reader. The result is the same site, usable by far more people. AI-assisted and disclosed. More at temerarii.com.

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