Asked by exclusion
The test compares the field with that one name and refuses a match. Every other way of working passes, and nothing anywhere in the record lists which ones are meant.
What that lets through
Because the field is weighed by comparison with one name rather than by being asked what it is, a value that is no way of working at all passes. A word, a number, or nothing at all goes through, none of them being the name refused.
The other way round
The same question elsewhere is asked by inclusion: a field is matched against a frozen set of the named values, or against a kind. Those tests name what is allowed, so anything outside it is refused.
Here one value is named and the rest allowed. A way of working added later would be accepted by this record without anything being changed, and so would a mistake.
Related
Source evidence
---
row: P62-04
baseline: 49aa659
created: 2026-11-08 19:13 UTC
modified: 2026-11-08 19:13 UTC
evidence:
- claim: "A scheme beginning refuses one named way of working by identity against that one name"
source: "`events.py` 771-773"
- claim: "Every other way of working passes, nothing listing which are meant"
source: "`events.py` 771, which names the one refused and no other"
- claim: "The field is not asked to be one of the named ways at all, so something that is no way of working passes this test"
source: "`events.py` 771, comparing by identity rather than asking a kind"
- claim: "Elsewhere the question is asked by inclusion, against a frozen set of values or against a kind"
source: "`events.py` 1639-1642, or 1674-1677, or 1963-1965"
---