
This paper formalizes the architectural separation between pure computation and governed mutation in protocol-governed systems. Building on the execution model defined in Paper 6 [Bachi, 2026f], it specifies the semantic boundary between Capability Transforms (CT_) and Capability Side Effects (CS_). We define purity invariants for transforms, mutation declaration requirements for side effects, ordering guarantees, replay constraints, and mutation surface bounding. This separation is shown to be necessary for deterministic replay, trace completeness, and structural enforceability. This paper does not analyze security implications (Paper 8), execution engine architecture (Paper 6), governance mechanics (Paper 4), or lifecycle economics (Paper 9). Its purpose is definitional: to formalize the world-interaction boundary that enables determinism and auditability guarantees.
Software Engineering, Programming Languages, Software Architecture
Software Engineering, Programming Languages, Software Architecture
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
