ras-audit

ras-audit: provenance manifest

Tool

ras_manifest_write(out_json, case?, project?, plan?, inputs?, results?, figures?, run?, edits?, tool_calls?, notes?)

• writes out_json (schema agentic-hecras/manifest/1): every listed file with {path, exists, bytes, sha256}, the QA subset of the ras_run return (status, usable, reasons, metrics, hdf, ras_version, elapsed_s), the edit records (ras_plan_set / ras_flow_set_hydrograph returns), the ordered tool calls, free notes, and the Python / platform / package versions
• returns missing_files — must be [] before claiming reproducibility

Procedure

1. Collect: the copied .prj (project), plan, the edited .u## / .p## (inputs), the .p##.hdf files (results), the PNGs (figures), the full ras_run return (run), the edit returns (edits), and the list of {tool, args, ok} calls made so far (tool_calls).
2. ras_manifest_write(out_json=runs/<case>/manifest.json, ...) as the LAST call of the case.
3. Report the manifest path and missing_files (must be empty).

Rules

• One manifest per case (baseline + variant together is fine: list both HDFs in results, the variant's run in run).
• Never write the manifest before the runs finished; the sha256 of a half-written HDF is useless.
• Keep notes to the plain-language goal + anything not derivable from files (why the edit, what was skipped).