Build with Agents as naturally as you build with code.
Skills give Agents instructions and resources for useful work. Jig and FLOW help you bring that work into your software as executable methods you can call and combine with ordinary code.
A Flow packages a reusable method. When executable, it accepts input and returns an outcome and result. Its implementation can use code, Agent judgment, or both. The caller works with the method's contract without adopting its internal orchestration model.
FLOW is the independent standard for that package and invocation boundary. Jig is the microkernel-inspired host that runs accepted methods with operator-chosen powers and accounts for their execution. Methods own the work; applications own purpose and consequences; Jig owns the common execution boundaries.
Start with one caller, three implementations: a contact importer calls a column mapper written as code, an Agent method, or a combination. Its caller stays unchanged. The shared interface keeps composition consistent; it does not guarantee equal answers or make Agent judgment correct.
For larger applications, try a tested patch or support-case handling.
The shared aspiration is to expand human possibility. FLOW pursues capability compounding; Jig pursues agency through power under control. Why FLOW exists and how Jig works explain the architecture behind them.
Jig's current source uses the source-available Bread License: personal non-business use, genuine evaluation, and business use below US$1m in consolidated group annual revenue are free. Larger groups need company coverage for operational use. Jig's prices buy permanent rights to covered releases across applications, including twelve months of new official releases.
Install the developer alpha on a supported Linux or Mac host:
npm install --global @jigging/jig@alpha
jig init hello-jig
cd hello-jig
jig review --allow-resolution-network
jig run flow:flows/hello --input '"Ada"'Read the source and policy during review, then approve the exact revision before running it.
The network flag permits dependency preparation. It gives the Flow no runtime network access.
Expect status: "succeeded", outcome: "done", and output.message: "Hello, Ada!".
Follow your first Flow to change that result and handle a failed run. Then call it from your application, add an Agent, and compose methods. Later source or policy changes need another review.
For Agent-assisted development, install the FLOW and Jig authoring skills in your project. They teach portable Flow design and Jig's project workflow.
- Documentation home — choose a task or learning path.
- Start here — run, call, and change one method.
- Build — compose methods, use files, add effects, and handle results.
- Understand — learn what the application, method, operator, and host each own.
- Examples — follow complete applications through their results and checks.
- Reference — look up settings, limits, APIs, and exact host contracts.
- Research — explore hypotheses separately from supported behavior.
- FLOW specifications
- Security, contributing, and release process
Jig is prerelease software. See the guides for the current supported surface. Licenses are mapped in LICENSES.md; FLOW's public stewardship is described in FLOW governance.