Ethical Mediation and Decision Use
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 mediation and decision-use pattern Status: Stable Pattern role: This compact pattern owns the ethical use of an already mapped conflict: mediation, refusal, evidence demand, bounded decision use, and residual handling.
Use this when. Use this pattern when an interlevel ethical conflict structure from D.3 must be used for mediation, refusal, decision, evidence demand, causal return, assurance return, or architecture return.
Not this pattern when. If the conflict structure is not yet mapped, use D.3. If the issue is only value plurality, use D.1. If the issue is only entry recognition, use D.2. If the current work is bias, fairness, impact audit, causal-fairness audit consumption, or ethical assurance, use D.5.
What goes wrong if missed. A mapped ethical conflict is treated as solved, blocked, or decision-ready without naming mediation, refusal, evidence demand, return, accepted residual, or bounded decision use.
What this buys. The practitioner can use a D.3 conflict structure for one admissible mediation action or bounded decision use while keeping evidence, causality, assurance, architecture, and bias-audit claims with their owners.
Once an interlevel ethical conflict is visible, the next risk is premature closure. A team may declare a compromise before evidence is sufficient, turn an assurance input into ethical permission, use one level's value as a trump card, or hide a refusal behind technical language.
Relations
Content
Problem Frame
Once an interlevel ethical conflict is visible, the next risk is premature closure. A team may declare a compromise before evidence is sufficient, turn an assurance input into ethical permission, use one level's value as a trump card, or hide a refusal behind technical language.
D.4 governs the use of the mapped conflict. It does not make FPF a final moral authority. It asks what move is admissible from the current conflict structure and what must return to evidence, causality, assurance, architecture, decision, or value framing before action is justified.
Problem
A mapped ethical conflict can still be used badly. The failure is to treat a conflict structure, assurance input, formula, or architecture return as if it already selected a compromise, refusal, evidence demand, accepted residual, or bounded decision use.
Forces
Solution
Record an EthicalMediationDecisionUse@Context:
The record names the current ethical use of the conflict: mediate, refuse, continue under explicit residual, demand evidence, ask a causal question, ask for assurance, return to architecture, or make a bounded decision.
Mediation Moves
Archetypal Grounding (Worked Slices)
Fair-share case. A service outage plan can protect hospitals, households, or industrial customers, but not all at once. D.3 maps affected scopes and value concerns. D.4 records the mediation use: options, accepted residuals, evidence demand, role assignments for decision responsibility, and return conditions. A mathematical allocation method may be cited through C.29, but the allocation formula is not the ethical decision by itself.
Override case. An assurance review says a release has the required technical assurance relation, but D.3 shows unresolved harm for a subgroup. D.4 does not let assurance override the ethical conflict. It records whether release is refused, conditioned, delayed for evidence, returned to C.28 causal-use analysis, or allowed with explicit residual and responsibility.
Boundaries
D.4 does not own conflict structure, bias audit, ethical assurance, architecture residual, causal identification, evidence provenance, or decision theory in general. It owns the ethical use of a mapped interlevel conflict.
Do not name a mediation move "calculus" unless a mathematical lens is selected and the lens is actually doing work. Do not name a mediation move "operator" unless the current pattern explicitly governs an operation. Most D.4 use is a bounded decision-use record, not a mathematical object.
Bias-Annotation
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
This pattern makes ethical action reviewable without pretending that every conflict has a clean optimum. It preserves refusal, evidence demand, and residual acceptance as first-class outcomes. It also prevents architecture, assurance, or causal evidence from quietly becoming moral permission.
Rationale
D.4 exists because an inspectable ethical conflict still needs a bounded use. Some uses stop work. Some demand evidence. Some return to causal, assurance, or architecture owners. Some proceed under an accepted residual with named responsibility and return conditions. Without this pattern, teams either freeze because conflict exists or move too fast because the conflict was mapped once.
The pattern keeps refusal, evidence demand, and residual acceptance visible as ordinary outcomes. It also prevents formulas, assurance labels, architecture residual repairs, or causal claims from silently becoming moral authorization.
SoTA-Echoing
Relations
- Builds on
D.3for the mapped conflict structure. - Coordinates with
D.1andD.2when value frame or multilevel entry is incomplete. - Coordinates with
D.5when bias, fairness, impact audit, causal-fairness audit consumption, or ethical assurance is current. - Coordinates with
A.10,B.3,C.11,C.28,C.29, andC.30.ILCwhen evidence, assurance, decision, causal, mathematical-lens, or architecture-residual claims are current.
D.4:End
Last Updated: 2026-08-04 — upstream FPF commit 67092138 (github.com/ailev/FPF)