Skip to content

I1945 — The test-evidence decision and its plan are recorded

Record the test-evidence design as ADR 0087 with status proposed, create the milestone test-evidence, and give every slice of the design one issue, so that `majordomus plan` tracks the work and each slice is held to one written definition.

DONE wave 0 · p1 · implementation profile · parallel safe

Part of test-evidence — Every verifiable claim and widget resolves to revision-bound test evidence, on every surface.

Objective

Record the test-evidence design as ADR 0087 with status proposed, create the milestone test-evidence, and give every slice of the design one issue, so that `majordomus plan` tracks the work and each slice is held to one written definition.

Why

The design reconciles two proposed decisions that disagree about where CI evidence goes (ADR 0068 and ADR 0080) and defines what every surface reads. Without a record, each slice would carry its own reading of it, and the reconciliation would live only in a gitignored plan.

Current state

The design exists only under tmp/plans, which is gitignored. No ADR, milestone or issue names the work.

Desired state

ADR 0087 is proposed on master, the milestone test-evidence exists, and I1945 to I1965 describe the slices with their dependencies, so that `majordomus plan waves` orders them.

Scope

  • .ai/repo/adrs/0087-evidence-is-indexed-by-subject-and-judged-at-the-presented-revision.md
  • .ai/repo/project/milestones/test-evidence.yaml
  • .ai/repo/project/issues
  • site/content/adrs/adr-0087.md

Out of scope

  • Any code, script or case
  • docs/CLAIMS.yaml and docs/EVIDENCE.md
  • Accepting any ADR, which is the owner's act
  • A version bump

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

  • ADR 0087 has status proposed, cites ADR 0068, 0080 and 0071 by number and title only, and passes majordomus adr check
  • Its Decision amends ADR 0068 sentence by sentence, quoting each sentence it changes and listing every sentence that stands
  • The milestone and every issue pass majordomus plan validate with no failure
  • No prose states a number a command can compute; where one matters, the command is named

Validation

  • bin/majordomus adr check
  • bin/majordomus plan validate
  • bash test/run.sh 28_no_hardcoded_values
  • bash test/run.sh 104_strict_derivation
  • scripts/ci/english-only-check
  • scripts/ci/diagram-check
  • scripts/derive-check

Evidence required

  • adr_proposed
  • plan_valid

Evidence

coverstypecommandresultat commit
adr_proposedmanualbin/majordomus adr check; grep -m1 '^status' .ai/repo/adrs/0087-*.mdexit 0 at b4a781c668: 80 decisions examined, every reference resolves; ADR 0087 is status: proposed (bea35d4489)b4a781c
plan_validtestbin/majordomus plan validateexit 0 at b4a781c668: 24 milestone(s), 257 issue(s), 0 failure(s)b4a781c

Risk

The ADR names proposed pull requests (#577, #578, #597, #600, #629) whose content may still change. It cites them by number and quotes only what it amends, so a later change to one of them shows as a quotation that no longer matches.

Timeline

started
2026-09-26
verified
2026-10-07T13:27:32Z
completed
2026-10-07T13:27:35Z

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1945.yaml. Read it back with majordomus plan show I1945.

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