documentation-finalization

To finalize documentation against shipped behavior, you update Development Docs, Design Docs, and Domain Design Docs by validating terminology, fixing cross-references, and removing obsolete placeholders to ensure accuracy.

Updating design docs before a release involves applying a finalization checklist to remove placeholders, enforce terminology consistency, and validate cross-reference integrity against the current implementation state.

Maintaining terminology consistency and cross-reference integrity in domain docs requires validating document contents against the current implementation to align definitions and remove broken links.

You need to finalize decision docs and development docs when your implementation reaches a shipped state, ensuring the recorded decisions and guidance accurately reflect the final product behavior.

Yes, you can automate obsolete content removal by applying a formal finalization workflow that validates markdown documents against the implementation and strips out stale guidance automatically.

Documentation finalization works alongside markdownlint to enforce terminology consistency, using the finalization workflow to align content and the linter to validate markdown formatting rules.