The latency
A finite number at or above nought. A true-or-false is refused outright, though such a thing counts as a number.
Asking for finiteness turns back an infinity and a figure that is not a number. Five records elsewhere on these two sides refuse a figure by comparing it with nought instead, and where the figure is an ordinary number such a comparison turns back neither.
The flag
A true-or-false, and nothing standing in for one. A whole number of one is refused, and so is text.
That is unusual too: the record saying how one report was handled turns on a flag it never asks the type of, so text there is read for truth alone. Here the type is asked first.
Related
Source evidence
---
row: P13-01
baseline: 49aa659
created: 2026-11-08 14:17 UTC
modified: 2026-11-08 15:12 UTC
evidence:
- claim: "Recording a request refuses a latency unless it is a finite number at or above nought, with a true-or-false refused outright"
source: "`praxis/core/health_tracker.py` 61-68"
- claim: "It refuses a success flag that is not a true-or-false, a whole number of one turned back as well"
source: "`praxis/core/health_tracker.py` 70-72"
---