E.17.ID.CR:4.3.d - Fuller Declaration Block

When the heavier declaration weight really stays here, the unit still makes at least these fields recoverable:

• sourceRelationClass using the shared E.17:5.1b vocabulary when the comparison depends on source pointer, source availability or retrieval, source use, source faithfulness, claim recoverability, contradiction, omission, claim widening, added linkage, independent verification, bounded use, forbidden downstream use, or reopen trigger;
• sourceAnchorSet or sourceRefs;
• comparativeRelationClass = sameEntityComparisonClass | sharedFrameDistinctAlternativeClass | readerFitComparativeClass;
• comparisonBasis;
• addedClaimPolicy;
• required bridgeOccurrenceRef and boundedUseClaimRef when the case depends on bridge-mediated comparative relation; the use-claim reference resolves an exact claim whose EntityOfConcern is that Bridge occurrence and whose proposed use, direction, correspondence rule, tolerated loss, and polarity match the current comparative unit;
• optional bridgeCardRef when a reusable Card exists;
• optional bridgeStanceRef when it resolves the separate F.9.1 episteme whose EntityOfConcern is that exact use claim;
• targetUserModel when reader-fit is materially shaping the comparison unit;
• interactionMode when the review unit is not just one static comparative sentence;
• contrastiveQuestion when the case is answering a specific contrast;
• boundedComparativeUse;
• overreadRisk;
• promptWorthinessThreshold;
• ontologyBoundaryTrigger;
• worldContactPolicy;
• downstreamAuthorityLimit;
• baseCasePattern when the review unit is a mixed case layered over A.6.3.* or E.17.EFP.

sourceRelationClass is only the source-relation or bounded-claim class for the local claim or use. comparativeRelationClass is only the comparative-relation class of this review unit. Neither field is a neighboring object or claim such as a relation kind, Bridge occurrence, bounded-use claim, Card, stance note, semantic identity, evidence relation, gate, assurance, work relation, speech act, commitment, authority reference, or decision record. The sameEntityComparisonClass value is a special case for comparisons where the compared sources really describe the same entity; it does not assert semantic identity. When the unit compares distinct alternatives, use sharedFrameDistinctAlternativeClass plus distinct alternative refs, and do not treat the alternatives as equivalent or substitutable without an obtaining Bridge and the required bounded-use claim. readerFitComparativeClass by itself does not create an interpretation claim. When bounded correspondence wording implies a cross-context Bridge, first apply F.9. The boundedUseClaimRef must resolve a claim whose EntityOfConcern is the exact bridgeOccurrenceRef, and its proposed use, direction, correspondence rule, tolerated loss, and polarity must match this comparative unit. A positive proposed use requires affirmative polarity; when A.10 or B.3 is triggered, current reliance must support that exact use. A degraded reliance result narrows the use. Negative, abstaining, reopened, evidence-needed, blocked, or mismatched results stop this bridge-mediated use. The pattern that directly constrains the proposed comparison decides authorization, and evidence of the comparative-review Work says whether it occurred. A bridgeCardRef remains optional packaging. A bridgeStanceRef is also optional and is admissible only when it resolves a separate F.9.1 episteme whose EntityOfConcern is that same bounded-use claim. None of these references can substitute for another. The main comparison question plus the neighboring pattern boundaries still decide the selected FPF pattern or project-side FPF kind and reference named by value.