M1 — Detailed Planning and Team Onboarding

SOW Deliverable(s): D1 — Requirements Validation Output Acceptance basis: Review and approval (Requirements clarified, agreed and internally consistent — marked-up requirements / approval note, reviewed by Curo)

Status legend

Symbol	Requirement Clarity	Symbol	Dev Status (from POC)
✅	Clear, no open questions	🟢	Prototyped/validated in POC
🟡	Minor clarification useful	🟡	Partially prototyped
⚠️	Blocking — needs Curo/client answer before work starts	❌	Not started
🆕	New scope vs. the original v3 Requirements doc	⚪	N/A — process/release task, not a build item

Tasks

ID	Task	SOW Ref	Requirement Clarity	Dev Status	Task File
M1-01	Requirements validation & sign-off — reconcile Appendix 1 against the earlier v3 High-Level Requirements doc and produce D1	SOW §1.4, Appendix 1	⚠️ See open items below	⚪	M1-01-requirements-validation-signoff.md
M1-02	Delivery team onboarding — roles, access, environments per Appendix 4	SOW Appendix 4	✅	⚪	M1-02-delivery-team-onboarding.md
M1-03	Environment & tooling setup — AWS dev account, repo, branching model	SOW Appendix 6, NFR6	✅	🟢	M1-03-environment-tooling-setup.md
M1-04	Governance cadence setup — weekly status call, design/build review, milestone review	SOW Appendix 4	✅	⚪	M1-04-governance-cadence-setup.md
M1-05	Confirm Assumptions/Dependencies/Constraints (Appendix 5) with Curo	SOW Appendix 5	✅	⚪	M1-05-confirm-assumptions-dependencies-constraints.md

Notes

This milestone is primarily a process/paperwork milestone (D1 is a document, not code), but it is the natural point to close out the open requirement-clarity questions raised in the SOW-vs-original-requirements review, since everything downstream (M2 onward) depends on them being resolved rather than assumed.