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.
Select an isolated target
Section titled “Select an isolated target”Test account, mock, or copy
Section titled “Test account, mock, or copy”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.
Record what ran
Section titled “Record what ran”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.
Example Meeting desk rehearsal
Section titled “Example Meeting desk rehearsal”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@1Target: Test meeting summaries listInput: Synthetic summary for a meeting with a fictional attendeeChecks: Map summary; reject undeclared attendee field; suppress live publicationObserved: Test list received only summaryCoverage gap: Live account and permission still need to be checked before dispatchSherma 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.