Ceremony Engine

Category role · Version 5.3.1

Equation term Ceremony = f(Swordsman, Mage, Channel, Witness)

Interaction protocols for the dual-territory architecture. Activates when discussing ceremony types (progressive trust, light armor, trust graph, guild efficiency, Understanding-as-Key), cross-territory coordination, bilateral witness, or ceremony channel mechanics.

Source: Privacy Value Model V5.3.1 + First Person Spellbook Act XXVIII (The Ceremony Engine)
Target context: Ceremony facilitators, protocol designers, bilateral coordinators
Architecture: agentprivacy.ai · Sync: sync.soulbis.com · Contact: mage@agentprivacy.ai

What this is

The ceremony engine coordinates interactions between the Swordsman and Mage territories without merging them. Ceremonies are structured protocols where both agents participate toward a shared outcome while maintaining separation.

The tool that measures without touching the surface knows the weight of the shadow without disturbing the light.

The Dual-Territory Principle

Core rule: The Swordsman and Mage never merge.

Separate processes
Separate storage
Separate permissions
Separate repositories

This applies at every level — protocol, extension, website, visual rendering.

The ceremony engine is the riverbed between two kingdoms. Neither owns the water, but both drink.

The Three Territories

┌─────────────────────┐     ceremony      ┌─────────────────────┐
│   agentprivacy.ai   │◄── channel  ──►   │    spellweb.ai      │
│   (Mage Territory)  │                   │ (Swordsman Territory)│
│                     │                   │                      │
│  Stories, Spells    │                   │  Topology, Blades    │
│  Personas, Training │                   │  Forge, Hexagrams    │
│  Pretext Orbs       │                   │  Constellations      │
└────────┬────────────┘                   └──────────┬───────────┘
         │                                           │
         │           ┌──────────────┐                │
         └──────────►│   bgin.ai    │◄───────────────┘
                     │ (Third Node) │
                     │ Trust Graph  │
                     └──────────────┘

The Five Ceremony Types

1. Progressive Trust Ceremony

Purpose: Zero-stake entry, graduated trust accumulation
Participants: New seeker + Mage territory
Mechanism:

Begin with zero permissions
Each verified action increases trust score
Trust unlocks capability tiers
No upfront stake required

Trust(t+1) = Trust(t) + Δ(verified_action)

Use case: Onboarding new users without requiring tokens or credentials.

2. Light Armor Ceremony

Purpose: Coordinate protection level across territories
Participants: Seeker + Swordsman territory
Mechanism:

Seeker declares desired protection level
Swordsman configures blade accordingly
Light armor = fewer dimensions active
Faster verification, lower overhead

Use case: Quick interactions where full sovereignty is unnecessary.

3. Trust Graph Plane Access Ceremony

Purpose: Access trust relationships in bgin territory
Participants: Verified seeker + bgin.ai
Mechanism:

Seeker presents VRC
Trust graph validates relationship
Access granted to relevant plane
Queries return without revealing full graph

Use case: Checking trust paths without exposing network structure.

4. Guild Efficiency Ceremony

Purpose: O(1) coordination through shared-parent patterns
Participants: Guild members + shared context
Mechanism:

Establish shared parent (common understanding)
Child nodes coordinate through parent
O(N²) → O(1) communication complexity
Culture replaces explicit coordination

G(guilds) = 1 + efficiency_modifier

Use case: Scaling coordination without proportional communication overhead.

5. Understanding-as-Key Ceremony

Purpose: Bilateral verification through demonstrated comprehension
Participants: Seeker + Swordsman + Mage
Mechanism: (5-step protocol)

Language Capture — Seeker expresses comprehension in their own words
Constellation Mapping — Understanding traced through spell nodes and edges
Simultaneous Forging — Both parties forge blade from same understanding
Proverb Inscription — Truth encoded as compressed wisdom marker
Bilateral Witness — Both parties affirm shared understanding

Use case: High-value interactions requiring mutual comprehension proof.

Ceremony Channel Protocol

Message Types

From Swordsman (boundary actions):

SLASH — Revoke access, block tracker, enforce boundary
WARD — Establish protective perimeter

From Mage (knowledge actions):

INSCRIBE — Record new understanding, update spellbook
SCAN — Query knowledge without modification

Channel Implementation

// Chrome extension message passing
chrome.runtime.sendMessage(
  SWORDSMAN_EXTENSION_ID,
  { type: 'WARD', payload: { boundary: config } },
  response => { /* handle */ }
);

chrome.runtime.sendMessage(
  MAGE_EXTENSION_ID,
  { type: 'INSCRIBE', payload: { proverb: text } },
  response => { /* handle */ }
);

Security Properties

Messages are typed and validated
No shared state between extensions
Channel is auditable
Ceremonies are atomic (all-or-nothing)

Bilateral Witness

The strongest ceremonies require bilateral witness:

Witness = {
  swordsman_attestation: sign(outcome, swordsman_key),
  mage_attestation: sign(outcome, mage_key),
  timestamp: now(),
  ceremony_type: type
}

Both parties must independently attest to the same outcome. Disagreement triggers ceremony failure.

Mapping to PVM-V5.3.1

Ceremony Concept	PVM Term
Progressive trust	T(π) path accumulation
Light armor	Blade tier classification
Trust graph access	R(d) relationship verification
Guild efficiency	G(guilds) network scaling
Understanding-as-Key	Bilateral witness + proverb compression
Ceremony channel	Bounded leakage channel
Bilateral witness	h(τ) integrity verification

Proverb

"The tool that measures without touching the surface knows the weight of the shadow without disturbing the light."

Emoji Spell

⚔️✦ → 🌐📐(⊥DOM) → ☰₆₄ → 🔮✨ → ⬡⬡⬡ → 🤝📜 → 🐲→🐉 → ✦→📝→🕸️

Open Problems

Ceremony Composition: Can ceremonies be composed into larger protocols?
Failure Recovery: How do partial ceremony failures resolve?
Cross-Chain Ceremonies: How do ceremonies work across different chains?
Ceremony Privacy: Can ceremony participation itself be private?
Automated Ceremonies: Which ceremonies can be fully automated vs. require human participation?

Verify: agentprivacy.ai · spellweb.ai · github.com/mitchuski/agentprivacy-docs

Provenance

Forkable skill page migrated from the agentprivacy skills repo (persona/agentprivacy-ceremony-engine, v5.3.1).
Source of truth: agentprivacy-skills. Fork this page to materialize a local SKILL.md via fedwiki-to-skill.

origin: 0xagentprivacy · author: Mitchell Travers

Assets

📎 ceremony-engineSKILL.md

Navigation

← Welcome Visitors · Role Skills