Recognize Ethical Concerns Across Levels and Scopes (Multilevel Ethics)
About this pattern
This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.
How to use this pattern
Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.
Type: D-family ethical entry pattern Status: Stable
Use this when. An action or arrangement may benefit one affected entity while harming another across levels or scopes, or responsibility is assigned across levels.
Not this pattern when. If only the value frame is missing, use D.1. If D.3 has already described the conflict, use that result. If the conflict has to be mediated or used in a decision, use D.4. If the concern is bias, fairness, impact audit, causal-fairness audit consumption, or ethical assurance, use D.5.
What goes wrong if missed. A local improvement is treated as ethically sufficient while another declared level, scope, or affected holon carries the harm.
What this buys. Identify who or what may bear a loss, explain how the affected scopes are related, and choose the question to examine next.
Ethical trouble in system-holon work often appears because the action is good for one level and bad for another. A person may benefit while a team is damaged. A project may benefit while a community pays the cost. A standard may improve coordination while excluding a minority case. A model may improve one metric while moving harm to a less visible scope.
Relations
Content
Problem Frame
Ethical trouble in system-holon work often appears because the action is good for one level and bad for another. A person may benefit while a team is damaged. A project may benefit while a community pays the cost. A standard may improve coordination while excluding a minority case. A model may improve one metric while moving harm to a less visible scope.
Do not force these cases into a fixed ladder such as local, group, ecosystem, planetary. Declare the levels and scopes present in the situation and explain who or what may be affected, including where the scopes overlap or one contains another.
Problem
A change can benefit one affected entity while imposing harm, exclusion or risk elsewhere, or change who is responsible for its consequences. The failure is to infer ethical sufficiency from the local gain without examining consequences for others. When responsibility matters, state its basis; a kind or assignment does not by itself establish that responsibility. Use E.10.ROLE when role wording leaves the relevant object or relation unclear.
Forces
Solution
Start with the proposed action or arrangement and the local gain. If an adequate account of affected parties and consequences already exists, use it. Otherwise follow the changed work, use or dependency from the proposal to the entities that may bear its effects; use A.1.CSD when a consequential bearer or effect path remains unclear. Keep an obtaining relation distinct from a possible consequence and retain an unresolved bearer or path as unresolved.
Name the possible loss and the levels or scopes that make it an ethical concern, then state the next question to settle. Recognition is complete when the affected sides and next use are sufficiently clear; an already qualified D.3 conflict or D.4 decision question can be used.
Use MultilevelEthicsEntry@Context when the practitioner or a recipient needs to recover these connections for comparison or revision. Keep its content in the existing answer or working note when that suffices. Add evidence, value-frame editions, and supporting relations where the stated concern relies on them:
The entry has one job: make the multilevel concern recognizable and choose its next use. It does not require a separate dossier or new inquiry before the concern can be discussed. A proposed inquiry goes through C.11.DUA when its receiving contribution or feasibility is unresolved; conflict description and decision use remain with D.3 and D.4.
Material systems and epistemes can be affected EntitiesOfConcern. For an episteme such as a standard, state which uses and interests make its change ethically relevant.
Recognition Matrix
Boundaries
D.2 recognizes ethical concerns across levels and scopes. Use the corresponding subject method to judge a conflict, mediate it or conduct an audit.
Levels and scopes are declared relations in the situation. If a mathematical lens is needed for scale, frustration, optimization, Pareto comparison, or renormalization-like reasoning, use C.29 and the applicable pattern for the object.
Archetypal Grounding (Worked Slice)
A product team wants to reduce service cost by making a medical device harder to service outside authorized centers. The team expects better manufacturer quality control and lower liability risk. To find who may bear the cost, follow the proposed restriction through the service arrangement: some regions have local repair services but no authorized center; losing the local route may prolong device downtime and reduce patients' timely access.
This is a possible consequence of the restriction, with its likelihood and extent still to be established. The next question is which service restriction, if any, addresses the hazard without imposing avoidable access harm. That question and the connected sides complete the present D.2 recognition; D.3 can describe their tension from this account.
Now suppose a release decision depends on whether a proposed servicing method can leave calibration outside the declared tolerance. A qualified test team can perform the discriminating check before the release window closes, and the release authority needs its result under the applicable rule. Preserve that investigation and the rule's force.
Use C.11.DUA to compare the restriction's protective contribution with access harm, feasible alternatives, delay, and displaced work. D.4 carries the resulting decision, including the authority needed to change a requirement or accept a residual. If the required basis cannot be obtained, the proposed release remains unsupported; a narrower continuation must meet its conditions.
Bias-Annotation
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
Making cross-scope concerns explicit lets the practitioner choose the next question, such as an ethical conflict, an architectural consequence or a need for audit.
Rationale
A change can look technically local while shifting costs, risks or responsibilities across affected entities. Recovering those relations lets the practitioner formulate the ethical question before choosing mediation, an audit or an architectural response.
SoTA-Echoing
For recognizing a transferred consequence, adopt A.1.CSD's tracing of a proposed change through actual relations and supported possible effects, when the affected account is incomplete. Compared with judging only the proposal's local target or assigning priority by level, :2 and the service-restriction case retain the access loss alongside the claimed quality benefit. D.1 supplies the value premise; D.3 and D.4 describe and decide the resulting conflict.
This construction makes the traced concern available for the next question without a fixed level catalogue or a full impact study. Its conclusion covers the bearers and effect paths recovered. Reuse an adequate existing account; reconsider it when a new relation, consequence or value premise changes the affected concern.
Relations
- Builds on
D.1for ethical value frame boundary. - Builds on
A.1,B.1, andC.13for holon, level, scope, and part-whole grounding. - Coordinates with
D.3for the interlevel ethical conflict description and withD.4for mediation or decision use. - Coordinates with
D.5for bias, fairness, impact audit, causal-fairness audit consumption, and ethical assurance. - Coordinates with
C.11.DUAwhen a proposed inquiry or disputed protective requirement needs contribution, feasibility, and burden appraisal. - Coordinates with
A.15,A.3.4,C.16,C.29, andC.30.ILCwhen method, work, transformation, measurement, mathematical lens, or architecture residual claims are current.
D.2:End
Last Updated: 2026-11-12 — this section last modified in upstream FPF commit 1e57ccda (github.com/ailev/FPF)