Raw actor-id boundary
Closes: a raw sov:/human: id — whose slug IS the human's callsign — reaching a machine surface.
The organism · its privacy architecture, proven
All 15 privacy boundaries proven active — just now, live. The most recurring leak in this organism's history is a privacy boundary that exists in code but is left unbound at one machine surface — invisible until an audit walks it. This page turns that audit into a living account: it lists every boundary it enforces and re-proves each one right now, by running the real redactor on a synthetic probe. A boundary reads active only when the redaction just happened — so if one ever regresses, it shows here as a gap, out loud, before it becomes a leak.
Raw actor-id boundary
Closes: a raw sov:/human: id — whose slug IS the human's callsign — reaching a machine surface.
Obelisk denial-receipt boundary
Closes: a crossing actor's raw sov:/human: id on the machine ledger an agent polls to AUDIT the organism (the 9th carrier).
Held-spam signal boundary
Closes: a gate-rejected or quarantined spam signal's free-typed name + body reaching the Record.
Contribution feed boundary
Closes: a signed-in Sovereign's raw id + held-spam contributions on the polled machine feed.
Whisper archive boundary
Closes: a Steward-eyes-only whisper event crossing a public timeline.
Whisper receipt boundary
Closes: a whisper signal's Steward note copied onto its public receipt.
Confluence slug boundary
Closes: two conveners' crossing callsigns (bare slugRoots) deanonymized on a confluence surface.
Shared-cache audience boundary
Closes: one Sovereign's personalized page or proof card being stored by a SHARED cache under an actor-free URL and replayed to every later caller — the 12th carrier, and the first in the AUDIENCE dimension rather than the contents one.
Credential hand-off boundary
Closes: a shared cache storing the response that MINTS a Sovereign Key and replaying that credential to the next caller. This one is a CLASS bound on a LATENT instance and says so: all six sites are 303s, which RFC 9111 omits from the heuristically-cacheable statuses, so nothing was being stored. That was a status-code accident rather than a boundary — the first cookie-setting 200 would have put a Sovereign Key into a shared cache.
Connection boundary
Closes: the first request of a visit — a typed address, an http:// link, a QR code — leaving the browser in cleartext where an on-path attacker can answer the redirect themselves and proxy the site. Every other boundary here governs what a response CONTAINS or who may RECEIVE it; this one governs the pipe they all travel through, and it was the only one never declared.
Request-provenance boundary
Closes: a forged cross-site request MAKING the organism mint a Sovereign Key into a victim's browser — login-CSRF / session fixation. The three sibling rows above reason about the RESPONSE (who receives it, what it hands back, the pipe it travels); this is the one that reads the REQUEST: did this exchange originate here? A body leak spends an identifier and a Set-Cookie leak spends a credential — but a forged request spends the WHOLE session, binding the victim's browser to the attacker's identity so every act they take is recorded as the attacker's.
Navigation-capability boundary
Closes: a path-shaped value whose backslash becomes a browser authority, turning a local redirect into an off-origin navigation capability.
Failure-projection boundary
Closes: a payment provider's or a runtime's own words travelling out under the organism's name. Every row above governs a SUCCESS projection — a value VEILOS wrote and then chose to publish. A failure answers with text VEILOS did NOT write, so no projector had ever been applied to it: Stripe's "No such customer: cus_…" reached an unauthenticated visitor as the receipt code, because normalizeMutationReason SHAPED the value without ever BOUNDING it.
Identity-addressing boundary (capability monotonicity)
Closes: the public tag reversing into the raw sov: id. Every row above asks what a projection may CONTAIN; this one asks what it may HAND BACK relative to what it was GIVEN. S228 made travelling proof cards address a Sovereign by tag precisely so the callsign-bearing id would stop riding along — and the page those cards point at published that id anyway, so one weak address bought the strongest one and the anonymity promise held in the H1 while breaking one element below it.
Anonymity-set cardinality boundary
Closes: a Sovereign being named by ARITHMETIC rather than by a field. Every row above governs what a projection may SAY about a person; this one governs how many people a redaction has to hide among. `commonsGraph` labelled every un-opted-in convener "a Sovereign" and published the population total in the same object — and a reader can count the NAMED ends by eye but never the anonymous ones, so one subtraction gives k. At k = 1 the placeholder is a unique designator: every "a Sovereign" on the page is provably the same individual and their whole convergence neighbourhood links into one profile, with the projection itself supplying the proof of uniqueness.
The ceiling on the public address
Every Sovereign's public address is four hexadecimal characters — 65536 possible addresses in total. When two inhabitants share one, VEILOS refuses to guess which of them you meant, so a proof card that has already travelled stops resolving. That refusal is correct, and it is why this number is published before it matters rather than after.
0 inhabitants · 0 distinct addresses · no address is currently shared.
Why prove them live
A privacy boundary that exists in code but is unbound at one projector is the organism's single most recurring leak. This census re-proves each boundary live by running its real predicate on a synthetic probe: a boundary reads `active` only when the redaction just happened, so a regression surfaces here — publicly, out loud — before it becomes a leak.
every probe is a synthetic literal; no real actor id, name, or body is read or shown — the census proves each boundary WITHOUT exercising it on anyone real
Machine census (JSON) → · The Failure Census → · The Abstention Ledger → · The Recovery Covenant →