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 topic-soc-strategykind topicweek —date —campaign social-pillarpillar socialbeat —asset videoduration 94.5sground blackscenes 14

Checklist the per-video bar — engine/sim

93.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-soc-strategy good|bad)
⚠ 2 flag(s) — not yet ship-ready: too_complexgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel
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 14 scenes · 94.5s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–5.4sspatial-parallaxicon·ember-fill♪ —
Most brands do not have a social strategy — they have a posting habit and a quiet hope.
on-screen: Social strategy, not posting
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→three-mark
2s2
matches intent
NumberedList
template		legacy5.4–12.600000000000001scrossfade-8ficon·wireframe♪ —
The old approach posted whatever was on hand, whenever someone remembered, and called the silence a tough algorithm.
on-screen: The old way: post and pray
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListshape torusground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate items
3s3
matches intent
ChecklistCard
template		teach12.6–20.0skinetic-buildicon·wireframe♪ —
We start by mapping who you are actually talking to, pulling real audience data from the platform analytics APIs.
on-screen: Start with the audience
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→html-in-canvas-panelcurate items, nodes
4s4
matches intent
NodeGraphCard
template		teach20.0–25.9skinetic-buildicon·wireframe♪ —
Then we narrow to three content pillars, so every post belongs to a theme instead of being a one-off.
on-screen: Pick three pillars
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate hub, nodes
5s5
matches intent
StepFlow
template		teach25.9–32.6skinetic-buildicon·wireframe♪ —
We run social listening with an Apify scraper to see what your audience already argues about, then write into that.
on-screen: Listen before you talk
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, steps
6s6
matches intent
ProcessFlow
template		teach32.6–39.5skinetic-buildicon·wireframe♪ —
We take a single idea and cut it for each platform's shape, rendering the variants programmatically with Remotion.
on-screen: One idea, many cuts
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, steps
7s7
matches intent
AnnotatedDiagram
template		teach39.5–47.2skinetic-buildicon·wireframe♪ —
We schedule against when your audience is actually online, not a generic best-time chart, using each platform's own data.
on-screen: Schedule on purpose
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate callouts, nodes
8s8
matches intent
FlowSchematic
template		teach47.2–54.400000000000006skinetic-buildicon·wireframe♪ —
A single approved cut goes out across every account through the Blotato API, so distribution stops eating your day.
on-screen: Post once, everywhere
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, stages
9s9
matches intent
BuildLog
template		teach54.4–60.5skinetic-buildicon·wireframe♪ —
We draft replies with Claude but a person hits send, so the account sounds like you and not a bot farm.
on-screen: Reply like a human
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate lines, nodes
10s10
matches intent
WireframeMock
template		teach60.5–67.6skinetic-buildicon·wireframe♪ —
Every week we pull the numbers that matter — saves, shares, and clicks to the site — not the vanity follower count.
on-screen: Measure what moved
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes
11s11
matches intent
DiffCard
template		teach67.6–73.69999999999999skinetic-buildicon·wireframe♪ —
Then we kill the pillar that flopped and double the one that landed, so the strategy sharpens itself each
on-screen: Cut what does not work
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate lines, nodes
12s12
first render · fix pending
RankList
templategeneric_scene		proof73.7–81.0sreceipts-counticon·wireframe♪ —
On one account this loop roughly doubled reach while cutting production time in half. Placeholder until the real dashboard is live.
on-screen: 2.3x reach, half the time
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels
13s13
matches intent
shared field
signature-3d		futurist81.0–88.6sspatial-parallaxicon·wireframe♪ —
Soon the whole loop runs as a scheduled system — scrape, draft, schedule, measure — with you steering instead of grinding.
on-screen: A self-tuning engine
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape torusground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
14s14
matches intent
shared field
signature-3d		resolve88.6–94.5scoalescenceicon·ember-fill♪ swell
If you want social that compounds instead of just filling a calendar, come build it with The Big T-M.
on-screen: Build your strategy · temerarii.xyz
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→three-coalescence

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 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

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

tiktokMost brands don't have a social strategy. They have a posting habit and a quiet hope. Here's the loop that fixes it. Map who you're actually talking to with platform analytics. Narrow to three content pillars. Listen with an Apify scraper, then write into what your audience argues about. Cut one idea per platform with Remotion. Measure saves, shares, and clicks, not follower count. Kill what flopped, double what landed. (AI-assisted) temerarii.xyz
instagramMost brands don't have a social strategy. They have a posting habit and a quiet hope. The loop: Map your real audience from platform data. Narrow to three pillars. Listen before you talk. Measure saves, shares, clicks, not followers. Kill what flopped. Double what landed. Social that compounds, not just fills a calendar. #socialstrategy #contentpillars #remotion #analytics #temerarii
linkedinMost brands do not have a social strategy. They have a posting habit and a quiet hope, then call the silence a tough algorithm. Here is the loop we run: - Map who you are actually talking to, pulling real audience data from the platform analytics APIs - Narrow to three content pillars, so every post belongs to a theme instead of being a one-off - Run social listening with an Apify scraper to see what your audience already argues about, then write into that - Take one idea and cut it for each platform's shape, rendering variants programmatically with Remotion - Schedule against when your audience is actually online, using each platform's own data - Push one approved cut across every account through the Blotato API - Draft replies with Claude, but a person hits send - Measure saves, shares, and clicks to the site, not the vanity follower count - Kill the pillar that flopped and double the one that landed If you want social that compounds instead of just filling a calendar, come build it with The Big T-M. temerarii.xyz
xMost brands don't have a social strategy. They have a posting habit and a quiet hope. The loop: map your audience from platform data, pick three pillars, listen with Apify, measure saves and clicks, kill what flopped. temerarii.xyz
facebookMost brands do not have a social strategy. They have a posting habit and a quiet hope, then blame a tough algorithm. Here is the loop that fixes it. Map who you are actually talking to with platform analytics. Narrow to three content pillars. Listen with an Apify scraper, then write into what your audience already argues about. Cut one idea per platform with Remotion. Schedule against when your people are online. Measure saves, shares, and clicks to the site, not follower count. Then kill the pillar that flopped and double the one that landed. Want social that compounds instead of just filling a calendar? Build it with The Big T-M at temerarii.xyz.
threadsMost brands don't have a social strategy. They have a posting habit and a quiet hope. The loop: map your real audience from platform data, pick three pillars, listen with an Apify scraper, cut one idea per platform with Remotion, measure saves and clicks, then kill what flopped and double what landed. Social that compounds, not just fills a calendar.
pinterestSocial media strategy that compounds: the full loop. Map your real audience from platform analytics APIs, narrow to three content pillars, run social listening with an Apify scraper, cut one idea per platform with Remotion, schedule when your audience is online, measure saves and shares and clicks instead of follower count, then kill what flopped and double what landed. A repeatable strategy you can copy. temerarii.xyz
blueskyMost brands don't have a social strategy. They have a posting habit and a quiet hope, then blame the algorithm. The loop: map your real audience, pick three pillars, listen with Apify, cut per platform with Remotion, measure saves not followers, double what landed. temerarii.xyz
youtubeSocial Media Strategy That Compounds: The Full Loop, Given Away Most brands do not have a social strategy. They have a posting habit and a quiet hope, then call the silence a tough algorithm. This is the loop that fixes it. The steps: - Map who you are actually talking to, pulling real audience data from the platform analytics APIs - Narrow to three content pillars, so every post belongs to a theme - Run social listening with an Apify scraper to see what your audience already argues about - Take one idea and cut it for each platform's shape with Remotion - Schedule against when your audience is actually online, not a generic chart - Push one approved cut across every account through the Blotato API - Draft replies with Claude, but a person hits send - Measure saves, shares, and clicks to the site, not the vanity follower count - Kill the pillar that flopped and double the one that landed What is next: the whole loop runs as a scheduled system, with you steering instead of doing it all by hand. If you want social that compounds instead of just filling a calendar, come build it with The Big T-M 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