The build that is thrown away
As it is made, it builds a protective-settings record out of five of its own fields. The built thing is bound to no name, so nothing is kept of it.
What the build is for
The settings record checks itself as it is made. Each leg must carry exactly one of an outright price and a distance, and each of the five figures that is given must be a positive finite figure, with any left out passed over.
Building one and discarding it is how those checks come to be run on the event's fields.
Why it reads oddly
The event holds no test that weighs one of its fields against another, yet two of its fields are weighed against each other. A reader looking for the rule in the event finds a build with no result and no name.
The flat fields are what travels: the settings record exists for the length of the check and the event keeps the fields it was built from.
Related
- The records that weigh their own fields against each other
- The settings each way of working takes
- Protection
Source evidence
---
row: P61-06
baseline: 49aa659
created: 2026-11-08 19:05 UTC
modified: 2026-11-08 19:05 UTC
evidence:
- claim: "The record of a bracket beginning builds a protective-settings record out of five of its own fields"
source: "`events.py` 883-889"
- claim: "Nothing is kept of what it built, the built thing being bound to no name"
source: "`events.py` 883, the statement holding the call and nothing else"
- claim: "What the build is for is the settings record's own checks, which require each leg to carry exactly one of an outright price and a distance"
source: "`bracket_params.py` 51-57"
- claim: "Those checks also hold each of the five figures that is given to being a positive finite figure, passing over any left out"
source: "`bracket_params.py` 59-71, the absent ones passed over at 67"
- claim: "So two of the event's fields are weighed against each other without the event containing a test that does it"
source: "`events.py` 883-889 into `bracket_params.py` 51-53, and 55-57"
---