Observed
100%
Every request on the protected path is seen. Definition of the mode, not a live count.
Control
Observation before enforcement
Prove it before you enforce it.
Dry run sits on the real production request path. It observes, evaluates, and records. It does not interrupt.
01 — Dry run
See what Bruiser would have stopped.
Dry run is not a separate sandbox. The request continues as it does today. Bruiser records the decision it would have made.
Evaluated and recorded
100%
Every observed request is evaluated and written down. Nothing is enforced.
Enforced
0%
No request is interrupted. Production traffic continues as it does now.
Report fields
The dry-run report records the following. These are fields, not a live sample.
- Requests observed
- Unique customers
- Executions
- Would allow
- Would queue
- Would reject
- Customers affected
- Requests potentially absorbed
- Estimated origin-load reduction
- EAF
02 — Progressive enforcement
Evaluate it safely in your production.
Dry run sits on the live path and records the decision, without changing traffic. Enforcement starts only after that record has been read, and only on a share you choose. Observation stays complete.
- 0%
- 10%
- 25%
- 50%
- 75%
- 100%
At 10%
Observation stays complete. Enforcement is the only thing that is partial.
- 100% observed, evaluated, and recorded.
- 10% actively enforced.
- 90% continues normally.
- Hypothetical decisions recorded for the unenforced cohort.
Cohort assignment
Assignment is deterministic, from a stable merchant-controlled customer identifier. All agents, browsers, sessions, and devices of that customer inherit the same cohort. Requests are not assigned at random.
Emergency control
0% is observation only. Enforcement can return to zero without turning observation off. Emergency control does not require a new identity system, and it does not replace the waiting room or the origin.