p24-infra — Improvement Specs

Specifications and implementation plans for 15 infrastructure improvements identified in the May 2026 tooling audit.

Read first: rulebook.md — operating rules for designing, building, and shipping these improvements.


Priority tiers

TierMeaningTarget window
P1Material risk reduction (data loss, debug blindness, secret sprawl). Do next.Within 4 weeks
P2Quality-of-life + drift prevention. Do this quarter.Within 12 weeks
P3Polish + visibility. As bandwidth allows.Opportunistic

Index

Total: ~14 days of focused work.


Suggested execution order

Week 1   →  01 (backups) + 06 (cleanup health-checks) + 13 (runbook)
Week 2   →  03 (secrets) — unlocks 04, 14
Week 3   →  02 (logs) + 05 (synthetic) + 12 (certs)
Week 4   →  07 (status page) + 08 (CVE scanning)
Quarter  →  04 (IaC), 09 (SSH), 10–11, 14–15

Creating issues from these specs

A helper script generates one GitHub issue per spec, with the spec markdown as the issue body:

.\scripts\create-improvement-issues.ps1                # dry-run (default)
.\scripts\create-improvement-issues.ps1 -Apply         # actually create
.\scripts\create-improvement-issues.ps1 -Apply -Only 1,3   # subset

Each issue is created with milestone Triage, label enhancement, and a link back to the spec file on main.