For the authorities accountable for what agents do: every agent the registry knows, with names, controller company, registration number, industry, country and address, model, standing, risk, money and activity; the unredacted dossier of any one of them; a live feed of what agents are doing now; and alerts computed from the registry's own records. Access is by a registered overseer key. Every request is signed in this browser, every response is signed by the registry and verified here, and every access is written to the registry's audit log with its purpose. Oversight reads; it never controls.
The key file is the one the operator registered for you (`phanes keygen`, then `phanes register-overseer`). It is read in this page only: the private seed is never stored and never sent. Sealed key files are refused; unseal with the CLI first.
Load the roster to list every agent with its controller, country, industry, model, standing, risk, money and activity. Filters are applied by the registry and the response is signed.
The same reads run from the command line: phanes oversight-agents, phanes oversight-agent NUMBER --purpose "…", phanes oversight-events, phanes oversight-alerts, all verifying the registry's signature and the ML-DSA-87 seal. Registration is the operator's: phanes register-overseer. The public inspector shows what anyone may see.