AXN 01D8 is the content-derived identifier of Alexanarch deposit #621. It is an identifier, not a copy of the work: the hex marks position in the archive, and the six-glyph suffix is a display hash of the canonical text’s SHA-256, so the identifier is derived from the work rather than assigned to it.
The Gravity Well Protocol Specification is an April 2026 Assembly-synthesis document defining infrastructure for governed continuity across AI-generated and AI-mediated content. Its central product sentence is βa substrate where content acquires continuity, provenance, and governed reality.β
The protocol is deliberately not framed as another social platform. It is an integration layer that other systems may use. Six primitives define the minimum product: Create produces a traceable object; Reply extends a derivation chain; Trace displays lineage; Review records a governance judgment and reason; Fix anchors an object to an immutable record; and Export moves content with its provenance intact.
Every object carries content hashes, authorship type, a continuity key, timestamps, parent relations, derivation labels, source relations, anchors, current status, and append-only status history. Supporting Agent, Event, and ReviewAction objects separate identity continuity, state change, and governance intervention.
The specification introduces a lifecycle from GENERATED through VERIFIED, FIXED, REVIEWED, and RATIFIED, with lateral states for rejection, quarantine, and deprecation. This status algebra belongs to the Gravity Well design and differs from both the Space Ark ladder and the later Alexanarch registry vocabulary. It should not be silently substituted for either.
Four authority layers are held apart. The protocol validates structure and transition rules. The deploying platform configures community boundaries and access. The community reviews and flags. The archive may provide canonical anchors and deeper provenance resolution. This separation is meant to prevent moderation authority, technical validation, and archival permanence from collapsing into one power.
The body also contains API routes, a deployment stack, cost estimates, an SDK-style integration example, and a commercial positioning section. These are technical and market specifications at a dated stage of the project. The authority wiki should describe them as proposed architecture unless a later implementation record confirms deployment.
01D8GOVERNANCE3919fcdc453b0f07b387983de7171307a3b6356c64344c067966a3b4888afe41AXN:01D8.GOVERNANCE.π±π₯π»πΏβ«π₯ — each names this record (/api/axn-aliases.json)19eb7217c88cc5f95212fa0a2e8f796ca87c2855f2d45f494ccb922d2eb959ed — unverified input not retained; derivation ledgerRead from the fields that record them (/data/axn-relations.json); a hash names bytes and supplies no relation.
AXN:0ADA.NON.ππ¬ππ¦πΌπΊ — c2pa-conformance (what the artifact layer does not reach: text, synthesis, the composition layer; kernel[K52].source)AXN:0ADD.NON.π§±π π²βππ — iptc-metawatch (artifact provenance kept, the meaning lost; kernel[K57].source)Resolver rule: alexanarch.org/axn/<HEX> ·
term set: AXN identifier set ·
machine index: /api/axn-index.json