Name coverage, provenance and totality apart #50

Parent

#35

What to build

"Total" names four claims today: 0005 (every hand-tuned live value is reachable from layer 1), chapters 00 and 16 (no Deliverable has in-degree zero), chapter 30 (a derivation with no output is not total) and 0068 (a value that cannot be derived is a defect in the input). In transformation vocabulary a total function is only the last. Three names replace the one:

• Coverage (0005): the live estate lies inside what resolution can produce. Settled by render-and-diff against the cluster.
• Provenance (chapter 16's first property) and no dead declarations (its third): checked over the trace.
• Totality: every conformant model resolves to a Resolved Deployment or to coded diagnostics, and nothing throws.

0005 is retitled. Its decision and its normative anchor stand; the register row, chapters 00, 16 and 30 and 0068 use the new names.

Acceptance criteria

• "Total" and "totality" appear only for the third property.
• 0005 passes lint:adrs, and its register row matches its title.

Blocked by

• Rewrite the em-dashes in the specification #26
• Rewrite the em-dashes in the decision records, registers, root documents and tooling #27