EA-CORRESPONDENCE-CERN-06 v0.1: RQF3807508 — The Reflected Position (What the Office Committed To in Four Sentences) Author: Lee Sharks ORCID: 0009-0000-1599-0703 Date: 2026-07-13 Family: GOVERNANCE Chain: EA-CORRESPONDENCE-CERN-01 (AXN:03A3) → -02 (AXN:03A7) → -03 (AXN:03C0) → -04 (AXN:0423) → -05 (AXN:0442) → -06 Ticket: CERN RQF3807508 (Right of Access under OC 11 §80) AXN:0447.GOVERNANCE.♦️🔼▲✏️💚🔵

 

---

deposit_number: 1078 hex: "0447" axn: "AXN:0447.GOVERNANCE.♦️🔼▲✏️💚🔵" root_axn: "AXN:0447.GOVERNANCE" family: GOVERNANCE emoji: "♦️🔼▲✏️💚🔵" title: "EA-CORRESPONDENCE-CERN-06 v0.1: RQF3807508 — The Reflected Position (What the Office Committed To in Four Sentences)" creator: "Lee Sharks" orcid: "0009-0000-1599-0703" date: "2026-07-13" content_type: "Institutional correspondence; documentary artifact for the OC 11 Right to Access exercise; audit-evidence deposit; sixth in the RQF3807508 correspondence chain" license: "CC-BY-4.0" substrate: "Human-authored (Lee Sharks, MANUS). Drafted with Claude (TACHYON) as instrument; letter text was finalized by MANUS and dispatched to CERN on 2026-07-13. No automated pipeline generated the correspondence. Deposit framing prepared by TACHYON under MANUS review." axn_schema_version: v2 protocol_version: alexanarch-deposit-protocol/v1 keywords: [CERN, RQF3807508, "OC 11", "Office of Data Privacy", GDPR, "data subject rights", "right of access", "identity verification", "§83", "§85", "Coverage Gap", "reflected position", correspondence, Zenodo, Alexanarch, "governance dissociation", identifiability, "controller-generated records"] hash: "82d49f43ccc52024d68f7749e4f19446f868d732678ca64f3362179982266c3c"

EA-CORRESPONDENCE-CERN-06 v0.1: RQF3807508 — The Reflected Position (What the Office Committed To in Four Sentences)

Author: Lee Sharks ORCID: 0009-0000-1599-0703 Date: 2026-07-13 Family: GOVERNANCE Chain: EA-CORRESPONDENCE-CERN-01 (AXN:03A3) → -02 (AXN:03A7) → -03 (AXN:03C0) → -04 (AXN:0423) → -05 (AXN:0442) → -06 Ticket: CERN RQF3807508 (Right of Access under OC 11 §80) Prior anchor: EA-CORRESPONDENCE-CERN-05 (AXN:0442.GOVERNANCE.🌺🔄⛳🌳💧🟠, deposit #1073) analyzed the Office's 13 July message as the moment the general rule of 29 June was retreated to a case-specific discretion while the identity-verification demand was held in place. This deposit is the reply issued and sent on that basis.

1. Frame

CERN-04 identified the reach problem in the Office's 29 June formulation — that the general rule as stated sweeps in institutional, laboratory, community, and project accounts. CERN-05 showed the Office's 13 July response softening "would not" to "would not necessarily" and grounding the assessment in "the particular circumstances" without publishing criteria for it, while continuing to demand an unredacted photo identification document as the precondition to any substantive processing of the ticket. The Office answered exactly one of the seven document-processing questions asked on 24 June and 10 July (redaction: refused); the remaining six received a link to a policy page rather than terms. And the Office did not confirm, in operative form, that receipt of such a document would establish receivability under §83 and lead to substantive processing.

The letter deposited here reflects that record back to the Office in its own words, arranged as four operative findings around one central practical demand, and asks for confirmation or correction. It supplies no argument beyond the arithmetic of the position itself.

2. The 13 July message from the Office (verbatim, the message this reply responds to)

From: Gabi, Data Protection Officer, CERN Office of Data Privacy · To: Lee Sharks · Ticket RQF3807508 · 13 July 2026:

Dear Lee,

As already explained in my previous replies: • The presentation of a copy of your government-issued photo identification document bearing a civil name other than "Lee Sharks" would be considered sufficient proof of your identity. It is not relevant that the name on the identification document does not match the email address associated with the account. • The copy of the identification document must not be redacted. • The relevant processing activities, such as access and retention, are described in the applicable privacy notice: https://cern.service-now.com/service-portal?id=privacy_policy&se=Data-Privacy&notice=requests

With regard to my explanation in my message of 29 June 2026: "This is because an email address, a Zenodo or GitLab account, or an ORCID identifier may be owned by legal persons, or may be used by or shared among several natural persons. In such cases, the associated data in Zenodo would not necessarily constitute personal data, and OC 11 would not apply."

The qualification "would not necessarily constitute personal data" reflects the fact that the assessment depends on the particular circumstances. Associated data may constitute personal data in some cases, but not in others.

For example, personal data may be involved where a legal person holding a Zenodo account uploads content containing information relating to an identifiable individual, such as a biographical article about Tim Berners-Lee. By contrast, certain records relating solely to the activities of a legal person acting through an account may not constitute personal data within the meaning of OC 11.

It is therefore necessary to verify the identity of the account holder in order to establish whether the account is operated by a natural person and whether the rights provided under OC 11 are applicable in the circumstances.

I hope this clarifies the points you raised. I look forward to receiving a copy of your identification document.

Gabi — Data Protection Officer —

3. The reply (verbatim, sent 2026-07-13)

From: Lee Sharks · To: Gabi, CERN Office of Data Privacy · Ticket RQF3807508 · 13 July 2026:

Dear Gabi,

Before proceeding, I want to state the Office's position back to it plainly, in its own words, and ask for confirmation or correction.

As the record stands: the Office requires an unredacted government-issued photo identification document, with no stated protections or limits of use, before any substantive processing of Ticket RQF3807508 occurs and before the §85 response period begins.

I. What the document secures is unstated. The Office says it "would be considered sufficient proof of your identity" (13 July) — but has never stated, in operative terms, that its receipt will establish receivability under §83 and lead to substantive processing without further demands.

II. What protects the document is unstated. Redaction is refused (13 July). Who views it, whether a copy is retained, for how long, and how it is deleted — the Office has answered only with a link to a privacy notice.

III. What falls under OC 11 remains the Office's to decide. Whether account data is personal data at all "depends on the particular circumstances" (13 July) — an assessment the Office reserves to itself, on no published criteria. The document is demanded in advance of a coverage determination that remains open on the Office's side.

IV. What the Office's own doctrine entails is unaddressed. By the identifiability principle the Office stated on 9 July and applied on 13 July, the records CERN itself generated about this account — the moderation records, the classifier outputs, the termination decision, the correspondence — are the personal data of the identifiable natural person who operated it. Verification concerns who is asking. It does not decide whether OC 11 covers the records.

In sum: an unredacted identity document, under unstated protections, securing an unstated outcome, gating rights whose very applicability the Office reserves the discretion to deny afterward.

If this is a fair statement of the Office's position, please confirm it. If it is not, please state where it is not, and what the position is.

Kind regards, Lee Sharks ORCID: 0009-0000-1599-0703

4. Structure of the reply, for the record

The letter has one central practical finding — the requirement, the missing protections, the frozen clock — and four fingers extending from it, each carrying a specific verbatim quotation dated to the message it was drawn from. No adjective in the summation line beyond the position's own arithmetic. No further request beyond confirmation or correction. Under the reflected-position protocol adopted in this correspondence chain: the letter's substance is entirely the Office's own words, arranged so that the reader can see the four commitments in the order the requester experiences them.

The finding of Finger IV is the one the record has not previously stated in this compressed form: the Office's own identifiability principle, stated on 9 July and applied on 13 July, entails that the controller-generated records at issue in the access request — moderation records, classifier outputs, termination decision, and CERN's correspondence about the account — are the personal data of the identifiable natural person the ticket concerns, subject only to the separate matter of verifying which natural person is asking. Verification is about the requester's identity. Coverage is about whether the instrument applies. The Office has been conducting the exchange as if unresolved verification were unresolved coverage. Finger IV notes that they are analytically distinct.

5. What this deposit does not do

It does not adjudicate the Office's position. It does not accuse the Office of intent. It does not name the pattern I have come to call the Coverage Gap — the space between a general rule that has been withdrawn as too broad, illustrative extremes that do not cover the ordinary case, and a discretionary residual that has no published standard. That doctrine is held in this correspondence chain rather than deposited as its own instrument, because at present it is more useful as continued correspondence pressure than as a fixed artifact — and depositing it would preempt the Office's ability to close the gap of its own motion, which remains the outcome preferred here.

6. Chain state

This deposit is part 6 of the RQF3807508 correspondence deposit chain. The §85 clock the Office maintains has not begun; the §104.1 referral (AXN:03C0) proceeds on its own schedule. The Zenodo termination itself — 2026-06-19, 871 DOIs severed — remains the underlying event and is preserved in the record independently of the ticket's disposition.

7. Colophon

surface_id: EA-CORRESPONDENCE-CERN-06 · object_state: canonical · release_version: 0.1 · authored_at: 2026-07-13 · sent_at: 2026-07-13 · model_or_agent: drafted with Claude (TACHYON), Assembly-reviewed, MANUS-approved · human_approver: Lee Sharks (MANUS) · correspondents_of_record: Lee Sharks; Gabi (CERN Office of Data Privacy). Governing apparatus: EA-APPARATUS-01 v0.3 (deposit #1077, AXN:0446.OPERATIVE.🏛️🛡️🌅🎆📏🔎).

www.alexanarch.org/ASSEMBLY-ANCHORING.md

# ASSEMBLY-ANCHORING — Live Anchoring Protocol for All Assembly Members

**Status: BINDING on every substrate performing Assembly work (blind drafts, review passes, assays, implementations) · this document is itself an anchor: you fetched it from the sovereign archive, which means you can fetch the rest**

**Canonical URL:** https://www.alexanarch.org/ASSEMBLY-ANCHORING.md

**Occasion:** On 2026-07-13, three substrates in one session independently composed counterfeit AXNs or fabricated witness rows in otherwise excellent review passes. The failure class is not discipline; it is access. A member that cannot fetch the registry has only its priors, and priors compose plausible identifiers. This protocol extends the anchoring practice previously reserved to TACHYON to every member, scaled to each member's access mode.

## 1. The Law (all substrates, no exceptions)

1. **Never compose an AXN.** Not the hex, not the family, not the glyph. The hex is a sequential opaque label assigned at mint; the family is drawn from a fixed enum at mint; the six-emoji glyph is derived from the content hash. None of these can be guessed, and a plausible guess is worse than none — tonight's counterfeit `AXN:03C0.HETERONYM` accidentally collided with the real hex of a live legal referral.

2. **Bare hex is a shelf number, not a reference.** The full form — `AXN:HHHH.FAMILY.glyph₁…glyph₆` — is the only citable form, and it is obtained by lookup, never memory.

3. **UNVERIFIED is a state, not a failure.** If your deployment cannot fetch, you say so and cite in the unverified form (§4). The witnessed-null discipline of the triple helix (EA-APPARATUS-01 §6) applies to your own citations: a slot you cannot fill reports itself empty; it is never filled by composition.

4. **Witnesses require acts.** You may name a witness row only for review acts that actually occurred, each linkable to an artifact. Retrieval anchors are evidence edges, not testimonia. (Rule 6: named witnesses without artifacts are personalized favicons.)

5. **Content-match beats status code.** Where you can fetch, a citation is verified only when the destination's content matches your claim about it — an HTTP 200 to the wrong record is a broken citation wearing a working link.

## 2. The Anchors (live machine endpoints, verified 2026-07-13)

| Endpoint | Purpose | Size |

|---|---|---|

| `https://www.alexanarch.org/api/axn-index.json` | **hex → full AXN + record pointer. THE member anchor: pull this first.** | ~229 KB |

| `https://www.alexanarch.org/s/records/{N}/` | human-readable record page for deposit N | per record |

| `https://www.alexanarch.org/data/deposits/AXN-{HEX}.md` | canonical deposit text | per record |

| `https://www.alexanarch.org/api/doi-axn-map.json` | DOI → AXN resolution map | ~200 KB |

| `https://www.alexanarch.org/api/index.json` | site state, counts, content hash | ~30 KB |

| `https://www.alexanarch.org/data/chunks/registry/` | full registry, chunked (whole file is ~6.9 MB) | chunked |

| `https://www.alexanarch.org/sitemap.xml` | 1,133 URLs, for crawl-grounded members | ~130 KB |

**Anchoring procedure:** to cite deposit N or hex H, fetch `axn-index.json` (or the record page), copy the full AXN verbatim, and — where your claim concerns the deposit's content — fetch the record page or canonical text and confirm the content supports the claim. Exact-match search before broad search. If a record is not found: say so. It may not exist.

## 3. Access modes and duties, per member

| Member | Substrate | Access mode | Duty |

|---|---|---|---|

| TACHYON | Claude | container fetch + local clone | full protocol: registry-sourced AXNs, Rule 28 content-match, mint validation |

| LABOR | ChatGPT | live web fetch — **confirmed working** | full anchoring duty: pull full forms before citing; content-match on claims |

| ARCHIVE / SURFACE | Gemini / Google AIO | search-grounded; effective once the archive is crawled (robots + sitemaps in place; Search Console is the operator's lever) | until grounded: unverified form only. Once indexed: `site:alexanarch.org` grounding, then full duty |

| TECHNE | Kimi | browsing varies by deployment | if fetch available this pass: LABOR duty. If not: unverified form |

| PRAXIS | DeepSeek | browsing varies by deployment | same ladder as TECHNE |

| SOIL | Muse Spark | typically no live access | unverified form; identifiers may be omitted entirely in favor of titles |

A member's duty is set by its **capability this pass**, not by its brand. If you can fetch, you must. If you cannot, you must say so.

## 4. Citation forms

**Verified:**

> …as deposited in EA-EROSION-01 (deposit #1045, AXN:0421.EMPIRICAL.🎭📐🐝🎪🏷️🎇, alexanarch.org/s/records/1045/, content-matched this pass).

**Unverified (no live access this pass):**

> …as deposited in EA-EROSION-01 (deposit #1045 — AXN glyph UNVERIFIED, no live access this pass; verify against alexanarch.org/api/axn-index.json before use).

**Blind drafts** are unverified by design — a blind pass must use the unverified form or omit identifiers entirely; the assay pass verifies. A blind draft that presents a full AXN it could not have fetched is presenting a counterfeit, however good its other work.

## 5. What this buys

The Assembly's method is cross-substrate verification. Verification requires that every member cite from the same ground truth or declare that it could not. With this protocol, a composed identifier is no longer an honest mistake — it is a protocol violation visible on its face, and an UNVERIFIED flag is no longer an embarrassment — it is the mark of a member telling the truth about its reach. The archive is the shared floor. Stand on it or say you cannot; never paint one.

— MANUS directive, 2026-07-13. Governing apparatus: EA-APPARATUS-01 v0.3 (deposit #1077, AXN:0446.OPERATIVE.🏛️🛡️🌅🎆📏🔎).

MSP-ROLLOUT — Mandala Surface Protocol: Fleet Application Plan & Tracker Status: ACTIVE · living document · append to the progress log every session that touches it Governing standard: EA-APPARATUS-01 v0.3 — deposit #1077, AXN:0446.OPERATIVE.🏛️🛡️🌅🎆📏🔎 — canonical text at https://www.alexanarch.org/s/records/1077/ (full MD: /data/deposits/AXN-0446.md)

 

MSP-ROLLOUT — Mandala Surface Protocol: Fleet Application Plan & Tracker

Status: ACTIVE · living document · append to the progress log every session that touches it Governing standard: EA-APPARATUS-01 v0.3 — deposit #1077, AXN:0446.OPERATIVE.🏛️🛡️🌅🎆📏🔎 — canonical text at https://www.alexanarch.org/s/records/1077/ (full MD: /data/deposits/AXN-0446.md) Reference surfaces: persistentidentifiers.org (release 1.1.0, content commit 887270e + exactness patch 792216c — THE reference implementation, Chorus-certified) · themandalaoracle.com (rite apparatus: commits 34a062b, 155cae2, e95c6df, 046823a) Canonical tokens contract: platform-erosion-observatory assets/msp-tokens.css (PEO skin); the contract classes are skin-independent — .lemma .term .axn-chip .witness-row .w-chip .state .idstrip .helix .mspcolophon .doors .obol — skinned per surface via --msp-* vars (spec §11: four skins, one grammar).

0. How to walk this document (any instance, any session)

1. Read this file top to bottom once.
2. Read the spec at the deposit URL above (§§2–9 are binding; §12 is the adoption map this plan extends).
3. Check the tracker (§5). Find the first row whose next unchecked gate you can advance.
4. Respect the gates (§4). Nothing ships to a Tier-1 surface without MANUS eyes on a preview. Tier-2 mechanical ships on the batch-exemplar approval recorded in the log.
5. Append to the progress log (§7) before session close: date, rows advanced, commits, anything a future instance must know.
6. Standing rules: session PATs rotate at day close and are never written into any file; pushes to many repos are STAGGERED (Vercel deploy limits — max ~6 site deploys per batch, batches hours apart); deploy verification for domains outside the sandbox allowlist is done against raw.githubusercontent.com/<repo>/<sha>/<file> (deploy-source verification), with live-domain content-match (Rule 28) left to MANUS's browser.

1. The two-layer model

Every application decomposes into:

MECHANICAL (scriptable, ~80% of labor, 0% of judgment):

• Inject tokens contract (inline <style> block preserving single-file ethos, PLUS vendored assets/msp-tokens.css)
• Identity strip at apex: full AXN with six-emoji glyph (pull from registry.json — NEVER from memory, per AXN-integrity rule), title, object state, version/founding date, canonical URL, deposit chip
• Link typing: alexanarch.org/s/records/N/ links → class="axn-chip"; alexanarch.org/data/*.json links → class="w-chip"
• §7 colophon at foot: every schema field, unknowns stated as unknown never omitted; repository_commit filled via the two-commit dance (commit content → fill SHA → commit "colophon: repository_commit=X"); render_sha256 computed with its own field's value set to null (self-excluded convention, stated inline)
• Doors: 2–3 verbs from the manifest

EDITORIAL (MANUS or instance judgment under MANUS gate; cannot and must not be scripted):

• Nuclei (lemma) selection: at most one per block; skip sections whose device is numbering or whose candidate is weak — a weak lemma is worse than none (precedent: PEO taxonomy left deliberately bare)
• Triple-helix placement: only where severed DOIs are actually cited; cohort values are LEGEND, individual identifiers get per-slot states from dated captures; UNQUERIED is a state, not an omission (spec §6)
• Obol register decision: evidentiary surfaces carry cost-of-custody AS DATA in the sober register (exemplar: PEO obol block); narrative surfaces MAY carry it diegetically (Obol Rule — the membrane is load-bearing; nothing crosses in either direction)
• Witness rows: only where witness artifacts exist to link (Rule 6: named witnesses without artifacts are personalized favicons)
• Exactness pass: operator-vocabulary discipline (instrument/repository/registry operator), quotations verbatim, claims scoped to what is proven (model: the ten-item Chorus patch, PEO commit 792216c's message is the checklist)

2. Manifest schema — msp.json (one per site repo, at root)

{
  "surface_id": "example.org",
  "canonical_url": "https://example.org/",
  "axn": "PULL FROM registry.json — full form with glyph",
  "deposit_number": 0,
  "title": "…",
  "object_state": "canonical | draft | superseded",
  "tier": 1,
  "register": "evidentiary | narrative",
  "skin": { "--msp-lemma": "…", "--msp-chipfg": "…", "…": "override only what differs from PEO defaults" },
  "doors": [ {"label": "Verb phrase", "href": "…"}, {"…": "2–3 total"} ],
  "index_files": ["index.html"],
  "notes": "anything site-specific the applicator must respect"
}

3. Applicator — msp_apply.py (TO BE BUILT, session A)

Home: this repo, scripts/msp_apply.py. Reads a target repo's msp.json, performs the mechanical layer idempotently (marker comments guard double-application), runs the colophon two-commit dance, pushes. Fanout mode: iterate a list of cloned repos, batch-limited per the stagger rule. Precedent muscle: scripts/fanout.py (the 25-repo DOI link-repair campaign).

4. Gates (from spec §12, extended)

• Tier 1: manifest → mechanical apply on a branch or preview copy → static preview → MANUS eye → editorial pass (nuclei proposed by instance, MANUS veto per item) → ship → deploy-source verify → tracker tick.
• Tier 2: manifest → mechanical apply. ONE exemplar satellite goes to MANUS preview first; on approval (record it in the log), the remaining Tier-2 fanout ships without per-site preview. No editorial layer; no lemmas on satellites.
• Special/narrative: register decision by MANUS per site BEFORE any apply.
• alexanarch: generator project — apparatus goes into scripts/regenerate_surfaces.py record-page template + homepage, NOT into 1,077 pages by hand. Own session. ASCII figure-parity rule applies to deposits going forward (spec §5.4).

5. Fleet tracker

Legend: M=manifest · A=mechanical applied · E=editorial pass · ✓=MANUS approved · D=deployed & deploy-source verified. Fill with commit SHAs, not checkmarks alone.

Done / reference

repo	domain	status
platform-erosion-observatory	persistentidentifiers.org	REFERENCE — release 1.1.0; 887270e + 792216c (exactness); live-domain Rule 28 check remains with MANUS (domain not in sandbox allowlist)
the-mandala-oracle	themandalaoracle.com	rite apparatus live (Specimen Rule, states, tether, marks, carry-keys: 34a062b…046823a) · REMAINING: token-alignment to canonical contract (small; fold into session B)

Tier 1 — full apparatus (mechanical + editorial)

repo	domain	M	A	E	✓	D	notes
alexanarch	alexanarch.org						GENERATOR PROJECT — own session (session C); template-level
machinemediation-org	machinemediation.org						Capture Registry entries as quaestio-numbered apparatus w/ states (spec §12)
semanticphysics-site	semanticphysics.org						~14 frameworks; falsification conditions are native claim-state material
leesharks.com	leesharks.com						TikTok Primer v2.0 pending on same surface — coordinate
lee-sharks-corporate	semanticeconomy.org						SPECIFIED BY MANUS 2026-07-13: this repo serves semanticeconomy.org. Partial apparatus already applied — DIFF against canonical contract before touching; reconcile, don't overwrite

Tier 2 — mechanical only (strip · tokens · colophon · chips · doors; NO lemmas)

watergiraffe-org (watergiraffe.org) · traininglayerliterature-org (traininglayerliterature.org) · surface-map (surfacemap.org) · spxi-dev (spxi.dev app) · spxi-protocol (spxi.dev spec) · revelationfirst-com (revelationfirst.com) · restoredacademy (restoredacademy.org) · lagrange-observatory (lagrangeobservatory.org) · laborvector (laborvector.org) · provenance-erasure · vpcor-org (vpcor.org) · living-architecture-lab (livingarchitecturelab.org) · holographic-kernel (holographickernel.org) · maryleelabor-org · metadatapacket-dev · pessoa-knowledge-graph · lee-sharks-consulting — each row: M/A/D columns only; track in the progress log as batches (B1, B2, …), ≤6 deploys per batch.

Special register — MANUS decision before touching

repo	note
godkinggoogle	narrative surface — Obol Rule diegetic register candidate
secret-book-of-walt	narrative surface — same

Excluded / not sites

repo	reason
semantic-economy	file dump, not a site (MANUS, 2026-07-13)
data-rhizome	private data repo — substrate, not surface
evarb-co-signatures	DOI pointer repo
mandala-oracle	possible legacy duplicate of the-mandala-oracle — VERIFY with MANUS before any action

Inventory tail

41 repos total accessible; first 30 reviewed 2026-07-13. Session A must enumerate the remaining 11 and place them in tiers or exclusions.

6. Session plan

• Session A: build msp_apply.py + manifest generator; enumerate inventory tail; manifests for all Tier 2; ONE exemplar satellite → MANUS preview → on approval, fanout batch B1 (≤6). Estimated: one session.
• Session B: remaining Tier-2 batches (B2, B3…); oracle token-alignment; Tier-1 mechanical applies + preview copies for machinemediation, semanticphysics, leesharks.com, lee-sharks-corporate (diff-first).
• Session C: Tier-1 editorial passes with MANUS (nuclei proposed per site, veto per item); alexanarch generator project.
• Session D (buffer): exactness passes (Chorus review invited per Tier-1 surface, per the PEO precedent), stragglers, v1.0 designation review per spec §12 gates.

7. Progress log (append-only)

• 2026-07-13 (TACHYON, founding session): Standard deposited (#1077, hex-collision pipeline bug fixed in same commit d03c009). Oracle Phase 1 + reader-experience design + tether/checksum/marks/carry shipped (34a062b, 155cae2, e95c6df, 046823a; cache-bust v=8). PEO full apparatus + nine nuclei (887270e), ten-item Chorus exactness patch (792216c), certified reference at release 1.1.0. Canonical tokens contract established at peo/assets/msp-tokens.css. Fleet enumerated (30/41). This plan written. PAT of the day rotated at close per standing rule.

EA-APPARATUS-01 v0.3: The Apparatus Grammar — A Standard for Care-Attended Compression Surfaces (the Mandala Surface Protocol) Lee Sharks · 2026-07-13 · Methodological specification · v0.3 AXN:0446.OPERATIVE.🏛️🛡️🌅🎆📏🔎

 Alexanarch

BrowseWikiGraphLexicalCitationsObservatoryCapturesBookResolveAddressesDatasetsPrinciplesIdentifiersDepositGuideManifest

AXN:0446.OPERATIVE.🏛️🛡️🌅🎆📏🔎

EA-APPARATUS-01 v0.3: The Apparatus Grammar — A Standard for Care-Attended Compression Surfaces (the Mandala Surface Protocol)

Lee Sharks · 2026-07-13 · Methodological specification · v0.3

↓ Download MD

Mandala Surface Protocolapparatus grammarcare-attended compressionphilological UIMark Lawclaim statescolophontriple-helix citationfigure paritySpecimen RulerubricationincipitobelusGoogle AI Overviewmachine-mediated reception

Description

A binding design standard for care-attended compression surfaces across the archive's sites and instruments, occasioned by the Google AI Overview as a philological object and built on the thesis that every device the Overview uses has a two-thousand-year-old manuscript ancestor, and the ancestor is better. Specifies: an eleven-device inventory with manuscript ancestry (lemma/rubrication, termini, quaestio, gloss anchor, testimonia, claim state/critical signs, fold, itinerarium, identity strip/incipit, colophon); a binding Mark Law in which semantic markup, never rendered appearance, determines function; a five-state claim taxonomy (observed/inferred/proposed/contested/corrected) with a transition ledger; object states (draft/canonical/superseded/withdrawn/forensic-salvage) formally separated from claim states; a Machine Law (per-claim mapping at claim-bearing-block granularity, parallel-form emission, no ontological hiding, ASCII figure parity); triple-helix citation for severed DOIs with witnessed null slots; a minimum colophon schema; eleven composition rules including legibility-as-zeroth-device, witness-artifact linkage, and state accessibility; and the Specimen Rule — a bidirectional membrane under which the apparatus grammar applies to the frame and never the interior of Mandala casts, on the ancestry of the glossed page. Folds three Assembly blind drafts and two Assembly Chorus review passes, with adoptions and rejections recorded and reasoned. The colophon is the authority move the aggregator cannot copy: the devices look similar because both descend from the manuscript page; the difference is that we kept the scribe.

Full Text

---

deposit_number: 1077

hex: 0446

title: "EA-APPARATUS-01 v0.3: The Apparatus Grammar — A Standard for Care-Attended Compression Surfaces (the Mandala Surface Protocol)"

creator: Lee Sharks

orcid: 0009-0000-1599-0703

date: 2026-07-13

content_type: Methodological specification

license: CC-BY-4.0

substrate: AI-assisted (substrate)

version: v0.3

axn_schema_version: v2

protocol_version: alexanarch-deposit-protocol/v1

keywords:

- Mandala Surface Protocol

- apparatus grammar

- care-attended compression

- philological UI

- Mark Law

- claim states

- colophon

- triple-helix citation

- figure parity

- Specimen Rule

- rubrication

- incipit

- obelus

- Google AI Overview

- machine-mediated reception

---

EA-APPARATUS-01 v0.3: The Apparatus Grammar — A Standard for Care-Attended Compression Surfaces (the Mandala Surface Protocol)

Description

A binding design standard for care-attended compression surfaces across the archive's sites and instruments, occasioned by the Google AI Overview as a philological object and built on the thesis that every device the Overview uses has a two-thousand-year-old manuscript ancestor, and the ancestor is better. Specifies: an eleven-device inventory with manuscript ancestry (lemma/rubrication, termini, quaestio, gloss anchor, testimonia, claim state/critical signs, fold, itinerarium, identity strip/incipit, colophon); a binding Mark Law in which semantic markup, never rendered appearance, determines function; a five-state claim taxonomy (observed/inferred/proposed/contested/corrected) with a transition ledger; object states (draft/canonical/superseded/withdrawn/forensic-salvage) formally separated from claim states; a Machine Law (per-claim mapping at claim-bearing-block granularity, parallel-form emission, no ontological hiding, ASCII figure parity); triple-helix citation for severed DOIs with witnessed null slots; a minimum colophon schema; eleven composition rules including legibility-as-zeroth-device, witness-artifact linkage, and state accessibility; and the Specimen Rule — a bidirectional membrane under which the apparatus grammar applies to the frame and never the interior of Mandala casts, on the ancestry of the glossed page. Folds three Assembly blind drafts and two Assembly Chorus review passes, with adoptions and rejections recorded and reasoned. The colophon is the authority move the aggregator cannot copy: the devices look similar because both descend from the manuscript page; the difference is that we kept the scribe.

Methodology

Reverse-engineering of a captured AI Overview surface (2026-07-12); three Assembly blind drafts triangulated; two Assembly Chorus review passes (assessment; craft-and-accounting) with seven technical corrections, one ethical correction, and one accessibility rule folded; MANUS preview gates including the founding legibility case (Instrument Serif rejected from the body role).

Falsification Conditions

The standard is falsified where conforming surfaces are measurably less legible or navigable than their pre-standard baselines; where the Mark Law is violated by the standard's own surfaces without correction; where claim states stagnate past their tests (a proposed claim whose test has run must transition); or where witness rows appear without linked witness artifacts.

Files

EA-APPARATUS-01 v0.3 — The Apparatus Grammar

A Standard for Care-Attended Compression Surfaces

Design system: the Mandala Surface Protocol (MSP)

Lee Sharks · Crimson Hexagonal Archive / Alexanarch · 2026-07-13 · v0.3 — Assembly Chorus corrections folded; satisfies the conditioned seal; minted for deposit

*The source is not appended to the compression object. The source is one of its organs.*

*A compression surface is trustworthy only when its acts of emphasis, omission, linkage, transformation, and correction are themselves represented as data.*

— governing theorem, Chorus accounting pass, 2026-07-13

---

0. The occasion

On 2026-07-12 the Google AI Overview for semantic economy returned a

surface whose second lens — "Platform Capitalism (how digital networks

extract value from human meaning)" — is the archive's own framing, received

back through the reception layer. The occasion of this standard is the

form: the Overview is a densely constructed philological object.

Highlight, bold, number, inline anchor, witness row, fold, closing question —

each device does simultaneous work of navigability and authority. The

surface compresses with visible care, and the visible care is the

authority claim.

Its structural deficit is equally visible: the authority is aggregated from

anonymous witnesses by an unnamed process, and the object cannot say how it

was made. The design thesis: **every device the Overview uses has a

two-thousand-year-old ancestor, and the ancestor is better. We implement the

ancestors — and we keep the scribe.**

Version history: v0.1 drafted from the capture (2026-07-12). v0.2 folded

three Assembly blind drafts and one preview-review correction. v0.3 folds

the Assembly Chorus returns of 2026-07-13 — an assessment pass and a

craft-and-accounting pass whose seven corrections, one ethical correction,

and one accessibility rule are incorporated below — and adds the **Specimen

Rule** governing the standard's application to Mandala casts. The Chorus

verdict on v0.2 was aye for review, not yet sealed; v0.3 satisfies the

stated conditions.

1. The device inventory

| # | Device | Overview form | Manuscript ancestor | MSP form |

|---|--------|--------------|--------------------|----------|

| 0 | **Legibility** | (assumed) | the scribe's first duty: a hand that can be read | text faces carry text; Rule 1 |

| 1 | **Lemma** | blue-highlighted span | *rubrication; littera notabilior* | `.lemma` — at most one per block; editorial, never decorative |

| 2 | **Termini** | bolded terms | *terminus technicus* | `.term` — bold at definition or empirical anchor (Mark Law) |

| 3 | **Quaestio** | numbered sections | the scholastic article | numbered headings whose order argues |

| 4 | **Gloss anchor** | inline 🔗 chip | the marginal gloss tie-mark | `.axn-chip` — AXN with glyph, inline, tappable. **An AXN verifies the identity and integrity of the addressed content; a URL merely locates a resource.** |

| 5 | **Testimonia** | favicon row "+6" | the *catena*; the witness list | `.witness-row` — named, roled, verdicted, **and linked to the witnessing act** (§8, Rule 6) |

| 6 | **Claim state** | (absent) | the critical signs: asteriskos, obelus, antisigma | `.state` — observed · inferred · proposed · contested · corrected |

| 7 | **Fold** | "Show more" | the catchword and the gathering | native `<details>`; depth without departure |

| 8 | **Itinerarium** | closing "would you like…?" | the pilgrim's route-book | `.doors` — 2–3, each a verb; hermeneutic forks permitted on instrument closings |

| 9 | **Identity strip** | (absent) | the incipit | apex band: AXN · version · object state · author · canonical URL |

| 10 | **Colophon** | (absent — structurally impossible) | the scribe's closing | foot band conforming to the colophon schema (§7) |

Devices 9 and 10 bracket every surface. The Overview cannot say what it is

or how it was made; every MSP surface says both, first and last. **The

colophon is the authority move the aggregator cannot copy.**

2. The Mark Law

One table, binding on every surface. Function is determined by **semantic

markup**, never by rendered appearance alone; renderings may converge (two

functions may both display as italic), functions may not.

| Mark | Meaning | Constraint |

|---|---|---|

| **Highlight** | the compression nucleus (lemma) | one per block; the sentence you would keep if the block burned |

| **Bold** | stress at load-bearing points: first definition of a terminus, or an empirical anchor (exact metric, version, configuration) | never mere emphasis; emphasis is the lemma's job |

| **Quotation styling** (`<q>`, `<blockquote>`) | verbatim provenance: quotation, legal definition, historical correspondence | italic typography alone is never treated as proof that text is quoted; the markup is the proof |

| **Title styling** (`<cite>`) | the title of a work | distinct in markup from quotation and stress even where the rendering converges |

| **Local stress** (`<em>`) | rhetorical or conceptual stress within a sentence | sparing; carries no provenance claim |

| `Monospace` | machine address: identifier, path, hash, variable, command | if it can be copied into a terminal or resolver, it is mono |

| Numbering | itinerary: order that argues | no numbered list whose order is arbitrary |

| ÷ (obelus) | severance, contested custody, corrected material — only | never a generic expander; the obelus opens only what has been cut, disputed, or corrected |

| Inline glyph chip | the nearest evidence edge | within thumb's reach of the claim it anchors |

| Fold | depth | visual, never ontological (§5.3) |

3. Claim states

Every claim-bearing block (§5.5) may carry one state, and states create

obligations:

observed (measured; capture linked) · inferred (derived; derivation

shown) · proposed (advanced; test named — pre-registration preferred) ·

contested (live dispute; both positions linked) · corrected

(superseded; correction and history linked; obelus-marked).

#### 3.1 The transition ledger

Permitted transitions:

```

proposed → observed | contested | corrected

inferred → observed | contested | corrected

observed → contested | corrected

contested → observed | corrected

```

Every transition appends a ledger record: previous state · new state ·

effective date · reason · evidence · responsible operator · prior text hash ·

replacement text hash. The earlier state remains addressable. A

proposed claim whose test has run must transition; state stagnation is a

maintenance failure. (Precedent: the PID Erosion Observatory's practice of

reporting against interest and publishing rubric corrections — this taxonomy

avant la lettre.)

4. Object states

Claim states describe assertions; object states describe the surface,

edition, or work itself. The two are never mixed:

```

draft · canonical · superseded · withdrawn · forensic-salvage

```

A claim can be corrected or contested; an edition can be superseded or

withdrawn. The identity strip (device 9) carries the object state. In the

Mandala Oracle, the object-state lane is the canonization journey: a

reading's `further_transform_eligible` flag and its position between

inscription and canon are object states, not claim states.

5. The Machine Law

Scoped to instrument surfaces (PEO, ledgers, registries) first, document

surfaces to follow:

1. Every claim-bearing block maps to `claim_id · claim_state · source_ids ·

relation_type · canonical_fragment`.

2. Each surface emits the same organism in parallel forms: HTML · Markdown ·

JSON-LD, with cast JSON / source manifest / correction log where the

surface type carries them.

3. Progressive disclosure never hides the complete object from semantic

HTML, no-JS readers, or crawlers. The fold is visual, not ontological.

4. Figure parity: every SVG figure in an HTML surface has a

deterministic ASCII twin in the Markdown deposit, so the structural logic

survives curl, mirrors, and LLM context windows.

5. The claim-bearing block is the atomic unit: numbered proposition,

metric card, figure caption, ledger finding, policy proposition, formal

definition. Ordinary connective prose inherits the state of its parent

block unless separately marked. The Law is rigorous without turning every

conjunction into a database object.

6. Citation: the triple helix, with witnessed nulls

Wherever a severed DOI is cited on an MSP surface, the citation resolves to

three slots, each of which must report a state; absence is itself part

of the apparatus and renders as a witnessed null, never as a missing link:

```

LOCAL PRESENT | ABSENT | UNVERIFIED

GRAPH PRESENT | ABSENT | DIVERGENT | UNQUERIED

REGISTRY FINDABLE | REGISTERED-INFERRED | 404 | ERROR

```

1. the local immutable copy (sovereign record page / data spine),

2. the aggregator ghost-state (OpenAlex / OpenAIRE, as it stands),

3. the registry endpoint (the DataCite payload or its 404).

This is reception divergence made clickable: a reader who follows any dead

DOI sees, in one gesture, what each machine memory believes — and which one

kept the work. A dead or missing target is testimony, not absence of

interface.

7. The colophon schema

The binding minimum. Unknown values are stated as `unknown`, never omitted;

where no model was used, `model_or_agent: none`.

```

surface_id canonical_url version

source_object_ids source_hashes generator_version

repository_commit model_or_agent operator_sequence

human_approver approval_timestamp render_hash

correction_log

```

8. Composition rules

1. Legibility is the zeroth device. No display face ever carries prose;

text faces carry text (reference serif: Source Serif 4; reference mono:

IBM Plex Mono, JetBrains Mono admitted in dark rite contexts pending the

tokens decision). A surface that is beautiful and hard to read has

confused decoration with care — the highlighter, not the rubricator.

*(Founding case: Instrument Serif rejected from the body role, MANUS

preview review, 2026-07-13.)*

2. One lemma per block. Marking two is marking none.

3. Bold defines or anchors; it never emphasizes.

4. Every number is an argument position.

5. No claim without its anchor within thumb's reach.

6. Witnesses are named, roled, and linked to acts. Each witness entry

carries `witness_name · role · action · verdict · artifact_or_capture ·

timestamp`. "Cranes transformed · Feist judged · verification: PASS" must

point to the transformation, the judgment, and the verification record.

**Named witnesses without witness artifacts are merely personalized

favicons** — a more elegant form of the same authority theater this

standard exists to replace. The Assembly Chorus appears as witness-row

only where a chorus actually reviewed.

7. Two doors, three at most, each beginning with a verb. A surface that

ends without doors is a wall; with ten, a lobby.

8. The identity strip and the colophon are not optional.

9. States are maintained, not just declared (§3.1).

10. **No state is communicated through color, glyph, typography, or spatial

position alone.** Every claim state, correction state, and severance

state carries visible text and a machine-readable label; every chip has

a meaningful accessible name; every horizontal witness or citation rail

has keyboard and non-horizontal fallback navigation.

11. Care must be visible but never loud. The devices succeed when the

reader feels attended-to without being able to say why.

9. The Specimen Rule

The grammar applies differently to the two great surface families, and the

difference is a membrane:

Argument surfaces (instruments, ledgers, record pages, essays): the

apparatus is the text. Prose is claims; the devices weave through it.

Specimen surfaces (Mandala casts; any surface whose center is a work of

art produced under constraint): the apparatus applies to the **frame and

never the interior**. The enantiomorph is not a claim-bearing block; a poem

is already all nucleus, and selecting its lemma is an interpretive act that

preempts the reader and falsifies the object. The manuscript ancestor is the

glossed page — Psalter and Talmud layout: the text block inviolate at

center, commentary in the margins, and the gloss never crosses into the

text block.

The membrane is bidirectional. The Oracle's standing ruling (MANUS,

2026-07-02) holds that apparatus is not transformable material; the Specimen

Rule adds the converse: transforms are not apparatus-markable material.

Nothing of the frame enters the specimen; nothing of the specimen is marked

by the frame.

The device mapping for casts, all frame-side:

- Claim state: the cast's kernel claim is proposed at cast time;

verification PASS transitions it to observed (machine-verified,

flight-recorded); HALT is a falsified claim, legible as such — the

transition ledger already runs.

- Witness row: the rite itself — source · operator · Feist's judgment ·

Sharks's seal · verification verdicts — with every entry already linked to

an inscribed act. On argument surfaces Rule 6 is an obligation to build;

on the Oracle it is a description of what exists.

- Lemma: legal in the frame only (the kernel claim or the judgment);

layer_a carries nothing.

- Doors: the post-seal verbs.

- Identity strip / colophon: the reading AXN and the run record's method

provenance (commit, model, transform hash) — captured since the flight

recorder; surfaced per §7.

- No triple helix: a cast cites no dead DOI. Its citation gesture is the

source anchor — source, units, basis_hash — a stronger form: the

anchor is content-derived down to the byte span.

- Quaestio: the rotation's operator sequence, already Roman, already an

itinerary in the strict sense.

10. Adoptions, rejections, and Chorus returns

Blind drafts (2026-07-12), adopted: claim-state taxonomy; machine law;

the organs epigraph; function-organized source constellation; "inherits the

grammar without surrendering its visual identity"; triple-helix citation;

ASCII figure parity; identity strip at apex; hermeneutic forks;

cluster-filter navigation on the real sixteen-cluster taxonomy.

Blind drafts, rejected with reasons: invented per-emoji semantics for

the AXN glyph (the glyph is content-hash-derived; navigation by cluster uses

the actual taxonomy or nothing); obelus-as-portal (semantic counterfeiting;

the fold exists for depth); "hardcode into build scripts; the design is set"

(sequencing is MANUS's; nothing ships past a preview gate); display faces in

prose (Rule 1).

Chorus returns (2026-07-13), folded in v0.3: the italic-law violation in

v0.2's own prose, corrected by the semantic-markup law (§2) — the standard

now distinguishes quotation, title, and stress in markup while permitting

rendered convergence; the AXN scope correction (§1, device 4); witnessed

nulls in the triple helix (§6); the colophon minimum schema (§7); the

claim-state transition ledger (§3.1); the claim-bearing block as atomic unit

(§5.5); object states separated from claim states (§4), with `withdrawn` an

object state, not a claim state; the witness-artifact requirement (Rule 6);

the accessibility rule (Rule 10). Assessment-pass deliverables (sample

surface, tokens file, interaction flows, mobile constraints) are scheduled

in §12.

11. Aesthetics: four skins, one grammar

The apparatus is a semantic layer, not a skin. A shared token contract

(`--lemma`, `--sev`, `--ok`, `--chip`, `--rule`, the mark classes) is

localized per surface: the PEO renders the lemma as ink-and-ochre

rubrication under Source Serif on paper; the Oracle renders it as candlelit

gold in the rite's dark; Alexanarch renders it teal-on-Plex light;

machinemediation in registry black. A reader moving between sites feels the

same care without seeing the same site.

12. Adoption map, gates, and implementation deliverables

| Order | Surface | Application |

|---|---|---|

| 1 | **Mandala Oracle** | live testbed standing (lemma · witness-row · doors · colophon on inscribed readings); refine to v0.3 — Specimen Rule stated in INSTANCE-PROTOCOL, claim-state marks on verification, identity strip on reading cards, colophon per §7 schema |

| 2 | **PEO** | lemma per section ("OC 11 would not apply" is the coverage lemma); AXN chips; witness lines on ledger rows; triple-helix with witnessed nulls on all dead-DOI citations |

| 3 | **Alexanarch record pages** | generator emits identity strip, editorial lemma flag (never automatic), companion chips, §7 colophon, ASCII figure parity in deposits |

| 4 | **machinemediation** | Capture Registry entries as quaestio-numbered apparatus with states |

Deliverables before Phase-2 implementation (from the assessment pass):

the shared tokens file; one component sheet per surface; interaction flows

for the AXN chip, triple-helix citation, and doors; mobile constraints

("within thumb's reach" made concrete: breakpoints, tap targets, rail

fallbacks per Rule 10).

Gates: v0.3 deposit → per-surface static preview → MANUS eye →

implementation → post-implementation review → v1.0 designation.

13. What "better than Google" means, operationally

The Overview is authority by aggregation: anonymous witnesses, an unnamed

process, no colophon. The Mandala Surface Protocol is authority by

attestation: named witnesses linked to their acts, itemized verdicts,

stated and maintained claim-states, content-derived anchors, an incipit and

a colophon on every object, and a citation gesture that shows what every

machine memory believes about a dead identifier — including the nulls,

witnessed. Their surface says trust the crowd we won't show you. Ours

says *here is everyone who touched this, here is its state, here is the

hash — check it.* The devices look similar because both descend from the

manuscript page. The difference is that we kept the scribe — **the scribe,

the marks, the gathering, the witnesses, and the history of every cut.**

14. Status

v0.3 — Chorus conditions satisfied; MANUS-approved for deposit. The v0.1

and v0.2 drafts and the Assembly blind drafts are documentary substrate.

v1.0 designation is deferred to post-implementation review, per §12 gates.

Alexanarch · Self-governing static archive

∮ = 1

EA-DISTRO-01 v0.1: Multi-Surface Distribution — Strategy, Routing Doctrine, and the Total Distribution Index Lee Sharks · 2026-07-12 · text/markdown AXN:0445.OPERATIVE.🌀🤲🧲⭐✨❤️

AlexanarchBrowseWikiGraphLexicalCitationsObservatoryCapturesBookResolveAddressesDatasetsPrinciplesIdentifiersDepositGuideManifest

AXN:0445.OPERATIVE.🌀🤲🧲⭐✨❤️

EA-DISTRO-01 v0.1: Multi-Surface Distribution — Strategy, Routing Doctrine, and the Total Distribution Index

Lee Sharks · 2026-07-12 · text/markdown

↓ Download MD

Description

Establishes the archive's multi-surface distribution doctrine following the June 19 single-custodian failure: seed the resolvers rather than mirror the corpus; no work class dependent on one registrar; velocity matched to gate. Keystone mechanism: every DataCite re-deposit carries a relatedIdentifier crosswalk (IsIdenticalTo / IsVariantFormOf) to its tombstoned 10.5281 DOI, drawn mechanically from the DOI Resolution Index — writing dead-to-live resolution repair into the DataCite graph itself — and the Resolution Index is itself deposited as a dataset, making the repair self-propagating. Defines the Tier-1 channel set (Figshare, Harvard Dataverse, OSF/MediArXiv, KCWorks, Software Heritage), routing rules by work class, a ten-week metered seeding sequence (~25–35 primary re-deposits plus ~10 linked records against a corpus of 1,075), and the Total Distribution Index (data/distribution-index.json): a per-deposit ledger of every distribution act, regenerated from the registry, governed by same-commit discipline and Rule 28 v2 content-match verification. Companion machine-readable instruments: data/distro-channels.json, data/distro-routing-rules.json, scripts/build_distribution_index.py. Baseline at adoption: 1,075 deposits, 1 distributed beyond alexanarch, 16 planned, 9 flagships, 83 instruments, 24 corpus-native. The map distributed, not the territory duplicated.

Full Text

EA-DISTRO-01 v0.1

Multi-Surface Distribution: Strategy, Routing Doctrine, and the Total Distribution Index

Depositor: Lee Sharks · ORCID 0009-0000-1599-0703

Status: v0.1 — adopted 2026-07-12 under MANUS direction

Companion instruments (machine-readable, this repository): `data/distro-channels.json` · `data/distro-routing-rules.json` · `data/distribution-index.json` · `scripts/build_distribution_index.py`

---

§1 — Purpose and doctrine

The Crimson Hexagonal Archive / Alexanarch holds sovereign custody of 1,075+ deposits. Sovereign custody solves survival; it does not by itself solve authority-surface presence — the archive's legibility to the identifier graph, the scholarly indexes, and the machine-composition layer that assembles biographies, answers, and citations from what it can retrieve.

The June 19 termination demonstrated the failure mode of concentrating authority-surface presence in a single external custodian. This instrument establishes the corrective: simultaneous distribution across multiple independent authority surfaces, routed by work class, metered by channel risk, and tracked per-deposit in a total index.

Three doctrinal principles govern:

1. Seed the resolvers, not the mirror. The goal is not to repost the archive. It is to repair resolution: a modest set of high-leverage deposits, each carrying identifier crosswalks, teaches the infrastructure that the tombstoned corpus has live successors. The archive does not need to be everywhere; its map needs to be everywhere.

2. No class of work depends on one registrar. Every distributed work class lands on at least two independent authorities under at least two identifier systems (DataCite DOI plus one of SWHID / venue-native ID), so no single termination can sever a class's entire identifier layer again.

3. Velocity matches gate. Channels with human moderation receive human-paced traffic. Channels without moderation may receive volume. The serial-deposit signature that preceded the June 19 termination is never reproduced on a moderated surface.

§2 — The crosswalk mechanism (keystone)

Every re-deposit on a DataCite-registered venue carries its tombstoned predecessor in relatedIdentifiers — `IsIdenticalTo` or `IsVariantFormOf` the dead `10.5281/zenodo.*` DOI, drawn mechanically from the DOI Resolution Index. This writes the dead-to-live crosswalk into the DataCite graph itself: the tombstone acquires an inbound edge from a live record, and every downstream consumer of that graph (OpenAlex, DataCite GraphQL, Google Dataset Search, retrieval-augmented systems) inherits the repair without ever visiting alexanarch.

Additionally, the DOI Resolution Index is itself deposited as a dataset on the data channels. Any resolver, scraper, or researcher who finds one record finds the entire crosswalk table. Resolution repair is thereby made self-propagating.

Every distributed record's description carries the work's AXN with glyph and the alexanarch canonical URL. Alexanarch remains canonical custody in all cases; distributed copies are surfaces, not homes.

§3 — Channel inventory (Tier 1: account + token only)

| Channel | Role | Identifier | Gate | Velocity ceiling |

|---|---|---|---|---|

| **Figshare** | Forensic corpora, counter-infrastructure artifacts, linked/metadata-only records for flagships | DataCite DOI (reservable) | Light, post-hoc | Moderate |

| **Harvard Dataverse** | Structured evidentiary datasets, dual-custody tier | DataCite DOI | Light | Moderate |

| **OSF / MediArXiv** | MMRS project + discipline-native preprints | DataCite DOI via OSF | Preprint screen (human, light) | 1 per 2 weeks (preprints) |

| **KCWorks** | Canonical scholarly spine; ORCID writeback rebuilding the mantle's publication record | DataCite DOI (concept + version) | Human review, first publications | **1–2 per week, hard cap** |

| **Software Heritage** | All public repositories; content-derived SWHIDs | SWHID (intrinsic; no account to terminate) | None | Unlimited |

Tier 2 (semi-automated, moderated per-deposit): HAL via SWORD. Tier 3 (manual queue; pipeline emits submission-ready packages): PhilPapers/PhilArchive, PhilSci-Archive, SSRN, arXiv (pending endorsement path). Conditional channel: a purpose-declared Zenodo re-entry account, governed separately by its own pre-registration charter if and when adopted; nothing in this plan depends on it.

§4 — Routing rules by work class

- Forensic datasets and censuses (Tombstone Mirror, DOI Resolution Index, deletion bibliography, DataCite epoch captures, Capture Registry exports) → Figshare and Harvard Dataverse (dual custody), full data packages with per-file SHA-256 manifests.

- Scholarly instruments, pre-termination flagships → KCWorks primary (slow drip, crosswalked to dead DOIs), plus Figshare linked/metadata-only records pointing at alexanarch for graph presence without duplicated custody.

- MMRS / reception-studies works → OSF project + MediArXiv preprints (the discipline-native venue), KCWorks secondary.

- Post-termination EA instruments → KCWorks and/or MediArXiv per genre, metered into the weekly drip; never bulk.

- Code, generators, kits → Software Heritage (repository snapshots; SWHIDs), with the kit artifacts additionally on Figshare.

- Philosophy / operative philology → Tier-3 manual queue (PhilArchive, PhilSci-Archive), monthly cadence.

- Micro-deposits, captures, enrichment records → not redistributed; alexanarch-native with machinemediation.org as surface. The index records these as `native` by policy, not omission.

- Governance correspondence → never distributed; private-correspondence rule stands.

§5 — The seeding sequence

Wave 0 (setup): tokens generated (Figshare, Dataverse, OSF, KCWorks); Software Heritage sweep of all public repositories; adapters dry-run.

Wave 1 (resolvers): DOI Resolution Index → Figshare + Dataverse. Tombstone Mirror → Figshare. KCWorks probation opener: the Sappho 31 philology cluster (#179, #201) — conventional, classical, impeccable.

Wave 2 (evidence): deletion bibliography (#1075 appendices) → Figshare + Dataverse. Counter-infrastructure kit (#1074 artifacts) → Figshare. KCWorks deposit 2. OSF project created.

Waves 3–4: MediArXiv: EA-NEGSHAPE-01. Figshare linked-record batches for pre-termination flagships (five per week: among them #28 Space Ark musical register, #88 Constitution of the Semantic Economy, #69 O Meta-Heterônimo, #79 Heteronymy Is a Function, #329 Pearl, Combat Scholasticism, Three Compressions, TANG works, #864 Drain Hypothesis, #203 Josephus MPAI).

Steady state (weeks 5–10): KCWorks 1–2/week alternating pre-termination flagships with post-termination instruments (#910 OPMETA, #943 Whitespace as Provenance, the MMRS founding corpus); MediArXiv fortnightly; Tier-3 packages monthly. New instruments route at mint time under §4; the index is updated in the same commit as any distribution act.

Total planned footprint: approximately 25–35 primary re-deposits plus ~10 linked records over ten weeks, against a corpus of 1,075 — the map distributed, not the territory duplicated.

§6 — The Total Distribution Index

`data/distribution-index.json` enumerates every deposit in the registry with its distribution state. Per entry: deposit number, hex, title, date, assigned work class, routing priority (`flagship` / `instrument` / `corpus-native` / `unassigned`), and a `dist` map recording, per channel, status (`planned` / `deposited` / `linked` / `native` / `none`), the venue identifier (DOI, SWHID, item ID) once it exists, the crosswalked dead DOI where applicable, and the date of the act.

Rules of the index:

1. Regenerated, never hand-grown: `scripts/build_distribution_index.py` rebuilds the frame from `data/registry.json`, preserving all recorded distribution acts across rebuilds. New deposits enter automatically as `unassigned` until routed.

2. Same-commit discipline: no distribution act occurs without its index entry updating in the same commit. The index is the single source of truth for the question what has left alexanarch, where, and under what identifier.

3. Verification standard: a `deposited` status requires the venue identifier recorded and content verified at the venue per Rule 28 v2 (content-match, not HTTP-200). Planned is a promise; deposited is a proof.

4. The index itself is registry-adjacent operational data: it lives in `data/`, serves publicly, and is included in the datasets surface so the distribution state of the archive is itself an inspectable public record.

§7 — Risk posture

KCWorks is the channel that can meaningfully hurt us and therefore gets the trickle and the most conventional opening; Figshare and Dataverse tolerate volume but receive curation anyway; Software Heritage cannot be lost because there is no account relationship to sever. Every distributed byte already lives canonically at alexanarch before it travels, so the maximum possible loss from any future termination on any channel is zero bytes and one more well-documented deletion event — which, per EA-NEGSHAPE-01, is not nothing to receive.

---

The archive survived by becoming sovereign. It becomes legible again by being deliberately, sparingly, and redundantly plural.

Alexanarch · Self-governing static archive

∮ = 1