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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:40:10 UTC

A.6.A:7 - Conformance Checklist (CC-A.6.A)

A text or pattern conforms to A.6.A iff:

  1. CC-A.6.A-1 — Recoverable claim or question. The intended claim or question and the participants and conditions needed for its use are recoverable. Apply a direct obtaining predicate when an actual relation is claimed; no common relation kind or sense token is required. An ordinary sentence may suffice, and an unresolved question may be the result.

  2. CC-A.6.A-2 — Explicit site and site-facet relation binding. When the site changes the meaning, identify it; distinguish EntityOfConcern, Description episteme, publication and carrier participation where the claim depends on that distinction.

  3. CC-A.6.A-3 — Explicit invited enactor. Identify the would-be enactor when the claim or question depends on it.

  4. CC-A.6.A-4 — Enactor discipline. When the invited enactor is meant as the actual would-be enactor, it resolves to a U.System or role assignment with system holder.

  5. CC-A.6.A-5 — Recoverable action and independently identified Method when selected. State the action or inquiry being discussed. If the result selects a Method for enactment, identify its exact U.Method and keep any MethodDescription separate. A proposed action need not invent a Method, WorkPlan or actual Work.

  6. CC-A.6.A-6 — Explicit coupling frame. Recover the actual conditions or coupling relation that determine the claim, when applicable; named configuration objects alone do not establish it.

  7. CC-A.6.A-7 — Detector, viewpoint reference, and view separation. When current, detector, ref-backed viewpointRef, its effective reference scheme, and independent optional view are not silently collapsed. The reference resolves to an exact admitted viewpoint episteme; a cited view already passes E.17.0 independently.

  8. CC-A.6.A-8 — Lawful normal form. When the receiving use needs one of §4.5’s forms, apply its discipline. A sufficient ordinary sentence, claim or question has no additional record requirement.

  9. CC-A.6.A-9 — Articulation-hint discipline. If omission changes meaning, articulationHint is explicit and is not treated as F or as an acceptance state.

  10. CC-A.6.A-10 — No invitation-as-obligation. An invitation is not silently published as a duty or gate.

  11. CC-A.6.A-11 — No invitation-as-work. An invitation is not silently published as a work occurrence.

  12. CC-A.6.A-12 — No capability collapse. A situated invitation is not silently rewritten as a general capability claim.

  13. CC-A.6.A-13 — No site-participant-property collapse. Affordance language is not published as a monadic site-participant property when enactor, site, and coupling frame matter.

  14. CC-A.6.A-14 — No hidden scalarisation. OptionSet publication does not introduce a hidden comparator value or ranking without an explicit comparator or policy.

  15. CC-A.6.A-15 — No silent sense rewrite. State what interpretation changed and how that changes the claim or its use. The optional verbs in §4.8 can express that change.

  16. CC-A.6.A-16 — No silent relation-family switch. A changed interpretation or an additional quality, ability, commitment or Work claim is made explicit under its own governor. Use a relation-kind change only when an actual relation-kind claim changes; two distinguishable sentences need no mandatory pair of records.

  17. CC-A.6.A-17 — Bridge accountability. A cross-tradition comparison first states whether it asserts or relies on semantic correspondence between exact senses in different semantic contexts. If yes, it cites an obtaining F.9 Bridge only after the predicate passes and adds a matching bounded-use claim only when a proposed use is live. If no, it uses E.17.ID.CR or the exact direct relation that supplies the contrast. Any F.9.1 stance note remains optional reader help for an already constituted claim.

  18. CC-A.6.A-18 — Boundary-claim hook when needed. If the recovered claim bears on admissibility, commitment, publication or automation, its applicable L, A, D or E classification and grounds are explicit.

  19. CC-A.6.A-19 — Lexical firewall. Bare action-first trigger tokens are absent from Tech prose and normative prose except as quoted metalinguistic discussion.

  20. CC-A.6.A-20 — Direct semantics for an actual relation claim. An obtaining relation or individuated occurrence uses its own predicate and any needed identity rule under A.6.REL. A recovery note, menu label, detector change or publication event does not supply those semantics or establish world-side change.

  21. CC-A.6.A-21 — Material alternatives remain recoverable. If a different interpretation changes a decision, retain the rival and the ground that excludes it, or return the missing discriminating question. Use a separate note only when the receiving use needs one.

  22. CC-A.6.A-22 — Record inclusion grants no dependent-kind membership. viewpointRef resolves under the effective reference scheme to an independently admitted U.Viewpoint; optional view names an independently identified episteme whose U.View membership follows only from exact E.17.0 conformance. Neither field nor a recovery note establishes either membership.