Dependencies

How dependencies are recorded (section 9). Generated from requirements v0.5 by scripts/gen-requirements.ts; do not edit by hand. Cite one as req:aai-dependencies#<ID>.

ID	Level	Requirement
DEP-01	SHALL	Ordinary technical dependencies use GitHub’s native “blocked by” and “blocking” relationships between the issues concerned. Workstream teams create these themselves.
DEP-02	SHALL	A dependency becomes a D-number issue in aai-programme if it is programme-significant: it crosses workstreams or partners and needs a deadline, negotiation, escalation or an assessment of consequences.
DEP-03	SHALL	Each D-number issue links to the waiting epic and to what it waits on. Where that is another epic and the relationship is a true blocking dependency, the agent also creates a native “blocked by” relationship between the two epics. Where the dependency is on a review, an external decision or a shared platform item, no native relationship is created.
DEP-04	SHALL	The agent imports the existing dependency register (D01 to D29) as D-number issues in aai-programme.
DEP-05	SHALL NOT	Do not create extra fields for waiting epic, epic waited on or needed-by date. Each D-number issue uses Workstream (the waiting workstream), Target date (the needed-by date), Delivery health, Risk category, Impact and Assignee. Its issue body follows this template: