TCC Engine overview

TCC Engine checkpoints a logical continuation at durable boundaries and resumes by loading that continuation. It does not replay the completed prefix.

Choose the integration that matches your deployment model:

You want to	Use
Deploy Programs to Trigora Cloud or run them with trigora dev	@trigora/sdk, @trigora/client, and the trigora CLI
Embed TCC Engine in your own host	The published packages below from tcc-engine

npm:    @tcc-engine/frontend-typescript, @tcc-engine/bindings-javascript
PyPI:   tcc-engine
Cargo:  tcc-ir, tcc-state, tcc-core, tcc-host, tcc-host-sqlite, tcc-rust-frontend

The Node and Python SQLite hosts in the repository are reference implementations for the host protocol and conformance suite; they are not published packages. Similarly, @tcc-engine/host-node and @tcc-engine/frontend-rust are not available as published packages. The Trigora CLI includes tcc-rust-compile, while tcc-host-sqlite provides the persistent Rust host used by trigora dev. See Reference SQLite hosts.

TCC Engine
    ↓
host_protocol_version: 1
    ↓
your host
    ├── persistence
    ├── effects
    ├── events
    ├── timers
    └── scheduling

Persistence belongs to the host rather than the engine. The reference hosts use SQLite, while Trigora Cloud provides its own persistence layer. Both implement host protocol version 1 and are validated against the same conformance suite. See Host protocol and Host conformance v1.

Source: github.com/trigora-dev/tcc-engine.