Search

Where science actually begins

We design, build and verify software and AI systems for organisations that need control of their data, operations and infrastructure.

Open platform Explore systems

Or discuss a project with the engineers who build it

What we publish, counted now

The counts load in your browser.

What do you want to do?

Choose what you came to do and its layer comes forward. Every link is a published record or a working page; find your route if none fits.

  1. Systems you run

  2. Engineering you commission

    Scope, acceptance tests and handover are agreed before work starts.

    Services · Stages and deliverables · Discuss a project

  3. Research you read

    The questions, methods and published results, including what is not established.

    Research programme · Publications · Limitations

  4. Claims you check

    The register holds 13 graded public claims, each with the check behind it. This deployment has not run a workflow yet.

    Evidence register · Security controls · Service status

  5. Ownership you keep

    Hosting, data, recovery and handover, stated before you commit.

    What you control · Host it yourself · Get RJV

Inside the platform

See how a change is checked

A change has a named caller, a current grant, a result and a record you can inspect with the right access.

Read the evidence register or inspect the security controls.

From request to recorded result
  1. IdentityEstablish who is making the change.
    Who acts
    The session check or the API key check for a machine caller.
    Takes
    The session cookie and its request token or the API key.
    Produces
    The acting principal, loaded from the identity record.
    If refused
    The request is answered 401 and nothing is read or changed.
  2. AuthorityDecide whether this principal may perform this operation on this resource.
    Who acts
    The authority layer, from grants the runtime can read and never write.
    Takes
    The principal, its current grants, the operation and the resource.
    Produces
    An allow decision bound to the request, with the request itself recorded.
    If refused
    The request is answered 403; the refused request stays on the record.
  3. TransactionCarry out the authorised change.
    Who acts
    The operation that owns the data, in one database transaction.
    Takes
    The validated request and the state it was checked against.
    Produces
    The committed change.
    If refused
    The transaction rolls back and no partial change remains; a stale revision is answered 409.
  4. EvidenceRecord what happened.
    Who acts
    The evidence layer, inside the same transaction as the change.
    Takes
    The principal, the grant, the operation, the resource and the outcome.
    Produces
    An entry linked into the hash chain, verifiable by recomputation.
    If refused
    If the entry cannot be written the change does not commit either.

Most changes commit with their audit record. Workflow approval decisions and run expiry commit first, then report whether the record was written.

Intelligence and digital agency

A native model, and what it actually did

AGI is our intelligence programme, and its language model is our own: we trained it and we serve it on our own host. The figures beside this text come from the model itself when this page was drawn. They show its generation and how many decisions it took where its teacher would otherwise have completed them.

The portal is where you operate our systems, and it is separate from the intelligence. The AGI page sets out the programme, the governed execution beneath it and what the core measures about itself.

Read what the model reports and what we claim
The native model's share of the decisions it was offered Of 6 decisions, 5 were taken by the model and 1 by the teacher. The model reports a composition score drawn at 96.9 percent. The model answered 5 of 6 (83%) Composition
Both figures are the core's own report. Composition is measured against the evaluation the core ships with; this page does not present it as a comparison with any other system.

Commission engineering

Agree what delivery means

Set the scope, acceptance tests and responsibilities before work starts. Agree what you need to operate, maintain and recover the system after handover.

See the engineering stages and deliverables

Last reviewed 13 November 2026.