E.9.DA:5 - Worked slices

Filled ordinary case — an overbroad wording DRR. Exact DRR DRR-ROLE-TRIGGER-03@2 selects this answer for an E.10 amendment and its named consumers: “replace every bare role with system role.” The required use is authoring input for that amendment; the review request supplies the use, and the E.9.DA default floor is 3. Before assigning coordinates, the evaluator checks the wording problem, system-role practice, the strongest meaning-recovery alternative, misuse and recovery cases, and the actual predecessor A.6.5 consumer. A.6.5:1 and A.6.5:4.1 expose the omitted question: does each occurrence denote a local system-role kind, or does it denote a relation-participant meaning, a declaration-local slot, an assignment, or an ordinary non-terminological use? That question changes the selected answer.

The ordinary result is repairBeforeDrafting. The blanket replacement would turn several distinct objects and uses into one term. First repair the DRR so it selects meaning recovery: write system role where the text denotes the local kind, and name an assignment, participant meaning, SlotKind, or ordinary use where that is the actual subject. Reopen when the revised DRR distinguishes those uses, names its true consumers, and the actual-host replay preserves precision and readability. This ordinary result uses the compact branch.

Small reliance-bearing extension. Suppose a named later comparison needs one stable result episteme, E9DA-Result-ROLE-03@1, but no Method, application, or Work identity. The complete result would still cover every coordinate; the following one-row excerpt shows the required grain and the near-floor distinction:

The effective floor is 3, so this row contributes to repairBeforeDrafting; another high coordinate cannot compensate. The result’s bounded search basis names the wording problem, actual host, strongest meaning-recovery alternative, and the omitted question above. No unused Method, application, Work, witness, or evidence-use reference is added.

Adequate multi-locus DRR. The DRR selects the precision-restoration move, assigns positive responsibilities to selected loci, states the first drafting action, carries source payload into examples and conformance, and closes only the alternatives needed to explain the answer. The reviewer can judge it from that content and the actual-host replay. A reliance-bearing evaluation may additionally publish coordinate values and an aggregate result, but the ordinary judgement does not wait for that apparatus.

Architecture-impact DRR. A checked DRR cites diagrams, graphs, dashboards, or architecture notes. Review the exact DRR against the relevant E.9.DA questions: did it settle the architecture or structure claim, structural-view relation, preserved and lost structure, missing-structure return condition or source-use relation, selected loci, and publication boundary? A description locates material; it is neither the architecture, the decision, nor the assessment result. Open exact Method, application, Work, and result identities only when the reliance uses them; do not open one because another is present.