Technologies Search

RJV Technologies

Software you can operate and verify

We research how computation can be checked, then build software and AI systems around the work your organisation needs to do.

Explore systems Discuss a project

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.

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 22 October 2026.