Inspectable fictional example
Sample coding-agent run: objective to review evidence
This is a fictional walkthrough, not a customer run, live integration, release artifact, or performance result. It illustrates the records an evaluator should inspect in a real BranchRunner workflow.
TASK-482 · successful recovery
Example- Objective
- Retry failed webhook deliveries with bounded exponential backoff.
- Requirements
- Backoff with jitter; five-attempt limit; alert on final failure; queue schema unchanged.
- Workspace
- Isolated worktree and disposable preview environment.
- Validation
- Unit checks and integration scenario represented as passed example evidence.
- Human decision
- A reviewer approves the displayed diff only after inspecting requirements and checks.
TASK-482 · failed validation path
Example- Failure
- A validation check fails; the run is not marked delivered.
- Preserved evidence
- Requirement ledger, command output, diff, workspace reference and audit events remain available for review.
- Recovery
- A person corrects scope or retry conditions, then a new attempt records its own evidence.
- Limitation
- No downloadable export or released reproduction artifact is published yet; do not treat this fictional page as executable proof.