M5-08 Verification Platform Integration (VerifyMyCreds / Velocity Verification Platform)¶

Milestone: M5 — Disclosure and Verification SOW Reference: FR3, INT4 Requirement Clarity: 🟡 Confirm exactly what code/access NeuralRays receives from VCL to reuse — the SOW assumes "the Supplier can assume some of this code will be reused" from VerifyMyCreds, but doesn't specify the mechanism (shared library? forked repo? API-only?) Dev Status: ❌ Not started — no integration code exists anywhere in the codebase today

Overview¶

Run verification on some or all disclosed credentials via an existing Velocity-enabled universal verification platform (VerifyMyCreds), reusing as much of VCL's existing code/functionality as licensing and technical compatibility allow.

Backend Tasks¶

Get clarity from VCL/Curo on the exact reuse mechanism and what's provided vs. what needs building from scratch
Build a VerificationService (the verification module currently has zero controllers/providers — this is the first real code in it)
Implement calls to trigger verification and receive outcomes

Frontend Tasks¶

Build a "Run Verification" action from the candidate's disclosed-credentials view
Display verification outcome (feeds M5-09)

Dependencies¶

M5-07 wallet disclosure integration — verification runs against already-disclosed credentials.
Appendix 5, A10 — "Supplier may reuse existing Velocity/VCL components where permitted by licence and technical compatibility."

Acceptance Criteria¶

User can initiate verification
Verification platform integration succeeds
Verification outcome displayed (per SOW Appendix 3, FR3 acceptance criteria)

Existing Reference Material¶

Blockers & Risks¶

Needs decision: the reuse-code access question directly affects effort here — treat as a scoping question to raise alongside the M5-02/M5-11 open items.