TraceScript from the ground up.

Twenty foundational documents trace the full arc — core corpus (docs 0–9) plus an extended v2 corpus (docs 10–19) covering v0.5 constitutional agents, sensitivity-conditioned execution, substrate protection, and expanded runtime specs. The shipped RC1 runtime implements the enforcement trunk. Start with the paradigm essay →

North-star sentence

—

Execution lock

—

Trunk lock (Sprint 33)

—

Sensitivity doctrine

—

Trunk architecture hub → — Governed Signal Kernel, trace lifecycle, recovery, and contradiction substrates (Coordination OS integration).

The paradigm shift

Traditional software treats state as passive storage. TraceScript treats state as a living medium whose accumulated history changes future computation.

Traditional app

—

TraceScript

—

The core primitive is not function(input) → output. It is propagate(signal, medium) → { substrateUpdate, replayReceipt, updatedMedium }. See the paradigm essay (read online) for the nine language primitives (medium, trace, signal, operator, field, governance, receipt, and more).

Three layers

The import analysis splits TraceScript into core language, runtime/stdlib, and domain packages — keeping the trunk clean while Enterprise Security, Code Medium, and Disclosure Firewall branch out.

Language primitives

Version roadmap

Spec evolution from living medium runtime through Code Medium governance. Rows marked RC1 reflect what is deployed today; earlier rows are the design lineage that informs the canonical public whitepaper and application modules.

Version	Name	Core contribution

How this connects to the product

Canonical whitepaper

Governed configuration assembly, obstruction/repair, trusted-state formation — the formal public articulation of the trunk.

Technical whitepaper →

Buyer whitepaper

Trust, say, and do — the executive translation of the same runtime for enterprise buyers.

Enterprise AI Trust Infrastructure →

Application modules

Policy Corpus, Disclosure Firewall, Code Medium, Action Firewall — domain packages on the runtime.

Application whitepapers →

Foundation document corpus

Start with the paradigm essay (doc 0) online, then read the paradigm shift essay (doc 13). Use reading paths to filter by topic — or browse all docs below.

Core corpus — specs and roadmap (download)

Extended v2 corpus — sensitivity, v0.5, protection (download)

Ten additional documents extend the language into sensitivity-conditioned execution, the full v0.5 constitutional layer, substrate protection, field-reactive UI, and expanded v0.1/v0.3 specs. Duplicates from the source batch were deduplicated (kept longest/canonical editions).

Build on the governed path.

The RC1 API implements synchronous enforcement, receipt emission, and replay verification today.

Try the API Production architecture