From a07ee75dc9f5d66fde072f348c27a8c7e275f34d Mon Sep 17 00:00:00 2001 From: zouantchaw <44246692+zouantchaw@users.noreply.github.com> Date: Tue, 24 Feb 2026 13:45:24 -0500 Subject: [PATCH] docs(m4): align verification contract naming and section order --- .../planning/m4-verification-architecture-contract.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/MILESTONES/M4/planning/m4-verification-architecture-contract.md b/docs/MILESTONES/M4/planning/m4-verification-architecture-contract.md index 59731ea3..31ea59b2 100644 --- a/docs/MILESTONES/M4/planning/m4-verification-architecture-contract.md +++ b/docs/MILESTONES/M4/planning/m4-verification-architecture-contract.md @@ -111,8 +111,8 @@ Rules: "detectedColor": "dark" }, "provider": { - "name": "vertex", - "reference": "job_abc" + "name": "vertex-attire", + "reference": "gemini-2.0-flash-lite-001" }, "review": null, "createdAt": "2026-02-24T15:00:00Z", @@ -207,7 +207,7 @@ Rules: 4. Log request and decision IDs for every transition. 5. For government ID, keep provider response reference and verification timestamp. -## 11) Provider configuration (environment variables) +## 9) Provider configuration (environment variables) 1. Attire model: - `VERIFICATION_ATTIRE_PROVIDER=vertex` - `VERIFICATION_ATTIRE_MODEL=gemini-2.0-flash-lite-001` @@ -220,14 +220,14 @@ Rules: 4. Provider timeout: - `VERIFICATION_PROVIDER_TIMEOUT_MS` (default `8000`) -## 9) Frontend integration pattern +## 10) Frontend integration pattern 1. Upload file via existing `POST /core/upload-file`. 2. Create verification job with returned `fileUri`. 3. Poll `GET /core/verifications/{id}` until terminal state. 4. Show machine status and confidence. 5. For `NEEDS_REVIEW`, show pending-review UI state. -## 10) Delivery split (recommended) +## 11) Delivery split (recommended) 1. Wave A (fast): attire verification pipeline end-to-end. 2. Wave B: certification verification with issuer adapter + review. 3. Wave C: government ID provider integration + reviewer flow hardening.