#Interlevel Ethical Conflict Structure

D.3 · Stable · D-family ethical conflict-structure 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 conflict-structure pattern Status: Stable Pattern role: This compact pattern owns the structure of an interlevel ethical conflict; mediation, decision use, assurance, causal use, and architecture residuals remain with their direct owners.

Use this when. Use this pattern when an ethical conflict spans declared levels or scopes and the conflict structure itself must be made inspectable before mediation, decision, assurance, or architecture return.

Not this pattern when. If only the ethical value frame is missing, use D.1. If only entry recognition is needed, use D.2. If the conflict structure is already mapped and the current question is mediation or decision use, use D.4. If the question is bias, fairness, impact audit, causal-fairness audit consumption, or ethical assurance, use D.5.

What goes wrong if missed. The team debates values or decisions before it has named the levels or scopes, carriers, harms, benefits, evidence, and residuals that actually conflict.

What this buys. The conflict becomes an inspectable structure that D.4, D.5, assurance, causal, and architecture owners can use without guessing.

Interlevel ethical conflict is not just disagreement between people. It may involve a system part and a whole, a person and an organization, one organization and a community, a project and a society, a collection and its members, an episteme family and the decisions it shapes, or an architecture move and the holon levels it affects.

#Relations

#Content

#Problem Frame

Interlevel ethical conflict is not just disagreement between people. It may involve a system part and a whole, a person and an organization, one organization and a community, a project and a society, a collection and its members, an episteme family and the decisions it shapes, or an architecture move and the holon levels it affects.

The central move is structural: name what is in conflict, at which declared levels or scopes, through which methods, work, transformations, role assignments, evidence, value concerns, and consequence horizons. Do not turn the conflict into publication wording, assurance claim, or architecture residual unless that is the current governed object.

#Problem

Interlevel ethical conflict is often debated before it is structured. The failure is to argue over values or decisions while the affected objects, declared levels or scopes, value frames, methods, work, transformations, evidence, uncertainty, thresholds, and consequence horizons remain implicit.

#Forces

#Solution

Record an InterlevelEthicalConflictStructure@Context:

InterlevelEthicalConflictStructure@Context:
  conflictConcernRef
  boundedContextRef
  affectedEntityOfConcernRefs
  declaredLevelOrScopeRefs
  affectedHolonRefs
  affectedEpistemeRefs?
  collectionOrMembershipRelationRefs?
  partWholeRelationRefs?
  roleAssignmentRefs
  interestOrConcernRefs
  valueFrameRefs
  agencyOrResponsibilityThresholdRefs?
  methodOrWorkRefs?
  transformationRefs?
  evidenceRefs
  uncertaintyRefs
  consequenceHorizonRefs
  conflictRelationRefs
  nonConflictOverread
  nextUseOwnerRef

This structure may be represented by a table, graph, formal predicate, narrative case, or another selected description form. The representation is not the conflict itself. If a mathematical lens does work in the claim, cite [C.29](/generated/patterns/C.29); if the publication form changes admissible use, cite [E.17](/generated/patterns/E.17).

#Collection and Episteme Cases

A collection is ethically current only when whole-level characteristics, membership relations, environment-mediated effects, or aggregate consequences matter. Use A.14 for part-whole and membership relation vocabulary and C.13 for constructive grounding. Do not assign responsibility to a collection merely because it has a plural name.

An episteme is ethically current when its claim-bearing structure, source-use relation, publication relation, described EntityOfConcern, or model family changes affected systems or decisions. Use C.2.1 for the episteme slot relation and E.17 for publication claims. Do not turn every ethical conflict over a theory, standard, architecture description, or policy description into a problem about wording.

#Boundaries

#Archetypal Grounding (Worked Slices)

Engineering advice. A consultant improves the effectiveness of a client's harmful project. The conflict is not only "bad client, good method." D.3 maps the client organization, affected public, consultant role assignment, method, work occurrence, responsibility threshold, evidence uncertainty, and consequence horizon. D.4 governs refusal, conditions, escalation, or decision use.

Collection case. A fleet-level optimization reduces maintenance cost but increases failure risk for a small subfleet used in harsher conditions. D.3 names the fleet, subfleet, membership relation, any acting collective system, affected users, evidence set, value concerns, responsibility relations, and consequence horizon separately. Collection membership alone makes neither the fleet a responsible acting whole nor the subfleet its part under another relation; each stronger claim needs its direct owner.

Episteme case. A published architecture description normalizes an interface assumption that excludes an alternative implementation option. The ethical conflict may involve the episteme whole, its source-use relation, affected suppliers, and system consequences. D.3 maps the conflict; C.30.AD governs architecture-description adequacy and E.17 governs publication-use claims.

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

This pattern gives D.4, D.5, B.3, C.28, A.10, C.11, and C.30.ILC a conflict structure they can use without stealing the ethical object. The cost is that conflicts cannot be waved through by a slogan. The gain is that mediation and decision work start from a typed structure rather than from a politically convenient label.

#Rationale

D.3 provides the typed structure that ethical mediation, assurance, causal, architecture, and bias-audit patterns can use. Without it, D.4 receives slogans rather than inspectable conflicts; D.5 receives fairness claims without affected scopes; architecture receives value conflict disguised as residual; and evidence patterns receive claims with no declared consequence horizon.

The pattern therefore focuses on the conflict EntityOfConcern: affected objects, declared levels or scopes, value frames, role assignments, methods, work, transformations, evidence, uncertainty, thresholds, and consequence horizons. It keeps descriptions of the conflict useful but secondary.

#SoTA-Echoing

#Relations

• Builds on D.1 and D.2 for value-frame boundary and multilevel entry.
• Builds on A.1, A.14, B.1, and C.13 for holons, part-whole, membership, collections, and constructive grounding.
• Coordinates with D.4 for mediation and decision use.
• Coordinates with D.5 for bias, fairness, impact audit, causal-fairness audit consumption, and ethical assurance.
• Coordinates with C.2.1 and E.17 for episteme and publication-use claims.
• Coordinates with C.30.ILC, A.10, B.3, C.28, and C.29 when architecture residual, evidence, assurance, causal, or mathematical-lens claims are current.

#D.3:End

Last Updated: 2026-08-05 — upstream FPF commit 3dbce514 (github.com/ailev/FPF)