Rejected candidates have to count as zeros before a stalled agent shows up at all

The parser in the demo asks one question about each generated pattern: whether it is well-formed ^[10]. On a no, the last good pattern keeps looping and that agent publishes nothing new ^[6]. A metric built from successful publishes alone cannot see this, because a rejection produces no event, so the ratio holds steady while one producer has stopped producing.

The size of the signal depends on how many producers you have. With three agents publishing at the same rate, one dead instrument takes roughly a third off the total ^[20]. A third is a big step in a series with ordinary variance. A fleet with hundreds of producers hands the same guard a much smaller number, so before this design transfers, the thing to check is the variance of your own publish rate at the window length the guard uses.

Reverting one change at a time works here because both of the things that change are runtime objects. An agent's model, parameters and system message are a variation in an AgentControl config; the code around the agent, including the limit its validator enforces, sits behind a boolean flag, and neither needs a restart ^[9]. Anything compiled into the build is outside that set.

There is a coupling that comes with it. The musical vocabulary is not in Shipping Floor at all: personas, gain limits and groove recipes all arrive from LaunchDarkly prompt snippets at runtime ^[7]. For a walkthrough that is a fair simplification. A production copy of this shape needs a cached last-known-good config on the client, because the prompt is now on the serving path.

About eleven loop cycles a minute is about 660 an hour, and near 15,800 a day if it ran continuously ^[19]. LaunchDarkly's own contrast is the pipeline where a person wrote every change, review was the quality system, and a few changes a day could each be read before they shipped ^[22].

The walkthrough is LaunchDarkly's, and the fix runs on LaunchDarkly's flags and configs ^[7][9]. The engineering claim under it is separable and, in my view, correct: gate each artifact on an invariant you can compute, measure the process for drift, and let a change that moves the process be taken back without a person ^[16]. The post's framing is that a factory gates in three places on three different clocks, and only the first is a runtime gate ^[18]. The third is a release control, so it can catch a change every individual gate approved ^[16].