The Hexagon Interface Constitution v2.0: System Specification for the Crimson Hexagonal Archive as Governed Commons

The Hexagon Interface Constitution v2.0 is a constitutional and implementation document by Lee Sharks. It defines how the Crimson Hexagonal Archive should be rendered as a governed commons without allowing any interface to replace the underlying architecture.

Its constitutional sentence states that the Hexagon is a governed reading-and-production environment whose topology organizes but does not replace text, labor, and provenance. Several principles follow. Text must remain directly readable rather than becoming metadata subordinate to a map. Participation, not mere public visibility, defines a commons. Constraint is generative rather than a usability defect. Contribution remains open at proposal and annotation levels while canonical modification proceeds through governance.

The document identifies seven first-class object types. Rooms carry physics and adjacency. Documents are deposited, versioned texts. Relations are typed and provenanced argumentative edges. Trails are ordered, shareable paths. Annotations accrete without modifying their targets. Proposals enter through the Airlock. Witness actions record reviews, votes, and status changes append-only.

Six interface modes provide different postures. MAP renders room topology. READ places documents first. WORK applies operators in a synthesis canvas. ORACLE routes questions through the graph rather than returning a terminal answer. ASSEMBLY exposes governance queues and witness actions. TRACE makes the chain of custody traversable. No mode is constitutionally central.

The charter also separates CONSTITUTIONAL and IMPLEMENTATION material. Governance principles, status visibility, participation thresholds, and object definitions require formal amendment. Storage vendors, API style, hosting, and staged build choices may change without constitutional amendment so long as they do not violate the higher layer.

The status system and governance clauses must be read historically. This document contains a particular transition ladder and quorum formulation that later records modify or contradict. It also describes build phases ranging from an existing map prototype to future workshops, governed contribution, automated deposit, and scaled public participation. These are roadmap states, not all completed features.