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: an intake method calls a classifier 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 host:
npm install --global @jigging/jig@alphaFollow your first Flow for a complete small project, or copy the tested-patch application.
Inside the greeting project from the first-Flow guide, the everyday loop is:
jig review --allow-resolution-network
jig run flow:flows/hello --input '"Ada"'review shows the proposed changes and asks for approval. run executes the
approved revision, returns its result, and settles owned work. Later source
changes need another review.
- Get started and supported hosts
- Choose an Agent
- Working with files and dependencies
- Workflow design and use cases
- Project authoring and execution policy
- 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 Governance.md.