ME.5:5 - Archetypal Grounding — EC-417 Individual Stops
The EC-417 dossier supplies four identified Methods and several candidate accounts. The bounded use is a safety-relevant release arrangement in which signed evidence must exist before safety closure, confidential supplier geometry must stay outside the AI provider, and decision Work remains with admitted human Systems under separate covering assignments and permission or direct decision-authority relations.
| Subject and prior status | Individual result | ME.5 return |
|---|---|---|
M-HW-Verify, identified Method | accepts the affected change and pinout version; produces a verification result with named rig and hardware capability conditions | qualified for the bounded use |
M-SW-Integrate, identified Method | accepts explicitly versioned provisional or signed pinout evidence; its integration record preserves the exact edition, any provisional uncertainty, and the edition actually used; later signed evidence supersedes a provisional edition only for safety-closure reliance while the earlier use and provisional-to-signed relation remain traceable; software remains reversible until D-1 | qualified under the evidence-version, history, closure-reliance, and reversibility conditions |
M-Supplier-Approve, identified Method | produces signed supplier approval or the explicit missing-approval stop; requires supplier-configuration responsibility and evidence access | qualified under the named access and responsibility conditions |
M-Release-Authorize, identified Method | consumes the safety result and named evidence conditions; admitted human System ReleaseDecider-17 performs W-ReleaseDecision-17 under covering assignment ASG-ReleaseDecision-17 and independently supported direct relation AUTH-ReleaseDecision-17; returns release, withhold, or next-slot authorization | qualified for the bounded Work, assignment, and authority scope; none proves the others |
C-Evidence-Reconcile-Internal, candidate account | eight internal cases support an account in which the versioned provisional edition, uncertainty, and earlier integration use remain traceable through reconciliation to later signed evidence before closure | retained as a candidate account; A.3.1 identification remains open |
C-Evidence-Reconcile-Supplier, candidate account | four supplier-originated cases and one held-out supplier case support a signed-evidence branch | retained as a candidate account; A.3.1 identification remains open |
C-AI-Trace-Review, candidate account | the account specifies a trace-suggestion contribution; TraceReviewer-17 performs the accept/reject Work under ASG-TraceReview-17 and PERM-TraceAcceptReject-17, while the AI provider holds neither | retained as a human-governed candidate account |
The provider-default AI proposal is outside ME.5’s present qualification subjects because no identified Method or candidate Method account has been supplied for it. Independently, implementing the proposal would disclose confidential geometry to the AI provider, and the proposal names no admitted human decision performer, covering assignment, or permission/authority relation. Those failures would block this use even if a candidate account were supplied.
Local schema correspondence A-17 maps signed or explicitly provisional pinout-version fields to the integration bundle and preserves the exact edition and uncertainty used. Five stored bundles support that mapping for the named schema editions. The mapping preserves the provisional basis after later signed evidence becomes the safety-closure basis. This is a local connection result, not whole compatibility.
Two honest stops are now available. A project needing only hardware verification can stop with the qualified M-HW-Verify; no architecture comparison is required. A project investigating supplier reconciliation can stop with the retained C-Evidence-Reconcile-Supplier account and its open A.3.1 question. EC-417 continues to ME.6 only because the combined safety allocation, board timing, evidence routing, and recovery burden differ among whole alternatives.