Ethan's recent deboerbuilding commits show a pattern of building safety gates (deploy gated on contact tests, a notifier that cannot send yet, write-guard proof artifacts like SABOTAGE-viatool.txt) — but there's no single place that tracks which guards are armed vs. still stubbed. Guard Ledger scans all repos for these deliberately-disabled safety mechanisms and surfaces the ones that have been 'temporarily' off the longest, so a gate never silently stays open past its intent.
Create ~/bin/guard-ledger: grep across ~/projects/* and active repos for guard markers (`cannot send yet`, `DRY_RUN=1`, `return early`, `SABOTAGE`, `# GUARD:`, `if false`, skipped tests via `test.skip|@pytest.mark.skip|xit(`). For each hit, run `git log -1 --format=%at -S'