Context

⚠️ SUPERSEDED 2026-05-08. This directory has been migrated into the LLMWiki at ../wiki/. The atomic pages with wikilinks live there now. New knowledge should be added to ../wiki/, not here. These files are kept for git history but are no longer the canonical knowledge base.

Migration map:

• architecture.md → wiki/concepts/concept-two-process-model.md (and others)
• argocd-applicationset.md → wiki/concepts/concept-applicationset.md
• config-hierarchy.md → wiki/concepts/concept-config-hierarchy.md
• deployer-steps.md → wiki/steps/step-*.md (one page per step)
• fixes-and-gotchas.md → wiki/incidents/incident-*.md (one page per incident)
• fixes-repo.md → wiki/concepts/concept-fixes-repo.md
• operations.md → wiki/runbooks/runbook-*.md
• patches.md → wiki/patches/patch-*.md and wiki/patches/fix-*.md
• rendering-pipeline.md → wiki/concepts/concept-rendering-pipeline.md
• safe-destroy.md → wiki/runbooks/runbook-safe-destroy.md

Start at ../wiki/MOC.md.

---

Persistent knowledge base for AI assistants working on this repo. Keeps high-value findings out of context window. Update when discoveries change; do not duplicate what CLAUDE.md already covers.

Index

• architecture.md — services, ports, two-process model, communication patterns
• deployer-steps.md — 20-step sequence (step 0 = preflight), file-vs-logical-number mismatch, checkpointing
• rendering-pipeline.md — helmfile template → split → post-process → inventory preflight → ESO
• fixes-repo.md — version-scoped fix pack loader, primitives DSL, failure→fix workflow
• patches.md — fork-pipeline (source) patches + deployer (rendered) patches, and why (patch catalog moved to fixes repo as of 2026-04-16)
• argocd-applicationset.md — ApplicationSet, labels, RollingSync phases, sync policy
• config-hierarchy.md — project.yaml / instance.yaml / runtime-state.json / checkpoint
• fixes-and-gotchas.md — non-obvious bugs, deadlocks, race conditions, fatal traps
• operations.md — common kubectl/argocd/debugging commands
• safe-destroy.md — Blast Radius dry-run flow, PlanStore, token gate, DestroyPlanModal
• ../docs/reliability/audit-2026-04-15.md — reliability audit: inventory, themes, risk matrix, open questions
• ../docs/reliability/roadmap-2026-04-15.md — reliability roadmap: 5 initiatives, sequencing, success criteria

Conventions

• Treat each file as a point-in-time snapshot. Verify against live code before asserting as fact.
• Prefer updating an existing file over creating a new one.
• Keep each file focused — if a file grows past ~300 lines, split by topic.