Continuous Integration

Requirement Every pull request MUST run the jobs the jobs table selects for its changed areas.

Rationale A job skipped because its surface did not change is recorded with that reason on the pull request. The supply-chain gate that litespec/quality/ci#enforce-the-supply-chain-gate requires is one of these jobs, selected by a change to a manifest, a lockfile, or a workflow.

Requirement The docs job MUST run on every pull request and fail on a page that breaks the page contract, configuration, language, or prose rules.

Rationale Specification metadata shape, configuration, term use, and prose shape are cheapest to check on every pull request.

Requirement CI MUST regenerate committed OpenAPI and API types from source deterministically and fail on any difference.

Rationale Deterministic generation emits no unstable timestamps, machine paths, or nondeterministic ordering.

Requirement A persistence change MUST publish a schema artifact that names its reviewer and lists every destructive operation with its reason.

Rationale For Marten the artifact is the schema plan and document transformation. For EF Core it is the generated migration and reviewed SQL.

Requirement CI MUST enforce the supply-chain gate on every pull request.

Rationale An advisory names a component and a version range. Without an inventory, answering whether a running release contains it means rebuilding the dependency graph of a commit somebody has to find first. NIST SP 800-218 states the practice, and the frozen lockfile is what the inventory is generated from.

Example The build job that produces the artifact generates the inventory from the same frozen lockfile. It stores the inventory beside the artifact, under the release version.

Requirement CI MUST build one immutable artifact and promote that same artifact through staging and production.

Rationale Rebuilding from a mutable branch between environments means the tested artifact is not the deployed one.

Requirement The default branch MUST require the jobs table entries for the project's size, a reviewed pull request, and a clean merge state.

Rationale A direct push or bypassed check is permitted only during a documented repository recovery action.

Requirement A direct push or bypassed check on the default branch MUST produce a record naming the actor, the reason, and the change it admitted.

Rationale The permission exists for recovery, and a recovery nobody wrote down is indistinguishable from a habit. The record is what makes the next reviewer able to tell which commits on the branch were reviewed. NIST SP 800-218 treats the same bypass as an event that has to be attributable.

Example The record is the recovery decision itself where one exists. A bypass smaller than a decision takes a dated entry in the operations log at docs/operations/log/.

Requirement Consumer CI MUST use the job names and responsibilities the jobs table states.

Rationale The release job and the branch protection settings reference those names, so a renamed job breaks the gate.