Exported because a run that arrived as JSON has to be checkable by the same
rule that produced it, and because a second implementation of the canonical
form would be a second answer to what a run says.
The digest is a sha256: lowercase hex string over a canonical text with one
JSON array per line: the header (protocol, version, id, domain, subject,
input revision, the three solver fields, settings digest and outcome status),
then one line per metric, sample and warning in their stored order, or one
line holding a refused outcome's reason and remedy. JSON escapes every
newline and separator inside a string, so two runs that differ in any covered
encoded JSON value produce different text. JSON normalizes signed zero and writes nonfinite numbers as null; hash collisions are possible. Reordering distinct metrics, samples or warnings changes the
digest.
The digest that seals one run's contents.
Exported because a run that arrived as JSON has to be checkable by the same rule that produced it, and because a second implementation of the canonical form would be a second answer to what a run says.
The digest is a
sha256:lowercase hex string over a canonical text with one JSON array per line: the header (protocol, version, id, domain, subject, input revision, the three solver fields, settings digest and outcome status), then one line per metric, sample and warning in their stored order, or one line holding a refused outcome's reason and remedy. JSON escapes every newline and separator inside a string, so two runs that differ in any covered encoded JSON value produce different text. JSON normalizes signed zero and writes nonfinite numbers as null; hash collisions are possible. Reordering distinct metrics, samples or warnings changes the digest.