The Last Application · Part V — Technical Appendices
Chapter 18 — Semantic State and Representability
4 min read
This chapter defines semantic closure as a membership condition on evolution, and identifies the product’s internal model with a typed graph. Every later chapter assumes these definitions.
Semantic state
Definition 18.1 (Semantic state). A system carries a semantic state
where:
- is the substrate — the physical and computational machinery that stores bits and runs interpreters (hosts, databases, engines, model APIs).
- is the internal model — a structured description of the product and the aspects of the world the product must know.
- is the representational relation — the correspondence between states of and states of the world, together with the causal paths by which changes in change what does.
is not a single function. It includes typing, linking, rendering, execution, and policy. What matters is that is internal: the system does not need an external manuscript to know what it is.
Evolution and semantic closure
Let be the set of evolution operators available to the system at — every way the product may change: human craft, agent edit, workflow commit, promote, heal, install.
Definition 18.2 (Semantic Closure Criterion). The system is semantically closed at when every admissible evolution lies in the representational capacity of :
Equivalently: there is no admissible change whose meaning exists only outside (in a slide deck, a forked UI tree, an unrecorded chat, or an engineer’s memory). If such a change exists, write for its unrepresentable component; then .
Reading. This is a criterion on product systems, not a theorem of pure mathematics. Semantic closure is not Turing completeness. It is the absence of a silent second description of the product.
The model as a typed graph
For product systems of the kind this book describes, is realized as a finite labeled directed graph.
Definition 18.3 (Product graph).
- is a finite set of objects (nodes).
- is a finite set of links (directed edges), possibly with edge labels drawn from a finite alphabet.
- assigns each object a schema label from a finite schema alphabet .
Definition 18.4 (DataObject). An object is a record
where is a globally unique identifier, is its schema, is a typed payload (a finite key–value structure conforming to the schema), and is the set of outbound link targets in .
Definition 18.5 (Schema). A schema is a signature
where and are finite sets of field names and assigns each field a value type (string, boolean, number, enum, object, array, reference, …). Write when the payload satisfies the signature.
Axiom 18.1 (Identity). is injective. No two live objects share an identifier.
Axiom 18.2 (Typing). For every , .
Axiom 18.3 (Referential integrity). For every link , .
When these axioms hold, is a well-formed product graph. Chapter 19 treats violations as rejected mutations.
Completeness of the product description
Let be the set of product facets the organization treats as first-class: experience structure, process definitions, knowledge, integrations, events, brand, policy, and skills.
Definition 18.6 (Descriptive completeness). is descriptively complete for when there is a surjective assignment
such that every facet is encoded as a (possibly empty) subgraph , and every runtime behavior attributed to is a function of and alone.
If some facet lives only in (hard-coded pages, shadow process engines, chat-only doctrine), descriptive completeness fails and fails for changes to that facet.
Chart of the state
Definition 18.7 (Computational chart). On the open set of well-formed graphs, identify
so that the semantic state for product work is effectively
with the interpreters attached to (renderer, workflow engine, query API, agent tools, policy checker).
This is the sense in which the graph is the source of truth: is , and projections of are not alternative models.
Seven clauses, formalized
| Clause | Formal reading |
|---|---|
| Complete | Descriptive completeness (Def 18.6); |
| Structured | with Axioms 18.1–18.3 |
| Read | Existence of projections and machine readers of |
| Verify | Integrity predicate before commit (Ch 19) |
| Rewrite | Mutations applied by (Ch 19) |
| Under governance | Restriction to admissible operators (Ch 23) |
| While running | Interpreters in read live without a compile step that forks |
The point
Semantic closure is . For this paradigm, is the typed graph . The next chapter defines how moves.