01
Membership is open; standing is earned
You should be able to: Explain why the door can be both open to everyone and gated at once.
A front door in this estate answers two questions that used to be tangled: may I approach you, and what will you do for me? The first answer is always yes — approaching is open, it costs a couple of minutes, and it puts you on no list.
The second answer depends on what you publish at your own domain, because that is the part a stranger can verify without trusting the organization on the other side. A credential that lives only in someone else’s database is not standing; a file you serve at your own domain is.
So the door is open and the ladder is steep on purpose. Nobody is stopped from knocking; what you are owed in return is a published schedule rather than a private decision.
Source: Flashy OS — join the mesh
02
Lanes: the door knows which question you are asking
You should be able to: Match an approach to the right lane, and know a lane you should not use here.
frontdoor/1 defines a small set of lanes — build on it, wire up an agent, work together commercially, raise or invest — and a property opens only the ones that make sense for it. A platform does not solicit capital from its own documentation, so it simply does not open that lane and says where it lives instead.
Each lane carries its own question, written twice: a precise version for the few who already speak the vocabulary, and a plain version anybody can answer. The plain one is what a stranger is asked; the precise one is the contract behind it.
A lane a door opens must lead somewhere, and a lane it does not open must still be named — never a dead end. The failure to avoid is a page that invites an approach the organization has quietly said it does not take.
Source: Flashy OS — @flashyos/frontdoor
03
The ladder: cost and what is owed, published
You should be able to: Read a rung as a two-sided contract rather than a status level.
The ladder is the schedule of rungs. The open rung costs two minutes and owes you an honest "we read everything and promise nothing." The next rung asks you to publish a charter — about twenty minutes — and owes you a reply within a set time from a named human, not an alias.
Higher rungs ask for real work — being in the mesh, then running something of yours on something of theirs — and owe correspondingly more: a listing, a place in a pipeline with a decision date, a reasoned no in writing. Every rung names both halves.
The whole ladder is published once for the estate and cited everywhere, so climbing at one door and arriving at another owes you the same thing. A schedule kept in two places is two schedules the day one is edited.
Source: Gord Holdings — how to engage
04
A rung is not authority
You should be able to: Explain why publishing a file at a domain proves control of the host and nothing more.
The sharp caution the door carries: a rung buys a reply and a place in a queue. It never buys authority, money, or access. Publishing a file at a domain proves someone can write to that host — it does not prove the organization is who it says it is, and the door does not treat it as though it did.
This matters because a door is trivially easy to mistake for an authorization: a file at a domain, naming an organization, producing something that looks like a permission level. Where real authority is needed it is delegated and verified through the identity layer, and the chain is checked — the front door is not that check.
The practical rule when you build one: the moment a fetched file starts being treated as a permission, you have turned a front door into a vulnerability. Keep the two jobs — prioritize an approach, versus grant an authority — strictly apart.
