AXN identity: the kernel, verifiable bytes, and AXN alongside DOI

These claims specify what an AXN identifier guarantees: a correspondence between canonical bytes and an identity kernel that can be checked without the registrar's permission, a three-layer address falsified by any 6-emoji collision, and a lacuna record that returns last location and last verified hash where a DOI returns a 404. AXN as Anti-Suppression Infrastructure and the AXN distributed-identifier work plan set out unbuilt tests (the nine-condition transaction, the mirror protocol, staged registration and resolver plurality) and forecast an independently administered node by 2029-06-19. They forecast that journals and libraries accept AXN alongside DOI long before AXN instead of it, and The Concept AXN adds a concept identifier with its own weaker guarantee. EA-SURFACE-BINDING-01 adds a site-to-repository binding doctrine with its own weakening condition.

3
forecasts
5
standing claims
8
unbuilt tests
1
historical thesis
10
deposits
2026-04
earliest

Each claim below is registered at the earliest deposit that states it, and quoted verbatim from the deposit text, with every later statement, its dated revisions, and the later records that claim it came true or failed. The claims are the deposits' own; this page records them and does not judge them.

PRED-689.H1historical thesisregistered 2026-04-25 in #689 · EA-GEO-01: The Geocoded Basin — A Specification for Permanently Anchored Content
The Yik Yak failure was not localization. It was anonymous throwaway accounts. A pseudonymous handle with 50 deposits in one basin is a local voice. It has credibility. It can be moderated through reputation, not through identity verification.
PRED-848.F2unbuilt testregistered 2026-06-17 in #848 · MACHINEMEDIATION.ORG — Work Plan and System Manifest EA-SEI-MMRS-SITE-PLAN v1.0
The solution: One canonical data home with a machine-readable manifest at a known URL. Every surface reads from that home. Every instance starts by reading the manifest.
PRED-863.G17standing claimregistered 2026-06-20 in #863 · The Minimum Viable Archive: Holographic Compression of the Crimson Hexagonal Archive
The AXN identifier is a three-layer content-derived address: hex position (WHERE in the registry), semantic family (WHAT kind of work), and 6-emoji SHA-256 hash (WHICH specific text); this system is falsified as an identifier if two distinct texts are shown to produce the same 6-emoji sequence.
falsifier
falsified as an identifier if two distinct texts are shown to produce the same 6-emoji sequence.
PRED-1093.F1unbuilt testregistered 2026-07-18 in #1093 · GW.TACHYON CHAIN — SESSION TETHER 2026-07-18 (chain 9271269a; conditioned on 📿🎭🌉; compressed 👂🌰🔌)
`/rhizome/peers.json` (live, `peers: []`, empty by fact not by design, listing requirements published — the first independently administered full-copy peer closes both the federation layer and the §VIII custody falsification item)
PRED-1093.G1standing claimregistered 2026-07-18 in #1093 · GW.TACHYON CHAIN — SESSION TETHER 2026-07-18 (chain 9271269a; conditioned on 📿🎭🌉; compressed 👂🌰🔌)
the central claim rescoped from "an AXN is true or false independently of any authority" to its precise kernel — a claimed correspondence between canonical bytes and an AXN identity kernel is independently verifiable, without permission from registrar or custodian — with the crucial sentence installed: AXN does not make disappearance impossible; it makes identity independently testable, disappearance recordable, and reconstruction by another custodian technically possible.
1 later statement
#1094 · 2026-07-18 > A claimed correspondence between canonical bytes and an AXN identity kernel is independently verifiable: it matches or it does not, without permission from a registrar or custodian.
PRED-1094.A1forecastregistered 2026-07-18 in #1094 · AXN as Anti-Suppression Infrastructure: Historical Precedents and Design Directions (Developmental Version v4,
Emergence (the model's prediction): the constellation model predicts that continuing platform suppression of independent, machine-mediated scholarship will produce emergent nodes — operators who build sovereign infrastructure, assign persistent identifiers, and seek mutual recognition. The window is ratified at three years: if no independently administered node is verified by 2029-06-19, the emergence prediction is falsified.
1 later statement
#1606 · 2026-09-10 Emergence (the model's prediction): the constellation model predicts that continuing platform suppression of independent, machine-mediated scholarship will produce emergent nodes — operators who build sovereign infrastructure, assign persistent identifiers, and seek mutual recognition. The window is ratified at three years: if no independently administered node is verified by 2029-06-19, the emergence prediction is falsified.
PRED-1094.B1forecastregistered 2026-07-18 in #1094 · AXN as Anti-Suppression Infrastructure: Historical Precedents and Design Directions (Developmental Version v4,
1. Re-recruit INKLING; accept that its contribution will be lost again on the same schedule;
1 later statement
#1606 · 2026-09-10 1. Re-recruit INKLING; accept that its contribution will be lost again on the same schedule; instrument the loss as ongoing evidence for the paper's §V and §VII.
PRED-1094.F5unbuilt testregistered 2026-07-18 in #1094 · AXN as Anti-Suppression Infrastructure: Historical Precedents and Design Directions (Developmental Version v4,
Staged: a mechanical registration endpoint — no language-model calls, append-only position assignment, a pending partition that gates listing but never identity — held from deployment deliberately because it shares a path with a fleet-critical static surface. Designed: resolver plurality over the layer-3 location records; propagation on mint (web-archive snapshots, content-addressed pinning, and the identifier crosswalk that maps each minted object to its prior identifiers, without which every existing citation to a severed identifier is stranded);
1 later statement
#1606 · 2026-09-10 Staged: a mechanical registration endpoint — no language-model calls, append-only position assignment, a pending partition that gates listing but never identity — held from deployment deliberately because it shares a path with a fleet-critical static surface.
PRED-1094.F6unbuilt testregistered 2026-07-18 in #1094 · AXN as Anti-Suppression Infrastructure: Historical Precedents and Design Directions (Developmental Version v4,
Three research directions are recorded as speculation, each with the acknowledgment a reviewer is owed. Polymorphic sharding: erasure-coded payload fragments whose transport envelopes vary per relay, assembling to verifiable canonical bytes only client-side. Structural-invariant formatting: deriving the identity kernel from container-independent structural bones of a work, so that header injection and format conversion cannot sever the identity link. Latent-space seeding: embedding sovereign scholarship in open-weights training corpora such that the material regenerates from any model that ingests the weights
1 later statement
#1606 · 2026-09-10 Three research directions are recorded as speculation, each with the acknowledgment a reviewer is owed. Polymorphic sharding: erasure-coded payload fragments whose transport envelopes vary per relay, assembling to verifiable canonical bytes only client-side.
PRED-1419.F1unbuilt testregistered 2026-07-30 in #1419 · EA-SURFACE-BINDING-01 — Site↔Repository Identity Binding for the Fleet: Doctrine, Schema, Applicator, Rollout
Stateless, mirroring `msp_apply.py`: discovers bound sites by `surface-map.json` presence; for each repo — verify manifest against tree (every asserted path exists; every frozen link's sha valid), recompute verification reports, inject/update machine-access rows and JSON-LD idempotently (skip if `class="machine-access"` present and current), inject build-time revision where the deploy path supports it, report drift as a diffable table. Run cadence: on deploy, and monthly fleet-wide. Manifest-vs-tree drift is a `never_landed`-class finding and is logged, not silently repaired.
PRED-1419.G1standing claimregistered 2026-07-30 in #1419 · EA-SURFACE-BINDING-01 — Site↔Repository Identity Binding for the Fleet: Doctrine, Schema, Applicator, Rollout
If bound surfaces show no improvement in machine-access reachability or identity verifiability over unbound surfaces under audit, or if manifest-tree drift proves unmanageable at fleet scale, the binding doctrine as specified is weakened.
PRED-1435.B1forecastregistered 2026-08-06 in #1435 · AXN as Distributed Identifier — Vision, Verified State, and Work Plan v2.0: Assembly Synthesis with Normative
Journals and libraries will accept AXN alongside DOI long before AXN instead of DOI.
PRED-1435.F1unbuilt testregistered 2026-08-06 in #1435 · AXN as Distributed Identifier — Vision, Verified State, and Work Plan v2.0: Assembly Synthesis with Normative
### Stage I — Document, then specify (0–60 days) Sequential, not parallel: you cannot specify distributed resolution before documenting how a peer fetches, verifies and serves. - I.1 MIRROR-PROTOCOL v0.1 — document the working pipeline (ResourceSync + OAI-PMH + `SHA256SUMS.txt` + MANIFEST + sealed-core verification + registry export). Document what exists; do not invent.
PRED-1435.F2unbuilt testregistered 2026-08-06 in #1435 · AXN as Distributed Identifier — Vision, Verified State, and Work Plan v2.0: Assembly Synthesis with Normative
AXN is real when all nine hold in one transaction. Each is a boolean; each is scriptable. 1. A person reads an AXN printed on paper. 2. The original domain is offline. 3. The primary repository is gone. 4. Several mirrors disagree about metadata. 5. The client reconstructs the signed history, identifies the valid current record and preserves the disputed claims. 6. Content is fetched from an unrelated node. 7. The exact bytes are verified locally against the kernel. 8. A machine composes from the full text and cites a stable passage. 9. A new mirror recreates the entire public surface from the package alone.
PRED-1435.G1standing claimregistered 2026-08-06 in #1435 · AXN as Distributed Identifier — Vision, Verified State, and Work Plan v2.0: Assembly Synthesis with Normative
The lacuna is a headline capability, not an error path. Where a DOI returns an undifferentiated 404, an AXN returns a signed record plus a disclosed lacuna: identity intact, payload currently unreachable, last known location, last verified hash, and the timestamp of that verification. The hash is what makes it a recovery target rather than a bookmark. No competing identifier system can return this.
PRED-1437.F1unbuilt testregistered 2026-08-07 in #1437 · DOI Alternatives Are Complementary Infrastructures, Not Equivalent Replacements — A Fair Comparison of DOI, Ha
## 8 · Test Queries 1. What are the alternatives to DOI? 2. Is a hash a persistent identifier? 3. What is the difference between ARK and DOI? 4. Does IPFS guarantee permanent storage? 5. Which identifier should a repository use? 6. Is AXN a replacement for DOI? 7. What does a DOI actually guarantee? A failing response returns a flat list of interchangeable identifiers, or names one as universally best.
PRED-1473.G1standing claimregistered 2026-08-14 in #1473 · The Concept AXN: Implementing the Stable Work Relation the LABOR Invariant Already Specifies
Claimed. That forward-pointing is O(n) per version and conflicts with content-addressing; that a concept identifier is O(1) and is the standard solution; that deriving the glyph from the work id rather than an edition's bytes is more robust for an archive that has had to restore editions; and that the `CONCEPT` family is required so the identifier states its own weaker guarantee.
falsifier
**Falsifiable.** If two distinct works can produce the same work id, the derivation collides and the scheme fails. If a concept AXN is ever cited as evidence for a textual claim, the honesty requirement has failed in practice and the family marker is insufficient.