---
title: "When the PR Queue Becomes a Firehose"
description: "On why human git patterns don't survive contact with agents, and what has to replace them."
doc_version: "1.0"
last_updated: "2026-05-12"
canonical: "https://modiqo.ai/blog/when-the-pr-queue-becomes-a-firehose.txt"
---

# When the PR Queue Becomes a Firehose

*From the Factory Floor — notes from inside the workshop where rote is being built.*

Git was designed for humans. Every primitive carries the fingerprint of a contributor who sleeps, whose attention is the bottleneck, not their typing speed. Then you point a wizard's hat at the room and every assumption that gave the reviewer leverage disappears.

## What changes when contributors are agents
- No incident memory. No hallway. No gut.
- The reviewer agent is also a stranger — no tacit knowledge of *your* codebase.
- Hundreds of plausible PRs, all green, one of them quietly breaks the invariant.

## The threshold effect
Four strain modes — queue growth, defects missed, thread loss, tacit drift — do not arrive sequentially. They arrive together, the moment you cross some volume threshold.

## Six patterns that mirror agent distribution
1. PR-per-agent-task is the wrong granularity — split along semantic seams.
2. Stacked PRs become the default, produced by the orchestrator.
3. The master reviewer manages the *distribution*, not diffs.
4. Outcome streams (trajectories) become first-class artifacts.
5. The merge queue needs an explicit back-pressure primitive.
6. Tacit knowledge has to be crystallized — in skills, adapters, flows, deterministic paths. The gap rote exists to close.

You don't have to use rote. But you have to build something that performs this function, or the queue eats you alive.

— Chetan