PGS

] In Part 6, I showed what happened when I built a complete AI governance domain in a day — from specification to deterministic trace — without modifying the execution engine. That post demonstrated something important: Governance can be structural. It can be declared first and executed mechanically. It does not need to be embedded in application code. After publishing it, several readers pointed me toward a parallel thread in the industry: the rise of “Security-First” and “Golden Path” development practices in cloud-native systems. ...

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. ...

In the previous post, “From Serverless Guardrails to Structural Governance,” we examined how the industry is gradually moving governance into structural layers such as infrastructure templates and Golden Paths. Those practices reflect an important realization: Procedural governance does not scale. Checklists, code reviews, and guidelines work only as long as systems remain small and development speed remains human. But modern software development is changing rapidly. Infrastructure is automated. Cloud deployments are instantaneous. And increasingly, AI can generate software at machine speed. ...

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. ...

In the previous post, we explored how Protocol-Governed Systems deliver three structural dividends: governance, protocol reuse, and architectural clarity. Those dividends become even more relevant when we examine how software is now being created. Because today, a new force is reshaping development practice: AI-assisted coding. And with it, a concept that sounds entirely positive — but deserves closer examination: Smart coding. What Is “Smart Coding”? Smart coding is the practice of writing software using: ...

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. ...

) In PGS, governance constructs the track before execution begins. AI Increased the Speed of Implementation. It Did Not Solve Governance. A protocol-first execution architecture for the AI era. Governed by Protocol. Constructed by Compiler. Proven by Trace. In the previous post, we examined how AI-assisted coding creates a double-edged sword: implementation accelerates while governance falls further behind. That gap has a name And it has structural consequences. The Governance Gap Modern software systems are extraordinarily capable at generating behavior. ...