documentation

The concrete uses, built so they hold up. This lesson covers plan decomposition and what it is actually good for, the documentation nobody writes, chasing and dependency tracking, retrospectives where clustering helps and candour does not survive recording, and the portfolio view a PMO can genuinely gain.

Controls only work if a team meets them inside their normal process at a point where answers can still change the design. This lesson covers the three gates, writing a checklist that produces decisions rather than ticks, model and system cards, and giving someone the authority to stop a launch.

Governance that leaves no trace is indistinguishable from no governance. This lesson covers the documentation the AI Act requires: Annex IV technical documentation and its simplified SME forms, the quality management system, instructions for use, log retention, the fundamental rights impact assessment, registration, and how to make documentation a byproduct.

Retrieval solved the read side, so the constraint moved to what gets written down. This lesson covers the capture write path: architecture decision records, docs-as-code, change-triggered updates, and making capture cheap enough to survive. Then how to evaluate a company brain with golden questions, groundedness, and a permission regression suite, plus the failure modes that end these projects.

Before building a company brain, understand the problem it inherits. This lesson covers explicit versus tacit knowledge, Nonaka's SECI spiral, why the 1990s knowledge-management wave left rotting repositories behind, and what retrieval and LLMs genuinely changed. The answer is precise: they collapsed the cost of reading, and did nothing at all about the cost of writing.