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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:35:06 UTC

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

  • Planning the whole tool lifecycle. Keep candidate generation, selection, execution, scoring, and publication outside C.24.
  • Route description as Method. Recover the Method or keep the route in probe state.
  • Plan as execution. Put actual burn and call facts in Work-side results and the trace.
  • BLP slogan as comparison. Use C.19.1’s probe and any selected comparison; keep a waiver separate or return no scale claim or no scale-based preference.
  • Catch-all policy or profile ref. Cite the actual PoolPolicyResult, EmitterPolicy, C.19.1 result, B.3 result, or domain-defined constraint, or omit the branch.
  • Confidence threshold as assurance. Use a direct condition and cite B.3 only for a named assurance use.
  • Executable adaptation by implication. Store the binding in a route description; identify any executable adaptation independently.
  • Successful probe as commitment. Require a checkpoint with a commit trigger.