Three levels, and only the third is ours to grant
Run the FlashyOS conformance suite against any domain. Checks the flashyos/1 handshake, the AAO charter, and the three runtime facts a file cannot prove. Exit 0 only when the level you asked for is actually met.
Runs the whole suite against a domain: the flashyos/1 handshake, the AAO charter, and then the three questions a file cannot answer — who authorized this agent, can it be revoked, what did it do. Those last three are read from the register rather than from the site being checked.
Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
flashyos-conformApache-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.