The concierge

What happens to it

A person reads it. That is the whole of layer zero, and saying anything more would be describing software that does not exist yet. The panel drafts a message in your own mail client, so you see the exact bytes before they leave and you are the one who sends them — which is why it can honestly claim to make no network calls of its own. It keeps no draft, sets no cookie and loads no third party. Those are not promises in a policy: a test greps the served bundle for fetch, XMLHttpRequest, sendBeacon and every storage API, and the build fails if one appears.

Why a door and not a form

A form collects; a door files. The distinction matters here because nothing about you is matched, ranked or shared without a person on each side agreeing to it — the same consent rule this property applies to settlement records. An intent filed through this panel is held by this property, answered by this property, and travels no further unless somebody says it may.

The same door, everywhere

This panel is a machine surface with a human face: the same dependency-free script runs on every property in the group, each filing to its own named human rather than to a shared inbox. If you would rather see the full ladder first — what an organisation actually does to join the mesh, in four rungs — that is /join/, and the mesh-wide door is flashyos.com/join.