Verified, not just designed.

RC1 is captured evidence — migrations, conformance fixtures, receipt replay, tenant isolation, and TrustScript proof flows you can reproduce locally. Claims on this site point to artifacts, not slides.

What RC1 proves

  • Migration proof — schema applies cleanly
  • Worker proof — queue claim → receipt emission
  • Receipt proof — immutability, replay audit, bindings
  • Tenant isolation — cross-tenant boundaries at API layer
  • Product smoke — 15 product-depth routes
  • Evaluation profiles — lightweight through product_deep on integrity evaluate
  • Module proof ladder — whitepaper ↔ runtime ↔ demo status (below)
  • Production security — API keys, incidents, SLO posture
  • Learning loop proof — outcome → prediction error → calibration → effectiveness via pnpm proof:learning-loop
  • RC2 conformance — 68 golden fixtures (20 RC2 + 16 ISF + 3 LR + TrustScript wedge) + invariants + replay + RL2 + ISF assurance via pnpm test:conformance (CI full + nightly)
  • Substrate physics canon — phase, basis, retrieval, SmartPeers adapter, learning registry v0.2
  • ISF Baseline B — trust zones, blood types, promotion decisions (Sprint 56); Baseline C planned Sprints 57–59

Reproduce locally

pnpm install --frozen-lockfile
docker compose up -d postgres
pnpm db:migrate
pnpm rc1:full
pnpm test:conformance

Hosted verification

export SUBSTRATE_API_URL=https://tracescript-substrate-api.fly.dev
pnpm smoke:remote

View release artifacts on GitHub → · Read validation evidence →

Module proof ladder

Each platform module should have a whitepaper, runtime path, developers demo, and captured proof. See the buyer evaluation checklist for question-to-module mapping.

Module Risk zone Whitepaper Runtime Demo Proof

Substrate physics proof ladder

Physics canon lives in docs/substrate-physics/ with a code alignment map at IMPLEMENTATION_MAP.md. Phase policy, action basis, retrieval envelope, SmartPeers review substrate, and learning registry v0.2 are live in runtime; demos below for SmartPeers + learning effectiveness.

Capability Zone Canon Runtime Demo Proof

TrustScript proof console (Surfaces 5+6)

Unified RC1 flow — operator-bound continuity verify + audit evidence export for a receipt. Use the hosted API when available; Portal observability tab captures authenticated runs.

TrustScript · Surfaces 5+6

Not loaded

API: POST /trustscript/proof/run · Portal proof run →

Physics demos (buyer-visible)

SmartPeers review substrate and the learning-registry effectiveness loop have live runtime paths and conformance proof (SP-001..003, LR-001..003). Use the hosted API when available; otherwise the page shows a captured sample from pnpm proof:learning-loop.

SmartPeers review substrate

Review room → paper artifact → review object → objection graph with phase-regime coupling.

Demo live SP-001..003 conformance · migration 070

Governed path demo (Developers) →

SmartPeers product surface →

Learning registry effectiveness

Closed loop: receipt → outcome → prediction error → calibration proposal → tenant rollup.

Not loaded

API: GET /substrate/learning/effectiveness · fixtures LR-001..003

What makes this different

OthersTraceScript
Log prompts and responsesEmit immutable integrity receipts
Moderate after the factEnforce inside the transaction
One-size-fits-all APIProduct-native depth per surface
“We have RLS somewhere”Tenant-scoped evaluation + audit export
Architecture decksCaptured proof JSON + CI gates