A.11.OP:12 - Relations
- Classified by:
E.3as onePragprinciple. 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.11for whether an ontology addition is needed. A useful operational requirement does not by itself require a new ontology value; an admitted value does not by itself justify mandatory work. - Coordinates with:
E.11.PUAandE.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.DUAfor the merits and feasible continuation of an advice or evidence demand, including a single requirement with no live OptionSet;C.11for a current local choice and probe-worthiness; andC.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.13for proxy-to-value repair andE.23for operations inside repeated evaluated improvement. A.11.OP retains the initial action-admission question. - Coordinates with:
A.3.1andA.3.2for Method and MethodDescription identity,A.15.1for dated Work, andA.15.7for next-action choice during ongoing Work. A.11.OP governs design-time admission of the requirement. - Constrained by: applicable law and regulation,
E.5Guard-Rails,A.10reliance boundaries,B.3assurance 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 execution and assurance. Their local arrangements remain local rather than FPF authority.