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

Need classification

High-risk

Blocked deployments

Live, with blocking work open.

Written, not built

Controls designed and no further.

Evidence holding

41%

Worldwide annual turnover (organisation)
As at
Move the date. Nothing in the ledger is edited — records simply age past their expiry, and the controls that rest on them follow.

System	Industry	Actor	Category	Owner	Status	Evidence	Ceiling	Next action
Fraud alert triage AI-001 · v2.4	Financial services	Deployer	High-risk review 7 obligations attach	AI_RISK_LEAD	Production Blocked	57%	€60M	Start: fria
Clinical document drafting AI-002 · v1.1	Healthcare	Deployer	High-risk review 7 obligations attach	DPO	Pilot	14%	€60M	Complete the classification — 1 facts missing
Product content generation AI-003 · v3.0	Retail	Deployer	Transparency 2 obligations attach	PRODUCT_OWNER	Production	100%	€60M	Monitor
In-house foundation model GPAI-001 · v0.9	Cross-industry	Provider	Outside listed categories 1 obligations attach	CTO	Pilot	0%	€60M	Complete 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.