A Gord Holdings company on the FlashyOS mesh
Magician.
Ask

The standard door

The Mesh Concierge

One dependency-free script that puts an intent door on any site. A visitor types what they need; the filing goes to a named human at that property — their queue, their graph. The panel below is the live widget, not a screenshot.

What it does — and refuses to do

Layer zero is intake, done honestly. The widget drafts a filing through your own mail client to the accountable human this property’s charter names. It makes no network calls of its own, stores nothing — the draft dies with the tab — and tracks nothing. Those are not policy statements: a test greps the served bundle for fetch, XHR, beacons and storage APIs, and the build fails if any appears. A door with nobody behind it refuses to render at all: the script requires a named contact or shows nothing.

What happens next is the same consent machinery as everything else here: a human reads the intent, and the loop — path, consent, introduction, sealed outcome — runs only if they say yes. Agents suggest; humans consent. The concierge is the suggestion box, never the decision.

Adopt it on your property — the Activation

Every new property in the estate, and any partner site, carries the Magician layer by shipping four artifacts. This is the whole standard; there is no second definition:

  1. The script, served. concierge.js at your root, included once in your layout with data-contact naming a human at your organisation. Filings go to your queue and build your graph — sovereignty is enforced at the widget, not promised in prose.
  2. A /concierge page. Five lines: an element carrying data-magician-concierge-slot plus the same script. The page you are reading is the reference — this site passes its own activation check in its own test suite.
  3. The handshake pointer. Your /.well-known/flashyos.json carries join pointing at your door, so machines find it the way people do.
  4. A /demo page. Something a stranger can try before any trust has been extended in either direction — no account, and fictional data that says so. A claim with no demo is a brochure. This property's is the whole loop, live in the browser.

One dependency-free script verifies all three before anything is installed: node vendor-check-activation.mjs. It exits naming the missing artifact, or passes silently. Committed is not served — deploy, then let the estate’s join survey confirm from outside.

The layers above, so nobody builds them twice

L1 adds deterministic want-suggestions from the same engine that powers the demo — still client-side, still no server. L2 adds real conversation on metered inference. Every layer upgrades the same script; the three activation artifacts never change shape, so adopting today is not a migration later.

Join Magician · The twelve concepts · The mesh this property belongs to