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

Assured AI programme: the pilot

Process_AAI_Pilot · strict · 7 step(s)

Prove the set-up small before building it big (req:aai-design-principles#DP-08): build the section 12 pilot set from representative Assured AI items, each marked as a pilot, run every pilot test, and stop on the first failure. No artificial dependencies, and no existing operational work moved to test the configuration.

How it connects

• Called by: Assured AI programme: build the GitHub set-up
• Calls: none
• Presented on: no docs page section shows this diagram

Lanes — who acts

lane	role	what it does here
PM & Architecture Integration	pm-architecture-integration	Owns sequencing, dates, dependencies, evidence and escalation. Does not make technical readiness judgements (req:aai-design-principles#DP-05).
WHO GitHub owner	who-github-owner	Answers the section 3 decisions and makes the organisation-level changes only an owner can make (req:aai-decisions#BD-05, #BD-08).
Build agent	build-agent	Builds what the decisions allow and stops where the requirements say to stop. Never invents users, teams, repositories, dates or field values.
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 7 step(s) is documented.

step	lane	skill / sub-process	what it does
Provide the test partner account A_Account	WHO GitHub owner	—	One account with partner-level access, removed after the build (req:aai-decisions#BD-03b).
Create the pilot set, each item marked pilot A_Set	Build agent	—	One epic; two features in two workstream repositories as its sub-issues, one blocked by the other; a D-number, a decision, a research question and a milestone; one item with Review type set; one thin-slice and one sprint-demo item; one issue linking to an external partner repository.
Run the pilot tests A_Tests	Build agent	—	PIL-01, PIL-02, PIL-03, PIL-05, PIL-06 and PIL-08 to PIL-11 (req:aai-pilot), each recorded with its result.
Run PIL-07 as the test partner A_Partner	Build agent	—	Set Integration readiness to Validated on a pilot item with no confirmation comment; AUTO-10 must add validation-exception and one comment, and nothing more when run again (req:aai-pilot#PIL-07).
Confirm validation on the pilot item A_Confirm	Technical Integration Lead	—	Post Validation confirmed: with the evidence, so AUTO-10 removes the label (req:aai-automation#AUTO-10).
Report the results on the programme issue A_Report	Build agent	—	One line per pilot test with its result and evidence.
Agree to the bulk import A_Agree	PM & Architecture Integration	—	The PM accepts the results before step 8 starts.

Decisions

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

decision	what decides it	branches
Every test passed? GW_Passed	Answered by the recorded results: does every pilot test pass?	no → Stopped: report the failure yes → Report the results on the programme issue