Demanded
The record of what an outcome was delivered against asks two of its fields to be a true-or-false, by a test of kind for each: whether the order was opening a position, and whether it meant to close one entirely.
Declared and never read
Four fields across the forty-two are declared as a true-or-false. Those two are the only ones any test reads.
The flag on a replanned scheme and the one on a fill saying whether the order waited are declared and weighed nowhere, so either may arrive as anything at all.
Refused
Four places turn a true-or-false away outright, each by a test standing beside the one asking for a whole number: two of the shared checks, a venue's code where it is given, and every entry in a planned ladder's run of places.
For the venue's code the true-or-false is turned away first, and the question of whether the value is a whole number comes after.
Why the refusals are written at all
A true-or-false answers to being a whole number wherever that is asked plainly, standing as the number one or nought.
What the separate test adds is narrower than that suggests. Each of the two shared checks also asks for a figure at or above one, which false already fails. Dropping the separate test would let true through and go on refusing false.
So the same thing is a required kind for two fields, a forbidden one in four places, and unweighed in two more.
Related
Source evidence
---
row: P62-03
baseline: 49aa659
created: 2026-11-08 19:13 UTC
modified: 2026-11-08 19:13 UTC
evidence:
- claim: "One record asks two of its fields to be a true-or-false, by a test of kind for each"
source: "`events.py` 1967-1969, and 1971-1973"
- claim: "Four fields across the forty-two are declared as a true-or-false, and those two are the only ones any test reads"
source: "`events.py` 1967 and 1971, with nothing reading the flag on a replan or the one on a fill anywhere in 416-435 or 572-595"
- claim: "Four places refuse a true-or-false outright, each by a test standing beside the one for a whole number"
source: "`events.py` 91-93, or 330-335, or 1326-1328, or 1425-1428"
- claim: "A venue's code is refused the same way where it is given, a true-or-false turned away before the question of its being a whole number"
source: "`events.py` 330-335"
- claim: "Those refusals stand because a true-or-false answers to being a whole number wherever that is asked plainly"
source: "`events.py` 331 testing for it separately from 332"
- claim: "Dropping the separate test from the two shared checks would let true through and go on refusing false, each asking for a figure at or above one"
source: "`events.py` 91 and 1326, the floor at 76 and the one written at 1326"
---