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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:30:20 UTC

B.1.4:4.1 - Compact Obligation Rows

ObligationWhat must be namedWhy it matters
Independence and joinsBranch relation refs, join relation refs, and the condition under which branches may be combined.Prevents an ordered aggregate from silently treating dependent branches as independent evidence or work.
Order specificationTotal order, partial order, precedence relation, or another named relation over the selected positions.Keeps order-sensitive claims from being read as unordered collection claims.
Decisive dependency relationThe relation that makes one position, delay, or missing step decisive for the aggregate use.Allows weakest-link claims only when the decisive relation is visible.
Carrier identityThe carrier being followed across phases and the condition under which it remains the same EntityOfConcern.Prevents temporal aggregation from hiding identity change or MHT.
Temporal coverageTime window, phase refs, coverage rule, and non-overlap or overlap policy.Prevents missing phases and double counting.
Chronological disciplineThe rule that separates chronological order, logical order, publication order, and performed-work order.Keeps a document sequence, argument sequence, and work occurrence sequence from substituting for one another.
Monotone characteristicThe exact characteristic that is preserved, bounded, or improved when the aggregate grows.Blocks generic monotonicity claims over an unspecified aggregate.