Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:25:17 UTC

A.10:6 - Conformance Checklist

  1. 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.
  2. Result rule: every measurement, formal, causal, diagnostic, conformance, comparison, selection, acceptance, gate, permission, commitment, system-role-kind classification, system-role-assignment occurrence or state, relation among system-role kinds, or decision result identifies the pattern that defines or tests it; any other technical role use is first routed through E.10.ROLE.
  3. 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.
  4. 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 as U.Work.
  5. MethodDescription boundary: the identified episteme 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.
  6. Result boundary: domain result, result episteme, carrier, provenance entry, outcome, and later action remain distinct.
  7. 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.
  8. Time/currentness: edition, window, supersession, revocation, source order, and G.11 result are explicit when they affect use.
  9. Reliance: bounded use and local RelianceDisposition are present. Include a grounded, plausible unsupported use, a live rival, and a stop or reopen condition when they change the reliance decision; B.3 opens only when an actual named assurance claim is current.
  10. Contest/privacy: the affected party can challenge the claim and disposition, while sensitive carrier access is minimized without erasing recoverability.