# DoNotAct Monthly Incident Report - Example 2026-06

Schema: `donotact_monthly_incident_report_v0`
Account: `example-design-partner`
Generated at: `2026-06-30T23:59:00Z`

## Scope

This is a static example showing report shape only. It is not generated from a real customer ledger.

It is operational accounting only: no trading execution, no custody, no order signing, no probability estimate, no performance claim, and no advice.

## Summary

| metric | value |
|---|---:|
| diagnostic calls | 128 |
| unique venue/market pairs | 37 |
| READY | 73 |
| DO_NOT_ACT | 31 |
| INSUFFICIENT_EVIDENCE | 24 |
| fail-closed responses | 55 |
| p95 latency ms | 418 |

## Verdict Mix

| item | count |
|---|---:|
| `READY` | 73 |
| `DO_NOT_ACT` | 31 |
| `INSUFFICIENT_EVIDENCE` | 24 |

## Venue Mix

| item | count |
|---|---:|
| `polymarket` | 86 |
| `kalshi` | 42 |

## Source Attribution

| item | count |
|---|---:|
| `mcp-closeedge/0.1.0` | 64 |
| `sdk-python/0.1.0` | 41 |
| `custom-agent/0.1.0` | 23 |

## Reason Codes

| item | count |
|---|---:|
| `R6_BOOK_STALENESS_LIQUIDITY` | 18 |
| `R8_RESOLUTION_AMBIGUITY` | 16 |
| `R3_TICK_PRECISION` | 9 |
| `R4_METADATA_READINESS` | 7 |

## Interpretation Boundaries

- A `DO_NOT_ACT` response means a blocking diagnostic issue was found in reviewed public evidence.
- An `INSUFFICIENT_EVIDENCE` response means DoNotAct failed closed because required public evidence was missing or stale.
- Counts in this report are not monetary savings, not outcome predictions, and not a measure of trading performance.
- This report should be paired with receipt verification when cryptographic attestation is required.