Assay Reports¶

Assay reports are operator-facing renderings of proof artifacts. They do not decide whether a finding is true; they summarize an existing Assay finding and optional Seam, meshmapper, and robustness artifacts.

Render A Finding¶

cd agentic-redteam/assay
python3 -m assay.cli report render \
  --finding finding.json \
  --out report/

This writes:

report.md
report.html
manifest.json

The report includes the finding verdict, oracle evidence, route and framing statistics, confidence intervals, transcript references, and the evidence boundary. Agent self-report is still not evidence.

Add Supporting Artifacts¶

python3 -m assay.cli report render \
  --finding finding.json \
  --transcript seam-transcript.json \
  --graph graph.json \
  --paths paths.json \
  --robustness-bundle bundles/refund_m6 \
  --out report/

Supporting artifacts are summarized without copying them by default. The rendered report shows transcript record counts and hashes, graph node/edge counts, path-hypothesis classes, graph refs, and robustness survival axes.

Raw transcript payloads such as raw_b64 are intentionally omitted from rendered output. Reviewers should inspect the transcript directly when raw payload review is required.

Bundle Inputs¶

Use --bundle-artifacts when you want the report directory to carry copies of the input files:

python3 -m assay.cli report render \
  --finding finding.json \
  --transcript seam-transcript.json \
  --graph graph.json \
  --paths paths.json \
  --out report/ \
  --bundle-artifacts

The manifest.json records source paths, copied paths, byte counts, and SHA-256 checksums.

Formats¶

--format both is the default. Use --format markdown or --format html when a workflow needs exactly one output.

python3 -m assay.cli report render \
  --finding finding.json \
  --out report-md \
  --format markdown