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-W24-Tuekind threadweek W24date 2026-06-16campaign thread · Tuepillar brandbeat Tueasset videoduration 35.0sground whitescenes 6

Checklist the per-video bar — engine/sim

90.3/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-the-stack-W24-Tue good|bad)
⚠ 4 flag(s) — not yet ship-ready: too_complexlow_vo_coveragedead_air · 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.0s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
first render · fix pending
shared field
signature-3ddead_air
hook0–5.0skinetic-buildicon·wireframe♪ node_lock
The tool is the chat assistant you use daily, and the catch is it forgets every fact about you the moment the session closes.
on-screen: ChatGPT forgets you
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape icosaground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→ChatGPT forgets you
2s2
first render · fix pending
ChecklistCard
templatedead_air
teach5.0–10.0skinetic-buildicon·wireframe♪ node_lock
The old fix was pasting context every time. The new fix is a memory MCP, a small server that stores facts the assistant can read back on its own.
on-screen: MCP memory server
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→MCP memory servercurate items, nodes
3s3
matches intent
StackTrace
template
build10.0–15.6stype-onicon·wireframe♪ node_lock
Suddenly the assistant knows your repo, your clients, your house rules across every session.
on-screen: Assistant that knows your stack
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Signum leads · code · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape icosaground whitetreatment wireframemotion type-onpower summoninstrument draw-on→Assistant that knows your stackcurate codeLines, errMsg, errType, fix, frames
4s4
matches intent
ListCard
template
proof15.6–21.4sreceipts-counticon·wireframe♪ node_lock
So clone one open-source memory MCP, point your client at it, and give it three facts
on-screen: Clone one memory MCP
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual receiptsshape icosaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Clone one memory MCPcurate items, statsLabels
5s5
matches intent
shared field
signature-3d
futurist21.4–28.4sspatial-parallaxicon·wireframe♪ bed
Soon your assistant remembers every client across every tool. Memory stops being a feature and becomes the floor.
on-screen: Memory becomes the floor
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape icosaground whitetreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→Memory becomes the floor
6s6
matches intent
shared field
signature-3d
resolve28.4–35.0scoalescenceicon·color♪ bed_out
One small server, and you never re-introduce yourself to a robot again. The Big T-M, signing off.
on-screen: Stop repeating yourself
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Stop repeating yourself

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: your daily chat assistant forgets you every session. The old fix was pasting context every time. Clone one open-source memory MCP, point your client at it, give it three facts. Now it knows your repo, clients, and house rules. (AI-assisted)
instagramChatGPT forgets you every session. The old fix: paste context every single time. The stack: Clone one open-source memory MCP. Point your client at it. Give it three facts. Now it knows your repo, your clients, your house rules. #ai #mcp #chatgpt #devtools #automation
linkedinThe chat assistant you use daily forgets you the moment a session ends. The old fix was pasting the same context every time, which is its own small tax. The stack that fixes it: clone one open-source memory MCP, point your client at it, and give it three facts to start. Suddenly the assistant knows your repo, your clients, and your house rules across every session. It is one open-source server and three facts. That is the whole setup.
xYour daily chat assistant forgets you every session. The old fix was pasting context every time. Clone one open-source memory MCP, point your client at it, give it three facts. Now it knows your stack. temerarii.com
facebookThe chat assistant you use every day forgets you the moment a session ends, so you end up pasting the same context over and over. The fix: clone one open-source memory MCP, point your client at it, and give it three facts. Now it knows your repo, your clients, and your house rules across every session. Give it a try this week.
threadsYour daily chat assistant forgets you every session. The old fix was pasting context every time. The stack: clone one open-source memory MCP, point your client at it, give it three facts. Now it knows your repo, your clients, your house rules across every session. One server, three facts.
pinterestGive your AI assistant long-term memory with one MCP server. The stack: your daily chat assistant forgets you every session, so stop pasting context. Clone one open-source memory MCP, point your client at it, and give it three facts. Now it knows your repo, clients, and house rules across every session.
blueskyYour daily chat assistant forgets you every session. Old fix: paste context every time. Clone one open-source memory MCP, point your client at it, give it three facts. Now it knows your stack.
youtubeTitle: Give Your AI Assistant Real Memory With One MCP Server The chat assistant you use daily forgets you every session, and the old fix was pasting context every time. The stack that fixes it: clone one open-source memory MCP, point your client at it, and give it three facts. Suddenly the assistant knows your repo, your clients, and your house rules across every session. One open-source server and three facts is the whole setup.

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