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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:05:20 UTC

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

Anti-patternRepair
Fill-all-cards defaultStart with triage and add only the live profile.
Rung label as validity proofRun the common threat screen and cite the actual results.
One support-basis enumKeep data, identification, estimate, sampling, simulation, and transport separate.
Estimate creates identificationRequire an identification or design-based result first.
Graph-only causalityCite the model or diagram, assumptions, and replayable derivation or bound.
Feasibility as performed evidenceKeep the sampling-realizability result separate from a WorkPlan, dated Work, and resulting data.
Work or plan as dataRequire the A.10 path to the resulting sample or data before claiming the empirical regime.
Simulation as realized evidenceUse simulationResultRef and state unsupported realized/interventional use.
Shared context label proves transportName exact causal endpoints, assumptions, and formula.
Support verdict authorizes actionReturn the support result to the downstream decision pattern.
Specialist branch named but not consumablePut its exact result ref in the common component contract and keep its assumptions, limits, uncertainty, and reopen condition with that result.
Ontology dossier as precisionKeep specialist refs behind the ordinary question, threat, and support statement.