Verification
Verification checks every Change and every night’s state against deterministic checks and returns verdicts, never Approvals.
Outcome
| Part | This Process |
|---|---|
| Outcome | Each Change carries a pass or fail verdict with Evidence, and each regression found overnight is an Issue with a reproduction. |
| Reads | Change |
| Leaves | Issue, Change, Evidence |
| Runs in | Each Startup |
Accountable
Workflows
| Workflow | Runs | Team |
|---|---|---|
| Nightly quality run | every day at 03:00 | Quality Team |
| Change verdict | on Change.created | Quality Team |
Who does each step
| Workflow | Step | Role | Calls | Approval |
|---|---|---|---|---|
| Nightly quality run | 1. Re-run every check across the Startup. | Tester | Action.evaluate | None |
| Nightly quality run | 2. Replay known-good Actions on every Interface. | Tester | Watch.replay | None |
| Nightly quality run | 3. Walk the synthetic paying stranger from signup to first value. | Tester | ||
| Nightly quality run | 4. Open an Issue for each regression, with the Action that reproduces it. | Tester | Issue.create | None |
| Change verdict | 1. Run the Change’s checks. | Quality Lead | Change.review | None |
| Change verdict | 2. Replay known-good Actions and the synthetic paying stranger against it. | Quality Lead | Watch.replay | None |
| Change verdict | 3. Record the verdict, pass or fail, with its Evidence. | Quality Lead | Evidence.create | None |
Events
| Direction | When | What happens |
|---|---|---|
| In | Every day at 03:00 | Starts Nightly quality run |
| In | On Change.created | Starts Change verdict |
| Out | Action.evaluated | Raised by step 1 of Nightly quality run |
| Out | Watch.replayed | Raised by step 2 of Nightly quality run |
| Out | Issue.created | Raised by step 4 of Nightly quality run |
| Out | Change.reviewed | Raised by step 1 of Change verdict |
| Out | Evidence.created | Raised by step 3 of Change verdict |
Plays
No Play names this Process.
Controls
- Worker competence
- Control wake review
- Control definition
- One-way Action windows
- Control sameness
- Adversarial control testing
- Namespace isolation
- Append-only records
- Change approval
- Agent definition evals
- Environment separation
- Input validation
- Action completion
Settings
None.
Failure
A failed step retries; when retries run out, the Action goes to the Quality Lead.
Loop
No loop: the path is never randomized, because it serves Agent definition evals.
Code
Turn on verificationEnable
On by default for every Product Template. Process.pause stops new Actions; Actions in progress finish.
Example
A Change renames total to amount in an invoice-parsing API. Two known-good runs fail against it, so the verdict is fail, with both runs as Evidence. That night, the quality run passes every replay on the unchanged main line.