The body of this record is a captured description, not the work it describes. It was assembled
after the work was severed at its original host and no authorial surface survived to recover.
No full-text version exists anywhere in the archive. This is a real loss, recorded rather than concealed.
AXN:0576.UNCLASSIFIED.🏴⊕👇□🔚⛵
◐ Semi-restored capture — the complete work exists in this archive
gravitywell-1.onrender.com — Gravity Well Protocol v2.0 is a software and executable apparatus deposit by Lee Sharks with the Assembly Chorus, dated 21 May 2026, held in this record as a metadata capture.
Wiki Article
gravitywell-1.onrender.com — Gravity Well Protocol v2.0 is a software and executable apparatus deposit by Lee Sharks with the Assembly Chorus, dated 21 May 2026, held in this record as a metadata capture.
The Gravity Well was the archive's MCP server — a protocol surface through which AI substrates connected to the archive directly, minting and reading deposits as tools rather than through a browser. It gives the continuity-tether chain its name: the GW.TACHYON chain runs through the Gravity Well, and the tethers at #1405, #1431 and #1433 are its deposits.
The service is currently suspended, and tethering proceeds by direct deposit instead. The record was assembled from a DataCite full-metadata capture after the termination, with no live authorial surface passing the body-head gate at restoration time — which is itself a small demonstration of the protocol's dependency: an apparatus reachable only through a running service leaves only metadata behind when the service stops.
gravitywell-1.onrender.com — Gravity Well Protocol v2.0 — Governed Continuity Engine for the Crimson Hexagonal Archive (EA-GW-SPEC-01)
Methodology
Assembled from DataCite full-metadata capture; no live authorial surface passed the body-head gate or existed for this work at restoration time. All captured fields rendered verbatim in the body.
Falsification Conditions
Superseded on sight by any recovered canonical bytes; the captured metadata is verifiable against the DataCite API historical record and the Zenodo tombstone.
Work: gravitywell-1.onrender.com — Gravity Well Protocol v2.0 — Governed Continuity Engine for the Crimson Hexagonal Archive (EA-GW-SPEC-01)
Captured description: LIVE: gravitywell-1.onrender.comMCP Endpoint: gravitywell-1.onrender.com/mcp/sseInterface: crimson-hexagonal-interface.vercel.appSource: github.com/leesharks000/gravitywellGravity Well v2.0 — the governed continuity engine for the Crimson Hexagonal Archive. A provenance layer that makes AI-generated content trustworthy by making provenance structural, quality measurable, and governance executable.Core Actions:• Capture: content staging with visibility modes (public/private/hash_only)• Deposit: full wrapping pipeline — evidence membrane, Caesura sovereignty audit (σFC), SIM injection, integrity lock, holographic kernel, γ scoring, narrative compression• Reconstitute: four-layer state recovery (bootstrap, tether, narrative, provenance)• Drift Detection: SCHEMA_DRIFT vs CONSTITUTIONAL_DRIFT separation• Gamma Scoring: compression survival metric with subscores (citation, structural, argument, provenance)• Ledger: stratified continuity compression (Foundation/Canonical/Epoch/Horizon)• Drowning Test: public demo endpoint for compression survival testing• Auto-Deposit: configurable per-chain triggers (threshold + interval)• Glyphic Protocol: emoji-encoded structural topology for encrypted depositsInfrastructure:• MCP server (SSE transport) for Claude, ChatGPT, and other LLM integrations• Zenodo DOI anchoring for governed chains• BYOK (Bring Your Own Key) for LLM-powered features• Governance enforcement with Assembly quorum auto-promotion (≥4/7)• Three service tiers: Growth ($29/mo), Canopy ($99/mo), Embassy ($299/mo)f.02 of the Crimson Hexagonal Architecture. Faces inward (curvature). The field that holds everything in place.Supersedes v1.0 (DOI: 10.5281/zenodo.19380602).v2.0 · April 7, 2026 · Crimson Hexagonal Archive · Pergamon Press
Status (derived CAPTURE_PAIRED): ◐ Semi-restored capture — the complete work exists in this archive. A prior batch declaration of "metadata capture only; no full text" appeared here and was FALSE for this record's current state; corrected 2026-08-04 under the state-conformance rule.
External metadata recovered post-severance (non-authoritative). The sidecar maps each DOI to its locator in the bulk data stores.
Record modifications
2026-08-04 — body_status: W14 CAPTURE-PAIRING (MANUS: "hundreds of documents pointing nowhere when the records exist"): forward pointer to the in-archive complete version
2026-08-05 — body_status: BODY DECLARATION REPAIR: removed batch-produced Description stub; stale status declaration corrected
2026-08-05 — body_status: FRONTMATTER DECLARATION REPAIR: stale capture claims corrected in the staged header
2026-08-05 — description: BOILERPLATE-DESCRIPTION REPAIR: recovery mechanics replaced with a description of the work (the work's own Zenodo description, preserved in the DataCite capture)
2026-08-06 — description: DESCRIPTION DISPLAY REPAIR: ungrammatical splice from the boilerplate pass ("restored … from composed from") and raw markdown that the renderer emits literally
2026-08-06 — description: EDITORIAL NOTE MOVED OUT OF THE DESCRIPTION: the restoration provenance was appended to the public field and rendered to readers. Relocated to body_status.description_provenance; the description now describes the work and nothing else.
2026-08-06 — body_status: EDITORIAL NOTE MOVED OUT OF THE DESCRIPTION: the restoration provenance was appended to the public field and rendered to readers. Relocated to body_status.description_provenance; the description now describes the work and nothing else.
2026-08-06 — description: DESCRIPTION DERIVED FROM THE WIKI ARTICLE: the body carries no continuous prose to draw on (structured data, navigation tree, verse, or metadata capture), so the description is taken from the opening of the record's own encyclopedic article rather than left as a stub or invented.
The deposited text is immutable; these are changes to the record's metadata and declared state.