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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:15:14 UTC

A.6.RSIR:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
Rename role to position everywhereIt loses real system-role-kind and assignment cases and creates a new umbrella.Start with E.10.ROLE; recover a system-role kind, assignment, direct participant, declaration-local SlotSpec, representation position and correspondence, episteme-use relation, another object, or ordinary prose from the current claim.
Treat interface as one root kindIt merges module, functional, protocol, API, signature, publication, representation, architecture, and boundary-package claims.Recover the governing object first; then apply A.6.M for module-interface, A.6.F for functional port or functional structure, A.6.0 plus A.6.5 for a reusable RelationSignature and its SlotSpecs, C.29 or the exact representation pattern for positions and explicit correspondence, E.17 for publication or API-description cases, A.6.C only when recovered agreement-like, protocol, or SLA wording bundles promise, utterance or publication, governance, Work or consequence, or evidence claims, A.6.P:4.11a when service or service-access wording hides its exact referent or direct relation, A.6.B only for L, A, D, or E statement classification inside a boundary package, or C.30, C.30.ASV, C.30.AD, or C.30.TFS-REL for architecture claims.
Put evidence and status into a system-role assignmentIt gives epistemes a work-facing assignment they do not have.Use evidence-use, source-use, status-use, assurance-use, or publication-use relations under A.10, B.3, F.10, E.17, C.2.1, or C.28 when those relations are current.
Use A.6.5 as relation identitySlot discipline does not say which relation is being asserted.Apply A.6.P or the relation-specific pattern for relation identity; use A.6.5 only for SlotSpecs.
Treat function as the recovered kindFunction-like wording may point to capability, method, work, architecture, mathematical function, quality, or module allocation.Apply A.6.F after RSIR selects function-like recovery.
Keep a quoted source label but use it as governing contentReduced-use wording becomes hidden FPF vocabulary.State the retained source-label use and blocked overread.