<?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>Papers on omnibachi</title>
    <link>https://omnibachi.org/papers/</link>
    <description>Recent content in Papers 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>Thu, 26 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://omnibachi.org/papers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Protocol-Governed Systems: A Constitutionally Constrained Architecture for Autonomous and AI-Generated Software</title>
      <link>https://omnibachi.org/papers/pgs-constitutionally-constrained-architecture/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/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: Architecture Inversion Concepts</title>
      <link>https://omnibachi.org/papers/architecture-inversion-concepts/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/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;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. 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: A Conceptual Model</title>
      <link>https://omnibachi.org/papers/conceptual-model/</link>
      <pubDate>Thu, 29 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/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: Compiler Conceptual Model</title>
      <link>https://omnibachi.org/papers/compiler-conceptual-model/</link>
      <pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/compiler-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;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 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 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.&lt;/p&gt;
&lt;p&gt;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 &amp;mdash; governance before execution &amp;mdash; is actually delivered.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Systems: Runtime Conceptual Model</title>
      <link>https://omnibachi.org/papers/runtime-conceptual-model/</link>
      <pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/runtime-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;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>Protocol-Governed Systems: Closed-Loop Governed Evolution</title>
      <link>https://omnibachi.org/papers/change-management-conceptual-model/</link>
      <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/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;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. 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>
    <item>
      <title>PGS Field Manual</title>
      <link>https://omnibachi.org/papers/field-manual/</link>
      <pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/field-manual/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Public Reference Artifact — v0 · Baseline: PGS v0.5.0&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Canonical Repository:&lt;/strong&gt; &lt;a href=&#34;https://github.com/bachipeachy/pgs_workspace&#34;&gt;bachipeachy/pgs_workspace&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Audience:&lt;/strong&gt; Architects · Compiler Engineers · Runtime Engineers · Governance Engineers · AI Coding Agents&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;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.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Intended for:&lt;/strong&gt; system architects, compiler engineers, runtime engineers, governance engineers, AI coding agents operating under human supervision, security reviewers, technical maintainers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
