087-the-answer-is-a-member-not-the-document

The answer is a member, not the document

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Spec 053's `## Verification` block compares the whole of `registry plan --next --json` against one spec object, and spec 074 moved that object under a `next` member so the empty ready set could be a value rather than a missing document, so `spec-spine verify 060` has been red since 093 merged. 093 declared an `amends` edge to 060 for exactly this change and carried the replacement text for 053's rule; what it could not reach was 053's acceptance, because spec 037 forbids editing the amended file and the block lives inside it. The same block leaves 053 3.2's strongest requirement unasserted: that `--next` is a projection of `plan` and does not reimplement selection, which a one-element fixture cannot show. This spec declares 053's acceptance replaced and carries the corrected block, without editing 053's file. It is the third of the four follow-ons spec 084 4 named.

Read the full pinned specification ↗

Relationships

Claimed units

No ownership claims exported.

Source headings

  1. 087: The answer is a member, not the document
  2. 1. Purpose
  3. 1.1 One red assertion, and this one has an amendment behind it
  4. 1.2 This is not an over-strict assertion; it is an amended rule
  5. 1.3 The block never asserted 053's strongest requirement
  6. 1.4 The crossing was silent
  7. 2. Territory
  8. 3. Behavior
  9. 3.1 What spec 053's acceptance now is
  10. 3.2 The verb's exit status is the line's status
  11. 3.3 The pick is read from the member 093 put it in
  12. 3.4 The fixture gains a second ready spec, so "first" can fail
  13. 3.5 The acceptance
  14. 3.6 The empty ready set stays where spec 074 put it
  15. 3.7 No code changes
  16. 4. Out of scope
  17. 5. Resolved decisions
  18. Verification

Frozen anchors

No frozen anchors declared.