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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:15:11 UTC

A.2.1:9 - Common Anti-Patterns

Anti-patternWhy it failsRepair
Alice is reviewer, used as assignment identityIt names neither species nor occurrence.Recover the direct species and the obtaining occurrence needed by the receiver.
One universal binary assignment relation over U.KindIt admits arbitrary kinds and hides stronger participant laws.Use one exact local assigned-kind domain in every direct species.
Generic assignment plus appointment occurrenceOne world-side episode receives two competing identities.Make the appointment species a subtype of U.SystemRoleAssignment; use its holder projection.
One assignment row reused for every shiftStorage identity collapses repeated occurrences.Distinguish maximal uninterrupted predicate-true intervals.
Assignment proves WorkHolding is confused with dated performance.Use A.13 to identify each actual performer and A.15.1 to admit the Work independently. Add F.6 only if the current use also needs the exact assignment under which that Work was performed; a missing or failed check leaves the Work intact.
Durable RoleEnactment objectIt duplicates Work and attribution.Use A.13 to identify the actual performer and A.15.1 to admit the dated Work independently. Add the exact assignment and F.6 only if the current use must also say under which assignment the Work was performed; do not mint a duplicate occurrence.
Report holds a system-role assignmentAn episteme is made a holder by usefulness.Use its direct evidence, result, source-use, or publication relation.
Optional ContextSlot everywhereUnrelated locality, scope, structure, and locus meanings collapse.Recover the denoted object and declare it only when a direct species truly depends on it.