Evidence & Reports

A convergence claim, QoI value, validation verdict, figure, or report statement points to a run, command record, parser result, artifact, file hash, citation, or review record. The report surface is a projection over evidence, not a place to invent results.

Solver parsers produce typed residual and monitor records. The UI renders status badges, convergence plots, iteration counters, and failure cards from those records while keeping raw logs available for audit.

QoIs are declared before extraction. Each carries units, extraction method, spatial or temporal scope, uncertainty or tolerance, and the evidence path used to compute it. A QoI without a path can't go into the report.

Knowledge citations record source path, heading path, excerpt, score, authority, and retrieval time. A solver-recommendation citation that says "k-ω SST is appropriate for adverse pressure gradient" points at a chunk of the OpenFOAM/SU2 knowledge pack — not at the LLM's training memory.

Report generation uses case state, validation records, figures, standards-pack requirements, citations, and artifact hashes. Publishing freezes a content-addressed bundle so another engineer can replay, regenerate, or challenge the result.