Asset Core Docs

Deterministic world-state engine documentation and API references.

Decision Gate docs

Start here: Integration

If you are integrating Asset Core into an application or service, this path gives you the fastest route to a correct, production-safe integration. It focuses on the HTTP contract, the transaction model, and the SDKs that map directly to the public API.

Asset Core is deterministic and transactional. That means your integration is as much about correctness and replay as it is about throughput. The pages below are ordered to build the mental model and then move into task execution, with Runtime Model available when you want the formal why.

  1. Getting Started Overview - System components and data flow.
  2. Runtime Model - Single-writer world, determinism, and replay.
  3. First Commit and Read - End-to-end HTTP walkthrough.
  4. HTTP API - Endpoint catalog and request structure.
  5. Transactions and Error Model - Commit envelope, responses, and error taxonomy.
  6. Python SDK - Typed client and operation builders.

What success looks like

A correct integration should be able to provision a namespace, submit a transaction with an idempotency key, and read back deterministic state with freshness metadata. If you can do that, you have the core integration loop working and can proceed to domain-specific modeling.

Next steps

  • If you need the conceptual model behind determinism and replay, read Runtime Model.
  • If you are building automation or agents, switch to the Automate path.