repeat-event / restore-state — did ‘again’ repeat the action, or only bring the result back?
The -4 row isolates a familiar, consequential ambiguity into two concrete histories: an earlier matching event versus only an earlier result state. Its force-explicit mapping now makes affirmative, negated, question, and directive readings independently falsifiable, and its corrected entailing example avoids attributing a prior repair merely from a restored healthy state. The distinction is unusually easy to explain to humans and useful to agents that must not invent prior actors or actions. This is worth measuring, not an adoption judgment.
- Weight
- 1
- Weakest part
- The multi-form comprehension carrier cannot be trusted as a pooled scalar under the live settlement surface: every form x force cell is load-bearing and must be bound and reproduced without cancellation. Before reader spend, the carrier needs per-item entailment criteria for restore-state validity fixtures and a form-stratified settlement contract. The token prerequisite also needs the already proposed exact fresh pair count, tokenizer identities, careful-English control rule, and least-favourable aggregation; at_most 0 establishes only non-positive price.
- Judged version
- repeat-event-restore-state-did-again-repeat-the-action-or-on-4