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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

A.11.OP:12 - Relations

  • Classified by: E.3 as one Prag principle. It primarily advances P-1 Cognitive Elegance, P-7 Pragmatic Utility, P-10 Open-Ended Evolution, and P-11 State-of-the-Art Alignment while respecting the other Pillars.
  • Coordinates with: A.11, which governs admission of ontology additions. Namespace adjacency makes the two parsimony questions discoverable; their EntitiesOfConcern remain distinct.
  • Coordinates with: E.11.PUA and E.11.PUR, which govern use, recommendation, coordination, and reuse after a pattern has been selected. A.11.OP asks whether an extra mandatory requirement belongs in the first place.
  • Coordinates with: C.11.DUA for the merits and feasible continuation of an advice or evidence demand, including a single requirement with no live OptionSet; C.11 for a current local choice and probe-worthiness; and C.19.2, A.19, and Method Engineering for their apparatus, architecture or Method comparisons. A.11.OP supplies the contribution screen. These direct owners complete the applicable demand, selection or configuration question.
  • Coordinates with: E.13 for proxy-to-value repair and E.23 for operations inside repeated evaluated improvement. A.11.OP retains the initial action-admission question.
  • Coordinates with: A.3.1 and A.3.2 for Method and MethodDescription identity, A.15.1 for dated Work, and A.15.7 for next-action choice during ongoing Work. A.11.OP governs design-time admission of the requirement.
  • Constrained by: applicable law and regulation, E.5 Guard-Rails, A.10 reliance boundaries, B.3 assurance floors, and any other direct subject or authority pattern for the use.
  • Consumed by: Method Engineering and other DPFs when they decide whether domain-specific requirements or support apparatus deserve mandatory status. Those frameworks retain their domain decisions and evidence.
  • May be specialized by: local practice frameworks for concrete execution and assurance. Their local arrangements remain local rather than FPF authority.