TraceScript executes substrate governance.

TraceScript is the substrate programming language — every meaningful input becomes a governed signal before it can change durable state. TrustScript secures what may become trusted enterprise state. Application modules enforce believe, say, and do on the same receipt path. Trunk architecture →

Three-layer placement

TraceScript programs substrate state. Substrate is the medium — memory, retrieval, policy, workflow, documents, code, and context. TrustScript gates what may become trusted enterprise state. Domain surfaces run on the same receipt-backed runtime. TrustScript hub → · Products overview →

TraceScript Core

Operators, receipts, replay contracts, artifact ledger — the governance language inside the Coordination OS.

TrustScript

Six surfaces — action firewall, memory integrity, policy, workflow truth, continuity verify, evidence export.

Domain surfaces

SmartPeers, CSD/DENSITY, and TrustScript-governed application whitepapers on the same runtime.

Coordination Intelligence (regime routing, privacy envelopes, organizational intelligence upgrades) is planned as a fourth layer above TrustScript — documented internally, not shipped as public TrustScript product surfaces. Regime and privacy doctrine remain org-intelligence preview only.

Signal → trusted state pipeline

Every meaningful input passes through TraceScript Core evaluation, then TrustScript product surfaces when the signal targets trusted-state formation. Blocked signals preserve substrate integrity; allowed signals emit receipts bound to operator chains for replay and audit export.

raw input
  → GovernedSignal (ingest)
  → TraceScript Core evaluate (operators, enforcement, receipt)
  → TrustScript surface gates (action / memory / policy / workflow / proof)
  → trusted enterprise state  |  blocked / quarantined state
  → continuity verify + evidence export (Surfaces 5–6)
  → domain product branches (SmartPeers, CSD, disclosure, code medium)

Live TrustScript routes include /trustscript/surfaces/*/evaluate, /trustscript/proof/run, and observability views for surface decisions and proof runs. Developer quickstart → · RC1 proof console → · System Architecture v1.0 →

Coordination Intelligence upgrades (planned)

Regime routing, privacy envelopes, and organizational intelligence layers are documented in the Coordination Intelligence upgrades appendix — planned above TrustScript, not shipped as public TrustScript surfaces. Download appendix → · Language foundation → · TrustScript hub →

Governed configuration assembly

The language foundation defines execution as configuration assembly, not bare state mutation. Every signal proposes an extension; the runtime evaluates compatibility, coherence, reachability, trust, replay, and repair before substrate mutation. Full language foundation →

raw input
  → GovernedSignal (ingest)
  → GovernanceDecision (integrity evaluate)
  → Trace + phase / influence boundary
  → ReplayReceipt
  → CoordinationState update
  → product-depth branches (memory / disclosure / action / code)
  → replay verification

Language foundation

Ten foundational documents trace TraceScript from medium-oriented programming through specs v0.1–v0.4.2 and the roadmap to constitutional agents (~21k lines). The RC1 runtime implements the enforcement trunk; the corpus defines the language tree.

Evaluation pipeline

ingest signal
  → resolve region + trace
  → load substrate state
  → evaluate equations + threat
  → run 11-layer enforcement
  → decide (allow / review / quarantine / block)
  → mutate or preserve state
  → emit integrity receipt + bindings

Runtime layers

State physics

Pressure, phase, threat, and coordination modeling before enforcement runs.

Deep enforcement

Authority, policy, coherence, memory, membrane, flux, recovery — inside the transaction.

Decision + receipt

Hard decisions with tamper-evident receipts and bindings to every governance artifact.

Async workers (42)

Calibration, flux regulation, recovery, SLO monitoring, audit export — off the hot path.

Production security

API keys, rate limits, request audit, incidents, backup verification, deployment manifests.

Deployment topology

Browser / product app
  → Supabase Edge Function
  → SUBSTRATE_API_URL (Fly.io Fastify API)
  → Supabase Postgres (substrate schema)
  → Worker process (event queue)

TypeScript monorepo · Zod contracts · OpenAPI from live routes · Docker + k8s manifests · CI proof chain.

Three execution modes

Evaluate synchronously

Integrity decisions in the API path, tenant-scoped transaction.

Prove asynchronously

Workers handle drift, recovery, and evidence export without blocking trust.

Operate in production

Auth, audit, rate limits, and posture views — not bolted on later.