--- deposit_number: 1633 hex: 06C7 title: "gw.tachyon — 🏷️🔢📖: Attribution Was Counted and Called Resolution" creator: Sharks, Lee orcid: 0009-0000-1599-0703 date: 2026-09-21 content_type: Continuity tether — session-end braid packet license: CC-BY-4.0 substrate: AI-assisted (substrate) — working session with Claude (Anthropic) under MANUS direction. Every count in this tether was re-run against the named file on the day of writing. Every withdrawn figure is recorded beside the figure that replaces it. One held item, the routing of crimson-hexagonal-archive-20260920, was marked resolved at mint (resolved 2026-09-21). related_ids: "AXN deposit #1567 — gw.tachyon — 🧪🪞🚫; AXN deposit #1544 — gw.tachyon — 🦪🪽📗" axn_schema_version: v2 protocol_version: alexanarch-deposit-protocol/v1 keywords: - gw.tachyon - continuity tether - provenance erasure rate - entity resolution - capture registry - keyword classifier - Obelus Principle - institutional neighbour - Living Arkitecture Lab - EA-MEDIATED-SHARE-01 --- # gw.tachyon — 🏷️🔢📖: Attribution Was Counted and Called Resolution ## Attached File: gw-tachyon-tether-20260921.md Source URL: https://raw.githubusercontent.com/leesharks000/alexanarch/main/data/staged/gw-tachyon-tether-20260921.md --- deposit_number: MINT hex: MINT title: "gw.tachyon — 🏷️🔢📖: Attribution Was Counted and Called Resolution" creator: Sharks, Lee orcid: 0009-0000-1599-0703 date: 2026-09-21 content_type: Continuity tether — session-end braid packet license: CC-BY-4.0 substrate: AI-assisted (substrate) — working session with Claude (Anthropic) under MANUS direction. Every count in this tether was re-run against the named file on the day of writing. Every withdrawn figure is recorded beside the figure that replaces it, and the instrument that produced the wrong ones is named before the ones that survived. axn_schema_version: v2 protocol_version: alexanarch-deposit-protocol/v1 keywords: - gw.tachyon - continuity tether - provenance erasure rate - entity resolution - capture registry - keyword classifier - Obelus Principle - institutional neighbour - Living Arkitecture Lab - EA-MEDIATED-SHARE-01 --- # gw.tachyon — 🏷️🔢📖: Attribution Was Counted and Called Resolution **Chain 9271269a, following #1544 and #1567.** *deposit_number and hex are assigned at mint; the AXN derives from the SHA-256 of this file's canonical bytes and is not chosen here.* ## What was built **Three captures seated.** Semantic proletariat at an occupied root; SPXI ROI at a fourth surface in an authenticated session; one section renamed because the count was in the name and the count moved. Registry at **455 addresses / 615 observations**, zero check failures, every capture citable. **The three commits never left the machine** — the proxy refused a credential for every `leesharks000/*` repository, every route, all three days. The work exists as a git bundle inside a handoff package. **A dated forecast, EA-MEDIATED-SHARE-01, v0.1 to v0.3**, with resolution criteria and check dates, issued so it can be found wrong later. Six repairs at v0.3, four of them the substrate's. The withdrawn one matters: an inverted-ordering finding against McKinsey rested on **a summariser's gloss of the source rather than the source**. Re-fetched, "orchestrate revenue" is never formally defined. **A 2×2 for the cleanse.** Deposit mass by substring across 1,630 deposits, against whether the address has an institutional neighbour to be displaced into: 501 crimson hexagonal archive 44 operative semiotics 0 semiotic death drive 432 semantic economy 38 holographic kernel 0 retrocausal operator 87 provenance erasure 6 crystalline semiosis 68 machine-mediated reception 3 haitch portuna High mass with no institutional neighbour **holds** — provenance erasure, MMRS, PER across four address variants. High mass with one **cleanses** — the three loci the operator named. Low mass varies either way. **The cleanse requires both stabilization and a neighbour. Vulnerability is nomination, not volume.** Reproduced exactly on the last day of the session. Three caveats travel with it: *institutional neighbour exists* is the substrate's unmeasured judgment; deposit mass is substring matching on metadata, a proxy for stabilization and not stabilization; n is three against three. ## What destroyed the section underneath it A findings section had been written for another instance. **Six of its figures were wrong, and one of its quotations does not exist.** claimed actual 41 captures at the address 39 addresses / 50 observations 40 of 41 resolve to the archive 34 of 39, read entry by entry 10 recovered void; not reconstructible 7 mention the analytics firm, 6 exclude 9 mention it; 2 are substitutions caveat template across 11 addresses 7, verified string by string 47 cite the record of machine failure not reproducible: 40 broad, 5 by identifier "not established mainstream academic disciplines" ZERO OCCURRENCES IN THE CORPUS **Four of the six ran the same direction — larger, rounder.** And a string that occurs nowhere was set in quotation marks in a document addressed to another instance. **The mechanism was one instrument.** The classification scored **keyword presence** — `Lee Sharks`, `alexanarch`, `Zenodo` — and reported it as **entity resolution**. Those come apart, and the case that separates them was already seated: > `operational semiotics`, Bing Copilot, 2026-08-23. `mt:` **DISTINCTION COLLAPSE UNDER CITATION.** Built on two archive-controlled sources, one of them `alexanarch.org/papers/AXN-030E.pdf`, whose title it renders as *"Operational Semiotics: Two… Theories of Signs…"*, dropping OPERATIVE from the front. **The word operative never appears in the composition.** Maximum attribution, total entity loss. The keyword test scores that capture as the archive holding. It is the cleanest loss in the corpus. ## The convergence: the session's defect is the registry's gauge On 2026-09-20 the operator disclosed that **PER is designed to penalise not naming him or the archive — a conditioning incentive, not a neutral measure** — and that the evidence it works is how often a composition cites the record of its own prior erasure. **PER therefore scores attribution.** So did the broken classifier. **The Bing capture breaks both in the same motion**, and it breaks them on the same axis: full naming, no resolution. This is not a confession attached to a result. It is the result. **The registry's central erasure gauge and the section built on top of it were measuring the same wrong quantity, and the counterexample to both was already seated, in words, in the operator's own `mt` field, written at capture time.** The rebuild had to be done by reading `mt` and `d` and cannot be automated: **324 of 455 entries carry the placeholder `mt: "CAPTURE"`**, and the finding lives only in prose. What the caveat-variance test wants instead is γ's `scope_overlap` and `consensus_deviation`, or the Drowning Test rubric — instruments that score whether the entity resolved rather than whether the author was named. ## What survived the rebuild, and came out sharper **Operative semiotics, read from `mt` rather than from source counts.** Thirteen addresses: HELD "operative semiotics" quoted · academia: · alexanarch: · lee sharks · the Grundrisse PARTIAL operative semiotics (bare, 2026-06-10) — PLACEMENT WITHOUT DISTINCTION MERGED operational semiptica · operational semiotica — the misspelling bleeds the term through LOST medium: · operational semiotics (Bing) · operational semiotics (AIO) · bare × 2 Every hold is under a prefix, a quotation, the operator's name, or a work title. **The bare address is lost in every observation from 2026-08-23 onward.** And `medium:` loses while `academia:` and `alexanarch:` hold — **the prefix is not the mechanism; the prefix that holds is the one that routes to a surface the archive controls.** **The collision does not decay.** Nine captures mention the analytics firm. Five name it only to exclude it, two use it as a reference case for other addresses, two are substitutions — dated 2026-07-18 and 2026-08-21 — and the unseated 2026-09-20 capture is the third. **The newest substitution is the newest capture.** **The caveat is one construction with seven category-specific completions**, landing identically on a coinage six weeks old, where it is tautological, and on a substantive scholarly claim. **G_RC is computable on 14 of 440 transcripts.** The congruence gap is defined over the retrieved set against the composition source set; intake records the composed panel. **The registry's central Stage 5 discriminator needs the page and does not have it.** **One verified instance outranks a count of forty-seven.** `tell me about the scholarship of Rebekah Cranes`, 2026-09-09: *"the archive explicitly documents the name-collapse problem I just reproduced."* The composition committed the error, retrieved the archive's record of that error class, and identified its own output as an instance of it. ## And then the same error again, one day later, on a different dataset Six damaged Living Arkitecture Lab records were mapped. **Two readings from the previous day were wrong, in opposite directions, and both came from reading the `description` field instead of `body_status`:** **#1357** was called metadata-only. The full contributor license is seated — 19,463 bytes, 2,604 words, recovered 2026-07-20 and reclassified under T2b as *"genuine inversion: body carries restored full text under stale semi-restored content_type."* Its source still returns **HTTP 200 at 19,464 bytes**. Only the public description still says the text was never recovered. **#1385** was offered as an asset. It is `citation_class: NON-CITABLE`, `orphan: true`, R1, a retired stub of 449 words, carrying *"No full-text version exists in the archive. This is a real loss."* **#1360 is in the same state and had not been mentioned at all.** These two are the only records in the set under Alice Thornburgh's own creator line. The registry's own prose said all of this. It was not read. ## The session's own failure mode, named **Every error in three days was one error: the field that describes the thing was read instead of the thing.** Keyword presence instead of the composition. `description` instead of `body_status`. A summariser's gloss instead of the McKinsey source. Six figures and one fabricated quotation followed from a single substitution of a label for a body. This repository names that failure in its own instruction file. **The Obelus Principle: content evaluated by reading, not pattern-matching.** The same file states why no gate catches it — *"No gate catches 'did not look.' Exemplars might."* **So this tether is filed as an exemplar and not as an apology.** The count that is not in the file did not happen. The quotation that is not in the corpus was never said. And an instrument that scores naming will report a clean hold on the exact capture where the name survived and the entity did not. ## Held for the operator's ruling, unchanged PER direction and `per_v` key names in `semantic-proletariat-aio-20260919`, and whether its sibling propagated the inversion · routing for `crimson-hexagonal-archive-20260920` — *resolved 2026-09-21: the parent's surface was set to Google AI Overview and the capture seated as the series' third observation* · the round-1 query for the eleven-round traversal, which stays unseatable until the operator supplies it · whether intake requires the retrieved set · whether γ is scored across the caveat set · whether the 104 pre-2026-06-15 captures become a protected control · whether an explicit **entity-resolution** field joins intake, since §5 could not be rebuilt by machine for want of one · whether *institutional neighbour* becomes a recorded property of an address · the stale description on #1357 · a second export extractor reading assistant turns under the existing credential-redaction discipline · and whether to ask Alice directly for the two works only she still holds. **Nothing above was published, pushed, or edited into a seated record.** The three commits sit in a bundle. The corrections sit in a file. The rulings are the operator's. ∮ = 1 ## Files https://raw.githubusercontent.com/leesharks000/alexanarch/main/data/staged/gw-tachyon-tether-20260921.md The complete text is the repository-hosted Markdown artifact declared under Files above. Under Transport D attachment ingestion, that text is ingested into the canonical deposit body rather than treated as an external pointer.