English · Español
Phase 40 — Hardening, Postmortem, "What's Next"¶
Requires: 39 — Capstone: The Miniature Production System Teaches:
postmortem·hardening·performance-audit·synthesisJump to any chapter from the phase reference index.
Chapter map¶
🇪🇸 Fase final. Sin nuevo código (más allá de pulir lo existente). Tres entregables: pasar un hardening sobre el servicio capstone, escribir el postmortem del viaje de 40 fases, y curar una lista de lectura. Si el resto del proyecto fue aprender a construir, esta fase es aprender a cerrar.
Anchors: LYNX_CORTEX.md §4 / PHASE 40, PHASE_40_PLAN.md, LYNX_CORTEX_ADDENDUM.md §A12.
Goal¶
Close out the 40-phase journey. Three deliverables, in order:
- Hardening pass on the Phase 39 grammar-tutor service — close residual
security/THREATS.mditems, raise the bar on observability and cost guardrails. - Postmortem — what worked, what didn't, what changed Borja's mental model. Real incident-style structure (timeline, contributing factors, action items).
- "What's next" reading list — a curated 20-40 entries pointing at the next-largest problems: full-size LLMs, distributed at scale, real-world MLOps, the research frontier.
The phase ships no new src/ module. It hardens existing code, writes documents, and stops.
What you'll produce¶
docs/phase-40-hardening-postmortem/
├── README.md # this file
├── postmortem.md # the journey postmortem (lab 01)
├── READING_LIST.md # 20-40 annotated resources (lab 02)
├── diagrams/
│ └── knowledge-graph.svg # the visual map of the 40 phases (lab 03)
└── theory/ # the docs you're reading
Plus updates to:
security/THREATS.md— every open thread closed, accepted, or punted.learners/borja/phase-40/reflections.md— final synthesis.PHASE_40_REPORT.md— closure report.ROADMAP.md— flipped to 🟢.
What this phase does NOT cover¶
- New features. None. Adding scope here is the failure mode.
- A second project. Phase 40 ends here. A "next charter" is optional and lives in
learners/borja/, not in this phase's deliverables. - Re-architecting Phase 39's service. If a hardening item requires re-architecture, document it as a known gap, don't fix it.
- Recording a talk or write-up for external audiences. Welcome to do, but out of phase DoD.
Read order¶
theory/00-motivation.md— what "closing a project" means in practice.theory/01-postmortem-structure.md— the canonical postmortem format and why each section exists.theory/02-decision-survival.md— measuring which architectural decisions held up.theory/03-residual-risk-and-offramps.md— accepting risk explicitly; finding the next problem.lab/00-hardening-pass.md— close outsecurity/THREATS.md.lab/01-write-the-postmortem.md— structured doc.lab/02-reading-list.md— the curated list.lab/03-knowledge-graph.md— the visual artefact.lab/04-final-reflection.md— synthesis.
Definition of Done¶
See PHASE_40_PLAN.md §6 (at repo root). Briefly:
- All open items in
security/THREATS.mdeither closed or carry an explicit risk-acceptance rationale. postmortem.md≥ 1500 words, structured.READING_LIST.md≥ 20 entries, each annotated.- Knowledge graph rendered to SVG, linked here.
learners/borja/phase-40/reflections.mdwritten.PHASE_40_REPORT.mdwritten and approved; ROADMAP row flipped to 🟢.
Next: theory/00-motivation.md
Further reading¶
Optional — enrichment, not required to pass the phase.
- 📕 Postmortem Culture: Learning from Failure — Google SRE · 2016. how to write a blameless postmortem.
- 📄 How Complex Systems Fail — Richard Cook · 1998. 18 lessons that age extremely well.