Skip to content

For reviewers

Read a report

report.html opens offline and loads nothing from the network.

  1. Verdict banner. ACCEPTED, FAILED or OUTSIDE_PLAN, with one sentence on what it means.
  2. Summary. Failed checks, warnings, the alpha this evaluation used, and the key numbers.
  3. Checks table. One row per check, with the result and what a failure does to the verdict.
  4. Figures.
    • The update timeline shows AUROC per version against the anchor and the drift budget.
    • The forest plot shows each subgroup's change with its interval at the level it was tested.
    • The calibration and decision curves compare candidate and previous version.
    • The gauges show how much of each plan budget is used.
  5. Check details. Every number behind every check.
  6. Environment and inputs. Tool and library versions, seed, and the SHA-256 of every input file.

report.json holds the same content in a published schema.

Match files to a decision

Each ledger entry and report records the SHA-256 of the plan, the three prediction files, the training manifest and the model metadata. Hash the files you were given and compare.

shasum -a 256 change-plan.yaml candidate.parquet model.yaml
medagentrx fingerprint candidate.parquet

Verify the ledger

medagentrx ledger verify ledger.jsonl --head trusted-copy/ledger.jsonl.head
medagentrx ledger verify ledger.jsonl --public-key ledger-signing.pub --plan change-plan.yaml
medagentrx ledger show ledger.jsonl

verify recomputes every hash and checks the chain against the head file. Edited, reordered or removed entries are reported, as are entries out of time order. When the plan pins a signing key, --public-key checks the head's signature, and --plan checks that the key is the one ledger_signing_key_sha256 names. A signature does not rule out a rollback to an older signed head, so compare the entry count with a head you trust. The ledger page explains the format.

Read the plan itself

medagentrx render-plan change-plan.yaml --out pccp/

This writes the plan as an FDA PCCP document with the EU cross-reference. It comes from the same file the gate runs.