Browser simulation
Refund amount substitution and replay in a browser-only sandbox; no provider execution.
Strix Execution Control
A workspace for the actions your agents cannot be allowed to get wrong.
Configure one consequential action, attack its assumptions, release only an authorized execution, and preserve what happened. The workspace organizes the work; Strix remains the authority, policy, token, enforcement, and evidence system.
Reusable workflow
Generalize the proof process, not the action semantics.
A refund, a vendor payment, an outbound data transfer, and a clinical mutation do not share the same meaning. They can share a disciplined path from configuration to coverage review.
- 01Configure
Name the capability, effect-producing route, material parameters, actor, tenant, and environment.
- 02Adversarially test
Exercise substitutions, replay, expiry, route changes, and action-specific failure modes.
- 03Execute under control
Canonical Strix policy, authority, and token services decide whether the exact action may cross the boundary.
- 04Inspect evidence
Review terminal records and independently verify canonical signed evidence where enabled.
- 05Review coverage
Name every route that can still produce the consequence, including paths outside the governed boundary.
Coverage lifecycle candidate
CLR-1 proposes binding a dated route inventory to the production request path. Production route coverage and bypass resistance remain evidence-gated, not established by this specimen.
Evaluation scope
Real transactions, agent tools, data egress, and communications require their own route inventory, enforcement test, and outcome evidence.
Claim discipline
No route coverage, live provider execution, or signed-evidence claim without the corresponding evidence.