M1-05 Confirm Assumptions, Dependencies and Constraints

Milestone: M1 — Detailed Planning and Team Onboarding SOW Reference: SOW Appendix 5 Requirement Clarity: ✅ Clear Dev Status: ⚪ Not a build item

Overview

Walk through Appendix 5's Assumptions (A1-A12), Dependencies (DEP1-DEP13) and Constraints (C1-C17) with Curo to confirm they still hold, since the whole Milestone/Charges schedule is built on them.

Tasks

• Confirm VNF/VCL access, documentation and technical clarifications will be available on request (A3, A4, DEP2-DEP4, DEP13)
• Confirm branding assets, email content, T&Cs/Privacy Policy text will be supplied by Curo (A7, DEP8)
• Confirm Curo will provide business representatives for UAT (A8, DEP10)
• Confirm independent penetration testing arrangement (DEP9) — timing matters for M9-11
• Confirm AWS hosting environment provisioning responsibilities (DEP5) — directly feeds the open AWS decision blocking M3-13/M4-01

Dependencies

• M1-01 requirements sign-off — closely related; can be done in the same sessions.

Acceptance Criteria

No standalone Appendix 3 criterion — this reduces risk across every later milestone rather than being tested itself.

Existing Reference Material

• SOW Appendix 5 (Assumptions, Dependencies and Constraints)

Blockers & Risks

None on its own — but skipping this task is exactly how the open items in ../CONSOLIDATED-SUMMARY.md end up surfacing mid-build instead of now.