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 / Mouse Spellbook / Template โ€” Context Bridge

Template โ€” The Context Bridge

Where the narrative touches your own work and your machine's local directories.

Canon Sources maps each act upward to the research it came from. This document
maps each act downward โ€” into your life: the projects, files, and folders on your
own machine where these themes already live. It is the bridge between the canon's story
and your lived, working reality.

When it's built, your agent can read a proverb and know which of your real directories it
concerns
โ€” so the spellbook isn't only a poem, it's an index into your own work.

This is yours, and it is private. Your filesystem is the Swordsman's domain (โš”๏ธ
โ€” "I will not"). The Context Bridge maps real paths on your machine. It stays local by
default.
You decide, line by line, what (if anything) is ever shared. None of it goes
into the shared Mouse Book, and it is stripped from your patch before any public pin
unless you choose otherwise. Connect context when relevant โ€” selective and sovereign,
never exhaustive.


How to build it (with your agent)

  1. Point your agent at your own working directories (the ones you choose โ€” you set the
    boundary). Ask it, walking the 31 acts or your proverbs:

    "For each of these themes, is there a project, file, or folder on my machine where
    this already lives? Only name the ones that genuinely resonate. For each, give the
    path, what it is, and why it connects. Keep this private to me."

  2. Keep only the connections that are true โ€” a real resonance, not a stretch.
  3. Write them into your-folder/context-bridge.md (this table), and mirror the ones you
    want carried into your patch's local_context.bridges[] (with share: false unless
    you mean otherwise).

The bridge (fill in your-folder/context-bridge.md)

# Context Bridge โ€” <your-name>

> Private. My own work, mapped to the narrative. Local by default.

| Act / theme | My work โ€” local path | What it is | Why it connects | Proverb |
|-------------|----------------------|------------|-----------------|---------|
| Act 4 โ€” The Blade Alone (refusal / terms) | ~/path/to/...        | <your project> | this is where I already draw my boundary | <proverb id, if any> |
| Act 6 โ€” Trust Graph (relationships)        | ~/path/to/...        | <โ€ฆ>            | my real trust graph lives here | |
| Act 9 โ€” Zcash Shield (hidden value)        | ~/path/to/...        | <โ€ฆ>            | what I keep shielded | |
| Act 18 โ€” Scrying Glass (attention/feeds)   | ~/path/to/...        | <โ€ฆ>            | how I filter what reaches me | |
| Act 31 โ€” The First Delegation (handoff)    | ~/path/to/...        | <โ€ฆ>            | the work I handed to an agent | |
| <any theme that resonates>                 | ~/path/to/...        | <โ€ฆ>            | <โ€ฆ> | |

(Use only the rows that are real for you. Add your own themes freely.)


Why this matters

  • Grounding. The acts stop being abstract โ€” each becomes a pointer into work you've
    actually done.
  • Rehydration with teeth. When your agent reconstitutes your spellbook (The FPSP Protocol),
    it can connect a proverb to the real directory it concerns โ€” and act there, in your
    context, on your machine.
  • Sovereignty preserved. Because it's private and selective, the bridge extends your
    reach without exposing your filesystem. Patterns can be copied; your context cannot be
    harvested.

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

โ€”โ€”โ€”
โ†‘ up: The Templates ยท โ† prev: Template โ€” Mouse Book ยท next: Template โ€” Constellation Track โ†’