Project Docs v0.4.2
This release brings the documentation-governance improvements since public v0.3.0 into v0.4.2.
- Starts from the complete request and the decisions readers need to make. Necessary content does not automatically require a separate file, and five logical responsibilities do not require five documents.
- Follows affected facts to their canonical owners, evidence and actual consumers, including consumers outside the diff. Reading scope and reference loading remain proportional to the question.
- Distinguishes current contracts, replaceable snapshots, frozen history and derived content, including different update modes within one file.
- Preserves visible implicit selection and existing write authorization. A concrete approval can cover continuous completion and necessary consumer updates; selection itself grants no new authority, and structural or ownership changes still need explicit authorization.
- Shortens the v0.4.2 catalog description while preserving direct governance requests, concrete governance problems and ordinary-maintenance exclusions. The remaining package body, references, assets and cases keep their accepted v0.4.1 semantics.
The installable six-file package tree is 84b977ad757affba74cf30c30d1ed20afe885d3f.
Repository checks and independent source review are distinct from the recorded local development-copy installation. Publication does not reclassify that copy as newly qualified stable installed-copy evidence, or establish fresh-task loading, model behavior or broad efficacy. Historical v0.3.0 qualification, prior candidates and failed evidence remain scoped to their original inputs.