standard
Configuration format used for group-level execution switches, individual test case definitions, tolerance values and column mapping.
No evidence-backed relationships are recorded.
YAML 1.2 killed the Norway problem in 2009. A dev.to post makes the operator's point: if half your parsers never moved, the file is read two correct and incompatible ways, silently.
Reality
An overnight agent pipeline logged the same file-not-found error 117 times in seven weeks. Tracing it found no broken code, and the run reports never mentioned it once.
Reality
A dependency rule for agent config files read only the scalar form of a YAML key. Authors who declared nothing went clean; authors who declared properly got the warning.
Reality
A NexFlow write-up splits structural, cross-reference and runtime checks. The first two only prepare a configuration for execution; the third, which the author calls future, is what stops an action.
Reality
A published blueprint moves migration checks out of bespoke Python and into config files QA can own. The interesting field is tolerance, because that is where rounding errors get buried.
Reality