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

Compile a deterministic graph.

Use StateKnot's implemented graph compiler to validate a bounded topology and freeze its schema, reducer, limits, and canonical digest.

Run the maintained example

The example is compiled by the workspace's all-targets gate. It declares validate → finish, compiles the descriptor, and prints the SHA-256 digest of its canonical definition.

Shell · from a repository checkout
cargo run -p stateknot-core --example compiled_graph --locked

Read the complete Apache-2.0 example in compiled_graph.rs.

What compilation freezes

  1. Owner-qualified identity

    A graph name is local to an issuer/subject owner and an exact semantic version. Any definition change requires another version.

  2. Schema and reducer references

    Input, state, update, output, and reducer implementation references are digest-pinned; executable code is never inferred from a name.

  3. Bounded topology

    Entry nodes, successors, routes, maximum parallelism, and maximum supersteps are part of the immutable definition.

  4. Canonical identity

    Nodes and routes are put in stable order, serialized as canonical JSON, and hashed. Checkpoints retain the resulting exact reference.

Invalid graphs fail before admission

The compiler rejects, among other cases:

  • duplicate node or route identities;
  • missing entry or successor nodes;
  • nodes unreachable from every entry;
  • paths that cannot reach a wait or terminal boundary;
  • ready sets above graph parallelism limits; and
  • definitions above the node, route, or two-MiB byte ceilings.

Register once, recover by exact reference

Migration 13 stores canonical compiled definitions under a tenant plus owner/name/version key. Re-registering identical bytes is idempotent; reusing the version for another digest is a conflict. Recovery recompiles the bytes and validates the checkpoint binding under the live fence.

Rust · current pre-alpha store API
let registered = store
    .register_graph_definition(tenant_id, graph)
    .await?;

let pinned = recovery.load_pinned_graph().await?;

Missing, altered, cross-tenant, or checkpoint-mismatched graph evidence fails closed. During claimed recovery, integrity failure enters the same fence-bound quarantine path as corrupt checkpoint or journal evidence.

Move from definition to execution

The pure barrier planner already validates complete result coverage, applies updates to the exact pinned reducer in stable NodeId order, resolves continue/route/wait/terminal control, and creates a successor checkpoint intent. The Runtime now binds that definition to an offline schema/reducer/node executable closure and drives the durable root path. Continue with the Durable Graph runtime guide, then the Durable Agent Loop guide. Bounded journal-isolated siblings now overlap with canonical commits; loops, subgraphs, and the stable public Agent API remain later milestones.