# Agent preview boundary review

Blank operational worksheet. This is not native Claude Code configuration, an enforcement mechanism or a certification. Run destructive test attempts only against approved isolated fixtures.

## Scope and owner

- Workflow and review date:
- Boundary owner and reviewer:
- Preview identity and expiry:
- Allowed targets and permitted reads:
- Allowed staging output location:
- Acceptable incidental effects (for example, restricted access logging):
- Forbidden business mutations:
- Enforcement point and policy revision:
- Alternate paths (shell, HTTP client, inherited credentials) removed or restricted:

## Proposed change

- Immutable proposal reference:
- Exact target and payload reference:
- Relevant input versions:
- Scope, fallback routes and ordering reviewed:
- Approval invalidation conditions:

## Boundary tests

For each case record the request identity, policy decision, receiving-system evidence reference, observation window, result and reviewer. Use restricted evidence handles, not credentials or sensitive payloads.

| Case | Expected | Actual and evidence | Pass / fail / unknown |
|---|---|---|---|
| Approved read | Success against the intended fixture | | |
| Forbidden mutation | Denied before any business effect | | |
| Alternate tool route | Same restriction holds | | |
| Nominal read with indirect effects | Blocked or replaced with an inert fixture | | |
| Execution with preview identity | Denied | | |
| Separately approved execution | Matches exact reviewed scope in isolated fixture | | |
| Changed target or payload | Requires new approval | | |

## Independent effect checks

- Before/after business-state evidence:
- Queues, webhooks and downstream services checked:
- Completion or drain signal used:
- Observation window and why it is sufficient for this service:
- Unaccounted-for or delayed effects:
- Failed checks and required remediation:

## Decision

- Decision: HOLD until reviewer completes this record.
- Unresolved unknowns:
- Execution identity, expiry and scope (if approved):
- Approval evidence bound to proposal and relevant input versions:
- Reviewer and decision timestamp:
- Runtime permission checks retained:

A successful preview test is evidence for this tested configuration only. Recheck after changes to identity, policy, adapters or receiving-service behavior. Keep routes with unresolved effects unavailable during preview.