CI planned from one model, the site deployed from its verified run

Why it exists

Operational moments from the Why catalogue that name one of this feature's mechanisms. Nothing here was assigned: a moment appears because it names a rule, a command, a capability or a claim this feature also names.

• →opened CLAUDE.md and AGENTS.md and found two different rulebooks for one repository
• →found a task "in progress" that nobody had touched for three weeks
• →asked what the workers did last night and had only transcripts to grep
• →found the rule for that directory in a README no session ever loaded
• →read three roadmaps for one project and believed none of them
• →watched the always-loaded instruction file grow past a thousand lines

How it works

The objects it is made of

Kinds of the layer. Each is a schema, a source class and a file on disk; the number beside it is what this repository holds today, counted at build time.

• derive-offload1

Where it sits

domain

Completion — Done is a contract the repository evaluates line by line. Work is not accepted while any line fails, and a refusal stays on the record.

areas of work

verification

names

DoctrineBenchmarks

named by

CoverageEvidenceBenchmarks

Evidence

What is guaranteed

Each claim this feature names, with the status its row declares, the verdict the recorded runs support, and the test that settles it.

• ○declared status: guaranteed ○recorded evidence: not run A change runs the gates its paths can affect, decided by one model of what affects what, and a change to the pipeline itself or a path the model does not know runs every gate test/cases/94_ci_plan.sh
• ○declared status: guaranteed ○recorded evidence: not run The verdict status is green only when planning succeeded and every gate the plan selected ran in a job that succeeded; a failed or cancelled job, a selected gate whose job was skipped, or a plan that selected nothing is red test/cases/94_ci_plan.sh
• ○declared status: guaranteed ○recorded evidence: not run The behavioural suite runs a bounded number of cases at a time with the serial runner's semantics, a case that writes into the checkout declares itself exclusive and runs alone, and the parallel phase fails naming the paths when the checkout changed under it test/cases/94_ci_plan.sh
• ○declared status: guaranteed ○recorded evidence: not run Publication is gated on everything that can make the published site wrong and waits for nothing else; the checks that decide whether a change may merge run beside it on the same commit, not in front of it test/cases/97_pages_fast_path.sh
• ○declared status: guaranteed ○recorded evidence: not run The site is deployed by one script, scripts/site-deploy, from a terminal or from the publication workflow; it refuses a dirty tree, a commit master does not contain and a build that is not HEAD's, pushes site/public to gh-pages with the source commit named, and pushes nothing when the output is unchanged test/cases/96_site_deploy.sh
• ○declared status: guaranteed ○recorded evidence: not run Every gate the Rust executable must pass is one script, scripts/rust-check, and CI runs that script on every change that can reach the crate test/cases/77_rust_evidence.sh

Executable use cases

• policyGate CI on the tool itself, with an exit code that is a contract

The rules that hold it

• ✕blocking Blocking checks are deterministic and cheapproject.blocking-checks-cheap
• ✕blocking Tests run in disposable repositoriesproject.tests-run-in-disposable-repos
• ✕blocking The Rust executable carries its evidence with itproject.rust-cli-evidence
• ✕blocking A command asserts in the file that declares it that it is what it claims, and is composed rather than registeredproject.rust-command-tested-in-file

The decisions behind it

• adr-0006CI planned from one model of what affects what, gates as repository-owned scripts, and the site deployed from the run that verified it accepted

Using it

The commands that run it

• majordomus doctor inspect · read-only

  It checks governance only: is Majordomus itself healthy, and is every enforcement it declares actually wired here?

• majordomus watch inspect · read-only

  What has drifted since the last update — policy, projections, state, retention.

Where this page comes from

the file

.ai/repo/features/ci.md

the same answer

majordomus product show ci

read further

Continuous integration

GitHub Pages performance

Related features

• named by this feature · shares 1 use case

  Doctrine

  ✓feature status: stable

  A rule is enforced when a validator decides it, a command runs it, a test proves it and CI blocks on it; anything less is documentation, and the tool knows the difference.

  Explore Doctrine →

• names this feature · same domain

  Coverage

  ✓feature status: stable

  One coverage measurement, test code out of the denominator, holds a crate floor, a floor over the session/continuity domain, and — the invariant of #214 — every executable line a change touches.

  Explore Coverage →

• same domain

  Finish contract

  ✓feature status: stable

  A worker does not get to define its own successful completion: every line of the finish contract is printed pass or fail, the task is not accepted until all of them pass, and every time it was claimed done and was not is on the record.

  Explore Finish contract →

• names this feature

  Evidence

  ✓feature status: stable

  Every claim is joined to the execution recorded for its test — the outcome, the commit, the tree, the digest and the command that produces it again — and a run against this commit is never reported as the same thing as a run whose inputs merely have not changed.

  Explore Evidence →

• named by this feature · names this feature · shares 1 claim

  Benchmarks

  ✓feature status: stable

  Every externally callable operation is timed directly, over MCP and over HTTP, the denominator is generated from the registry, and a regression against the accepted baseline fails the check.

  Explore Benchmarks →