Acceptance criteria

What the finished build is checked against (section 15). Generated from requirements v0.5 by scripts/gen-requirements.ts; do not edit by hand. Cite one as req:aai-acceptance#<ID>.

ID Level Requirement
AC-01 SHALL The programme project and the template exist in the agreed organisation, with the agreed access for partners, Gates Foundation contacts and WHO staff
AC-02 SHALL Every view in section 8.1 exists and shows the intended items
AC-03 SHALL The section 7.1 fields are organisation issue fields, and no project field duplicates them (unless the section 7.4 fallback was used)
AC-04 SHALL Every epic from the CSV appears once in V1
AC-05 SHALL Every Gates output has exactly one milestone issue and one saved filter in V3
AC-06 SHALL All seven research questions exist, and every epic has a Primary research question, which may be None
AC-07 SHALL Every D-number from the register exists once in aai-programme and links to the waiting epic and what it waits on; native “blocked by” relationships exist only where DEP-03 calls for them
AC-08 SHALL NOT Nothing section 6 keeps off GitHub appears in any repository, issue, comment, commit or attachment
AC-09 SHALL NOT No automation sets readiness, approval, risk category, impact, a decision or risk acceptance
AC-10 SHALL The READMEs explain each field, how items enter the project, who owns what, what is kept off GitHub and why, and how the projects link
AC-11 SHALL All pilot tests PIL-01 to PIL-11 passed before the bulk import
AC-12 SHALL NOT No aai-ws5 repository or WS5 project exists. Every workstream repository created so far exists in the WHO organisation with the agreed roles, and none was created before its lead was confirmed; no issue from an external repository has been added to the programme project
AC-13 SHALL WS5 Governance and stewardship is not represented as the final sequential pipeline stage; cross-cutting items use Pipeline stage = Cross-cutting / N/A where appropriate
AC-14 SHALL Every D-number and DEC-number issue title starts with its number
AC-15 SHALL Organisation issue-field headroom and every project’s total field count are within GitHub limits, and both are recorded in the build report
AC-16 SHALL Every item with a Gates output value also carries the matching gates: label
AC-17 SHALL Every item with a Primary research question other than None also carries the matching rq: label
AC-18 SHALL Charts M1 to M5 exist, or the report records which cannot be built natively
AC-19 SHALL Every pilot item in V10 carries a “Next action” line in its issue body