F.15:7 - Finite scope and conformance record

Declare the finite scope before applying a rule:

FiniteHarnessScope:
  ScopeDesignator:
  ReceivingUse:
  EffectiveReferenceSchemeValues[]:
  ExactCurrentObjectOrOccurrenceRefs[]:
  ExactDescriptionOrRecordRefs[]:
  ExactVersionRefs[]:
  PriorLaterPairs[]?:
  SelectedStructureRefs[]?:
  SelectedStructureDescriptionRefs[]?:
  TriggeredRuleRefs[]:
  ExcludedClaimsAndNearestNonUses[]:

SelectedStructureRefs is empty unless an independently selected A.1.1/A.22 structure changes interpretation for the receiving use. A Structure description never replaces the Structure, its obtaining membership relations, or another scope member.

Use an optional record only to package already identified neighbors:

UnificationConformanceRecord:
  EntityOfConcern: exact checked slice/version selected by FiniteHarnessScope
  EffectiveReferenceScheme: scheme interpreting this record's ClaimGraph
  ClaimGraph: exact claims designated by the fields below
  FiniteHarnessScopeRef:
  CheckApplicationRefs[]?:
  AssessmentWorkRefs[]?:
  ResultClaimRefs[]:
  WitnessRefs[]?:
  EvidenceProvenancePathRefs[]?:
  BridgeOccurrenceRefs[]?:
  BridgeDescriptionOrCardRefs[]?:
  PublicationOccurrenceRefs[]?:
  PublicationFormRefs[]?:
  PresentationCarrierRefs[]?:
  CurrentnessRelationRefs[]?:
  NonAdmittedUses[]:
  ReopenTrigger:

The checked scope, rule declaration, ordinary checking action or admitted dated assessment Work, exact application, result claim, witness, A.10 evidence-provenance path, conformance-record episteme, E.24.PUB occurrence, publication form, carrier, and G.11 currentness relation remain distinct. A result ref is included only after its C.2.1 claim exists. The optional record may cite an already admitted Work ref; it does not restate the Work’s performer, Method, assignment, time, or containing System. Publication and currentness refs are neighbouring claims, not record identity shortcuts.