SYSE.45:5.1 - A converter, a learned interpretation and two failed withdrawals
A service accepts an interval in seconds. Target identity, revision and actual effect must be obtained through the current interface. For already structured input duration_ms=12000, a deterministic conversion returns seconds=12. Under the supplied conditions that small controller is adequate and cheaper to construct and qualify than an adapter. Stable recurrence alone supplies no reason to replace it.
Now change the target to interpreting recurring, varied requests such as “take three readings each minute” and “take one reading every twenty seconds.” Both call for seconds=20 under the supplied meanings. The fixed converter still works after a supported structured duration exists, but it does not obtain that interpretation. Compare a phrase-rule parser, retained specialist/guidance support, and an adapter with the same converter, current interface and executor. In this constructed case, representative source examples establish that a small phrase rule leaves many intended forms unsupported; expanding and maintaining it has greater estimated whole-horizon burden than the offered bounded adapter trial, including target qualification, tests and failed-trial fallback. C.11 therefore selects that trial. If those grounds or training access are absent, use the supported parser/guidance way or obtain a worthwhile comparison premise.
Training histories include the request, applicable tool definition, current target/revision and the observations needed for a call. Targets vary phrases, rates, durations and identifiers. Missing-unit or ambiguous requests target clarification. The learner fits the intended interpretation/call, while the executor retains permission, actual-state binding and result checks. Optional semantic preparation and trajectory warm-up address different failures; any later reward must use qualified tool/argument meaning and protected results.
Two held-out failures discriminate what was lost when guidance was reduced. Inspect the candidate’s proposed call before execution; the retained binding checks reject an unsupported call:
| Input and condition | Candidate output and observed defect | Smallest supported repair |
|---|---|---|
duration_ms=12000; the applicable definition still says the argument is seconds, and current target/revision are present | seconds=12000 instead of 12. The stable conversion is wrong despite sufficient inputs. | Retain the small converter or restore guidance; if learning that mapping remains worthwhile, repair its targets and test new values. Another current-state lookup cannot supply the missing transformation. |
The provider changed to a millisecond argument, but the new definition was omitted from the input; the old call uses seconds=12 | The call no longer matches the current interface. Restoring the fresh definition, with the same weights, yields the supported duration_ms=12000 call. | Retain the required interface observation and repair its retrieval/input path. Training on old documentation cannot supply an unobserved future contract. |
Guidance reduction therefore tests a particular stable contribution, not all support. Untouched cases also include ambiguity, unsupported units and restraint after a lost reply. A delayed comparison must record intervening adapter, provider, controller and memory changes before attributing retained benefit.