CURRENT EVIDENCE BOUNDARY
Make every claim
inspectable.
The full workflow includes real Duo, independent execution, native approval and hosted probes.
Integration requirements
No inferred passes| Boundary | Current evidence | Remaining dependency |
|---|---|---|
| Order persistence | Native PostgreSQL application path | Acceptance and browser checks |
| Business round trip | Executed independently on fresh DBs | Artifact/container qualification |
| GitLab Duo | NOT CONFIGURED | Named application/control projects and authorized roles |
| Approval & deployment | NOT VERIFIED | Native approval path, exact image and hosted target |
| Hosted monitoring | NOT RUN | Authorized cloud region, budget and provider access |
| Security campaign | NOT RUN | Owned isolated sandbox and regression/adaptive probes |
Why a compatible fixture is still UNKNOWN
Passing the thirteen business checks answers a specific data question. The release identity and platform authority must also be complete. Until those boundaries are verified, no deployment action is exposed.