# Stacksona Docs

> Approval, policy, signed decision, and audit controls for AI agent workflows.

## Canonical starting points
- [AI should choose the path. You govern the moment it acts.](https://docs.stacksona.com/index.md): Add policy and human review to governed agent actions without rebuilding your runtime or workflow.
- [Stacksona for Custom REST](https://docs.stacksona.com/integrations/custom-rest.md): Call the Gate Agent API directly from any HTTP-capable runtime before executing the governed action.
- [Stacksona for MCP](https://docs.stacksona.com/integrations/mcp.md): Enforce Gate in the MCP tool boundary before the real domain tool is forwarded or executed.
- [Stacksona for n8n](https://docs.stacksona.com/integrations/n8n.md): Keep the workflow flexible and put Stacksona immediately before the node that performs the governed action.
- [Stacksona for Node / TypeScript](https://docs.stacksona.com/integrations/node-typescript.md): Wrap your tool function with Stacksona Gate immediately before the real side effect.
- [Gate Agent API Reference](https://docs.stacksona.com/reference/api-contract.md): Complete Stacksona Gate Agent API reference for runtime tool contracts, policy checks, human review, decisions, signed approvals, events, revisions, webhooks, limits, and errors.
- [Decision Statuses](https://docs.stacksona.com/reference/decision-statuses.md): Use Stacksona Gate decision statuses to execute, wait, revise, replan, or stop safely.
- [LLM-ready Documentation](https://docs.stacksona.com/reference/llm-ready-docs.md): How Stacksona docs expose llms.txt, llms-full.txt, Markdown exports, and copy-for-LLM buttons for AI assistants and coding agents.
- [Security](https://docs.stacksona.com/reference/security.md): Security guidance for runtime tool execution, Gate API keys, signed approvals, webhook verification, and fail-closed agent workflows.

## Workflow playbooks
- [Approve customer email before it runs](https://docs.stacksona.com/playbooks/customer-email-approval.md): Use this pattern when an agent is about to send a customer-facing email, reply, or outbound message that a person should review first.
- [Workflow Playbooks](https://docs.stacksona.com/playbooks.md): Start with the action your agent is about to take. Each playbook shows where to add Stacksona before the action runs, what to show the reviewer, and what to log after the decision.
- [Approve production API calls before they run](https://docs.stacksona.com/playbooks/production-api-approval.md): Use this pattern when an agent is about to call a production API, trigger a job, send a webhook, mutate a database record, or touch an internal system.
- [Approve refunds before they run](https://docs.stacksona.com/playbooks/refund-approval.md): Use this pattern when an agent is about to issue a refund, credit, adjustment, or billing change that a person should review first.

## Platform guides
- [Stacksona for Copilot Studio](https://docs.stacksona.com/integrations/copilot-studio.md): Wrap governed Copilot actions in a connector, Power Automate flow, HTTP action, or service that checks Gate before execution.
- [Stacksona for CrewAI](https://docs.stacksona.com/integrations/crewai.md): Wrap side-effecting CrewAI tools so the crew can reason and delegate normally while Gate controls execution.
- [Stacksona for Custom REST](https://docs.stacksona.com/integrations/custom-rest.md): Call the Gate Agent API directly from any HTTP-capable runtime before executing the governed action.
- [Stacksona for Dify](https://docs.stacksona.com/integrations/dify.md): Put a Gate HTTP node or governed action service immediately before the Dify action that changes the outside world.
- [Stacksona for GitHub Actions](https://docs.stacksona.com/integrations/github-actions.md): Check the exact deployment, release, migration, or production operation immediately before the job performs it.
- [Stacksona for Google ADK](https://docs.stacksona.com/integrations/google-adk.md): Wrap governed ADK tool execution with Gate while session state and agent reasoning remain in ADK.
- [Stacksona for LangGraph](https://docs.stacksona.com/integrations/langgraph.md): Put Gate in the governed tool-execution node while LangGraph keeps planning, routing, checkpoints, and state.
- [Stacksona for LlamaIndex](https://docs.stacksona.com/integrations/llamaindex.md): Gate the action adapter or workflow tool that performs a real side effect while LlamaIndex keeps reasoning and workflow context.
- [Stacksona for Make](https://docs.stacksona.com/integrations/make.md): Place an HTTP Gate module in the governed route immediately before the module that performs the real action.
- [Stacksona for MCP](https://docs.stacksona.com/integrations/mcp.md): Enforce Gate in the MCP tool boundary before the real domain tool is forwarded or executed.
- [Stacksona for n8n](https://docs.stacksona.com/integrations/n8n.md): Keep the workflow flexible and put Stacksona immediately before the node that performs the governed action.
- [Stacksona for Node / TypeScript](https://docs.stacksona.com/integrations/node-typescript.md): Wrap your tool function with Stacksona Gate immediately before the real side effect.
- [Stacksona for OpenAI Agents SDK](https://docs.stacksona.com/integrations/openai-agents.md): Wrap each governed function tool so Gate checks the exact selected function arguments before the function executes.
- [Stacksona for Salesforce Agentforce](https://docs.stacksona.com/integrations/salesforce-agentforce.md): Gate the Apex, Flow, or service boundary that performs a governed CRM or external mutation.
- [Stacksona for Zapier](https://docs.stacksona.com/integrations/zapier-agents.md): Use Evaluate Action immediately before the app action, then resume the exact review thread when human review is required.

## Package guides
- [@stacksona/agent-tools](https://docs.stacksona.com/packages/agent-tools.md): Deterministic utility tools for agents, available through CLI, TypeScript imports, request files, MCP mode, and native imports for event context and stable task identifiers.
- [@stacksona/mcp-server](https://docs.stacksona.com/packages/mcp-server.md): MCP server for Stacksona Gate approvals, decision polling, audit logging, signed token validation, and revision events.
- [n8n-nodes-stacksona](https://docs.stacksona.com/packages/n8n-node.md): n8n community node for Stacksona Gate approvals, audit events, decision polling, signed token validation, and approval waiting.
- [@stacksona/sdk](https://docs.stacksona.com/packages/sdk.md): TypeScript and JavaScript SDK for Stacksona Gate approvals, audit events, polling, signed token validation, revision events, and gated action execution.

## Full export
- [llms-full.txt](https://docs.stacksona.com/llms-full.txt): Complete Markdown export of all current Stacksona integration docs.