Implemented plans (archive)
This folder contains historical implementation plans that have already been executed.
Implemented plans:
2026-04-29-annual-edition-recovery-handoff-docs.md2026-04-24-repo-audit-truth-maintenance.md2026-04-15-zensical-migration-prep.md2026-04-14-healtharchive-monorepo-consolidation-plan.md2026-04-14-healtharchive-monorepo-phase0-inventory.md2026-03-23-annual-crawl-content-cost-and-scope-diagnosis.md2026-03-21-docs-boundary-and-ci-followthrough.md2026-03-17-repo-governance-and-ci-maintenance.md2026-02-25-crawl-health-remediation.md2026-02-23-automation-first-crawl-alerting-and-dashboarding.md2026-02-19-alerting-noise-reduction-and-routing-tuning.md2026-02-06-crawl-operability-locks-and-retry-controls.md2025-12-24-6-phase-upgrade-roadmap-2025.md2025-12-24-sequential-implementation-plan.md2025-12-24-ops-observability-and-private-usage.md2025-12-25-compare-live.md2026-01-03-ci-e2e-smoke.md2026-01-03-ci-e2e-smoke-hardening.md2026-01-03-crawl-safe-roadmap-batch.md2026-01-03-ops-automation-verification-json.md2026-01-03-ops-automation-verifier-improvements.md2026-01-08-storagebox-sshfs-stale-mount-recovery-and-integrity.md2026-01-17-documentation-architecture-improvements.md2026-01-17-ops-tiering-alerting-and-incident-followups.md2026-01-17-disaster-recovery-and-escalation-procedures.md2026-01-03-search-ranking-and-snippets-v3.md2026-01-19-annual-crawl-resiliency-hardening.md2026-01-23-annual-crawl-throughput-and-artifacts.md2026-01-24-infra-error-and-storage-hotpath-hardening.md2026-01-27-archive-tool-hardening-and-ops-improvements.md2026-01-28-patch-job-config-and-integration-tests.md2026-01-29-warc-discovery-consistency.md2026-01-29-warc-manifest-verification.md2026-02-01-disk-usage-investigation.md2026-02-01-operational-resilience-improvements.md2026-02-06-ci-schema-and-governance-guardrails.md2026-02-06-roadmap-backlog-items.md2026-02-06-storage-watchdog-observability-hardening.md2026-02-07-deploy-workflow-hardening.md
Guidelines
- Compressed format: Plans >200 lines should be compressed to summary format (~40-80 lines) after implementation. See
docs/documentation-guidelines.mdfor the template. - Dated filenames: Use
YYYY-MM-DD-<short-slug>.md. - Canonical docs first: Ensure outcomes are captured in canonical docs under
docs/deployment/,docs/operations/, ordocs/development/. The plan here serves as supporting history. - Historical detail: Detailed phase-by-phase narratives are preserved in git history.
- Minimal edits: Treat these as a record; avoid ongoing edits except for small errata.