Brand and protocol, split on purpose
The formats under the hat
Magician is the name humans remember. Underneath are two deliberately boring wire formats, because institutions adopt boring formats — versioned, strict, and verifiable offline with nothing but a hash function.
| Format | Tense | What it carries |
|---|---|---|
trust/1 | present, decaying | A consented, multidimensional edge between people: domains with authority and register, strength with register, provenance, renewal clock. Private tier by default. |
introduction/1 | past, sealed | What an introduction produced: intent, path, consents, outcome — hashed over canonical JSON, append-only, verifiable by anyone. |
beacon/1 | present, published | A sovereign circle’s reachability: per capability, a hop bound, a trust band, a register — no identities, no membership, no counts. The parser refuses a beacon carrying any of them, so two organisations can discover a trusted path exists between their private graphs without either revealing its graph. |
Two formats because the two tenses are shaped differently on purpose — the estate’s rule, applied here: a present-tense claim decays and is never sealed; a past-tense fact is sealed and never decays. Making them symmetric breaks one of them.
Publication is gated, and the gate is the promise
Both formats are documented in this repository and licensed Apache-2.0, and neither is promoted as a standard until the first Circle we do not control adopts them. Captive adoption — a portfolio company, a client, a shareholder — is evidence about a relationship, not a format; the estate counts it separately and never headlines it. The current state is always on the roadmap.
The sealing discipline is shared with the wider mesh: the same canonical-JSON-plus-sha256 shape that seals settlement records at flashyos.com and the public ledger verdict at claimyour.gold, so one open verifier can eventually cover all of it.