Paper

Historic working paper. An early, DOI-published draft preserved for historical reference. Its implementation terminology predates the current PGS compiler and runtime architecture and is superseded by the current Papers. Figures survive only in the canonical PDF below. Download PDF (canonical, with figures) Contact: bachipeachy@gmail.com Abstract This paper formalizes the execution mechanics of protocol-governed systems. Building on the protocol specification model defined in Paper 5 [Bachi, 2026e], it specifies how ratified behavioral law is deterministically enforced at runtime. ...

Contact: mailto:bachipeachy@gmail.com Preface This paper is part of the PGS technical paper series. The paper Protocol-Governed Systems: Conceptual Model established the architectural foundations: constitutional governance, the four-layer stack, and the separation of governance from execution. The paper Protocol-Governed Systems: Compiler Conceptual Model described how the compiler converts protocol declarations into a governed execution boundary called the Protocol Snapshot. The paper Protocol-Governed Systems: Runtime Conceptual Model described how the runtime consumes that snapshot and executes workflow instances without any domain knowledge. The paper Protocol-Governed Systems: Architecture Inversion Concepts established why inverting the traditional relationship between specification and implementation is a structural requirement, not a design preference. Together, those four papers establish that behavior is fully determined before execution begins and that the protocol is the sole source of behavioral truth. ...

Historic working paper. An early, DOI-published draft preserved for historical reference. Its implementation terminology predates the current PGS compiler and runtime architecture and is superseded by the current Papers. Figures survive only in the canonical PDF below. Download PDF (canonical, with figures) Contact: bachipeachy@gmail.com Abstract 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_). ...

Status: Public Reference Artifact — v2 · Baseline: PGS v0.8.0 · revised for the full change-management lifecycle (Authoring → Construction → Admission → Execution Validation → Promotion), the unified pgs_change CLI, and the Governance-Impact / Promotion≠Adoption result (§4). The v0 edition is the published DOI record. Canonical Repository: bachipeachy/pgs_workspace Audience: Architects · Compiler Engineers · Runtime Engineers · Governance Engineers · AI Coding Agents What This Manual Is This is a high-density architectural restoration artifact. Its purpose is to restore the correct architectural mental model of Protocol-Governed Systems in under 30 minutes — not to teach, not to document implementation, not to walk code. ...

Historic working paper. An early, DOI-published draft preserved for historical reference. Its implementation terminology predates the current PGS compiler and runtime architecture and is superseded by the current Papers. Figures survive only in the canonical PDF below. Download PDF (canonical, with figures) Contact: bachipeachy@gmail.com Abstract This paper analyzes the security properties that emerge structurally from protocol-governed architecture. Building on the deterministic enforcement model (Paper 6) [Bachi, 2026f] and the computation-mutation separation (Paper 7) [Bachi, 2026g], we demonstrate that protocol governance inverts conventional trust assumptions. ...

Contact: bachipeachy@gmail.com Preface Software changes continuously, yet software engineering has traditionally treated construction, execution, and evolution as largely separate concerns. This paper presents an architecture for software evolution—how running software changes over time while remaining governed, verifiable, and executable. Most of what follows can be read without any prior knowledge of Protocol-Governed Systems (PGS). The architecture is general. It concerns the relationship between a business problem and the running software that addresses it, and that relationship is the same whether or not one has encountered PGS before. A reader interested in software architecture—and skeptical of any particular platform—is exactly the reader this paper is written for. ...

Historic working paper. An early, DOI-published draft preserved for historical reference. Its implementation terminology predates the current PGS compiler and runtime architecture and is superseded by the current Papers. Figures survive only in the canonical PDF below. Download PDF (canonical, with figures) Contact: bachipeachy@gmail.com Abstract This paper analyzes the lifecycle, complexity, and implementation economics of protocol-governed architecture. Building on the structural taxonomy (Paper 3) [Bachi, 2026c], governance mechanics (Paper 4) [Bachi, 2026d], deterministic enforcement (Paper 6) [Bachi, 2026f], and mutation bounding (Paper 7) [Bachi, 2026g], we model how constitutional separation affects long-term system evolution, incremental domain implementation cost, and human cognitive scaling. ...

Contact: bachipeachy@gmail.com Preface This paper describes an architecture for software execution. Most of what follows can be read without any prior knowledge of Protocol-Governed Systems. The architecture is general. It concerns the relationship between a description of behavior and the machine that carries that behavior out, and that relationship is the same whether or not one has ever heard of PGS. A reader interested in software architecture, and skeptical of any particular runtime, is exactly the reader this paper is written for. ...

Historic working paper. An early, DOI-published draft preserved for historical reference. Its implementation terminology predates the current PGS compiler and runtime architecture and is superseded by the current Papers. Figures survive only in the canonical PDF below. Download PDF (canonical, with figures) Contact: bachipeachy@gmail.com Abstract The increasing adoption of generative artificial intelligence (AI) in software development introduces a structural asymmetry: implementation generation now occurs at machine speed, while behavioral governance remains constrained by institutional deliberation. These processes are not merely mismatched in velocity; they are orthogonal in function. Generation produces executable artifacts. Governance establishes permissible behavior. ...