SHAPE

SHIFT

Back to homepage

From Worker Finding To Gate

A worker finding is not automatically a fix.

It is a signal.

The useful path is longer: a worker finds a gap, the coordinator checks it, the system turns it into a fixture, the matrix gets a row or stronger expectation, the gate runs, and only then does the rule become part of admission.

That lifecycle is how swarms improve the system without turning review into chaos.

A worker finding becomes valuable when the coordinator turns it into a reviewed gate and feeds it back into the next wave.

The Worker Finds A Gap

A good worker output is not just a patch.

It should say:

what world it saw
what surface it inspected
what gap it found
what evidence supports the finding
what change would catch the gap next time
Worker FindingNeeds coordinator review
Runtime Proof Gap
Surface
CSS cascade runtime proofThe gap belongs to a named merge surface.
Finding
Legacy proof shape can overclaimThe worker found a bypass, not a general failure.
Evidence
Minimal proof object and expected refusalThe finding is reproducible.
Route
Add fail-closed fixture and gateThe next step is a system rule, not a chat summary.
A finding is useful when it names the surface, the gap, the evidence, and the next admission route.

The coordinator should not blindly merge the worker output.

The coordinator should extract the useful claim.

The Coordinator Turns It Into A Case

The next step is usually a focused case:

base source
worker source
head source
candidate output
proof object
expected route
expected admission result

That case should be small enough that future workers and humans can understand it without reading the original transcript.

The transcript found the problem.

The fixture preserves it.

The Gate Makes It Durable

Once the case exists, the gate decides whether the system now knows how to handle it.

A gate turns one reviewed finding into comparable evidence future candidates have to satisfy.

A useful gate does not only say pass or fail.

It says:

which claim was checked
which evidence was required
which artifact was produced
which route happens on failure

That is how one swarm finding becomes part of the admission contract.

The Matrix Learns

The matrix should change when the finding changes the denominator.

Finding To MatrixA Gap Becomes A Row
SurfaceClaimRequired proofCurrent evidenceRoute
RequiredFindingThere is an uncounted riskWorker evidenceReproducible gapCoordinator review
ProvedFixtureThe case has an expected outcomeMinimal source pairPass or fail expectedRun focused gate
RequiredMatrixThe denominator includes the riskNamed row or proof conditionMissing route or fail-closed ruleUpdate admission
ProvedAdmissionFuture candidates obey the ruleGate and decision recordBlocked unsafe proof or admitted bounded proofApply when proved
The worker does not make the system smarter by being right. It makes the system smarter when the finding becomes a durable rule.

The Next Wave Uses It

The point is feedback.

After the gate exists, future agents get better task boundaries:

attach this proof shape
avoid this broad claim
expect this fail-closed route
run this focused gate
report this evidence object

The system becomes easier to parallelize because the review standard is no longer hidden in the coordinator's head.

The Mental Model

A swarm finding should move through four states:

observation
fixture
gate
admission rule

Only the last state changes production behavior.

That is the difference between agent output and system learning.