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-Thukind longformweek W52date 2026-12-31campaign longform-youtubepillar multimediabeat asset videoduration 154.6sground 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-Thu 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 · 154.6s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–23.4sspatial-parallaxicon·color♪ bed_in
Still on this week's theme, explore what is next. Today, the Internet of Things, which is a long name for cheap sensors that report what is happening in the real world. By the end you will know how to take a reading off a real device and turn it into an action, a text, or a number on a dashboard, without a hardware team.
on-screen: The Internet of Things, made useful
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→The Internet of Things, made useful
2s2
matches intent
NumberedList
template
teach23.4–44.3skinetic-buildicon·wireframe♪ node_lock
First, demystify it. A connected device is a small thing that measures one fact, temperature, motion, a door open or shut, and sends that fact over the internet. A twenty dollar board with a sensor and wifi does this. The whole game is getting that fact somewhere you can use it. The hardware is the easy half.
on-screen: A sensor is just a fact, on
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→A sensor is just a fact, on a wirecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach44.3–66.3skinetic-buildicon·wireframe♪ node_lock
Second move. Devices mostly talk over a lightweight protocol called MQTT. A device publishes a message to a named channel, and anything listening to that channel hears it. You run a small broker in the middle that passes messages along. Once you see it as channels and messages, it stops being electronics and becomes plain plumbing you can reason about.
on-screen: Speak the language: MQTT
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Speak the language: MQTTcurate items, nodes
4s4
matches intent
LegacyCard
template
teach66.3–87.19999999999999skinetic-buildicon·wireframe♪ node_lock
Third move. A reading is worthless until it sits somewhere. We pipe every message into one store, a simple time-stamped table, so each fact has a when attached to it. From there you can chart it, search it, or trigger off it. Get the data landing reliably first. Everything clever you want to do comes after that.
on-screen: Land the data in one place
expected on screen: white ground · a LegacyCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Land the data in one placecurate nodes
5s5
matches intent
CheatSheet
template
teach87.2–110.6skinetic-buildicon·wireframe♪ node_lock
Fourth move. Now make it do something. Set a rule: when this channel reports past this line, send a text, flip a switch, open a ticket. We hang these rules off the same message stream. Cold storage too warm, someone gets a message before the product spoils. The value is not the sensor, it is the action it fires the second a fact changes.
on-screen: Turn a reading into an action
expected on screen: white ground · a CheatSheet panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Turn a reading into an actioncurate nodes, points, uses
6s6
matches intent
ComparisonTable
template
proof110.6–133.29999999999998sreceipts-counticon·wireframe♪ node_lock
Honest proof, no fake metrics. Our whole studio works the same shape: one brain reads a stream of facts and reacts to each one through small adapters. Swap a temperature sensor for a content job and it is the identical pattern, a fact arrives, a rule fires, an action runs. We learned the pattern on our own work, in public, at office.temerarii.xyz.
on-screen: We run the studio from one stream
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We run the studio from one streamcurate colA, colB, rows, statsLabels
7s7
matches intent
shared field
signature-3d
resolve133.3–154.60000000000002scoalescenceicon·color♪ bed_out
Takeaway. The Internet of Things is not a smart-city budget, it is one cheap sensor, one channel, one rule. Pick the one real-world fact you wish you knew sooner, a freezer, a door, a machine, and wire it up so it texts you when it changes. Start with one fact that matters. See the pattern running at office.temerarii.xyz.
on-screen: Wire up one sensor this week
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Wire up one sensor this week

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)

youtubeInternet of Things made useful: turn a sensor reading into an action The Internet of Things is a long name for cheap sensors that report what is happening in the real world. By the end you will know how to take a reading off a real device and turn it into an action, a text, or a number on a dashboard, with no hardware team. The moves: - A sensor is just a fact, sent. A connected device is a small thing that measures one fact, temperature, motion, a door open or shut, and sends it over the internet. A twenty dollar board with a sensor and wifi does this. The whole game is getting that fact somewhere you can use it. The hardware is the easy half. - Speak the language: MQTT. Devices mostly talk over a lightweight protocol called MQTT. A device publishes a message to a named channel, and anything listening to that channel hears it. You run a small broker in the middle that passes messages along. Once you see it as channels and messages, it becomes plain plumbing. - Land the data in one place. A reading is worthless until it sits somewhere. Pipe every message into one store, a simple time-stamped table, so each fact has a when attached. From there you can chart it, search it, or trigger off it. Get the data landing reliably first. - Turn a reading into an action. Set a rule: when this channel reports past this line, send a text, flip a switch, open a ticket. Cold storage too warm, someone gets a message before the product spoils. The value is not the sensor, it is the action it fires the second a fact changes. The honest proof, no fake metrics: our whole studio works the same shape, one brain reads a stream of facts and reacts to each one through small adapters. Swap a temperature sensor for a content job and it is the identical pattern: a fact arrives, a rule fires, an action runs. The Internet of Things is not a smart-city budget; it is one cheap sensor, one channel, one rule. Pick the one real-world fact you wish you knew sooner and wire it up so it texts you when it changes. See the pattern running at office.temerarii.xyz Keywords: Internet of Things for small business, IoT sensors, MQTT, time-series data, sensor to action, freezer monitoring, event-driven rules

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