← CSM / 08 · Runtime Semantics, State Machines, Recorders, and an Executable Reference Model

CSM · 08 v0.1 · Executable Runtime Specification 2026-08-27

Runtime Semantics, State Machines, Recorders, and an Executable Reference Model

Converts the theory of Papers 00–07 into a first-version, implementable runtime specification. Defines the machine state (native graph, state map, certificate recorder, debt recorder, frontier, cut sets, obstruction cover, exhaustion, policy, ledger head, version); every theorem-level mutation must go through an atomic transaction. Fixes a three-tier runtime: L0, a canonical append-only event ledger (the source of truth); L1, the natively materialized closure state (must be reconstructible by replay); and L2, purpose-specific views (whose authority never exceeds L1’s). Core safety principle: no certificate path ⇒ no native theorem mutation. States explicitly that the runtime is implementation-agnostic — it makes no difference whether it is realized as an LLM, a theorem prover, a GUI, a web service, or a distributed database; what matters is deterministic semantics, the recorders, the ledger, PCOs, transactions, replay, querying, and consistency testing.

Every theorem-level state mutation must go through an atomic transaction; without a certificate path there is no native theorem mutation; the runtime’s implementation method is immaterial. The flagship item among the paper’s 8 Runtime Nonclaims: it does not claim that completing NS ingestion is equivalent to a Clay proof. Also: it does not claim deterministic replay resolves semantic ambiguity.

Connections

Relationship to the rest of the series, stated as closely as possible in the document's own words, not my interpretation.

Loading…