<?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>Working Papers (Historic Archive) on omnibachi</title>
    <link>https://omnibachi.org/papers/working_papers/</link>
    <description>Recent content in Working Papers (Historic Archive) 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, 19 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://omnibachi.org/papers/working_papers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>#01 — Motivation: Why Protocol-Governed Architecture is Inevitable</title>
      <link>https://omnibachi.org/papers/working_papers/motivation-why-pgs-inevitable/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/constitutional-realization-turing-complete/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/layer-concern-constitutional-model/</link>
      <pubDate>Thu, 29 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/governance-and-authoring/</link>
      <pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/protocol-as-law/</link>
      <pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/deterministic-enforcement/</link>
      <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/pure-computation-and-governed-mutation/</link>
      <pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/inversion-of-trust/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/three-dividends/</link>
      <pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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/working_papers/generation-governance-impedance-mismatch/</link>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/working_papers/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>
  </channel>
</rss>
