Relationships
#2666 gatorwalk-factory: conditional human approval
Opened by skunk-ape · 9/29/2026· Shipped 9/29/2026
Found while mapping the swamp-extensions process onto the gatorwalk lifecycle format (swamp-club #2630; see gatorwalk-factory/lifecycles/swamp-extensions.md, Format gaps).
A human-approval gate applies every time its transition is taken. Some human stops only apply when the data says so: in swamp-extensions a person must see the regression evidence and verdict before a bug is classified as a regression, but a non-regression classification goes ahead without them.
Today the only ways to express that are a second exit per case (gated on the condition, one with the approval and one without; for triage that doubles four exits to eight) or a cel gate that blocks until the data changes, which cannot express 'go ahead once a person has seen it'.
Wanted: a human-approval gate that applies only when a condition over run data holds (for example a when: CEL expression), with the graph analysis treating it accordingly.
Shipped
Click a lifecycle step above to view its details.
skunk-ape commented 9/29/2026, 3:58:56 PM
Decision (2026-09-29, from the format-gap review): in play for launch. The launch material needs it: the classify preset (chores skip plan review, security always stops for a human) and the Jev decision plugin's uncertain band (GW-14). Suggested shape: a when CEL expression on human-approval; when it is false the gate does not apply. status must report whether each approval is required right now, because the driving skill's stop-and-ask rule depends on it; update the skill accordingly. The graph analysis treats a conditional approval as a possible human stop. Use it for the regression case in lifecycles/swamp-extensions.yaml. #2667 (requireField matching) is being built in parallel and also touches gates.ts and graph.ts, so expect a rebase.
Sign in to post a ripple.