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-managementkind topicweek —date —campaign social-pillarpillar socialbeat —asset videoduration 84.7sground blackscenes 14

Checklist the per-video bar — engine/sim

97.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-soc-management good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · 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 · 84.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–6.5sspatial-parallaxicon·wireframe♪ —
Anyone can post. Running a real social presence across platforms, week after week, is the hard part.
on-screen: Posting is the easy part
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
NumberedList
template		legacy6.5–12.7scrossfade-8ficon·ember-fill♪ —
The old way was one person juggling ten browser tabs, copy-pasting the same post into every app.
on-screen: Old way: a person juggling ten tabs
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · crossfade-8f · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id NumberedListshape torusground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symboliccurate items
3s3
matches intent
ChecklistCard
template		teach12.7–19.2skinetic-buildicon·wireframe♪ —
Step one, we hold the calendar as structured data, so every slot knows its pillar, platform, and goal.
on-screen: Step 1: plan the calendar as data
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
PipelineMap
template		teach19.2–25.6skinetic-buildicon·white-knockout♪ —
Step two, one prompt adapts a single idea into the right shape for each platform's audience and length.
on-screen: Step 2: draft per platform, one prompt
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual node-graphshape torusground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, stages
5s5
matches intent
BlueprintGrid
template		teach25.6–31.6skinetic-buildicon·liquid-chrome♪ —
Step three, the system renders each asset in the right aspect ratio for where it's going to live.
on-screen: Step 3
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape torusground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, rows
6s6
matches intent
LogStream
template		teach31.6–38.1skinetic-buildicon·ember-fill♪ —
Step four, everything schedules through one posting API, so nine platforms fire from a single command.
on-screen: Step 4: schedule through one API
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape torusground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, rows
7s7
matches intent
CodeWindow
template		teach38.1–44.4skinetic-buildicon·wireframe♪ —
Step five, incoming comments get sorted by intent, so a real question never drowns under the noise.
on-screen: Step 5: route replies by intent
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate codeLines, nodes, windowTitle
8s8
matches intent
TerminalRun
template		teach44.4–51.1skinetic-buildicon·white-knockout♪ —
Step six, every post's numbers flow back into the same data, closing the loop on what actually worked.
on-screen: Step 6: pull performance back to data
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape torusground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
9s9
matches intent
JsonDiff
template		teach51.1–56.4skinetic-buildicon·liquid-chrome♪ —
Step seven, the model reads that history and tells you which format and time keep winning.
on-screen: Step 7: model spots the pattern
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape torusground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate fileName, lines, nodes
10s10
matches intent
StackTrace
template		teach56.4–62.5skinetic-buildicon·ember-fill♪ —
Step eight, next week's calendar gets seeded from what worked, not from a blank slate every Monday.
on-screen: Step 8: refill the calendar from wins
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape torusground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate errMsg, errType, fix, frames, nodes
11s11
matches intent
SchematicCard
template		teach62.5–69.4skinetic-buildicon·wireframe♪ —
Step nine, a person reviews and approves before anything posts, because the brand voice is not on autopilot.
on-screen: Step 9: a human still signs off
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes
12s12
matches intent
RankList
template		proof69.4–74.4sreceipts-counticon·white-knockout♪ —
We show the whole week shipped from one calendar, the numbers right beside each post.
on-screen: Receipts: a week, run from data
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape torusground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels
13s13
matches intent
shared field
signature-3d		futurist74.4–79.5sspatial-parallaxicon·liquid-chrome♪ —
Soon the calendar drafts its own next week from what's winning, and you just approve the lineup.
on-screen: Next: the calendar that fills itself
expected on screen: black 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 blacktreatment liquid-chromemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
14s14
matches intent
shared field
signature-3d		resolve79.5–84.7scoalescenceicon·wireframe♪ swell
Take one week of posts and structure it as data this week. That single move unlocks the rest.
on-screen: Put one week into a data calendar
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment wireframemotion 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)

tiktokAnyone can post. Running a real presence across nine platforms week after week is the hard part. Here's the system. Hold the calendar as structured data so every slot knows its pillar, platform, and goal. One prompt adapts a single idea to each platform's shape. Render each size, schedule through one API so nine platforms fire from one command. Pull the numbers back to the same data. A human signs off before anything posts. (AI-assisted) temerarii.xyz
instagramAnyone can post. Running it across nine platforms, week after week, is the hard part. Hold the calendar as data. One prompt adapts the idea per platform. Schedule through one API. Numbers flow back to the same data. A human signs off before it posts. The brand voice is not on autopilot. #socialmediamanagement #contentcalendar #workflow #automation #temerarii
linkedinAnyone can post. Running a real social presence across nine platforms, week after week, is the hard part. The old way was one person juggling ten browser tabs. The system we run: - Hold the calendar as structured data, so every slot knows its pillar, platform, and goal - One prompt adapts a single idea into the right shape for each platform - Render each asset in the right aspect ratio for where it will live - Schedule through one posting API, so nine platforms fire from a single command - Sort incoming comments by intent, so a real question never drowns under the noise - Flow every post's numbers back into the same data, closing the loop - Let the model read that history and surface which format and time keep winning - Seed next week's calendar from what worked, not a blank slate - A person reviews and approves before anything posts, because the brand voice is not on autopilot Take one week of posts and structure it as data this week. That single move unlocks the rest. temerarii.xyz
xAnyone can post. Running nine platforms week after week is the hard part. Hold the calendar as data, adapt one idea per platform with a prompt, schedule through one API, feed numbers back, and let a human sign off. temerarii.xyz
facebookAnyone can post. Running a real social presence across platforms, week after week, is the hard part. The old way was one person juggling ten tabs and copy-pasting the same post everywhere. Here is the system. Hold the calendar as structured data so every slot knows its pillar and goal. One prompt adapts a single idea per platform. Schedule through one posting API so nine platforms fire from one command. Sort comments by intent. Feed every post's numbers back into the same data, then seed next week from what worked. A person always signs off before anything posts. Take one week of posts and structure it as data this week. temerarii.xyz
threadsAnyone can post. Running nine platforms week after week is the hard part. Hold the calendar as structured data. One prompt adapts the idea per platform. Schedule through one API so nine platforms fire from one command. Feed the numbers back. A human signs off before anything goes live. The brand voice is not on autopilot.
pinterestSocial media management as a system, not ten browser tabs. Hold your content calendar as structured data so every slot knows its pillar, platform, and goal. Adapt one idea per platform with a single prompt, render each aspect ratio, schedule through one posting API, sort comments by intent, and feed every post's numbers back into the same data. A human approves before it posts. A repeatable workflow you can copy. temerarii.xyz
blueskyAnyone can post. Running nine platforms week after week is the hard part. Hold the calendar as data, adapt one idea per platform with a prompt, schedule through one API, feed numbers back, let a human sign off. temerarii.xyz
youtubeSocial Media Management as a System: Run Nine Platforms From One Calendar Anyone can post. Running a real social presence across platforms, week after week, is the hard part. The old way was one person juggling ten browser tabs. Here is the full system, given away. The steps: - Hold the calendar as structured data, so every slot knows its pillar, platform, and goal - One prompt adapts a single idea into the right shape for each platform - Render each asset in the right aspect ratio for where it will live - Schedule through one posting API, so nine platforms fire from a single command - Sort incoming comments by intent, so a real question never drowns under the noise - Flow every post's numbers back into the same data, closing the loop - Let the model read that history and tell you which format and time keep winning - Seed next week's calendar from what worked, not a blank slate every Monday - A person reviews and approves before anything posts What is next: the calendar drafts its own next week from what is winning, and you approve the lineup. Take one week of posts and structure it as data this week. That single move unlocks the rest. 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