Skip to content

Sandbox rehearsal

A sandbox rehearsal exercises the proposed behavior against an isolated environment. A copied form, a mocked connector, or a test account can show which checks pass, what would change, and what the test cannot establish.

Choose the closest environment in which the important behavior can be exercised safely. A copied form can validate field rules. A test connector can check request and response mapping. A mock can check how the harness reacts to a timeout or rejection. Use synthetic or authorized data and prevent live writes, messages, and charges.

Capture the tested inputs, definition revision, target, expected effects, observed results, and coverage gaps. If a rehearsal is required and no suitable target exists, hold the affected work for setup or manual handling. A proposal that changes materially needs matching evidence and review.

Use a disposable workspace and a test publisher for meeting-summaries. The following record illustrates the evidence. A portable evidence schema remains planned.

Playbook revision: publish-summary@1
Target: Test meeting summaries list
Input: Synthetic summary for a meeting with a fictional attendee
Checks: Map summary; reject undeclared attendee field; suppress live publication
Observed: Test list received only summary
Coverage gap: Live account and permission still need to be checked before dispatch

Sherma offers a real persona example. It rehearses normalized answers against a form twin and shows the exact answers for review before submission.

See the rehearsal checklist, governed execution, and isolated code execution.