Maintenance

This route owns the repository-health question: how do maintainers change the product safely without breaking boundary checks, docs truth, release language, or hostile-review evidence.

Start Here

• Open Maintainer Safe Change when the question is which route to follow before changing a package.
• Open Maintainer Handbook when the answer lives in checked maintainer code, make routing, or GitHub automation.
• Open Cross-Package Ownership when ownership or handoff class is in dispute.

High-Risk Checks

• Release Readiness Matrix
• Release Narrowing Protocol
• Release Support
• Artifact Governance
• Testing And Validation

Adjacent Routes

• Open Product Overview when the reader still does not know which product area their change touches.
• Open Workflow Families when the change could alter a family trust sentence or blocker.
• Open Execution when the change affects rerunability, run mode, or runtime artifacts.

Boundary

This route should help maintainers choose the right checks and owner surfaces before they edit code. It should not become another vague release reminder page.