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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:40:20 UTC

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

Anti-patternSymptomWhy it failsHow to avoid or repair
Site-participant-property affordance“The site participant is actionable” with no enactor or coupling framecollapses relationality into monadic property languagepublish site, enactor, action, and coupling frame
Invitation-as-obligation“This calls for rollback” is treated as if rollback is already requiredhides A-classified or D-classified claim status and accountabilityrecover the actual claim and apply its duty or gate rule through A.6.B
Invitation-as-work“The system reacted” is used where only a cue or option existsconfuses offer with executionkeep invitation separate from A.15 and U.Work
MethodDescription as invited MethodEnact(methodDescriptionRef=Runbook) supplies no exact Methodmakes a C.2.1 episteme the world-side way of doingselect exact methodRef -> U.Method; keep the description auxiliary
Viewpoint or view by record inclusiona field name or bundle row is treated as proof of U.Viewpoint or U.Viewbypasses reference resolution and E.17.0 dependent-kind rulesresolve viewpointRef under the effective scheme and establish any view’s conformance independently
Capability-as-invitation“The robot can do X” stands in for a situated affordancedestroys local enactor and site conditionsseparate capability description from action invitation
Latent cue as explanationa model tendency is narrated as if it were already an explicit rationaleoverstates articulation and evidencestate the supported model tendency; use a cue pack or option set only when that form helps the receiving use
Premature automationa cue without required witness records is wired directly into gates or controllers with no explicit hook authoritySourceRef named source or guardcreates unsafe action-to-automation couplingapply the existing controller or gate rule, recover authority and evidence, and use an explicit hook when its interface requires one
ArticulationHint as F proxyhook-explicit is treated as “more formal”recreates a forbidden second formality characteristickeep F in C.2.3; reserve articulation and closure semantics for A.16