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 thread-the-stack-W35-Tuekind threadweek W35date 2026-09-01campaign thread · Tuepillar strategic_relationsbeat Tueasset videoduration 35.9sground redscenes 6

Checklist the per-video bar — engine/sim

82.9/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-the-stack-W35-Tue good|bad)
⚠ 6 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SchematicCard
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 6 scenes · 35.9s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–5.0skinetic-buildicon·liquid-chrome♪ node_lock
The tool is HubSpot, the CRM everyone has, and its forms just collect dumb fields.
on-screen: HubSpot forms = dumb fields
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→HubSpot forms = dumb fields
2s2
matches intent
NumberedList
template
teach5.0–13.0skinetic-buildicon·white-knockout♪ node_lock
So on submit, a workflow sends the entry to an assistant that cleans the company name, finds the size, and scores the fit,
on-screen: LLM enrich on submit
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→LLM enrich on submitcurate items, nodes
3s3
matches intent
TerminalRun
template
build13.0–20.9stype-onicon·liquid-chrome♪ node_lock
Now sales opens a CRM where every record is clean, scored, and ranked, so they call the best fit first instead
on-screen: Sales calls only hot leads
expected on screen: red ground · a TerminalRun panel over a dimmed Signal Field · Nexus leads · code · type-on · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape tetraground redtreatment liquid-chromemotion type-onpower summoninstrument draw-on→Sales calls only hot leadscurate codeLines
4s4
matches intent
FlowSchematic
template
proof20.9–25.9sreceipts-counticon·white-knockout♪ node_lock
So wire one form to an enrichment prompt before it saves, then watch the records clean themselves.
on-screen: Enrich one form
expected on screen: red ground · a FlowSchematic panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Enrich one formcurate stages, statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
futurist25.9–30.9sspatial-parallaxicon·liquid-chrome♪ bed
The Stack
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→The Stack
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve30.9–35.9scoalescenceicon·white-knockout♪ bed_out
The Stack
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→The Stack

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)

tiktokThe Stack: HubSpot forms collect dumb fields. The fix: on submit, a workflow sends the entry to an assistant that cleans the company name, finds the size, and scores the fit. Sales calls the best fit first. (AI-assisted)
instagramThe Stack: HubSpot. Forms = dumb fields. On submit, enrich with an LLM. Clean the name. Find the size. Score the fit. Sales calls only hot leads. #crm #hubspot #salesops #leadgen #automation
linkedinThe Stack: HubSpot, the CRM almost everyone has. Out of the box, its forms just collect dumb fields. The move: on submit, a workflow sends the entry to an assistant that cleans the company name, finds the size, and scores the fit before it ever saves. Now sales opens a CRM where every record is clean, scored, and ranked, so they call the best fit first instead of guessing. The real limit: enrichment is only as good as your scoring rules, so write those down first. Wire one form to an enrichment prompt before it saves.
xThe Stack: HubSpot forms collect dumb fields. On submit, send the entry to an LLM that cleans the name, finds the size, and scores the fit. Sales calls the best fit first. temerarii.xyz/build
facebookThe Stack: HubSpot is the CRM everyone has, but its forms just collect dumb fields. The fix: on submit, a workflow sends the entry to an assistant that cleans the company name, finds the size, and scores the fit. Then sales opens a clean, ranked list and calls the best fit first. Wire one form to an enrichment prompt before it saves.
threadsThe Stack: HubSpot, the CRM everyone has. Its forms collect dumb fields. So on submit, send the entry to an assistant that cleans the company name, finds the size, and scores the fit. Now sales calls the best fit first instead of guessing. Wire one form to an enrichment prompt before it saves.
pinterestHow to enrich HubSpot form submissions with AI. The method: on submit, a workflow sends the entry to an LLM that cleans the company name, finds the company size, and scores the fit before it saves. Sales then opens a clean, scored, ranked CRM and calls the best-fit leads first. CRM lead enrichment and scoring workflow for sales teams.
blueskyThe Stack: HubSpot forms collect dumb fields. On submit, send the entry to an LLM that cleans the name, finds the size, and scores the fit. Sales calls the best fit first.
youtubeTitle: The Stack, Enrich HubSpot Forms With an LLM on Submit HubSpot is the CRM almost everyone has, but its forms just collect dumb fields. The move: on submit, a workflow sends the entry to an assistant that cleans the company name, finds the size, and scores the fit before it saves. Now sales opens a CRM where every record is clean, scored, and ranked, so they call the best fit first instead of guessing. The real limit: enrichment is only as good as your scoring rules. Wire one form to an enrichment prompt before it saves.

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