Skip to contentThe claims register is public. 27 verified, 7 struck.

What is demonstrated, what is verified, and what we do not claim.

This is the honest page. It is regenerated from the claims register on every build, so the date below is the date this copy was produced.

The full registerWatch them run

Demonstrated

What is demonstrated. A visitor can watch the behaviour run.

The scenarios the Gate replays are not stage props. The behaviours behind them are re-verified by the platform's own test suites on every full run.

Watch them run
CLM-0100Demonstrated

Every action the platform governs is checked before it executes; an action that fails its checks does not execute.

· kernel adjudication suite — an in-bounds action verified with a signed record; over-limit and authority-breach actions refused

CLM-0106Demonstrated

A complete governed workflow — dispatch refusal, human approval gates, closure control, and an offline-verified evidence pack — was re-executed end-to-end over HTTP on 1 September 2026.

· governed-workflow integration suite re-executed end-to-end over HTTP, green, including the refusal cases and the offline-verified evidence pack

Verified

What is verified. Each sentence sits on the register with a named verifier and a date.

The verifier behind each one

The kernel

  • Same input, same verdict, every time.
  • When the governance layer cannot decide, the action is refused, not waved through.
  • The kernel applies deterministic mathematical governance; if its own checks cannot be discharged at start-up, it does not serve.

The record

  • Every governed action is sealed in a signed, tamper-evident record.
  • Records can be verified offline, without access to our systems.
  • The evidence a period produces can be handed to a third party and verified with Admissible absent.

The governed workforce

  • Agents run under quotas and spend caps, with human approval gates on the actions that matter.
  • An unsafe agent recipe is blocked at compile time, before it can run.
  • An action held for approval resumes by replaying only what was approved — nothing else.

The platform

  • Tenant isolation is enforced in the database itself and attacked by our own adversarial suite in CI.
  • An industry is a configuration file, not a codebase.
  • The industry pack is load-bearing: at boot the governance layer recomputes the pack's rule digest and refuses to serve if it does not match.

Not claimed

What we do not claim. Where a sentence cannot be verified, we do not write it.

How we correct an error

No live commercial deployments

Nobody runs their business on this yet. When that changes it will be claimed here with a verifier, and not before.

Nothing in progress is claimed

Evaluations and certifications that are under way are not named, not counted, and not hinted at until they conclude.

Held capabilities stay off the site

Where a capability is awaiting external confirmation, the sentence is withheld entirely rather than hedged. The struck and held list is public, with reasons.

The struck and held list

Start here

See the current state for yourself

Bring the workflow you trust least. We will show you the verdict, and the record it leaves.

Book a demoThe full register