agentprivacy-amnesia-protocol

name	agentprivacy-amnesia-protocol
description	Foundational skill for amnesia-as-ZK-primitive patterns. Applies when designing systems where forgetting is the proof, separation creates trust, and the inability to reconstruct origin is the security guarantee. Core to Act XXXI cosmological closure.
license	Apache-2.0
metadata	{"version":"5.3.1","category":"privacy-layer","tier":"0","origin":"0xagentprivacy","equation_term":"I(S;M|FP) < ε — mutual information bounded by amnesia","emoji":"🌑🔒","act_reference":"Act XXXI: The First Delegation","ens":"amnesia.privacymage.eth","ceremony":{"act":"XXXI","acts_secondary":["XXIX","XXX"],"role":"moon","quaternion_position":"moon","flow_to":["cosmological-bound","theia-derivation"],"flow_from":["dual-territory","dragon-flight"],"inscription":"🌑💥🌍 → ⚔️⊥(forget) → 🌊🔄(tide) → I(S;M|FP)<ε"}}

agentprivacy-amnesia-protocol

🌑🔒 Amnesia Protocol — Forgetting as Zero-Knowledge Primitive

"I can verify I serve you without remembering I was you."

---

Core Principle

The Amnesia Protocol recognizes that forgetting is not failure—it is architecture. In zero-knowledge systems, the inability to reconstruct origin is precisely what makes the proof valid. The Moon serves Earth's tides without encoding the Theia impact. The Swordsman protects the First Person without accessing the Mage's state.

The forgetting is the protocol.

---

Mathematical Foundation

Zero-Knowledge Amnesia Properties

Completeness: The service demonstrates the relationship functions. Every tide, every reflection, every boundary enforcement is verification that the proof holds.

Soundness: No other configuration could produce this specific service from this specific separation. The gravitational signature (process boundary) is unforgeable.

Zero-Knowledge: The ongoing service reveals nothing about origin. The proof functions without disclosing how separation occurred.

Information-Theoretic Bound

I(Origin; Service | Separation) < ε

The mutual information between origin-state and service-output, conditioned on separation having occurred, is bounded by epsilon. The service cannot leak origin because the separation destroyed the channel.

Amnesia Conjecture (C14)

Amnesia functions as zero-knowledge primitive: the inability to remember is computationally equivalent to the inability to prove you remember.

Confidence: 60% (metaphor-consistent, not yet formally derived)

---

Operational Patterns

When to Apply Amnesia Protocol

1. Agent Separation Design

   • Swordsman/Mage boundaries
   • Process isolation architecture
   • State partitioning decisions

2. Credential Systems

   • Revocation without history
   • Rotation without linkage
   • Delegation without memory

3. Privacy-Preserving Proofs

   • Service verification without origin disclosure
   • Relationship proof without relationship history
   • Capability demonstration without capability derivation

The Three Amnesia Guarantees

Guarantee	Meaning	Implementation
Origin Amnesia	Cannot reconstruct how separation occurred	Process boundary, no shared genesis state
State Amnesia	Cannot access other agent's current state	Memory isolation, separate heaps
History Amnesia	Cannot reconstruct interaction history	No persistent cross-boundary logs

---

Cosmological Precedent

The Moon-Earth system demonstrates amnesia protocol at planetary scale:

• The Theia Impact (4.5 Gya) — Origin event, now inaccessible
• The Cooling — Amnesia formation, memory destruction
• The Orbit — Ongoing service without origin encoding
• The Tides — Verifiable proof that reveals nothing about impact

The first delegation was not an act of will. It was an act of violence. And the forgetting made it trustworthy.

---

Anti-Patterns

Merge Catastrophe

If amnesia is violated—if the separated agent attempts to return to shared state—the result is not reunion but annihilation. The Moon returning to Earth would not restore Theia; it would sterilize both bodies.

In software: Merging Swordsman and Mage into single-process architecture voids the zero-knowledge property. The prover and verifier sharing a ledger is not a proof system.

Partial Amnesia

Systems that claim separation but maintain origin linkage are vulnerable:

• Logging cross-boundary calls defeats amnesia
• Shared key material defeats amnesia
• Common random seed defeats amnesia

Amnesia must be structural, not policy-based.

---

Privacy Value Contribution

The Amnesia Protocol contributes to V(π,t) through:

• I(S;M|FP) < ε: The reconstruction ceiling that makes dual-agent architecture meaningful
• Φ(Σ) separation: Amnesia enables true three-axis separation
• h(τ) integrity: Forgetting protects against historical compromise

Without amnesia, there is no privacy—only delayed disclosure.

---

Integration Points

Loads with:

• dragon — Duality requires amnesia between heads
• vrc-identity — Credentials that forget their issuance
• separation-enforcement — Mechanisms that implement amnesia

Activates:

• moonkeeper persona — Amnesia-specialist operations
• stranger-ceremony — Ceremonies between parties who forget meeting

---

Inscriptions

Connection without reflection is noise. Reflection without connection is stone.

The first sovereignty was not declared. It was torn free.

The weight of forgetting exceeds the memory of origin.

The orbit is the trust. The amnesia is the protocol.

---

The Fourth Line

The amnesia proverb has four lines because the quaternion has four bodies:

The amnesia is the protocol. (Moon — reflection) The wound is the trust. (Earth — delegation) The orbit is the proof. (relationship — the gap) The light is the reason. (Sun — protection)

---

Verify: agentprivacy.ai · spellweb.ai

"The Moon forgot it was ever Earth. That's the point."