Verify
Why a named command's exit code at a named commit is the only evidence Palisade accepts that work is done.
A green verification badge means a configured check exited 0 (success) at a specific commit. It does not mean the change is bug-free; it means that check passed. An agent’s summary alone does not create passing evidence.
What counts
| Evidence | Counts as done |
|---|---|
verify exited 0 at the current commit | Yes |
| The agent says the work is complete | No |
| Task checkboxes the agent ticked | No. They are labelled as agent self-reports. |
| Tests the agent says it ran | No |
Palisade never labels work complete, satisfied, or implemented without that evidence.
Merge is gated on it
In the Review lane, choose Configure Verification to name your project checks. Select Run verify to inspect results before merging.
Merge runs configured checks that do not already have passing evidence at the current commit. It stops if a check fails, the branch changes, or the worktree has uncommitted changes. You can configure more than one check, such as tests, typecheck, lint, and build.
Overriding
You can merge without a passing verify. Choose Merge anyway… and confirm the override. Palisade records it as an override, not a pass.
Verify in playbooks
A playbook gate can be a verify command. The next node only runs once it passes.
Where it shows
- The Fleet board shows verify evidence on each row, for example
NOT VERIFIED. - The Review lane shows it beside the diff.
- A failed verify moves the thread to Needs attention.