ME.10:5.1 - Minimal One-Task Manual Replay
This small constructed replay shows the cheap branch without claiming field evidence. Assume that the named Method and MethodDescription editions are admitted and that the two retrieval occurrences are independently admitted under A.15.1; an actual use must supply those bases rather than inherit them from the example.
CalibrationEngineer-5 must retrieve the current description of admitted Method M-Calibrate-Sensor-B for planned calibration Work. The pass criterion is: return MD-Calibrate-Sensor-B-v4, its current status, applicability to sensor family B, and the stop for an unknown serial class. The failure criterion is return of another edition or omission of status, applicability, or stop.
This is one receiver and one exact action. Candidate REP-Cal-B-Retrieval-1 is a C.2.1 episteme constituted by the maintained index row. Its exact use claim is that v4 is the current family-B description and carries the unknown-serial stop for this retrieval. It exposes currentness, applicability, the stop, and publication link; it withholds a stable audit digest and makes no capability, permission, authority, Work, or calibration-result claim. The ME.10 task row is the owning domain result for this use and carries the receiving task criterion, observation, and return. That one embedded realization supplies the complete one-result/one-use selection boundary, so the C.37 direct exit applies: no ME.9 profile row and no duplicate standalone C.37 account are created. If a later decision relies on the retrieved content as evidence, its exact A.10 path and disposition must be added for that later use.
The initial shared-folder route contains v3 and v4 but exposes neither currentness nor applicability. In W-ME10-Retrieve-Cal-B-0, the user retrieves v3; the task returns task-fail[wrong-edition] without changing either edition or admitting a capability claim.
| Candidate configuration | Criterion coverage and burden | Disposition |
|---|---|---|
| Rename v4 to “FINAL” and leave both files in the folder | Cheap, but the label supplies no governed currentness relation, applicability, or stop and obscures why v3 remains. | Insufficient for the declared criterion. |
| Add one manually maintained index row naming the Method, v4, currentness basis, family-B applicability, unknown-serial stop, and publication link | Covers every current criterion with one new episteme and no new platform. The folder remains a carrier; the index does not become the Method, publication occurrence, Work, or authority. | Retain as the only currently supported sufficient configuration for this one-task set; this does not exclude the untested portal. |
| Build a search portal with automated recommendations | Could add later functions, but no present criterion requires them and their provider, access, suggestion-use, and authority relations are ungrounded. | Untested and larger than this one-task need; do not claim failure. |
The repair adds only the retained index row and its maintained currentness cue. In W-ME10-Retrieve-Cal-B-1, the same user retrieves v4, sees family-B applicability, and stops on an unknown serial class. The receiving task result is task-pass for this exact retrieval action, so the use-bounded row disposition is select inside the stated v4/family-B window. Return if the source edition, currentness cue, applicability, unknown-serial stop, or task observation changes.
For the bounded set containing only this task, the currently supported set is the singleton containing the index row: the rename route is insufficient by its declared missing features, while the portal remains untested and is not ruled out as logically insufficient. This establishes neither unique sufficiency nor multi-task minimality, Method fit, general user capability, a selected A.22 structure, or worth in another project.
If the maintained index and matching observed retrieval result are already available when this same bounded task is raised, check that the edition, currentness basis, task conditions and acceptable burden still apply, then finish with the adequate route. No portal comparison or new minimality claim is needed. A new audit task, changed stop or defeated currentness cue reopens the affected adequacy question; the next replay shows why.