1. Choose boundary
Payment, AI agent, data export, IAM, job queue, cloud deploy or OT command.
2. Provide receipts
3–6 read-only files: decision log, provider receipts, downstream logs, cost or settlement reports if available.
3. Run close
BOUNDA maps receipts, builds Unit Ledger + Consequence Graph and returns HELD / BREACHED / UNKNOWN.
4. Decide
Open Decision Room: STOP / RETUNE / ENFORCE / SCALE and plan Monthly Evidence Close.
| Required | Why |
|---|---|
| Rejected-flow description | Defines the stop-line and expected zero consequence. |
| Sample logs / receipts | Supports proof sufficiency and avoids fake clean claims. |
| Expected downstream systems | Maps where units may be born after NO. |
| Test/read-only environment | Keeps the pilot safe and client-friendly. |