Checklist the per-video bar — engine/sim
80.9/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-field-notes-W52-Sat good|bad)⚠ 6 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 5 scenes · 28.0s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | hook | 0–7.2s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Field note. Every Friday someone hand-builds the same status report and quietly resents it. Let the machine write it. on-screen: The report nobody wants |
expected on screen: red ground · torus hero in the shared Signal Field · Nuntius leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape torusground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→The report nobody wants | |||||||
| 2 |  matches intent ChecklistCard template | teach | 7.2–13.0s | kinetic-build | icon·white-knockout | ♪ node_lock | Old chore: open every dashboard, copy the numbers, paste them into a doc, every week. on-screen: Pull, summarize, send, weekly |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Pull, summarize, send, weeklycurate items, nodes | |||||||
| 3 |  matches intent BuildLog template | diff | 13.0–18.0s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Find the report you dread most and hand its pieces to a model on a schedule. on-screen: Automate one Friday ritual |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Nuntius leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape torusground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Automate one Friday ritualcurate codeLines, lines | |||||||
| 4 |  first render · fix pending NodeGraphCard templatedead_airgeneric_scene | proof | 18.0–23.0s | receipts-count | icon·white-knockout | ♪ node_lock | Field Notes |
expected on screen: red ground · a NodeGraphCard panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual receiptsshape torusground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Field Notescurate hub, nodes, statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 23.0–28.0s | coalescence | icon·liquid-chrome | ♪ bed_out | Field Notes |
expected on screen: red ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||
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)
tiktokField note: every Friday someone hand-builds the same status report and quietly resents it. Open every dashboard, copy the numbers, paste them into a doc. Hand its pieces to a model on a schedule instead. (AI-assisted)
instagramThe report nobody wants to write.
Every Friday: open dashboards, copy numbers, paste into a doc.
Let the machine write it.
Hand the pieces to a model on a schedule.
#fieldnotes #automation #aitools #buildinpublic #worksmarter
linkedinField note. Every Friday, someone hand-builds the same status report and quietly resents it.
The old chore: open every dashboard, copy the numbers, paste them into a doc, every single week. It is repetitive, it is error-prone, and nobody wants the job.
The move: find the report you dread most and hand its pieces to a model on a schedule. Pick one Friday ritual and automate it this week.
xField note: every Friday someone hand-builds the same status report and resents it. Open dashboards, copy numbers, paste into a doc. Hand the pieces to a model on a schedule. temerarii.xyz
facebookField note: every Friday, someone hand-builds the same status report and quietly resents it. The old chore is open every dashboard, copy the numbers, paste them into a doc, every week. Find the report you dread most and hand its pieces to a model on a schedule instead.
threadsField note: every Friday someone hand-builds the same status report and quietly resents it.
Open every dashboard, copy the numbers, paste them into a doc, every week.
Find the report you dread most and hand its pieces to a model on a schedule.
pinterestHow to automate the weekly status report nobody wants to write: instead of opening every dashboard, copying numbers, and pasting them into a doc every Friday, hand the pieces to a model on a schedule. A simple field note on picking one dreaded ritual and letting the machine handle it.
blueskyField note: every Friday someone hand-builds the same status report and resents it. Open dashboards, copy numbers, paste into a doc. Hand the pieces to a model on a schedule.
youtubeTitle: Automate the Friday Report Nobody Wants to Write
Field note. Every Friday, someone hand-builds the same status report and quietly resents it. The old chore: open every dashboard, copy the numbers, paste them into a doc, every single week. The move is to find the report you dread most and hand its pieces to a model on a schedule. Pick one Friday ritual and automate it this week. (AI-assisted)