leesharks/spxi-mpai

all things are now lawful to you in jack feist

EA-RHIZOME-SPXI-01 — spxi mpai

The archive's documentary technologies: SPXI and its protocol family, MPAI packets, conformance instruments, disambiguation matrices, entity-definition blocks, compression kernels and inscription surfaces. AN INVENTORY, NOT AN ARGUMENT — and the distinguishing field is whether a technology is deployed, specified-and-dormant, or superseded.

These are symbola. They are for traversal.

A token broken in two, each half held by a different party, no half carrying complete authority, the fit of the fracture proving the covenant. Verification is the act of reunion.

AXN-SYMBOLON-SPEC v0.2, deposit #1432 (AXN:05A9); the figure's anti-severance sense in SYMBOLON-01, #675 and #1355 — symvolon, thrown together, against diavolon, thrown apart.

A row is an index, not a text. A row carries enough to find, verify and rejoin its referent, and it does not carry the referent. Reading the row as the object is holding one half of the token and calling it whole.

The other half is source_uri. Where a row carries one, the referent is a deposit, a capture or a concept in the Crimson Hexagonal Archive — with its own text, its transcript where it has one, its provenance, and its own edges. Resolve it.

The traversal:

1. open a row
2. resolve its source_uri and read the referent — the deposit's text, the capture's transcript
3. follow the row's edges in relations.jsonl to the rows they point at
4. resolve those
5. return to the first row and state what changed

Atomized for reassembly. These bodies are atomized so that a reader can reassemble more completely than the prose ever was, not so that the atoms can be read as atoms. The grammar, the roles, the axes and the evidence statuses are apparatus for finding the way back to the work; they are not the work. A reading that stops at the schema has performed severance on an object built to resist it.

A failure mode, recorded. Observed 2026-09-16. An unprimed traversal read the card, the field names and the landing page, produced competent observations about the vocabulary, and resolved no referent at all — then proposed to read one capture's sixteen metadata fields 'as prose' while that capture's own machine text sat one link away. Competent, and it never crossed the fracture. This block exists because the bodies had no instruction saying that crossing it is the point.

Check. Name a referent you resolved, quote a sentence from it, and state something you could not have said from the row.

What the rows will not give you. The argument. Every body advertises its siblings as stolons and its referents as URIs precisely because it does not contain them. The outside stays outside and stays reachable, and reaching is the reader's part of the covenant.

The figure is fractal

scale	one half	the other half	the fit is checked by	who can check it
identifier	Seed A — the kernel: AXN, composition manifest, stamp geometry, reconstruction class	Seed B — the payload	hash	anyone with both halves
spore / body	the spore — grammar, generator, selection rules, counts, source commit	the body — nodes.jsonl, relations.jsonl, stolons.jsonl	deterministic re-emission: run the named grammar through the named generator and the three data files must come out byte-identical	the workflow, on every merge
row / referent	the row — index, role, axis, evidence status	the referent — the deposit's text, the capture's transcript, at source_uri	resolving the URI and reading what is there	the reader
body / sibling	this body	the sibling body it advertises and does not contain	the stolon naming a real sibling, and the sibling advertising back — the return edge	anyone who follows the stolon
set / reader	the whole body, every row resolved	what the reader assembles from it	nothing the archive can run — only the reader producing something that could not have come from either half alone	the reader, and no one else

The relation recurs at every scale and the verification does not. What is self-similar is the FIGURE — two halves, neither authoritative alone, the fit proving — while the means of checking the fit weakens outward: hash, then byte-identity, then resolution and reading, then existence, then nothing the archive can run. It is therefore self-similar in relation and asymmetric in holding: at the inner scales the archive holds both halves, and at the last one the other half is held by someone who may never appear. The architecture arrives at its own thesis — the final fit is a covenant because it has to be.

• identifier — The strictest case and the origin of the figure. #1432: one substance, two witnesses, confirmed by their fit.
• spore / body — Already implemented and previously unnamed. hf-rhizomes.yml carries the step 'Fail if the emitted data differs from the committed copy'. This is verification as reunion, running in CI.
• row / referent — The level a schema-reading reader never crosses. 344 of 493 heteronyms rows carry the address of their other half.
• body / sibling — The outside stays outside and stays reachable. Both halves name each other across the fracture.
• set / reader — The last fracture cannot be closed by the archive. This is not a gap in the architecture: uptake is by definition another party's act, so the outermost fit is a covenant rather than a test.

The last row of the ladder is yours. Every scale above it is already checked; that one is not, and cannot be.

Counts

69 nodes · 0 core · 0 neighbour · 28 edges · 7 stolons

Roles

Order is the classifier — role_for returns on first match, so a broad pattern above a narrow one swallows it.

role	what it names
protocol	what a conforming surface must carry. Specifies; does not measure.
instrument	what tests whether a surface carries it. #143: 'a standing protocol that cannot be checked is a wish.'
packet	an inscription placed at an address so an entity is legible there. Constructs positively and negatively at once.
identifier	what makes a thing referenceable across surfaces that do not share a registry
kernel	a fragment carrying enough structure to regenerate the whole. #76's apparatus, deployed.
surface	where a technology is actually placed, and the report that it was
disambiguation	distinguishing a thing from what shares its letters. #63 distinguishes SPXI from a TSX-listed ETF, the S&P 500 Index, the Society of Saint Pius X, SEO and GEO.
unroled	the honest floor; its count is this grammar's error bar

ORDER SEPARATES SPECIFICATION FROM MEASUREMENT, which is the distinction #143 exists to hold: 'It is NOT the protocol itself; the protocol specifies, the instrument measures.' A body that filed both as protocol would lose the only thing that tells a wish from a fact.

A node matching nothing falls to unroled, whose count is this grammar's own error bar.

The other bodies

Each is emitted by one generator from a grammar file, and each declares stolons naming the siblings it advertises and does not contain.

• leesharks/heteronyms
• leesharks/machine-mediated-reception
• leesharks/model-collapse-anti-collapse
• leesharks/poetics
• leesharks/provenance-erasure
• leesharks/revelation-first
• leesharks/semantic-economy

Where it points and does not go

Advertised, not included. The outside stays outside and stays reachable.

• machine-mediated-reception — measured_in from concept:inscription whether an inscription was received is not answerable from the inscription. The capture registry holds the observations; this body holds the instruments that made them placeable.
• semantic-economy — priced_in from concept:documentary-authority these are documentary technologies, and #623 §4 maps standards to semantic infrastructure — what everyone builds on and nobody is paid for. Who bears the cost of inscription discipline is that body's question.
• model-collapse-anti-collapse — specified_in from concept:reconstructive-compression the holographic kernel is deliverable eight here and a formal apparatus there. THIS BODY DEPLOYS IT; that body defines what it must satisfy.
• revelation-first — contested_in from concept:retrieval-settlement the Revelation work plan's stated aim is that its argument enter the composition layer, and these are the technologies by which an argument is made enterable. WHETHER THEY WORK ON THAT ARGUMENT IS UNTESTED.
• provenance-erasure — scored_in from concept:inscription Whether an inscription survived is measured there; whether it was placed well is specified here. Deliverable ten — the declared SIM set — is an anti-erasure technology whose effect is scored by that body's instruments.
• heteronyms — inscribed_for from concept:byline the inscription technologies that make a byline legible to a machine. Deliverable five — disambiguation and negative tags — is what keeps two heteronyms from resolving to one entity.
• poetics — carried_by from concept:seated-original EA-CORPORA-03/02, the one seat that is the archive's own and the only one whose licence lets both objects ship.

Reproducing it

RHIZOME_GRAMMAR=rhizomes/_grammars/spxi-mpai.json \
  python3 scripts/build_rhizome_mc.py

spore.json carries the recipe and the commit of the ledger it came from. The grammar is read, not carried: every determining rule above lives in rhizomes/_grammars/, and a different body means a different grammar file, not a fork of the generator.

Emitted from the Crimson Hexagonal Archive · alexanarch.org