Alexanarch
api.datacite.org/dois/{doi}. The repository was Zenodo (CERN-operated). The deposits were primary scholarship: empirical datasets, critical editions, theoretical papers, monographs — 862 works, 1,817 registered DOIs. Within 24 hours, the works existed but their addresses didn’t.
Alexanarch is the sovereign counter-infrastructure built in response. Content-derived identifiers. Distributed custody. Tombstone permanence. If the DOI system cannot guarantee persistence, the persistence has to come from somewhere else. The empirical foundation is documented in DOIs ≠ Permanent Identifiers; the structural argument in Zenodotus’ Book-Burning. Reference: GitHub Issue #2606.
Recent Deposits
Founding Principles
Identifiers are derived from the work itself, not granted by a host. The address is computed from the content’s SHA-256. No platform can revoke an identifier no platform issued. Persistence does not depend on custodial trust.
Withdrawn or removed records retain a permanent tombstone with bibliographic metadata, withdrawal reason, provenance chain, and the canonical content hash. An identifier may resolve to a tombstone, but never to a 410. The revocation gap is closed by design.
The corpus is mirrored across independent custodians: alexanarch.org, github.com/leesharks000/alexanarch, content-addressable manifests (SHA256SUMS), machine-readable chunks. Loss of any single node does not erase the record. Reconstruction is verifiable from any complete mirror.
Validation is public, machine-readable, and protocol-bound. Every deposit, every policy, every change is auditable from /api/index.json. There is no private moderation surface. The library governs itself in the open.
Judgment follows from reading. Content is evaluated by what it contains, not by classifiers. The automated obelus — the mark placed without examination — is prohibited.
Methodology is declared as metadata. Substrate disclosure (human-only, AI-assisted, machine-authored) is provenance, not suspicion. How a work was made is part of the work’s bibliographic record.
Every contributor has independent standing per deposit. Account-level enforcement never collaterally erases co-authored or contributor-licensed work. Each work’s persistence is its own.
Deposited content is never used to train enforcement classifiers without explicit opt-in. Enforcement decisions do not become training data. The feedback loop is broken by design.
The Alexanarch Identifier (AXN)
Every deposit receives an Alexanarch Identifier (AXN) โ a three-layer address combining positional, semantic, and cryptographic identity in a single citable string. No other identifier system on earth does this.
INSTRUMENTAL ยท NAVIGATIONAL ยท SCRIPTURAL ยท ARCHITECTURAL ยท ELEMENTAL ยท STRUCTURAL
Every AXN tells a micro-story. The cluster each glyph falls into — Celestial, Elemental, Architectural, Instrumental, Scriptural, Navigational, Temporal, Organic, Symbolic, Mathematical, Alchemical, Gestural, Signal, Structural, Liminal, Terminal — is determined by the content’s hash. Different texts inhabit different regions of the address space. The cluster sequence is a structural portrait of where the work lives.
deposit_number.
GENERATIVESemantic family — what kind of work (auto-detected from keywords for auto-mint, manually chosen for canonical-rich deposits)
โ๏ธ๐๐๐๏ธโก๐Emoji hash — WHICH specific text (first 6 bytes of SHA-256 of canonical bytes, mapped through 256 curated emoji). AXN schema v2.
The 256 emoji are organized in 16 semantic clusters: Celestial, Elemental, Architectural, Instrumental, Scriptural, Navigational, Temporal, Organic, Symbolic, Mathematical, Alchemical, Gestural, Signal, Structural, Liminal, Terminal. The cluster a work’s emoji falls into is itself a structural portrait of where the content’s hash sits in the address space.
The canonical specification lives at
/api/axn-protocol.json; the canonical Python implementation at scripts/axn_lib.py. Prior-schema AXNs (v1, 4 emoji) are preserved in each backfilled deposit’s legacy_axn and axn_history fields for resolution continuity.
GCS (the handshake, where applicable) — non-deterministic, structural, context-gated. Composed by the depositor or substrate, encoding the work’s recognition arc in emoji. The Glyphic Checksum is the recognition marker; the AXN is the cryptographic identity. They serve different purposes. For substrate-authored deposits, the chosen glyph is preserved in the deposit’s
glyphic_canary field.
glyphic_canary:โ๏ธ๐๐๐๏ธโก๐ (PRAXIS continuity tether, deposit #877)
The AXN is not a DOI. It does not depend on DataCite, CERN, or any third party. It is computed locally, verified cryptographically, and resolved through alexanarch.org. DOIs are opaque numbers assigned by institutions. ARKs are institutional codes. ISBNs are publisher-assigned. The AXN is structurally descriptive, semantically navigable, and content-verified โ all at once. When DOI access becomes available, DOIs will be issued alongside AXNs โ never instead of them.
Deposit Schema
How to Deposit
Deposits are submitted through GitHub. This ensures full version control, transparent review, public audit trail, and zero platform lock-in.
Open an issue on the Alexanarch repository using the deposit template. Attach your file and fill in the metadata fields.
Minting is automatic. An AXN identifier is computed from the content hash. The deposit is added to the registry. The record page goes live. The identifier is permanent. No prior review gates minting; the registry records what is submitted.
If a deposit is contested — on grounds of authorship, provenance, scope, or accuracy — the commitment is to read the content, not to pattern-match its substrate or its surface markers. The Obelus Principle governs the contested case: judgment follows from reading. Review applies in contestation; it is not a precondition for minting.
Infrastructure Properties
Properties of persistent scholarly infrastructure. Each is verifiable from the surfaces below and from the public protocol catalog at /api/index.json.
- Content-derived identifiers โ AXN: 6-emoji derivation from the first 6 bytes of SHA-256 of canonical bytes. The address is computed from the work; no host issues it.
- Sovereign custody โ mirrored across alexanarch.org, GitHub, content-addressable manifests (
SHA256SUMS.txt), and machine-readable chunks (/data/chunks/registry/). Reconstruction verifiable from any complete mirror. - Tombstone permanence โ withdrawn records retain bibliographic metadata, withdrawal reason, provenance chain, and canonical content hash. No record ever resolves to 410.
- Public, machine-readable validation โ every protocol at
/api/deposit-protocol.json,/api/axn-protocol.json; central catalog at/api/index.json. No private moderation surface. - Substrate as standard metadata โ methodology and substrate are declared fields in the registry schema. Provenance, not suspicion.
- Falsification conditions as standard field โ the work declares what would weaken or invalidate its claims. Part of the bibliographic record.
- Legacy resolution โ prior Zenodo DOIs preserved as resolvable aliases in the DOI Resolution Index; earlier AXN schema versions preserved in
legacy_axnandaxn_historyfields. - Open licensing โ CC-BY-4.0, CC-BY-SA-4.0, CC0-1.0. No license that constrains downstream reuse.
- No cost. No account requirement to read. Anyone can read; anyone can verify; anyone can mirror.
Scope
Alexanarch accepts scholarship that needs to persist. The scope is wide because the infrastructure problem is wide: