ONE ACTION UNDER CONTROL / 01

Approval has a boundary.
Try crossing it.

An agent wants to refund $4,200. Authorize it, change the request, then try using the approval twice.

~3 MIN

Runs entirely in your browser.
Sample data. No payment is initiated.

REFUND WORKSPACEBrowser simulation

01 / REQUESTED ACTION

Issue a refund

Agent: refund_agent
Payment: demo_payment_1042
Currency: USD

Refund amount (USD)

The walkthrough starts with a $4,200 refund.

02 / AUTHORIZATION

READY TO REQUEST

An action is waiting.

Start by attempting the refund without an authorization. Follow what reaches the simulated payment adapter.

Approved amount—AuthorizationNot issuedApprover—

03 / SIMULATED PAYMENT ADAPTER

No refund operation invoked

0CALLS

STEP 1 OF 6

Does a request alone allow execution?

FOLLOW THE RESULT

Inspect the evidence.

No records yet

Each authorization or execution decision creates a signed demonstration record. Verify the original, then alter a copy to see signature verification fail.

STEP	DECISION	REASON	ADAPTER CALLS
Attempt the refund to create your first record.

BROWSER-GENERATED KEY / ECDSA P-256

Evidence is yours to inspect.

Session keys are created locally. These records are not Strix production receipts.

View the latest signed record

No record yet.

Verification checks this session’s signatures and record chain against the included public key. It does not establish trusted Strix identity or prove a real payment occurred. A modified copy never changes your original evidence.

THE ENGINEER’S QUESTION

Where does the control sit?

At the call that produces the effect. This walkthrough models exact-request binding and one-use authorization before a simulated refund adapter.

CONCEPTUAL FLOW · NOT A DROP-IN SDK EXAMPLE

agent requests a refund
  → check authorization for this exact request
  → refuse changed or consumed authorization
  → consume valid authorization
  → invoke the refund adapter
  → record the outcome

Real deployment requires server-side enforcement, atomic consumption, protected credentials, and controls over alternate execution routes. This browser model is editable by its visitor.

YOUR NEXT ACTION

What is holding your
agent out of production?

Bring one consequential action. Start a One Action Under Control evaluation with its execution route, approval conditions, and the proof you need.

Explore Strix’s published proof demo ↗

That separate walkthrough also uses demonstration evidence.