Skip to content

M2-13 Functional/Technical Design Document (D2a)

Milestone: M2 — Platform and Client Admin SOW Reference: Deliverable D2a Requirement Clarity: ✅ Clear Dev Status: ❌ Not started as a standalone deliverable — design intent exists implicitly across the M2 task files (M2-00 to M2-12), but not yet consolidated into a reviewable design pack

Overview

Produce the Functional/Technical Design deliverable for M2's scope (platform and client admin), in the format Appendix 2 specifies (Word/PDF/diagram), for Curo's review and approval — distinct from the task breakdown itself.

Tasks

  • Consolidate the design intent already captured across M2-00 through M2-12 into a single design pack
  • Cover: KYB flow, Velocity Registrar integration, admin config surfaces (Ts&Cs/Privacy/branding), user management, auth/RBAC, multi-tenant/zero-trust foundations
  • Submit to Curo for review

Dependencies

  • Draws on all other M2 task files.

Acceptance Criteria

  • Design materially supports agreed requirements and integrations (per SOW Appendix 3, D2a — Design pack / review note, reviewed by Curo)

Existing Reference Material

  • All M2-00 to M2-12 task files in this folder.

Blockers & Risks

None identified — this is a consolidation/write-up task, not new technical work.