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-W34-Satkind longformweek W34date 2026-08-29campaign longform-youtubepillar strategic_relationsbeat asset videoduration 158.6sground redscenes 6

Checklist the per-video bar — engine/sim

98.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W34-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 6 scenes · 158.6s · 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.5sspatial-parallaxicon·liquid-chrome♪ bed_in
We close this week's AI playbook with virtual reality. VR means a world you step inside instead of look at, and the usual advice is to spend a fortune first. We are going to do the opposite. By the end of this you will know how to test a VR idea in a normal web browser, for free, before you ever buy a single headset or hire a single developer.
on-screen: Virtual reality, the cheap test
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Virtual reality, the cheap test
2s2
matches intent
NumberedList
template
teach25.5–52.5skinetic-buildicon·white-knockout♪ node_lock
First, find the place that is expensive, dangerous, or far. A factory floor for training. A building that is not built yet. A clinic you cannot crowd with students. VR only earns its cost when being there in person is hard or risky. If your customer could just walk in and look, you do not need VR. Name the place that is too costly to visit, because that is the only place worth rebuilding.
on-screen: Find a place too costly to visit
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Find a place too costly to visitcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach52.5–80.5skinetic-buildicon·liquid-chrome♪ node_lock
Second, build the rough version on the open web. A free framework called A-Frame lets you make a walk-around 3D scene with plain HTML tags, and it runs in any browser and on a cheap headset through WebXR. You are not committing to an app store or a big engine. You are sketching the world in the same kind of code as a web page, so you can throw it away cheaply if the idea is weak.
on-screen: Build it in the browser first
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Build it in the browser firstcurate items, nodes
4s4
matches intent
BlueprintGrid
template
teach80.5–106.8skinetic-buildicon·white-knockout♪ node_lock
Third, the AI tie-in. An empty 3D room is slow to fill by hand. Use a model to generate the scene description, the object layout, even the textures, then drop them into your A-Frame world. You describe the space in words, the model drafts it, and you spend your hours judging whether it feels right instead of placing every box by hand. That is the same give-it-the-words move from the whole playbook.
on-screen: Let AI fill the empty world
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let AI fill the empty worldcurate nodes, rows
5s5
matches intent
ListCard
template
proof106.8–132.3sreceipts-counticon·liquid-chrome♪ node_lock
Our honest proof closes the week: our own front-room experiences are built to run in a plain browser first, on a normal canvas, before we ever reach for heavier tools. We test the cheap version in public and only invest more when it earns it. Same rule for your VR idea: prove it on the open web, where it costs almost nothing to be wrong, before you spend real money.
on-screen: We test on the web before we
expected on screen: red ground · a ListCard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We test on the web before we commitcurate items, statsLabels
6s6
matches intent
shared field
signature-3d
resolve132.3–158.60000000000002scoalescenceicon·liquid-chrome♪ bed_out
So that wraps the practical AI playbook. Virtual reality, made cheap: pick the place too costly to visit, build the rough world in the browser with A-Frame and WebXR, and let a model fill the space so you can judge instead of build. The thread all week was the same: use the new tool on purpose, on yourself first, for almost nothing. See the whole machine running in the open at office.temerarii.xyz.
on-screen: See it at office.temerarii.xyz
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→See it 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)

youtubeTest a VR idea in a plain browser for free before you buy a single headset VR means a world you step inside instead of look at, and the usual advice is to spend a fortune first. This does the opposite: how to test a VR idea in a normal web browser, for free, before you buy a headset or hire a developer. What you learn: - Find the place that is expensive, dangerous, or far: a factory floor for training, a building not built yet, a clinic you cannot crowd. VR only earns its cost when being there in person is hard or risky. - Build the rough version on the open web. A free framework called A-Frame lets you make a walk-around 3D scene with plain HTML tags, running in any browser and on a cheap headset through WebXR. You can throw it away cheaply if the idea is weak. - Use a model to generate the scene description, the object layout, even the textures, then drop them into your A-Frame world. You describe the space in words and spend your hours judging whether it feels right instead of placing every box by hand. Our honest proof: our own front-room experiences are built to run in a plain browser first, on a normal canvas, before we reach for heavier tools. We test the cheap version in public and only invest more when it earns it. Same rule for your VR idea: prove it on the open web, where it costs almost nothing to be wrong. See the machine running at office.temerarii.xyz. Keywords: virtual reality, A-Frame, WebXR, browser VR, 3D prototyping, low-cost testing

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