A.10:6 - Conformance Checklist
- Claim: the selected claim or proposition and its C.2.1 episteme are named, together with a separate target claim when the evidence use distinguishes it. An asserted local result retains its defining or testing rule.
- Result rule: each asserted local result retains the rule that defines or tests it. Cite the applicable FPF pattern or domain source when that reference is needed. Use E.10.ROLE only for a remaining ambiguity about a technical role claim.
- Carrier/source: the selected source episteme and edition, any material publication occurrence, form, carrier, or face, the copy/transform chain, and direct provenance or citation relations are recoverable.
- Work: whenever production, interpretation, transformation, evaluation, or reliance is asserted as dated
U.Work, point to its basis: the A.13 core including the obtaining assignment first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. Add direct relations, A.6.1 bindings, and resource-use facts only when the receiving claim uses them. Ordinary source-finding action need not be admitted asU.Work. - MethodDescription boundary: when an episteme is identified as a
U.MethodDescription, it meets A.3.2’s positive membership rule. Its generic method claims, including intended effects, establish no actual participants, occurrence, use, proof/test event, or result. - Result boundary: domain result, result episteme, carrier, provenance entry, outcome, and later action remain distinct.
- Graph boundary: every asserted edge names an independently established direct relation; no edge establishes work, participation, production, result, currentness, reliance, or representation by graph membership.
- Time/currentness: edition, window, supersession, revocation, source order, and G.11 result are explicit when they affect use.
- Reliance: bounded use and local
RelianceDispositionare present. A live rival and stop/reopen condition are included when they affect reliance; any unsupported-use guard satisfies §4.4’s full F.19 test. B.3 opens only for a named assurance claim. - Contest/privacy: the affected party can challenge the claim and disposition, while sensitive carrier access is minimized without erasing recoverability.