Code runtime

Stacksona for LlamaIndex

Gate the action adapter or workflow tool that performs a real side effect while LlamaIndex keeps reasoning and workflow context.

Where Gate goes

Inside the tool/action adapter immediately before it calls the real external service.

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

Agent/workflow chooses action→Adapter checks Gate→Execute or emit wait/revision event

Start here

1
Build the final action.
Let LlamaIndex 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

Store the proposed tool, arguments, decision, and thread_id in workflow context. A pending review can emit a wait event; requested changes can emit a revision event back to the planner.

Handle the decision

Outcome	Gate status	What LlamaIndex 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 retrieval, reasoning, context, and event flow in LlamaIndex.
Use workflow context to resume the exact reviewed action.
Do not let a raw mutation tool bypass the governed adapter.

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