TarskiTarski/ docsJoin the waitlist

Cloud

The managed platform, covering cloud-first development, deploys with receipts, hosted parity and health, provider bindings, and multi-tenant read models.

Tarski Cloud is the default semantic authority for public development. Your files and terminal loop stay local. Protected semantic work (package admission, fixed-point evaluation, provenance construction, deterministic provider execution, and signed evidence) runs in managed Cloud or in an accepted BYOC, enterprise, or entitled full-local authority. The management API is at https://cloud.tarski.run, and Studio is at https://app.tarski.run. The hosted runtime temporarily retains the explicitly legacy https://runtime.cloud.jacqos.io hostname until the separate cell migration lands.

The workflow

tarski cloud login --email you@company.com   # code-only email login
tarski cloud select --project my-project     # fail-closed scope selection
tarski cloud deploy
tarski cloud status
tarski cloud observe --kind example.created --payload '{"id":"example-1"}'
tarski cloud replay-export --output hosted-evidence.json

tarski dev prepares a digest-addressed source bundle, uploads or reuses it, submits admission, and streams backend-owned diagnostics. tarski test and tarski verify keep local ergonomics while the authority produces the evidence. Local output without an authority receipt is labeled preflight or cached and is never reported as a current pass.

Selecting or publishing an existing workspace tuple is a re-selection and does not create a workspace, so repeated verification consumes no extra quota. Sessions record their subject, organization, bound authority, and origin; fixture-born sessions cannot reach managed Cloud.

Deploys you can audit

Every workspace activation pins its runtime contract, package digest, evaluator digest, and activation epoch. Upgrades and rollbacks are explicit operations with receipts, and a platform upgrade never silently reinterprets an existing activation. Deployment configures end-user identity on the runtime before activation promotes, and a rejected configuration fails the whole deployment.

Admission happens before observation. A runtime cell validates that the frozen package loads (ontology, mappers, helpers, standard-library pin, identity compatibility) before it becomes an active hosted evaluator. A package that fails this check is refused at deploy time, before any user event reaches it.

CI delivery with automation credentials

Interactive cloud sessions are for people; CI uses a separately scoped automation credential. From an authenticated operator session, issue one with only the verbs and lineage prefixes the pipeline needs:

tarski cloud automation-token issue \
  --token-id deploy-production \
  --verb deployment:write \
  --verb deployment:read \
  --verb activation:write \
  --verb activation:read \
  --lineage-prefix 'production:' \
  --expires-in-seconds 3600 \
  --json

The plaintext token is returned once. Store it in the CI provider and expose it only to the job as TARSKI_CLOUD_AUTOMATION_TOKEN. Automation tokens never persist in the CLI profile. Operators can list, rotate, and revoke them; runtime and delegated end-user tokens cannot deploy.

A headless pipeline is package-addressed:

tarski cloud deploy --json > deploy.json
# Read package_digest from the typed shadow deployment receipt.
tarski cloud endpoint-smoke --package-digest "$PACKAGE_DIGEST" --json
tarski cloud promote --package-digest "$PACKAGE_DIGEST" --json
tarski cloud status --json

cloud deploy creates or reuses a verified shadow package. It grants no effect authority. endpoint-smoke runs a read-only/effects-suppressed probe against that same package, so it works before an activation exists; cloud observe does not. Promotion refuses an unverified or different digest.

cloud status --json reports the active package digest, evaluator digest, activation epoch, and latest verified package. Promoting the already-active digest returns a typed no-op receipt. Roll back by promoting a previously verified package address:

tarski cloud rollback --package-digest sha256:... --json

Pin the receipt digest between steps. Never “deploy latest” after smoke, because another build could become latest before promotion.

Hosted health reporting

Hosted lineage health reports “observation accepted” separately from “projection committed”. A lineage is committed (lag 0), pending (projected head behind, true lag reported), or trapped (evaluation failed; typed diagnostic; partial progress preserved). The exit-code contract mirrors this: exit 2 means “recorded; do not re-append.”

A trapped lineage never loses data, because the observation log is immutable. To recover, deploy the corrected package as a non-authoritative candidate, prove load and parity, replay the immutable lineage, compare, and promote explicitly. The original trap evidence is retained for audit.

Receipts verify hosted publishes end to end: hosted observation acceptance, hosted export digest capture, and local replay verification of the hosted export. Together they are the recurring proof that hosted state replays locally.

Hosted queries

tarski cloud query executes declared queries against the hosted authority with certified local/hosted digest parity. Parity receipts compare canonical rows, ordering, digests, support witnesses, typed denials, and redaction state before capability discovery reports the operation as available. When hosted queries are unavailable, you get a typed state; Tarski never silently falls back to a local result and presents it as cloud truth.

Provider bindings per environment

tarski.toml stays environment-neutral; provider behavior binds per target:

[targets.test.providers.searchapi]
mode = "deterministic"            # fixtures and CI: no network, no credential

[targets.prod.providers.searchapi]
credential_ref = "SEARCHAPI_KEY"  # hosted production: live managed binding

Deterministic bindings can never satisfy live production provider evidence, and a missing live credential blocks typed before any network I/O.

Multi-tenant read models

To scale across tenants, use one lineage per tenant. Each tenant writes to its own lineage for isolation and write parallelism, and a global read surface composes from authorized projection imports. Each import is a reduct of another lineage’s worldview, admitted by the source projection’s own row policy. A composed read never exposes more than its source allows.

  • Import rows enter composed queries under their canonical relation names with per-import fact identity; live imports record observed lag, and every composed read carries per-import freshness receipts (current, stale_warning, pinned).
  • A projection can declare freshness.block_effects_on_stale = true to gate model-call admission while any live import lags. The gating is recorded with a typed reason.
  • Impossible compositions fail closed at load: a single-writer exclusivity invariant over a multi-source union is rejected with E2811, naming the projection, relation, sources, and invariant.

Tenant isolation guarantees (session-chosen tenancy, collision-resistant record identity, and org-scoped listings) are covered in Identity & tenancy.

Usage and plans

Studio’s Cloud and Billing surfaces show usage meters (observation ingest, effect executions by capability class, storage), plan state, and entitlements. During the current preview, organizations resolve to the built-in free plan; entitlement quotas (such as workspace counts) return typed, audited denials naming the axis and plan state.