Weekly Pilot Report Specification v1.0

One page, owner-readable, generated (r2.0 §4.2).

Report structure

1. Header: tenant · pilot day N/90 · phase · autonomy level (L0…) · flags state (both writebacks OFF).
2. Decisions this week: per Decision Job — proposed / RECOMMENDED / WITHHELD (with named reason) / human-approved / executed. WITHHOLD count is a headline, not a footnote.
3. Calibration: Brier, AUC, drift vs gate thresholds; plain sentence: "the model may/may not recommend autonomously, because…".
4. Causal evidence: active holdouts (registered date, estimand, horizon) · estimates with CIs · refutation pass/fail table · anything WITHHELD for failed refutation.
5. Net contribution: revenue → refunds/returns (actual-only until 1 cycle/SKU) → costs → contribution; excluded rows with the named missing cost.
6. Margin reconciliation: platform-reported vs governed number, delta explained.
7. Passports: links to every decision's ValidationPassport (signed once KMS lands).
8. Next week + asks: pending owner inputs, upcoming gate criteria.

Generator contract

Assembled only from ledger/passport/holdout/economics stores — no free-text claims; any field lacking data renders "no data," never an estimate; report itself carries ILLUSTRATIVE watermark until the claim ledger verifies pilot numbers.

Day-90 report = same structure, cumulative, + Gate-3 recommendation with evidence.