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 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 08:00:10 UTC

C.32.ADA:9 - Consequences

ConsequenceBenefitCost
Adequacy is coordinate-based.Review can point to exact repairs instead of vague approval or rejection.Evaluation requires inspecting every coordinate and explaining its value.
Declared use controls stop condition.A decision can be adequate for one use and inadequate for another without contradiction.Teams must state intended use before scoring.
No average is allowed.Weak but critical coordinates stay visible.Some dashboards and summaries need redesign.
Explicit repair conditions and subject-pattern locators are mandatory.Review results become actionable.Reviewers must recover the exact missing assertion and the pattern description containing its definition or constraint.