Library / Systems Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:00:20 UTC

SYSE.47:5.2 - Repair a fixed-model controller that ignores a usable return

One engineering agent repeatedly retrieves an applicable maintenance procedure until its budget expires. The trace shows that the controller never records the returned rule as supplying the outstanding premise. The engineer can change the external controller, but cannot train the model.

The repair adds per-attempt state and routing. A procedure return includes its source edition and applicability. When it supplies the outstanding rule, the controller marks that premise supplied and places its result in the existing action step’s input. A subsequent identical lookup requires a missing or defeated premise, or a justified refresh. Otherwise the procedure continues to the required current-target observation.

The model endpoint/settings, instruction templates, tool contracts, permissions and persistent memory policy/store stay fixed. Selected prompt inputs change because the controller now passes the usable return forward. This is an execution change, not parameter learning or a new memory policy.

The candidate must still reopen the premise when a new procedure edition changes a precondition. It must also preserve an unresolved effect across a lost reply. Compare ordinary progress, missing information, the changed edition and the interrupted effect under SYSE.46. A successful repair reduces redundant retrieval while preserving necessary fresh access and actual execution. This constructed example specifies observations to obtain; it claims no measured improvement.