E.9.DA - Evaluate a DRR for Its Declared Authoring Use (Decision-Adequacy CharacteristicSpace)
Status: Stable
E.9.DA:1 - Problem frame
Use E.9.DA to judge whether a particular version of a DRR can support a declared FPF authoring use. The use can be pattern drafting, host amendment, distribution across selected loci, carrying an accepted decision or source use through subsequent authoring, or deciding a scope boundary, split, or architecture hold. Specify the exact C.2.1 episteme identity only when the judgement or a named later reliance needs it. E.9.DA supplies the questions for this object and the reusable meanings of its coordinates.
For other questions, use E.21 to judge an authored pattern version, E.19 to review an FPF pattern edition or bounded subset for admission or refresh, and F.19 to repair wording, with E.10 for cues and unresolved meanings. Use C.16, A.17, A.18, and A.19 for measurement law.
First read the DRR in its declared use and state the working problem, selected answer, practical change, first drafting action, and boundary. If the DRR selects a broad authoring rule, inspect the effect on the actual host by comparing its predecessor and proposed versions before preparing any optional assessment or result materials.
A formally valid DRR can leave the author unable to draft. It may summarize sources without deciding, name neighbors without assigning obligations, hide rejected alternatives, leave trigger words unresolved, or omit the first drafting action.
What is being evaluated? One DRR version for one declared FPF authoring use and qualification window. Identify assessment work, a reusable coordinate result, witnesses, records, status use, assurance, acceptance, and later repair separately when the case involves them.
E.9.DA:2 - Problem
E.9 defines how to decide and record FPF content, the ordinary minimum DRR form, and the exact decision-work, result, and C.2.1 identities to establish when a claim or named reliance needs them. To judge adequacy, examine whether the DRR under review settles enough for the declared downstream use. A reviewer can approve the headings, source volume or prose while the author still has to invent a decision.
Recurring failures:
- The decision question is broad or implicit.
- The selected answer is a summary rather than a decision.
- Alternatives, rejected options, and outside-decision items are not closed.
- Receiving loci are named but not assigned content obligations or non-obligations.
- The selected FPF content architecture is explicit but wrong.
- Source use is copied without saying what changed in the accepted decision.
- Architecture descriptions, views, graphs, packets, or notes are treated as the FPF decision.
- Administrative state becomes adequacy evidence.
- Ordinal adequacy values become repair targets, so the
DRRgains source rows, locus tables, boundary catalogues, or review proof without making either the selected answer or the first drafting action more decisive.
E.9.DA:3 - Forces
| Force | Tension |
|---|---|
| Decision completeness vs concise rationale | A DRR must settle enough to guide drafting while leaving authors to write the final pattern prose. |
| Exactness vs drafting freedom | The DRR fixes selected answers and boundaries; authors still write usable pattern text. |
| Source preservation vs synthesis | Source distinctions matter, but the DRR must state FPF decisions. |
| Multi-locus coordination vs EoC boundary | One decision can affect many patterns while one DRR adequacy claim stays scoped. |
| Architecture selection vs address completion | Every locus can be assigned and still be the wrong split or merge. |
| Affordability vs completeness | Ordinary bounded review uses only the questions needed for the live judgement; an explicitly requested reusable evaluation covers every coordinate with stable values and evidence. |
E.9.DA:4 - Solution
Start with the decision itself. Read the DRR under review in its declared authoring use. Can a practitioner or author recover the working problem, selected answer, practical change, selected loci, first drafting action, and boundary without inventing decisions or decoding avoidable formality? Settle that question before constructing any optional evaluation materials.
The following result suffices for an ordinary bounded review.
- the exact DRR and declared authoring use;
- substantive findings, repaired DRR text, or the unchanged checked DRR when the review is clean;
- the actual predecessor/proposed host evidence when the DRR selects a broad language, ontology, or authoring rule;
- the first drafting action or first repair; and
- the stop or reopen condition.
Plain prose can carry this result. Reserve an assessment-work record, application object, aggregate result episteme, precision-profile record, witness package, or evidence-use package for a use that needs it.
Use the complete coordinate result when a complete reusable evaluation was explicitly requested or when a named later reliance needs stable coordinate values. Materialize the exact characteristic-space configuration, semantic evaluation Method, A.6.1 application, result episteme, witnesses, or evidence-use relations only when that receiving use depends on their identities.
A reusable coordinate result can exist without a semantic Method, A.6.1 application, or dated Work. Decide separately whether the receiving claim uses each identity. A claim may use a Method, or an exact application with its actual bindings, without asserting Work.
If the claim asserts dated U.Work, establish the Method enacted, every precise performer’s A.13 core, and independent A.15.1 Work admission. Add an A.6.1 application only when the claim uses an independently declared operation and its obtaining application. Establish any relation between application and Work separately. Use F.6 only when the result needs precise assignment-bound attribution.
Before assigning coordinates, make one bounded search for an important question the DRR omitted. Inspect the governed problem, the problem-owning practice, current sources, the strongest live alternative, failure and recovery cases, and direct consumers. If an omitted question would change the answer, architecture, source use, consumer obligation, first drafting action, or stop, return it as a substantive finding before completing the coordinate judgement.
In either branch, distinguish the checked DRR, evaluation specification, action or Work, application, result, record, evidence use, status use, authority, and later repair. A compact result can omit identities its receiving use does not need. A claim that asserts Work must still establish the facts required for that Work.
For a broad language or ontology rule, use the predecessor and proposed versions of the actual host to judge DraftingActionability, LexicalAndNamingClosure, and precision restoration. A promise in the DRR, complete table, test in another lane, or invented fact pack cannot establish how a practitioner can use that host. Require both formal precision and plain comprehensibility.
E.9.DA:4.1 - Local names and kind settlement
The names below are for a complete reusable result. Ordinary bounded review can proceed without them. In a reusable result, each name denotes the existing FPF object or reference described in its row. The names confer no authority and require no record on their own.
| Local name | Kind and function |
|---|---|
DRRDecisionAdequacyEvaluation | Compatibility label for the full evaluation package. Resolve it to the values its receiving use needs: configuration, result episteme, and, where applicable, semantic Method, assessment application and bindings, Work admission, witnesses or evidence-use relations, and record. The label does not denote a single kind, Method, application, or Work occurrence. |
DRRDecisionAdequacyCharacteristicSpaceRef | Reference to the exact A.19 U.CharacteristicSpace whose slots are the required E.9.DA coordinates and whose scale bindings use E.9.DA:4.3; not an assessment, result, or record. |
DRRDecisionAdequacyEvaluationSpecRef | Reference to this object-specific A.19.ECS evaluation-specification episteme: applicability, coordinates, scale meanings, evidence/missingness rules, result shape, calibration, status meanings, and reopen conditions. |
DRRVersionRef | Exact C.2.1 DRR episteme version named by value as the checked object. |
DRRDeclaredAuthoringUse | Downstream FPF authoring use for which that exact DRR episteme is assessed. |
DRRSelectedLocusDispositionMap | Map from selected loci named by value to selected content responsibilities, explicit non-responsibilities, sibling decisions, or outside-decision dispositions. |
DRRDecisionAdequacyQualificationWindow | Edition, source set, accepted-decision record, neighbour condition, and currentness window for which the result claim holds. |
DRRRequiredAuthoringUseSource | Review request, accepted decision, or E.22 question frame that fixes the authoring use before evidence is judged. |
DRREffectiveCoordinateFloorMap | E.9.DA’s default floor of 3 for every required coordinate plus any higher floor declared before evaluation, with the default or exact raising source recorded for each value. It is not a score target or permission to narrow the use after seeing values. |
DRRDecisionAdequacyCoordinateSet | The required coordinates in this pattern, each bound to the ordinal scale and its local evidence rule. |
DRRDecisionAdequacyEvaluationConfiguration | Local input tuple binding the exact checked DRR, required use and source, scope, characteristic space/specification, selected-locus map, evidence basis, qualification window, effective floor, and the semantic Method only when a receiving claim uses that identity. It is neither a new U-kind nor performed Work. |
DRRDecisionAdequacyAssessmentWorkRef | Exact dated A.15.1 U.Work, when that identity is needed. Every precise evaluator-performer first has an A.13 core; A.15.1 independently admits the Work from its performance history, semantic evaluation Method, interval, and containing System. The exact assignment species and obtaining occurrence remain part of the A.13 core. F.6 attribution is named separately only when the receiving result also needs precise assignment-bound attribution. |
DRRDecisionAdequacyApplicationRef | Exact A.6.1 application and actual bindings, when a receiving claim uses them. Its inputs and outputs are only the values named by its declaration and obtaining bindings. It implies no Work; relate it to Work only through a separately defined relation whose predicate obtains. |
DRRDecisionAdequacyEvidenceBasis | Checked DRR, source, accepted-decision, selected-locus, architecture, currentness, neighbour, and bounded omitted-question-search loci named by value when the receiving reliance needs them. Establish any evidence-use relation separately. |
DRRCoordinateValueRationales | Required result claims: coordinate, value, adjacent-value rationale, and evidence locus named by value. |
DRRCoordinateLocusRefs | Exact DRR loci cited by result claims. Justify the coordinate value from what the cited content shows. |
DRRSourceUseDischargeMap | Source-use relation, source-currentness, selected payload, rejected payload, and selected locus when a source publication, source pack, or source-use record governs a decision. |
DRRPrecisionRestorationProfile | Compact account of the effect of the DRR’s wording when the requested reusable result or named reliance needs it. State the overall effect, affected coordinates, and checked loci once. Its diagnostic facets are word-use precision, phrase apparatus, repetition-and-distribution, ontic-slot clarity, description-publication-source boundary separation, and pattern-application ontology; report a facet when it distinguishes the result or repair. Name the concrete pattern or relation when needed to resolve the affected meaning, and include a repair or blocker when present. A receiving form that needs an explicit clean disposition may use no-repair with the checked loci. |
DRRKindRestorationCheck | Pre-repair and post-repair check required when a wording, naming, or precision-restoration proposal can change an FPF-governed meaning. Compare the relevant object kind, relation or claim kind, current ontic slot, relation position, use relation, admissible use, and scope. A receiving form may use not triggered, ordinary prose, already satisfied, or blocker with loci when it needs an explicit disposition. |
DRROnticCandidateDisposition | If the DRR selects, rejects, splits, or declines a candidate ontic, this names the candidate EntityOfConcern, sufficiency rationale, rejected alternatives, broad candidate-universe sanity sweep when the claim is broad, slot-relation boundary, description-publication boundary, and selected pattern placement by value. |
CampaignProblemSolutionUnfoldingCheck | Triggered carry-through check for DRRs that create or modify README entries, path-shaped patterns, pattern families, DPF entries, first-practical routes, or constraint-governed unfolding structures. It names admitted problem-side record refs or cues, accepted starting records, current starting structures, entry cues, selected solution architecture, affected unfolding families, loci and concrete-pattern or relation map added or changed, any independently grounded overread that a plausible intended reader could make, and residue that must move from DRR or README into patterns or unfolding structures. |
DRRDecisionAdequacyResultRef | One C.2.1 result episteme whose EntityOfConcern is the exact checked DRR episteme and whose ClaimGraph states the required use and source, window, effective floor and source, coordinate-result claims, bounded omitted-question-search disposition, local status, first drafting action or repair, stop or return, reopen, and any grounded non-use boundary. Method, application, Work, witnesses, records, and later authority use remain separate objects or relations. |
DRRDecisionAdequacyWitnessRefs | Exact comparison, source, trace, case, or locus witnesses cited by result claims; witness presence is neither a value nor an evidence-use relation. |
DRRDecisionAdequacyEvidenceUseRefs | References to the independently established relations that support reliance on result claims. Reuse their adequate source and use grounds. Use A.10 when the source-to-use account is still implicit or its provenance, currentness or bounded reliance must remain replayable. |
DRRDecisionAdequacyRecordRef | Optional C.2.1 record episteme that packages refs to the configuration and the applicable Method, application, Work admission, result, witness, evidence-use, reopen, and grounded non-use values. Status and authority require their direct receiving relations. |
DRRDecisionAdequacyStatus | Local admissible-use value derived noncompensatorily from the required use and source, effective floor, coordinate values, and architecture or split blockers. Any F.10 status use or interpretation by a receiver is a separate relation. |
These names identify local evaluation positions and references. Release or review status, project evidence, gate results, assurance, work, publication, and pattern-quality values are separate from those positions and references. Establish each on its own grounds.
E.9.DA:4.2 - Optional exact evaluation application, Work, result, and record
DRRDecisionAdequacyEvaluationConfiguration:
DRRVersionRef: <exact C.2.1 DRR episteme>
DRRDeclaredAuthoringUse: <drafting | amendment | distribution | source-use carry-through | accepted-decision carry-through | split or hold decision>
RequiredAuthoringUseSource: <review request | accepted decision | E.22 question frame>
ClaimScopeRef: <exact U.ClaimScope>
DRRSelectedLocusDispositionMap: <locus -> selected responsibility, explicit non-responsibility, sibling decision, or outside-decision disposition>
DRRDecisionAdequacyQualificationWindow: <source, edition, neighbour, currentness window>
EffectiveCoordinateFloorMap: <default every required coordinate -> 3; any higher floor declared before evaluation;
source for each value: E.9.DA default | exact raising source>
DRRDecisionAdequacyCharacteristicSpaceRef: <exact A.19 space>
DRRDecisionAdequacyEvaluationSpecRef: <this E.9.DA specification edition>
SemanticEvaluationMethodRef?: <exact U.Method; include only when the receiving claim uses its identity;
required when AssessmentWorkAdmission is present>
DRRDecisionAdequacyEvidenceBasis: <checked loci and explicitly missing or unchecked loci;
for a reusable result, include the bounded omitted-question search basis>
DRRDecisionAdequacyAssessmentApplication?:
EvaluationConfigurationRef:
A6_1ApplicationAndBindingRefs: <exact application, actual checked-object and configuration inputs,
coordinate-result outputs, and aggregate-result output used by this application>
WorkApplicationRelationRef?: <include only when a separately defined relation between this
application and admitted Work is current and its predicate obtains>
ReturnedCoordinateResultRefs:
AggregateResultRef:
AssessmentWorkAdmission?: <omit when no dated U.Work is asserted;
when present, every non-optional field below is required>
AssessmentApplicationRef?: <include only when the Work account consumes an independently established A.6.1 application; state the obtaining Work-to-application relation>
AssessmentWorkRef: <one dated U.Work independently admitted under A.15.1>
AssessmentWorkInterval:
AssessmentContainingSystemRef: <exact U.System>
SemanticEvaluationMethodRef: <exact U.Method>
EnactedMethodRef: <same SemanticEvaluationMethodRef>
EvaluatorSystemRef: <the admitted U.System that performs the Work>
EvaluatorA13CoreBasisRef: <exact local agential kind and criterion, classification,
obtaining assignment, scope, working situation, window, and adequate core evidence;
add a characteristic profile only when its receiving use consumes it>
EvaluatorSystemRoleAssignmentSpeciesRef: <the declared assignment species and all
identity-bearing participant positions used by EvaluatorA13CoreBasisRef>
EvaluatorSystemRoleAssignmentRef: <the same obtaining assignment occurrence with all
declared participant values>
AssignmentHolderCheck: <the occurrence holder is EvaluatorSystemRef>
AssignmentPredicateCheck: <the declared assignment predicate obtains for all declared
participant values>
AssignmentInterval: <the uninterrupted interval in which the species predicate obtains>
AssignmentCoverageCheck: <AssessmentWorkInterval is covered by AssignmentInterval>
PerformedUnderAssignmentRef?: <include only when precise assignment-bound attribution is
current; cite the direct case fact that EvaluatorSystemRef performed AssessmentWorkRef
under the same EvaluatorSystemRoleAssignmentRef, then use F.6 after holder equality,
the declared species and participants, the assignment predicate, and interval coverage
above obtain>
AdditionalEvaluatorSystemRoleClassificationRef?: <optional additional neighbouring A.2
and C.3.2 claim, not the classification already required by the A.13 core; neither the
assignment nor Work establishes it>
DRRDecisionAdequacyResultEpisteme:
EntityOfConcern: <same exact DRRVersionRef>
EffectiveReferenceScheme:
ClaimGraph:
DeclaredAuthoringUse:
RequiredAuthoringUseSource:
QualificationWindow:
EffectiveCoordinateFloorMap: <map and source>
CoordinateTable: <all coordinates, values or unestablished states, adjacent-value rationales, evidence loci; rendering as in 4.4a>
BoundedOmittedQuestionSearch: <checked basis and any answer-changing question found>
PrecisionRestorationProfile?: <only when the requested reusable result or named reliance consumes it>
KindRestorationChecks?: <for repairs that can change FPF-governed meaning when this result consumes the exact check>
OnticCandidateDisposition: <when triggered>
CampaignProblemSolutionUnfoldingCheck: <when triggered>
DRRDecisionAdequacyStatus:
FirstDraftingActionOrFirstRepair:
MostExpansiveNonAdmissibleOverread?: <only when an independent local ground makes one competing reading plausible and action-changing>
StopOrRepairCondition:
ReopenIf:
WitnessRefs:
EvidenceUseRelationRefs:
An optional DRRDecisionAdequacyRecordRef can collect references to the configuration, result episteme, witnesses, evidence-use relations, publication, and currentness. Include the semantic Method and assessment application when used, and Work admission when Work is asserted. Establish the application and Work through their respective conditions. Coordinate claims, evidence use, assurance, F.10 status use, acceptance, and downstream authorization each require their own basis.
If reliance depends on a viewpoint or grounding claim, give the basis for that claim. The evaluator’s identity, the record’s packaging, and a source label cannot establish it on their own.
E.22 may frame whether the evaluation is floor-only, exceptional-improvement, trade-off, open-question, absorption, or proposal-producing and may raise a floor before evidence is judged. Keep the required authoring use fixed after evidence appears. E.23 governs later repeated improvement work on the checked DRR after result claims or findings exist.
E.9.DA:4.3 - Ordinal coordinate scale and effective floor
| Value | Label | Meaning for a DRR decision-adequacy coordinate |
|---|---|---|
| 0 | absent | The coordinate is not expressed for the declared authoring use. |
| 1 | namedOnly | The coordinate is named or implied, but cannot carry decision reliance. |
| 2 | partiallyExpressedForDeclaredUse | The coordinate is present but incomplete, fragile, or too narrow. |
| 3 | sufficientlyExpressedForDeclaredUse | The coordinate can carry the declared authoring use, with limits visible. |
| 4 | wellExpressedForDeclaredUse | The coordinate is clearly expressed with direct evidence and boundary protection. |
| 5 | exceptionallyExpressedForDeclaredUse | The coordinate is exceptionally expressed across reinforcing loci and cases without hiding cost or neighbour loss. |
When a complete reusable coordinate evaluation is produced, each ordinal value is a content-evaluation claim about the exact checked DRR under the declared use and window. In an ordinary bounded review, the same scale may guide judgement without materializing a measure, Work record, result episteme, assurance, acceptance, or reward.
Every required E.9.DA coordinate has a default floor of 3 sufficientlyExpressedForDeclaredUse. The review request, an accepted decision, or an E.22 question frame fixes the required authoring use. Use the E.9.DA default unless a source declares a higher floor for all coordinates or for named coordinates before the evidence is judged. Record the source of each raised floor.
Once the evaluator has seen the result, they may not lower a floor, narrow the use or selected loci, or shorten the qualification window to make the DRR admissible. A diagnostic evaluation with a lower target may report values. It cannot yield admissibleForDeclaredAuthoringUse.
E.9.DA:4.4 - Required decision-adequacy coordinates
Before assigning values, run the bounded omitted-question search from §4. Ask whether the DRR omitted an important question that would change its answer, content architecture, source use, consumer obligation, first drafting action, or stop. Inspect only enough of the governed problem, problem-owning practice, current sources, strongest live alternative, failure and recovery cases, and direct consumers to answer that question.
If the search finds an important omitted question, state it as a substantive finding before closing the coordinates. Reassess each affected decision, architecture, source-use, actionability and boundary coordinate under its value rule, keeping the required use fixed. When the search finds no such question, an ordinary clean review needs no separate ledger. A reusable result records the checked basis and clean disposition its named reliance needs.
For a framework-architecture decision, recover the practice field and the full use the initiating problem and sources require before evaluating the proposed owner. Inspect the decisive E.4.PFAD comparison, including any current framework boundaries that the new material calls into question.
A correct list of suppliers, a suitable carrier, closed alternative rows, or successful use of a newly written application can each support a narrower conclusion. None by itself establishes that the previous architecture already supplies the whole. Preserve each result at its demonstrated scope. Leave the architecture conclusion open when the required field or redistribution comparison is absent.
| Coordinate | Evaluation question |
|---|---|
BoundedDecisionQuestionRecoverability | Can the reader recover the FPF content decision question named by value and adjacent questions outside it? |
SelectedAnswerDecisiveness | Does the DRR record the selected answer as a decision made now rather than left for drafting? |
SourceUseAndDecisionInheritanceCarryThrough | Does needed source use or accepted decision inheritance change selected answers, boundaries, obligations, cases, architecture choices, stops, or reopen conditions by value? |
AlternativeDispositionCompleteness | Are the alternatives needed to explain the selected answer, live boundary, or reopen condition closed, while irrelevant discussion history is absent from the current DRR? |
SelectedLocusObligationClosure | Are selected content responsibilities and explicit non-responsibilities assigned to selected loci named by value without unclassified selected loci, hidden ontic-candidate decisions, or precision-restoration profile defects that would become pasteable pattern prose? |
FPFContentArchitectureSelectionAdequacy | Is the selected architecture adequate at the scale of the actual question: contribution or pattern, connected Method family, practice field and DPF, several fields and Suite, or publication/access arrangement? Are retention, addition, split, merge and redistribution of existing content compared where they can change that answer, with the concrete patterns and relations needed for outside claims and boundaries? |
ArchitectureSourceAndViewLossClosure | Are affected structures, structure kinds, structural views, view losses, missing-structure return conditions, source-use relations, and splits among architecture decision, architecture description, publication, and ontic description decided when the decision uses them? |
DraftingActionability | Does the DRR state the working problem, positive selected answer, practical change, selected-locus obligation, first drafting action, and nearest boundary plainly? For a broad authoring rule, does the actual predecessor/proposed host replay show that entry, action, result, and effort remain at least as usable? |
LexicalAndNamingClosure | Does actual proposed wording preserve the live kind, claim, relation, ordinary meaning, and first action under E.8 and F.19, using E.10, F.18, A.6.P, C.2.P, or the concrete defining or constraining pattern only where needed? |
SoTAAndEvidenceUseInDecision | Does each decision-governing source change a decision payload, and are non-SoTA source uses bounded? |
ScopeBoundaryAndNonOverread | Are the selected decision scope, action-changing outside items, source-use or missing-structure return conditions, and lost distinctions explicit without letting precision-restoration defects or architecture-memo leakage displace the selected answer? When a specific competing reading is independently grounded and plausible, is the smallest needed correction stated? |
ConsequencesAndRegressionCoverage | Are costs, validation obligations, source-loss regressions, actual-host cases, preserved predecessor ideas, near misses, and changes to direct consumers sufficient to protect drafting without demanding repeated full-corpus proof? |
SiblingDecisionCoordination | Is coordination with other DRRs, accepted decisions, or evaluation patterns explicit without duplication or weakening? |
AdministrativeStateAndAuthoringHistorySeparation | Are review logistics, packet state, landing, monolith placement, chat history, and authoring history kept out of decision evidence? |
CorpusEcologyAndShadowSpecResistance | Does the DRR place repeated doctrine in the concrete patterns that carry it, update the consumers that depend directly on the distributed content, and avoid duplicate local variants or shadow specs? |
Distinguish coordinates by the repair question each answers. One DRR section may support several coordinates. State which property it supports for each. When two coordinates always fail and require repair together, use A.19.ECS to repair the characteristic space in the DRR or the evaluation pattern.
E.9.DA:4.4a - Result-row discipline and calibration
Use the question-to-ground and result-acceptance operation in E.22:4.3 within this evaluation.
A complete reusable result must let the reader recover every coordinate, its value or unestablished state, the applicable adjacent-value rationale, and the evidence locus. Choose a form that suits the receiving use and preserves any required serialization. The table shows one sufficient form.
| Coordinate | Value | ShortRationale | EvidenceLocus |
|---|---|---|---|
<E.9.DA coordinate> | <0..5; leave unassigned while required evidence is missing or unchecked> | <assigned-value basis and the applicable adjacent-value rationale below> | <DRR section, row, alternative, source-use row, selected-locus row, accepted-decision row, architecture decision, or missing locus named by value> |
For values 1..4, explain why the lower adjacent value would understate the evidence and the higher adjacent value would overstate it. For 0, explain why 1 would overstate the evidence and what would raise the value or reopen it. For 5, explain why 4 would understate the evidence and what would lower the value or reopen it.
A reusable coordinate result is incomplete if any required coordinate, its value or unestablished state, the applicable rationale, or its evidence locus is missing. An ordinary bounded review is sufficient when it clearly identifies the checked DRR, the required use and its source, the effective floor, a substantive finding, repaired text or a clean unchanged result, the first action, and the stop or reopen condition.
When required evidence is missing or unchecked, identify the gap. Leave the affected value unestablished until the needed check is complete. Assign a lower value only if checked content establishes the inadequacy in that coordinate’s rule. For example, the checked DRR may lack a required decision. If an omitted question changes the answer, reassess each dependent coordinate under its own rule. The question adds no coordinate, and strength on another coordinate cannot compensate.
Common calibration points:
| Coordinate family | 3 | 4 | 5 |
|---|---|---|---|
| Decision question and selected answer | The decision can guide limited drafting, but unsettled or ambiguous material remains visible. | The selected answer and outside questions are directly recoverable for declared authoring use. | The decision is reinforced across question, alternatives, consequences, selected loci, and first drafting action without hidden unsettled branches. |
| Source-use and inheritance | Sources or inherited decisions are relevant, but payload mutation or rejection is compact or incomplete. | Source-use relation, adopted payload, rejected payload, currentness, and selected-locus obligation are explicit. | Source distinctions are replayable across selected answer, cases, boundaries, and first drafting action. |
| Selected-locus and architecture closure | Loci are named, but some obligation, non-obligation, split, architecture choice, ordinary reference relation, or phrase apparatus remains generic. | Loci are named by value and content obligations are closed for declared use without precision-restoration defects or architecture-memo prose in the future pattern body. | The split, merge, concrete pattern or relation for each outside claim or boundary, and lost-structure or source-use distinctions are replayable across cases and consequences while product prose remains positive-subject first. |
| Drafting actionability | A skilled author can proceed, but must infer some governed EntityOfConcern, first move, selected-locus relation/decision, user-facing action, boundary disposition, or reference/architecture disposition from scattered material. | The DRR directly exposes the governed EntityOfConcern, first substantive drafting move, exact selected-locus relation or decision, user-facing action, and only necessary boundary/reference pointers as positive subject kind and action guidance; ordinary references remain references, apparatus stays out of pattern prose, and an evaluation row is neither future method nor work. | Drafting can proceed across heterogeneous selected loci from the decided content, without inventing missing decisions or importing local negative catalogues, reference boilerplate, phrase apparatus, architecture-memo prose or unsupported Method/Work claims. |
E.9.DA:4.5 - Local result status and stop condition
Each status below applies to the DRR under review, required use, effective floor, and qualification window. An ordinary bounded review may state it. Create a C.2.1 aggregate result episteme only when a named later reliance needs that reusable object. A local status neither decides a review nor establishes a gate result, permission, assurance level, or work state.
| Status | Meaning |
|---|---|
admissibleForDeclaredAuthoringUse | Every required coordinate meets its effective floor, no architecture or split blocker remains, and the result states the first drafting action, stop or return, and reopen condition. Any downstream acceptance or authorization uses its own receiving relation. |
newFrameRequired | The DRR appears useful only for a different decision, authoring use, selected-locus set, source-use claim, or qualification window than the required one. This is not an admissible result for the current request; open a new E.22 frame or repair the DRR. |
repairBeforeDrafting | One or more required coordinates fall below their effective floors for the required authoring use. |
splitDecisionRequired | Several coupled questions need separate decision records or explicit convergence before the current result can be admissible. |
holdForArchitectureDecision | Content object, branch, neighbour boundary, selected locus, structural-view relation, missing-structure return condition, source-use relation, or publication split must be decided before adequacy can close. |
Derive status without compensation across coordinates. An unresolved architecture blocker yields holdForArchitectureDecision regardless of the other values. A required split yields splitDecisionRequired, and an easier or different use yields newFrameRequired. Otherwise, any required coordinate below its effective floor yields repairBeforeDrafting. State the required-use source, effective floor, and floor source in either result form so another evaluator can reproduce the conclusion.
When evidence needed for a coordinate is missing or unchecked, that value remains unestablished. Complete the check before drawing a conclusion that depends on that value. An unestablished required value cannot support admissibleForDeclaredAuthoringUse. An independently established architecture blocker, required split, or below-floor finding remains usable.
A result carrying admissibleForDeclaredAuthoringUse states the first drafting action, stop or return, and reopen condition. A non-ready result states the first repair, split boundary, or architecture question. Add a non-admissible reading only when an independent local ground makes it plausible and action-changing; any later gate or authorization uses a separately defined receiving relation.
E.9.DA:4.6 - Compact result form
Keep an ordinary bounded result short. One possible form follows.
E.9.DA bounded review:
Exact DRR:
Required authoring use and its source:
Effective floor and source: <E.9.DA default 3 | predeclared higher floor and exact raising source>
Actual-host evidence: <required only when a broad authoring rule is selected>
Substantive result: <findings, including any answer-changing omitted question | repaired text | unchanged checked DRR when clean>
Status:
First drafting action or first repair: <include the applicable stop or return condition>
Most expansive non-admissible overread?: <only when one is locally warranted>
Reopen if:
This form suffices when no named later use needs a reusable coordinate result. A clean focused review may point to the unchanged DRR without a separate clean ledger for the bounded omitted-question search. After an inspect–repair–verify pass, point to the repaired text and its focused verification.
Extend the bounded result when a complete reusable coordinate evaluation is explicitly required or a named later reliance needs exact result identity. Keep the bounded result’s content in the extended form.
E.9.DA reliance-bearing result:
Exact DRR and effective ReferenceScheme:
Required authoring use, its source, and qualification window:
Effective coordinate floor map and source:
CharacteristicSpace and evaluation-spec refs:
Semantic evaluation Method ref, only when used by the receiving claim:
A.6.1 assessment application and actual binding refs, only when used:
A.13 performer-core and A.15.1 Work refs, only when dated U.Work is asserted:
F.6 attribution refs, only when precise assignment-bound attribution is asserted:
Evidence basis checked, including the bounded omitted-question search:
Coordinate results: <each Coordinate, Value or unestablished state, ShortRationale, EvidenceLocus; form as in 4.4a>
Precision-restoration reading and triggered exact checks:
Witness and evidence-use refs on which the named use relies:
Status, first action or repair, bounded overread, and reopen condition: <include stop or return; overread only when independently grounded>
Only the reliance-bearing branch requires every coordinate and the exact identities its receiving use needs. Method, application, and Work remain independently conditional. A claim of dated U.Work requires the enacted Method, every precise performer’s A.13 core, and independent A.15.1 admission. Include an A.6.1 application only if the receiving claim uses that separately established application. Add F.6 only for precise assignment-bound attribution. Downstream status use, assurance, E.19 admission, authority, and drafting permission require their own direct grounds.
E.9.DA:4.7 - Structured finding row when reuse needs it
E.9.DA finding:
DRR version: <DRRVersionRef>
Declared authoring use: <DRRDeclaredAuthoringUse>
Coordinate or status affected: <all affected coordinates, statuses, or stop conditions>
DRR locus: <section, row, alternative, source-use row, accepted-decision row>
Value or status effect: <value, status, floor, or stop impact>
Correction direction: <selected answer | selected locus | source-use payload | architecture choice | example | boundary | stop or reopen>
Closure test: <what changed DRR text would show>
Use this row when the finding must be reusable in a structured form. In an ordinary bounded review, you may put the same precise diagnosis and repair direction in the handoff or repaired text. Labels such as weak DRR, needs more evidence, or architecture unclear leave the repair unspecified in either form. Record each independently repairable defect once and identify all affected coordinates or statuses, preserving their distinct values and rationales.
When E.22, E.23, absorption, or exceptional-improvement framing requests improvement, below-floor claims support finding rows and subsequent repair. Use a proposal row for an above-floor change only when it offers a substantive, non-dominated improvement within the declared authoring use. It might settle the answer more decisively, change the adopted source payload, assign a selected-locus obligation, decide an architecture split or merge, close a rejected alternative, specify a first drafting action or regression case, or remove or relocate apparatus that would otherwise enter the pattern prose.
A value below 5 is not in itself a defect. Stopping at 4 requires loci showing why a further change to decision content is dominated, unavailable, or outside scope.
E.9.DA:5 - Worked slices
Ordinary case — an overbroad wording 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 review request fixes the use as authoring input for that amendment. 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 predecessor text of the affected 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? The answer changes the proposed rule.
Return repairBeforeDrafting. The blanket replacement collapses distinct objects and uses into one term. First repair the DRR so it selects recovery of the intended meaning. Write system role for the local kind. Where the text denotes an assignment, participant meaning, SlotKind, or ordinary use, name that meaning. Reopen when the revised DRR distinguishes those uses, names the consumers that depend on the change, and the actual-host replay preserves precision and readability. The compact result suffices here.
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 level of detail and why this value falls below the floor:
| Coordinate | Value | ShortRationale | EvidenceLocus |
|---|---|---|---|
LexicalAndNamingClosure | 2 | Value 1 would understate the DRR because it names the target word and selected E.10 amendment. Value 3 would overstate it because the answer still conflates a system-role kind with the assignment, relation-participant meaning, SlotKind, and ordinary word uses exposed by the actual host. | DRR-ROLE-TRIGGER-03@2, selected-answer row; A.6.5:1; A.6.5:4.1 |
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. This comparison needs no Method, application, or Work reference. Include witness and evidence-use references only if it relies on them.
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.
E.9.DA:6 - Bias annotation
This pattern favors settling decisions before drafting. A missing decision costs more to repair once several pattern authors depend on it.
A small editorial decision can use E.9 directly. In an ordinary DRR review, judge the decision, perform the bounded omitted-question search, and identify the first action. This review needs no separate assessment record. When a named later reliance needs an exact reusable result, Method, application, and Work remain independently conditional. If Work is asserted, preserve its evaluator System, enacted Method, and independently established admission basis. An application, attribution, result, evidence use, or receiving status enters through its own claim and grounds. E.21 covers pattern quality, E.23 repeated improvement, and F.19 wording repair, with E.10 for cues and unresolved meanings.
E.9.DA:7 - Conformance checklist
| Check | Requirement |
|---|---|
CC-E9DA-0 | Make the semantic judgement first. For an ordinary bounded review, name the exact DRR, required authoring use and source, effective floor and source, substantive findings, repaired text or unchanged checked DRR when clean, first action or repair, stop or return, and reopen. Add a non-use boundary only when an independently grounded competing reading is plausible and action-changing; do not require a formal dossier. |
CC-E9DA-0a | When a broad language, ontology, or authoring rule is selected, use one replay comparing the predecessor and proposed versions of the same actual host, accounting for their dependencies. Evaluate recognizable entry, inputs, first action, vocabulary, formality and assurance burden, first result, stop, preserved ideas, and direct consumers at comparable effort. A proxy does not substitute. |
CC-E9DA-0b | Before coordinate closure, make one bounded search of the governed problem, problem-owning practice, current sources, strongest live alternative, failure and recovery cases, and direct consumers for an important question the DRR omitted. Return an answer-changing question as a substantive finding and reassess every affected coordinate under its value rule. A clean ordinary review needs no separate search ledger; a reusable result records only the basis its receiving reliance needs. |
CC-E9DA-1 | Keep the exact DRR, required authoring use and its source, selected-locus map, qualification window, and effective floor recoverable. Method, A.6.1 application, and dated Work are independently conditional. Add each identity only when the receiving claim uses it. If dated U.Work is asserted, establish the enacted Method, every precise performer’s A.13 core and independent A.15.1 admission in 4.2. Add the application and its relation to Work only when independently established and used by the receiving claim; add F.6 only for precise assignment-bound attribution. |
CC-E9DA-2 | When a complete reusable coordinate evaluation is explicitly required, evaluate every coordinate with value, adjacent-value rationale, and evidence locus. Otherwise perform the focused content review requested and return its findings or repairs without creating unused coordinate records. |
CC-E9DA-3 | Justify values from DRR decision content, accepted source-use payload, and the bounded omitted-question search, not administrative state, source reputation, official status, recency alone, or popularity. |
CC-E9DA-4 | Derive the local status noncompensatorily from the required use, effective floor, coordinate values, and architecture or split blockers. Constitute an aggregate result episteme only when the requested reusable result or named later reliance requires it; keep any receiving status use or authority separate. |
CC-E9DA-5 | Keep the adequacy judgement distinct from the checked DRR, pattern quality, E.19 admission, review or release state, assurance, gate, project work, and later repair. In the reliance-bearing branch, also keep Method, assessment application, Work, witnesses, evidence use, result episteme, and optional record distinct. When assessment U.Work is admitted, keep every precise performer’s A.13 core and the independent A.15.1 Work account in 4.2 distinct and recoverable; keep any current F.6 attribution as a separate later relation. |
CC-E9DA-6 | Apply F.19 to decision-governing wording introduced or repaired by the evaluation, including names, coordinates, status values, examples, stop conditions, and findings. Use E.10 for cues and routes to an unresolved meaning’s defining or constraining pattern. |
CC-E9DA-6a | Check the precision-restoration effect before accepting values: ordinary meaning and first action, word-use precision, phrase apparatus, repetition/distribution, ontic-slot clarity, description/publication/source separation, and pattern-use wording. Record a profile only when the requested reusable result or named reliance consumes it. |
CC-E9DA-6b | When a proposed wording or naming repair can change an FPF-governed meaning, compare the object, relation or claim, slot, use, admissible scope, and practitioner action in the wording before and after the repair. If a live distinction changes without an accepted semantic decision and the concrete defining or constraining pattern, return repair rather than treating the wording as clean. |
CC-E9DA-6c | When a DRR selects, rejects, splits, or declines a candidate ontic or an ontic-publication boundary, evaluate DRROnticCandidateDisposition: candidate EntityOfConcern, sufficiency rationale, rejected alternatives, candidate-universe sanity sweep when the claim is broad, slot-relation boundary, description-publication boundary, and selected pattern placement by value. Missing disposition lowers SelectedAnswerDecisiveness, SelectedLocusObligationClosure, FPFContentArchitectureSelectionAdequacy, and DraftingActionability. |
CC-E9DA-6d | When first-entry, route-shaped, path-shaped, DPF, pattern-family, or unfolding-structure material is selected by the DRR, evaluate CampaignProblemSolutionUnfoldingCheck. If the selected solution architecture remains only in the DRR or public README after drafting, lower SourceUseAndDecisionInheritanceCarryThrough, SelectedLocusObligationClosure, DraftingActionability, and CorpusEcologyAndShadowSpecResistance as applicable. |
CC-E9DA-7 | State each source contribution by named practice question, exact source, current-best or lineage status, selected payload, adopt/adapt/reject decision, changed E.9.DA or DRR locus, qualification, and smallest reopen condition. |
CC-E9DA-8 | Check whether any intended value or protected trade-off worsened when visible decision-adequacy values improved; report any observed loss. |
CC-E9DA-9 | In an ordinary bounded review, cite the evidence needed for each substantive finding or repair. In a complete reusable coordinate result, state the full DRRDecisionAdequacyEvidenceBasis, including only the bounded omitted-question search basis needed by the reliance; identify missing or unchecked source-currentness, inheritance, selected-locus, architecture, comparator or omitted-question evidence and complete the needed check before assigning the affected value. Lower a value only when the coordinate’s rule makes the established inadequacy a lower value. |
CC-E9DA-10 | Use the value-appropriate adjacent comparison in §4.4a for every assigned value, including the endpoint rule for 0 or 5. |
CC-E9DA-11 | Keep ordinal values as ordinal content-evaluation result claims, not repair targets. Every required coordinate below its effective floor prevents admissibleForDeclaredAuthoringUse; an architecture blocker or required split is noncompensatory. Above-floor improvement requires substantive non-dominated proposal rows when requested and cannot close by adding source volume, selected-locus tables, boundary catalogues, quality proof, or process evidence that does not make the DRR more decisive for its required authoring use. A no-proposal or stay-at-current-value disposition must name loci and why no worthwhile decision-content move remains. |
E.9.DA:8 - Common anti-patterns and repairs
| Anti-pattern | Repair |
|---|---|
| Specification or record as evaluator. A filled coordinate table, published record, or E.9.DA pattern is said to have assessed the DRR, issued assurance, accepted it, or authorized drafting. | Name the U.System that performed the evaluation. An evaluator-role label does not identify that System. Leave an ordinary review outside Work admission. Add Method, application, or Work identity only when the receiving claim uses it. If dated U.Work is asserted, use the complete branch in 4.2. An optional local system-role classification is a separate claim. |
| Conditional branch collapsed into Work. A reusable result is said to require assessment Work, or a Method or A.6.1 application is described as Work because all three can occur in one case. | Keep Method, application, and Work independently conditional. The Work branch requires its enacted Method, every precise performer’s A.13 core and independent A.15.1 admission. An application remains conditional on a claim using that independently established declared-operation application. Add F.6 only when precise assignment-bound attribution is also current. Neither Method nor application entails Work. A relation between application and Work must be separately defined and obtain. |
| Heading-complete DRR. Headings exist but authors cannot tell what to write. | Return the missing selected answer, selected-locus obligation, and first drafting action for repair; in a complete reusable evaluation, lower the corresponding coordinates. |
| Question-complete around the wrong frame. Every named question is answered, but the DRR omitted a question that changes the answer, architecture, source use, consumer obligation, first action, or stop. | Before closing the coordinates, run the bounded search for an omitted question. Return the question as a finding and reassess the coordinates whose claims it changes under their value rules; do not narrow the frame to preserve the values. |
| Source packet in DRR clothing. Sources are preserved but FPF decisions are absent. | State selected payload, rejected payload, and selected-locus obligations. |
| Address completion without architecture. Every locus is named but the split or merge is wrong. | Repair FPFContentArchitectureSelectionAdequacy. |
| Watch item as decision. Drafting is expected to choose the answer during pattern authoring. | Select, repair, split, or hold. |
Ontic candidate left to drafting. A DRR uses uncertain candidate phrasing for a concept cluster or pattern set but leaves candidate sufficiency, rejected alternatives, publication boundary, and placement for the pattern author. | Close DRROnticCandidateDisposition now: select, reject, split, or decline the candidate by value; when no new ontic is warranted, name the existing concrete pattern, relation, or bounded local account that carries the contribution the DRR needs. |
| Review-state proxy. Review acceptance or landing is treated as adequacy. | Use decision-content evidence only. |
| Floor or scope laundering. After seeing weak values, the evaluator chooses an easier use, lower floor, smaller selected-locus set, or shorter window and reports an admissible result. | Recover the required use and floor source before judging evidence. Return newFrameRequired, repair, split, or hold for the original request; a different frame is another evaluation, not a pass. |
Adequacy result without evidence loci. Values are listed without by-value DRR or source loci. | Re-run the evaluation with each coordinate, its value or unestablished state, applicable adjacent-value rationale, and evidence locus recoverable. Identify any missing or unchecked evidence and complete the check before assigning the affected value. Use a lower value only when checked content establishes the inadequacy defined for that coordinate. |
| Apparatus-overwrapped drafting payload. The DRR offers selected-pattern wording wrapped in role, publication-form, locus, flow, state, status, text, package, or process apparatus without changing a recoverable kind, relation, claim, admissible use, selected locus, user-facing action, or flow role. | Apply F.19. If a kind or claim changes, repair it through the concrete defining or constraining pattern; otherwise remove the apparatus and restore the positive subject and first action. |
| Proxy replay for a broad rule. A schema, invented fact pack, lane test, or promise inside the DRR is used as evidence for language or actionability. | Replay the complete proposed rule on the predecessor and proposed versions of an actual host and the consumers affected by that host change. Lower the affected values or return repair when use worsens. |
| Formal assessment before semantic judgement. Configuration, Method, application, Work, result-episteme, and evidence-use fields are completed before anyone can state the DRR’s decision and first drafting action. | Judge the exact DRR, bounded omitted-question search, and actual-host effect first. Open each reliance-bearing identity only when a receiving use needs it. |
Goodharted DRR adequacy. A DRR is made easier to defend as 4 or 5 by adding source rows, locus tables, boundary catalogues, or review proof while the selected answer and first action do not improve. | Reject apparatus-only improvement; repair decision content, delete or relocate proof material, and use E.13 when the measure substitutes for decision usefulness. |
| Solution architecture evaporates after DRR. A DRR solves a multi-locus unfolding or first-entry problem, but hosts receive only fragments and the DRR remains the only place where the structure is understandable. | Move the surviving solution into selected pattern bodies, local unfolding blocks, E.11 entry expansions, or concrete relation loci; recheck direct consumers. |
E.9.DA:9 - Consequences
| Consequence | Benefit | Cost |
|---|---|---|
| DRR adequacy becomes inspectable before drafting. | Pattern authors get decisions, not source summaries. | Ordinary review touches only the live questions; a complete reusable evaluation covers every coordinate. |
| Architecture selection becomes visible. | By-value but wrong split or merge choices no longer pass as complete distribution. | Some DRRs need architecture repair before drafting. |
| Source mutation is explicit. | SoTA, standards, reviews, audits, and accepted decisions shape decisions rather than decorate them. | Rationale-only sources cannot raise values. |
| The effective floor and required use are reproducible. | Two evaluators can derive the same status without choosing an easier frame after seeing evidence. | The invoking use or E.9.DA default must be named, and every below-floor required coordinate remains noncompensatory. |
| One bounded search tests the DRR’s frame before coordinate closure. | The reviewer can identify an omitted question that changes the answer. | To answer that question, the evaluator must inspect the problem, practice, sources, alternative, failure and recovery cases, and the consumers that depend on the decision. Limit the search to what the answer requires. |
E.9.DA:10 - Rationale
Settle a missing FPF decision in the DRR before distribution so several later authors do not have to make the same choice. For an ordinary review, judge the decision in the DRR using the bounded search for an omitted question and any actual-host replay the decision requires.
A separately requested reusable evaluation or named later reliance can require a complete coordinate result and exact evaluation or result identities. These two review forms let authors keep decision records as concise as the decisions allow and supply the evaluation detail that reliance needs. In either form, adequacy depends on the content of the decision.
E.9.DA:11 - SoTA-Echoing and source use
| Practice question | Exact source and status | Selected payload and disposition | Changed E.9.DA locus | Qualification and smallest reopen condition |
|---|---|---|---|---|
| How much structure should the first decision result expose? | Nogueira, Silva, and Conte, One Size Fits All? An Empirical Comparison of ADR Templates regarding Comprehension, Usability, and Ease of Adoption, 2026 preprint — current empirical comparator for ADR-form usability. | Adapt. The study’s controlled comparison favours Nygard’s concise and objective form overall, while participant feedback identifies MADR’s advantage for structural detail and specific requirements. E.9.DA therefore keeps a short ordinary result and adds detail only for a named reliance. Reject one universal record shape or the inference that the longest template is the most adequate decision. | §§4, 4.6, and 5: ordinary result first; reliance-bearing extension second. | Qualified on 2026-08-15 for the reported student experiment and five templates. Reopen these loci if a stronger practitioner study reverses the form trade-off or shows that a named E.9.DA use needs a different minimum. |
| How should a reviewer treat fluent, reconstructed, or generated rationale? | Zhou, Li, Liang, et al., Using LLMs in Generating Design Rationale for Software Architecture Decisions, 2025 preprint — current empirical stress line for rationale completeness and misleading additions. | Adapt, with a domain boundary. In the reported 100-problem study, generated rationale had incomplete recall and a small share of potentially misleading arguments. E.9.DA does not generalize those rates to all DRRs; it uses the result to reject fluency, source volume, or recovered prose as completeness evidence and to require one bounded search for an important omitted question. | §§4, 4.4, 4.4a, 5, and CC-E9DA-0b/9. | Qualified on 2026-08-15 for generated software-architecture rationale, not all human-authored decisions. Reopen if better direct evidence changes the omission/misleading-risk answer or supplies a more effective low-cost completeness test. |
| Which architecture-description distinctions may an architecture-facing DRR reuse? | ISO/IEC/IEEE 42010:2022, Software, systems and enterprise — Architecture description — current-standard reference, not SoTA by official status. | Adopt narrowly. Reuse the standard’s explicit separation between an entity’s architecture and an architecture description, and its boundary that the standard does not define the architecting process or recording medium. Reject treating the standard, an architecture description, a viewpoint, or a model as the DRR adequacy method or as the architecture decision itself. | ArchitectureSourceAndViewLossClosure, the architecture-impact slice, and Relations. | Qualified to the published 2022 edition checked on 2026-08-15. Reopen only if a relied-on distinction changes; a later edition number alone does not make the standard a better adequacy method. |
| How should an actionable finding connect present condition, desired condition, and next move? | Sadler, Formative assessment and the design of instructional systems, 1989, and Hattie and Timperley, The Power of Feedback, 2007 — retained feedback lineage, with current FPF use carried through E.22 and E.23 rather than claimed as new SoTA. | Adapt as lineage. Keep the gap, evidence locus, first repair or drafting action, and reopen condition together so a finding changes the next move. Reject praise, a score, or a condition label without an action-changing diagnosis. | §§4.4a, 4.5–4.7, the worked case, and finding-related checks. | Retained because the desired/current/next-action distinction still answers this narrow feedback question and is used by E.22/E.23. Reopen only if a better feedback result changes that action structure, not because the sources are old. |
| How should several adequacy dimensions and trade-offs remain visible? | Qin et al., A survey on Quality-Diversity optimization: Approaches, applications, and challenges, Swarm and Evolutionary Computation 100 (2026) 102240 — current multi-dimensional optimization overview; MCDA and Pareto practice remain design lineage. | Adapt only the preserved-dimension lesson. E.9.DA keeps distinct coordinates, adjacent-value reasons, and visible trade-offs; it does not average them or import a QD archive, algorithm, fitness function, or selection mechanism into DRR review. The effective-floor rule is noncompensatory. | §§4.3–4.5, calibration, Consequences, and CC-E9DA-8/10/11. | Qualified on 2026-08-15 for the current overview’s quality-plus-diversity separation. Reopen if the selected dimensions no longer lead to distinct repair questions or a better decision-evaluation practice preserves the same distinctions at lower use cost. |
| What prevents decision-adequacy values from replacing decision usefulness? | Karwowski et al., Goodhart’s Law in Reinforcement Learning, ICLR 2024 — current theoretical and empirical proxy-optimization branch; Goodhart and Campbell remain lineage. | Adapt. Treat the ordinal value as an imperfect proxy claim, ask whether an intended value or protected trade-off became worse, and stop value-directed repair when it improves the visible score without strengthening the selected answer or first action. Reject all-5, 5-defensible, source-count, or checklist-completion targeting. | Problem failure 9; §§4.4a and 4.7; CC-E9DA-8/11; the Goodharted-DRR anti-pattern. | Qualified on 2026-08-15 as a proxy-risk result, not as an assertion that DRR review is reinforcement learning. Reopen if better proxy-risk work changes the early-stop or protected-value answer used here. |
The current-best source set spans empirical decision-document use, rationale-completeness risk, multi-dimensional evaluation, and proxy optimization. ISO/IEC/IEEE 42010 is used as a narrow current-standard reference; the feedback, MCDA, Pareto, Goodhart, and Campbell traditions remain lineage where the current rows or neighbouring FPF patterns carry the present answer. A new publication date, official status, citation count, or popular template does not by itself reopen any row.
E.9.DA:12 - Relations
| Pattern | Relation |
|---|---|
E.9 | Defines the DRR decision method and ordinary minimum form, with optional exact work/result and C.2.1 identity when a current claim or named reliance needs them. E.9.DA evaluates the version under review of that decision record. Use E.9 for the decision and its form. |
A.19, A.19.ECS, A.17, A.18, C.16, C.16.Q, C.25 | Define or constrain the characteristic space, evaluation specification, characteristics, scales, measurement boundary, quality-ascription precision, declared-use floor, noncompensatory status meaning, and any separately selected Q-Bundle consumed here. E.9.DA supplies the DRR-specific coordinates and result rules. |
A.13, A.15.1, F.6, A.6.1, A.2, A.2.1, C.3.2 | A.13 supplies every precise evaluator-performer’s core and same obtaining assignment; A.15.1 independently admits dated Work; F.6 supplies a separate later relation only when precise assignment-bound attribution is current. A.6.1 governs an exact application of a declared mechanism operation and its actual bindings; A.2 and A.2.1 supply the assignment species and occurrence; C.3.2 is relevant only to an independently asserted local system-role classification. Method, application, Work, and attribution are independently conditional here. Neither an application nor a Method entails Work. |
C.2.1 | Defines the identity of an exact checked DRR or reusable coordinate/result/record episteme when that identity is current. An ordinary bounded review need not create those objects. |
A.10, B.3 | Use the direct subject grounds for reliance on the checked result. A.10 recovers an implicit source-to-use account or makes provenance, currentness and bounded reliance replayable when needed. Use B.3 when someone makes a named assurance claim about an exact target claim. A favorable value does not establish those separate grounds. |
F.10, G.11 | Govern any downstream status use/interpretation and currentness. A local E.9.DA status value does not authorize drafting by itself. |
E.24.PUB, C.29 | E.24.PUB governs publication occurrence, form, and carrier; C.29 governs representation through a declared mathematical lens when such a lens is used for a result or record. State publication separately from the assessment and its evidence basis. |
E.8 | Governs later authored pattern bodies and the current-best-versus-lineage, source-payload, adoption, changed-locus, and reopen discipline used in §11. |
E.19 | May use precise E.9.DA findings, a repaired DRR, or reusable coordinate-result claims, and may expose an upstream DRR defect. Its admission or refresh review remains distinct. |
E.21 | Declares the pattern-quality characteristic space and result rules used for resulting pattern versions. Dated E.21 assessment work and its result concern one exact pattern version, not DRR adequacy, E.19 admission, or the E.9.DA record. |
E.22 | Frames one evaluation question and required use, may raise the effective floor before evidence is judged, and requires a separate evaluation if a later frame asks an easier question. |
E.23 | Governs repeated improvement and repair work after findings or proposals exist. |
E.13 | Governs proxy-to-value alignment when adequacy values, source counts, review marks, or discharge evidence substitute for decision usefulness. |
E.10, A.6.P, C.2.P, F.18, F.19 | F.19 supplies precise plain-language checks and ordinary wording repair. E.10 supplies cues and unresolved-meaning routes; A.6.P and C.2.P supply relation and episteme phrasing; F.18 supplies durable naming. The precision profile records only the distinctions its receiving use needs. |
| Architecture-facing FPF patterns | Receive architecture, structure, view, graph, publication, and source-use distinctions when the DRR decision uses them. |