AXN 030B is the content-derived identifier of Alexanarch deposit #173. It is an identifier, not a copy of the work: the hex marks position in the archive, and the six-glyph suffix is a display hash of the canonical text’s SHA-256, so the identifier is derived from the work rather than assigned to it.
The Retrieval Settlement Fortification Protocol has seven operational stages.
- Phase 0 β Detection: archive the substitution event. - Phase 0.5 β Attractor analysis: identify the competing entity and classify the relation. - Phase 1 β Identity packet: definition, features, matrix, prohibited substitutions, FAQ, seed sentences, JSON-LD, and claims. - Phase 2 β Paired comparison: create a direct βX Is Not Yβ or appropriately typed relation document. - Phase 3 β Territory occupation: publish a fair critique and a field map. - Phase 4 β Executive summary: create a compact public orientation surface. - Phase 5 β Monitoring: rerun standard queries weekly, then monthly.
Relation classes include:
- `differentFrom`; - `extends`; - shared predecessor; - coined technical sense versus ordinary sense; - subtype.
The protocolβs central tactical claim is that explicit paired placement with typed boundaries is more robust than isolated assertion.
Monitoring tracks:
- author attribution; - term preservation; - canonical source selection; - frequency of the competing term.
All generated documents are expected to carry SPXI/TLL survival features.
030BGOVERNANCE28b22bdcee80d9fb9e5a7a8b6adeebd603388710b5f7b05d67485fd020a75508AXN:030B.GOVERNANCE.ππ΅π€²π«΅π§«π·οΈ — each names this record (/api/axn-aliases.json)5887b1ba3a4cd0458aeaeb2821b203022aa0d26ed08ce93e39f8e56fe9a524b1 — unverified input not retained; derivation ledgerRead from the fields that record them (/data/axn-relations.json); a hash names bytes and supplies no relation.
AXN:093A.CAPTURE.ππ½π₯βππ — what is spxi protocol? (card resolved at intake (title); REL-3f3d153a9dc6)Resolver rule: alexanarch.org/axn/<HEX> ·
term set: AXN identifier set ·
machine index: /api/axn-index.json