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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:15:11 UTC

A.6.S:12 - Relations

  • Depends on:

    • A.3.1/A.3.2/A.15/A.15.1/A.15.2 — Method, MethodDescription, WorkPlan, Work, and work-result separation
    • A.7 — Strict Distinction (object ≠ description ≠ carrier; Face ≠ Surface)
    • A.6 — Signature Stack: Classify and Place Boundary Claims
    • A.6.0 — U.Signature
    • A.6.2 — effect-free episteme-arrow discipline, only when a constructor operation uses a mathematical arrow; endpoint facts are read or compared, not changed by the arrow
    • A.1, A.13, and A.15.1 — System admission, the complete actual-performer core including local-kind classification and an obtaining A.2.1 assignment, and independent dated-Work admission; F.6 follows only for precise attribution through that same assignment
    • C.2.1 — episteme identity through claim content, exact EntityOfConcern, and effective ReferenceScheme, with empirical grounding and edition continuity kept as separate direct relations
    • (optional) E.18 — TransformationFlowStructure, when signature-construction work is represented as a transformation-flow structure
    • E.10 and LEX discipline — if the publication uses Plain twins (“SoI”) or shorthands, keep their exact Tech readings recoverable and keep Plain twins out of normative register
    • A.6.3 — U.EpistemicViewing
    • A.6.4 — EntityOfConcern-retargeting arrows, their separate C.2.1 bounded-use assertions, and separate current-case judgements
    • A.6.5 — relation-declaration slot discipline
    • A.6.6 — Base Declaration Discipline
    • A.6.B — Boundary Norm Square & Claim Register discipline
    • E.17 and E.17.0 — MVPK and multi‑view describing

  • Coordinates with: A.6.5 for reused relation-participant or reference operations and A.6.6 for direct base-dependence assertions and optional declaration history; neither vocabulary is mandatory.

  • Constrains: a signature-engineering use only where the relevant meaning change, edition, reference retargeting, view, application, or Work claim is current; one distinction does not make the others mandatory.