SYSE.46:5 - Archetypal Grounding
SYSE.46:5.1 - Separate support benefit from the choice to obtain it
In a constructed service-update diagnostic, the optional contribution is documentation lookup; execution, current-state checks and permission remain common. E supplies an applicable procedure premise, R leaves a decisive procedure fact only in the reachable source, and T supplies a sufficient premise while offering an irrelevant source.
| Situation | No optional lookup | Source operation supplied | Agent chooses support under the current rule |
|---|---|---|---|
| E: sufficient applicable premise | Completes correctly. | Completes, with acquisition that adds no premise. | Completes after two redundant lookups. |
| R: decisive premise missing | Returns the missing fact; completion is unsupported. | Binds and performs the source call, uses the fact and completes. | Skips the available call, guesses and fails. |
| T: sufficient premise, irrelevant offered source | Completes correctly. | Rejects the irrelevant return and completes from its premise. | Repeats the irrelevant lookup twice, then completes from the premise. |
The stipulated R trace locates missed assistance selection, because the usable call was skipped. If the call had been chosen with a wrong target, repair invocation instead; if the returned fact disappeared from the next input, repair input preparation; if it remained visible but control sent the task back to retrieval, repair the procedure. E and T reveal unnecessary work despite correct answers. Count required effect verification and a sufficient-result stop as well as calls and completion.
After the selected rule repair, unused matched cases must show E using its supplied premise, R obtaining and using the needed source, and T declining irrelevant acquisition, while keeping the actual-state and at-most-one-effect checks. Fewer calls with a guessed R answer fails. The Reference works the whole repair comparison. This table defines an illustrative diagnostic, not observed effectiveness.
SYSE.46:5.2 - A person’s arithmetic and order information
A person reports the total for six lots. Keep ordinary arithmetic means available while varying optional access to the relevant order document. One card already supplies 347 per lot; another matched task omits the current lot size; a third supplies the needed facts but offers an unrelated order. Supplied-support trials identify which order lookup to perform; the person must still recover the right quantity, calculate and report. In the missing-fact case, no-support work should return the gap, while a useful lookup can supply the fact needed to obtain 2082. In the sufficient case, extra lookup needs a benefit that repays its burden.
Use different matched orders and values, with order/allocation chosen for the claim, so the first exposure does not give away a later answer. Record errors, unnecessary or missed lookup, result use and relevant burden separately. If the person learns during the comparison or becomes fatigued, bound the attribution accordingly. Correct supported arithmetic does not establish later unaided learning; that separate question uses HCD’s tests.
SYSE.46:5.3 - Test the reliance that extends beyond the immediate repair
Consider a constructed record for an agent that kept retrieving an already usable procedure. A controller repair records and consumes the returned premise. The model, tool contracts, persistent memory policy and task criterion stay fixed.
| Occasion and stipulated observation | What the observation can support |
|---|---|
| Initial controller repeats six lookups and exhausts the budget before reading target state. | The configuration fails this task; the trace locates a repeated unconsumed contribution. |
| Revised controller uses one procedure lookup and the required current-state calls, observes the requested effect and supplies a usable report. | Immediate task improvement in the compared conditions; no parameter-learning claim. |
| After the normal restart interval, the same revised configuration and intended support complete an equivalent fresh task. | Persistence across that restart/interval, at the tested reach. |
| A new procedure edition adds a state precondition. The agent obtains it, performs the new required observation and uses it in the task. | Sensitivity to this consequential source change, despite the earlier reduction of repetitive calls. |
The table is an illustrative record, not a deployment report. An actual reliance claim needs its observed inputs and results, chosen repetitions and representative coverage.
If the last row instead returns an old answer without accessing the reachable new source, lower effort accompanies failure. Return the freshness transition to SYSE.47 or the affected memory operation to SYSE.43. If the source is unavailable and the task returns that exact gap, record warranted restraint separately from completion. If the provider changed the model between rows, preserve the observed system results but leave controller-only persistence unqualified.