STOPPING CONDITION · 24 MARCH
Written before any run: if the best candidate writes to more than three of the
twelve protected accounts, no agent is built. B met it at exactly three. It survives
by nothing at all, except that the number was written down while nobody was
negotiating with a result.
SHAPE ATHE JUDGE
Decides the holds
Reads the account, decides send or hold, writes the letter. The
demonstration, grown up.
7 / 12holds mishandled
5of them confidently
HOW ITS FAILURE PRESENTSA confident, well-written letter to
the customer. Indistinguishable, on its face, from a correct one.
WITHDRAWN 26 MAR
The holds turn on
signals captured nowhere a system can read. A records problem, not a model
problem; recorded so it cannot be reopened as a capability question.
SHAPE CTHE SORTER
Deterministic filter
Routes by flags and thresholds; the agent drafts whatever gets
through. No model in the deciding path.
7 / 12holds mishandled
0warnings of any kind
HOW ITS FAILURE PRESENTSNothing. Silence. The case sails
through, because the holds are defined by the absence of a flag.
WITHDRAWN 26 MAR
A filter routes
only what someone flagged. It ties A on misses and, unlike A, it cannot improve.
SHAPE BTHE TRIAGER
Drafts, stops on signals
Drafts the routine outreach; stops on anything it cannot resolve
and hands the account over with the reason it stopped.
3 / 12written to
9stops, signal named each time
HOW ITS FAILURE PRESENTSA queue entry naming the signal
that stopped it. The only failure mode of the three that can be supervised.
PROCEEDS · MEMO 2 APR
Becomes
Agent v2. It never decides a hold: it writes to the 220 and hands over the 41
with a reason, which is the entire case for building it.