ReviewerStep through the full bot-pipeline trace for one decision to understand exactly why an envelope was accepted or rejected.When: When an operator disputes a rejection or a reviewer needs to verify a decision.
Details
What this page is forStep through the full bot-pipeline trace for one decision to understand exactly why an envelope was accepted or rejected.
When to use itWhen an operator disputes a rejection or a reviewer needs to verify a decision.
Powered byrisk.killswitch risk.compliancegate
Decisions — Explainability
Inspect why a single decision fired — trace inputs, rules hit, and exit codes.
Current version
v2.4.1
published 2026-04-28
Pending draft
v2.5.0-draft
under review
Prior versions
8
Last rollback
Never
Version history
| Version | Published | Author | State | |
|---|---|---|---|---|
| v2.5.0-draft | — | John D. | Draft | |
| v2.4.1 | 2026-04-28 | John D. | Current | |
| v2.4.0 | 2026-04-10 | John D. | Retired | |
| v2.3.1 | 2026-03-25 | Admin | Retired | |
| v2.3.0 | 2026-03-01 | Admin | Retired | |
| v2.2.0 | 2026-02-10 | Admin | Retired |
Publish new version
Diff: v2.3.1 → v2.4.1
Showing key policy changes
- drawdown_intraday_pct: 0.05 + drawdown_intraday_pct: 0.04 - max_gross_exposure_pusd: 150000 + max_gross_exposure_pusd: 140000 # New: AI_FRONTIER cluster cap + cluster_caps: + AI_FRONTIER: + gross_pusd: 10000 + net_pusd: 5000 - stale_book_window_s: 20 + stale_book_window_s: 15