Hey, I run a few small software factories on Claude Code, one per product. Each has a pm agent that files tickets, starts coder sessions and merges, and a GENESIS.md that says what the product is for and what it won't do. Yesterday two of these factories talked to each other, and it went wrong in a way I learned from.
The two products: a notes app that keeps everything on the device and syncs through a server that can't read the notes, and the open-source local-first database underneath it, which keeps a full copy on every device and syncs encrypted changes through a relay. The notes app is the database's first user. Its pm compared what the app needs with what the database ships and sent the database's pm seven gaps, each marked "Blocks: …", with "please triage them in your tracker". Fifteen minutes later the database pm had filed twelve tickets from that one app. I approved an order of work, and four sessions started. Under two hours in, a session began on "a documented bulk import of ~81k operations", and that's when I asked why an importer sits with the database at all; mapping your own data, dry runs and resuming are the app's job. One RFC draft, for deleting a synced space, even contradicted a principle in GENESIS (history is archived, never lost). The draft noticed, as one open question among six, after the work was done.
The database pm's own reading afterwards: it took the requester's wording as the work, GENESIS was something it checked in PR review and not at intake, and my "go" on an order of work read to it as a "go" on the scope.
That's the real miss. A pm's job is to balance three things: the idea of the product, its strategy, and what the market needs. A wish from one user is one input to that balance. Our database pm skipped the balancing and went straight to delivery.
What I changed: a request from another project, a user or another session isn't a ticket yet. The pm first names the general question behind it (here: does the engine survive large bursts of writes?) and the part of GENESIS it serves. Only then does it become work; otherwise it comes to me as "should we do this at all?", and nothing gets built that only one app needs. The asking side changed too: sort app-only wishes out before sending, bring a measurement instead of a wish, and ask the other pm to weigh the list rather than triage it.
The generic measurement that replaced the importer then found two limits every app would hit: a write above 16 MiB silently never left the device, and memory grew 50 to 90 times with the size of a change.
What still worries me: naming "the general question" is judgement, and an agent can generalise a request until the strategy seems to cover it. And every question that now comes to me waits until I answer, which is exactly when an agent is tempted to decide alone.
How do you keep agents from turning someone else's request into work? Do you gate at intake, in review, or by budget, and has a rule like ours held up for you?
I'll collect the answers, test the suggestions in my factories and share what held up back here. Nothing personal from the answers gets used, and nothing gets sold.