For AI providers — step 2 of 3

Issue the passport once.
Present it at every border.

A hospital trust, a bank’s third-party risk function, and a supervisory authority are asking for the same evidence in three different formats. A Ripple is the evidence passport your AI system carries — issued once, presented at every review.

Issued once, presented everywhereDiagnostics run inside your perimeterRipple-issued — a credential that expires

Asked at every review

Six questions that decide whether your system is cleared.

Deployers in health, financial services, and minor-facing services now carry personal obligations under the EU AI Act and GDPR that your assurance cannot discharge. They need a record they can hold up — and be held to. The passport is that record, and it is yours to issue before they ask.

"Which special-category data does the system reach — GDPR Art. 9?"

"Is our data used to train or fine-tune the model?"

"How was bias examined under AI Act Art. 10? Show the result."

"How is human oversight designed under Art. 14 — who can override, and on what basis?"

"Has accuracy held since validation, or has the population shifted — Art. 15?"

"If you swap the model behind the endpoint, how would we know?"

What the passport records

Nine sections. Each tied to the article the reviewer must satisfy.

A passport records what is proven about a system — never how it is built. Weights, prompts, corpora, and training data never leave your infrastructure.

System identity, provider, and intended purpose

Data categories — Art. 9, Art. 8, financial profiling

Model and provider stack, with swap detection

Legal basis — GDPR Art. 6, 9, 22 · DPIA under Art. 35

Data governance and bias examination — AI Act Art. 10

Human oversight design — AI Act Art. 14

Accuracy and robustness under shift — AI Act Art. 15

Event logging and traceability — AI Act Art. 12

Sealed Evidence Records, expiry, and the visas in force

How it works

Issue. Seal. Present. Carry.

Issue the passport

Complete the Ripple: purpose, data categories, legal basis, oversight design, and the model actually running behind the endpoint.

Seal the diagnostics

Bias examination, accuracy under shift, and exposure checks run inside your perimeter. Only the signed Evidence Record leaves — never the data, the corpus, or the weights.

Present it as a Wake

A stamped, sealed export travels to the reviewer — DPO, CISO, procurement, or a competent authority — already assembled, and verifiable offline.

Carry the credential

"Carries a Ripple" — Ripple-issued, verifiable, expiring. The reviewer checks the passport itself rather than trusting a logo.

The evidence request

The deployer requires a passport. You issue it.

When a procurement team refuses access to an unpassported system, you receive a direct request. Issue the Ripple against it and the review can proceed — with the evidence already sealed.

The gate holds

Procurement refuses access to a system carrying no passport.

The request arrives

You receive a direct link to issue the Ripple for that deployer.

The visa is granted

With the passport in hand, the deployer clears one context — and states its expiry.

Step 2 — the passport

Issue the passport your system carries.

One Ripple answers the health trust, the bank, and the supervisory authority from the same record — with the diagnostics sealed, the model version bound, and the expiry date on its face.

Technical evidence record. Not certification, notified-body conformity assessment, or regulatory approval.