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

Assured AI programme: record and escalate a dependency

Process_AAI_Dependency · strict · 5 step(s)

A dependency starts as a native “blocked by” link in the workstream (req:aai-dependencies#DEP-01). It becomes a D-number issue in aai-programme only when it is programme-significant: it crosses workstreams or partners and needs a deadline, negotiation, escalation or an assessment of consequences (req:aai-dependencies#DEP-02).

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 team	workstream-team	The people delivering a workstream’s features, stories and spikes, in its own repository.
Workstream lead	workstream-lead	Owns the workstream’s delivery and its project (req:aai-design-principles#DP-02). Proposes epics; never creates them.
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).

Steps

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

step	lane	skill / sub-process	what it does
Link the issues with “blocked by” A_Native	Workstream team	—	GitHub’s native relationship between the two issues (req:aai-dependencies#DEP-01).
Raise it with the PM A_Raise	Workstream lead	—	Name the waiting epic, what it waits on, when it is needed by and the consequence if late.
Create the D-number issue A_DNumber	PM & Architecture Integration	—	In aai-programme, its title starting with the D-number (req:aai-acceptance#AC-14), its body following the DEP-05 template, with Workstream (the waiting one), Target date (needed by), Delivery health, Risk category, Impact and assignee (req:aai-dependencies#DEP-05).
Write the Next action A_Next	PM & Architecture Integration	—	When it is At risk or Blocked: what will happen, who will do it, and by when, in the issue body. It then shows in V9 and V10 (req:aai-views#V9, #V10).
Link the two epics with “blocked by” A_EpicLink	PM & Architecture Integration	—	Only for a true blocking dependency between epics (req:aai-dependencies#DEP-03).

Decisions

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

decision	what decides it	branches
Programme-significant? GW_Significant	Answered by the lead against DEP-02: does it cross workstreams or partners, and need a deadline, negotiation, escalation or an assessment of consequences?	no → Handled in the workstream yes → Raise it with the PM
A true blocking dependency between epics? GW_Epic	Answered by the PM (req:aai-dependencies#DEP-03): is it a true blocking dependency on another epic, rather than on a review, an external decision or a shared platform item?	no → Tracked in V9 and V10 yes → Link the two epics with “blocked by”