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 social-W33-Fri-1kind threadweek W33date 2026-08-21campaign thread · Fripillar it_devbeat Friasset videoduration 66.1sground whitescenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W33-Fri-1 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
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 9 scenes · 66.1s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–7.7sspatial-parallaxicon·ember-fill♪ bed_in
Trying to read every new launch will burn you out, and you still will not feel like you caught up.
on-screen: Chasing every update will break you
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Chasing every update will break you
2s2
matches intent
shared field
signature-3d		hook7.7–14.3skinetic-buildicon·wireframe♪ node_lock
Old way, you scrolled the feed all day, terrified of missing the one thing that supposedly mattered.
on-screen: The old way: drown in the feed
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→The old way: drown in the feed
3s3
matches intent
NumberedList
template		teach14.3–22.4skinetic-buildicon·wireframe♪ node_lock
Here is the move: judge each new thing by one question, does this touch a job I actually do this month.
on-screen: Triage by your real job
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Triage by your real jobcurate items, nodes
4s4
matches intent
ComparisonTable
template		proof22.4–30.5sreceipts-counticon·wireframe♪ node_lock
Most launches are not yours to act on, so you note them, let them pass, and feel zero guilt about it.
on-screen: Most news isn't yours to act on
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Most news isn't yours to act oncurate colA, colB, rows, statsLabels
5s5
matches intent
CodeWindow
template		diff30.5–36.8scrossfade-8ficon·wireframe♪ node_lock
A firehose leaves you soaked and confused. A simple filter leaves you calm and actually informed.
on-screen: A filter beats a firehose
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→A filter beats a firehosecurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template		teach36.8–44.099999999999994skinetic-buildicon·wireframe♪ node_lock
Now have a model summarize the week's news against your own job list and flag only what truly fits.
on-screen: Let a model summarize the week
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let a model summarize the weekcurate items, nodes
7s7
matches intent
KpiGrid
template		proof44.1–51.4sreceipts-counticon·wireframe♪ node_lock
You get one short list tied to your work, and your weekly catch-up shrinks to about ten quiet minutes.
on-screen: One short list, ten minutes
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→One short list, ten minutescurate kpis, statsLabels
8s8
matches intent
AnnotatedDiagram
template		step51.4–58.4skinetic-buildicon·wireframe♪ node_lock
Three steps: write your real jobs, filter the week against them, skim only the short list that survives.
on-screen: Step: define your jobs, filter, skim
expected on screen: white ground · a AnnotatedDiagram panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Step: define your jobs, filter, skimcurate callouts, stages, steps
9s9
matches intent
shared field
signature-3d		resolve58.4–66.1scoalescenceicon·ember-fill♪ bed_out
You do not have to chase the wave. You just have to ride the small part that is actually yours.
on-screen: Triage, don't chase
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Triage, don't chase

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)

tiktokChasing every AI update will burn you out, and you still won't feel caught up. (AI-assisted) The fix: judge each launch by one question, does this touch a job I actually do this month? Then let a model summarize the week against your job list. Triage, don't chase.
instagramStop chasing every update. Judge it by one question: does this touch my real job this month? Let AI filter the week. Skim the short list. #airnews #productivity #focus #aitools #worksmarter
linkedinTrying to read every new launch will burn you out, and you still won't feel caught up. The fix: triage instead of chase. Judge each new thing by one question, does this touch a job I actually do this month? Most launches aren't yours to act on, so you note them, let them pass, and feel no guilt. Then have a model summarize the week's news against your own job list and flag only what truly fits, so your weekly catch-up shrinks to about ten quiet minutes. You don't have to chase the wave. You just have to ride the small part that's actually yours.
xChasing every AI update will burn you out. Judge each launch by one question: does this touch a job I actually do this month? Then let a model filter the week against your job list. Triage, don't chase. temerarii.com
facebookTrying to read every new AI launch will burn you out, and you still won't feel caught up. The fix: judge each one by a single question, does this touch a job I actually do this month? Then let a model summarize the week against your job list. Triage, don't chase. temerarii.com
threadsChasing every AI update will burn you out, and you still won't feel caught up. Judge each launch by one question: does this touch a job I actually do this month? Then let a model filter the week against your job list. Triage, don't chase.
pinterestStay current without burnout: triage AI news by asking if it touches a job you actually do this month, then let a model filter the week against your job list. Avoid information overload, focus, AI news triage, productivity, work smarter not harder.
blueskyChasing every AI update will burn you out. Judge each launch by one question: does this touch a job I actually do this month? Then let a model filter the week against your job list. Triage, don't chase. temerarii.com
youtubeStay Current Without Burning Out: Triage, Don't Chase Trying to read every new launch will burn you out, and you still won't feel caught up. This short shows the fix: triage instead of chase. Judge each new thing by one question, does this touch a job I actually do this month? Most launches aren't yours to act on, so note them and let them pass. Then have a model summarize the week against your own job list and flag only what fits, so your catch-up shrinks to about ten quiet minutes. You don't have to chase the wave. Just ride the part that's yours. #productivity #focus #ainews

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view