> For the complete documentation index, see [llms.txt](https://docs.sail.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sail.money/sailor/guides.md).

# Guides

Task-oriented walkthroughs, each grounded in real `sailor` commands. In rough order of the operator lifecycle:

1. [Deploy & predict an SMA](/sailor/guides/deploy-sma.md) — create the account, and compute its deterministic address up front.
2. [Build & register a mandate](/sailor/guides/build-a-mandate.md) — author permissions, then register them.
3. [Configure a shared template](/sailor/guides/configure-a-template.md) — use an example template end to end.
4. [Run a strategy & dispatch](/sailor/guides/run-a-strategy.md) — write the agent `tick()`, run it, and read a denied dispatch.
5. [Simulate before going live](/sailor/guides/simulate.md) — prove a permission off-chain (PASS / FAIL / REVERT).
6. [Multi-chain operation](/sailor/guides/multi-chain.md) — the same SMA address across the supported chains.
7. [Automate with GitHub Actions](/sailor/guides/ci.md) — run the agent on a schedule in CI.

Every command here is verified against the Sailor source. Add `--json` to most commands for machine-readable output (useful for agents and CI).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sail.money/sailor/guides.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.