Digest over protocol, version, id, domain, subject, input revision, solver, settings and outcome, in the same sha256: form; validation recomputes it.
Domain this run answers for.
Non-blank stable run identity; a report refuses two runs with one id.
Non-blank design revision the run read.
What the run produced, or why it produced nothing.
Versioned run protocol.
Digest of the canonical settings text the run was configured with, written sha256: followed by 64 lowercase hex digits.
Solver identity.
Non-blank open subject label, usually the logical space or boundary analysed.
Schema version.
One analysis run: what was asked, of which design revision, by which solver, and what came back.
inputRevision makes a result perishable. A run that names revision
r7is counted stale by a report forr8; the producing owner must establish which inputs were actually read. The digest binds covered canonical fields, not solver execution or scientific accuracy: changed encoded fields generally break the seal, while extra unencoded fields and signed-zero changes do not, and hash collisions remain possible.