Actions and verifiers

Helix Patch uses both. They share HTTP + M2M transport into Patch, but answer different questions.

	Remote verifier	Remote action
Question	Is this good enough?	Please do X
When	HEE lifecycle phases (executor, task_complete, run_complete)	Brain chooses mid-session
Patch API	POST /v1/hee/verify	POST /v1/hee/actions
Binding	remoteVerifiers / heeRemoteVerifiers	remoteActions / heeRemoteActions
Result that matters	{ ok } — can block the session	{ ok, data } — tool output for the brain
Examples	Trivy closure vs baseline CVEs	scan_fs, apply_bump, open_pr, notify, try_image_on_cluster

Trivy stays in Patch. helix-ee never embeds scanner logic; it only POSTs evidence (verify) or requests tools (actions).

How bindings get to helix-ee

Inside one remediation session

Campaign loop (many sessions)

Verifiers and actions apply inside each HEE session. Across days, Patch owns merge wait + rescan and starts the next IO/HEE session when findings remain.

See also: contributor doc HELIX_PATCH_CAMPAIGN.md.