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-W37-Tue-1kind threadweek W37date 2026-09-15campaign thread · Tuepillar strategic_relationsbeat Tueasset videoduration 58.6sground 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-W37-Tue-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 · 58.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–5.5sspatial-parallaxicon·ember-fill♪ bed_in
Websites used to be one fixed layout that everyone saw the exact same way.
on-screen: Websites were one fixed layout
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Websites were one fixed layout
2s2
matches intent
shared field
signature-3d		hook5.5–11.8skinetic-buildicon·wireframe♪ node_lock
The blunt truth: one page can't fit a first-time visitor and a returning buyer at once.
on-screen: The same page rarely fits everyone
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→The same page rarely fits everyone
3s3
matches intent
NumberedList
template		teach11.8–18.4skinetic-buildicon·wireframe♪ node_lock
Here is the method: design a system of blocks with clear rules, not a single hand-built page.
on-screen: Design the system, not the page
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Design the system, not the pagecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof18.4–25.4sreceipts-counticon·wireframe♪ node_lock
When each block knows its rules, the page can rearrange itself for the person in front of it.
on-screen: Rules let the page rearrange itself
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape tetraground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Rules let the page rearrange itselfcurate colA, colB, rows, statsLabels
5s5
matches intent
JsonDiff
template		diff25.4–33.1scrossfade-8ficon·wireframe♪ node_lock
What is now possible: a page that shows the new visitor the promise and the returning one the next step.
on-screen: Future: pages that adapt per visitor
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual codeshape tetraground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Future: pages that adapt per visitorcurate codeLines, fileName, lines
6s6
matches intent
ChecklistCard
template		teach33.1–40.1skinetic-buildicon·wireframe♪ node_lock
We let AI assemble the layout from your blocks, while a human keeps the taste and the limits.
on-screen: Let AI assemble from your blocks
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let AI assemble from your blockscurate items, nodes
7s7
matches intent
KpiGrid
template		proof40.1–46.4sreceipts-counticon·wireframe♪ node_lock
The right block in front of the right person beats a pretty page nobody acts on.
on-screen: Right block, right person, faster
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Right block, right person, fastercurate kpis, statsLabels
8s8
matches intent
StepFlow
template		step46.4–52.699999999999996skinetic-buildicon·wireframe♪ node_lock
Your move: define your blocks, write their rules, name visitor intent, then let the page adapt.
on-screen: Steps: blocks, rules, intent, assemble
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual pipelineshape tetraground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: blocks, rules, intent, assemblecurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve52.7–58.6scoalescenceicon·ember-fill♪ bed_out
That is how The Big T-M builds sites that meet people where they actually are.
on-screen: Sites that meet people where they are
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Sites that meet people where they are

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)

tiktokFuture of web design: stop building ONE fixed page. Design a system of blocks with rules, so the page rearranges itself, new visitor sees the promise, returning buyer sees the next step. AI assembles, humans keep taste. AI-assisted. #webdesign #webdev #UX #design #tech
instagramDesign the system. Not the page. Let it adapt to the visitor. #webdesign #webdev #ux #uidesign #design
linkedinWeb design is moving from fixed pages to adaptive systems. One layout can't serve a first-time visitor and a returning buyer equally. The method: design a system of blocks with clear rules so the page can rearrange itself by visitor intent, showing newcomers the promise and returning users the next step. AI can assemble the layout from your blocks while a human holds the taste and the limits. The right block for the right person beats a pretty page nobody acts on.
xFuture of web design: don't build one fixed page. Build a block system with rules, let the page adapt to visitor intent. AI assembles, humans keep taste. temerarii.com
facebookWebsites used to be one fixed layout for everyone. The future is a system of blocks with rules, so the page adapts, new visitors see the promise, returning ones see the next step. Design the system, not the page. More at temerarii.com.
threadsWeb design is going adaptive. One fixed page can't fit a newcomer and a returning buyer at once. Design a block system with rules so the page rearranges itself by visitor intent. AI assembles from your blocks, a human keeps the taste.
pinterestWeb design future: build adaptive block systems with rules instead of one fixed page, so layouts adjust to visitor intent. Web design tips, UX design, responsive design systems.
blueskyFuture of web design: build a block system with rules, let the page adapt to visitor intent. AI assembles, humans keep taste. temerarii.com
youtubeAdaptive Web Design: Build the System, Not the Page One fixed layout can't serve everyone. We cover designing a system of blocks with clear rules so pages adapt to visitor intent, showing newcomers the promise and returning users the next step, with AI assembling and humans holding taste. AI-assisted. More at temerarii.com. #WebDesign #UX #WebDev

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view