FPF Reference

    Ethical Mediation and Decision Use

    D.4 · Stable · D-family ethical mediation and decision-use pattern · Part D - Multi-scale Ethics and Conflict Optimization

    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 contains the defining content for 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 InterlevelEthicalConflictDescription from D.3 must support mediation, refusal, a decision, an evidence demand, or a return to causal, assurance, or architecture work.

    Not this pattern when. If the conflict has not yet been described, 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 one exact D.3 conflict-description episteme for an admissible mediation action or bounded decision use while keeping evidence, causality, assurance, architecture, and bias-audit claims with their subject patterns.

    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

    D.4builds onInterlevel Ethical Conflict Structure
    D.4builds onDecision Theory (Decsn-CAL)
    D.4coordinates withBias Audit and Ethical Assurance
    D.4coordinates withEvidence Graph Referring (C-4)
    D.4coordinates withTrust and Assurance Calculus
    D.4coordinates withCausalUse-CAL: Causal-Use Questions, Identification, and Realizability
    D.4coordinates withCross-Scope Architecture Residual Triage
    D.4coordinates withConstraint Validity for Transformation Steps
    D.4coordinates withGate Decisions from Independent Check Results
    D.4explicit referenceInterlevel Ethical Conflict Structure
    D.4explicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    D.4explicit referenceDecision-Useful Advice and Evidence Demands
    D.4explicit referenceEvidence Graph Referring (C-4)
    D.4explicit referenceTemporal Claim Adequacy: State Readings, Temporal Trends, and Intervention-Sensitive Change
    D.4explicit referenceTrust and Assurance Calculus
    D.4explicit referenceBias Audit and Ethical Assurance
    D.4explicit referenceCross-Scope Architecture Residual Triage
    D.4explicit referenceThe Agential Role & Agency Spectrum
    D.4explicit referenceU.Work: Dated Performed Work Occurrence
    D.4explicit referenceSystemRoleAssignment and Performed-Work Attribution Check
    D.4explicit referenceDecision Theory (Decsn-CAL)
    D.4explicit referenceU.SystemRoleAssignment - Contextual System-Role Assignment
    D.4explicit referenceMathematical Lens Use
    D.4explicit referenceCausalUse-CAL: Causal-Use Questions, Identification, and Realizability
    D.4explicit referenceEthical Value Plurality and FPF Boundary
    D.4explicit referenceMultilevel Ethics For System-Holon Work

    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 guides one use of the conflict described by D.3. It does not make FPF a final moral authority. It asks what move is admissible from the current description and what must return to evidence, causality, assurance, architecture, decision, or value framing before action is justified.

    Problem

    A described ethical conflict can still be used badly. The failure is to treat its description, an assurance input, a formula, or an architecture return as if it already selected a compromise, refusal, evidence demand, accepted residual, or bounded decision use.

    Forces

    ForceTension
    Described conflict vs. premature closureA conflict description makes action discussable, but does not by itself decide compromise, refusal, or permission.
    Evidence demand vs. decision pressureWork may need a decision, while the ethical claim still needs stronger evidence, causal analysis, assurance, or architecture return.
    Mediation vs. universal authorityD.4 can guide one bounded use of a described conflict, but cannot become a general decision theory.
    Residual acceptance vs. hidden harmProceeding under residual harm can be admissible only when residuals, the admitted Systems involved, prospective plans or assignment requirements, direct responsibility relations or exact missing governors, and return conditions are explicit. If performance has occurred, its complete Work chain is mandatory.
    Mathematical allocation vs. ethical decisionA formula or optimization can inform a decision, but it is not the ethical decision by itself.

    Solution

    Record an EthicalMediationDecisionUse:

    EthicalMediationDecisionUse:
  conflictDescriptionRef: exact C.2.1 U.Episteme identified through D.3
  affectedEntityOfConcernRef
  affectedSystemRefs?
  valueFrameEditionRefs
  decisionQuestionRef?
  intendedDecisionUse?
  intendedWorkUse?
  claimScopeRef?: U.ClaimScope
  qualificationWindowRef?
  optionRefs
  proposedMediationRefs?
  refusalOrStopCondition?
  evidenceDemandRefs?
  causalReturnRefs?
  assuranceReturnRefs?
  architectureResidualReturnRefs?
  acceptedResidualRefs?
  decisionRecordRefs?
  decisionOrRepairSystemRefs?: independently admitted U.System refs
  localSystemRoleKindRefs?: exact local U.Kind refs
  systemRoleClassificationAssertionRefs?: FinSet(U.EpistemeRef)
  intendedWorkPlanOrCommitmentRefs?: prospective plan or commitment content
  intendedAssignmentRequirementRefs?: prospective requirement content; creates no assignment occurrence
  performedWorkRows?:
    - performerSystemRef: exact U.System
      workOccurrenceRef: exact dated U.Work
      assignmentSpeciesRef: exact directly declared species under U.SystemRoleAssignment
      assignmentOccurrenceRef: obtaining occurrence of assignmentSpeciesRef with actual participant values, applicability, and extent covering the Work
      f6AttributionRef: exact performedUnderAssignment occurrence
      holderEquality: performerSystemRef = assignmentOccurrenceRef.HolderSystemSlot
      methodRef:
      workExtentRef:
      containingSystemRef:
  responsibilityRelationRefs?: exact direct predicate, participants, applicability, and occurrence identity
  responsibilityMissingGovernorRefs?: exact A.6.RCD results
  authorityRelationRefs?: exact direct relation refs
  authorityMissingGovernorRefs?: exact A.6.RCD results
  permissionRelationRefs?: exact direct relation refs
  permissionMissingGovernorRefs?: exact A.6.RCD results
  commitmentRelationRefs?: exact direct relation refs
  commitmentMissingGovernorRefs?: exact A.6.RCD results
  admissibleUse
  inadmissibleOverread
  strongerSourceReturnCondition

    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.

    Name the affected EntityOfConcern and any affected Systems, the value-frame editions, the decision question and options, and the intended decision or Work use. Add ClaimScope and a qualification window when they delimit that use. State the proposed mediation or refusal and any accepted residuals. If evidence, causal adequacy, assurance, architecture residuals, responsibility, permission, or actual Work remains unresolved, return only that question to the pattern that defines it. These values delimit the mediation; a generic context field does not.

    Mediation Moves

    Current situationAdmissible D.4 moveNeighboring subject pattern
    A compromise is proposed but the D.3 description omits a side, affected entity, scope, value frame, consequence, or horizon.Return to D.3 and complete the affected side or tension.D.3
    Harm claim depends on causal effect.Demand the C.28 causal-use evidence value and verdict before ethical decision use.C.28
    Evidence is too weak or outdated for the proposed use.Name the affected claim and use. Use C.11.DUA to compare a feasible evidence request with a narrower use, explicit residual acceptance or refusal; obtain stronger or fresher evidence when the selected use needs it.C.11.DUA; A.10 and C.27 for the evidence and its currentness
    Assurance claim is being used as ethical permission.Keep assurance as an assurance or evidence relation, not moral authorization.B.3, D.5
    Architecture move reduces one residual but creates ethical conflict elsewhere.Return the architecture residual and keep the ethical conflict distinct.C.30.ILC, D.3
    A decision must proceed with residual harm.Record the accepted residual, admitted decision or repair Systems, prospective plan, commitment, permission, authority, or assignment requirements, direct responsibility relations or exact missing governors, evidence limits, and return condition. If Work has actually occurred, recover each precise performer's A.13 core and independently admit the Work under A.15.1; add F.6 only when the decision account also needs exact assignment-bound attribution.C.11, B.3, D.5, A.2.1, A.13, A.15.1, and F.6 as applicable

    When required evidence cannot be obtained, the attempted use remains unsupported. A different bounded use must satisfy its own evidence, ethical and authority conditions. Record accepted residuals under the residual-harm row.

    Archetypal Grounding (Worked Slices)

    Fair-share case. A service outage plan can protect hospitals, households, or industrial customers, but not all at once. The D.3 conflict description connects each affected scope and value concern to its consequence and horizon. D.4 records the mediation use: options, accepted residuals, evidence demand, admitted decision Systems, prospective assignment requirements or commitments, direct decision-responsibility relations or exact missing governors, and return conditions. No assignment or Work is asserted merely because the plan names intended action. If execution occurs, the record adds the complete Work row. A mathematical allocation Method may have a separate C.29 representation or lens-use assertion, but the allocation formula is not the ethical decision, assignment, or responsibility relation.

    Override case. An assurance review says a release has the required technical assurance relation, but the D.3 description shows unresolved harm for a subgroup. D.4 does not let assurance override that conflict. It records whether release is refused, conditioned, delayed for evidence, handled under C.28 causal-use analysis, or allowed with an explicit residual and an independently obtaining responsibility relation or exact missing governor.

    Boundaries

    D.4 does not define the conflict description, bias audit, ethical assurance, architecture residual, causal identification, evidence provenance, or decision theory in general. It defines one ethical use of a conflict already described by D.3.

    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

    Bias riskFailureMitigation
    Conflict description becomes decisionA D.3 description is treated as if it already selected an action.Name the D.4 move and its admissible use.
    Assurance becomes permissionTechnical assurance is read as ethical authorization.Keep assurance as an assurance or evidence relation and record the ethical use separately.
    Formula becomes ethicsAllocation, optimization, or scoring is treated as the ethical decision.Use C.29 for the mathematical lens; use D.4 to record the bounded ethical use without making the pattern an agent or responsible party.
    Residual harm disappearsAction proceeds while residuals, admitted decision or repair Systems, and direct responsibility relations stay unnamed.Name accepted residuals, prospective plans, commitments, permissions, authority and assignment requirements, the admitted direct responsibility predicates or exact missing governors, evidence limits, and return condition. Add the complete Work-attribution basis only when performance has occurred.

    Conformance Checklist

    IDRequirementPurpose
    CC-D4-1An exact conflictDescriptionRef identifies one C.2.1 episteme through D.3, or the use returns to D.3.Prevents mediation without a reidentifiable conflict description.
    CC-D4-2The record names the affected EntityOfConcern, any affected Systems, value-frame editions, decision question and options, intended decision or Work use, and the current admissible move. ClaimScope and qualification window are explicit when they delimit that use.Keeps ethical use explicit without relying on a generic context premise.
    CC-D4-3Evidence, causality, assurance, architecture, and decision claims use their subject patterns.Prevents D.4 from becoming universal decision authority.
    CC-D4-4When proceeding under residual harm, name accepted residuals and admitted Systems; keep any local kind, C.2.1 System-classification assertion episteme, prospective plan or assignment requirement, and actual relation distinct. Every responsibility, authority, permission, or commitment claim has its independently obtaining direct relation or exact A.6.RCD missing governor. Every actual Work row first recovers each precise performer's A.13 core and independently admits the Work under A.15.1; it adds F.6 only when precise assignment-bound attribution is also current.Keeps bounded decision use reviewable without deriving responsibility or performance from an assignment or decision.

    Common Anti-Patterns and How to Avoid Them

    Anti-patternWhat goes wrongRepair
    Decision-ready by mapThe mapped conflict is treated as solved.Choose a D.4 move: mediate, refuse, demand evidence, return, decide with residual, or stop.
    Trump-card levelOne level's value automatically overrides all others.Use D.3 if the level relation or value frame is incomplete; otherwise record the explicit D.4 use.
    Evidence postponementThe team proceeds while saying evidence can be checked after the decision.Demand evidence, causal analysis, assurance, or architecture return before the decision use, unless residual acceptance is explicit.
    Permission by assuranceA passed assurance relation is treated as moral authorization.Keep B.3 assurance and D.4 ethical use distinct.

    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 patterns. 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

    Source linePractical implication for this pattern
    Decision analysis and applied ethicsMediation and decision use need options, refusal, condition, evidence-demand choices, accepted residuals, responsibility, and return conditions, not only a value slogan.
    Safety and assurance practiceAssurance can inform bounded ethical decision use, but does not authorize action under unresolved harm or replace the D.3 conflict description.
    Causal and evidence governanceHarm, benefit, and fairness claims depending on causal effect or weak evidence must use C.28, A.10, or B.3 before ethical decision use.
    FPF mathematical-lens disciplineOptimization, allocation, scoring, Pareto, and threshold reasoning are selected lenses or measurement claims; they do not replace the D.4 ethical-use record or create a universal optimizer.

    Relations

    • Builds on D.3 for the exact conflict-description episteme used by this mediation or decision.
    • Coordinates with D.1 and D.2 when value frame or multilevel entry is incomplete.
    • Coordinates with D.5 when 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, and C.30.ILC when evidence, assurance, decision, causal, mathematical-lens, or architecture-residual claims are current.

    D.4:End

    Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)