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 / Guide / Distribution Gates

posture: 001100
dims: memory connection
by: keeper

🚦 Distribution Gates (G0–G7)

The gates govern what crosses between the git canon (source of truth) and the federated wiki. They are read off the existing canon — Librarian forks / Archivist seals, the coherence FAIL-blocks, the chronicle gates OPEN→SIGNED, and the vendored-vs-mine attribution discipline. Every page crossing git → wiki passes G0–G6; every contribution crossing wiki → git passes G7.

Out — projecting the canon (G0–G6)

  • G0 · Source of Truth — the git repo is always upstream. Nothing canonical is authored first on the wiki; a wiki page is a fork that records its origin. Librarian forks; Archivist never copies.
  • G1 · Classification — every file is marked circulating (federate) or sealed (stay in git: chronicles, plans, drafts, version-history, audits). Only circulating content passes.
  • G2 · Coherence — labels/slots/numbers match the canon: conjecture numbers vs the register, cast tiers/sigils vs the head grimoire, no foreign labels.
  • G3 · Attribution — every page carries upstream:, author, and license; vendored content is credited to its real author, never to us.
  • G4 · Projection — content is shown at the right compression altitude (spellbook→narrative→skill→proverb→spell); the guide surfaces the transmissible layer and links down to source.
  • G5 · Hyperlink coherence — cross-links derive from the graph edges; every link resolves; no orphans.
  • G6 · Distribution — content routes to the correct sibling site under canonical slugs; no cross-site collisions.

Back — contributions into the canon (G7)

  • G7 · Fork-back — an external edit returns to the git canon only through coherence (G2) + attribution (G3) + a First-Person sign-off (OPEN→SIGNED). The page journal is the lineage; a merge-back step proposes a diff into the source repo for signing — it never auto-commits.