<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Foundations on omnibachi</title>
    <link>https://omnibachi.org/papers/foundations/</link>
    <description>Recent content in Foundations on omnibachi</description>
    <image>
      <title>omnibachi</title>
      <url>https://omnibachi.org/og-default.png</url>
      <link>https://omnibachi.org/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 22 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://omnibachi.org/papers/foundations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Protocol-Governed Computing: An Architecture for Deterministic Declarative Execution</title>
      <link>https://omnibachi.org/papers/foundations/architecture-deterministic-declarative-execution/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/architecture-deterministic-declarative-execution/</guid>
      <description>&lt;p&gt;&lt;strong&gt;© 2026 Bhash Ganti&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;
ORCID Profile: &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;https://orcid.org/0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;preface&#34;&gt;Preface&lt;/h2&gt;
&lt;p&gt;This paper describes an architecture for software execution within a fundamentally redesigned software architecture suited to an era in which AI and LLM-based coding assistants can automate software implementation at increasing scale. When implementation can be generated, modified, and regenerated automatically, conventional assumptions about where software behavior resides—and how that behavior remains governed—no longer suffice. This paper presents &lt;strong&gt;Protocol-Governed Computing (PGC)&lt;/strong&gt;, an architecture in which behavioral authority is moved out of implementation and into explicit, validated, executable protocols. It is the first of three companion papers: the second addresses governed transformation, and the third addresses realization of the architecture as a functioning normative platform.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Computing: An Architecture for Closed-Loop Governed Transformation</title>
      <link>https://omnibachi.org/papers/foundations/architecture-closed-loop-governed-transformation/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/architecture-closed-loop-governed-transformation/</guid>
      <description>&lt;p&gt;&lt;strong&gt;© 2026 Bhash Ganti&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;
ORCID Profile: &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;https://orcid.org/0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;preface&#34;&gt;Preface&lt;/h2&gt;
&lt;p&gt;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—in an era in which AI and LLM-based coding assistants can automate software implementation at increasing scale. When implementation can be generated, modified, and regenerated automatically, the question of who governs the act of change becomes the architectural question. It is the second of three companion papers: the first addresses deterministic declarative execution [Ganti, 2026l], and the third addresses realization of the architecture as a functioning normative platform [Ganti, 2026m].&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Computing: Realizing the Normative Platform and Its Governed Transformation</title>
      <link>https://omnibachi.org/papers/foundations/realizing-the-normative-platform/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/realizing-the-normative-platform/</guid>
      <description>&lt;p&gt;© 2026 Bhash Ganti. All rights reserved.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Bhash Ganti (aka Bachi)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;ORCID Profile: &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;https://orcid.org/0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Companion papers&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Part 1 — &lt;em&gt;Protocol-Governed Computing: An Architecture for Deterministic Declarative Execution.&lt;/em&gt;
&lt;a href=&#34;https://doi.org/10.5281/zenodo.21879516&#34;&gt;https://doi.org/10.5281/zenodo.21879516&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Part 2 — &lt;em&gt;Protocol-Governed Computing: An Architecture for Closed-Loop Governed Transformation.&lt;/em&gt;
&lt;a href=&#34;https://doi.org/10.5281/zenodo.21879948&#34;&gt;https://doi.org/10.5281/zenodo.21879948&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Two companion papers establish the architecture of protocol-governed computing. One defines
execution as declarative traversal of a compiled protocol; the other defines evolution as the
governed transformation of one executable baseline into the next. Both state what must be true.
Neither states what it takes to make it true, nor how one would know it had been achieved.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Computing: Field Manual</title>
      <link>https://omnibachi.org/papers/foundations/field-manual/</link>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/field-manual/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Author:&lt;/strong&gt; Bhash Ganti (aka Bachi)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;© 2026 Bhash Ganti. All rights reserved. Released under the Apache-2.0 License.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Audience:&lt;/strong&gt; architects · compiler engineers · runtime engineers · governance engineers · AI coding
agents under human supervision&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;what-this-manual-is&#34;&gt;What this manual is&lt;/h2&gt;
&lt;p&gt;A high-density restoration artifact. Its purpose is to rebuild the correct mental model of
Protocol-Governed Computing in under thirty minutes — not to teach it, not to document code, not to
walk a codebase.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: Architecture Inversion Concepts</title>
      <link>https://omnibachi.org/papers/foundations/architecture-inversion-concepts-v1/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/architecture-inversion-concepts-v1/</guid>
      <description>&lt;p&gt;&lt;strong&gt;(c) 2026 Bhash Ganti&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;mailto:bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;ORCID Profile: &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;https://orcid.org/0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Revision v1.&lt;/strong&gt; Two changes, neither altering a claim of the paper. The preface was
reframed so the paper reads as an entry point rather than as the fourth of a series, which is
the role it now serves. A note on the change of name from Protocol-Governed Systems to
Protocol-Governed Computing was added. The fifteen inversions and their development are
unchanged from v0.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: A Conceptual Model</title>
      <link>https://omnibachi.org/papers/foundations/conceptual-model/</link>
      <pubDate>Thu, 29 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/conceptual-model/</guid>
      <description>&lt;p&gt;(c) 2026 Bhash Ganti&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Bhash Ganti&lt;/em&gt; Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Define the conceptual model for Protocol-Governed Systems,
validated through the PGS reference implementation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Audience:&lt;/strong&gt; Protocol designers, compiler authors, runtime
implementers, conformance engineers&lt;/p&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: A Constitutionally Constrained Architecture for Autonomous and AI-Generated Software</title>
      <link>https://omnibachi.org/papers/foundations/pgs-constitutionally-constrained-architecture/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/pgs-constitutionally-constrained-architecture/</guid>
      <description>&lt;p&gt;© 2026 Bhash Ganti. All rights reserved.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Bhash Ganti (aka Bachi)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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 &lt;strong&gt;unauthorized, non-deterministic, and
unauditable behavior.&lt;/strong&gt; Existing approaches &amp;mdash; static analysis, runtime
guardrails, policy engines &amp;mdash; attempt to constrain behavior after code
is produced, but cannot guarantee compliance when implementation evolves
faster than governance capacity.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: Compiler Conceptual Model</title>
      <link>https://omnibachi.org/papers/foundations/compiler-conceptual-model/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/compiler-conceptual-model/</guid>
      <description>&lt;p&gt;&lt;strong&gt;(c) 2026 Bhash Ganti&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;mailto:bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;ORCID Profile: &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;https://orcid.org/0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Revision v1.&lt;/strong&gt; Two changes, neither altering a claim of the paper. A forward reference to
&amp;ldquo;Paper 6 in this series&amp;rdquo; was repointed: the authoring pipeline it promised is now developed in
&lt;em&gt;An Architecture for Closed-Loop Governed Transformation&lt;/em&gt;, which supersedes the earlier
treatment of governed change. A note on the change of name from Protocol-Governed Systems to
Protocol-Governed Computing was added. The compiler model itself is unchanged from v0.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: Runtime Conceptual Model</title>
      <link>https://omnibachi.org/papers/foundations/runtime-conceptual-model/</link>
      <pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/runtime-conceptual-model/</guid>
      <description>&lt;p&gt;&lt;strong&gt;(c) 2026 Bhash Ganti&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;mailto:bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;ORCID Profile: &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;https://orcid.org/0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;preface&#34;&gt;Preface&lt;/h2&gt;
&lt;p&gt;This paper is part of the PGS technical paper series. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20300611&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Conceptual Model&lt;/em&gt;&lt;/a&gt; established the architectural foundations: constitutional governance, the four-layer stack, and the separation of governance from execution. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20471804&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Compiler Conceptual Model&lt;/em&gt;&lt;/a&gt; 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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#01 — Motivation: Why Protocol-Governed Architecture is Inevitable</title>
      <link>https://omnibachi.org/papers/foundations/motivation-why-pgs-inevitable/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/motivation-why-pgs-inevitable/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_1_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Categories:&lt;/strong&gt; Software Engineering (cs.SE), Programming Languages
(cs.PL), Software Architecture&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Keywords:&lt;/strong&gt; software architecture, declarative systems, deterministic
execution, protocol governance, AI-generated code, auditability,
separation of concerns, constitutional primitives, architectural layers,
behavioral concerns&lt;/p&gt;</description>
    </item>
    <item>
      <title>#02 — A Constitutional Realization of Turing-Complete Systems</title>
      <link>https://omnibachi.org/papers/foundations/constitutional-realization-turing-complete/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/constitutional-realization-turing-complete/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_2_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Categories:&lt;/strong&gt; Software Engineering (cs.SE), Programming Languages
(cs.PL), Computational Complexity (cs.CC)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Keywords:&lt;/strong&gt; Turing completeness, universal computation, protocol
governance, declarative systems, constitutional architecture,
deterministic execution, auditability, AI-era software&lt;/p&gt;
&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;h2 id=&#34;motivation-why-turing-completeness-is-no-longer-enough&#34;&gt;Motivation: Why Turing Completeness Is No Longer Enough&lt;/h2&gt;
&lt;p&gt;The theory of computation has long celebrated Turing completeness as the
definitive measure of computational power. A system is deemed “complete”
if it can simulate any Turing machine—if it can compute any function
that is computable in principle . This criterion, established nearly a
century ago, remains the benchmark against which programming languages,
virtual machines, and computational models are evaluated.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#03 — The Layer-Concern Constitutional Model: A Formal Structural Taxonomy</title>
      <link>https://omnibachi.org/papers/foundations/layer-concern-constitutional-model/</link>
      <pubDate>Thu, 29 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/layer-concern-constitutional-model/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_3_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;This paper formalizes the structural core of protocol-governed systems through a constitutional taxonomy based on two orthogonal primitives: &lt;strong&gt;layers&lt;/strong&gt; and &lt;strong&gt;concerns&lt;/strong&gt;. Prior work established the separation between behavioral specification and execution mechanics [Bachi, 2026a] and demonstrated that constitutional constraint is compatible with universal computation [Bachi, 2026b]. This paper isolates the structural grammar that makes such governance enforceable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#04 — Governance and Authoring: The Legislative Process of Behavioral Law</title>
      <link>https://omnibachi.org/papers/foundations/governance-and-authoring/</link>
      <pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/governance-and-authoring/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_4_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#05 — Protocol as Law: Behavioral Specification and Versioned Authority</title>
      <link>https://omnibachi.org/papers/foundations/protocol-as-law/</link>
      <pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/protocol-as-law/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_5_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#06 — Deterministic Enforcement: Runtime Binding, Execution, and Trace Conformance</title>
      <link>https://omnibachi.org/papers/foundations/deterministic-enforcement/</link>
      <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/deterministic-enforcement/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_6_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#07 — Pure Computation and Governed Mutation: Capability Transforms and Side Effects</title>
      <link>https://omnibachi.org/papers/foundations/pure-computation-and-governed-mutation/</link>
      <pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/pure-computation-and-governed-mutation/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_7_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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_).&lt;/p&gt;</description>
    </item>
    <item>
      <title>#08 — The Inversion of Trust: Vocabulary-Bounded Security</title>
      <link>https://omnibachi.org/papers/foundations/inversion-of-trust/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/inversion-of-trust/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_8_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#09 — The Three Dividends: Governance, Protocol, and Architecture Economics</title>
      <link>https://omnibachi.org/papers/foundations/three-dividends/</link>
      <pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/three-dividends/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_9_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>#10 — The Generation-Governance Impedance Mismatch: PGS in the AI Era</title>
      <link>https://omnibachi.org/papers/foundations/generation-governance-impedance-mismatch/</link>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/generation-governance-impedance-mismatch/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Historic working paper.&lt;/strong&gt; An early, DOI-published draft preserved for
historical reference. Its implementation terminology predates the current
PGS compiler and runtime architecture and is &lt;strong&gt;superseded by the
&lt;a href=&#34;https://omnibachi.org/papers/&#34;&gt;current Papers&lt;/a&gt;&lt;/strong&gt;. Figures survive only in the canonical PDF below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://omnibachi.org/papers/working_papers/techpaper_10_v0.pdf&#34;&gt;Download PDF (canonical, with figures)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: Architecture Inversion Concepts</title>
      <link>https://omnibachi.org/papers/foundations/architecture-inversion-concepts/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/architecture-inversion-concepts/</guid>
      <description>&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;mailto:bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;preface&#34;&gt;Preface&lt;/h2&gt;
&lt;p&gt;This paper is part of the PGS technical paper series. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20300611&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Conceptual Model&lt;/em&gt;&lt;/a&gt; established the architectural foundations: constitutional governance, the four-layer stack, and the separation of governance from execution. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20471804&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Compiler Conceptual Model&lt;/em&gt;&lt;/a&gt; described how the compiler converts protocol declarations into a governed execution boundary called the Protocol Snapshot. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20478471&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Runtime Conceptual Model&lt;/em&gt;&lt;/a&gt; described how the runtime consumes that boundary and executes governed behavior without containing any domain knowledge.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: Closed-Loop Governed Evolution</title>
      <link>https://omnibachi.org/papers/foundations/change-management-conceptual-model/</link>
      <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/foundations/change-management-conceptual-model/</guid>
      <description>&lt;p&gt;Contact: &lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;mailto:bachipeachy@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;preface&#34;&gt;Preface&lt;/h2&gt;
&lt;p&gt;This paper is part of the PGS technical paper series. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20300611&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Conceptual Model&lt;/em&gt;&lt;/a&gt; established the architectural foundations: constitutional governance, the four-layer stack, and the separation of governance from execution. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20471804&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Compiler Conceptual Model&lt;/em&gt;&lt;/a&gt; described how the compiler converts protocol declarations into a governed execution boundary called the Protocol Snapshot. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20478471&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Runtime Conceptual Model&lt;/em&gt;&lt;/a&gt; described how the runtime consumes that snapshot and executes workflow instances without any domain knowledge. The paper &lt;a href=&#34;https://doi.org/10.5281/zenodo.20497732&#34;&gt;&lt;em&gt;Protocol-Governed Systems: Architecture Inversion Concepts&lt;/em&gt;&lt;/a&gt; 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.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
