DecisionAdequacyAverage | Strong rationale and readable ADR produce a high average despite absent method docking. | Remove the average; use weakest triggered coordinates to choose repair. |
ADRCompletenessAsDecisionAdequacy | The record has all headings, so the decision is treated as adequate. | Evaluate PAD relation, method docking, trade-off, source-return, and reopen conditions separately. |
ReviewCommentWithoutRepairPattern | The reviewer says “unclear” or “not enough detail” without a target repair pattern. | Assign the weak coordinate to C.32.PAD, C.32.ADR, A.15, C.30.AD, C.32.ACS, or another exact subject pattern. |
GateByScale | A value of 4 or 5 is treated as approval or certification. | Keep ADA as evaluation; use A.21, A.10, B.3, or governance patterns for gate, evidence, assurance, and enforcement claims. |
NotTriggeredAsConvenience | A difficult coordinate is marked not triggered to close the review. | Require a declared-use reason and receiving-pattern boundary; otherwise score it and repair. |
MethodDockingSkipped | The decision is adequate for architecture discussion but then used to direct developer work. | Re-declare use as developer-work readiness and evaluate method docking, work split, and publication handoff. |
SystemRoleLabelAsEvaluator | A reviewer system-role kind, assignment, or ADA record is treated as the performer of evaluation. | Recover the exact admitted evaluator System through A.13 and let A.15.1 independently admit the dated evaluation Work. Add assignment species, occurrence, and F.6 only when precise assignment-bound attribution is expressly represented. Keep any responsibility relation, result episteme, and operation application separate. |
ContextLabelAsEvaluationScope | A project, domain, or bounded-context label stands in for the evaluation boundary. | Bind the exact U.ClaimScope, selected context slices, scheme and plane, evaluation window, and decision-question input projection. |