The standard door

State what you need. A person reads it.

Not a chatbot, not a router, not a form that disappears into a queue. One sentence about the outcome you are after, filed to a named human here — and nothing about you is matched, ranked or passed on without somebody on each side agreeing to it.

What it does, and what it refuses

The panel drafts a message in your own mail client. You see the exact bytes before they leave and you are the one who sends them, which is why it can honestly say it makes no network calls of its own. It stores nothing — the draft dies with the tab. It sets no cookie, loads no third party and carries no pixel. Those are not policy sentences: a test greps the served bundle for fetch, XMLHttpRequest, sendBeacon and every storage API, and the build fails if one of them appears.

A door with nobody behind it refuses to render at all. If the script cannot name an accountable human it shows nothing rather than collecting into a void, which is the only honest behaviour available to an intake surface with no server behind it yet.

This is not the ladder

/join is the ladder: what an organisation publishes at its own domain, and what each rung earns it. That page assumes you have an organisation and a domain to publish from. This one does not. If you want a partnership, a pilot, an introduction or an answer, and none of the four rungs is the shape of it, say so here in a sentence and a person will read it. A door that only fits people who already know the vocabulary is a door for nobody.

The same door, everywhere

The same dependency-free script runs on every property in the estate, and each files to its own named human rather than to a shared inbox — the queue belongs to the property you arrived at. The widget is the Mesh Concierge, built by Magician, a portfolio company; we serve the version they publish, byte for byte, and a test fails if our copy drifts from theirs.