Skip to content

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.

The failure it answers

Done is cheap. A worker can report success before the repository's own checks hold.

When a piece of work counts as finished, and who decides: the finish contract a task is evaluated against, the coverage a change is held to, and the gates CI runs before anything is published. A worker can always say it is finished; here that sentence is a claim the repository checks, and nothing is recorded as done while any line of the contract fails.

Not in this domain: the proof behind a public claim, which is evidence; and the scope a task was allowed, which is coordination.

The features filed under it

Each feature names this domain in its own file; the domain lists none of them. A feature added with this domain is on this page at the next build, and one removed is gone.

  • Coverage

    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.

    1 of 1 claims guaranteed with a named test

  • Finish contract

    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.

    9 of 9 claims guaranteed with a named test · 7 use cases

  • CI

    A change runs the gates its paths can affect, every gate is the same script a person runs, and the public site is published only from a commit whose derived data proved current.

    6 of 6 claims guaranteed with a named test · 1 use case

The failure modes its features answer

Operational moments from the Why catalogue that name a rule, a command, a capability or a claim of a feature in this domain. Nothing here was assigned.

Every failure mode it answers (31)

What is claimed

Every claim a feature of this domain names, once, with the status it declares — guaranteed, advisory, planned or rejected — and the test that settles it. Whether a recorded run supports a claim is its own page's verdict.

16 claims, 16 guaranteed with a named test

Executable use cases

Scenarios the tool runs against itself every time this site is built.

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