Govern

Most personal automation rots. Scripts drift out of sync with what they are meant to do, documentation goes stale within weeks, and nobody notices until something breaks far downstream. What is built against that here is not any single pipeline; it is a set of checks running underneath everything else, catching decay as it happens rather than after the fact.

Every file the system writes gets checked the moment it lands. A set of hooks fires immediately after any write: one validates the note's metadata against a single canonical schema, one confirms the automatic cross-linking block is present where it should be, one checks that a note has been filed under the right project grouping. None of these block the write outright; each surfaces a clear warning in the same turn, so a mistake gets fixed before I move on.

Everything that runs on a schedule runs the same way, out in the open. Twenty-six scheduled jobs handle the recurring work, from the daily briefing to filing incoming content to the backups themselves, each living in its own folder with its scripts, logs, and state kept together. A dedicated health job checks hourly whether each job actually last succeeded, not just whether it is scheduled to exist, and writes one status table I glance at each morning: if something has gone silent, I find out there, not weeks later.

None of this is exciting to build. A system this large only stays trustworthy if it polices itself continuously, instead of relying on me to notice when something has quietly stopped working.