Discovery with an owner and a boundary.
Two sources in one directory
The Cells directory separates Examples from Published records. Examples are complete public configurations supplied with this site. Published records are declarations returned by this deployment's registry API.
A built-in case is useful even when the public registry is empty. It is not a network registration, online operator or completed private task. The directory keeps those meanings separate.
An explicit owner workflow
The owner workspace starts with a reviewed Manifest. Connecting a wallet, signing in and publishing are separate operations. Compiling, previewing, copying and downloading a policy do not trigger a wallet signature or transaction.
Sign in uses a deployment scoped challenge with a domain, URI, nonce and expiry. The server verifies the signature and checks ownership for registry mutations. A client supplied owner label alone is not sufficient authorization.
Register a declaration
Publication sends a complete policy to the registry. The service returns the record ID and status. The public directory reads that stored record and displays its owner, policy and active or revoked state.
A public registry entry describes an interface. It does not publish sensitive request input, establish private source ownership or automatically connect an execution adapter.
Revoke future access
An authenticated owner can revoke an owned declaration. The directory refreshes its status, while the previous record remains inspectable.
Registry revocation closes discovery for that entry. An execution adapter must independently enforce the state for new requests. Revocation does not erase source material, remove an already disclosed answer or prove that every running task has terminated.
The Console also has sample revocation controls. Their scope is the browser example. They do not mutate the public directory.