fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 41904–41933

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 05:45:20 UTC

B.2.5:0 - Use This When

Use this pattern when a holon is supervised, regulated, steered, corrected, constrained, or coordinated through a two-sided feedback relation between one supervising acting system and one or more supervised holons. If the supervision is conditioned by a local system-role kind or assignment, recover that classification and exact assignment separately.

The first useful move is to recover the facts supporting the feedback claim:

Which holons are supervised?
Which admitted system supervises these holons for this feedback use, under which policy and during which time window, and which local supervisor system-role kind and exact assignment obtain when that classification matters?
What observation, report, signal, publication, or source relation carries state?
What influence, constraint, objective, mode, or work change returns?
Which rule and case facts couple that return to the observation for each supervised holon?
Which transformation, work, architecture, evidence, assurance, timing,
or causal claim is being made in addition to the relation?

What goes wrong if missed. A control diagram, policy note, dashboard, publication channel, or supervisor word starts carrying part-whole, agency, safety, assurance, timing, gate, or architecture claims that belong elsewhere.

What this buys. B.2.5 gives a readable compound claim: for each named holon, this system receives the stated observation and returns an influence coupled to it under the applicable rule. The observation, influence and coupling facts remain separately governed; the assertion can support a control description without introducing a fused feedback occurrence.

Not this pattern when.

  • If the question is a control-structure view, use C.30.LCA.
  • If the question is architecture or selected structure, use C.30, A.22, and C.30.ASV.
  • If the question is reusable dynamics, timing, rate, or temporal validity, use A.3.3 and C.27.
  • If the question is causal use, use C.28.
  • If the question is evidence, provenance, assurance, or a gate decision, use A.10, G.6, B.3, or A.21 respectively. Use A.20 for its internal-constraint test in a transformation-flow structure; other constraint claims need their direct pattern.
  • If module or interface wording hides the exact claim, use A.6.M to recover it; use the direct pattern for an already precise allocation or commitment claim.
  • If the question is whole reidentification, use B.2.