Checks and build outputs

Current status: planned integrated checks; the first complete workflow is still in development.

Approved check profiles

Repository-defined checks have versioned commands, environment, services, timeouts, retries, resource budgets, output limits, and required status. Unit, integration, lint, type, security, build, and repository-specific checks execute through approved Run Targets. Compared candidates use the same declared profile. Execution and logs are bounded and linked to evidence.

Results and artifact provenance

A result includes exit status, duration, output digest, structured summary, coverage, reports/binaries, and known flakiness. Provenance binds Run, candidate, environment, and policy. Missing required checks block seal or proposal. A rerun creates a new receipt; it never overwrites failed history. Reviewers must be able to distinguish code failure, infrastructure failure, and unavailable evidence.

Example: “tests passed” becomes an exact receipt for the selected candidate and environment rather than an agent's unverified completion message.

See checks requirements.