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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:50:20 UTC

C.3.A:6 - Conformance checklist (normative)

IDRequirement
GC-01A universally quantified claim pins both claim-kind and receiving-kind declaration editions; the non-bridged restriction requires the receiving kind to be identical to or a subkind of the claim kind, while producer/output positions use their own direction. No candidate is invented.
GC-02Every claim-to-candidate use pins candidate, claim kind, receiving kind, both needed signature editions, and slice; it checks admissibility before evaluating the target receiving judgment and consuming true/false/unknown. An inadmissible request retains not-applicable without a judgment.
GC-03not-applicable, unknown, and known false remain distinct from each other and from guard refusal.
GC-04RoleMask use recovers the declaration episteme and exact masked judgment; any MaskAdapter remains a separate declaration.
GC-05Cross-context use compares kind identity and recovers each bridge channel required by its own applicability, the exact target declaration, and a fresh target judgment when a candidate is current; penalties route to R only.
GC-06Scope, Gamma_time, freshness, type compatibility, admissibility, classification, and disposition remain separate.
GC-07SpanUnion preserves one typed claim and line independence; candidate-specific evidence names exact candidates and judgments.
GC-08KindAT appears in no guard, and no plan, row, card, log, or slice substitutes for an actual candidate or Work occurrence.

C.3.A:6.1 - Proven-equivalent aliases

A context-specific guard alias is equivalent only when all required objects, inputs, classification values, bridge distinctions, and disposition boundaries can be recovered. Similar wording or the same final allow/refuse bit is insufficient.

C.3.A:6.2 - Bridge consequences

Phi(CL_scope) and Psi(CL_kind) are monotone non-increasing consequences on the receiving R path under the governing bridge patterns. This Annex prescribes no numeric form. It never performs arithmetic on F or G.