M7 — Design and Develop the Reclaim Protocol Functionality¶
SOW Deliverable(s): D2d (Design), D3d (Developed components), D4d (Test evidence) Requirement source: SOW Appendix 1 — FR4 (Reclaim Protocol)
⚠️ This entire milestone is new scope. It does not appear anywhere in the original v3 High-Level Requirements document (no mention of "reclaim" or "HMRC" in that document at all). It was added between the original RFP-era requirements and the current SOW.
Wireframe cross-check (20 Aug 2026): searched the entire docs/design/ tree for "reclaim" or "HMRC" — found nothing. Unlike M5 (which has 9 relevant wireframe pages not yet reflected in the task breakdown), M7 had zero design work of any kind.
Draft wireframes added (20 Aug 2026): to get concrete client feedback rather than only abstract questions, three draft screens now exist at docs/design/ui-designs/reclaim-protocol/ covering the end-to-end flow implied by M7-01's scenario — agency requests verification, candidate lands on a consent page and is handed off to HMRC/Reclaim, agency sees the verified result. These are explicitly marked as unconfirmed drafts (banner on every page) meant to surface the same open questions visually — they are not an approved design and should not be treated as scope confirmation on their own.
Tasks¶
Substantial design/scoping work already existed for this milestone in the repo — all of it has been moved here rather than rewritten.
| ID | Task | SOW Ref | Requirement Clarity | Dev Status | Task File |
|---|---|---|---|---|---|
| M7-00 | (overview) Implementation roadmap — POC vs. Reclaim Protocol | FR4 | ⚠️ See M7-01 | ❌ | M7-00-implementation-roadmap-overview.md — moved from existing doc |
| M7-01 | Reclaim Protocol scope confirmation & sign-off | FR4 | ⚠️ Blocking. Confirm this has actually been answered by Curo. | ❌ | M7-01-reclaim-protocol-scope-confirmation.md — moved from existing doc |
| M7-02 | HMRC / external-source integration — technical design | FR4 | ✅ once M7-01 is answered | ❌ | M7-02-hmrc-integration-technical-design.md + M7-02b-updated-architecture-diagram.md — both moved from existing docs |
| M7-03 | HMRC / external-source integration — build | FR4 | ✅ once M7-01 is answered | ❌ | M7-03-hmrc-integration-build.md + M7-03b-integration-open-questions.md — both moved from existing docs |
| M7-04 | Agency-initiated reclaim request flow | FR4 | ✅ | ❌ | M7-04-agency-initiated-reclaim-request-flow.md — moved from existing doc |
| M7-05 | Candidate consent flow for reclaim | FR4 | ✅ | ❌ | M7-05-candidate-consent-flow.md — moved from existing doc |
| M7-06 | Functional/Technical Design Document | D2d | ⚠️ Blocked on M7-01 | ❌ Not started | M7-06-functional-technical-design-document.md |
| M7-07 | Test Evidence | D4d | ⚠️ Blocked on M7-01 | ❌ Not started | M7-07-test-evidence.md |
Notes¶
Unlike M5, this milestone is not just "unbuilt" — it's scope that was never part of the original requirements document at all. The good news is the design/scoping legwork has already been done in detail (see the linked docs) — what's missing is client sign-off on scope and the actual build, not analysis.
Cross-reference, 25 Aug 2026: M5's disclosure-request "packages" now include a "Reclaim Employment (HMRC)" option, described in that call as low-effort for us. Whether that's the same integration this milestone scopes, or something Velocity's own wallet now handles natively, is not yet confirmed — see the update on M7-01 and M5-00's 2026-08-25 section. Don't let M5 work proceed on the assumption that this milestone's scope is now moot without that being explicitly confirmed.