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

Assured AI programme: build the GitHub set-up

Process_AAI_Build · strict · 12 step(s)

Build the shared programme project, its repositories and automations in the order section 13 of the programme requirements sets, stopping wherever a decision, a credential or a pilot test is missing. Nothing past pre-flight is created until the decisions for that step are confirmed, and nothing is bulk-imported until every pilot test passes.

How it connects

• Called by: no call activity names this process
• Calls: Assured AI programme: the pilot
• 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 12 step(s) is documented.

step	lane	skill / sub-process	what it does
Step 1: pre-flight A_Preflight	Build agent	—	Inspect the organisation read-only: issue types, issue fields and headroom, project field counts, projects, teams, repository policies, SSO or EMU, and permissions. Reuse compatible configuration; create nothing that duplicates it.
Answer the open BD decisions A_Decide	WHO GitHub owner	—	BD-01a, BD-03a, BD-03b, BD-05, BD-06 and BD-08, each with its recommended default unless the owner says otherwise. The answers are recorded on the programme issue.
Step 2: create or reuse issue types and fields A_OrgSetup	WHO GitHub owner	—	Create or reuse the section 5.1 issue types and the section 7.1 issue fields, and pin them as section 5.3 says. If issue fields cannot be used, apply the section 7.4 fallback and record it.
Step 3: repositories, roles and labels A_Repos	Build agent	—	Create aai-programme and the two workstream repositories the pilot needs, public, with the BD-04 roles and the section 7.3 labels (req:aai-information#SEC-04).
Step 4: programme project and template A_Projects	Build agent	—	Create the programme project with views V1 to V13 in the listed order (req:aai-views), and the workstream template from section 8.3.
Step 5: READMEs and directory A_Readmes	Build agent	—	Write the READMEs (req:aai-acceptance#AC-10, req:aai-automation#AUTO-07) and create the pinned Workstream directory issue (req:aai-linking#LINK-01).
Step 6: automations AUTO-01 to AUTO-11 A_Automations	Build agent	—	Set up the automations (req:aai-automation). Every script reruns safely and has --dry-run. None makes a judgement (req:aai-automation#AUTO-05).
Step 7: the pilot Call_Pilot	Build agent	calls Assured AI programme: the pilot	Build and test the section 12 pilot set; see the pilot process.
Provide the section 14 inputs A_Inputs	PM & Architecture Integration	—	The epics CSV reviewed by each lead, the Gates output list, R1 to R7, the dependency register with anything section 6 keeps off GitHub removed, the directory details, and the needed GitHub usernames.
Step 8: bulk import and backfill A_Import	Build agent	—	Import the inputs, leaving missing values empty and listing them, then run the AUTO-11 backfill.
Step 9: charts and acceptance checks A_Charts	Build agent	—	Build charts M1 to M5 (req:aai-metrics), or record which cannot be built natively, and check AC-01 to AC-19 (req:aai-acceptance).
Step 10: build report A_Report	Build agent	—	Hand back the section 16 report.

Decisions

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

decision	what decides it	branches
Decisions for the next step confirmed? GW_Decided	Answered from the section 3 decision record (req:aai-decisions): is every decision that step 2 onward depends on confirmed? no sends the open ones to the owner.	no → Answer the open BD decisions yes → Step 2: create or reuse issue types and fields
Automation credentials in place? GW_Creds	Answered by whether the BD-08 credentials exist as an organisation secret. no stops and reports exactly which permission is needed (req:aai-automation#AUTO-09).	no → Stopped: credentials needed yes → Step 6: automations AUTO-01 to AUTO-11
Every pilot test passed? GW_Pilot	Answered by the pilot’s results (req:aai-pilot). no stops the build and reports the failure; there is no bulk import after a failed pilot.	no → Stopped: a pilot test failed yes → Provide the section 14 inputs