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

C.32.PAD:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
ADRBeforeDecisionRelationThe team starts from an ADR template and fills prose before the selected option, trade-off, and work consequences are recoverable.Draft ArchitectureDecisionRelation@Project first; then use C.32.ADR only as publication projection.
CandidateWinnerByMetricOne score, benchmark, or eval reading is treated as the architecture decision.Use C.32.ACS, C.32.ACE, C.16, and A.19.CPM; decide only after trade-offs and accepted losses are recorded.
StructureOnlyDecisionThe decision names a target structure but gives no Method-use or work-boundary instruction for the Systems intended to realize it.Add Method-description or pattern-use refs, intended System, optional local kind and independently optional classification judgment, any current assignment species and occurrence or prospective assignment requirement without conflating them, work boundary, readiness exit, and expected structure effect. Add responsibility, authority, permission, or commitment only under its independent direct predicate or exact missing governor. If actual Work is claimed, recover each exact performer through A.13 and let A.15.1 independently admit the U.Work. Add an F.6 ref only when precise assignment-bound attribution is expressly consumed; its absence or failure leaves the Work intact.
MethodOnlyDecisionThe decision says which style, pattern, or tool to use but not which target structures it is expected to produce or preserve.Name the intended selected structures and architecture-characteristic trade-offs; use C.30, C.30.ASV, or C.32 if the structure is not recoverable.
FrozenArchitectureDecisionThe decision has no source-return or reopen condition.Add eval guardrails, source-currentness return, architecture-influence/transformed-side fit trigger, or supersession rule.
LensOrQBundleAsDecisionAuthorityA view, structural-information lens, measurement row, Q-Bundle, or eval reading is treated as if it selected the architecture.Use the exact subject predicate for the source: C.29 for lens use, C.25 for Q-Bundle, C.16 for measurement, C.32.ACE for eval, and PAD for the actual decision relation.
GovernanceByImplicationTeams are expected to follow the decision, but no readiness, gate, evidence, assurance, or governance exit is named.Add refs to the patterns for the next questions; do not import those statuses into PAD.
ProjectSelectionOrRoleByDecisionA PAD field is treated as proof that a project selected a System, or that the System gains a kind, classification, or assignment because the decision names it.Keep the decision designation and every direct fact; recover role wording through E.10.ROLE, apply A.15.6, A.2, and A.2.1 independently, and return missing-substrate[project-selection-conjunction] when the compound truth is needed.
NetworkOrInfluenceByCitationA cited network record, C.32.CONWAY frame or pair row, or PAD decision is treated as a network member, cross-flow occurrence, architecture-influence occurrence, performer, or actual structure effect.Restore the exact E.18.NET network and direct relation patterns, use C.30.TFS-REL for architecture use, and keep expected structure effect modal until C.30 independently establishes the actual architecture relation.