CI and Delivery Policy

CI is an optional expansion path after the accessibility baseline is representative. It reproduces a versioned experience in customer-controlled infrastructure and publishes checksum-bound evidence with repository metadata.

Runner sequence

1. Build and start the target in a production-like mode.
2. Restore a dedicated, least-privilege test session when authentication is required.
3. Run the selected flow and representative context policy.
4. Publish the resulting definition and evidence envelope with commit identity.
5. Let the provider adapter report advisory or approved enforcing status.

Use a dedicated test account without production data or billing access. Never commit browser storage state. Redaction and field allowlists run before upload.

Policy safety

Begin advisory. An enforcing result may block only an approved, high-confidence new mechanical failure inside the configured scope. Human-review findings, advisory output, cantTell, untested, worker or provider failure, unavailable services, and active-flow overage never become a false accessibility failure.

Provider delivery is idempotent and retry-safe. GitHub, GitLab, and Azure DevOps receive equivalent native status semantics. The linked platform execution explains the rule contract, checkpoint, context, retained evidence, durable barrier, and policy decision.

See Optional Delivery Policy and Integrations.