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-W50-Tuekind threadweek W50date 2026-12-15campaign thread · Tuepillar socialbeat Tueasset videoduration 33.1sground redscenes 6

Checklist the per-video bar — engine/sim

79.1/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-the-stack-W50-Tue good|bad)
⚠ 7 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 · 33.1s · 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 Vercel. You can deploy a front-end in seconds, but its functions time out on long jobs.
on-screen: Vercel functions time out
expected on screen: red ground · torus hero in the shared Signal Field · Nuntius leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape torusground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Vercel functions time out
2s2
first render · fix pending
ChecklistCard
templatedead_air		teach5.0–10.0skinetic-buildicon·white-knockout♪ node_lock
So we don't run the long job inline. We hand it to a queue and then poll for the result.
on-screen: Queue it, poll for result
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Queue it, poll for resultcurate items, nodes
3s3
matches intent
LogStream
template		build10.0–18.1stype-onicon·liquid-chrome♪ node_lock
Now a five-minute render or generation completes happily in the background while your fast deploy stays fast and never hits the
on-screen: Long AI jobs, no crash
expected on screen: red ground · a LogStream panel over a dimmed Signal Field · Nuntius leads · code · type-on · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape torusground redtreatment liquid-chromemotion type-onpower summoninstrument draw-on→Long AI jobs, no crashcurate codeLines, rows
4s4
matches intent
PipelineMap
template		proof18.1–23.1sreceipts-counticon·white-knockout♪ node_lock
So take your one function that flirts with the timeout and move it behind a queue.
on-screen: Move one slow call off-thread
expected on screen: red ground · a PipelineMap panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual receiptsshape torusground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Move one slow call off-threadcurate stages, statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene		futurist23.1–28.1sspatial-parallaxicon·liquid-chrome♪ bed
The Stack
expected on screen: red ground · torus hero in the shared Signal Field · Nuntius leads · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape torusground redtreatment liquid-chromemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→The Stack
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene		resolve28.1–33.1scoalescenceicon·liquid-chrome♪ bed_out
The Stack
expected on screen: red ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground redtreatment liquid-chromemotion 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: Vercel deploys a front-end in seconds, but its functions time out on long jobs. So don't run the long job inline. Queue it and poll for the result. Move your one slow call off the request thread. (AI-assisted)
instagramThe stack. Vercel deploys a front-end in seconds. But its functions time out on long jobs. The move: queue the job and poll for the result. Now a 5-minute render finishes in the background and your fast deploy stays fast. Move one slow call off-thread. #vercel #webdev #serverless #devtips #thebigtm
linkedinThe stack: Vercel lets you deploy a front-end in seconds, but its functions time out on long jobs. The move is simple. Don't run the long job inline. Queue it, then poll for the result. A five-minute render or AI generation finishes in the background while your fast deploy stays fast and never hits the timeout. The takeaway: find your one function that flirts with the timeout and move it behind a queue. One slow call off the request thread fixes most of these.
xThe stack: Vercel deploys a front-end in seconds but its functions time out on long jobs. Don't run them inline, queue the job and poll for the result. Move your one slow call off-thread. temerarii.xyz
facebookThe stack: Vercel deploys a front-end in seconds, but its functions time out on long jobs. The fix is simple. Don't run the long job inline. Queue it and poll for the result, so a five-minute render finishes in the background and your fast deploy stays fast. Take your one slow function and move it behind a queue.
threadsThe stack. Vercel deploys a front-end in seconds. But its functions time out on long jobs. The move: queue the job and poll for the result. A 5-minute render finishes in the background, deploy stays fast. Move one slow call off-thread.
pinterestThe stack: fix Vercel function timeouts on long jobs. Vercel deploys fast but times out on long work, so don't run the job inline. Queue it and poll for the result. A five-minute render finishes in the background while your deploy stays fast. Move one slow call off the request thread.
blueskyThe stack: Vercel deploys in seconds but functions time out on long jobs. Don't run them inline, queue the job and poll for the result. Move your one slow call off-thread.
youtubeTitle: The Stack: Fix Vercel Function Timeouts by Queuing Long Jobs Vercel deploys a front-end in seconds, but its functions time out on long jobs. The move: don't run the long job inline. Queue it, then poll for the result. A five-minute render or AI generation finishes in the background while your fast deploy stays fast and never hits the timeout. Find your one function that flirts with the timeout and move it behind a queue. More at temerarii.xyz

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

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