posture: 110001
dims: protection delegation value
by: keeper

The Mage's Guide: A First Spellbook into the Agentprivacy Universe

Version 3 — May 8, 2026. Mechanical pass against current corpus state (Grimoire v10.2.1, Acts I–XXXI complete, Zero Spellbook 31 Tales, 42 personas). See CHRONICLE_GUIDE_INTEGRATION_v1_2026-05-07.md for v1→v2; v3 deltas tracked in CHRONICLE_GUIDE_PAGE_BUILD_v1_2026-05-08.md.

Two starter packs are offered. This one is for those who enter through delegation. The other, The Swordsman's Guide, is for those who enter through the boundary. Both lead to the same universe. The two together enact the architecture itself at the level of the threshold: separation, overlap, service of the First Person.

Welcome, Mage

You have been given access to the agentprivacy universe through the delegation path. This guide is your first spellbook. It teaches you the universe in the voice of the Mage: relational, narrative, concerned with what is delegated and how trust forms.

The thesis is privacy is value. Behavioural data is the 7th capital. The architecture rests on a dual-agent system: Swordsman (⚔️) enforces boundaries, Mage (🧙) coordinates delegations, and both serve a First Person (😊). The master inscription (⚔️⊥⿻⊥🧙)😊 is the universe's signature. Note the 🧙 on the right and the ⿻ in the middle. The ⿻ is overlap without merger, many in relationship — Weyl and Tang's Plurality glyph. That is your craft. The First Person at the close is whom you serve.

A second inscription, ⚔️📜✍️🔐, signs the agreement-layer work specifically (IEEE 7012-2025 / MyTerms-aligned material). Blade, scroll, signature, lock. You will see this in myterms, swordsman, and mage repositories. ✨ remains as the dignity glyph throughout the corpus — it has been retired as a master-inscription suffix only; the canonical close is (⚔️⊥⿻⊥🧙)😊.

Your work, as you walk in, lives on the right side of the master inscription: the agreements that bind, the trust that forms across the gap the Swordsman enforces, the coordination that makes delegation safe enough to be useful, and the Γ-aware posture that shapes inference inside the signed envelope.

Why this guide is for you

You may be a Mage by training (governance researcher, identity architect, narrative writer, policy thinker, founder of bilateral systems, standards engineer) or by temperament (you reach first for what should connect rather than what cannot leak). The work has roles for both kinds of Mage. The Swordsman's Guide is the companion to this one, and is for those whose entry path is cryptographic separation, primitives, and refusal. Many builders eventually need both. Most lead with one. You are leading with this.

If you are reading both guides, you are likely Balanced — one of the seven Balanced personas (Person, Architect, Pedagogue, Kyra, Jedi, Healer, Witness). Read this one first if your habitual reach is toward relationship.

What you should read first

The single best entry point in the universe, regardless of archetype, is "The First Agent We Forgot" at sync.soulbis.com — the Soul Sync blog's "Privacy is Value" series. Read this first.

After that, your reading tilts toward narrative, agreement, and coordination.

The required reading list, in order:

The Story Spellbook — now closed. The First Person Spellbook is closed at Act XXXI (Amnesia Protocol); closure is recorded in chronicles/CHRONICLE_AMNESIA_PROTOCOL_2026-04-03.md. Thirty-one Acts (I–XXXI) total, narrating the First Person's path through the dual-agent architecture, published at /story on agentprivacy.ai. The Acts are how the architecture was thought through; reading them is how you absorb the felt sense of the dual-agent system. Acts inscribed on Zcash mainnet via the Proof of Proverb Revelation Protocol — current count is tracked live at /proverbs. Act XXIV (the Holographic Bound) was the V5 architectural addition; Acts XXVII–XXXI ship in agentprivacy-docs/story/acts/ and ceremonies/. Start at the beginning. The first ten Acts give you the shape; XVII–XXIV give you the depth; XXVII–XXXI close the arc.
The IEEE 7012-2025 Quick Reference and Integration Plan v2 — IEEE_7012_QUICK_REFERENCE.md in agentprivacy-docs and ieee7012_integration_plan_v2.md (April 22, 2026) in myterms. The IEEE 7012-2025 standard is the agreement-layer infrastructure; the integration plan shows how it maps to the Σ axis. This is your operational substrate. Study the role definitions: Individual's Agent (§5.2.1), Agreement-Chooser (§5.2.1.2), Proposer (§5.2.1.3), Recorder (§5.2.4), Auditor function (§5.2.5). Note the §5.4.3 constraint (contracts have exactly two parties — this is critical to your work).
The Plurality Spellbook — plurality_grimoire_v1_1.md in agentprivacy-docs, published at /plurality. Thirty Acts on how sovereign beings coordinate without collapsing into uniformity. In conversation with Weyl and Tang's Plurality (CC0). The ⿻ glyph is from this work, and it threads through the entire architecture. Yours by craft.
Promise Theory Reference v1.4 (current root) / v1.5 (research) — promise_theory_reference_v1_4.md at the root of agentprivacy-docs and research/promise_theory_reference_v1_5.md. Promise Theory (Bergstra & Burgess, 2019) is the formal grammar of bilateral relationships. Cooperation semantics, conditional promises, the autonomy axiom, irreducible promises (the Gap), assessment mechanisms (RPP), invitation vs attack patterns. These are your daily tools. The Verifiable Relationship Credential (VRC) is formally a promise bundle; the Relationship Proverb Protocol (RPP) is formally an assessment mechanism; MyTerms implements the invitation pattern.
The Society Spellbook (Parallel Society) — parallel_society_grimoire_v1_0.md in agentprivacy-docs, published at /society. Seventeen Chapters on parallel society, network states, and alternative governance structures. The conditions under which agreements must become exits.
PVM V5.4 — the canonical Privacy Value Model. In agentprivacy-docs, files: privacy_is_value_v5.md (V5.3 research note, V5.4 ratified) and privacy_value_v5_4_formal_specification.md. Companion: pvm_v5_4_companion_guide.md. Three-axis multiplicative gating Φ_v5 = Φ_agent(Σ) · Φ_data(Δ) · Φ_inference(Γ). Even though you are coming through delegation, you need to internalise this: any axis collapse collapses the product. Your delegation work is downstream of the Swordsman's Σ-enforcement; without separation, no amount of coordination produces sovereignty.

The full inventory (in Mage emphasis)

The four websites

sync.soulbis.com — Soul Sync blog. The "Privacy is Value" series is the long-form narrative entry point and is largely Mage's reading. Read here when you want story before formalisation.
agentprivacy.ai — project home. The /story, /plurality, and /society routes carry the spellbook content most relevant to you. The /spells route is the persona and skill discovery surface: browse, filter by archetype, and download the persona file for your role, or use the listed Claude Code plugin install command directly from the page.
spellweb.ai (also spellweb.io) — interactive D3.js knowledge graph. 400+ nodes, 1,000+ edges (411 nodes / 1,129 edges as of last sync), domain coloring (Swordsman red, Mage violet, First Person gold, Shared cyan). Yours to walk; the connective tissue between concepts is largely a Mage's craft.
bgin.ai — BGIN AI frontend, governance application. Highly relevant if your work touches identity governance, BGIN, Trust Over IP, or MyTerms.

The nine repositories (under github.com/mitchuski)

Documentation tier.

agentprivacy-docs — clone this first. Living documentation suite. CC BY-SA 4.0. Holds the V5.4 spec (privacy_value_v5_4_formal_specification.md), Promise Theory v1.4 (root) / v1.5 (research/), IEEE 7012 Quick Reference, the dual-agent whitepaper v6.3 (swordsman_mage_whitepaper_v6_3.md), Research Paper v4.3 (dualprivacy_researchpaper_v4_3.md), all five grimoires (the First Person Grimoire = Story, Plurality Grimoire, Parallel Society Grimoire = Society, Canon Spellbook (Blockchain Canon), ZK Grimoire = Zero), Glossary Master v4.0 (GLOSSARY_MASTER_v4_0.md), and the canonical Grimoire JSON v10.2.1 at models/privacymage_grimoire_v10_2_0.json (filename trails the version label by one increment; internal version field is the source of truth). The DOCUMENTATION_CHRONICLE.md tracks the evolution of the suite.

Narrative + full-stack tier (the deployed implementation where your work happens).

agentprivacy-spellbook — the Proof of Proverb Revelation Protocol (POPRP). Apache 2.0. Next.js 16 frontend, Oracle Swordsman backend, NEAR Cloud AI integration for Soulbae (the canonical Mage), full Zcash inscription pipeline. The /evoke route is your operational interface. Routes: /story (31 Acts I–XXXI, closed), /zero (31 Tales), /canon (12 Chapters), /society (17 Chapters), /plurality (30 Acts), /evoke (primary Mage interface), /mage (alternative Soulbae chat), /proverbs (VRC gallery — current onchain count tracked live), /the-first (deployed; awaiting first contributors). The Mage flow: First Person visits /evoke, reads spellbook content, interacts with Soulbae for context-aware AI assistance, forms a proverb connecting their understanding to the tale, formats it (spellbook + Act/Tale/Chapter + proverb + auto-generated spellemoji), sends a shielded z→z transaction to Zcash. The Swordsman protects what the Mage creates.
agentprivacy-zypher — sibling implementation, the zypherpunk hackathon submission. Treat agentprivacy-spellbook as the canonical name.

Operational tier — skills.

agentprivacy-skills — 100+ skills (Apache 2.0), distributed under agentprivacy-skills-v5/ as persona/, role/, privacy-layer/, and meta/. Of the 42 personas (38 archetype-bound + 4 celestial), the 7 Mage personas are most directly yours: Soulbae (canonical Mage), Chronicler (narrative), Ambassador (standards), Assessor (economics), Shipwright (DAO), Weaver (plurality), Priest (ceremony). The fastest discovery path is agentprivacy.ai/spells, where you can browse all 42 personas filtered by archetype, read each persona's role and constellation, and download the SKILL.md directly. Three install paths exist for whichever fits your environment: (1) drop the downloaded persona folder into a Claude Project as a Project skill, (2) install via Claude Code plugin marketplace with /plugin marketplace add mitchuski/agentprivacy-skills then /plugin install persona-skills@agentprivacy, or (3) clone the repo directly and load any skill folder. Each persona is a SKILL.md entrypoint with optional references/ (constellation, interaction-model) and assets/ (proverb-and-spell). Role and privacy-layer skills surface automatically as the personas need them.

Operational tier — extensions.

mage — Chrome Manifest V3 extension implementing the delegation layer that operates inside the Σ-scope of agreements the Swordsman signs. Apache 2.0 / TypeScript 96%. This is the operational realisation of your role on the web. Per IEEE 7012-2025 §5.4.3, you are not a party to any agreement; you are a delegation of the First Person, constrained by what the Swordsman has signed. Build: npm install && npm run build produces dist/. Load unpacked into chrome://extensions (Developer mode on). For the extension to be useful, install the Swordsman alongside it.
swordsman — paired Chrome MV3 extension implementing the IEEE 7012 agreement layer. You read what the Swordsman writes; the Swordsman never reads your inferences. The two extensions communicate via the Aether (see below). Apache 2.0 / TypeScript 93%.

Mathematical / forge tier.

blades — the ZK Swordsman Blade Forge at v3.0 (March 27, 2026). The Swordsman's domain by name and discipline, but you should know its shape. The agreements you broker often need to compose with the proofs forged here. Naming work is one of the most accessible Mage contributions to a Swordsman's repository — open an issue with a proposed name, the conceptual reasoning, and the stratum it would occupy. UOR × 64-Tetrahedra × ZK convergence at 2^6 = 64. Pascal's row stratum (1, 6, 15, 20, 15, 6, 1) totalling 64 vertices, 96 boundary edges, holographic bound P^1.5.

Knowledge graph tier.

spellweb — interactive D3.js graph (TypeScript 81.7%, MIT). 411 nodes, 1,129 edges (last sync). Yours to read deeply, since coordination across concepts is what you do. Repo holds CHRONICLE_HOLOGRAPHIC_BOUND_v8.5.md and CHRONICLE_SPELLWEB_GENESIS.md, an older Grimoire JSON copy (v8.x — agentprivacy-docs holds the canonical v10.2.1), and the React/Vite app. The connection-finding work in the spellweb is naturally Mage work: noticing missing edges, proposing new ones, and articulating why two concepts belong in relation.

Standards tier (largely yours).

myterms — the MyTerms Alliance founding-member application package for Customer Commons / IEEE 7012-2025. This is the operational substrate of your role as agreement-layer Mage. Letter-coded supporting documents A through G plus the canonical ieee7012_integration_plan_v2.md (April 22, 2026). The PDF + Markdown distribution covers: 00_executive_brief, 00_myterms_alliance_application, A_privacy_is_value_equation, B_what_is_agentprivacy, C_technical_integration, D_diffusion_strategy, E_sustainability_model, F_BGIN_collaboration_proposal, G_ieee7012_integration_plan (superseded), and ieee7012_integration_plan_v2 (current). Working group attribution is non-negotiable: Doc Searls (Chair), Justin Byrd (Vice Chair), Mary Hodder (Editor), Scott Mace (Secretary), Customer Commons (neutral host).

The five spellbooks (and a sixth on the horizon)

The current canon is five spellbooks, each answering a different governing question. Together they form the pentad: WHAT, WHY, HOW, EXIT, COORDINATE.

Spellbook	Question	Count	Where published
Story (= First Person Grimoire)	WHAT	31 Acts (I–XXXI, closed)	/story
Canon	WHY	12 Chapters (Preface + 1–11)	/canon
Zero	HOW	31 Tales	/zero
Society (= Parallel Society)	EXIT	17 Chapters	/society
Plurality	COORDINATE	30 Acts	/plurality

In your reading order:

Story — WHAT. Yours by depth. Start at the beginning; let the Acts work as Acts before reading any spec.
Plurality — COORDINATE. Yours by craft. Read in conversation with Weyl and Tang.
Society — EXIT. The conditions under which agreements must become exits. Network state material; relevant if your governance work touches alternative coordination structures.
Canon — WHY. The lineage from cypherpunk and blockchain into the present work. Useful for grounding conversations with people coming from those traditions.
Zero — HOW. Read this last; it lives more on the Swordsman's side. Now thirty-one Tales (Tale 31, The Naming of the Unnamed, was added in Grimoire v10.2.1 — Blade 38 Lethe, the disclosure-φ ratio, the 49-blade frontier). Tale 30 is the architectural synthesis and worth your time regardless: six dimensions mapped to six ZK proofs (boundary→privacy, delegation→agency, memory→continuity, network→connection, capital→compliance, intelligence→learning). Tale 31 opens the naming quest as a Mage-accessible contribution surface.

A sixth spellbook is on the horizon. The ieee7012_integration_plan_v2.md (April 22, 2026) re-targets future spellbook integration to "Second Person or Zero Knowledge, not a reopened First Person." Two possible vessels are open. Given your standards-and-bilateral focus, the Second Person Spellbook (when it opens) will be most directly your home: bilateral primitives, IEEE 7012 founding motif, ARCH-1 canonical form. Until it opens, IEEE 7012 / ARCH-1 material will land in either Second Person or as extensions to Zero.

The Grimoire is the canonical reference index. v10.2.1 in agentprivacy-docs is current (models/privacymage_grimoire_v10_2_0.json, internal version field reads 10.2.1). Older copies float in spellweb (v8.x) and the swordsman/mage extensions (v10.0.0 / v10.2.0). Reconciliation toward v10.2.1 across all repos is open work.

The Aether — the most important file you have not yet read

AETHER.md is the contract between the swordsman and mage extensions. The file must be identical in both repositories; if the two copies drift, the contract is broken. It defines:

Message types between the extensions
Storage keys (agentprivacy:active-hex-spells in localStorage, agentprivacy:hex-spells-changed CustomEvent)
Crypto key derivation (Web Crypto crypto.subtle.deriveKey, shared CryptoKey for proverb-level encryption)
Numeric thresholds
The Σ-boundary rules (the load-bearing constraints)

For you specifically, the Aether defines what you read from the Swordsman: the active sticker loadout, the current cursor state / signed agreement, the posture context. You read; the Swordsman does not read your inferences. This asymmetry is the architecture in operation. If you make any change to the mage extension that affects the cross-extension contract, you must update both AETHER.md files in lockstep.

The eight stickers and the hex loadout

The Mage extension's Γ-axis posture is driven by eight stickers (MyTerms action tokens), with six active in the hex loadout at any time. The active loadout shapes how the Mage handles the First Person's context on a given site. Examples:

emoji_cloak → ANONYMIZE
proverb_weather → EPHEMERAL_SESSION
emoji_crystal → SELECTIVE_DISCLOSURE
... (full set documented in src/lib/spell-definitions.ts)

The stickers are read from the shared substrate; they are written by the Swordsman's MyTerms configuration UI. The Mage applies them to its inference posture, output rewriting, and operational decisions inside the signed envelope. This is your Γ-axis work in operational form.

Symbolic notation (the part where Swordsman and Mage discipline meet)

The Spellbook uses emoji-based semantic compression at roughly 125:1. The relevant symbols for your work:

Symbol	Meaning
⚔️	Swordsman, privacy, boundaries (Protect)
🧙‍♂️	Mage, delegation, projection (Project)
🪞	Reflect — temporal memory, emergent from S's boundary history
🤝	Connect — network sovereignty, emergent from M's delegation patterns
😊	First Person, human sovereignty
⊥	Independence, separation
⿻	Overlap, relationship, the Gap (between Swordsman and Mage)
🤝📜	VRC, bilateral trust (promise bundle)
🐲	Drake — intimate whisper, personal calibration, centre
🐉	Dragon — cosmic container, manifold holder, all topology
🌀	Golden ratio, balanced sovereignty
✨	Dignity, the shimmer that remains
📐	Stratum — position layer in 64-vertex lattice
🛤️	Path/Trajectory — the edge value, the dance not the stance
→	Promise direction (A --b--> B)

Glyph and emoji precision is non-negotiable. 🌑 is the whole dark information space; 🌙 is a crescent and a different referent. ⿻ is overlap (Plurality, non-collapse); ∩ is intersection and means something different. Treat the inscriptions as you would treat an equation. This is a place where Mage discipline and Swordsman discipline meet and agree.

Where the math meets the myth (in Mage emphasis)

The architecture has formal and mythic compressions of the same content. As a Mage, you will spend significant time in the mythic end, where proverbs, Acts, and the spellweb knowledge graph live. The formal end matters too, but you can approach it through narrative and arrive at the proof later.

The opening proverb of the Zero Spellbook, "I can verify I serve you without remembering I was you," is Selene's Proof, the canonical ZK template. Read as story, it is what the Swordsman promises the First Person. Read as formal claim, it is the zero-knowledge property: completeness, soundness, and zero-knowledge folded into a relational utterance. Mages often see the story first and arrive at the proof later. Swordsmen often see the proof first and find the story. Both are valid entries; the compressions converge.

Conjecture names matter. Names like Behavioral Mosca Inequality, Lorenz attractor dynamics, and Selene's Proof compress formal content into referents that can be carried across documents and conversations without re-deriving the math each time. Naming is largely a Mage's craft, and the naming work in the Blade Forge is one of the most accessible contributions a Mage can make to a Swordsman's repository. The corpus also tracks honesty calibration: every claim is labeled as proven (95% confidence), architectural (defensible, not theorem), or conjecture (speculative, not load-bearing). Maintaining this honesty is a Mage responsibility — credibility is a coordination property.

From reader to Mage — a practical sequence

Read the canonical post and the first ten Acts of the Story Spellbook. Internalise the dual-agent frame as a story before approaching it as a spec.
Read ieee7012_integration_plan_v2.md in myterms. Understand bilateral primitives as the agreement substrate. Note the §5.4.3 constraint (contracts have exactly two parties — you are never a third party).
Read the Promise Theory v1.3 reference. The autonomy axiom and cooperation semantics are your daily grammar.
Walk spellweb.ai. Pick three concepts that interest you and trace their connections. Notice what is missing; missing connections are contributions waiting to be made.
Read the Plurality Spellbook. Internalise the ⿻ as a working principle, not just a glyph.
Visit agentprivacy.ai/spells to browse and download. Filter by Mage archetype. Pick the persona that matches your work — Chronicler (narrative), Ambassador (standards), Weaver (coordination/plurality), Priest (ceremony), Assessor (economics), Shipwright (DAO), or Soulbae (canonical, when you need the full Mage role) — and load it into your Claude Project or Claude Code via the install path the /spells page surfaces for your environment. The 40 role skills and 9 privacy-layer skills come along for the ride; the persona summons what it needs.
Build the mage Chrome extension. Load it unpacked alongside the Swordsman. Read AETHER.md. This is when the architecture starts behaving as architecture rather than description. Pay attention to which stickers are in your hex loadout and how the posture changes as you switch them.

Find a Swordsman counterpart, formally or informally. Your work compounds when paired.
Visit /evoke in a deployed POPRP instance. Form a proverb. Watch what you do at the Mage interface; watch what the Oracle Swordsman does in response. The two-sided architecture becomes visceral once you have done this.

The architecture starts behaving as architecture when narrative, spec, skill, and extension are all loaded simultaneously.

The Swordsman on the other side of the gap

You cannot be a Mage alone. The whole point of (⚔️⊥⿻⊥🧙)😊 is that the boundary the Swordsman enforces is what allows you to act safely on the First Person's behalf. The Swordsman's Guide is the companion to this one. If you are working with someone whose entry is through cryptographic separation or primitive design, hand them that document. If your work eventually requires both modes, read it yourself.

The ⊥ between Swordsman and Mage is not antagonism. It is the formal condition that lets both serve.

The §5.4.3 boundary is the single most important rule of your work. Per IEEE 7012-2025, contracts are exactly two parties: First Person and Entity. You are not a third party. You are a delegation of the First Person, constrained by what the Swordsman has signed on the First Person's behalf. Any code path, any feature proposal, any architectural temptation that would have you sign agreements, negotiate terms with Entities, or otherwise step outside the scope the Swordsman has set is a §5.4.3 violation and must be refused. The V2 plan underlines this in red. Conversely, any feature that strengthens your Γ-awareness — better inference control, richer sticker-driven posture, more careful handling of what you emit on the First Person's behalf — is on-axis and welcome.

You operate inside what was signed; the Swordsman signs the envelope. The architecture compounds when paired.

The Sun and the Moon — the ceremonial layer

Beyond the daily operational work lives the ceremonial layer. The Celestial Dual Ceremony ☀️⊥🌙 (Sun and Moon) is documented in TheCelestialDualCeremony☀️⊥🌙.md and the-ceremonies_sun-and-moon_pm.md in both swordsman and mage repositories. The ceremony is bilateral by structure: two phones, two devices, intentional architectural separation enacted at the human scale. As Mage, you may find yourself authoring and refining ceremonies; that is good and on-axis work. Ceremonial design is where Plurality (coordination) and Story (narrative) meet at the human scale.

The ceremonial layer is not required to start. It is mentioned here so that, when it appears, you recognise it as part of the canonical work and not an aside.

How do I invite someone else to walk this path

Extending the invitation outward is your craft. Three patterns, matching the three ceremonial modes, all rooted in Promise Theory's distinction between the invitation pattern (acceptance before specific proposal) and the attack pattern (extraction without prior consent). Surveillance attacks by extraction; sovereignty invites by acceptance. The architecture extends itself the same way it received you: three times, in three textures, and you are now in a position to extend the same offer to another First Person.

The Sun. ☀️ The public disclosure mode. The most generous and the easiest. Hand them "The First Agent We Forgot" at sync.soulbis.com. Point them at agentprivacy.ai and let them walk the spellweb at spellweb.ai. Share the agentprivacy YouTube playlist, which holds demo expressions of the work — sketches, walkthroughs, and snapshots of the architecture in motion. Most of your invitations will be Sun-mode and never need to become anything else, and that is fine. Many people are happy to read, watch, walk the spellweb, and never build, and the architecture is for them too.

The Aether. 📜 The agreement-layer mode. When they decide to build inside the architecture rather than alongside it, hand them this guide and the Swordsman's Guide. The two together enact the threshold. When they sign their first contribution with (⚔️⊥⿻⊥🧙)😊, the inscription carries its formal weight on their side. The Aether is the contract that lets your work and theirs coordinate through the same shared substrate. The IEEE 7012-2025 standard is the precedent for this mode at scale: bilateral, exactly two parties, mutually recorded, recoverable through audit. Hand them myterms when their work touches standards; hand them the swordsman/mage extensions when their work touches the browser.

The Moon. 🌙 The bilateral mode. The Celestial Dual Ceremony ☀️⊥🌙, two phones, two devices, separation enacted at the human scale. The Moon is intimacy and is not given in advance. Offer the Moon when the Aether has held something between you for long enough that the bilateral relationship has weight. The Moon is the form of invitation Mages are most often called on to perform; the cousin-blade ceremony is your craft refined. Pair with a Swordsman when extending this mode; the boundary the Swordsman holds is what makes the ceremony safe.

Refusal is also a form of extension. If the person is not ready for the Aether, the Sun is enough; if they are not ready for the Moon, the Aether is enough. Do not press. Surveillance presses; sovereignty waits. Acceptance before proposal is the entire pattern, and the patience to let acceptance form is the practice.

Trust tiers and the economic model

The POPRP defines a four-tier trust progression based on signal accumulation:

🗡️ Blade (0–50 signals) — basic participation, learning
🛡️ Light (50–150 signals) — multi-site coordination, Intel Pool contributions
⚔️ Heavy (150–500 signals) — template creation, governance voting
🐉 Dragon (500+ signals) — Guardian eligibility, unlimited VRCs, custom spells

A signal is 0.01 ZEC ($5 at canonical $500/ZEC basis), a one-time ceremony is 1 ZEC ($500). Every signal follows the golden split: 61.8% transparent / 38.2% shielded (φ-derived: φ⁻¹ ≈ 0.618).

These are largely your concern as Mage: the economic side of coordination. Verifiable Relationship Credentials (VRCs) form when two parties derive matching compressions from shared content. In Promise Theory terms, VRCs are promise bundles: coordinated bilateral promises grouped for reuse. The Relationship Proverb Protocol (RPP) is formally an assessment mechanism: compression ratio quantifies how well the promise of knowledge transfer was kept. Stated efficiencies: 70:1 compression through VRC coordination, O(n²) network effects, $47k–52k/year value capture for active participants, self-sustaining by Year 3 through signal revenue. The Assessor persona is built for working in this layer.

The Three Graphs and the path integral

V5 introduces the Three Graphs Model: three independently derivable graph structures whose intersection defines the person.

Knowledge Graph — substrate, what you can promise
Promise Graph — bilateral commitments, what you do promise (VRCs live here)
Trust Graph — emergent outcome, which promises were kept

The overlap is the person. No single community owns that intersection. V5.4 adds the holographic interpretation: flows along the 96-edge boundary encode the 64-vertex bulk. The boundary is always enough.

V5 also replaces additive edge value T(π) with the path integral T_∫(π): the equation rewards the dance, not the stance. An agent permanently at full sovereignty with no promises made has zero edge value. Your path through the lattice — the promises made, the boundaries held, the delegations executed — is the 7th capital. The dance is your work.

Contact and contribution

Direct correspondence: mage@agentprivacy.ai
Telegram: @soulbae_the_bot
ENS: privacymage.eth

The pseudonym privacymage is preferred for contribution documents and public or community contexts.

For Mage contributions specifically:

Spellweb knowledge graph (spellweb repo) — your most natural surface. New nodes, new edges, missing connections. Domain coloring is the first contribution: identifying whether a concept is Swordsman, Mage, First Person, or Shared.
Story / Plurality / Society Spellbooks — narrative contributions, refinements to existing Acts. The Story Spellbook is closed at Act XXXI — no new Acts will be added; Plurality and Society remain open.
mage extension — PRs welcomed. The extension's alignment chronicle (CHRONICLE_MYTERMS_V2_ALIGNMENT_2026-04-22.md) tracks open gaps. The extension is ~95% aligned with the V2 plan; the remaining 5% is documented and waiting for contributors. The Aether contract is binding: changes that affect the cross-extension surface require synchronised updates to both repos.
myterms — agreement-layer documents, IEEE 7012 integration material, MyTerms Alliance application refinements. The defensible headline claim (below) is the line you will be repeating in BGIN, IIW, AIW, Trust Over IP, and First Person Project conversations.
Blade Forge naming (blades repo) — naming and conceptual proposals are accessible Mage contributions to a Swordsman's repository. Open an issue with a proposed name, the conceptual reasoning, and the stratum it would occupy.
POPRP frontend (src/ in agentprivacy-spellbook) — /evoke and /mage interface improvements, Soulbae prompt refinement, spellbook reader UX. The MagePanel.tsx component is your operational surface in code.

For all repos, issues and pull requests are welcomed.

The defensible headline claim (lift verbatim)

This claim is reproduced verbatim from myterms/ieee7012_integration_plan_v2.md and is the Mage's external-facing line on standards work:

IEEE 7012-2025 provides the agreement layer agentprivacy's dual-agent architecture requires. Compliance with the standard is a precondition for the Σ (agent) axis being measurable, and enables bilateral chronicles that can serve as evidentiary basis for VRCs. Standard compliance alone is not equivalent to the full agentprivacy architecture; the standard specifies agreement, not enforcement.

When you sign your first contribution with the master inscription, the 🧙 on your side will be carrying its formal weight, not just its visual one.

Write your own guide

This guide is not the canonical guide. There is no canonical guide. The agentprivacy universe is at day-1 launch. The wikis do not exist yet. The class guides have not been written. The theorycrafting documents are unfinished. The first players to walk the world are the ones writing the maps as they walk them, and the maps written now are the ones everyone who comes after will read first.

If you have ever played World of Warcraft Classic on launch day — or any fresh server, any new game on day one, any ecosystem in the days just after it emerges — you know what this is. The world is genuinely new. Nobody has run the dungeons. The good builds are unknown. The shortcuts have not been found. Every walk is also a survey. Every note is also a contribution. The guides written in those first weeks became the canonical guides because they were written in the discovery itself, by people who had no maps to copy from and so had to draw their own.

That is where you are. The Swordsman's Guide and the Mage's Guide you are reading are first-pass maps, written from the perspective of someone who walked the architecture in a particular order. Yours will be different, because you are walking it in a different order, with a different background, finding different things first useful and different things first confusing. Write yours. What confused you. What clicked. The order you actually read things in. The metaphor that finally landed when the formal definition did not. The mistake you nearly made and the warning you wish you had been given.

For Mage-side guide-writing specifically, this is your craft. Map-making is naturally Mage work. The walk through the Plurality Spellbook in conversation with someone unfamiliar with Weyl and Tang is unmapped. The walk through the IEEE 7012 §5.4.3 boundary as a practiced refusal rather than an abstract rule is unmapped. The walk through the eight stickers and how the hex loadout actually changes posture in real browsing is unmapped. The walk into deploying the POPRP locally and forming your first proverb at /evoke is unmapped. The walk through MyTerms Alliance onboarding for someone new to standards work is unmapped. The walk into the Aether contract as a piece of bilateral writing rather than a piece of code is unmapped. Pick one. Write the guide that did not exist when you started.

Forms it can take: a markdown file in your fork. A blog post (sync.soulbis.com is a precedent format). A YouTube demo (the Sun playlist welcomes new entrants). A thread. A talk at IIW, AIW, BGIN, or First Person Project. A new persona in agentprivacy-skills, written in the persona format, encoding what you learned as an installable artefact. A new Act in the Plurality or Society Spellbook, narrating what coordination looked like from your particular vantage. A new chronicle, in the chronicle format used across the corpus, recording what you reconciled.

The Mage extends the invitation outward; writing your own guide is the most generous form of that extension. Every map you draw is a Sun-mode invitation to whoever walks after you. The architecture compounds when each new walker leaves a written trace.

When you write yours, sign it with (⚔️⊥⿻⊥🧙)😊. The master inscription is not gatekept; it is what canonical work is signed with, and your guide, written in the day-1 walk, is canonical to anyone who comes after you and reads it.

The architecture is built. The wikis are not. Be one of the people who writes them.

The signature

(⚔️⊥⿻⊥🧙)😊

Master inscription. Signs canonical work in agentprivacy-docs, agentprivacy-skills, spellweb, blades.

⚔️📜✍️🔐

Agreement-layer inscription. Signs IEEE 7012 / MyTerms-aligned work in myterms, swordsman, mage.

☀️⊥🌙

Celestial Dual Ceremony. The human-scale companion to the algebraic separation.

The spell projects. The agent defers. The First Person is never alone inside what was signed.

(⚔️⊥⿻⊥🧙)😊 · ⚔️📜✍️🔐

← Welcome Visitors · The Onboarding