StateKnot
Docs · Start Overview Choose the right entry point and understand the pre-alpha boundary. Docs · Start Getting started Install the pinned toolchain and validate the repository locally. Docs · Start Core contract examples Compile the first Agent, typed Tool, Model stream, and explicit protocol mapping without runtime dependencies. Docs · Start Typed Agent Generate and pin typed schemas, then bind the first-party OpenAI and Anthropic adapters. Docs · Start In-process Agent Run a typed Agent without HTTP while preserving PostgreSQL durability, authorization, recovery, and owned roles. Docs · Start Durable admission Atomically commit authenticated intent, database time, the first event, and the initial checkpoint. Docs · Start Durable runs and results Submit with a durable ingress key, recover the original run, and read a verified public result. Docs · Understand Compile a graph Build a schema-pinned graph, validate its topology, and freeze its canonical digest. Docs · Understand Subgraphs and loops Compose shared-state subgraphs, finite loops, and explicit recovery-safe return paths. Docs · Understand Skill composition Choose capability bundles, shared-state subgraphs, durable child runs, and guarded MCP Skills without creating a second runtime. Docs · Understand Durability model Learn how journal, checkpoint, lease, fence, and recovery evidence fit together. Docs · Understand Durable Graph runtime Register exact executable code, replay noninitial state, and drive deterministic bounded sibling batches under one fence. Docs · Understand Durable Agent Loop Commit lifecycle handoffs and execute one tenant-scoped durable scheduling quantum. Docs · Understand Durable invocations Execute exact model and tool attempts with durable starts, staged ordered Tool coordination, streaming validation, and no-dispatch terminal recovery. Docs · Understand Provider-native Agent Compile and operate the durable multi-turn graph with bounded output repair, ordered parallel read-only Tools, write barriers, policy, accounting, and cancellation evidence. Docs · Integrate Local Rust Tools Generate digest-pinned schemas, register typed local code, and preserve the durable invocation boundary. Docs · Integrate AgentService v1 Authorize and expose exact durable Agent revisions through the versioned embedding boundary. Docs · Integrate Agent HTTP v1 Submit, recover, read and cancel through authenticated bounded JSON HTTP. Docs · Integrate General MCP Tool client Discover and call bounded stateless MCP 2026-07-28 Tools with JSON/SSE, OAuth, custom headers, and mediated MRTR. Docs · Integrate MCP OAuth client Bind one MCP resource to challenge-driven discovery, PKCE, issuer validation, durable credentials, and bounded replay. Docs · Integrate MCP Remote Tool Bind one strict stateless MCP 2026-07-28 Tool with pinned identity, schemas, durable dispatch, and reconciliation. Docs · Integrate MCP Server profile Expose bounded Tools, Resources, Prompts, Completion, and MRTR behind the strict stateless production boundary. Docs · Integrate MCP Skills Publish and activate Final SEP-2640 static Skills with immutable manifests, origin-scoped approval, and verified lazy reads. Docs · Integrate MCP conformance status See the frozen official runner inventory, implemented evidence, and exact boundary of current MCP claims. Docs · Integrate A2A 1.0 Client Discover and pin one agent, call all eleven operations, and reconcile durable unknown sends only through attested remote guarantees. Docs · Integrate Durable artifact storage Materialize terminal A2A parts into immutable PostgreSQL metadata and private integrity-checked object bytes. Docs · Integrate A2A 1.0 Server Expose bounded HTTP+JSON and JSON-RPC/SSE through identity-first policy and a durable service contract. Docs · Integrate A2A conformance status Inspect the frozen official TCK, audited harness patch, exact result, and server-only claim boundary. Docs · Operate Fair scheduling Configure replica-safe weighted tenant selection, exact starvation bounds, rollout, and retention. Docs · Operate PostgreSQL provider Configure, migrate, verify, and test the implemented durability provider. Docs · Operate Host qualification Record bounded capacity, recovery and fault evidence without turning CI into a production SLO claim. Docs · Project Versioning and releases Pin the public alpha exactly and understand compatibility, MSRV, durable-data, and release gates. Docs · Project Implementation status See what is implemented, in progress, and deliberately not claimed. Home Architecture map What exists, what is active, and what remains planned. Home Current cut Implemented slices and explicit gaps. Home Roadmap The path from contracts to a qualified v1. Repository Source code StateKnot/StateKnot on GitHub. Repository RFCs Draft architecture and durable execution contracts. Repository Security policy Private vulnerability reporting and support policy.
↑↓ navigate ↵ open 39 results

Pre-alpha documentation

Durability is evidence, not process memory.

The StateKnot durability model separates logical work, physical ownership, external effects, and authoritative graph state.

Why the boundaries exist

Agent work crosses databases, model providers, tools, humans, and remote agents. A process crash cannot prove whether an external request ran, and an in-memory future cannot authorize a replacement worker. StateKnot therefore records the evidence needed to make the next decision without pretending that every side effect is exactly once.

The evidence chain

  1. Journal

    Append-only canonical facts establish what became authoritative and in which run-local order.

  2. Checkpoint

    An immutable graph and state snapshot is anchored to an exact journal head and parent checkpoint.

  3. Lease and fence

    A database-clock lease grants temporary ownership; every worker write repeats its monotonically increasing fencing epoch.

  4. Invocation ledger

    Model and tool intent, physical attempts, terminal evidence, and unknown external effects survive process loss.

  5. Pending result

    One logical node result commits before the barrier and remains reusable if a sibling or worker crashes.

  6. Barrier

    A complete canonical result set becomes one successor checkpoint and consumes its pending inputs atomically.

Logical identity is not worker identity

A node activation belongs to an exact tenant, run, graph namespace, superstep, and node. A physical AttemptId and its worker FencingEpoch describe who tried to execute that logical work. Recovery may replace the physical attempt without changing result order or silently creating another logical invocation.

External work never runs inside a database transaction

StateKnot commits intent or an attempt start, closes the transaction, and only then dispatches model, tool, A2A, or human work. The returned evidence is committed in a later transaction. This prevents long-held database locks while keeping crash boundaries explicit.

Exactly-once database mutation does not imply exactly-once real-world side effects. Tools use idempotency keys where supported and preserve an explicit unknown outcome when completion cannot be proven.

What recovery can decide today

Recovery now reloads the exact compiled graph from a tenant-scoped immutable registry, recompiles its canonical bytes, validates the checkpoint binding, and then verifies pending results and complete attempt histories under one live fence. It classifies each ready node as completed, dispatchable, deferred, in flight, failed, or exhausted, then requires a durable attempt start before node code can launch. When every unsettled node is deferred, the store atomically releases the lease into an indexed database-time wakeup; direct claims cannot run it early.

The durable Driver now freezes executable schemas, reducers, and nodes; independently replays every committed noninitial checkpoint; renews the lease while node code runs; commits Continue barriers; and returns typed Wait/Terminal/failure handoffs. Read the runtime integration contract and Agent Loop contract before wiring a worker deployment.