Concierge
State what you need. A person reads 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.
Why a door rather than a contact form
This firm publishes no relationship it cannot evidence — the rule that governs alliances governs intake too. A form collects and files you somewhere; a door hands one sentence to one accountable person and does nothing else with it. Nothing you write is matched, ranked or forwarded without somebody on each side agreeing to it.
The widget is the Mesh Concierge, built by Magician. We serve the version they publish, byte for byte, and a test in this repository fails if our copy drifts from theirs.