Documents and system access.

The Architecture & Assurance Dossier describes the control plane and data plane in full, the enforcement points and how each is verified, the egress matrix by edition, the authority model, resilience and recovery. Certification reports and access to a working system are released alongside it.

◆Sent under NDA◆No call required first◆Questions answered by engineering

Contents

What is in it.

Reference architecture

Control plane and data plane in full, component by component, with what each holds and what it never holds.

Enforcement points

Each target-architecture enforcement point, the mechanism that implements it, and the engineering confirmation that demonstrates it.

Egress matrix

What crosses each boundary, in which direction, under whose authority, for every edition from Foundation to Sovereign.

Authority model

What the control plane may instruct, what it may not, and what the data plane refuses regardless of instruction.

Identity, keys and custody

Where custody sits per edition, key-management options, and the separation-of-duties model.

Resilience & recovery

Loss and corruption treated as distinct failure modes, recovery objectives, and the re-derivation path.

Build, release & supply chain

Signing, software inventory, provenance attestation and the customer approval gate.

Deployment-time decisions

The seven choices, who owns each, when it is made, and what it determines.

Request access

Documents and system access are released under mutual NDA. We send the NDA first — there is nothing to sign before you see what you are signing about. No nurture sequence, and no one calls unless you ask.

NameRequired

Work emailA valid work email

OrganisationRequired

Role Required

What you need Required

Sector

Organisation size

Preferred contact

Anything specific your review needs

I request the Architecture & Assurance Dossier under mutual NDA, and confirm I am authorised to receive it on behalf of my organisation.

Leave this empty

We use these details to send the NDA, release the documents and keep a record that you requested them. Our lawful basis is legitimate interests — answering a business enquiry and being able to evidence a document release. The tick box above is a request under NDA, not consent to marketing, and nothing is added to a mailing list. You can ask us to delete your data; we will, except for the record of the NDA and release itself, which we keep and will identify to you. Your details post to our own endpoint and reach us through a transactional email processor. Privacy notice.

✉

A draft has opened — it is not sent yet

Your details are in a pre-filled email to [email protected]. Press send in your mail client and it reaches us.

If nothing opened, your browser may be blocking mail links. Copy the address above and send us the same details directly.

Open the draft again

✓

Request received

The mutual NDA follows within one business day. The documents are released as soon as it is countersigned, and system access is scheduled alongside it if you asked for it.

No mailing list · no nurture sequence

Also available

Other routes in.

A demo, or a technical briefingAs light or as deep as you like — with engineering, against your architecture. No deck unless you want one.→ Trust CenterCertifications, the public documentation, what is released under NDA, and the three levels of system access.→ What raw egress 0 B meansThe claim defined precisely, per edition, with the invariants separated from the deployment choice.→ A scoped deploymentOne urgent use case, a handful of critical sources, running inside your boundary.→