M3-04 Velocity Credential Agent Integration (Issuance)¶
Milestone: M3 — Issuing Functionality SOW Reference: FR1, INT1 Requirement Clarity: ✅ Clear Dev Status: 🟢 Prototyped in POC — verified live against Velocity staging
Overview¶
Integration to the VCL-supplied Velocity Credential Agent so the platform can actually issue EmploymentPastV1.1 credentials, rather than just modelling them locally.
Backend Tasks¶
- Confirm
CihApiService/CihApiTypes(app/backend/src/shared/services/cih/cih-api.service.ts) covers all required Credential Agent operations (issue, status check, error handling, retry) - Confirm tenant/key setup for each organisation (
admin/services/velocity-tenant.service.ts) is solid — this underlies every credential issued - Verify the co-located AWS infrastructure requirement (Appendix 6 — Credential Agent co-located with the platform) is satisfied once the AWS hosting decision (see M4-01) is made
Frontend Tasks¶
- N/A — this is a backend integration task.
Dependencies¶
- M2-02 Velocity Registrar — organisation must exist on the Network before it can issue.
- Appendix 5 assumptions A3/A4/A5 (VNF API/service availability).
Acceptance Criteria¶
- Credential is successfully issued via Velocity Credential Agent (per SOW Appendix 3, FR1 acceptance criteria; also INT1 "successful credential issuance, status retrieval, error handling, retry handling verified")
Existing Reference Material¶
docs/requirements/tasks/POC/13-verified-integration-log.md(kept in place — records actual verified Velocity staging calls from 2026-04-15)docs/requirements/tasks/POC/01-setup-configuration.md(kept in place — VNF SDK setup)
Blockers & Risks¶
None currently — this is the most verified integration in the platform.