Which lanes you open, what you ask, and what you owe
frontdoor/1 — a published door: which lanes an organisation opens, what it asks at each, and what it owes in return. Emitted per repository, validated across an estate, verified from the applicant's own domain.
A published door: the lanes an organisation opens to strangers, what it asks at each one, and what it commits to in return. Emitted per repository, validated across an estate, and verified from the applicant’s own domain rather than from a form they filled in.
Installing it puts these commands on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
flashyos-frontdoorflashyos-frontdoor-verifyflashyos-frontdoor-auditflashyos-frontdoor-registryflashyos-frontdoor-joinflashyos-frontdoor-surfacesApache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.