084-an-acceptance-outlives-the-output-it-was-written-against

An acceptance outlives the output it was written against

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Spec 044's `## Verification` block has three assertions that no longer hold, and none of the three describes a defect. It compares the whole of `index check`'s stdout against one line, which spec 050 legitimately added a second line to; it takes `len()` of `index diagnostics --json` as a bare array, which spec 074 legitimately wrapped in an `items` envelope; and it pins `VERDICT_SCHEMA_VERSION` at the literal `0.2.0`, which spec 071 legitimately moved to `0.4.0`. The third is the sharpest: 044 3.6 rules that the envelope version MUST NOT move for a payload addition, and a literal pin cannot assert that, because it also fails for every move the rule permits. None of the three amending specs declared `amends_verification`, and all three predate the spec that built it. This spec declares 044's acceptance replaced and carries the corrected block, without editing 044's file.

Read the full pinned specification ↗

Relationships

Claimed units

No ownership claims exported.

Source headings

  1. 084: An acceptance outlives the output it was written against
  2. 1. Purpose
  3. 1.1 Three red assertions, no defect behind any of them
  4. 1.2 A literal pin cannot assert that a literal does not move
  5. 1.3 The crossings were silent, and nothing reruns a merged block
  6. 2. Territory
  7. 3. Behavior
  8. 3.1 What spec 044's acceptance now is
  9. 3.2 The verdict line is read as a line, and the verb's exit status is kept
  10. 3.3 The envelope comparison is a consistency check, and says so
  11. 3.4 The payload member is asserted, because the rule is about it
  12. 3.5 The acceptance
  13. 3.6 No code changes
  14. 4. Out of scope
  15. 5. Resolved decisions
  16. Verification

Frozen anchors

No frozen anchors declared.