The Last Application · Part V — Technical Appendices
Chapter 19 — Graph Dynamics and Integrity
3 min read
Chapter 18 fixed as the model. This chapter defines change: proposals, integrity, commit, events, and projections.
Mutations
Definition 19.1 (Mutation). A mutation is a finite triple
where is a set of objects to create, a set of payload updates (and optional link rewrites), and a set of identifiers to delete.
Write for the number of affected objects. The empty mutation is .
Definition 19.2 (Application). Given well-formed and , the raw application is the graph obtained by inserting , applying , and removing (and all edges incident to deleted nodes). Raw application need not preserve Axioms 18.1–18.3.
Integrity
Definition 19.3 (Integrity predicate). An integrity predicate is a boolean
is admissible at when .
Definition 19.4 (Four integrity classes). Decompose
where, writing :
- Structural — has no forbidden cycles or orphan components relative to the structural rules of (for example: every page reachable from an experience root; no component parenting cycles).
- Typing — for every , .
- Referential — every edge target in exists in .
- Semantic — all declared domain invariants and policy constraints hold (quality gates, brand rules, environment policy, constitutional flags).
Ideal. Commit only when .
Runtime approximation. A deployed system may evaluate (for example typing plus soft referential checks) and treat some failures as warnings rather than hard rejects. The mathematics of the paradigm remains the full ; is an implementation gap to close, not a different theory (same claim in Chapter 21).
The transition
Definition 19.5 (Gated transition). The commit map is
Definition 19.6 (Action pipeline). An action (craft step, workflow step, API mutation, heal) induces a proposal . The full pipeline is
Mnemonic: execute → propose → validate → commit.
Proposition 19.1 (Closure under gated transition). If satisfies Axioms 18.1–18.3 and includes at least , then satisfies the same axioms whenever .
Proof sketch. Typing and referential classes are exactly Axioms 18.2–18.3 on ; structural class restores well-formed reachability; identity injectivity is preserved if creates mint fresh ids and updates do not rebind .
Events
Definition 19.7 (Event). An event is an object with schema in the event family, recording a transition:
with timestamp and a payload sufficient to audit (or a redacted digest).
Ideal. Every successful commit emits at least one event. Incomplete emit paths are holes in organizational memory — that cannot see its own past.
Definition 19.8 (Issue). An issue is a judgment object opened by a workflow or gate, distinct from a raw event: events say what happened; issues say what must be resolved.
Projections
Definition 19.9 (Projection). A projection is a map
computable from (and configuration in ) alone. Examples: Experience HTML, GraphQL responses, IDE page trees, Assistant retrieval contexts, brand CSS variables.
Axiom 19.1 (Disposable views). If is lost, it is regenerable from . No projection is a second source of truth. Editing without updating is exactly .
Operators and admissibility
Definition 19.10 (Operator). An operator is a (possibly nondeterministic) map that, given and a context (user, run, environment), produces a proposal .
Governance (Chapter 23) restricts operators to an admissible set . Semantic closure under governance is
The point
moves only by gated . Integrity is four predicates. Projections read; they do not author. The next chapter specializes operators to workflows — BPM-class process and agentic orchestration — as mathematical objects on the same graph.