The console
The regulatory artifact and the auditor gateway, for both products.
Updated June 2026
The console is the firm's regulatory artifact and the auditor's gateway. It is not a daily review queue, and a compliance officer is not expected to live in it. Day-to-day signal arrives in Slack, Teams, and email; the console is where proof lives when a board, a carrier, or an examiner asks for it, and where a flagged event gets investigated in depth.
The surfaces
| Page | What it serves |
|---|---|
| Overview | The firm's AI traffic at a glance: a flow of employees to the AI providers they used, and a Servers view of which AI surfaces are covered |
| Intelligence | Three question-led lenses on usage: spend and value, coverage and proof, reach and exposure |
| Threat Coverage | Which risk categories the deployment currently covers |
| Compliance | Framework posture against the firm's rule set, the audit trail, examination mode, report packets, and the identity vault |
| MCP Tools | Every tool server with its mode, activity, and the server-to-employee map |
| Activity | The event stream and the exception queue, where each event narrates itself |
| Rox | An assistant that answers questions from the firm's own record |
The signed record
Every interaction joins one append-only record. Each row is canonicalized, hashed, Ed25519-signed, and chained to the previous row, back to a fixed genesis entry: device interaction events are signed on the device that produced them with that device's own key, connected operations are signed by the workload that performed them, and console actions are signed and chained per tenant. An exported packet carries the chain and the public keys, so an examiner can verify it offline with the bundled verifier: re-derive the bytes, check every signature, walk the chain. A modified or deleted row breaks the walk visibly. Every console page carries a small chain pill confirming the record is intact and current.
Risk is a band, not a number
People are never given scores. Where the console characterises an employee's pattern, it shows one of three bands, within baseline, watch, or attention required, with a one-sentence narrative of why. The composites behind the band stay on the server and are not displayed, by design: a number on a person invites ranking, and ranking is not supervision.
When the examiner shows up
Examination mode mints a scoped, read-only session for a named regulator over a chosen period. The minting itself is written to the signed record, so there is evidence of what was opened, to whom, and when. Report packets cover the recurring asks without assembly work: a board pack, a cyber-insurance pack, a regulator pack that includes the hash-chained log and the signing key, and an ISO 42001 pack with the statement of applicability and control evidence.
Rox
Rox is the console's assistant. It answers from the firm's record through a fixed set of tools: summarise posture over a period, list events touching a framework, read recent flagged events and active policies, check the chain head, and queue a report packet. Answers cite the underlying events with links, and Rox does not speculate past what the tools return.