A durable CI state machine
GitLab jobs reflect Code Voucher state; they do not host long-running agents. Every attempt can survive web deploys, worker restarts, and duplicate events.
Identity and repository access are separate
Your GitLab sign-in establishes your Code Voucher identity and organization membership. The organization's dedicated GitLab service account controls which repositories Code Voucher can read and which user publishes statuses and merge request comments. A teammate's personal GitLab permissions never silently expand the organization connection.
Run lifecycle
Durable state separates short web requests, untrusted execution, and trusted publication. A deploy or duplicate event can resume the same run instead of starting an untracked second workflow.
1 · Ingress
Webhook creates a run
A signed provider event is normalized, persisted, and queued.
2 · Analysis
Review challenges the diff
Trusted validation decides which model observations affect the verdict.
3 · Execution
QA follows approval
Route smoke and deterministic scenarios run in bounded browser contexts.
4 · Publication
Publisher reports
Private evidence stays in the dashboard; providers receive classified summaries.
Follow the review as it runs
Reviews with recorded phase evidence show Exploration, Adversarial review, and Code quality above the findings. The current phase updates automatically, with elapsed time and retry information. On small screens, expand Show phase details to see the whole sequence.
Exploration may be unavailable while the remaining review continues with limited context. A completed phase means execution finished; its findings can still request changes. Completed reviews collapse into a summary so the findings stay prominent. Older reviews without phase evidence keep their existing review summary.
Native CI, private detail
The pipeline remains the merge gate engineers already use. The dashboard is the evidence system for findings, screenshots, rejected observations, retries, failure reasons, and the preserved scope, verification, depth, and residual risk from each independent review pass. Clean approvals retain the full review report instead of collapsing to a verdict alone.
