Start with the LikeC4 specification. Diagrams own the scopes in the ownership index. Supporting prose intentionally owns precise contracts,invariants,rationale and evidence within completed split specifications;do not maintain duplicate authoritative definitions. HPX-OWNER-032 changes definition ownership, not the status of proposed designs or implementation evidence.
Owner decisions and accepted obligations retain authority. Diagram-first ownership does not promote planned features to implemented ones. Current users are workspace-local, with one machine user per provider per workspace; see canonical actor definitions and the supplemental chat/MCP contract. No public API, new code or publication is authorised by documentation changes.
These organise supporting documents; they do not duplicate the C1–C4 model:
- Purpose
- Governance
- Requirements and acceptance
- Architecture supplements and ADRs
- Domain invariants
- Subsystems, interfaces and formats
- Exact implementation contracts
- Assurance and evidence
- Guides
Maintain one definition per claim. Update diagram-owned structure in its owning view; retain exact wire/schema/byte/permission/security rules and acceptance criteria in their assigned precise contracts;a deliberate model/prose partition keeps those rules in their precise homes. Preserve stable IDs and source provenance. Requirements, proposals, implementation and actual verification are separate. Do not invent missing mechanisms, infer acceptance by recency or discard evidence.
Read current execution status and the current scope/evidence summary, then only the affected contracts. Read chronological logs, audit reports and full proof details when their evidence is relevant. Use the test register for checks actually executed. No application acceptance follows from model validation.
The shared LikeC4 workflow describes commands and external local tooling state. Active documentation lives in the numbered01–09 folders; the root retains this entry point and the shared model configuration/package files.