Canon Objects
Specifications, concepts, engineering decisions, proof artifacts and other governed knowledge retain explicit identity and lifecycle rather than becoming anonymous pages.
A governed environment for preserving engineering knowledge as more than documents: identity, lifecycle, provenance, relationships, evidence, standing, chronology, and multiple representations remain inspectable together.
The goal is not another document repository. It is to keep the identity and standing of knowledge visible while allowing different human and machine representations.
Specifications, concepts, engineering decisions, proof artifacts and other governed knowledge retain explicit identity and lifecycle rather than becoming anonymous pages.
Readers can inspect where an object came from, what it supersedes, what evidence supports it, and which relationships are established rather than inferred.
Books, tree views, maps, evidence views, chronology and future 3D representations reveal the same governed knowledge without becoming its authority.
The next major Canon-facing interaction should connect ordinary reading to technical depth without turning the reading experience into an engineering console.
Begin in familiar long-form reading.
Reveal definition, version, standing and relationships.
Inspect provenance, prior versions, evidence and technical records as needed.
Return to the passage without losing context.
Status: this complete passage → depth → exact-return loop is a planned interaction milestone, not yet represented as complete Build 12.6 behavior.
Build 12.6 makes their relationship explicit rather than presenting Explorer, Library, lineage, proof and Canon material as disconnected pages.
Reading, Tree, 3D Navigator, SIW and future inquiry modes are being aligned as independent governed representations of the same Canon knowledge substrate.
Updated (Build 15 local integration candidate): Book One's 12-chapter object binding through Canon Access, including governed representation content, is proven and integrated into the local Reader candidate — no longer pending. See the Build 15 convergence status table for the exact standing (proven / integrated / locally preflighted — not publicly deployed).