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:45:17 UTC

C.30.ILC:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Generic complexity bucketEverything becomes complexity or interlevel conflict.Name declared holon levels or declared scopes, level-bearing structure, residual, and first architecture move.
Structure conflict as interlevel conflictTwo structures are in tension, but no declared holon level, scale window, or coarse-graining relation is recoverable.Use C.30, C.30.ASV, D.3, D.4, C.28, evidence, assurance, or decision patterns as applicable; use C.30.ILC only when the conflict is across declared levels or scopes.
Frustration-as-ontologyFrustration is treated as a new FPF kind, psychological state, physics kind, biology kind, assurance score, or proof.Keep frustration as an entry label; recover FrustrationResidual, conflict carriers, residual-bearing locus, and subject patterns for C.29, evidence, assurance, causal, mediation, or synthesis claims when those claim kinds are being made.
Optimization-as-global-proofA local optimization claim is treated as proof that the whole architecture optimizes one global objective.Record local and wider-scope claims separately; use C.29 only for an admissible mathematical lens with recoverable level mapping or scale mapping and use candidate-generation, comparison, or decision patterns for synthesis and selection.
Measurement-first conflictThe team starts measuring before declaring what is in conflict.Run ILC triage first; apply C.16 or the characteristic pattern governing the characteristic under evaluation only when the measured characteristic is under evaluation.
Risk color as cross-scope decisionA red, yellow, or green risk cell, risk matrix, or maturity score decides the cross-scope architecture move or resource-allocation priority.Recover declared holon levels or declared scopes, structure kind under consideration, the residual, the loss, hazard, or threat relation, selected source, evidence, or relation interpretation, characteristic scale, comparator, gate pattern, and first admissible architecture move; do not treat ordinal risk color as architecture adequacy, evidence sufficiency, causal proof, assurance proof, resource-allocation priority, or gate passage.
Mediation-only conflictA structural residual is treated as ethical mediation with no architecture move.Use D.3 only when an interlevel ethical conflict needs a description and D.4 only when that description is being mediated or used in a decision.
Hidden candidate generationThe residual immediately spawns many designs.State the first admissible move; apply C.32.MLAO and C.32 only when residual-reducing candidate work is being claimed, and apply G.5 only when selected-set result declaration is current.
Scope word without scope recordThe text says level, layer, scale, or scope without a declared field.Recover the declared holon level or declared scope named by value, or demote the phrase to ordinary recognition.