Change over time

Every assessment run is an immutable snapshot; the estate's key numbers are charted across runs, and any two runs can be compared. Runs are expected monthly. There is one run so far, so trends begin populating from run 2: what you see below is the baseline the next run will be measured against.

Assessment runs

Run	Date	Assessed	In scope
run-2026-07-27-1 baseline	2026-07-28T13:40:08Z	213	213

Trace snapshots on record: 2026-07-24, 2026-07-26, 2026-07-27, 2026-07-28.

The baseline (run run-2026-07-27-1)

The numbers the programme moves. Each links to the repos behind it.

Systems on end-of-life runtimes	96
Systems touching WCF	98
Repos with credentials in source	36
Dormant but deployed	40
Kernel systems (bound by 2+ mechanisms)	67
Repos with no tests	47

Estate health, month by month

average score (0 to 100)green reposred repos

One point per assessment run, recorded by the health snapshot alongside each run. Score model version 1.0; the model is versioned so trend movements mean the estate changed, not the scoring.

Run-to-run comparison

Comparison unlocks with the second assessment run: repos added, removed or retired, scores moved, flags cleared, and binding points cut will appear here.

Kick off a run

The app requests and monitors; execution happens in the existing pipeline (the trace scripts and the agent-driven assessment). No dispatch endpoint is configured yet (set RUN_DISPATCH_URL server-side), so requests are recorded for the team to action.