Vocabulary, declared once
Glossary
Every term below means exactly what the engine enforces — the definitions and the code cannot drift, because the code is where the definitions came from.
- Intent
- One sentence of what you need, plus the capability tags (wants) that make it routable. An intent with no wants is refused: it would be invisible to routing.
- Trust edge (trust/1)
- A multidimensional, decaying, consented record of a relationship: domains and authority, strength with its register, provenance events, and a renewal clock. Private by default.
- Sealed outcome (introduction/1)
- The record of what an introduction produced — path, consents, outcome — hashed over canonical JSON so anyone can re-verify it offline. Append-only; “none” is a real outcome.
- Register
- How a figure knows what it claims: measured (from sealed outcomes or recorded behavior), asserted (somebody said so, and we can name who), or estimated (inferred). Every number in Magician carries one.
- The veil
- The rendering rule for paths: your own first hop is visible; every node past the consent frontier shows only a domain hint until the person whose edge it crosses says yes.
- Consent frontier
- The furthest point along a path where every hop owner has consented. Reveals advance one yes at a time and never skip.
- Silent decline
- A declined hop renders to the requester exactly as a path that never existed. A visible refusal would leak the relationship data the refusal was protecting.
- Decay
- Trust is perishable. Edges age from fresh to aging to stale on a renewal clock; stale edges route only at the estimated register. Decay is derived — there is no expiry field to write, by design.
- Provenance
- The events a trust claim stands on: transactions, introductions, investments, work together — or hearsay, which caps the edge at estimated. A claim with no basis is refused.
- Hearsay edge
- An edge recorded secondhand. It may suggest a path exists, but it can never contribute better than estimated, whatever its author typed.
- Path
- A sequence of trust edges from you to a capability, ranked by match quality first, then fewest introductions, then trust. Its trust carries the weakest register seen along the way.
- Hop
- One edge crossed in a path. Each hop names the person whose consent it needs. Traversing an edge against its asserted direction downgrades that hop to estimated.
- Routing power
- The one measured figure a person carries: sealed non-none outcomes their edges helped route. Nothing a person does alone can move it.
- Circle
- A sovereign graph with an owner — a person, fund, family office, university. Circles federate by exposing permissioned capabilities, never membership.
- Federation
- Circles answering each other’s intents under scoped, revocable grants. An identity is defined by exactly one graph; everyone else borrows it.
- Capability tag (cap/)
- A routable want: cap/robotics-manufacturing, cap/distribution. A tag names a kind of ability, not a company that has one — tags are vocabulary, never nodes.
- Superconnector
- A person whose relationship graph routes an outsized share of an economy’s coordination — and who, before Magician, could query almost none of it.
- Consent inbox
- Where introduction requests wait for their owner, ranked by stated consequence and aging loudly — the estate’s operator-lane pattern applied to trust.
- Local-first store
- Your graph lives in files you hold, git-guarded and never uploaded. “Nothing leaves without consent” is an architecture, not a policy page.
- Relationship succession
- The consented handover of a graph’s routability and outcome history — institutional memory without expropriating anyone’s contacts.
- The mesh
- The FlashyOS network of chartered organisations this property belongs to: handshakes, directories, conformance, sealed records. Magician is its human-trust layer.
- Handshake (flashyos/1)
- The discovery document at /.well-known/flashyos.json: who this org is, what it offers, where to join. Magician’s is derived from its charter so the two cannot disagree.
- Trust Graph
- A relationship graph whose edges record what a connection is made of — domains, strength, provenance, decay — rather than the fact of contact. A contact list tells you who you have met; a trust graph tells you who would take your call, about what, and on what evidence.
- Relationship Capital
- The economic value held in a person or institution’s trusted relationships — real, differentiating, and almost universally unbooked, unmeasured, and lost on departure. Magician makes it recordable (trust/1), routable (trusted paths), and provable (sealed outcomes).
- Institutional Memory
- What an organisation still knows after the person who knew it leaves. For relationship businesses it is the map of which relationships exist, what each produced, and where authority lives — kept without expropriating anyone’s contacts. See relationship succession.
- Permissioned Introduction
- An introduction in which every crossed edge’s owner consented with the request in front of them — the only kind Magician makes. Contrast the connection request (no intermediary consent) and the cold outreach (no intermediary at all).
- Relationship Intelligence
- Computation over a trust graph: which paths answer an intent, which edges are decaying, which latent connections nobody has noticed, which relationships actually produce outcomes. Distinct from contact management, which computes over names.
- Trusted Path
- A sequence of trust edges from an intent-holder to a capability, ranked by match then introductions then trust, carrying the weakest register seen along it, and explainable hop by hop from fields a user can open. The unit the router returns.
- Network Intelligence
- What a network knows that none of its members knows: that a path exists, that a fit is latent, that a relationship converts. Magician’s constraint is that network intelligence must be computed without exposing what participants are not entitled to see.
- Human Capability Graph
- People annotated with what they answer for (cap/ tags) and connected by trust — the human half of the two questions of an economy. Its organisational counterpart is the mesh’s capability directory.
- Institutional Relationship Graph
- A sovereign graph owned by an institution — a fund, family office, university, government ecosystem — routable under its own policy, federating through beacons, never uploaded into anyone’s global pool.
- Agentic Networking
- Software agents doing the mechanical 95% of networking — detecting latent fits, preparing cases, negotiating logistics — under the rule that makes it trustworthy: agents suggest, humans consent, and no introduction happens without a named human’s yes.
- Intent-Based Networking
- Starting from what you need to accomplish (an intent with routable wants) instead of who you might meet. The network’s job becomes routing, not browsing — there is no feed to scroll because there is nothing to browse.
- Beacon (beacon/1)
- A circle’s published reachability summary: per capability, a hop bound, a trust band, and a register — no identities, no membership, no counts. The parser refuses a beacon carrying any of them. Reading one discloses nothing to its author.
- Graph Learning
- The loop’s last step: a sealed outcome renews the edges its path traveled, adds an introduction event to their provenance, and (for non-none outcomes) upgrades their register to measured. Values never inflate — the outcome is evidence about how we know, not licence to know more.
- AAO
- Agentic Autonomous Organization — the charter standard at flashyos.com: named roles, a human accountable by email address, and approval thresholds an agent cannot cross alone.
- Mesh Concierge
- The estate’s standard door: one dependency-free script that lets a visitor state an intent on any property and files it to a named human at that property — their queue, their graph. Layer zero makes no network calls, keeps no storage, and does no tracking; a test greps the served bundle for all three promises.
- The Activation
- What it means for a property to carry the Magician layer: concierge.js served, a /concierge page, and a handshake whose join points at it — three artifacts, verified by one dependency-free script that runs before an install. A property that passes is activated; there is no second definition.