ME.1:5 - Archetypal Grounding — EC-417 Release Focus
In the EC-417 release scenario, eight of twenty releases reopened. The package is commonly called the “release methodology”, so the first proposal is to replace it as one Method.
Three management questions expose different subjects in this scenario:
| Management question | Direct subject and claim | Boundary |
|---|---|---|
| project scheduling | The release WorkPlan states intended integration at D-21, signed evidence at D-8, release at D0, and required people and rig time. | These are intended Work and resource claims; the schedule establishes no performed release Work. |
| recurring checks and approvals | The four identified Methods below supply reusable verification, integration, supplier-approval, and authorization actions; the reconciliation accounts remain candidates. | Keep each Method or account as its own subject; recurrence and co-use establish no composite Method. |
| closure of the pinout-evidence question | The claim to settle is whether the signed pinout and the version used in integration satisfy the release’s evidence condition. | Recover the relevant evidence and acceptance rule; the record itself establishes neither satisfaction nor release authority. |
The status inventory contains four identified Methods: M-HW-Verify, M-SW-Integrate, M-Supplier-Approve, and M-Release-Authorize. It also contains candidate accounts C-Evidence-Reconcile-Internal, C-Evidence-Reconcile-Supplier, and C-AI-Trace-Review. C-EC-Release-v2 is only a proposed-whole account. The PLM, CI, test rig, AI provider, safety capability, and supplier responsibility are support, System, capability, access, or assignment subjects rather than Method candidates by position.
| Focus option | Result |
|---|---|
one Method: C-EC-Release-v2 | rejected because the whole is not identified as a Method |
| established release-Method family | rejected because no governed family membership is supplied |
project-local LG-EC417-ReleaseMethods grouping | retained only as a comparison locator; no family claim |
candidate account: C-AI-Trace-Review | not selected as the current focus because its bounded trace suggestions govern neither evidence reconciliation nor release authority; candidate-account status is preserved |
| relations among the four Methods and two reconciliation accounts | selected because evidence timing, result use, allocation, and authority relations change the release decision |
| test-rig support decision | retained as a rival non-Method return, but current evidence does not make it the sole focus |
The schedule exposes a timing conflict, the reusable accounts expose the checks and guards, and the case question identifies the evidence condition still to settle. These connections support a Method-relation focus without making the three subjects one Work. The first result is therefore a Method-relation focus. It creates no fifth Method and no composite. Reopen to a test-capability focus if two of the next three comparable delays occur while required evidence is complete and the rig is unavailable.