<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Work Queue Service on Project Hummingbird</title>
		<link>https://hummingbird-project.io/docs/background/tools/workqueue-service/</link>
		<description>Recent content in Work Queue Service on Project Hummingbird</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://hummingbird-project.io/docs/background/tools/workqueue-service/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Work Queue Service Design</title>
				<link>https://hummingbird-project.io/docs/background/tools/workqueue-service/design/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://hummingbird-project.io/docs/background/tools/workqueue-service/design/</guid>
				<description>&lt;p&gt;Architectural design document for &lt;code&gt;workqueue-service&lt;/code&gt;. Covers the&#xA;reasoning behind every major design choice so that future changes can be&#xA;made safely. For operational usage, see&#xA;&lt;a href=&#34;https://hummingbird-project.io/docs/background/tools/workqueue-service/&#34;&gt;Work Queue Service&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-design-philosophy&#34;&gt;1. Design Philosophy&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#1-design-philosophy&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Four principles shaped the service&amp;rsquo;s architecture:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Security boundary.&lt;/strong&gt; The service sits between untrusted callers (AI&#xA;agents, CI jobs, automation scripts) and trusted write operations (GitLab&#xA;pushes, MR creation). All changes are inspectable structured data, not&#xA;opaque blobs. Path blocklists and action validation run before any&#xA;GitLab write.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Work Queue Service Design Decisions</title>
				<link>https://hummingbird-project.io/docs/background/tools/workqueue-service/design-decisions/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://hummingbird-project.io/docs/background/tools/workqueue-service/design-decisions/</guid>
				<description>&lt;p&gt;Design Decision Registry (DDR) for &lt;code&gt;workqueue-service&lt;/code&gt; — every major design&#xA;choice, the alternatives considered, and why the chosen approach won. For the&#xA;design overview, see&#xA;&lt;a href=&#34;https://hummingbird-project.io/docs/background/tools/workqueue-service/design/&#34;&gt;Work Queue Service Design&lt;/a&gt;. For operational&#xA;usage, see &lt;a href=&#34;https://hummingbird-project.io/docs/background/tools/workqueue-service/&#34;&gt;Work Queue Service&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;ddr-1-phase--dimensions-vs-linear-state-machine&#34;&gt;DDR-1: Phase + dimensions vs linear state machine&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#ddr-1-phase--dimensions-vs-linear-state-machine&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Decision&lt;/strong&gt;: Replace the 12-state linear state machine with a phase +&#xA;dimensions model.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Context&lt;/strong&gt;: The initial design used a single &lt;code&gt;state&lt;/code&gt; column:&#xA;&lt;code&gt;pending → in_progress → created → mr_ci → approved → merged → post_merge_ci → building → releasing → completed&lt;/code&gt;. This broke because&#xA;post-creation concerns (CI, approval, Konflux build) are independent —&#xA;CI can pass before approval, approval can be revoked, force-push resets&#xA;CI but not approval.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
