PGS

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

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 governance mechanics of protocol-governed systems. Building on the structural taxonomy defined in Paper 3 [Bachi, 2026c], it specifies how behavioral law is proposed, validated, ratified, versioned, and amended. ...

In Part 3, we argued that agentic AI needs a constitution, not just guardrails. The core insight: the real enterprise risk is not hallucination — it is ambient authority, the implicit power agent frameworks grant to models without structural boundaries. That post was about why. This one is about how. And we have a concrete protagonist: OpenClaw. OpenClaw: The Agent Enterprises Want OpenClaw is an open-source autonomous AI assistant that is catching fire in the developer community. It runs locally, uses Claude as its reasoning engine, and has capabilities that would have seemed science fiction two years ago: ...

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

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 semantics of protocol artifacts in protocol-governed systems. Building on the structural taxonomy defined in Paper 3 [Bachi, 2026c] and the governance lifecycle established in Paper 4 [Bachi, 2026d], it specifies how behavioral law is represented in ratified protocol artifacts. ...

In Part 4, we showed how a constitutional governance layer sits between an agentic AI system and enterprise infrastructure — catching a $400,000 license misallocation before it happened. The mechanism was structural: undeclared behavior was architecturally impossible. But that example assumed we already understood why such a layer is necessary. This post examines the specific failure mode that makes it urgent: quiet privilege escalation — the structural pattern by which AI agents inherit authority nobody explicitly granted them. ...

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

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

In Part 3, I argued that agentic AI needs a constitution, not just guardrails. In Part 4, I made it concrete — showing how a constitutional governance layer between an agent and enterprise systems could structurally prevent a $400,000 license misallocation. In Part 5, I dissected quiet privilege escalation — the silent accumulation of composite authority that traditional controls were never designed to catch. Those posts defined the problem. They made the case. They laid out the architecture. ...

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