<?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>Preprints — Under Review on omnibachi</title>
    <link>https://omnibachi.org/papers/preprints/</link>
    <description>Recent content in Preprints — Under Review 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>Tue, 15 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://omnibachi.org/papers/preprints/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Who Authorizes Software Behavior? Governing the AI-Native SDLC</title>
      <link>https://omnibachi.org/papers/preprints/who-authorizes-software-behavior/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/preprints/who-authorizes-software-behavior/</guid>
      <description>&lt;p&gt;&lt;strong&gt;© 2026 Bhash Ganti&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Independent Researcher&lt;/em&gt; — Camas, WA, USA&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;p&gt;&lt;strong&gt;Submitted to:&lt;/strong&gt; IEEE Computer — under review.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;As software projects become increasingly agent-mediated, implicit authorization fails: the lifecycle is gated repeatedly—merge, release, deployment—and those disjoint approvals are assumed to compose, a composition living in reviewers&amp;rsquo; heads that requires producers to be few, known, and sharing tacit context. Agents break all three, and no single point determines what behavior a system is authorized to realize. Authorization must instead be an explicit, independently checkable property established during governed construction and carried in a sealed state that execution realizes but cannot amend. Three tests are reported: a reference implementation assembling seven governed domains under one governance surface; an independent realization built from a frozen specification, claiming only the surfaces it exercised; and mutation testing in which removing two required guards left demonstrations unaffected, while a discriminating mutation of declared routing failed as expected. These address realizability, specification sufficiency, and evidence adequacy, exposing a concrete limitation of conventional evidence.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Human-AI Software Engineering: Autonomy Without Authority</title>
      <link>https://omnibachi.org/papers/preprints/autonomy-without-authority/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/preprints/autonomy-without-authority/</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;(c) 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;Preprint:&lt;/strong&gt; &lt;a href=&#34;https://doi.org/10.5281/zenodo.22650863&#34;&gt;https://doi.org/10.5281/zenodo.22650863&lt;/a&gt; — this page is the frozen rendition of that deposit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Submitted to:&lt;/strong&gt; Springer Automated Software Engineering — under review.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Autonomous agents can now perform substantial portions of the software-engineering lifecycle, yet conventional lifecycles rarely make explicit who authorizes the resulting software: repository write access and human review do not by themselves constitute an authorization decision.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Computing: A Software Development Lifecycle Architecture for Deterministic Declarative Execution and Governed Transformation</title>
      <link>https://omnibachi.org/papers/preprints/lifecycle-architecture/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/preprints/lifecycle-architecture/</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;(c) 2026 Bhash Ganti. All rights reserved. Released under the Apache-2.0 License.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt; · ORCID &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Preprint:&lt;/strong&gt; &lt;a href=&#34;https://doi.org/10.5281/zenodo.22758703&#34;&gt;https://doi.org/10.5281/zenodo.22758703&lt;/a&gt; — this page is the frozen rendition of that deposit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Submitted to:&lt;/strong&gt; Elsevier Journal of Systems and Software — under review.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Software systems are governed across three activities usually treated separately: changing what the system is, constructing an executable representation, and executing it. This separation lets authority migrate between them. Transformation may author behavior, construction may repair incomplete declarations, or a runtime may resolve omissions by inference. Behavior is then determined partly by declarations and partly by the mechanisms that realize them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Computing: Architectural Inversion, Its Consequences, and a Scaling Claim</title>
      <link>https://omnibachi.org/papers/preprints/architectural-inversion/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/preprints/architectural-inversion/</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;(c) 2026 Bhash Ganti. All rights reserved. Released under the Apache-2.0 License.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt; · ORCID &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Preprint:&lt;/strong&gt; &lt;a href=&#34;https://doi.org/10.5281/zenodo.22736531&#34;&gt;https://doi.org/10.5281/zenodo.22736531&lt;/a&gt; — this page is the frozen rendition of that deposit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Submitted to:&lt;/strong&gt; Wiley Software: Practice and Experience — under review.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Conventional software architecture spreads behavioral authority across several sources. Declarations
govern some behavior. Implementation, build tooling and runtime decide the rest. Protocol-Governed
Computing reverses that arrangement. Governed declarations determine authorized behavior, business
process rules included. Construction, implementation and execution realize that determination and add
nothing to it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protocol-Governed Computing: Business Software That Runs on a Domain-Neutral Substrate</title>
      <link>https://omnibachi.org/papers/preprints/domain-neutral-substrate/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://omnibachi.org/papers/preprints/domain-neutral-substrate/</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;(c) 2026 Bhash Ganti. All rights reserved. Released under the Apache-2.0 License.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;mailto:bachipeachy@gmail.com&#34;&gt;bachipeachy@gmail.com&lt;/a&gt; · ORCID &lt;a href=&#34;https://orcid.org/0009-0007-3810-6520&#34;&gt;0009-0007-3810-6520&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Preprint:&lt;/strong&gt; &lt;a href=&#34;https://doi.org/10.5281/zenodo.22779384&#34;&gt;https://doi.org/10.5281/zenodo.22779384&lt;/a&gt; — this page is the frozen rendition of that deposit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Submitted to:&lt;/strong&gt; Oxford University Press, The Computer Journal · manuscript ID COMPJ-2026-09-1249 — under review.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Operating systems admit a new process, virtual machines new bytecode, and database engines a new
query without being rebuilt for it. This paper asks whether governed business domains can likewise
arrive as artifacts that a shared substrate admits and executes without acquiring domain-specific
behavior.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
