Workflow platform

Stacksona for Make

Place an HTTP Gate module in the governed route immediately before the module that performs the real action.

Where Gate goes

Inside the route that owns the target API or app side effect.

Keep the platform's normal reasoning and orchestration. Gate only the exact action at the last safe point before execution.

Scenario/router chooses route→Gate HTTP module checks it→Target module executes or route stops

Start here

1
Build the final action.
Let Make choose the action and produce the arguments it intends to execute.
2
Check the exact action with Gate.
Send tool_name and the final payload immediately before the side effect.
3
Follow one of four outcomes.
Continue, wait, revise, or stop. You do not need the advanced features to get this basic path working.

Minimal setup

Map the final action values first, then send those exact values to Gate. Only the executable outcome should reach the target module.

Handle the decision

Outcome	Gate status	What Make should do
Continue	`allow` or `approved`	Execute the exact proposed action. If signed proof is required, validate it first.
Wait	`pending_review`	Store `thread_id` and resume that exact review later.
Revise	`changes_requested`	Return reviewer feedback to the part of the runtime that can revise the proposal.
Stop	`reject` or `rejected`	Do not execute. Replan, fall back, or end the action.

Unknown or failed decision = stop.

Fail closed if Gate cannot be reached, returns an unknown state, or required approval proof is missing or invalid.

Platform notes

Keep scenario routing, mapping, and app credentials in Make.
Use a separate continuation scenario or webhook for long human reviews.
Send requested changes back through the mapping or AI revision path.

Advanced: review threads, revisions, proof, and audit

task_id is your grouping ID. thread_id identifies the exact Gate review and should be persisted whenever work can pause.

For changes_requested, revise on the same review thread using the revision event contract. For high-impact actions that require signed proof, validate the returned approval token before execution. Log execution success or failure when you need complete audit evidence.

For long reviews, use the platform's durable continuation mechanism instead of keeping a process, workflow, or runner open.

Advanced runtime patterns Full Gate API Exact decision states