Capstone: ship your system

Build-along · ~20 min at your own keyboard

Everything converges here: pick one real recurring need, assemble the pieces you've built across this track — directive, scripts, verification, schedule or webhook, logging — into a system that runs whether you show up or not. You don't graduate into a certificate. You graduate into a system with a heartbeat.

The long version: Putting a system together ↗

Do this

0/4

Checkpoints

▸You should now see one input or schedule, one output and your review step named.
▸You should now see a one-page how-this-works doc next to the system.
▸You should now see a full cycle of runs with log lines.
▸You should now see one failure it handled, with evidence.

The three ways this goes wrong

You rebuild everything from scratch. — Reuse the pieces from earlier lessons. The capstone is assembly.
You touch it mid-cycle to keep it going. — Let it run. If you have to step in, note why, then fix the cause.
The evidence is only a screenshot of success. — Add log lines from several runs and the one failure.

Share what happened

Paste your one-page system doc (trimmed) plus the evidence set: log lines, an output sample, and any failure it recovered from.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.