> For AI agents: the complete documentation index is available at https://jig.md/llms.txt, the full documentation bundle is available at https://jig.md/llms-full.txt.

# Build with power under control

Jig runs code and Agent methods through the same composable boundary, with
powers you approve. Start with one Flow, then build Agent intelligence into
your application while keeping authority and consequences explicit.

<div className="reader-grid">
<a className="reader-card" href="/guide/"><span className="tile-index">START</span><h3>Run your first Flow.</h3><p>Install on a supported Linux host, create a method, review it, and change its result.</p><span className="card-link">Follow the quickstart ↗</span></a>
<a className="reader-card" href="/guide/request-triage"><span className="tile-index">COMPOSE</span><h3>One caller. Three implementations.</h3><p>Call code, Agent judgment, and a combination through the same method boundary.</p><span className="card-link">Explore the example ↗</span></a>
<a className="reader-card" href="/guide/understand"><span className="tile-index">UNDERSTAND</span><h3>Learn the small architecture.</h3><p>See what applications, methods, the host, and the FLOW standard each own.</p><span className="card-link">Meet the four parts ↗</span></a>
<a className="reader-card" href="/guide/for-agents"><span className="tile-index">FOR AGENTS</span><h3>Bring the right context.</h3><p>Read focused Markdown pages or the complete public documentation bundle.</p><span className="card-link">Use the agent entrypoint ↗</span></a>
</div>

## Find the guide for your task

| I want to…                                                          | Read                                                                |
| ------------------------------------------------------------------- | ------------------------------------------------------------------- |
| Compose code and Agent work through one caller                      | [Request triage](https://jig.md/guide/request-triage.md)            |
| Produce a patch with executed checks                                | [Tested patch](https://jig.md/guide/tested-patch.md)                |
| Check whether my host can run Jig                                   | [Supported hosts](https://jig.md/guide/index.md#supported-host)     |
| Adjust startup verification, terminal appearance, or other settings | [Settings and configuration](https://jig.md/guide/configuration.md) |
| Choose a model, API, or native client                               | [Choose an Agent](https://jig.md/guide/agents.md)                   |
| Import libraries or share local packages                            | [Flow dependencies](https://jig.md/guide/dependencies.md)           |
| Supply source files and deliver artifacts                           | [Working with files](https://jig.md/guide/files.md)                 |
| Show progress in a terminal or another application                  | [Live progress](https://jig.md/guide/channels.md)                   |
| Put Agent interpretation behind application policy                  | [Handle a disputed charge](https://jig.md/guide/support-case.md)    |
| Decide whether I need a graph or several Agents                     | [Workflow structure](https://jig.md/guide/workflow-design.md)       |
| Share work across a team                                            | [Team ownership](https://jig.md/guide/teams.md)                     |
| Understand a result or recover from failure                         | [Results and recovery](https://jig.md/guide/results.md)             |
| Look up a term or a common question                                 | [Concepts and questions](https://jig.md/guide/concepts.md)          |

## Find an exact contract

Guides teach the experience. Specifications define the requirements.

- [Project authoring](https://jig.md/spec/project-sdk.md): declare Flows, Bindings, and project policy.
- [Execution policy](https://jig.md/spec/project-policy.md): review, accepted revisions, limits, containment, and lifecycle.
- [Agent Run](https://jig.md/spec/agent-run.md): bounded intelligent work through operator-selected Agents.
- [Project Command](https://jig.md/spec/project-command.md): commands and execution evidence.
- [Channels](https://jig.md/spec/channels.md): live communication between exact participants.
- [Run Checkpoint](https://jig.md/spec/run-checkpoint.md): retained application output and its limits.

Capability identity pages are listed in the sidebar. They explain the identity
and link to its exact descriptor; they are not invocation endpoints.

## Know which kind of page you are reading

**Guides** explain the documented alpha surface and link to prerequisites.
**Specifications** define exact contracts. **Research** records possibilities
and evidence gates; it is not an availability list. The
[use-case catalogue](https://jig.md/use-cases.md) and
[orchestration research](https://jig.md/orchestration-patterns.md) belong to that last group.

Use search for a concept, the sidebar for a learning path, and the page outline
for a section. Every page also has **Copy Markdown** and a plain-text version
for an Agent or your own notes.