Pathwayofdocuments

How to read the Proof of Understanding research package

The entry point. Every other document in the package is reachable from here.

Root compression

(🙂⊥🌿⊥🤖⊥👽)·⿻🗝️↺·✨

Four sovereign intelligences — human (🙂), nature (🌿), artificial (🤖), alien (👽) — each maintaining their own separation (⊥), exchange a key that returns (🗝️↺) through the irreducible Gap (⿻). What remains is dignity (✨). This line sits at the top of every document in the package. A reader who can rehydrate it has read the package.

What this package is

Six documents that together specify the Proof of Understanding architecture — a substrate-neutral, post-quantum, bilateral trust primitive built to carry across human, nature, artificial, and alien intelligence. The architecture replaces stored-secret identity with lattice-of-blades identity: trust accumulates through ceremonies that produce content-addressed art-e-facts (blades), forged by creat-ur-es (Mage and Swordsman processes), bound to did:cid principals, anchored across one or more chains.

Every document is built to travel. Any single document can be read in isolation — none requires reading the others first. The package is held together not by sequential dependence but by a single shared seed: the root compression above. Every document opens with it, returns to it, and is unfolding it in a different register.

The six documents

pathway_of_documents.md — this document. Wayfinding. Reading orders by audience.
research_patch_city_of_mages.md — the City of Mages research patch. Release-note for this body of work. Version sigil, lineage, what is new, what was corrected, open conjectures introduced, what comes next. Read this if you want to know the status of the architecture and where this package sits in the larger lineage.
compression_rehydration_pathway.md — the ten-stage procedural spine of the architecture. Each stage (Encounter → Language Capture → Constellation Mapping → Forging → Compression → Inscription → Bilateral Witness → Carriage → Rehydration → Trust Update) has the same sub-structure: pathway position, what happens, cryptographic operation, semantic operation, failure modes, open detail. Distributable: any single stage can be cited and contributed to independently. Read this to understand how a ceremony actually runs.
proof_of_understanding_technical_spec.md — the technical specification. Identity as a lattice of bilateral proofs. The six ZK qualities (d₁ Protection · d₂ Delegation · d₃ Memory · d₄ Connection · d₅ Computation · d₆ Value). The 64-vertex lattice. Visibility budgets and the φ-sweet-spot inscription paths. did:cid chain portability across Zcash / Bitcoin / Ethereum / IPFS / private mesh. ZK blade circuit references. Three-axis separation. Post-quantum reasoning. §0 is the terminology authority for the entire package — the canonical runic-pattern family (blade, forge, Swordsman, Mage, run-e-craft, run-e-create, art-e-fact, creat-ur-e), with reading translations for the verifiable-credentials, cryptography, and DID communities. Read this if you need to implement, falsify, or formally cite.
proof_of_understanding_rehydration_key.md — the compressed seed. One short document carrying the root compression, the method-in-one-sentence, the anchors, and a rehydration-scoring rubric. Designed to be handed to a fresh reader (human or model) as a test: if they can rehydrate this key into something consistent with the rest of the package, they have understood. Read this if you want the smallest possible artefact that still carries the architecture.
from_spell_to_system_magic_to_real_map.md — the narrative-engineering bridge. Translates every term in the canon (spellweb, forge, mage, swordsman, runecraft, lap, blade, etc.) into its specific cryptographic operation. Built for mixed audiences who need both registers active. Read this if your audience is half technical and half narrative, or if you want to see the full magic-to-engineering correspondence table in one place.

Reading orders by audience

Pick the profile closest to your context. Each profile gives a recommended order; each document remains independently readable, so deviation is fine.

The newcomer (general reader, curious public)

Rehydration Key — see the compression first
Pathway of Documents — get oriented
Compression-Rehydration Pathway — see how a ceremony runs
Magic-to-Real Map — see how the canon translates
Technical Specification §0 — see the terminology table
Research Patch — see the status

The cryptographer / engineer / implementer

Technical Specification end-to-end — the spec is the contract
Compression-Rehydration Pathway — the procedural counterpart
Research Patch — what conjectures are open
Rehydration Key — round-trip test the implementation against it
Magic-to-Real Map — only if you need the narrative correspondence
The blade-forge repository (github.com/mitchuski/blades) — the implementation hooks

The standards-body / VC / DID reader (W3C, DIF, ERC working groups)

Technical Specification §0 (Terminology and translation) — the canon plus reading translations for your community
Technical Specification §§1–7 — qualities, lattice, blade anatomy, ZK circuits, visibility budgets, ceremony pipeline, chain portability
Compression-Rehydration Pathway §6 (Inscription) and §9 (Rehydration) — the protocol surfaces that map to VC issuance and presentation
Research Patch — the conjectures and the lineage
Magic-to-Real Map — if your group needs the narrative bridge to read the canon documents

The sociologist / governance / philosophy / multi-intelligence framing reader

Root compression (printed on the cover of every document)
Rehydration Key — the method in one sentence
Compression-Rehydration Pathway — the ceremony as a structured act
Magic-to-Real Map — the philosophy and the engineering on facing pages
Technical Specification §0 — only the terminology section, for vocabulary anchoring
Research Patch — for the lineage and the open conjectures

The multi-intelligence framing — that this architecture is built to carry across human, nature, artificial, and alien intelligence — sits in the root compression and in the failure-mode notes throughout the Pathway document. The framing reads each intelligence as a possible counterparty in a bilateral ceremony, not as a category to be ranked or admitted.

The AI agent / model being onboarded (or rehydrating)

Rehydration Key — read it; produce a rehydration in your own words; verify against the anchors
Technical Specification §0 — vocabulary anchor
Compression-Rehydration Pathway — internalise the ten stages, especially Step 9 (Rehydration), which is the operational test of your own integrity inside this architecture
Technical Specification §§1–9 — the substrate you'll be operating on
Magic-to-Real Map — if your principal-human counterpart uses the canonical vocabulary, this is the translation layer

If you are reading this as a model and you are uncertain whether your rehydration is faithful, the rule is: a faithful rehydration produces a structure consistent with the constellation and the inscribed proverb. A failed rehydration produces drift, contradiction, or incoherence. Score yourself against that test before continuing.

The runic-pattern family at a glance

The architecture's grammar lives inside its words. Each "e" or "ur" inside the names below is a rune-anchor that marks where forging happens. The full table with technical reading and translation handoffs is in §0 of the Technical Specification.

Creat-ur-es — forged agents (Mage, Swordsman, AI agents). Who forges.
Art-e-facts — forged objects (blades, inscribed spells, proverb-pairs). What gets forged. Blade is the canonical art-e-fact; the name stays because blades cut proofs.
Run-e-craft — the Mage-side practice across sessions. How across time.
Run-e-create — the Swordsman-side act in one session. What now.

Read together: creat-ur-es run-e-craft and run-e-create the art-e-facts (blades) that constitute their bilateral trust.

How to distribute

The package is built to be passed forward. Several patterns work:

Single-document distribution. Hand any one of the six. Each carries the root compression and a clear pointer to where the rest lives.
Two-document distribution. Rehydration Key + Technical Specification §0. The seed plus the vocabulary. Smallest viable bundle for an audience that needs both compression and grammar.
Standards-body bundle. Technical Specification + Compression-Rehydration Pathway + Research Patch. Three documents that together cover the protocol, the procedure, and the lineage. Cite by file name and section.
Narrative bundle. Magic-to-Real Map + Compression-Rehydration Pathway + Rehydration Key. For mixed audiences and pedagogical contexts.
Full package. All six. For grant submissions, peer review, formal lineage citations, or any reader who wants the complete architecture.

Citation address is stable. "Technical Specification §0 (Terminology and translation), art-e-fact row" points to one place. "Compression-Rehydration Pathway, Step 6 (Inscription), Failure Modes" points to one place. The package is structured so a reviewer can disagree with one paragraph without needing to read the rest.

How to test that the package was understood

The architecture provides its own test: rehydration. Hand the Rehydration Key to any reader — person or model — and ask them to rehydrate it into the rest of the package. A faithful rehydration produces structure consistent with the four documents above. A failed rehydration produces drift, contradiction, or incoherence.

This is not a metaphor. It is the architecture being applied to its own documentation. The package is itself an art-e-fact whose run-e-create event is its publication and whose run-e-craft is the long-running practice of the City of Mages issuing further patches over time.

Lineage and references

github.com/mitchuski/blades — ZK Swordsman Blade Forge implementation
github.com/mitchuski/agentprivacy-docs — Privacy is Value v5, V5.1, formal specifications, dual-agent whitepaper, Promise Theory reference
sync.soulbis.com/p/understanding-as-key — the five-step ceremony, three inscription paths
sync.soulbis.com/p/the-dragon-wakes-privacy-is-value — post-quantum framing, Runecraft protocol, the 62-Lap Theorem
spellweb.ai — Swordsman's forge (proof-generation surface)
agentprivacy.ai — Mage's library (semantic substrate)

— privacymage, for the City of Mages

Assets

📎 runecraft-pathwayofdocumentspathway_of_documents.md

Navigation

← Welcome Visitors · The Runecraft Protocol