Generated from processes/process/integration-validation.bpmn by gen-processes-viz.ts — do not edit here. All processes

Assured AI programme: confirm a component is ready to integrate

Process_AAI_Validation · strict · 3 step(s)

Integration readiness is proposed by the workstream lead and confirmed by the Technical Integration Lead with evidence (req:aai-design-principles#DP-05). The Validation confirmed: comment is the record; changing the field alone does not count, and no automation sets Validated (req:aai-automation#AUTO-05, #AUTO-10).

How it connects

• Called by: no call activity names this process
• Calls: none
• Presented on: no docs page section shows this diagram

Lanes — who acts

lane	role	what it does here
Workstream lead	workstream-lead	Owns the workstream’s delivery and its project (req:aai-design-principles#DP-02). Proposes epics; never creates them.
Technical Integration Lead	technical-integration-lead	Confirms validation with a comment starting Validation confirmed: and the evidence (req:aai-design-principles#DP-05, req:aai-automation#AUTO-10).

Steps

Every one of the 3 step(s) is documented.

step	lane	skill / sub-process	what it does
Set Integration readiness to Ready to integrate A_Ready	Workstream lead	—	With the evidence linked in the issue. The item then appears in V6’s “Awaiting validation” filter, the Technical Integration Lead’s queue (req:aai-views#V6).
Check the evidence A_Check	Technical Integration Lead	—	With the relevant workstream leads and subject-matter experts.
Post Validation confirmed: and set Validated A_Confirm	Technical Integration Lead	—	A comment starting Validation confirmed: with a short note or evidence link, then Integration readiness = Validated (req:aai-automation#AUTO-10).

Decisions

Every one of the 1 decision(s) is documented.

decision	what decides it	branches
Validated? GW_Valid	The Technical Integration Lead’s judgement, never inferred from closed sub-issues.	no → Not yet: back with the workstream yes → Post Validation confirmed: and set Validated