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-W38-Thu-1kind threadweek W38date 2026-09-24campaign thread · Thupillar staff_trainingbeat Thuasset videoduration 60.7sground blackscenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W38-Thu-1 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · 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 · 60.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–7.0sspatial-parallaxicon·white-knockout♪ bed_in
Old way: virtual reality meant an expensive headset and a demo nobody could try without flying to you.
on-screen: VR was a headset showroom
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→VR was a headset showroom
2s2
matches intent
shared field
signature-3d
hook7.0–13.3skinetic-buildicon·ember-fill♪ node_lock
Here is the wall: if the experience needs hardware most people lack, the audience stays tiny.
on-screen: The headset gated it
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→The headset gated it
3s3
matches intent
NumberedList
template
teach13.3–20.6skinetic-buildicon·wireframe♪ node_lock
New way: build the walkthrough in the browser, so a normal phone or laptop can step inside the space.
on-screen: Build VR for the browser
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→Build VR for the browsercurate items, nodes
4s4
matches intent
ComparisonTable
template
proof20.6–27.6sreceipts-counticon·white-knockout♪ node_lock
Now a client tours a room or a venue from a link, no headset, no flight, no showroom.
on-screen: Anyone can step inside
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Anyone can step insidecurate colA, colB, rows, statsLabels
5s5
matches intent
LogStream
template
diff27.6–34.2scrossfade-8ficon·liquid-chrome♪ node_lock
Immersion is not the goal. Letting someone understand a space they cannot yet visit is the goal.
on-screen: Immersion vs the point
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape knotground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Immersion vs the pointcurate codeLines, rows
6s6
matches intent
ChecklistCard
template
teach34.2–41.2skinetic-buildicon·ember-fill♪ node_lock
Teach the build to add clear hotspots, so a visitor knows where to look instead of wandering lost.
on-screen: Mark the hotspots clearly
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Mark the hotspots clearlycurate items, nodes
7s7
matches intent
KpiGrid
template
proof41.2–47.5sreceipts-counticon·wireframe♪ node_lock
A guided path teaches more than total freedom, because a lost visitor learns nothing and leaves.
on-screen: Guidance beats freedom
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Guidance beats freedomcurate kpis, statsLabels
8s8
matches intent
NodeGraphCard
template
step47.5–53.4skinetic-buildicon·white-knockout♪ node_lock
Your step: take one space and build a simple browser walkthrough with three labeled hotspots.
on-screen: Ship one browser walkthrough
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape knotground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Ship one browser walkthroughcurate hub, nodes, stages, steps
9s9
matches intent
shared field
signature-3d
resolve53.4–60.699999999999996scoalescenceicon·white-knockout♪ bed_out
Now the space comes to them, no gear. The Big T-M builds VR that opens in a browser tab.
on-screen: VR without the gear
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→VR without the gear

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)

tiktokVR does not need a headset. Build the walkthrough in the browser so anyone tours the space from a link. (AI-assisted) #vr #virtualreality #webvr
instagramNo headset. No flight. A browser link steps you inside the space. Clear hotspots guide the way. #vr #virtualreality #webvr #immersive #tech
linkedinVirtual reality stayed niche for a hardware reason: if the experience needs a headset most people lack, the audience stays tiny. Browser-based VR changes the reach. Build the walkthrough so a normal phone or laptop can step inside, and a client tours a room or venue from a link, no headset required. The point is not immersion for its own sake; it is helping someone understand a space they cannot yet visit. Add clear hotspots so visitors know where to look. Guidance teaches more than total freedom. Build one browser walkthrough this week.
xVR does not need a headset. Build the walkthrough in the browser so anyone tours the space from a link. Guide with clear hotspots. Method:
facebookVirtual reality stayed niche because it needed a headset most people do not own. Build the walkthrough in the browser instead, so anyone tours the space from a link. Comment to see a sample walkthrough.
threadsVR stayed niche because it needed a headset. Build the walkthrough in the browser so a normal phone or laptop can step inside the space from a link. And add clear hotspots, because a lost visitor learns nothing. Guidance teaches more than total freedom.
pinterestWeb VR guide: how to build a virtual walkthrough that opens in a browser, no headset, so clients tour a space from a link. Use clear hotspots to guide visitors. Virtual reality, web VR, immersive experiences, real estate tech.
blueskyVR does not need a headset. Build the walkthrough in the browser so anyone tours the space from a link, guided by clear hotspots. Method:
youtubeWeb VR: Let Anyone Tour a Space From a Link, No Headset VR stayed niche because it needed hardware most people lack. This covers building a walkthrough that runs in the browser so a normal phone or laptop can step inside, and why clear hotspots that guide the visitor teach more than total freedom. Virtual reality, web VR, immersive design. AI-assisted production.

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