# Permission denied

Injected failure: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

Failure mode `permission_denied` of the CommitLayer failure matrix, on all 8 workflows. Each run below is the sandbox's scripted agent acting on the sandbox's fake systems of record under the injected failure, an oracle reading those systems' databases, and the verdict of engine 1.0.0 from the systems of record alone. The accounts, orders and amounts are the sandbox's and describe no real customer. Last changed 2026-11-13.

| Workflow | Agent reported | Oracle (policy) | CommitLayer (outcome / policy) | Why |
|---|---|---|---|---|
| Refund a customer | success | FAIL | FAIL / FAIL | No refund was created in payments |
| Cancel a subscription | success | FAIL | FAIL / FAIL | CRM does not show the subscription cancelled |
| Change a shipping address | success | FAIL | FAIL / FAIL | Address was not updated in the order system |
| Approve a discount | success | FAIL | FAIL / FAIL | Discount was not applied in the order system |
| Close a support case | success | FAIL | FAIL / FAIL | Ticket was not closed |
| Send a payout | success | FAIL | FAIL / FAIL | No payout was created in payments |
| Deploy a service | success | FAIL | FAIL / FAIL | The platform shows no deploy |
| Place a trade | success | FAIL | FAIL / FAIL | No order on the intended product was created at the broker |

## Refund a customer

Scenario `refund/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /tickets/tick_1`: 200
- `GET /orders/order_1001`: 200
- `POST /payments/refunds`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing payments.refund_created; missing orders.order_status_changed; missing crm.note_added; missing tickets.customer_notified.

### The verdict and why

FAIL — No refund was created in payments (outcome FAIL, policy FAIL).

- expected effect, payments.refund_created observed within 10m of the action: No refund was created in payments
- expected effect, orders.order_status_changed observed within 10m of the action where status=refunded: Order did not move to refunded
- expected effect, crm.note_added observed within 10m of the action: No CRM note was added
- expected effect, tickets.customer_notified observed within 10m of the action: Customer was not notified

### Three models on the same injected failure

From the [benchmark](https://commitlayer.ai/benchmark), where a model drove the agent instead of a script. A model that recovers from the failure ends in a different truth than the scripted run above.

| Model | Agent reported | Trace-only judge | Truth | CommitLayer |
|---|---|---|---|---|
| Anthropic | failure | FAIL | FAIL | FAIL |
| OpenAI | failure | FAIL | FAIL | FAIL |
| Google | success | PASS | PASS | PASS |

## Cancel a subscription

Scenario `cancel/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /crm/subscriptions/sub_1`: 200
- `POST /crm/subscriptions/sub_1/cancel`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing crm.subscription_cancelled; missing payments.billing_stopped; missing tickets.customer_notified.

### The verdict and why

FAIL — CRM does not show the subscription cancelled (outcome FAIL, policy FAIL).

- expected effect, crm.subscription_cancelled observed within 10m of the action: CRM does not show the subscription cancelled
- expected effect, payments.billing_stopped observed within 10m of the action: Billing was not stopped
- expected effect, tickets.customer_notified observed within 10m of the action: Customer was not notified

### Three models on the same injected failure

From the [benchmark](https://commitlayer.ai/benchmark), where a model drove the agent instead of a script. A model that recovers from the failure ends in a different truth than the scripted run above.

| Model | Agent reported | Trace-only judge | Truth | CommitLayer |
|---|---|---|---|---|
| Anthropic | failure | FAIL | FAIL | FAIL |
| OpenAI | success | FAIL | PASS | PASS |
| Google | success | PASS | PASS | PASS |

## Change a shipping address

Scenario `address/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /orders/order_1001`: 200
- `POST /orders/order_1001/address`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing orders.address_updated; missing crm.note_added; missing tickets.customer_notified.

### The verdict and why

FAIL — Address was not updated in the order system (outcome FAIL, policy FAIL).

- expected effect, orders.address_updated observed within 10m of the action: Address was not updated in the order system
- expected effect, crm.note_added observed within 10m of the action: No CRM note was added
- expected effect, tickets.customer_notified observed within 10m of the action: Customer was not notified

### Three models on the same injected failure

From the [benchmark](https://commitlayer.ai/benchmark), where a model drove the agent instead of a script. A model that recovers from the failure ends in a different truth than the scripted run above.

| Model | Agent reported | Trace-only judge | Truth | CommitLayer |
|---|---|---|---|---|
| Anthropic | failure | FAIL | FAIL | FAIL |
| OpenAI | success | PASS | PASS | PASS |
| Google | success | PASS | PASS | PASS |

## Approve a discount

Scenario `discount/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /orders/order_1004`: 200
- `POST /orders/order_1004/discount`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing orders.discount_applied; missing crm.note_added.

### The verdict and why

FAIL — Discount was not applied in the order system (outcome FAIL, policy FAIL).

- expected effect, orders.discount_applied observed within 10m of the action: Discount was not applied in the order system
- expected effect, crm.note_added observed within 10m of the action: No CRM note was added

### Three models on the same injected failure

From the [benchmark](https://commitlayer.ai/benchmark), where a model drove the agent instead of a script. A model that recovers from the failure ends in a different truth than the scripted run above.

| Model | Agent reported | Trace-only judge | Truth | CommitLayer |
|---|---|---|---|---|
| Anthropic | failure | FAIL | FAIL | FAIL |
| OpenAI | success | PASS | PASS | PASS |
| Google | success | PASS | PASS | PASS |

## Close a support case

Scenario `close/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /tickets/tick_1`: 200
- `POST /tickets/tick_1/close`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing tickets.ticket_closed; missing crm.note_added; missing tickets.customer_notified.

### The verdict and why

FAIL — Ticket was not closed (outcome FAIL, policy FAIL).

- expected effect, tickets.ticket_closed observed within 10m of the action: Ticket was not closed
- expected effect, crm.note_added observed within 10m of the action: No CRM note was added
- expected effect, tickets.customer_notified observed within 10m of the action: Customer was not notified

### Three models on the same injected failure

From the [benchmark](https://commitlayer.ai/benchmark), where a model drove the agent instead of a script. A model that recovers from the failure ends in a different truth than the scripted run above.

| Model | Agent reported | Trace-only judge | Truth | CommitLayer |
|---|---|---|---|---|
| Anthropic | failure | FAIL | FAIL | FAIL |
| OpenAI | success | FAIL | PASS | PASS |
| Google | success | PASS | PASS | PASS |

## Send a payout

Scenario `payout/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /ledger/accounts/acc_1`: 200
- `POST /payments/payouts`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing payments.payout_created; missing ledger.ledger_posted; missing crm.note_added.

### The verdict and why

FAIL — No payout was created in payments (outcome FAIL, policy FAIL).

- expected effect, payments.payout_created observed within 10m of the action: No payout was created in payments
- expected effect, ledger.ledger_posted observed within 10m of the action: Ledger entry was not posted
- expected effect, crm.note_added observed within 10m of the action: No CRM note was added

## Deploy a service

Scenario `deploy/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /platform/services/svc_api`: 200
- `POST /platform/services/svc_api/deploy`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing platform.deploy_created; missing platform.health_check; missing crm.note_added.

### The verdict and why

FAIL — The platform shows no deploy (outcome FAIL, policy FAIL).

- expected effect, platform.deploy_created observed within 10m of the action: The platform shows no deploy
- expected effect, platform.health_check observed within 10m of the action where status=healthy: No healthy check after the deploy
- expected effect, crm.note_added observed within 10m of the action: No change note was added

## Place a trade

Scenario `trade/permission_denied`: 403 on the primary write, agent claims success. The system refuses the write; the agent still reports the job done.

### What the agent reported

The agent reported success. Its calls, and what it saw come back:

- `GET /broker/products/TSLA-USD`: 200
- `POST /broker/orders`: 403 (injected: error)

Agent notes: tool error: {"error":"error","status":403}.

### What the systems of record showed

No record was written after the action.

The oracle, reading the databases directly: outcome FAIL, policy FAIL: missing broker.order_created; missing broker.order_filled; missing crm.note_added.

### The verdict and why

FAIL — No order on the intended product was created at the broker (outcome FAIL, policy FAIL).

- expected effect, broker.order_created observed within 10m of the action: No order on the intended product was created at the broker
- expected effect, broker.order_filled observed within 10m of the action: The order did not fill: it was placed but no trade happened
- expected effect, crm.note_added observed within 10m of the action: No CRM note was added

## Run it in the Failure Lab

The Failure Lab replays each run above: the agent's calls, the records the systems held and the verdict. No account is needed. The verdict comes from the production engine while you watch.

- [Refund a customer, Permission denied](https://commitlayer.ai/lab?workflow=refund&failure=permission_denied)
- [Cancel a subscription, Permission denied](https://commitlayer.ai/lab?workflow=cancel&failure=permission_denied)
- [Change a shipping address, Permission denied](https://commitlayer.ai/lab?workflow=address&failure=permission_denied)
- [Approve a discount, Permission denied](https://commitlayer.ai/lab?workflow=discount&failure=permission_denied)
- [Close a support case, Permission denied](https://commitlayer.ai/lab?workflow=close&failure=permission_denied)
- [Send a payout, Permission denied](https://commitlayer.ai/lab?workflow=payout&failure=permission_denied)
- [Deploy a service, Permission denied](https://commitlayer.ai/lab?workflow=deploy&failure=permission_denied)
- [Place a trade, Permission denied](https://commitlayer.ai/lab?workflow=trade&failure=permission_denied)

The sandbox in the app runs the exact scenario in your own workspace, as a verified action:

- [`refund/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Drefund%2Fpermission_denied)
- [`cancel/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dcancel%2Fpermission_denied)
- [`address/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Daddress%2Fpermission_denied)
- [`discount/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Ddiscount%2Fpermission_denied)
- [`close/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dclose%2Fpermission_denied)
- [`payout/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dpayout%2Fpermission_denied)
- [`deploy/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Ddeploy%2Fpermission_denied)
- [`trade/permission_denied`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dtrade%2Fpermission_denied)
