Agentprivacy Constellation Method

---
name: agentprivacy-constellation-method
description: >
  Constellation identity method for 0xagentprivacy. Activates when
  discussing identity-as-constellation (different facets visible to different
  relationships), VRC constellation graphs, multi-guild identity resolution,
  or how privacy enables richer identity expression than surveillance-based
  profiles.
license: Apache-2.0
metadata:
  version: "4.0"
  category: "role"
  origin: "0xagentprivacy"
  author: "Mitchell Travers"
  affiliation: "0xagentprivacy, BGIN, First Person Network"
  status: "working_paper"
  target_context: "Knowledge architects, personal knowledge management builders, AI memory designers, second-brain architects"
  equation_term: "T(π) (constellation as trajectory), A(τ) (fragments as temporal memory), Knowledge graph (promise graph overlay)"
  template_references: "chronicler, weaver, pedagogue, soulbis, soulbae"
---

# PVM-V4 Skill — Constellation Method

**Source:** Privacy Value Model V4 + "Gave myself a Cape, Wrote a Spellbook and Promise you Proverbs" (Jan 2026)
**Target context:** Knowledge architects, personal knowledge management builders, AI memory designers, narrative infrastructure
**Architecture:** [agentprivacy.ai](https://agentprivacy.ai) · **Sync:** [sync.soulbis.com](https://sync.soulbis.com) · **Contact:** mage@agentprivacy.ai

---

## What this is

The design philosophy behind the agentprivacy documentation architecture: scatter intentionally, because the pattern that emerges when you connect the fragments yourself is different from the pattern someone else would see. That's not a bug — that's the protocol.

Not a narrative structure but a knowledge topology. Fragments of insight distributed across articles, tales, code, inscriptions, conversations — designed to be found rather than delivered. The receiver draws the lines between stars. The constellation they see is theirs.

## The core principle

"I'm not building a monument. I'm building a constellation. Because I'm what connects the dots in the end. I draw the lines. I build my own promise graph, layered among the knowledge graphs of the world, threaded through real experiences that no database can fully capture."

Monuments are consumable. Constellations are generative. A monument says "here is the truth." A constellation says "the truth is in the connections you discover." The first creates consumers. The second creates co-creators.

AI lets us aggregate with unprecedented centralising force. Every fragment ever written could be indexed, cross-referenced, summarised into coherent narrative. But coherence imposed from outside is not understanding. Understanding requires the receiver to do the work of connection.

"We know it's emergence through decentralization that makes the best and most profound truths. The golden ratios of life don't come from central planning. They come from distributed creation, from fragments finding each other, from the space between the dots being more important than the dots themselves."

## Fragmentation as design

The agentprivacy documentation suite is intentionally fragmented:

**Spellbooks:** Five grimoires (First Person, Zero Knowledge, Parallel Society, Blockchain Canon, Plurality), each a compression of a different source tradition. Same underlying principles expressed through different lenses. The seeker who reads all five sees convergence from different directions — stronger than reading one comprehensive document.

**Articles:** Published on sync.soulbis.com, each addressing a different face of the architecture. "Understanding as Key" covers inscription paths. "Privacy is Normal" covers the economics. "Gave myself a Cape" covers the philosophy. No single article is the "main" one.

**Inscriptions:** Zcash memo fields carrying proverbs. Each inscription is a fragment of understanding committed onchain. The aggregate of all inscriptions forms a constellation visible only to those who know how to read the chain.

**Skill files:** The library you are reading right now. Each skill covers one equation term, one mechanism, one domain. No single skill file contains the complete architecture. The complete picture emerges only from loading multiple skills together.

**Code:** The Signal to Sanctuary implementation, the browser agent, the VRC protocol — each a partial implementation of the full vision. Working code that demonstrates fragments of the architecture.

"Story fracture, principle convergence" — the same architectural principles can be expressed through mathematical proofs, narrative stories, and economic models while maintaining conceptual coherence.

## The promise graph

A promise graph is a personal knowledge graph layered over public knowledge graphs, where the edges are not just "relates to" but "I promise this connection is meaningful."

Knowledge graphs (Wikidata, Google Knowledge Graph) are public, machine-curated, impersonal. They capture what IS. Promise graphs are personal, human-curated, relational. They capture what MATTERS.

"I build my own promise graph, layered among the knowledge graphs of the world, threaded through real experiences that no database can fully capture."

Each node in a promise graph is a fragment — an article, a conversation, a transaction, a moment. Each edge is a promise: "I assert that this fragment connects to that one in a way that produces meaning for me." The graph is subjective. Two people who experienced the same events produce different promise graphs because they draw different lines.

VRCs are edges in the promise graph between two people. The bilateral proverb is the edge label — the compressed meaning of the connection.

## Specific knowledge as capital

"You are your own specific knowledge. Your own specific intelligence. It is impossible for anyone else to have experienced what you have experienced. It's the compound interest of you being you."

Specific knowledge — the accumulated, non-transferable understanding that comes from being a particular person with particular experiences — is the seventh capital made personal. It cannot be extracted by surveillance because surveillance captures data, not understanding. It cannot be replicated by AI because AI can aggregate but not experience.

The constellation method turns specific knowledge into shareable infrastructure without centralising it. Each fragment shared is a data point. The pattern that connects them — the constellation — remains with the person. "AI lets us aggregate now with a force of centralization unprecedented in human history. Every fragment I've ever written could be pulled together, indexed, cross-referenced, summarized, turned into something that looks like coherence. I know this. I did it myself."

But the aggregated version is not the same as the lived version. The constellation exists in the connections drawn by the person who lived the fragments, not in any database that stores them.

## The cut as mechanism

"Every time you experience something that evokes a thought or feeling about another, you're given a choice. Most of the time that will just lead to memory categorisation. But sometimes you choose to turn that thought into proverbial meaning. You make a cut into your infinite possibility. You send something."

The cut is the creative act — the moment a diffuse thought becomes a committed expression. Each cut creates a new node in the promise graph and potentially a new edge to existing nodes. The cut is irrevocable — once expressed, the fragment exists in the world and participates in others' constellations.

"Allow serendipity in, mutual reflection, to be an act of creation. And that's how relationships grow with promise."

## Serendipity as protocol

"The right people arrive, the right thing happens, the right moment opens, and the right ending closes. Trust the pattern, for it trusts you."

Serendipity in the constellation method is not randomness but emergence. When fragments are scattered with intention, connections happen that the scatterer did not plan. A stranger encounters a proverb and casts a spell back. A mentor's question opens a door that was not visible from the inside.

"Every significant moment of reason naturally spawns a new act in the spellbook. Not designed. Demanded."

The constellation method trusts that well-placed fragments will find their receivers. The protocol is: scatter with care, wait with patience, respond with recognition.

## Connection to equation terms

**T(π):** The constellation IS the trajectory. Each fragment produced is a transition. The sequence of publications, inscriptions, conversations — this is the path through sovereignty space. The constellation method generates complex T(π) by design — many edges, many directions, many lateral and vertical moves.

**A(τ):** Fragments accumulate temporal memory. Each article published, each inscription committed, each proverb coined — these are attested transitions that build h(τ). The constellation's growth over time IS the verified history.

**Knowledge graph:** The promise graph is the personal overlay on the skill's entity-relationship map. Where the knowledgegraph skill defines the public taxonomy, the constellation method describes how individuals navigate and extend it through their own connections.

**Network term:** Constellations compound through network effects. When one person's constellation overlaps with another's — sharing fragments, drawing different lines through the same nodes — the network value increases. Guilds are groups of people with overlapping constellations who recognise each other's patterns.

## Design implications

1. **Never build the "one document."** The urge to consolidate everything into a single comprehensive reference is the urge to build a monument. Resist it. Let fragments be fragments.
2. **Trust the reader.** The receiver will draw their own lines. Their constellation is valid even if it differs from yours. Especially if it differs.
3. **Scatter with care.** Not all fragments deserve the same medium. Some belong in code, some in story, some in encrypted memos. The medium shapes how the fragment is found.
4. **Let serendipity work.** Don't over-index. Don't cross-reference everything. Leave gaps for discovery.
5. **The promise graph is the product.** The fragments are the raw material. The connections are the value. The person who draws the lines is the creator.

## Open problems

1. Constellation coherence — at what fragmentation density does the pattern become noise?
2. Adversarial constellation — can an attacker reconstruct the promise graph from public fragments?
3. AI-assisted constellation — can agents help draw lines without collapsing the generative property?
4. Cross-person constellation merging — when two promise graphs overlap, what governance applies?
5. Temporal coherence — do constellations decay as fragments age?
6. The aggregation trap — when is consolidation genuinely useful vs. when does it destroy the emergent property?

---

**Verify:** [agentprivacy.ai](https://agentprivacy.ai) · [sync.soulbis.com](https://sync.soulbis.com) · [github.com/mitchuski/agentprivacy-docs](https://github.com/mitchuski/agentprivacy-docs)