Pre-alpha documentation
Compose skills from durable primitives.
Choose capability bundles, shared-state subgraphs, durable child runs, or guarded MCP Skills without creating a second execution engine.
Choose the smallest durable boundary
| Need | Primitive | Boundary |
|---|---|---|
| Instructions plus independent Tools | Capability bundle | No separate runtime state |
| Fixed multi-step shared-state flow | Shared-state subgraph | One durable barrier per node |
| Isolated long-running work | Durable child run | Independent lifecycle and budget |
| Remote static package | MCP Skill activation | Verified untrusted content and guarded execution |
A Tool collection does not need a graph. Use a subgraph only when control flow itself must recover deterministically. Use a child run when state, ownership, deadline, budget or cancellation must be isolated.
Resolve everything before admission
Pin exact module versions, reject cycles and collisions, topologically order dependencies and freeze one deployment snapshot. Prompt slots keep unique instruction identities, provenance and trust labels. Never merge remote Skill bytes into privileged system instructions. New configuration creates a new Agent version; old executables stay installed until their runs drain.
Compile limits into existing Agent budgets, Tool execution limits, graph step bounds, child-run budgets and MCP acting windows. Conflicts choose the most restrictive compatible value or fail startup—composition never silently widens authority or resources.
Keep MCP activation explicit
MCP catalog discovery never mutates an Agent. Each direct or nested remote Skill receives explicit policy approval, verified lazy reads, a durable acting window and per-operation permits. Execution still passes through the ordinary Tool registry and attempt ledger. Dynamic manifests, native-code hot loading and automatic discovery-to-Agent composition are not claimed.
Read the complete design and JiaClaw example, then use MCP Skills or subgraphs and loops for the selected boundary.