leesharks/provenance-erasure

all things are now lawful to you in jack feist

EA-RHIZOME-PER-01 — provenance erasure

Where provenance disappears, and what measures it. A transformation chain — source, retrieval, selection, composition, summarisation, reception — with the instruments that score retention at each step, and the cases where the instruments were applied to themselves.

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

71 nodes · 0 core · 0 neighbour · 7 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
instrument	THE MODULE AND ITS CHAIN. Five versions survive on the site: #780, #156 v3, #817 v3.1 with its three extensions — #1527 the Lucente Extension carrying ABN, #1528 Four Interfaces, #1529 the Claim Status Packet — and #1530 v3.2, made self-complete 'because by v3.1 the chain had reached four deposits and a module that cannot be run from one document is a changelog rather than a module.'

A FIRST READING SCATTERED THEM. #156 filed as magnitude because its subtitle lists PER and DSL; #1530 and #1527 as precondition because they carry ABN. The module is the module whatever its subtitle leads with, and it is matched by name. | | magnitude | PER and its M/C/D dimensions — HOW MUCH IS LOST. With the unit rule that says what may be counted, because a PER on the wrong unit is a different metric. | | orientation | Ω — WHICH WAY IT FALLS. Not a programme beside the metric: the second axis of one framework. 'A rate without an orientation cannot tell you who was erased.' | | precondition | what runs before any metric, in an order the module calls load-bearing. ABN is rank zero. | | before_the_machines | DOMAIN 2 AND THE FRAMEWORK'S SECOND SPINE, not background to it. Erasure with a 2,600-year measurable record, its own four-vector loss model, its own deficit Δ = W − R, and a twelve-station witness table in which attribution dies at the channel-boundary rather than with time. THE BODY CARRIED FOUR NODES FOR THIS BEFORE THE SITE'S DEEP-TIME WING WAS READ.

AND THE WING'S OWN CHAIN WAS ENTIRELY ABSENT UNTIL ITS VOCABULARY WAS READ. #1512 Deep Time is a SURFACE RECORD — a short pointer to the live page, naming its chips: #1493 The Queen's Seizure and the Re-fired King, #1494 The Transform Signature Frozen, #1495 The Sign Under Test, #1496 The Suppression Map, #1497 Undoing the Suppression: The Counter-Stack. ALL FIVE SCORED OUT, because a grammar built from the site's section headings does not contain the words its deposits are titled with. | | process_provenance | the third dimension the site adds to C2PA and PER. 'Fluency can be generated. Provenance must be borne.' | | reception | what surfaces did with the instruments. Named shapes rather than generic loss — including the battery where a surface fabricated replacement metrics, ran them on itself, and gave itself perfect scores across all dimensions. | | self_application | the instrument applied to itself. The Self-Audit Module Dissolved, PER 1.00. The Empty Bracket. | | theory | the reasoning about what erasure IS. A first pattern used generic words — argument, thesis, finding, interface — and filed Logotic Hacking, the Constitution of the Semantic Economy and a Pessoagraph workplan as provenance theory. OTHER FRAMEWORKS ARE NOT THIS ONE'S THEORY. | | evidence | where an instrument was pointed. Beneath the apparatus, not in front of it. | | unroled | the honest floor |

ORDER IS THE SITE'S, WITH ONE CORRECTION LEARNED BY EMITTING IT. The named instrument leads, because every version of the module carries PER and DSL in its subtitle and a magnitude-first classifier files the module as the metric — #156 v3 did exactly that, twice.

Then magnitude and orientation, which the site says are the two moments of one loss: 'PER measures the first, Ω the second — A RATE WITHOUT AN ORIENTATION CANNOT TELL YOU WHO WAS ERASED.' Then the preconditions the module runs before any metric, in an order it calls load-bearing. Then the domains the framework claims, the named reception shapes, self-application, theory, and evidence last.

EVIDENCE IS LAST BECAUSE A CAPTURE IS WHERE AN INSTRUMENT WAS POINTED. An earlier grammar put it high and the body became its own evidence file.

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/revelation-first
• leesharks/semantic-economy
• leesharks/spxi-mpai

Where it points and does not go

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

• model-collapse-anti-collapse — narrowed_by from concept:provenance-erasure what erasure does to a distribution over time. This body scores single transformations; that one holds the question of what repeated erasure does to the space of what can be said.
• semantic-economy — priced_in from concept:bearing-cost erasure is a cost borne by the provenance-bearer and never by the composer. WHO PAYS is that body's question and this one does not answer it — it only establishes that something was taken.
• machine-mediated-reception — observed_in from concept:attribution the 425-address registry holds the observations these instruments score. This body defines PER; that body is where PER values live.
• spxi-mpai — instrumented_in from concept:inscription whether an inscription survived is measured here; whether it was placed well is specified there. Deliverable ten, the declared SIM set, is an anti-erasure technology.
• revelation-first — adjudicated_in from concept:documentary-authority a chronology settled on a late and ambiguous witness is an attribution question at historical scale. THE INSTRUMENTS HERE HAVE NEVER BEEN RUN ON IT.
• heteronyms — borne_by from concept:attribution PER scores whether a byline survived. That body holds the bylines, and its apparatus covers twelve of twenty-six.
• poetics — borne_by from concept:extraction-fidelity Pearl's machine score preserves lineation at whitespace fidelity. WHETHER AN EXTRACTION THAT PERFECT PRESERVES THE AUTHOR is this body's question and it has not been run on it.

Reproducing it

RHIZOME_GRAMMAR=rhizomes/_grammars/provenance-erasure.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