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 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:40:20 UTC

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

Anti-patternSymptomRepair
ScalarModularityScoreA single score claims architecture quality.Replace with ModularityVectorLite, disclosed scoring basis and subject pattern, or report-only boundary.
UntypedMeasureListA table of heads appears without characteristic, scale, declared measurement basis, or repair action.Classify heads and create C.16-compatible cards only where the recovered claim needs them.
MeasurementBeforeRepairThe practitioner is asked for full measurement before one useful move exists.Start with at most three characteristics under evaluation and repair direction.
OpenInterfaceEqualsModularInterface publication is treated as modularity.Apply relation repair through A.6.M and characterize only the interface or substitutability head under evaluation.
ComplexityAsOneCharacteristicAlgorithmic cost, graph-connectivity cost, policy and approval cost, evidence-maintenance cost, and cognitive cost are averaged.Keep residual heads claim-scoped and apply lens or measurement patterns when those uses are being made.
ProxyBecomesValueA report-only proxy becomes a beyond-local-repair claim.State forbidden use and use the subject pattern before relying on that claim.