⚔️ 📜 ✍️ 🔐

MyTerms

the standard specifies agreement, not enforcement.

IEEE Std 7012™‑2025 · the agreement layer · the expressions agentprivacy has built against it

Working Group — Doc Searls, Chair · hosted by Customer Commons · the individual proposes the terms

press → to walk the expressions

MAP⊥Where 7012 shows up in the work

Nine places the standard becomes concrete.

01 · PROTOCOL

Invitation Protocol

the First Person proposes; one round only.

02 · RECORD

Bilateral chronicle

two signatures, two kept copies.

03 · FORMAT

Three registers

JSON‑LD over W3C DPV.

04 · AGENTS

Swordsman ⊥ Mage

only one of them signs.

05 · MODEL

Three axes mapped

Σ · Δ · Γ, honestly bounded.

06 · ROSTER

SD‑BASE / PDC

consumed from Customer Commons.

07 · RUNS

Three artefacts

API · extensions · broker.

08 · WITNESS

VRC + Gödel

trust vouched from outside.

09 · RECOVERY

RPP

a proverb binds a credential.

FRAME⊥What 7012 is — and what it is not

A thin waist. It does one thing, at the agreement layer.

above the waist — the implementer'sdelegation · verifiable relationship credentials · trust graphs
the waist — IEEE 7012the routine by which a person and an entity agree — and nothing else
below the waist — the implementer'senforcement · cryptographic substrate · the chronicle

soeverything that follows sits above or below this waist. the standard specifies agreement, not enforcement.

EXPRESSION 01⊥The Invitation Protocol

The First Person is the Proposer.

acceptance before proposal. the entity may accept, counter once, or decline. negotiation is capped at a single round.

§5.2.1.3First Person plays the Proposer rolethe individual opens, not the platform
§A.1single‑round negotiationaccept · counter‑offer once · decline
11-the-invitation-protocol.mdthe canonical spec in the tomesthe swordsman's first blade
/hallseeded promise Own MyTermsthe civic home where terms get counter‑signed
EXPRESSION 02⊥The bilateral chronicle

Two parties. Two signatures. Two kept copies.

a chronicle neither can later deny. agents, devices and trust communities are the fabric around it, not parties to it.

honestan early draft wrongly wrote four parties. corrected to strictly two.

the First Person on one side, the Entity on the other. neither can be absent, neither can be merged. the ⊥ between them is the standard itself.§5.2.4 · hall-bilateral-witness
EXPRESSION 03⊥Three registers, as code

One agreement, three synchronised formats.

p7012:hasHumanReadableFormatplain language, what the person actually understands
p7012:hasLegalReadableFormatthe Customer Commons canonical legal text
JSON‑LD / W3C DPVthe machine‑readable body, so agents and devices can parse and act on it

whereencoded in C_technical_integration.md alongside the JSON‑LD body.

EXPRESSION 04⊥Swordsman ⊥ Mage · the role split, in code
⚔️

The Swordsman

Σ · signs
the only agent with a signing path.
background/index.ts · ECDH
⊥
🧙

The Mage

Γ · never signs
read‑only until it discovers the Swordsman, then acts inside scope.
myswordsman / mymage
⚔️blade · boundary
📜scroll · the contract
✍️signature · consent
🔐lock · registry trust
EXPRESSION 05⊥The three axes, mapped honestly to 7012

Φ_agent(Σ) · Φ_data(Δ) · Φ_inference(Γ)   any axis at zero collapses the whole.

Σagent
7012 defines the person‑agent / entity role boundary, making separation testable.
necessary, not sufficient · a compliant monolith can still score Σ ≈ 0
Δdata
SD‑BASE / PDC agreement IDs give a coarse data‑policy lattice.
cryptographic enforcement (ZK / TEE) lives below the standard
Γinference
the standard is mostly silent here.
inference over published data is out of scope
EXPRESSION 06⊥The roster · consumed, not minted

Standard terms come from Customer Commons.

like Creative Commons, for privacy. we consume the IDs, never invent our own.

SD‑BASE→ ‑DP→ ‑A→ ‑AT→ ‑ATP→ ‑ATP‑S3P

most protective → most permissive

PDC‑INTENTPDC‑AIPDC‑GOOD

honest gapour own stance / spell UX tokens are not yet grounded in real Customer Commons IDs.

EXPRESSION 07 · A⊥Artefact one · the negotiate API

A live two‑party term exchange.

an experiment built to try a conference‑style MyTerms pattern, around BGIN Block 14. a real endpoint, not a diagram — a shape to run in the room.

api/myterms/negotiate/route.tsthe term‑exchange endpoint
lib/ceremony/constellation.tsforges the agreement from both sides
13_MYTERMS_AGREEMENT_LAYER.mdthe agreement‑layer design spec

statusconference experiment · code exists.

EXPRESSION 07 · B⊥Artefact two · the dual extensions

Two orbs over any page. Converge them, forge an agreement.

your terms ⚔Swordsman orb
+
site's ✦Mage orb
→
convergeagreement forged
→
hashedconstellationHash
blade-forge.tshexagram → blade
spell-definitions.tseach sticker → a myTermsMapping + a proverb
ECDH key exchangescaffolded between the pair · signSpell() still a placeholder

statusbuilt · cryptographic sealing in progress, not shipped.

EXPRESSION 07 · C⊥Artefact three · the capability broker

Delegation inside an agreed scope.

WIKI_GRANT gives an agent host‑scoped write access, never the full authority the credential carries, and never the secret itself.

statusworking today at env‑var scope.

the IEEE 7012 version: the site owner publishes machine‑readable terms, the agent presents an agreement, and the broker honours a push only against a valid signed agreement, deriving the allowed scope from that agreement.broker.js · a miniature of the MyTerms pattern
EXPRESSION 08⊥The witness · why it is built incomplete

A self‑certifying agreement is a contradiction.

Gödel's lesson, put to work. so the trust community is not a party but a witness: a VRC signs nothing, it measures fidelity from outside, and vouches.

a trust that certifies itself is the one you cannot trust.the lintel
EXPRESSION 09⊥The Relationship Proverb Protocol

A proverb, spoken, unlocks a credential.

the three‑register logic turned on trust itself: recovery is gated by speaking a human‑readable proverb that binds a relationship.

humana proverb that binds a relationship
→
machinea recovery credential
→
on‑chainZcash inscription

noteproof of understanding replaces the stored secret · demonstrated decompression is the proof.

THE ASK⊥Founding membership · MyTerms Alliance

Four things a standard needs to reach adoption.

Implementation
production Swordsman + Mage; a conference‑pattern negotiate API.
Diffusion
weekly streams · AIW / IIW.
Narrative
a canon that makes the standard legible.
Sustainability
Foundation ↔ Labs ↔ Community.

before surveillance architectures lock in · the standard specifies agreement, not enforcement.

the blade slashes. the contract binds. the standard names what the contract is. all three serve the First Person.

APPENDIX⊥Status & honesty

Where the expressions actually stand.

Integration plan v2 (PVM V5.4)current operative text✓
Negotiate API (BGIN Block 14 experiment)conference pattern · code exists✓
Capability brokerworking; env‑var scope, signed‑scope next✓
Extension convergence UIbuilt; signSpell() is a placeholder→
SD‑BASE / PDC grounding of UX tokensnot yet mapped→
Grimoire standards.ieee_7012_2025 blockplanned, not in the JSON→
Staged wiki pagesstaged, not published→
V6 edition of the planqueued, not drafted→
⚔️ 📜 ✍️ 🔐 the agentprivacy expressions 01 / 16