Software and AI systems you can operate, verify and keep
Build and run software around your organisation’s needs. Retain control of your data, operating decisions and infrastructure.
Each engagement defines the problem, the system to be delivered, the tests that establish completion and the knowledge the customer needs to operate the result independently.
- 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.
- 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.
- 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.
- 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.
The change and its record commit together or not at all. Explore the security controls.
Where to start
Choose the route that matches your question
- You are selecting a system
- Read the catalogue to see what is published, then discuss the requirements, deployment and commercial terms for your organisation.
- You have a problem that needs engineering
- Follow the engagement stages from assessment to handover. See what you receive at each stage.
- You are evaluating technical evidence
- Explore the research programme, publications and evidence register to examine our methods and results.
- You are weighing risk, cost or how to leave
- Start with deployment and ownership, then security and assurance and the commercial terms.
How RJV engineers
Engineering with accountable execution
RJV starts from the requirement and writes down what would show that it has been met. The design then says who may do what and the tests say how completion will be decided.
In the platform RJV runs, every consequential change passes four checks. The system identifies who is making the change, checks that they hold a grant for exactly this operation, carries it out as one transaction and records an entry that anyone with the right to look can inspect afterwards. A change and its record commit together or not at all.
The same separation applies to automated agents. An agent may propose an action and deterministic code decides whether it is allowed. Every component must demonstrate correctness, security and operating evidence.
From requirement to operation
Know what you are commissioning
A useful system starts with a clear outcome. The scope connects that outcome to delivery, acceptance and the responsibilities of operating it.
Explore engineering services- Define the outcome
- Describe the work people need to complete, the information involved and the constraints of the operating environment. Identify the systems that must connect and the people who will use the result.
- Agree the scope
- Set the deliverables, interfaces, responsibilities and acceptance criteria in writing. The quotation establishes the price, delivery arrangements and commercial terms.
- Verify the result
- Assess the implementation against the agreed criteria, including normal use, refused operations and recovery. Record the results needed to make an acceptance decision.
- Take operational control
- Agree the deployment, documentation, training and support needed to operate the system. Establish data export, maintenance responsibilities and the handover conditions.
Customer control
Your systems, your infrastructure, your exit
The platform runs on a Linux server and uses PostgreSQL as its database. It needs no message broker, cache server or control plane run by RJV. Its register of outside services lists the database and an optional mail relay.
Agree the deployment, operating responsibilities and licence in your quotation. The deployment and ownership guide explains hosting, handover, data export and your route to independent operation.
One engineering discipline
Systems, research and customer control
- Systems
- Review the catalogue of published systems and services. Use your workspace to manage your account, agents and authorised work.
- Research
- Follow our research programme, read the publications and inspect the methods and results in the evidence register.
- Customer control
- Our mission connects engineering with human agency. Deployment, handover and commercial terms define how you operate and retain control of your system.
Work with Us
What do you need to accomplish?
Tell us the outcome you need, your operating constraints and the systems involved. The engagement starts with assessment, an agreed scope and a quotation.
Security reports follow the disclosure process and complaints follow the complaints procedure.
Last reviewed 22 October 2026.