Industries · Government

Records that outlive every vendor.

Public records must be checkable long after the contract that produced them ends. R-Series gives every AI-assisted step a hybrid post-quantum receipt that verifies offline, with published algorithms and vectors published under licence, and no call home to DCS.

Book a briefingStandards we build on
SignatureEd25519 + ML-DSA-65
FederationIn development
CertificationsNone claimed yet
00 Public records, AI-assisted

When software helps decide, the record must survive the software.

Public bodies are adopting AI to draft letters, triage cases, summarise evidence and route requests. Each of those steps can affect a citizen, and each must be explainable years later: at an appeal, an audit, a parliamentary question or a public inquiry, often long after the vendor contract has ended and the original system has been switched off.

R-Series gives every AI-assisted step a receipt that verifies offline. The receipt records the intent, the policy that applied, a hash of the result and the key that signed it. Anyone holding the department's public key can check it with the public verifier and test vectors (published under licence), with no account, no network call and no permission from DCS.

Each department holds its own keys and issues its own receipts. Records can be honoured by another agency through a shared trust registry, so a second department can rely on a record without calling the first. Federation between our own deployments and between separate organisations is in development.

Signatures are designed hybrid post-quantum: a classical Ed25519 signature next to an ML-DSA-65 signature on every v2 receipt (in development), so a record signed now stays checkable as national post-quantum migration timelines arrive.

A public record has to outlive the system that wrote it.

01 Requirements we design for

Sovereignty is a technical property.

A department should be able to keep, check and share its records without depending on any supplier, including us. These six properties are how we test that, each with its real state today.

01 · VERIFY

Verify without us

Published algorithms, a public verifier and vectors published under licence; the specification is shared under NDA. A receipt's signatures check with the issuer's public keys. The public verifier is in production for Website Maker receipts.

In production

02 · HYBRID

Post-quantum by default

Ed25519 and ML-DSA-65 are designed to sign every v2 receipt. The key-exchange algorithm protects transport only; it never appears inside the receipt.

Staging · release candidate 4

03 · FEDERATE

Federation across agencies

Receipts issued by one department, honoured by another, under a shared trust registry. A formal "independent verifier" (different organisation, different code) must exist before any certification is claimed.

In development

04 · KEYS

Department-held keys

Every v2 receipt carries the registry root and key epoch, so a verifier knows which key was valid when. Production keys are created only after certification.

In development

05 · MEMORY

Sovereign memory

Sealed storage for agent memory under a hybrid post-quantum envelope (HPKE with X-Wing). In development.

In development

06 · COMPUTE

Confidential compute

Receipts that bind a measurement of the software that ran. Today this is software-measurement attestation only, in simulation; hardware enclave quotes sit on a longer clock.

In development

02 How a public record stays true

Issued, receipted, sealed, shared.

Public record01 / 04
01 · THE INSTITUTION

Every department is an issuer.

Each ministry and agency holds its own signing keys and issues its own receipts. There is no central vendor in the middle and no shared master key: a compromise in one department does not let anyone sign for another.

  • Keys live behind a key handle in the department's own key store
  • The registry records which keys each issuer may use, and from when
02 · RECORDS ARRIVE

Every action becomes a receipt.

Applications, decisions, AI-assisted drafts and approvals arrive as receipts. Each one is canonicalised and hashed, and carries the intent, the policy that applied and a hash of the result, so the record says what was asked, under which rule, and what came out.

  • Receipts chain to the one before, so gaps and edits show
  • The underlying citizen data stays where it is; the receipt carries hashes
03 · SEALED

Sealed for the quantum era.

Each receipt carries an ML-DSA-65 signature next to Ed25519. A forger would have to break a lattice scheme and an elliptic-curve scheme at once, so the record remains checkable for decades, through the period when classical signatures alone stop being enough.

  • Hybrid engine: in development
  • Long-horizon archive signatures (hash-based): in development
04 · FEDERATED

Honoured by other agencies.

A second department verifies the record against the shared trust registry (its root and key epochs) without calling the department that issued it. If the issuer's systems are down, merged or decommissioned, the record still checks.

  • In development between our own deployments; multi-organisation federation is planned
  • Wiring the registry root and epochs into the receiving verifier is open work
03 Where it fits in the public sector

Wherever a decision will be questioned later.

These are the settings we design for. They describe where a receipt adds value, not deployments we have completed.

CASEWORK

Benefits and casework triage

When an assistant sorts or drafts a case decision, the receipt shows which policy applied and what the model produced, so an appeal starts from evidence rather than reconstruction.

APPROVALS

Procurement and grants

Approvals and denials become signed records with the rule in force at the time. Governance receipts already run in our own products; the approval pattern is being aligned with migration approvals.

INQUIRY

Evidence for inquiries

Hand an auditor or a committee a chain and a public key. They verify sequence and integrity offline, without access to departmental systems.

SHARING

Inter-agency data sharing

A record issued by one agency is relied on by another through the trust registry, without a bilateral integration or a live call between them.

REGISTERS

Licences, permits and registers

Each change to a public register becomes a signed record with the rule in force at the time, checkable by anyone holding the department's public key.

MIGRATION

Post-quantum migration evidence

When a department moves a system to post-quantum keys, a signed before-and-after record shows what changed. See migration evidence, in development.

04 Sovereignty, line by line

What each requirement means in the code.

RequirementHow R-Series addresses itState
No call homeReceipts verify with the issuer's public keys, using the public verifier and vectors (published under licence).In production (Website Maker receipts)
Signatures that lastHybrid Ed25519 + ML-DSA-65 on every v2 receipt; the receipt never depends on a single scheme.Staging · release candidate 4
Know which key was valid whenRegistry root and key epoch inside every v2 receipt; a historical verifier reports revocation separately from integrity.In development
Keys in your own custodySigning runs behind a key handle in a managed key store, tested on staging. Production keys are created only after certification.In development
Public anchoring is optionalA receipt must verify with the anchor absent; an anchor only adds an independent proof of time. Departments may choose private cosigning instead.In development
Records for decadesHash-based archive signatures, renewal receipts that carry old records forward, and an independent witness.In development
Honoured by other agenciesShared trust registry; a second agency verifies without contacting the issuer.In development
Erasure where the law requires itA destroyable per-subject key class, so personal data can be shredded while the receipt of the decision remains.Planned
05 Defence

Defence has its own page.

Naval, air, land and uncrewed forces face an adversary in the loop: interception, spoofed orders, jamming and supply-chain tampering. Signed orders, bounded autonomy, checked firmware, post-quantum links and the higher-strength defence profile are covered on the defence page.

R-Series for Defence

06 Certifications and long clocks

What we will not claim early.

Formal certifications, accredited hardware custody and standards-body acceptance run on their own clocks. They are shown as pending until an independent body has evidenced them, and nothing on this page should be read as a compliance stamp.

FEDERATION

External federation

Needs real partner organisations and at least one third-party verifier running different code. External federation waits on partners.

Planned

CUSTODY

Production keys

Production signing keys are created after the cryptography certification stage, in a managed key store, with a root ceremony.

Planned

HARDWARE

Hardware enclaves

Confidential-compute receipts use software measurement today, in simulation only. Hardware enclave quotes come later, with a stated trusted computing base.

In development

How to read the labels. In production means running for real. Staging means running on our staging systems, not in production. In development means being built. Planned means not started.
07 Working with a public body

From a briefing to a federated trial, in stages.

STAGE 1

Briefing

A closed session on the receipt format, the verifier and the honest state of every layer.

STAGE 2

Verify it yourselves

Your team checks sample receipts offline with the public verifier and vectors, on your own machines.

STAGE 3

Shadow pilot

Receipts emitted alongside one AI-assisted workflow, observe-only, with no effect on the live service.

  • Department-held keys
  • Nothing switched on without a human GO
STAGE 4

Two-agency trial

A second department verifies the first one's records through the trust registry. This is the multi-organisation step that is planned.

08 Questions

From public-sector teams.

Can it run entirely on our own infrastructure?

Receipts, verification and logs are designed to run where you choose, with keys in your own key store. Public anchoring is a separate, optional layer: a receipt must verify with the anchor absent.

Which certifications do you hold?

None are claimed yet. Formal certifications, accredited hardware custody and standards-body acceptance are shown as pending until an independent body has evidenced them.

Can records be shared with another agency?

Yes, by design: receipts verify against a shared trust registry, so a second agency can rely on them without calling the first. Federation is in development.

Is the post-quantum part real today?

The hybrid engine (Ed25519 + ML-DSA-65) is release candidate 4, running on staging; production verification runs for Website Maker receipts. Higher-strength defence parameters and hash-based firmware signing are later stages, labelled as such above.

What happens if DCS stops trading?

Your records still verify. The algorithms are published, the verifier and vectors are published under licence and run offline, and the keys are yours. Nothing in a receipt requires DCS to be reachable.

Does a receipt contain citizen data?

A receipt carries hashes of inputs and results, the policy that applied and the signing key, not the underlying case file. The data stays in your systems under your own retention rules.

Does this make an AI-assisted decision lawful or compliant?

No. A receipt is evidence of what happened. It supports your controls and your duty to explain; it does not replace legal review or declare compliance.

The record should still check when the inquiry comes.

Department-held keys, hybrid post-quantum signatures and an offline verifier: built so a public record can be checked years from now by someone who has never heard of us.

Book a briefingSee verification

In development — talk to us about a design partnership.

Want the details for your sector? Book a briefing — we share the full design and a live demo in a private session.