#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.

START

Run your first Flow.

Install on a supported Linux host, create a method, review it, and change its result.

Follow the quickstart ↗ COMPOSE

One caller. Three implementations.

Call code, Agent judgment, and a combination through the same method boundary.

Explore the example ↗ UNDERSTAND

Learn the small architecture.

See what applications, methods, the host, and the FLOW standard each own.

Meet the four parts ↗ FOR AGENTS

Bring the right context.

Read focused Markdown pages or the complete public documentation bundle.

Use the agent entrypoint ↗

#Find the guide for your task

I want to…	Read
Compose code and Agent work through one caller	Request triage
Produce a patch with executed checks	Tested patch
Check whether my host can run Jig	Supported hosts
Adjust startup verification, terminal appearance, or other settings	Settings and configuration
Choose a model, API, or native client	Choose an Agent
Import libraries or share local packages	Flow dependencies
Supply source files and deliver artifacts	Working with files
Show progress in a terminal or another application	Live progress
Put Agent interpretation behind application policy	Handle a disputed charge
Decide whether I need a graph or several Agents	Workflow structure
Share work across a team	Team ownership
Understand a result or recover from failure	Results and recovery
Look up a term or a common question	Concepts and questions

#Find an exact contract

Guides teach the experience. Specifications define the requirements.

Project authoring: declare Flows, Bindings, and project policy.
Execution policy: review, accepted revisions, limits, containment, and lifecycle.
Agent Run: bounded intelligent work through operator-selected Agents.
Project Command: commands and execution evidence.
Channels: live communication between exact participants.
Run Checkpoint: 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 and orchestration research 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.