fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 21641–21658

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 15:41:27 UTC · snapshot created 2026-10-03 15:43:46 UTC · last check 2026-10-03 15:55:10 UTC

A.6.6:7 - Conformance Checklist

An A.6.6 use conforms when the checks for its selected branch pass:

  1. CC-BD-1 - Direct assertion first. The actual dependent, base, direct relation, and readable affirmative or negative assertion are recoverable. The direct pattern supplies the predicate. Test affirmative obtaining or establish nonobtaining under its applicable criterion or closure basis; a record, label, or failure to establish the affirmative supplies no case result.
  2. CC-BD-2 - Ordinary stop. If that assertion answers the receiving question, no SlotSpecs, declaration record, witnesses, edition, occurrence identity, or assurance package is required.
  3. CC-BD-3 - Reusable declaration is demand-driven. A RelationSignature satisfies the reuse test in A.6.6:4.3 and applies only to an already admitted relation kind.
  4. CC-BD-4 - Assertion and occurrence stay separate. A scoped witnessed record, when used, is a C.2.1 assertion or description episteme. It is not the world-side relation occurrence, and its form alone does not establish that occurrence; any constitutive contribution follows the direct relation’s rule.
  5. CC-BD-5 - Qualifiers are local. Scope and time are explicit when the selected predicate or named receiving use depends on them; they are not a universal field kit. Gamma_time is not used as a proxy for evidence freshness.
  6. CC-BD-6 - Evidence ontology is direct. Evidence use follows A.2.4 and A.10. Work, operation result, result episteme, carrier, provenance, evidence-use relation, and reliance remain separate; no generic verifiedBy or validatedBy edge is minted.
  7. CC-BD-7 - Crossings are conditional. An actual relation between two exact F.17 cells uses F.9 only when its predicate obtains and keeps the bounded-use claim separate. A ReferencePlane crossing uses its applicable plane relation. One creates neither the other.
  8. CC-BD-8 - No silent retyping or direction flip. Participant kinds and direction follow the direct relation. A mismatch is repaired by the applicable narrowing, Bridge, retargeting, or direct relation rule, not by renaming an endpoint.
  9. CC-BD-9 - Plain language remains sufficient. Ordinary relation-specific prose is preferred. Functional or arrow notation is optional and may not replace the readable assertion.
  10. CC-BD-10 - Metaphors do not become ontology. anchor, ground, attach, and support remain source-word triggers unless they name an already reserved primitive; no metaphor-headed fallback kind or relation is minted.
  11. CC-BD-11 - Meaning lane stays separate. Source-local meaning starts with F.0.1 and uses F.17 only when a durable sense address or basis relation is needed; it is not a base-declaration record.
  12. CC-BD-12 - Change claims name the changed object. Changing an assertion’s or reusable declaration’s ClaimGraph, exact EntityOfConcern, or effective ReferenceScheme identifies another episteme; representation-only editing need not. An actual relation change requires the direct relation’s own change predicate and any separately current Work.
  13. CC-BD-13 - Optional history is proportional. declareBase, rebase, rescope, retime, or refreshWitnesses is used only when a named receiver needs that declaration history. The label establishes no world-side fact.