# Weekly review

1. Run `/ultra-config report YYYY-Www` and confirm the dialog. Use `events.jsonl` as the chronological source, `manifest.json` for joins, and the focused JSONL views for tasks, agents, model calls, tools, handoffs, and verification.
2. Inspect `privacy-report.json`. Use `/ultra-config export preview YYYY-Www` first when you want to review every line before writing the same bundle.
3. Compare cohorts only within matching profile, provider, model, and config-version cohorts.
   Review Routing Regret candidates using [ROUTING_REGRET.md](./ROUTING_REGRET.md); `null` means insufficient coverage, not zero candidates.
4. Propose at most three versioned config changes. Roll back by changing the champion pointer to an existing immutable config version.
5. Put challengers behind the HMAC 90/10 assignment and stop them on any safety incident, success-rate drop, rework increase, cost increase, sample corruption, or provider drift.
6. Accept a reviewed JSON recommendation with `/ultra-config recommendation accept <json-file> [id]`.
7. Reject it without changing config with `/ultra-config recommendation reject <json-file> [id]`.

The current local benchmark harness validates behavior and policy regression. It does not prove a production two-client/provider outcome.