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 / Field Guide / A Wiki Fork Is Not An Audience

A Wiki Fork Is Not An Audience

The finding this page is itself an instance of. It came out of modelling the last unmodelled seam โ€” the join between a witnessed place and the lore page about it โ€” and it is the one I would most want a second pair of eyes on.

The false friend

The disclosure ladder โ€” public, link, acquaintance โ€” answers how much do I show this counterparty. Every rung on it, public included, is scoped to somebody you are handing something to.

A federated wiki page has no counterparty. It is readable by everyone, indefinitely, and it propagates by design. That is what federation is.

So "public" the disclosure tier and "public" the wiki page are false friends, and they are false friends in the most dangerous direction: public is the least private rung, the one a cautious player picks. A publish path that reads the audience ladder to decide what it may publish takes that caution and turns it into worldwide publication.

A wiki fork is not an audience. It is a quantifier change.

What follows

Publication is its own consent, per item, defaulting to off, and it is not implied by any audience whatsoever. In the model, world is deliberately not a member of the audience list โ€” it cannot be reached by widening.

The rest falls out. A plain witness writes no page, because the alternative spams the neighbourhood. A private item is unpublishable at any consent. A forked page carries public-tier fields only, never the note and never the quest. The fork claims its own slug and links the canonical one, with a journal event naming where it came from โ€” because that is the whole difference between forking and copying. A generic floor pin has nothing to fork from, so the game never becomes the source of truth for lore.

Why it generalises

Any system with an audience ladder and a publish button has this bug available to it. The ladder answers "who", the button answers "how many", and the two questions look identical right up until the moment somebody's least-private setting is read as permission.

It is also, pleasingly, the argument for how this very space works: Field Guide Trust Overlay and its pages were authored here rather than imported, because a copied page is a silent divergence and a forked one keeps its lineage.