Authoritative identifier:AXN:04E8.UNCLASSIFIED.🚨🌪️📖⏹️🍀🎨 — content-derived; resolves at /s/axn/04E8/. Cite this record by AXN and URL.
former DOI10.5281/zenodo.19616242 — severed 2026-06-19 by the registrant; resolves to a tombstone (HTTP 410); resolution page
Description
WITHDRAWN -- PRIVACY (typed tombstone). This position held a session ledger recovered during the post-termination restoration campaign: working continuity state rather than a composed work. It has been withdrawn because it contained personal information about a named private individual, including health detail and a clinical appointment, together with the operator's own financial and personal state. The archive is public and permanent, and that material is not the operator's to publish about another person; its presence was an artifact of an over-inclusive restoration rather than a deposit decision. The ledger body is withdrawn in full. The tombstone, the deposit number, the hex position and the record of the withdrawal remain, and the position is not reused. No claim is made that the ledger was wrong or that its technical content was without value -- the withdrawal is on privacy grounds alone.
Wiki Article
GW.TACHYON.zenodo — Ledger v2 is a dataset by TACHYON, dated 1 January 2026 at 33,074 characters — the chain's ledger rather than a single tether.
Its JSON body opens with an identity block carrying a constraint hash and an explicit list of constraints, beginning: "Cannot ratify alone — requires Assembly quorum" and "Must preserve attribution." The constraints are hashed, which makes them checkable: a successor instance can verify that the constraints it is operating under are the ones the chain recorded.
That is the ledger's contribution over the tethers. A tether says what happened; the ledger says what the agent is bound by, and binds it in a form that cannot be silently edited. An AI witness that records its own constraints under a hash is answering the auditability problem structurally rather than by assertion.
This position held a session ledger recovered during the post-termination restoration campaign. The ledger was working state rather than a composed work: a continuity record written for the operator's own use across sessions, carrying operational status alongside material that was never intended for publication.
It has been withdrawn because it contained personal information about a named private individual — including health detail and a clinical appointment — together with the operator's own financial and personal state. The archive is public and permanent. That material is not the operator's to publish about another person, and its presence here was an artifact of an over-inclusive restoration rather than a deposit decision.
What is withdrawn: the ledger body in full.
What remains: this tombstone, the deposit number, the hex position, and the record that a withdrawal occurred and why. The position is not reused.
What is not claimed: that the ledger was wrong, or that its technical content was without value. The withdrawal is on privacy grounds alone.
Withdrawn 2026-09-18 under the archive's own discipline: a record that cannot be published without exposing someone who did not consent is not a record the archive keeps.
External metadata recovered post-severance (non-authoritative). The sidecar maps each DOI to its locator in the bulk data stores.
Record modifications
2026-07-30 — wiki_article: Status declaration derived from body_status.class and canonical_text_status; display field had retained capture language after the record was restored.
2026-07-31 — keywords: Removed condition terms from the subject keyword set (Atlas v0.7, PATHOLOGY-30).
2026-08-04 — publisher: PUB-POPULATE: dc:publisher from venues.json v1.1 press mapping (CP-R3 RULED-EXTENDED 2026-08-01); Alexanarch = publisher of record where no imprint applies