Papers

© 2026 Bhash Ganti. All rights reserved. Bhash Ganti (aka Bachi) Contact: bachipeachy@gmail.com Abstract The rapid acceleration of AI-assisted software generation exposes a fundamental limitation in conventional software architecture: behavior is implicitly defined by implementation, while governance operates reactively and at human speed. This mismatch creates a structural gap in which systems can exhibit unauthorized, non-deterministic, and unauditable behavior. Existing approaches — static analysis, runtime guardrails, policy engines — attempt to constrain behavior after code is produced, but cannot guarantee compliance when implementation evolves faster than governance capacity. ...

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 boundary and executes governed behavior without containing any domain knowledge. ...

(c) 2026 Bhash Ganti Bhash Ganti Contact: bachipeachy@gmail.com Purpose: Define the conceptual model for Protocol-Governed Systems, validated through the PGS reference implementation. Audience: Protocol designers, compiler authors, runtime implementers, conformance engineers Abstract Protocol-Governed Systems (PGS) propose a computational architecture in which governance precedes execution. Instead of relying on runtime policies, conventions, or post-hoc validation, PGS defines admissible behavior through governed protocol artifacts that are compiled into deterministic execution structures before runtime begins. ...

Contact: mailto:bachipeachy@gmail.com Preface This paper is part of PGS technical paper series. The paper, Protocol-Governed Systems: Conceptual Model, established the architectural foundations: constitutional governance, the separation of governance from execution, and the four-layer stack that makes governed execution possible. This paper focuses on one component of that stack: the PGS compiler. The compiler is the mechanism that converts governance declarations into a structure that execution can consume. Understanding what the compiler does, what it produces, and what it guarantees is essential to understanding how PGS works. No prior knowledge of compilers is assumed. The paper is written for readers who understand the PGS conceptual model and want to understand how its central promise — governance before execution — is actually delivered. ...

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. Together, those two papers establish that behavior is fully determined before execution begins. This paper focuses on the component that consumes that boundary: the PGS 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. ...

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

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

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

These are the original Protocol-Governed Systems working papers, each published with a DOI. They predate the enhanced PGS compiler and runtime architecture, so some implementation terminology is dated. The current Papers supersede them as the authoritative corpus. They are preserved here for historical reference and for the insight they still offer. Each page renders the readable text; the canonical PDF (with figures) is linked at the top of every paper.