Skip to content
Trigora

Search docs by title or keyword.
    Product Docs Pricing Research Blog GitHub Start building →
    Start building →

    Reference SQLite hosts

    The reference hosts demonstrate TCC Engine recovery independently of Trigora Cloud.

    trigora dev drives the Rust host:

    trigora
    → trigora-local
    → tcc-host-sqlite
    → TCC Engine
    HostWhere it runsStore
    Rusttcc-host-sqlite, driven by trigora-localSQLite (.trigora/state.db)
    NodeNode SQLite host in the tcc-engine repositorySQLite
    PythonPython SQLite host in the tcc-engine repositorySQLite, host-side

    tcc-host-sqlite is the persistent Rust host used by trigora dev and passes host conformance v1. The Node and Python hosts are repository-based conformance references rather than published packages.

    All three hosts are validated against the same semantic suite without requiring a shared SQL schema. Conformance tests terminate the process at defined crash points and resume from the durable store. Continuations contain logical Program state rather than a process heap or WASM memory image.

    Killing trigora dev during a wait, then starting it again, restores the wait from .trigora/state.db. That is the local version of the quickstart loop.

    Trigora Cloud uses its own persistence implementation rather than these SQLite stores, while implementing the same host protocol. See Custom host.