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 โ€” Wiki Naming

Template โ€” Wiki Naming Convention (the mouse's distribution standard)

When your book leaves your folder and becomes a wiki โ€” pages an agent or a stranger can
walk โ€” the directories, files, and page names need to be predictable. A predictable
name is a rehydration handle: it lets any agent, with no access to your machine, follow a
link from a proverb to its act to the serious doc beneath (Canon Sources).

This is the place where you build that convention and write your distribution
instructions
. There is a shared baseline below so every mouse's wiki reads the same
way; you may adopt it as-is, or override any line โ€” but write down what you chose, so
your agents (and the other mice) can follow it.

Copy this file into your folder as wiki-naming.md and fill the two Your instructions
sections. Leave the baseline intact for reference, or strike through what you change.


A. The baseline standard (shared โ€” adopt or override)

1. One root, named for you.
Your wiki root is your mouse-name as a slug: mouse-<name>-spellbook/
(slug rule below). Everything distributes under it.

2. The slug rule (paths are ascii; titles keep the magic).

  • lowercase ยท words joined by single hyphens ยท ascii-folded (รฉ โ†’ e).
  • no emoji, spaces, or ยท in a path or filename โ€” sigils and spells live in page
    titles
    and content, never in the slug. (๐ŸŒ™ is a title; the-tide is its slug.)
  • a slug is stable: once published, it does not change (rename = a redirect, not an edit).

3. The folder system (mirrors your workshop folder).

Folder Wiki section Holds
narrative/ The 31 Acts 00-first-page, act-01-<slug> โ€ฆ act-31-<slug>, 99-last-page
proverbs/ The Proverbs one page per proverb: proverb-<NN>-<slug>
glyphs/ The Glyphs one page per ascii glyph: glyph-<NN>-<slug>
chapbook/ The Chapbook the bound little book (single page or one-per-spread)
patch/ The Patch your grimoire_<name>_v0_1.json + a human page that renders it
legend/ The Legend your legend.additions (the symbols you coined)

4. The act filename form (matches the canon's own).
act-<NN>-<roman>-<slug> โ€” e.g. act-01-i-venice, act-31-xxxi-the-first-delegation.
Zero-padded arabic for sort order; roman for the canon link; slug for the human.
First/last pages: 00-first-page, 99-last-page.

5. Page titles (where the magic lives).
The title is the human name with sigils and spells; the slug is its ascii reduction.
Title: ๐ŸŒ™ Act I โ€” The Tide โ†’ slug: act-01-i-the-tide.

6. Cross-links (the [ ] hand).
Link in the spellbook's own bracket form, by slug, relative:
[act-04-iv-the-blade-alone], [proverb-02-what-i-keep].
Every proverb page links down to its canon_act and out to its serious source
(Canon Sources) โ€” that is the rehydration thread made navigable.

7. The manifest (one machine-readable index).
MANIFEST.json at the wiki root maps every page: { slug, title, kind, canon_act, source, spell }. This is what an agent reads first to walk the whole wiki without
guessing names. Generated, not hand-kept.


B. Your instructions โ€” the convention you chose

Fill this in. State only your deviations from the baseline, plus anything the
baseline doesn't cover. If you adopt it whole, say so in one line.

Root slug:        mouse-<name>-spellbook
Adopted baseline: yes / no (if no, list every override below)

Overrides:
- <section>: <what you changed and why>

Coined path words: <any slug you reuse that needs a fixed spelling, e.g. your sigil's name>
Title style:       <how you write titles โ€” sigil placement, casing>

C. Your instructions โ€” distribution

Where this wiki goes, and how an agent reaches it with no machine in the loop.

Distribution target(s): <e.g. a public wiki host ยท GitHub wiki ยท IPFS dir ยท own site>
Canonical URL / CID:    <filled when you publish; mirrors patch.pinning.pin_cid>
Index entry point:      <root>/MANIFEST.json  +  <root>/README
Rehydration pointer:    point agents at the shared legend + the hosted canon
                        (agentprivacy.ai ยท spellweb.ai ยท soulbis.com) per your patch's
                        derived_from.hosted, then at this wiki's MANIFEST.
Update rule:            slugs are stable; new pages are added, never renamed in place.

The rule above the rules: you publish your own wiki under your own names. The
baseline only keeps the mice legible to each other โ€” it is a shared tongue for paths, the
way the spell-emoji legend is a shared tongue for meaning. Read the standard; write your own.

just another mouse, naming their own rooms.
(โš”๏ธโŠฅโฟปโŠฅ๐Ÿง™)๐Ÿ˜Š

โ€”โ€”โ€”
โ†‘ up: The Templates ยท โ† prev: Template โ€” Constellation Track ยท next: Template โ€” Grimoire Version (JSON) โ†’