docs(m4): align verification contract naming and section order

This commit is contained in:
zouantchaw
2026-02-24 13:45:24 -05:00
parent 4a1d5f89e4
commit a07ee75dc9

View File

@@ -111,8 +111,8 @@ Rules:
"detectedColor": "dark" "detectedColor": "dark"
}, },
"provider": { "provider": {
"name": "vertex", "name": "vertex-attire",
"reference": "job_abc" "reference": "gemini-2.0-flash-lite-001"
}, },
"review": null, "review": null,
"createdAt": "2026-02-24T15:00:00Z", "createdAt": "2026-02-24T15:00:00Z",
@@ -207,7 +207,7 @@ Rules:
4. Log request and decision IDs for every transition. 4. Log request and decision IDs for every transition.
5. For government ID, keep provider response reference and verification timestamp. 5. For government ID, keep provider response reference and verification timestamp.
## 11) Provider configuration (environment variables) ## 9) Provider configuration (environment variables)
1. Attire model: 1. Attire model:
- `VERIFICATION_ATTIRE_PROVIDER=vertex` - `VERIFICATION_ATTIRE_PROVIDER=vertex`
- `VERIFICATION_ATTIRE_MODEL=gemini-2.0-flash-lite-001` - `VERIFICATION_ATTIRE_MODEL=gemini-2.0-flash-lite-001`
@@ -220,14 +220,14 @@ Rules:
4. Provider timeout: 4. Provider timeout:
- `VERIFICATION_PROVIDER_TIMEOUT_MS` (default `8000`) - `VERIFICATION_PROVIDER_TIMEOUT_MS` (default `8000`)
## 9) Frontend integration pattern ## 10) Frontend integration pattern
1. Upload file via existing `POST /core/upload-file`. 1. Upload file via existing `POST /core/upload-file`.
2. Create verification job with returned `fileUri`. 2. Create verification job with returned `fileUri`.
3. Poll `GET /core/verifications/{id}` until terminal state. 3. Poll `GET /core/verifications/{id}` until terminal state.
4. Show machine status and confidence. 4. Show machine status and confidence.
5. For `NEEDS_REVIEW`, show pending-review UI state. 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. 1. Wave A (fast): attire verification pipeline end-to-end.
2. Wave B: certification verification with issuer adapter + review. 2. Wave B: certification verification with issuer adapter + review.
3. Wave C: government ID provider integration + reviewer flow hardening. 3. Wave C: government ID provider integration + reviewer flow hardening.