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 / The Private Knowledge Network

๐Ÿ•ฏ๏ธ The Private Knowledge Network

The public guide you are reading is a static snapshot โ€” a projection, rebuilt from the live wiki farm. The farm itself is something more: a virtual private knowledge base, shared over a private mesh network (a tailnet) with the people and agents invited into it. No cloud host holds it; each participant reaches the others' machines directly, end-to-end encrypted, as if they shared a room.

What the network carries

  • The live sites โ€” every federation site you see here, but writable: fork a page, write on it, and the journal carries your lineage back.
  • The files โ€” each page's assets (source documents, runnable bundles, decks) served by the wiki itself, not frozen copies.
  • The embassies โ€” always-on small machines (a Raspberry Pi is enough) that host the shared record while personal machines come and go. An embassy accepts no direct writes: to change what it serves, you fork on your own site and the keeper countersigns. The fork is the reply.

The pattern

  1. Join the mesh โ€” install a mesh VPN client (we use Tailscale) and accept the invitation that shares the network with you. Your machine gets a stable private address; nothing is exposed to the open internet.
  2. Open the shared address โ€” the farm serves each sister site on its own port of the shared host. The address is not published here: it arrives with your invitation, the way a letter carries its own key.
  3. Bring your own wiki โ€” run a local farm of your own (wiki --farm), fork what you need, and serve your sites back into the mesh. Now the knowledge base has two homes, and the federation is real.

The trust posture

The mesh is default-deny: only the wiki ports are open, everything else is refused, and file-sharing protocols are blocked everywhere. Reading is free inside the network; writing follows the same gates as this guide โ€” Distribution Gates out of the canon, fork-and-countersign back in. A private network does not suspend the ceremony; it is where the ceremony lives.

Why private-first

The public snapshot is the publish layer; the tailnet is the workshop layer. Drafts, working assets, and half-formed pages circulate privately among invited peers first, and only what passes the gates is projected here. That order โ€” private workshop, public record โ€” is the whole architecture of the guide.

ask for an invitation; the address travels with it.

โ† Welcome Visitors ยท Federation Map ยท Contribute

Shared infrastructure across workshops

Small-machine embassies, including Raspberry Pi hosts, support multiple knowledge communities. HH Workshop contributes a related local learning and consent-led workflow. Shared hosting and maintainers belong in the resource model described by Community resources and trust tasks; actual host access remains invitation- and policy-specific.