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 longform-W37-Tuekind longformweek W37date 2026-09-15campaign longform-youtubepillar socialbeat asset videoduration 151.2sground blackscenes 8

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W37-Tue good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
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 8 scenes · 151.2s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–20.9sspatial-parallaxicon·ember-fill♪ bed_in
Today is about strategic partnerships, the quiet engine under this week's theme. A good partner shares your audience but not your fight. The hard part is finding them before someone else does. You will learn how to read your own listening data and surface the partners who are already standing next to you in your customers' lives.
on-screen: Partners hide in your data
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Partners hide in your data
2s2
matches intent
NumberedList
template
teach20.9–42.2skinetic-buildicon·wireframe♪ node_lock
First move. Take your scraped mentions and ask Claude to find every brand, tool, or person named in the same post as you, then count them. This is co-mention. If people keep saying they use your thing alongside another thing, that other thing is a partner candidate, ranked by a number you can actually see, not a hunch.
on-screen: Count who shows up beside you
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Count who shows up beside youcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach42.2–63.1skinetic-buildicon·wireframe♪ node_lock
Second move. Have the model split that list into two piles: ones people compare you against, and ones people use with you. The against pile is competition. The with pile is partnership. This one cut saves you from pitching a rival a joint deal, which is the fastest way to look like you never did your homework.
on-screen: Sort allies from rivals
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Sort allies from rivalscurate items, nodes
4s4
matches intent
LogStream
template
teach63.1–84.0skinetic-buildicon·wireframe♪ node_lock
Third move. For your top with-partner, pull their public audience signals with a web fetch and have the model compare them to yours. You want enough overlap that a shared offer makes sense, and enough difference that you each bring people the other does not have. Same crowd exactly is not a partnership. It is a mirror.
on-screen: Check the overlap is real
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Check the overlap is realcurate nodes, rows
5s5
matches intent
PipelineMap
template
teach84.0–105.6skinetic-buildicon·wireframe♪ node_lock
Fourth move. Ask the model to write the partnership note as a trade, not a favor. One thing you give them, one thing you want back, one small test to start. People say yes to a clear small trade. They go quiet on a vague big ask. Keep the first step tiny enough that saying yes costs almost nothing.
on-screen: Draft the offer, not the flattery
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Draft the offer, not the flatterycurate nodes, stages
6s6
matches intent
CheatSheet
template
teach105.6–123.3skinetic-buildicon·wireframe♪ node_lock
Honest proof: the partners we work with came out of this same co-mention read, not a conference badge swap. We let the data point at the obvious allies we kept overlooking. The names were sitting in our own mentions the whole time, waiting for someone to count them.
on-screen: We find ours this exact way
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→We find ours this exact waycurate nodes, points, uses
7s7
matches intent
KpiGrid
template
proof123.3–143.5sreceipts-counticon·wireframe♪ node_lock
The takeaway: your best partner is probably already in your data, mentioned right next to you, and you have been scrolling past them. Your next step is small. Run the co-mention count, sort with from against, and pick the one name at the top. The full method is live at office dot temerarii dot xyz.
on-screen: Start at office.temerarii.xyz
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Start at office.temerarii.xyzcurate kpis, statsLabels
8s8
matches intent
shared field
signature-3d
resolve143.5–151.2scoalescenceicon·ember-fill♪ bed_out
Social at scale: one story, rewritten by hand into nine posts, each shaped for how people read on that app.
on-screen: Chapter 7
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Chapter 7

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

Social captions supplemental published copy · per channel (comp_id level)

youtubeFind strategic partners hiding in your own social data A good partner shares your audience but not your fight. The hard part is finding them before someone else does. This is how to read your own listening data and surface the partners already standing next to you in your customers' lives. The method: - Count who shows up beside you. Ask Claude to find every brand, tool, or person named in the same post as you, then count them. If people keep saying they use your thing alongside another, that other thing is a ranked partner candidate, by a number you can see. - Sort allies from rivals. Split the list into people who compare you against, and people who use you with. The against pile is competition. The with pile is partnership. This one cut stops you pitching a rival a joint deal. - Check the overlap is real. For your top with-partner, pull their public audience signals with a web fetch and compare. You want enough overlap that a shared offer makes sense, and enough difference that you each bring people the other does not. - Draft the offer, not the flattery. Have the model write it as a trade: one thing you give, one thing you want, one small test to start. Clear small trades get yes; vague big asks go quiet. The honest proof: the partners we work with came out of this same co-mention read, not a conference badge swap. The names were sitting in our own mentions the whole time. Run the co-mention count, sort with from against, and pick the one name at the top. The full method is at office.temerarii.xyz. Keywords: strategic partnerships, co-mention analysis, audience overlap, partner outreach.

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