086-an-exact-key-set-refuses-what-the-rule-allows

An exact key set refuses what the rule allows

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Spec 052's `## Verification` block asserts that `index orphans --json` has exactly the keys `orphaned` and `inFlight`, and spec 074 legitimately added a `schemaVersion` member to every governed read, so `spec-spine verify 059` has been red since 093 merged. 052 3.1 requires the two named arrays to be present and always emitted; it never required them to be the only members, and an equality over the key set asserts a closed document the rule does not state. The same block is silent about the two decisions 059 actually recorded for that verb: that `--json` emits both arrays even when empty, and that the prose form stays silent on a corpus with nothing to report. This spec declares 052's acceptance replaced and carries the corrected block, without editing 052's file. It is the second of the four follow-ons spec 084 4 named.

Read the full pinned specification ↗

Relationships

Claimed units

No ownership claims exported.

Source headings

  1. 086: An exact key set refuses what the rule allows
  2. 1. Purpose
  3. 1.1 One red assertion, no defect behind it
  4. 1.2 An equality over a key set asserts a closed document
  5. 1.3 The block is silent about the decisions 059 recorded
  6. 1.4 The crossing was silent
  7. 2. Territory
  8. 3. Behavior
  9. 3.1 What spec 052's acceptance now is
  10. 3.2 The verb's exit status is the line's status
  11. 3.3 The key set becomes presence, type, order and version
  12. 3.4 The two recorded decisions are asserted, on the fixture that shows them
  13. 3.5 The acceptance
  14. 3.6 No `amends` edge was owed to 059 by spec 074, and none is claimed here
  15. 3.7 No code changes
  16. 4. Out of scope
  17. 5. Resolved decisions
  18. Verification

Frozen anchors

No frozen anchors declared.