Proprietary specification · AI agent trust

Verifiable records for connected AI workflows.

R-Series creates signed receipts for events captured through supported integrations. Verification checks the recorded evidence; it does not establish that an uncaptured action occurred or that a recorded action was authorised.

SignaturesEd25519 + ML-DSA-65
Canonical formRFC 8785
AnchorsPublic anchoring · in development
StatusStaging · release candidate 4
SCROLL
01 The problem

AI agents now book, buy, write and deploy. Almost none of it can be proven afterwards. R-Series makes the proof part of the action.

02 How a receipt is made

Five steps for each action captured through a supported integration.

Receipt pipeline01 / 05
01 · INTENT

The action is declared before it runs.

Who is acting, for whom, on what, and under which policy. On the governed execution path, nothing executes without an attributable intent, and the intent fields travel into every receipt.

02 · CANONICAL BYTES

One exact byte form, then a hash.

The receipt body is canonicalised with RFC 8785, so two implementations in two languages produce the same bytes and the same SHA-256 digest.

03 · HYBRID SIGNATURE

Two signatures. Both must hold.

Ed25519 for today, ML-DSA-65 for the quantum era; an ML-DSA-87 profile is in development. In the hybrid suite, a missing, stripped or invalid leg fails verification. No "either one will do".

04 · LINEAGE

Each receipt points to the one before.

Receipts chain by content address and roll up into Merkle trees. Change one byte anywhere and the root changes.

05 · ANCHOR

The root is designed to be anchored to a public chain.

Roots are designed to be anchored to a public chain. Public anchoring is an integration path in development for the current release.

02b The whole system

From a request to a proof anyone can check.

R-Series workflow01 / 08
STEP 1 · INTENT

A person or system asks an agent to act.

The request becomes a signed intent: who asked, for whom, what for, under which policy.

STEP 2 · POLICY

The policy decides before anything runs.

Limits, approvals and delegated authority are checked. Money and autonomy stay off until a human opens the gate.

STEP 3 · ACTION

The agent does the work.

A tool call, a model run, a file write, a payment. Through Connector OS or the MCP shim, nothing about the agent changes. Coverage depends on the integration. The evidence distinguishes recorded facts, issuer assertions and missing information. Approval and execution are checked from their own linked records.

STEP 4 · RECEIPT

The action becomes a receipt.

Eleven fields, canonicalised with RFC 8785, hashed with SHA-256.

STEP 5 · SIGNATURE

Signed twice: Ed25519 and ML-DSA-65.

Both legs are required. A stripped or invalid leg is a rejection. An Ed25519 + ML-DSA-87 profile is in development.

STEP 6 · LINEAGE

Linked to everything before it.

The receipt names its parent and joins a Merkle tree and a log.

STEP 7 · ANCHOR

The root is designed to go on a public chain.

Roots are designed to be anchored to a public chain. Public anchoring is an integration path in development for the current release.

STEP 8 · VERIFY

Anyone checks it, offline.

An auditor, a regulator or a counterparty checks the signature, the hash and the inclusion offline, without asking DCS.

03 Quantum

Evidence designed for cryptographic change.

Data recorded now can be decrypted later. Signatures made now can be forged later. New R-Series receipts are designed hybrid from day one: a classical signature and a lattice-based post-quantum signature. The Ed25519 + ML-DSA-65 receipt profile is running on staging. Customer production availability is assessed separately.

THREAT

Harvest now, decrypt later

Ciphertext captured today waits for a quantum computer. Post-quantum key establishment addresses future decryption of captured encrypted traffic.

THREAT

Forge later

Classical signatures on long-lived records become forgeable.

ANSWER

Hybrid by default

Ed25519 and ML-DSA-65, fail-closed. Staging · release candidate 4

ANSWER

Crypto agility

Versioned profiles and key history let a verifier interpret receipts under their recorded cryptographic policy. Long-term evidence preservation requires additional renewal and validation records.

03b Cryptographic capabilities

Three post-quantum families, each at its own stage.

Receipts are signed with Ed25519 + ML-DSA-65, both signatures required: the suite running on staging. Each family below has its own status; each card says how far it has gone into R-Series.

DIGITAL SIGNATURES

FIPS 204

ML-DSA

Lattice-based signatures. ML-DSA-65 is the post-quantum signature in every R-Series receipt; ML-DSA-87 is implemented and reviewed, with a defence profile in development; ML-DSA-44 is accepted for verification only.

Receipt suite · staging

FIPS 205 · BASED ON SPHINCS+

SLH-DSA

Hash-based signatures: large and slow to make, resting on hash-function assumptions. Three parameter sets implemented and tested, never per receipt. SLH-DSA checkpoints are in development. Archive signing is planned.

In development

KEY ESTABLISHMENT

FIPS 203

ML-KEM

Lattice-based key establishment for encrypted envelopes. It protects data; it never signs a receipt. ML-KEM-512, -768 and -1024 are implemented and tested.

In development

IETF DRAFT · HYBRID

X-Wing

X-Wing (ML-KEM-768 + X25519) is in evaluation and development for encrypted envelopes. Key establishment is separate from signature evidence. It is designed so an envelope stays closed unless both are broken.

In development

04 Evidence, not adjectives

Honest status, in four labels.

Every item on this site carries one of four labels: Planned In development Staging In production. Website Maker receipts are issued and checked in production on the Website Maker production backend, signed with Ed25519 and ML-DSA-65. Anchoring is separate and remains an integration path in development for the current release. The Ed25519 + ML-DSA-65 receipt profile is running on staging. Customer production availability is assessed separately. Nothing is presented as independently assured until an outside party signs it off.

Where we are. Internal AI-assisted review, a human cryptography review and a re-run by an engineer who did not write the code are separate steps. No external audit has taken place yet, and no certification is held. The fourth release-candidate tag is signed by the founder. An ML-DSA-87 defence profile is in development.

05 The stack

Fifteen layers, one receipt underneath.

05b Programmes

One engine, and the programmes built on it.

The receipt engine is the trust boundary. Everything else consumes it, and each programme is tracked against its own gates.

PQC MIGRATION

Governed migration, with evidence

Migration evidence components are being integrated with approved execution, failure handling and recovery. A customer change pilot has its own acceptance requirements.

In development

OT / IoT

Plants, grids and fleets

We are developing an R-Series reference architecture for industrial systems and device fleets. Capabilities are qualified by device class, bench tests and deployment environment.

In development

SPACE AND AUTONOMY

Trust for systems that run far from us

Decisions and records from satellites, autonomous platforms and remote infrastructure, made verifiable on the ground, later.

In development

CONNECTOR OS

Actions through supported connectors

Agents act across business systems; Connector OS produces facts for the actions it captures, and R-Series turns each one into evidence.

In development

ATLAS

Signed evidence, in order. Private by default.

Atlas, built on R-Series, is a private evidence explorer in development. Atlas holds no keys. R-Series does the cryptography. The R-Series integration is under review. Durable ingestion, investigation views and customer export are being qualified separately.

In development

SOVEREIGN DEPLOYMENT

Customer-hosted R-Series. For local AI workflows.

DCS is developing a customer-hosted deployment of R-Series for local AI workflows, with work focused on governed execution, offline evidence verification and independently tested deployment controls. A customer-hosted development package exists and is under review. Production key custody, target-environment tests and pilot acceptance remain separate milestones.

In development

CRYPTO-AGILITY

Assess. Plan. Change. Re-scan.

Crypto-Agility is a capability of R-Series, in development. An assessment and a bounded change pilot are two separate offers, each with its own gate. Assessment components are built and under review. Discovery acceptance, the reviewed report and service readiness determine when assessments can be delivered.

In development

PILOT PROGRAMME

The PQC migration pilot programme, step by step

The two offers in order, for one organisation’s own estate: what you do, what DCS does, what you receive and what evidence remains at each of the six steps.

In development

05b Two hybrid strengths

ML-DSA-65 today. ML-DSA-87 for the defence profile.

DEFAULT

Ed25519 + ML-DSA-65

The balance of size and strength for most records: enterprise, finance, government. The Ed25519 + ML-DSA-65 receipt profile is running on staging. Customer production availability is assessed separately.

Staging · release candidate 4

DEFENCE PROFILE

Ed25519 + ML-DSA-87

The highest ML-DSA security level, the one CNSA 2.0 names for national-security systems. For defence and strategic programmes. ML-DSA-87 is implemented and reviewed. A defence profile built on it is in development.

In development

Both are hybrid: a forger must break the classical and the post-quantum signature at once. Once the defence profile is available, a programme can keep one per system, run both side by side, or move from one to the other with signed migration evidence.

06 Where it matters

Built for places where "trust us" is not an answer.

07 First proof

Proven on its makers first.

The organisation that built R-Series runs on it. One human directs a fleet of AI lanes; their actions on the governed execution path are signed and logged, with money and autonomy kept off behind a human approval gate.

In development

Next

See R-Series on your own systems.

A 45-minute technical briefing: the receipt format, the hybrid suite, and what a migration looks like for your estate.

Request a briefingRead the developer guide