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-W52-Monkind longformweek W52date 2026-12-28campaign longform-youtubepillar it_devbeat asset videoduration 162.2sground whitescenes 7

Checklist the per-video bar — engine/sim

98.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W52-Mon 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 7 scenes · 162.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–22.0sspatial-parallaxicon·ember-fill♪ bed_in
We are still on this week's theme, explore what is next, and today the topic is machine learning. Not the kind that needs a research lab. The kind a small business can actually use. By the end you will know how to make a model learn from your own history and predict the next thing, without writing a single equation.
on-screen: Machine learning, minus the math fear
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→Machine learning, minus the math fear
2s2
matches intent
NumberedList
template
teach22.0–43.3skinetic-buildicon·wireframe♪ node_lock
First, drop the mystery. Machine learning means you hand a program a pile of past examples and it finds the pattern that connects the inputs to the outcome. Your old orders, your old tickets, your old churned customers. The pattern is already sitting in your spreadsheet. The model just reads it more carefully than you have time to.
on-screen: Learning is just pattern from history
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→Learning is just pattern from historycurate items, nodes
3s3
matches intent
ChecklistCard
template
teach43.3–69.6skinetic-buildicon·wireframe♪ node_lock
Second move, and it is the one people skip. The model is only as good as the rows you feed it. So clean first. We dump the data to a CSV, open it, and fix the obvious junk: blank cells, dates in three formats, the same customer spelled four ways. We have a model do the cleaning pass for us now, but a human eyes the result. Garbage in stays garbage out.
on-screen: Clean the data before the model
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→Clean the data before the modelcurate items, nodes
4s4
matches intent
SchematicCard
template
teach69.6–93.39999999999999skinetic-buildicon·wireframe♪ node_lock
Third move. You do not need a giant network for most jobs. A plain model that fits in a single library call will predict churn or sort tickets just fine. We start small, get a number on the board, and only reach for something heavier if the small thing falls short. Most of the time it does not. Boring and working beats fancy and broken.
on-screen: Start with a model you can run
expected on screen: white ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Start with a model you can runcurate nodes
5s5
matches intent
LogStream
template
teach93.4–117.5skinetic-buildicon·wireframe♪ node_lock
Fourth move. This is how you keep from fooling yourself. Take your history and hide a slice of it before training. Train on the rest, then test on the slice the model never saw. If it predicts the hidden part well, you have something real. If it only nails the data it studied, you have a parrot. Always grade on the test it could not memorize.
on-screen: Hold back data to test honestly
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Hold back data to test honestlycurate nodes, rows
6s6
matches intent
RankList
template
proof117.5–141.3sreceipts-counticon·wireframe♪ node_lock
Honest proof. We use a small model to score every job in our content pipeline from zero to one hundred and flag the weak ones for a rewrite. It learned from the work we already marked good or bad. No mystery, no claimed lift. Just our own past judgments, fed back in, doing a first pass so a person spends time only where it matters.
on-screen: We sort our own pipeline this way
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We sort our own pipeline this waycurate rows, statsLabels
7s7
matches intent
shared field
signature-3d
resolve141.3–162.20000000000002scoalescenceicon·ember-fill♪ bed_out
Takeaway. Machine learning is not a degree, it is a loop: gather history, clean it, train small, test on hidden data. Pick one thing worth predicting, who will cancel, what to restock, and run that loop once. You will learn more from one honest test than from a month of reading. Watch ours run live at office.temerarii.xyz.
on-screen: Predict one thing, then expand
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→Predict one thing, then expand

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)

youtubeMachine learning for small business, minus the math: predict from your history Not the kind of machine learning that needs a research lab. The kind a small business can actually use. By the end you will know how to make a model learn from your own history and predict the next thing, without writing a single equation. The loop: - Learning is just pattern from history. You hand a program a pile of past examples and it finds the pattern connecting the inputs to the outcome. Your old orders, your old tickets, your old churned customers. The pattern is already sitting in your spreadsheet; the model just reads it more carefully than you have time to. - Clean the data before the model. The model is only as good as the rows you feed it. Dump the data to a CSV, open it, and fix the obvious junk: blank cells, dates in three formats, the same customer spelled four ways. Have a model do the cleaning pass, but a human eyes the result. Garbage in stays garbage out. - Start with a model you can run. You do not need a giant network for most jobs. A plain model that fits in a single library call will predict churn or sort tickets just fine. Get a number on the board, and only reach for something heavier if the small thing falls short. Boring and working beats fancy and broken. - Hold back data to test honestly. Hide a slice of your history before training. Train on the rest, then test on the slice the model never saw. If it predicts the hidden part well, you have something real. If it only nails the data it studied, you have a parrot. Always grade on the test it could not memorize. The honest proof: we use a small model to score every job in our content pipeline from zero to one hundred and flag the weak ones for a rewrite. It learned from the work we already marked good or bad. No mystery, no claimed lift. Just our own past judgments, fed back in, doing a first pass. Machine learning is not a degree, it is a loop: gather history, clean it, train small, test on hidden data. Pick one thing worth predicting and run it once. Watch ours run live at office.temerarii.xyz Keywords: machine learning for small business, predict churn, clean your data, train-test split, simple model, practical ML without math

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