E.9.DA:4.1 - Local names and kind settlement

The following names support only the complete reusable-result branch. An ordinary bounded review need not instantiate them. When the branch is opened, each name resolves to the existing FPF object or reference stated here; none names an authority or mandatory record.

Local name	Kind and function
`DRRDecisionAdequacyEvaluation`	Compatibility compound label for the full evaluation package. Any use resolves to the exact values current for its receiving use: configuration, optional semantic Method, optional assessment application and bindings, optional Work admission, result episteme, witnesses or evidence-use relations, and optional record. The label is not one 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; inclusion is not evidence use by itself.
`DRRCoordinateValueRationales`	Required result claims: coordinate, value, adjacent-value rationale, and evidence locus named by value.
`DRRCoordinateLocusRefs`	Exact DRR loci cited by result claims; citation does not itself establish a value.
`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 profile of the DRR wording’s effect when the requested reusable result or named reliance consumes 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. Use A.10 to recover their exact sources, provenance, currentness and bounded use; its descriptive path creates none of those relations.
`DRRDecisionAdequacyRecordRef`	Optional C.2.1 record episteme that packages refs to the configuration and whichever of Method, application, Work admission, result, witness, evidence-use, reopen, and grounded non-use values are actually current. Its function is reference packaging; status and authority use 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 are local evaluation positions and refs. They are not release state, review status, project evidence, gate result, assurance, work, publication, or pattern-quality values.