Riaan Kleynhans
Open the engine

AI portfolio · the system of record

Every AI system, and the single next thing that must happen to it

Not a report — a register you come back to. Each system carries its passport, its classification, the obligations that attach, the controls that hold, and one next action. The ordering matters: a suspected prohibition can never queue behind a paperwork task.

The four systems below are invented for demonstration. No figure, vendor or client here is real.

Systems registered

4

Need classification

2

High-risk

2

Blocked deployments

1

Live, with blocking work open.

Written, not built

3

Controls designed and no further.

Evidence holding

41%

SystemIndustryActorCategoryOwnerStatusEvidenceCeilingNext action

Fraud alert triage

AI-001 · v2.4

Financial servicesDeployerHigh-risk review

7 obligations attach

AI_RISK_LEADProduction

Blocked

57%€60MStart: fria

Clinical document drafting

AI-002 · v1.1

HealthcareDeployerHigh-risk review

7 obligations attach

DPOPilot14%€60MComplete the classification — 1 facts missing

Product content generation

AI-003 · v3.0

RetailDeployerTransparency

2 obligations attach

PRODUCT_OWNERProduction100%€60MMonitor

In-house foundation model

GPAI-001 · v0.9

Cross-industryProviderOutside listed categories

1 obligations attach

CTOPilot0%€60MComplete the classification — 3 facts missing

Evidence ledger

What each control actually rests on, who captured it, who verified it, and when it lapses.

Chain —

Nothing lapses within ninety days of this date.

An expiry date is never extended. Stale evidence is replaced by fresh evidence that supersedes it, captured and verified by a named seat — a model may propose a record, it may never verify one.

Held in this browser only. A client deployment writes to the tenant ledger instead — the same contract with a different driver.

Stage 1 · Discover → Stage 2 · Diagnose

Then how ready and how exposed you are, scored against what is recorded.