TarskiTarski/ docsJoin the waitlist

Tarski documentation

How to build an expert system on Tarski: write rules and scenarios, connect LLMs as sensors and deciders, and deploy to Tarski Cloud. These docs cover v0.5.9-preview.

Fast paths

Start here

Concepts

Build

The Tarski language

A strict Datalog subset for declaring ontologies, with relations, rules, decisions, invariants, and reserved namespaces that the loader checks to enforce containment.

Mappers & observations

The deterministic boundary where raw events become typed evidence, covering Rhai mappers, pure helpers, and deterministic effect providers.

Entities

One declaration expands into the whole record kit, with versioned latest-wins state, fail-closed conflicts, soft delete with revival, and generated read queries.

Write policies

Admit observations before append with explicit actor, payload, target, metadata, and idempotency bindings.

Scenarios & fixtures

Fixtures pair deterministic observation timelines with exact expected worlds and form the proof model behind tarski verify, blessing, query expectation sidecars, and proof artifacts.

Codegen & portable fixtures

Generate TypeScript contracts from an app package and move canonical observation worlds between clean evaluators.

Effects & reconciliation

How Tarski performs external actions through declared capabilities, admission identity, retry policies, the effect lifecycle, work queues, and explicit reconciliation.

Declared queries

The named, typed, parameterized read surface over your derived worldview, covering authoring, exposure, validation, and the query engine that runs it.

Reactive queries

Keep a declared query's result current without polling, using durable per-query subscriptions, resumable deltas, held streams, and explicit rehydrates.

Workviews, Collectors & modules

Workflow-shaped inspection and acquisition without a workflow engine, using read models, dispatch policy, scenario-driven collection with completion seals, and composable modules.

Scheduling

Standing cron, interval, and one-shot schedules whose exactly-once fires enter the lineage as ordinary observations, so the lineage stays the only source of truth.

Storage

Content-addressed blob storage with backend invariance, quotas, and GC, plus semantic tiering that keeps observation history at object-storage cost.

Plugins & packages

Installable semantic packs for external systems, with designated namespaces, load-checked surface tiers, typed HTTP receipts, and locked package management.

Agents

Platform