Skip to content

A claim is proven by a run that happened, not by a file that exists

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.

status
feature status: stable
domain
Evidence
on the homepage
featured

What it does

majordomus evidence show renders every claim of docs/CLAIMS.yaml against the run recorded for its test: the proof state, the sentence that explains how that state was derived, the execution behind it, the files that have changed since, and the command that produces the proof again. evidence claim is one claim in full and evidence test is the reverse — one test with every claim it proves — read from the same derivation, so the two directions cannot disagree. evidence record writes what a run already reported into the ledger, stamped with the commit, the tree state, the digest of the test's own source, the time and the origin.

The seven states are ranked, and two of them are deliberately not one. proven is a passing run recorded against this very commit with a clean tree. inputs unchanged is a passing run where nothing the claim itself names has moved since — the absence of a known invalidation, which is weaker, and which is labelled as weaker everywhere it is shown.

What it does not do

It does not prove a claim at HEAD from a run made elsewhere: the dependency model is the files the claim names and nothing transitive, so inputs unchanged is honest about the change it cannot see. It does not resist forgery — the ledger is a tracked file and a hand-edited outcome is a line in a diff, not a cryptographic failure — and it keeps no history and no captured output, because the question it answers only ever reads the newest result and a log of every case belongs where the run happened.

How it works

The capability modules of the executable this feature names, each with the capabilities it composes. The interfaces each one reaches are listed under Interfaces below: they are projections of one declaration, not separate registrations.

Evidence evidence behaviorally verified

What actually ran, against which commit, and whether it still proves anything. The claims matrix binds a claim to a test by path; the ledger under .ai/repo/evidence records the latest execution of every test with the commit, the tree state, the digest of the test's own source, the time, the origin and the command that runs it again. Joining the two answers, per claim, whether the repository can honestly call it proven — and distinguishes a run recorded against this very commit from one whose inputs merely have not changed since, because collapsing those two is how a green badge stops meaning anything.

Where it sits

domain
Evidence — A claim names the test that settles it, a recorded run is judged against the commit it ran at, and a claim with no recorded run says so.
areas of work
verificationgovernance
named by
Economics

Interfaces

Each capability behind it, on every interface it is projected onto. A link goes to this site's reference for that interface; an HTTP route and an MCP tool are answered by a running majordomus serve, not by this site.

The capabilities behind this feature, by interface
capabilitycommand lineHTTPMCP tool
evidence.claim majordomus evidence claim GET /api/v1/evidence/claim majordomus_evidence_claim
evidence.record majordomus evidence record —none —none
evidence.report majordomus evidence show GET /api/v1/evidence majordomus_evidence
evidence.stamp majordomus evidence stamp —none —none
evidence.test majordomus evidence proves GET /api/v1/evidence/test majordomus_evidence_test

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.

The decisions behind it

Using it

The commands that run it

  • majordomus evidence work

    Record evidence against the active task: one obligation it declared, discharged, or one validation gate of the CI model that has reported — each as a ledger line carrying the hash of the files it was taken over.

From the executable's command line

The synopsis of each, as the executable's own help prints it.

Where this page comes from

the file
.ai/repo/features/evidence.md
the same answer
majordomus product show evidence

Searches the titles and descriptions of every page this site publishes.