Jump to text
On this page
Copy and source
Upstream freshness not yet confirmed

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:54:38 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 the characteristics needed for the next warranted repair; add measurement when that use requires it.
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.