Documents / Governance
Find the right operational explanation first, then inspect its status, freshness, provenance, and source boundary before relying on a record.
Governance & Control is the reader-facing front door to the project’s source-authority, research-control, role, registry, publication, validation, and maintenance material. It organizes already published contextual pages by reader purpose; it does not turn the website, a registry row, or a workflow record into new authority.
Each entry exposes its document type, operational scope, registered status, dated source snapshot, and manifest-backed provenance before sending readers to an internal explanatory route. Repository paths remain secondary provenance rather than the primary information architecture.
Raw governance Markdown is a separate publication class. A file appears only after explicit review, approval, catalog registration, and import into the public governance allowlist. No such public Markdown record is present in the current catalog, so this page does not expose an unapproved raw file.
Public catalog boundary
These counts come from the checked document and provenance manifests. They report publication state without promoting repository Markdown or transient control data.
Contextual front door
Every destination is an existing internal page. Its card states the document type, operational scope, and registered publication status; the audit table below makes freshness and provenance explicit.
Source Authority
Begin here when deciding which material may define a claim or status statement.
Research Control
Follow the operational chain without treating workflow completion as scientific proof.
Roles and Schemas
Inspect how role identity narrows into current, job-bound authority.
Publication and Provenance
See how source-bounded material becomes readable without changing source authority.
Registries and Status
Use registry rows to locate owners and status, then inspect the named evidence.
Registries and Status
Treat this as dated context that may become stale, never as a live control feed.
Registries and Status
Use retrieval to find evidence without allowing the retrieval layer to become authority.
Validation and Handoffs
Read validation at the exact scope checked; do not infer claim promotion or wider permission.
Website Maintenance
Use the map after identifying the reader task; repository layout remains secondary.
Website Maintenance
Apply the publication boundary while building or reviewing a website route.
Scroll table horizontally when it overflows.
Status discipline
The material class determines the safe reader action and the limit that must remain attached to it.
Scroll table horizontally when it overflows.
Inspection boundary
The catalog and manifests can establish identity, status, and traceability. The registered source or current governed record still owns the operative statement.