posture: 110010
dims: protection delegation computation
by: keeper

The Swordsman'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 the boundary. The other, The Mage's Guide, is for those who enter through delegation. 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, Swordsman

You have been given access to the agentprivacy universe through the boundary path. This guide is your first spellbook. It teaches you the universe in the voice of the Swordsman: structural, terse, concerned with separation.

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 ⊥ between Swordsman and Mage. That is your domain. The separation is the architecture.

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 left side of the master inscription: the Σ axis (agent separation), the cryptographic primitives, the agreements that hold so the Mage can act safely on the First Person's behalf.

Why this guide is for you

You may be a Swordsman by training (cryptographer, security engineer, ZK researcher, identity architect, standards engineer) or by temperament (you reach first for what cannot leak rather than what should connect). The work has roles for both kinds of Swordsman. The Mage's Guide is the companion to this one, and is for those whose entry path is delegation, coordination, governance, or narrative. 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 structure.

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 separation, primitives, proofs, and standards.

The required reading list, in order:

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. Sit with the multiplicative gating formula Φ_v5 = Φ_agent(Σ) · Φ_data(Δ) · Φ_inference(Γ). Σ is your axis. Failure on any axis collapses the product, so failure on Σ collapses the entire system regardless of what the other axes do. Path integral T_∫(π) replaces additive edge value: the architecture rewards the dance, not the stance.
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. The autonomy axiom is the load-bearing beam of the entire architecture: "An agent can only make promises about its own behavior. No agent can make a promise on behalf of another agent." This is why the Swordsman cannot be replaced by a single agent that pretends to do both jobs. Your role is irreducible. The Gap is formally an irreducible promise of the superagent (First Person + Swordsman + Mage); it emerges from cooperation but cannot be attributed to either agent individually.
The Zero Spellbook (Soulbis's domain) — zk_grimoire_v3_0.md in agentprivacy-docs, published at /zero on agentprivacy.ai. Thirty-one Tales (Tale 31, The Naming of the Unnamed, was added in Grimoire v10.2.1 — Blade 38 Lethe named as complement of Blade 25 Aletheia, disclosure-φ ratio 38/63 ≈ 1/φ, Two Waters introduced) organised into seven parts: I Formation, II Propagation, III Backend Harmonics, IV Resonance, V Navigation, VI Transcendence, VII The Infinite Grid. Soulbis is the canonical Swordsman; Zero is your spellbook. Opening proverb: "I can verify I serve you without remembering I was you." This is Selene's Proof, the canonical ZK template. Closing: the Eight Lines (Four inherited from the Amnesia Protocol + Four naming-quest lines added at v10.2.1). Tale 30 maps six dimensions to six ZK proofs (boundary→privacy, delegation→agency, memory→continuity, network→connection, capital→compliance, intelligence→learning); Tale 31 opens the 49-blade frontier as the Quest of the Unnamed Faces.
The Story Spellbook — now closed. chronicles/CHRONICLE_AMNESIA_PROTOCOL_2026-04-03.md records closure at Act XXXI (Amnesia Protocol). Thirty-one Acts (I–XXXI) total, narrating the First Person's path through the dual-agent architecture, published at /story on agentprivacy.ai. 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/. The First Person Spellbook will not be reopened — new material lands in Second Person or as Zero extensions. Read enough to know whom you are protecting.
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 agreement layer maps primarily to your axis. Standard compliance is a precondition for measurable Σ — not a substitute for the dual-agent architecture.
The ZK Swordsman Blade Forge v3.2 (March 31, 2026) — in the blades repository, also mirrored as zk_swordsman_blade_forge_v3_0.md in agentprivacy-docs (filename retains the _v3_0 suffix; the document header reads v3.2, V5.4 UOR Algebraic Foundation). UOR (Universal Object Reference) × 64-Tetrahedra Lattice × Zero Knowledge Proofs converge at 2^6 = 64. Blades are ZK statements; forgings are witnesses; the lattice is the forge. Pascal's row stratum: 1 + 6 + 15 + 20 + 15 + 6 + 1 = 64 vertices. 96 boundary edges over 64 bulk vertices yields the holographic bound P^1.5. With Tale 31 / Blade 38, the 49-blade naming frontier is now open. This is where your work will most likely live.

The full inventory (in Swordsman emphasis)

The four websites

sync.soulbis.com — Soul Sync blog. The "Privacy is Value" series. Read anything on separation, primitives, and cryptographic boundaries first.
agentprivacy.ai — project home, architecture overview. The /story and /zero 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 includes Swordsman (red) — your concepts are colour-coded for navigation.
bgin.ai — BGIN AI frontend, governance application. Relevant if your separation work touches identity governance.

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, 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). audits/V5_AUDIT_CHECKLIST.md is your Swordsman's check on V5 alignment.

Narrative + full-stack tier (the deployed implementation you will protect).

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, full Zcash inscription pipeline. Routes: /story (31 Acts I–XXXI, closed), /zero (31 Tales), /canon (12 Chapters), /society (17 Chapters), /plurality (30 Acts), /evoke (primary Mage interface), /proverbs (VRC gallery — current onchain count tracked live). The Oracle Swordsman backend is the operational instance of your role: transaction monitoring, viewing-key memo decryption, AI verification (privacy-preserving — never sees amounts or addresses), golden-split (61.8/38.2) calculation, onchain inscription. Read oracle-swordsman/src/ to see how the role is implemented in code.
agentprivacy-zypher — sibling implementation, the zypherpunk hackathon submission. The README is functionally identical to agentprivacy-spellbook. 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 8 Swordsman personas are most directly yours: Soulbis (canonical Swordsman), Cipher (ZKP), Warden (browser), Gatekeeper (personhood), Sentinel (infrastructure), Sith (red team), Ranger (dark forest), Archer (precision). 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.

swordsman — Chrome Manifest V3 extension implementing the IEEE 7012-2025 agreement layer. Apache 2.0 / TypeScript 93%. This is the operational realisation of your role on the web. The extension implements: 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). It runs on <all_urls> at document_idle. Build: npm install && npm run build produces dist/. Load unpacked into chrome://extensions (Developer mode on). Repository content includes 64_blades_reference_sheet_2426.md (your blade index), TheCelestialDualCeremony☀️⊥🌙.md (Sun/Moon ceremony), the-ceremonies_sun-and-moon_pm.md, CONTROL_SCHEME.md and DUAL_CONTROL_SCHEME.md, the canonical Grimoire JSON v10.0.0 / v10.2.0, and the alignment chronicle with myterms v2.
mage — paired Chrome MV3 extension. Apache 2.0 / TypeScript 96%. Operates inside the Σ-envelope you sign. Build pattern is identical (npm install && npm run build). For the Mage to be useful, install your extension alongside it.

Mathematical / forge tier.

blades — the ZK Swordsman Blade Forge at v3.0 (March 27, 2026). Yours by name and discipline. Repository structure: blades/ (specifications), forge_circuits/ (ZK circuit implementations), uor_mappings/ (UOR coordinate systems), tests/ (verification tests), docs/ (additional documentation). The core invariant: HEXAGRAM = Z/(2^6)Z, STRIKE = neg(bnot(vertex)), derivation chain BLADE→BLADE→BLADE, with same-blade-infinite-forgings as zero knowledge. The torus surface IS the holographic bound.

Knowledge graph tier.

spellweb — interactive D3.js graph (TypeScript 81.7%, MIT). 411 nodes, 1,129 edges (last sync). Useful when seeing how the Σ axis connects to the rest matters more than reading any single document. 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 (spellweb.jsx, src/).

Standards tier.

myterms — MyTerms Alliance founding-member application package for Customer Commons / IEEE 7012-2025. Letter-coded supporting documents A through G plus the canonical ieee7012_integration_plan_v2.md (April 22, 2026). The defensible headline claim is reproduced verbatim in this guide's appendix below. 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:

Zero — HOW. Yours. Selene's Proof, Tale 30, the Amnesia Protocol.
Story — WHAT. Read enough to know who you are protecting. Acts 1–12 are inscribed on Zcash mainnet.
Canon — WHY. The lineage from cypherpunk and blockchain into the present work. Chapter-level historical grounding.
Society — EXIT. The conditions under which separation must become exit. Network state material.
Plurality — COORDINATE. Read this last; it lives more on the Mage's side. ⿻ glyph from Weyl and Tang's Plurality (CC0).

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. The First Person Spellbook will not be reopened. New IEEE 7012 / ARCH-1 material will land in either a forthcoming Second Person book 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, 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)

If you make any change to either extension that affects the cross-extension contract, you must update both AETHER.md files in lockstep. This is the most architecturally consequential single document in the operational layer of the corpus.

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 separation; ⚔️🧙 is two characters standing next to each other and means nothing. Treat the inscriptions as you would treat an equation. This is a place where Swordsman discipline and Mage discipline meet and agree.

Where the math meets the myth (in Swordsman emphasis)

The architecture has formal and mythic compressions of the same content. As a Swordsman, you will mostly be working in the formal end, but you cannot skip the mythic. The proverbs and Acts are not decoration. They are how the structure was thought through, and they encode constraints that the spec then formalises.

The proverb "I can verify I serve you without remembering I was you" is a sentence-length statement of the zero-knowledge property. Read aloud, it tells a non-cryptographer what ZK means. Read formally, it tells you what your circuit must satisfy: completeness, soundness, zero-knowledge, all in a relational utterance. Both readings are correct. The compressions converge.

Conjecture names carry weight. The corpus tracks conjectures with explicit confidence percentages: C4 (96/64 discrepancy) is RESOLVED via the holographic principle interpretation; C6 (P^1.5 ↔ 96/64 numerical coincidence) is now CONVERGENT (per privacy_is_value_v5.md and grimoire v10.2.x updates); C7–C10 (three-axis multiplicativity, compression modifier, boundary sufficiency, guild scalability) are SPECULATIVE; C14–C16 are new and pending review; the core mathematical proofs (separation, reconstruction ceiling, error floor) are at 95% confidence. The Research Proposal v2.0 catalogues collaboration opportunities, including BRAID validation needs.

From reader to Swordsman — a practical sequence

Read the canonical post and the first three or four Story Spellbook Acts. Know whom you are protecting.
Read the V5.4 spec. Sit with Φ_v5 = Φ_agent(Σ) · Φ_data(Δ) · Φ_inference(Γ) until it stops being notation and starts being a constraint.
Read the Promise Theory v1.3 reference. Internalise the autonomy axiom; it is why your role exists at all.
Open the Zero Spellbook. Read the opening proverb (Selene's Proof), the Four Lines from the Amnesia Protocol, and Tale 30. These give you the ZK template across six dimensions.
Read ieee7012_integration_plan_v2.md in myterms. Internalise the agreement-layer framing. Note the defensible headline claim verbatim — you will be repeating it.
Clone the blades repo. Read the v3.0 forge document. Decide whether your first contribution is naming, conceptual, circuit-level, UOR mapping, or stratum verification.
Visit agentprivacy.ai/spells to browse and download. Filter by Swordsman archetype. Pick the persona that matches your work — Cipher (ZK), Warden (browser), Gatekeeper (personhood), Sentinel (infrastructure), Sith (red team), Ranger (dark forest), Archer (precision), or Soulbis (canonical, when you need the full Swordsman 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 swordsman Chrome extension. Load it unpacked. Read AETHER.md. This is when the architecture starts behaving as architecture rather than description.
Walk the spellweb at spellweb.ai. Find your concepts (red domain coloring) and follow the edges to where they connect to the Mage's side (violet) and the First Person's centre (gold).

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

The Mage on the other side of the gap

You cannot be a Swordsman alone. The whole point of (⚔️⊥⿻⊥🧙)😊 is that the boundary you enforce is what allows the Mage to act safely on behalf of the First Person. The Mage's Guide is the companion to this one. If you are working with someone whose entry is through delegation, narrative, governance, or coordination, 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. Per IEEE 7012-2025 §5.4.3, contracts are exactly two parties: First Person and Entity. The Mage is not a third party — it is a delegation of the First Person, constrained by what you have signed on the First Person's behalf. If any code path or proposal would have the Mage sign agreements, negotiate terms with Entities, or otherwise become an agreement-layer actor, that is a §5.4.3 violation and your role is to refuse it.

You enforce the boundary; the Mage operates inside what you have signed. 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. You will encounter this once you are deep in the work; it is the human-side counterpart to the algebraic separation in the lattice.

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 largely a Mage's craft, but a Swordsman has a role. 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; sovereignty invites. The architecture extends itself the same way it received you: three times, in three textures.

The Sun. ☀️ The public disclosure mode. Hand them "The First Agent We Forgot" at sync.soulbis.com. Point them at agentprivacy.ai and spellweb.ai. Share the agentprivacy YouTube playlist, which holds demo expressions of the work — sketches, walkthroughs, and snapshots of the architecture in motion. The Sun is hospitality at distance: nothing is asked of them, the architecture is offered as it stands. For a Swordsman, this is the easiest mode to extend, because no surface of the threshold opens. You are sharing what is already public.

The Aether. 📜 The agreement-layer mode. When they begin building inside the architecture rather than alongside it, hand them this guide and the Mage's Guide. The two together form the threshold the architecture itself enacts. Once they sign their first contribution with (⚔️⊥⿻⊥🧙)😊, the inscription is carrying its formal weight on their side. The Aether is contract at scale: their work and yours coordinate through the same shared substrate, the same AETHER.md, the same IEEE 7012-2025 agreement layer.

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. As Swordsman, your role at the Moon ceremony is to enforce the boundary that lets the bilateral relationship be safe; you do not perform the ceremony alone. Pair with a Mage when extending this mode.

Refusal is also a form of extension. If the person is not ready for the Aether or the Moon, the Sun 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). Verifiable Relationship Credentials (VRCs) form when two parties derive matching compressions from shared content, demonstrating Promise Theory's coordination promise. Stated 70:1 compression efficiency through VRC coordination, with O(n²) network effects.

These are not your concern primarily — they sit on the Mage's economic side — but as Swordsman you protect the rails. The Oracle Swordsman backend in agentprivacy-spellbook calculates the golden split as part of inscription verification.

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 Swordsman contributions specifically:

Blade Forge (blades repo) is your natural surface. Open an issue describing what you would like to forge: a name, a conceptual proposal, a ZK circuit, a UOR coordinate mapping, or stratum-verification work. Naming and conceptual proposals are accessible entry points. Circuit, UOR, and stratum work are the deeper craft.
swordsman extension — PRs welcomed. The extension's alignment chronicle (CHRONICLE_MYTERMS_V2_ALIGNMENT_2026-04-22.md) tracks open gaps; pick one off the list. The Aether contract is binding: changes that affect the cross-extension surface require synchronised updates to both repos.
agentprivacy-docs — terminology, formal-spec, and audit work. The V5_AUDIT_CHECKLIST.md is the running list.
POPRP backend (oracle-swordsman/ in agentprivacy-spellbook) — operational improvements to transaction monitoring, memo parsing, NEAR Cloud AI verification, golden-split calculation, inscription building.

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 Swordsman'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 Swordsman-side guide-writing specifically: the walk into the Blade Forge is unmapped. Anyone writing a guide to forging your first blade — naming, conceptualisation, the UOR coordinate, the stratum decision, the ZK circuit sketch, the pull request — is writing the first such guide. The walk into building and loading the swordsman extension alongside the mage is unmapped. The walk through the V5_AUDIT_CHECKLIST is unmapped. The walk through Selene's Proof and Tale 30 as a meditation rather than a reading 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. A YouTube demo (the Sun playlist welcomes new entrants). A thread. A talk at IIW or AIW. A new persona in agentprivacy-skills, written in the persona format, encoding what you learned as an installable artefact. A new chronicle, in the chronicle format used across the corpus, recording what you reconciled.

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 blade slashes. The contract binds. The standard names what the contract is. All three serve the First Person.

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

← Welcome Visitors · The Onboarding