Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-10-14 19:58:00 UTC · snapshot created 2026-10-14 19:58:38 UTC · last check 2026-10-15 05:30:05 UTC

A.15.8.MS: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 A.15.8.MS 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 C.37.MP 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 configurationCriterion coverage and burdenDisposition
Rename v4 to “FINAL” and leave both files in the folderCheap, 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 linkCovers 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 recommendationsCould 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.

A.15.8.MS:5.1.1 - Configure a Tailoring Aid and Repair Its Failed Check

Extend the constructed calibration setting with a different task: prepare a plan for one named sensor using the permitted choices in the current MethodDescription. This example concerns support for that preparation; it does not report a real calibration or establish its effectiveness. Assume the following domain facts are supplied with the admitted v4 description: the planner may select an approved fixture whose working interval contains the sensor’s required interval, but must retain the prescribed test points, acceptance rule, and unknown-serial stop. The current fixture register already establishes approval and intervals; matching numbers alone would not establish approval. The user’s assignment, permission and required preparation are also assumed independently established for this bounded planning task.

The input is sensor B-17 with a required interval of 0–10 V, description v4, and two current approved fixture entries: F10 covers 0–10 V and F5 covers 0–5 V. The output criterion is a plan naming B-17, the exact v4 edition and a covering fixture, with the unchanged test points, acceptance rule and serial-class stop. Unknown sensor class, absent approval, incompatible units, or an interval not covered by any available fixture must return the specific missing premise before a plan is released for use. This does not authorize actual calibration.

Configure one local planning worksheet to consume those inputs. Its tailoring rule is explicit: establish sensor class and the register’s currentness; check the supplied approval relation and compatible units; require fixture lower bound <= required lower bound and required upper bound <= fixture upper bound; copy the allowed selection into the plan while retaining v4’s fixed operations and stops. Selecting a parameter within these declared options creates a plan for this case; it does not by itself alter reusable Method semantics. If the task needs a new acceptance rule, return to Method design and A.3.1.MV instead of silently editing the template.

In the first constructed planning Work, the worksheet lists both fixtures but checks approval only. The user chooses F5 and obtains a plan labelled ready. The task fails: 5 V does not cover the required upper bound of 10 V. The register and v4 rule are correct, so the repair belongs to the worksheet’s omitted interval check. Add that check before export. In a separate repeat of the same task, F5 is rejected with the uncovered 5–10 V interval, F10 is accepted, and the resulting plan retains the prescribed operations and stops. A further changed-input probe with an unknown serial class stops before fixture selection. These are stipulated Work occurrences in the constructed replay; an actual claim needs its own admitted Work and observations.

The receiving result is bounded: the repaired worksheet supports this permitted plan adaptation under the named edition, register and task conditions. The earlier retrieval result alone supplied none of this evidence. A changed fixture register reopens its coverage and currentness premises; a changed tailoring rule reopens the affected plan construction; a failed repeat returns to the defeated worksheet check. Neither the successful preparation nor the worksheet’s ready label establishes release authority, general user capability, Method fit, or the result of performing the calibration.