Checklist the per-video bar — engine/sim
96.7/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review longform-W28-Fri good|bad)⚠ 2 flag(s) — not yet ship-ready: copy_genericgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
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 8 scenes · 172.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 | open | 0–22.7s | spatial-parallax | icon·ember-fill | ♪ bed_in | Launching the hub was the easy day. Keeping it up, fast, and backed up, every day after, is the real job. That work is systems admin, and most people only think about it the day everything breaks. Today I show you how we keep the The Big T-M hub healthy, so you can run your own site without the three a.m. emergency. on-screen: Keeping the hub up |
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Keeping the hub up | |||||||
| 2 |  matches intent NumberedList template | teach | 22.7–47.5s | kinetic-build | icon·wireframe | ♪ node_lock | First move. Every file of the hub lives in git, a system that saves a snapshot every time we change something. If a change breaks the site, we roll back to the last good snapshot in seconds. Nothing important lives only on one laptop. Your whole site, its full history, sitting safe where any version can be brought back. This is your undo button for the entire business. on-screen: Put the whole site in version control |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Put the whole site in version controlcurate items, nodes | |||||||
| 3 |  matches intent ChecklistCard template | teach | 47.5–71.3s | kinetic-build | icon·wireframe | ♪ node_lock | Second move. We do not upload files by hand, because hands make mistakes at midnight. Pushing an approved change to git triggers an automatic deploy that builds and publishes the new version. The same steps run the same way every time. Taking the human out of the boring part is how you remove the most common cause of an outage, which is a tired human. on-screen: Automate the deploy, remove the human |
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→Automate the deploy, remove the humancurate items, nodes | |||||||
| 4 |  matches intent StackTrace template | teach | 71.3–94.69999999999999s | kinetic-build | icon·wireframe | ♪ node_lock | Third move. You should learn the site is down from a machine, not a customer. We set up a simple monitor that pings the hub every few minutes and alerts us if it stops answering. We also keep a browser watching the live pages for errors. You do not refresh the site all day hoping. The machine watches so you can do real work. on-screen: Watch uptime, not your gut |
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StackTracevisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Watch uptime, not your gutcurate errMsg, errType, fix, frames, nodes | |||||||
| 5 |  matches intent SchematicCard template | teach | 94.7–119.2s | kinetic-build | icon·wireframe | ♪ node_lock | Fourth move. Everything that is not in git, like the contact records, gets backed up on a schedule to a separate place. And a backup you have never restored is just a hope. So we test ours by actually restoring it to a scratch copy and confirming the data is whole. The day you need a backup, you do not want to find out it never worked. on-screen: Back up like you will need it |
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→Back up like you will need itcurate nodes | |||||||
| 6 |  matches intent LogStream template | teach | 119.2–141.5s | kinetic-build | icon·wireframe | ♪ node_lock | The proof is dull on purpose. The hub is up. It loads. It came back from a test rollback cleanly and its backup restored whole, because we checked. We do not promise reliability with a number we made up. We run these habits on our own live site, and the fact that it keeps answering is the only proof that counts. on-screen: It is still up. |
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→It is still up. That is the proofcurate nodes, rows | |||||||
| 7 |  matches intent StatScoreboard template | proof | 141.5–167.0s | receipts-count | icon·wireframe | ♪ node_lock | That is how The Big T-M keeps the hub healthy. The takeaway, four habits. Put your whole site in git, automate the deploy, let a machine watch uptime, and test your backups by restoring them. Boring on purpose, because boring is what up looks like. Your next step. Get your site into git this week and set one uptime alert. See the live result at office dot temerarii dot xyz. on-screen: Set up your safety net |
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Set up your safety netcurate pillar, stats, statsLabels | |||||||
| 8 |  first render · fix pending shared field signature-3dgeneric_scene | resolve | 167.0–172.0s | coalescence | icon·ember-fill | ♪ bed_out | Social at scale: one story, nine native channels on-screen: Chapter 7 |
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Chapter 7 | |||||||
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)
youtubeSystems Admin for a Live Site: Git, Auto-Deploy, Uptime Alerts, Tested Backups
Launching a site is the easy day. Keeping it up, fast, and backed up every day after is the real job. This walkthrough shows how we keep a live hub healthy, so you can run your own site without the three a.m. emergency. Boring on purpose, because boring is what up looks like.
The four habits:
- Put the whole site in version control. Every file lives in git, which saves a snapshot on each change. A bad change rolls back in seconds. Nothing important lives only on one laptop. This is your undo button for the whole business.
- Automate the deploy and remove the human. Pushing an approved change triggers an automatic build and publish. The same steps run the same way every time. The most common cause of an outage is a tired human at midnight.
- Watch uptime with a machine, not your gut. A simple monitor pings the site every few minutes and alerts you if it stops answering. You learn the site is down from a machine, not a customer.
- Back up like you will need it. Anything not in git, like contact records, gets backed up on a schedule to a separate place. A backup you have never restored is just a hope, so test it by actually restoring to a scratch copy.
Your next step: get your site into git this week and set one uptime alert. See the live result at office.temerarii.xyz.
Keywords: systems administration, git deploy, uptime monitoring, backups, site reliability, devops basics.