Skip to content

M10-04 Source Code & Repository Handover

Milestone: M10 — Deployment / Go-Live and Handover SOW Reference: Deliverable D7, NFR6 — see also the numbering note below Requirement Clarity: 🟡 SOW-internal inconsistency, not something we introduced: Appendix 3's "Acceptance Criteria by Deliverable" table has a row for "D8" (repository/source code/deployment artefacts/handover materials, per NFR6 and Appendix 6), but Appendix 2's Deliverables table only defines D1 through D7 — there is no "D8" formally listed there. This task covers what Appendix 3 calls D8, filed under D7 since that's the closest formally-defined deliverable. Worth flagging to Curo rather than silently guessing which numbering is authoritative. Dev Status: ❌ Not started — no Infrastructure-as-Code exists yet regardless of hosting decision

Overview

Hand over full source code, repository access, deployment artefacts and Infrastructure-as-Code to Curo, in a fully reproducible form.

Tasks

  • Confirm Curo has administrator access to the source repository (per NFR6 — Curo owns master/release branches)
  • Confirm complete, traceable commit history for all deliverables produced under the SOW
  • Write/confirm Infrastructure-as-Code for whatever AWS services were chosen at M4-01 — currently nothing exists (no Terraform/CloudFormation in the repo)
  • Document third-party dependency inventory
  • Validate Curo can build and deploy from the repository and handover materials without undocumented supplier knowledge

Dependencies

Acceptance Criteria

  • Curo has administrator access to the agreed source code repository and all project-related repositories
  • All source code committed to the agreed repository and available to Curo
  • Repository contains complete, traceable commit history
  • Build reproducibility validated
  • Dependency management documented
  • Infrastructure as Code definitions, deployment scripts and configuration artefacts committed and capable of recreating the delivered environments
  • IP transfer confirmed
  • Handover validation: Curo has successfully accessed the repository and validated retrieval of source code and deployment artefacts (per SOW Appendix 3, "Source Code and Repository")

Existing Reference Material

  • SOW NFR6, Appendix 3 "Source Code and Repository" section, Appendix 6 "Deliverables for Handover"

Blockers & Risks

  • Risk: Infrastructure-as-Code is a hard requirement for handover acceptance but doesn't exist today — this needs to be built alongside the AWS deployment work in M3/M4/M9, not left until M10.