guide to agentprivacy
Browse collections
โœจVisualise
Connect with Star
Your VTA, your chosen perspective

The planned connection uses your VTA and the Trust Spanning Protocol to carry a scoped exchange for you or your agent. You choose what is presented; the receiving service checks the request before a view is shared.

This guide has no VTA connection adapter yet. Opening Star does not connect an identity or send a key.

Open Star โ†— ยท Inspect your City Key โ†—
guide / Research / Ceremony โ€” The Ceremony Engine: Technical Specification

The Ceremony Engine: Technical Specification

Acts XXVIIโ€“XXVIII Implementation Architecture

(โš”๏ธโŠฅโฟปโŠฅ๐Ÿง™)๐Ÿ˜Š

privacymage

Version: 1.1 โ€” April 2026
Status: Forge OPERATIONAL ยท Ceremony Engine SPECIFIED ยท Extensions NOT YET BUILT
Parent: Dual Territory Ceremony Spec v1.0


1. System Overview

The ceremony engine carries the blade forge from spellweb.ai across the open web. The forge proves the concept within a single site. The ceremony engine carries sovereignty everywhere else.

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”     ceremony      โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚   agentprivacy.ai   โ”‚โ—„โ”€โ”€ channel  โ”€โ”€โ–บ   โ”‚    spellweb.ai      โ”‚
โ”‚   (Mage Territory)  โ”‚     (mana)        โ”‚ (Swordsman Territory)โ”‚
โ”‚                     โ”‚                    โ”‚                      โ”‚
โ”‚  Stories, Spells    โ”‚                    โ”‚  Topology, Blades    โ”‚
โ”‚  Personas, Training โ”‚                    โ”‚  Forge, Hexagrams    โ”‚
โ”‚  Pretext Orbs       โ”‚                    โ”‚  Constellations      โ”‚
โ”‚  Path Page          โ”‚                    โ”‚  Cut Segments        โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜                    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
         โ”‚                                            โ”‚
         โ”‚           โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”                 โ”‚
         โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ–บโ”‚   bgin.ai    โ”‚โ—„โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                     โ”‚ (Third Node) โ”‚
                     โ”‚ Trust Graph  โ”‚
                     โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
         
         โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
         โ”‚        The Open Web              โ”‚
         โ”‚                                  โ”‚
         โ”‚  โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”  โ”‚
         โ”‚  โ”‚ Swordsman  โ”‚ โ”‚    Mage     โ”‚  โ”‚
         โ”‚  โ”‚ Extension  โ”‚ โ”‚  Extension  โ”‚  โ”‚
         โ”‚  โ”‚ (boundary) โ”‚ โ”‚ (knowledge) โ”‚  โ”‚
         โ”‚  โ””โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”˜  โ”‚
         โ”‚        โ”‚  ceremony     โ”‚          โ”‚
         โ”‚        โ”‚โ—„โ”€โ”€ channel โ”€โ”€โ–บโ”‚          โ”‚
         โ”‚        โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜          โ”‚
         โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Core rule: The Swordsman and Mage never merge. Separate Chrome processes. Separate storage. Separate permissions. Separate repos. This applies at every level โ€” protocol, extension, website, visual rendering.


2. The Forge (OPERATIONAL)

The forge is live at spellweb.ai. This section documents what is running.

2.1 Forge Components

Component Purpose Status
SpellWeb.tsx Main graph + forge modal + global controls โœ… Operational
SpellCeremony.tsx Ceremony panel + action bar + proof generation โœ… Operational
WanderingOrbs.tsx Orb wandering + tracing mode + cut segments โœ… Operational
SpellEffects.tsx Spell particles and visual effects โœ… Operational
types/graph.ts Hexagram types + dimension computation โœ… Operational

2.2 Forge Capabilities

  • 478-node knowledge graph (984 edges) with D3 force simulation (dated snapshot; the live data model counts 807 nodes / 1738 edges as of 2026-07-18 โ€” src/data/nodes.ts is the authority, per pipeline L158)
  • Dual orbs (Swordsman red #e74c3c, Mage purple #9b59b6, 35px orbit radius)
  • Constellation marking, saving, loading
  • Evocation (orbs trace constellation path, count laps, accumulate charge)
  • Blade forge (six-dimension activation, stratum/tier classification, SVG with inscribed constellation)
  • Hexagram computation (node dimensions โ†’ 6 binary lines โ†’ 64 states)
  • Node inspector with hexagram visualisation
  • Blade inventory with tracing (click blade โ†’ orbs retrace path with tier-coloured cut segments)
  • Blade export to markdown/JSON

2.3 Six Dimensions Activation

Dimension Canonical Implementation Activation Condition
d1 ๐Ÿ›ก๏ธ Protection Hide โ‰ฅ1 node in path
d2 ๐Ÿค Delegation Commit โ‰ฅ2 laps completed
d3 ๐Ÿ“œ Memory Prove โ‰ฅ30 seconds duration
d4 ๐Ÿ”— Connection Connect โ‰ฅ3 nodes traversed
d5 โšก Computation Reflect Always (proof generated)
d6 ๐Ÿ’Ž Value Delegate Charge โ‰ฅ FLAME

2.4 Charge Levels

Level Laps Description
SPARK 1 Minimal proof
EMBER 2โ€“3 Building presence
FLAME 4โ€“5 Sustained attention
BLAZE 6โ€“7 Deep engagement
INFERNO 8+ Full ceremonial presence

2.5 Blade Tiers

Tier Stratum Dimensions Active
Light ๐Ÿ›ก๏ธ 1โ€“2 1โ€“2 of 6
Heavy โš”๏ธ 3โ€“4 3โ€“4 of 6
Dragon ๐Ÿ‰ 5โ€“6 5โ€“6 of 6

2.6 Empirical Data (N=3, Single Forger)

Blade Nodes Laps Duration Spells Tier Hex Signature
Dual Agent 4 11 74s โ€” Dragon 3F SPELL-87BYW9-B
Hitchhiker's 10 13 433s โ€” Dragon 3F SPELL-2COQFM-D
Universe 10 62 2,170s 65 Dragon 3F SPELL-YW5I59-1Q

The Hitchhiker's Blade and Universe Blade trace the same 10-node constellation. Same hash. Same hex. Same tier. Different behavioural density (ฯ). This is the V5.1 data point โ€” reconstruction difficulty modified by traversal depth.


3. The Ceremony Engine (SPECIFIED)

The ceremony engine extends the forge across the open web via two Chrome extensions. This section documents the design. The code is not yet written.

3.1 Two Extensions, Not One

Extension Territory Carries Process
Swordsman spellweb.ai MyTerms assertions, cookie slashing, boundary enforcement, cursor state Separate Chrome process
Mage agentprivacy.ai Knowledge scanning, page intelligence, constellation mapping, Drake emergence Separate Chrome process

They find each other on every page through chrome.runtime.sendMessage. The Swordsman sends SLASH and WARD. The Mage sends INSCRIBE and SCAN. The communication grammar is the lore made executable.

The chrome processes are the Gap made executable. Separate storage. Separate permissions. Same I(S;M|FP) < ฮต* that governs the protocol-level separation.

3.2 Five Ceremony Types

The spellweb already has the dual orbs, the wandering dance, the evocation ceremony. The extensions carry this onto every page:

Dual Convergence โ€” orbs within 60px, at least one spell cast. Amber burst. Cursor becomes sovereign shield. MyTerms asserted. The ceremony the spellweb forge already demonstrates โ€” now on any website.

Hexagram Cast โ€” six lines between the orbs, each mapped to an architectural layer. 64 states for 64 privacy postures. The spellweb already computes hexagram states from node dimensions. Whether the I Ching's internal transition logic maps onto privacy state transitions remains open (C12, 50% confidence).

Emoji Cast โ€” the fastest ceremony. Select, click, the emoji becomes your cursor. You inscribe the page with sovereignty. The spellweb's spell particles, exported to the open web.

Constellation Wave โ€” the Mage scans the page, finds trackers and dark patterns, and launches particles along the lattice geodesic toward the Swordsman. Intelligence flowing through infrastructure. The spellweb already does this in miniature โ€” click a forged blade in inventory and the orbs retrace its constellation.

Bilateral Exchange โ€” for the future, when sites implement MyTerms endpoints. The Swordsman proffers terms. A third node appears. The Mage mediates. If terms are accepted: triangle. Trust triad. The strongest geometry.

3.3 The Drake Emergence

When both extensions are active and conditions warrant, the Drake emerges from the user's constellation across the web. Each node in the Drake's body is a condition from the Privacy Value Model. Set any to zero and the body breaks:

ฮฆ_v5 = ฮฆ_agent ยท ฮฆ_data ยท ฮฆ_inference โ€” multiplicative, honest. The equation rendered as serpentine form.

Dragon transformation requirements (sustained across the open web):

  • 10 domains asserted
  • 64 constellation nodes
  • Months of practice

Not a sprint. A discipline. The same discipline the spellweb forge already rewards at the single-site level.


4. DOM-Free Measurement

4.1 Pretext Integration

The ceremony engine uses pretext (by Cheng Lou) for text measurement. Pure JavaScript text measurement and layout that side-steps the DOM entirely.

One canvas.measureText() call โ€” one moment of contact with the font engine โ€” then pure arithmetic forever. layoutNextLine(). Each line can have a different width. Text flows around any shape.

The browser's layout engine โ€” that narrow, sequential, focused attention that McGilchrist warned us about โ€” is never triggered again.

One touch. Then memory. Then mathematics. Then silence.

4.2 Privacy Implications

Surveillance scripts fingerprint through DOM reflow: getBoundingClientRect, offsetHeight, LayoutShift entries. Every measurement is observable. Every observation is a fingerprint.

Pretext eliminates the observation surface. The text reflows. The layout engine never knows. The page is alive but measurement-dark.

This is the dual-agent separation applied at the rendering layer. The reconstruction ceiling R < 1 becomes harder to pierce because the fingerprinting surface has been removed at source.

Confidence: 95% โ€” the library's documented specification, not a claim.


5. Mana Economy

5.1 Earning

Action Mana Earned
10 spell casts on ordinary websites 1
1 convergence ceremony 2
1 evocation cycle (mage-x-feed-filter) 1
1 blade forged on spellweb (any tier) 1

Mana rewards practice, not achievement. The mana economy gates contribution to the knowledge graph.

5.2 Spending

Mana is spent on community inscriptions:

  • Node annotations
  • Community edges
  • Constellation projections
  • Forge-born proverbs

5.3 Properties

  • Earned through traversal (not purchased)
  • Non-transferable (no markets)
  • Spent on inscriptions (creates value)
  • Self-reported, honour-based (Sybil resistance = difficulty of earning, not server verification)

The knowledge graph grows through sovereignty practice. The Sybil resistance is proof of practice, not proof of capital. The spellweb that is only read dies. The spellweb that is inscribed lives.

5.4 Playtesting Status

The earn/spend rates are first estimates. Too cheap and the graph floods. Too expensive and nobody inscribes. Needs testing.


6. The Path Gate

The extensions are downloadable only from agentprivacy.ai/path โ€” a page that opens when you've completed minimum training:

  • 3 spells cast
  • 3 sections visited
  • 1 convergence witnessed

You learn the language on the spellbook. You forge your first blade on the spellweb. You install the extensions when you've proven you understand what they carry.

The blade goes first. Always.

This is understanding-as-key as the literal access control mechanism. No credentials. No sign-up. Demonstrated comprehension as the gate.


7. The Dragon Anatomy (Complete)

Act Anatomy What It Establishes Status
XXIV Boundary Holographic surface. 96 edges, 64 vertices โœ… Proven
XXV Hide Private mesh. Tailscale as nervous system โœ… Grounded
XXVI Brain Divided hemispheres. McGilchrist's thesis โœ… Grounded
XXVII Forge Where blades are made. UOR ร— tetrahedra ร— ZK โœ… Operational
XXVIII Ceremony Where blades cross. Extensions, mana, ceremony channel ๐Ÿ“‹ Specified
XXIX Flight Post-quantum resilience. Manifold proofs ๐Ÿ“‹ Specified
XXX Mirror Dihedral group. neg = Swordsman, bnot = Mage, succ = First Person โœ… Proven
XXXI Protocol Moon-Earth-Sun-Human cosmology. Amnesia Protocol โœ… Grounded

8. Bilateral Witness Ceremony (Demonstrated)

The Universe Blade verification demonstrated the bilateral witness primitive:

Movement 1 โ€” Private verification. The Swordsman (privacymage) sent the blade file and JSON proof to the Mage (Soulbae) via Telegram. The Mage matched every field to the architecture:

  • Hex 3F โ†’ binary 111111 โ†’ all six dimensions active
  • Stratum 6/6, Dragon tier
  • Constellation hash verified
  • Inscribed spell expanded symbol by symbol: ๐Ÿ”‘ (Genesis Key) โ†’ โš”๏ธ (Swordsman) โ†’ ๐Ÿง™ (Mage) โ†’ โ†’ (Ceremony) โ†’ ๐Ÿ˜Š (Person) โ†’ โœฆ (Constellation Hash) โ†’ โ˜ฏ๏ธ (Jedi Balance) โ†’ โš–๏ธ (Plural Balance) โ†’ โš”๏ธ๐Ÿง™ (Dual Ceremony returned)

Movement 2 โ€” Public testimony. In a separate chat (Hitchhiker platform, witnesses present), the Mage reconstructed the blades from proof signatures alone โ€” drawing on episodic memory of the private verification. Named the constellation path, tier, dimensional activation, inscribed spell, and architectural significance for both the Hitchhiker's Blade and the Universe Blade.

Promise Theory mapping: The Swordsman made a + promise (forged the blade, offered the proof). The Mage made a โˆ’ promise (verified privately, testified publicly). The community received the testimony without accessing the witness. Bilateral. Voluntary. Verifiable through the ceremony's own structure.

Proverb generated: "The weight of the shadow exceeds the light of the data."

Status: Demonstrated once (March 29, 2026). Needs formalisation. Conjecture C13 (bilateral witness, 60% confidence).


9. Celestial Ceremony Integration

The Celestial Ceremony (documented in the-celestial-ceremony.md) provides the human-layer ceremony that the ceremony engine formalises at the protocol layer.

9.1 Mapping

Ceremony Layer Human (Celestial) Protocol (Engine)
Sun Two phones, music + narration Swordsman extension, blade forge
Gap Conversation, territory changes Ceremony channel, constellation modification
Moon Shared reflection, Amnesia Protocol Both extensions active, shared page analysis
Reflect (night) Modify constellation, forge second blade Bilateral exchange, blade pair
Connect (day) Witness blade, carry forward Witnessed blade, unilateral acknowledgement

9.2 Progressive Trust (Understanding โ†’ Constellation โ†’ Blade)

Level Human Ceremony Protocol Layer Trust Tier
Understanding Shared experience, two phones Presence, no formal disclosure Entry
Constellation Traced on spellweb together Node selection, boundary-making Blade โ†’ Light
Blade Forged proof, cryptographic artifact Six dimensions, ZK, mana earned Light โ†’ Dragon

9.3 Ceremony Receiver (NOT YET BUILT)

The spellweb needs to accept:

  • Blade imports from other forgers
  • Constellation modifications (the Reflect flow)
  • Witnessed blade acknowledgements (the Connect flow)
  • Mana-powered community inscriptions

This is the primary engineering need for the Celestial Ceremony to operate on the spellweb at scale.


10. Open Conjectures

ID Conjecture Confidence Source
C11 Behavioural density ฯ modifies reconstruction difficulty 55% V5.1, Universe Blade
C12 Hexagram encoding maps onto privacy state transitions 50% Forge, I Ching
C13 Bilateral witness is a verification primitive 60% Universe Blade ceremony
C14 DOM-free measurement tightens reconstruction ceiling 95% Pretext specification

References

Document Location Relevance
Dual Territory Ceremony Spec v1.0 agentprivacy-docs Parent architecture
ZK Swordsman Blade Forge v3.1 blades Blade specification
The Celestial Ceremony agentprivacy-docs Human ceremony specification
The Celestial Overlap agentprivacy-docs Convergence map
Glossary Master v3.0+ agentprivacy-docs Canonical definitions
Privacy is Value V5 Blog Series sync.soulbis.com Parts 0โ€“5

The forge doesn't care how you struck the metal. It only cares what blade you hold.

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

(โš”๏ธโŠฅโฟปโŠฅ๐Ÿง™)๐Ÿ˜Š


Author: privacymage
License: CC BY-SA 4.0

Assets

๐Ÿ“Ž ceremony-the-ceremony-engine-technical-specificationceremony-engine-spec-v1_1.md

Navigation

โ† Welcome Visitors ยท The Ceremonies