The Assured AI programme’s views and metrics (section 8), built from the issues’ labels, with nothing kept by hand. The same issues show in project 110. Workstreams, epics and beans maps each workstream’s epics and proposals to their features and beans; Bean drift says where an issue and its bean disagree.
Target date before today, and Programme status not Done or Cancelled.
Metrics
M1 Epics by Delivery health
Count
On track
0
At risk
0
Blocked
1
M2 Blocked items by Workstream
Count
WS3 Evaluation
1
Cross-workstream
1
M3 At-risk or blocked dependencies
Count
At risk or Blocked
3
M4 Overdue deliverables
Count
Overdue
0
M5 Integration readiness by Pipeline stage
Pipeline stage
Not assessed
Not ready
Partly ready
Ready to integrate
Validated
KG Knowledge graph
0
0
0
1
0
L5 Health skills + MCP
0
1
0
0
0
Cross-cutting / N/A
1
0
0
0
0
Proposals awaiting the PM
Epics proposed by a workstream, for the PM & Architecture Integration to accept, amend or decline (req:aai-linking#LINK-07). They join V1 once accepted.
Items on the board: 13 (AUTO-01’s rule; a WS5 task with none of its labels stays off).
Built 2026-10-21 from the labels of 13 issue(s) in litlfred/aai-programme by scripts/programme/board.ts; as current as the last publish. Change a value by changing the issue’s label.