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-W40-Tuekind threadweek W40date 2026-10-06campaign thread · Tuepillar brandbeat Tueasset videoduration 37.3sground blackscenes 6

Checklist the per-video bar — engine/sim

71.1/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-the-stack-W40-Tue good|bad)
⚠ 8 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedup_sequence_across_assetsdup_set_across_assetsdead_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 · 37.3s · 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·wireframe♪ node_lock
The tool is Slack, where team decisions go to disappear after a week.
on-screen: Slack search forgets fast
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Slack search forgets fast
2s2
matches intent
ChecklistCard
template
teach5.0–12.6skinetic-buildicon·wireframe♪ node_lock
So we export the key channels and index them for search, then a bot answers questions and links the first message.
on-screen: Export + index key channels
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Export + index key channelscurate items, nodes
3s3
matches intent
BuildLog
template
build12.6–19.8stype-onicon·wireframe♪ node_lock
Now anyone can ask the bot what we chose for a client and get the exact thread, not a guess.
on-screen: Ask Slack what we decided
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Signum leads · code · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape icosaground blacktreatment wireframemotion type-onpower summoninstrument draw-on→Ask Slack what we decidedcurate codeLines, lines
4s4
matches intent
LegacyCard
template
proof19.8–27.3sreceipts-counticon·wireframe♪ node_lock
So export one busy channel, index it, and ask it a real question. That is memory you can keep.
on-screen: Index one channel
expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual receiptsshape icosaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Index one channelcurate statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
futurist27.3–32.3sspatial-parallaxicon·wireframe♪ bed
The Stack
expected on screen: black 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 blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→The Stack
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve32.3–37.3scoalescenceicon·liquid-chrome♪ bed_out
The Stack
expected on screen: black ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground blacktreatment 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 tool is Slack, where team decisions go to disappear. The move: export the key channels, index them for search, then a bot answers and links the first message. Now you ask the bot what we chose for a client and get the exact thread. (AI-assisted)
instagramThe tool: Slack, where decisions go to disappear. The move: export key channels, index for search. A bot answers and links the source. Ask what we decided, get the exact thread. #slack #knowledgebase #ai #productivity #semanticsearch
linkedinThis week's tool and its real limit: Slack, where team decisions go to disappear after a week. The move: export the key channels and index them for search, then a bot answers questions and links the first message it pulled from. Now anyone can ask what we chose for a client and get the exact thread, not a guess and not three people pinged. The limit is honest, this works on decision-heavy channels, not your meme channel. Export one busy channel, index it, ask it a real question. That is institutional memory you can keep.
xThe tool: Slack, where team decisions go to disappear. Move: export key channels, index them for search, a bot answers and links the source thread. Ask what we decided, get the exact message back.
facebookThis week's tool: Slack, where team decisions go to disappear after a week. Here is the move. Export the key channels and index them for search, then a bot answers questions and links the first message it found. Now anyone can ask what we chose for a client and get the exact thread, instead of pinging three people. Export one busy channel, index it, and ask it a real question.
threadsThe tool is Slack, where team decisions go to disappear after a week. The move: export the key channels, index them for search, and a bot answers questions while linking the source message. Ask what we decided about a client, get the exact thread back. Memory you can keep.
pinterestTurn Slack into searchable team memory: export your decision-heavy channels, index them for semantic search, and let a bot answer questions while linking the original message. Stop losing decisions after a week. A practical knowledge-management and AI workflow tip for teams and operators.
blueskyThe tool: Slack, where team decisions go to disappear. Move: export key channels, index for search, a bot answers and links the source thread. Ask what we decided, get the exact message back.
youtubeTitle: Turn Slack Into Team Memory: Export, Index, Ask This week's tool and its real limit: Slack, where team decisions go to disappear after a week. The move is to export the key channels and index them for semantic search, then a bot answers questions and links the original message. Ask what we chose for a client and get the exact thread. Export one busy channel and try it.

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