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

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:05:10 UTC

A.6.C:12 — Relations

  • Uses and is used by

    • Uses A.6.B for L/A/D/E claim classification, atomicity, and cross-quadrant reference discipline.
    • Used by A.6 cluster conformance (“contract unpacking”) as the detailed, reusable form of that discipline.
    • Complements A.6.S (signature engineering): contract unpacking is a common constructor step when turning prose boundaries into publishable signatures.
    • Coordinates with A.6.P families: when “contract or guarantee” wording in a boundary use still leaves a consequential ambiguity after RPR, apply A.6.C to that ambiguity. (A.6.C is not a specialization of A.6.P; A.6.P is relation‑precision, A.6.C is boundary‑contract disambiguation.)

  • Coordinates with

    • A.7 (EntityOfConcern, Description episteme, and carrier) for correct placement of evidence claims.
    • A.15.1 for the exact dated Work occurrence and its §4.6 dispatch to application/result, production, change, evaluation, evidence, delivery/transfer, and acceptance patterns.
    • F.12 (service acceptance) for structuring how promise-level commitments connect to evidence and acceptance windows.
    • E.17 MVPK “no new semantics” rule to prevent publication faces from becoming new contracts.
    • A.2.8.PER for the exact permission-side direct objects; A.6 A6-AW-* and A.6.B classify each atomic claim without treating pattern selection as its quadrant.