Releases

An asynchronous `Command` like process launcher that uses `bwrap` or `sandbox-exec` for controlled sandbox process execution.

Browser bindings for comply, the REUSE compliance tool

REUSE Specification compliance tool and library: lint, annotate, and fix SPDX license headers

GraphForge Graph IR → DataFusion relational lowering

Executor interfaces and default executor for Oneliner

IREE executable library ABI bindingsby Oneliner

GraphForge DataFusion integration, optimizer rules, and custom plan nodes

Compile alizarin-governed data into the Rós Madair DuckDB+Parquet substrate (tile-row + edge Parquet, concept catalog, manifest)

Interactive git helper

GraphForge StorageProvider trait and Parquet backend

GraphForge Graph IR — semantic, graph-native, semver-versioned

GraphForge runtime-loadable ontology model, validation, and migration

GraphForge lineage and confidence models

Immutable GraphForge knowledge and epistemic record domains

Collection of reusable Odra modules.

GraphForge AST — syntax-faithful, span-rich parse tree

Rust-native canary tokens and honeytokens for early detection of suspicious access to secrets and configuration.

GraphForge core types and traits

A HUB75 LED matrix driver for RP2040 and RP2350 (Pimoroni Interstate 75 W)

Tatara domain wrapping 1 CRD(s).

A reverse proxy server with built-in WebUI, supporting TCP/UDP/HTTP/TLS/WebSocket.

Edge-of-differences rollout planner. Diff two `tatara-env::Env` snapshots into a typed plan describing exactly what's added / removed / changed / unchanged. The synthesizer + FluxCD apply only the delta — no churn for resources that didn't move, no unnecessary restarts, no reapply storms.

tatara — umbrella CLI: fmt, lint, run, test, deploy. Drives feira for static checks, tatara-script for execution, wasm-platform for deploy.

Env → IaC-platform-shaped manifests. The RENDER phase (THEORY §IV.3) of the eight-phase convergence loop. Each `Backend` impl is a morphism from the typescape (typed Rust resources in `tatara-env::Env`) to a target's native shape (Kubernetes CR YAML, Helm template, Terraform JSON, Pangea Ruby DSL). Adding a backend inherits every existing proof — proofs attach to the typescape types, not to the rendering code (THEORY §III.2).

tatara-lisp-lint — typed, pluggable rule engine that lints .tlisp source against semantic Rules over the real tatara-lisp AST (read_spanned). Each rule is one trait impl; the first, GitMutationResultDiscarded, makes the auto-release silent-failure class (a discarded exec-check/exec-capture git mutation) mechanically un-reintroducible. Exposed via `tatara-script lint`.

tatara-script — standalone interpreter that makes tatara-lisp a full scripting language for nix-run apps. Wraps tatara-lisp-eval with a scripting-oriented stdlib (http, json, yaml, sops, file I/O, env, sha256, string ops) so a .tlisp file can replace a bash script one-for-one.

tatara-keywords — the tatara-lisp keyword namespace, checked. Scans a source tree for `#[tatara(keyword = "…")]` declarations, refuses two different types claiming one keyword, and checks a tree against a dated reservation ledger so a keyword taken in another repo cannot be silently re-taken here. `register()` can only see collisions inside one linked process; this sees them across a tree.

Typed environments — compose N tatara-domain resources into one validated stack snapshot. Every catalog domain (gateway-api, cilium, prometheus-operator, ebpf, …) plugs in via its `register()` and the env collects every (def<keyword> …) form into a typed graph the synthesizer / FluxCD / tameshi pipeline can consume.

Catalog browser — turn the registered tatara domains' compile + render + doc metadata into a stable Markdown index. The IDE / web view / `tatara doc` CLI all consume the same shape.

Tatara domain wrapping 1 CRD(s).