Conflict Of Interest Mitigation

Prevent competing interests from compromising entrusted judgment through timely disclosure, independent assessment, proportionate mitigation, recusal or structural separation, verification, and remedy.

Essence

Conflict-of-Interest Mitigation protects entrusted judgment when a person or institution has another interest that could pull against the duty attached to a role. The archetype is not a character test and does not assume that an interest proves corruption. It supplies a governed way to identify a relevant interest, trace how it could influence a particular matter, classify the risk independently, interrupt the influence path with a proportionate control, preserve a competent decision path, and repair the outcome if the control fails.

The central unit of analysis is not “a person with interests.” It is a relationship among four things:

• an entrusted role and the duty or beneficiary that gives the role its purpose;
• a specific matter, decision stage, information set, or continuing portfolio;
• a financial, relational, professional, political, intellectual, competitive, or dependency interest; and
• a plausible influence path from that interest to judgment, access, recommendation, implementation, review, or public confidence.

An interest is therefore relevant only in context. Owning a small amount of stock may be immaterial for one policy discussion and material for a procurement decision the owner can shape. A family relationship may be harmless in ordinary operations and disqualifying in a hiring panel. A strong scholarly view is not automatically a conflict, yet sponsorship, rivalry, access to unpublished work, or responsibility for reviewing one's own result may create one. Institutional revenue, appointment power, data dependence, reputation, or future employment can create conflicts even when no individual receives a direct payment.

The archetype uses a control hierarchy. Disclosure is the input to review, not a cure. When notice and monitoring adequately reduce risk, stronger restrictions are unnecessary. When the actor can influence agenda, evidence, criteria, access, deliberation, recommendation, approval, implementation, or appeal, mitigation must cover those stages. Persistent conflicts may require information barriers, transfer of duties, compensation changes, divestiture, role redesign, organizational separation, or disqualification. Each control must have an owner, evidence, an alternate decision route, a duration, and a residual-risk test.

The canonical operating loop is:

1. Define the role, duty, beneficiary, matter, and real decision stages.
2. Collect only the interests and relationships relevant to those duties and matters.
3. Trigger disclosure before participation and again when facts materially change.
4. Map affected parties and the channels through which the interest could influence the result.
5. Distinguish actual, potential, apparent, and nonmaterial conflicts using recorded facts.
6. Assess consequence, proximity, discretion, dependency, information advantage, likelihood, and reversibility.
7. Screen the reviewer and route the case to an authority independent of the same interest.
8. Select the least restrictive control that reduces residual risk to the accepted level.
9. Transfer excluded rights, restrict access, and name a competent alternate so the decision can continue.
10. Govern any necessary exception with a written necessity finding, compensating safeguards, and expiry.
11. Preserve a privacy-tiered reason record, notice, correction, and challenge path.
12. Verify implementation, investigate credible breaches, remedy tainted decisions, and recertify the regime.

The desired result is trustworthy judgment, not maximum disclosure, maximum exclusion, or maximum punishment. A sound design permits expertise, representation, and ordinary private interests while making divided loyalty visible and governable. It also recognizes that public confidence is an operational outcome: a substantively correct decision can still fail if an informed affected party cannot see how impartiality was protected.

Compression statement

Conflict-of-Interest Mitigation governs the gap between having an interest and allowing that interest to compromise a duty. It defines the role and beneficiary, inventories only relevant interests and relationships, links them to a matter and its affected parties, and triggers disclosure before influence occurs. An independent authority classifies actual, potential, and apparent conflicts and assesses materiality through influence channels rather than a single monetary threshold. A declared hierarchy then selects controls: notice, monitoring, restriction, recusal, information barriers, transfer, divestiture, role redesign, or disqualification. Every control preserves decision continuity and is verified. Narrow exceptions protect scarce expertise, representation, emergencies, and rights, but carry necessity findings, compensating safeguards, and expiry. Records support proportionate transparency, challenge, enforcement, remedy, and learning without publishing irrelevant private facts. The design treats disclosure as input, not cure; recusal as a scoped rights transfer, not absence from a final vote; and independence as an operational property, not a label.

Canonical formula: conflict_integrity = clarity(role,duty,matter) + completeness(relevant_interests,influence_paths) + independence(classification,mitigation,verification) + effectiveness(control,continuity,remedy) - residual_risk(concealment,proxy_influence,capture,appearance,retaliation,overrestriction); escalate the mitigation hierarchy until residual risk is accepted by an independent authority.

When to Use This Archetype

Use this archetype when an actor or institution is entrusted to decide, advise, allocate, evaluate, regulate, investigate, procure, publish, treat, represent, audit, certify, or review, and another interest may materially affect—or reasonably appear to affect—performance of that duty. It is especially useful when influence occurs before a final vote, when sensitive information itself creates value, when the interested party can shape criteria or evidence, or when the organization reviewing the conflict shares the same institutional incentive.

Strong use signals include:

• evaluators, approvers, advisors, or implementation owners have ties to an applicant, vendor, subject, sponsor, competitor, or beneficiary;
• a regulator or standards body depends on the industry it oversees for funding, information, appointments, expertise, or future employment;
• a board member, fiduciary, trustee, or executive participates in a related-party matter or serves principals whose interests diverge;
• a researcher, peer reviewer, clinician, journalist, auditor, certifier, or technical evaluator holds sponsorship, ownership, collaboration, rivalry, referral, publication, or product interests relevant to the matter;
• a gift, outside role, family relationship, campaign interest, investment, consulting engagement, board seat, debt, or employment negotiation changes during an active decision;
• a person has formally recused but still controls the agenda, selects evidence, briefs the substitute, retains system access, or directs implementation;
• leadership, revenue, legal exposure, or reputation makes an internal reviewer unable to assess the matter independently;
• the same exception, sponsor, counterparty, or reviewer pattern recurs, suggesting institutional rather than isolated risk;
• an affected party can plausibly question impartiality even though no improper action has been proven;
• an existing disclosure or mitigation plan is stale because ownership, access, duties, relationships, or decision scope changed.

Use the full archetype when several decision stages or control types must work together. A simple one-time, low-consequence matter may need only a short disclosure, independent materiality check, recorded decision, and monitoring. A high-consequence procurement, enforcement action, clinical choice, grant review, related-party transaction, or safety evaluation may require beneficial-owner matching, full lifecycle recusal, least-privilege access, an independent panel, alternate authority, communication controls, retrospective testing, and a decision-remedy rule.

The archetype also applies to institutions. An agency can be conflicted by appropriations, industry data dependence, revolving-door labor markets, or political appointment. A university can be conflicted by sponsor revenue or reputational exposure. A platform can be conflicted when its safety evaluator reports to a product-launch owner. A nonprofit can be conflicted by donor restrictions or a board member's related vendor. The question is not whether the institution has a conscience; it is whether incentives, authority, information, and review are sufficiently separated to protect the governing duty.

Do not invoke the archetype merely because people disagree, possess expertise, have values, or are affected by a decision. Perspective and stake can be legitimate sources of knowledge and representation. A conflict exists only when a competing interest bears on an entrusted duty in a defined matter through a plausible influence path. When the issue is ordinary disagreement, general process fairness, weak evidence, access control, incentive design, or abuse of authority without divided loyalty, use the appropriate neighboring archetype instead.

A practical intake test asks six questions:

1. What is the role, and to whom or what is the duty owed?
2. What matter and decision stages can the role holder influence in practice?
3. What other interest or relationship could pull judgment, access, or loyalty?
4. Through what concrete path could that interest affect consequence or confidence?
5. Who can assess the risk without sharing it?
6. What control would break the path while preserving a competent and legitimate decision?

If these questions cannot be answered, first clarify roles, decision rights, scope, and evidence. If they can be answered and reveal a material competing interest, the archetype is appropriate.

Structural Problem

Conflict-of-interest failures are usually structural before they are personal. Organizations assign people multiple roles, rely on small expert communities, mix public and private incentives, concentrate information, and create funding or appointment dependencies. They then ask individuals to recognize and neutralize the resulting risk through a disclosure form or a promise to be objective. This arrangement leaves the interested actor to define the matter, interpret materiality, decide whether to report, select the mitigation, and sometimes verify compliance. The control shares the conflict it is meant to govern.

Several structural pathways recur.

The final-vote illusion

Formal rules often focus on approval or voting. Influence, however, begins earlier and continues later. A person may place an item on the agenda, narrow the options, select evaluators, define technical criteria, choose evidence, control access, frame risk, negotiate terms, lobby colleagues, appoint the substitute, direct implementation, or review a challenge. Leaving the room for the vote does not interrupt these paths. Effective recusal must be scoped across the whole decision lifecycle.

Information as a benefit

A conflicted actor may gain from privileged bid, personnel, market, enforcement, clinical, research, or product information even without deciding the matter. Removing approval rights while leaving shared drives, assistants, meeting invitations, dashboards, or informal briefings intact fails to control the risk. Information firewalls need technical permissions, procedural boundaries, communication rules, exception approval, logs, and breach response.

Reviewer dependence

The nominal ethics officer, manager, committee, auditor, or board can share the same sponsor, reporting line, funding source, reputation, appointment path, or legal exposure. Formal separation is not enough. Reviewer independence depends on who appoints and can remove the reviewer, whether the reviewer has protected resources and evidence access, whether findings are binding or merely advisory, and where the reviewer can escalate a conflict involving its own authority.

Institutional conflict hidden inside individual forms

Individual registers miss interests held by the organization: revenue concentration, donor restrictions, product incentives, grant overhead, enforcement targets, industry data access, political sponsorship, litigation exposure, or future labor markets. An institution may pressure individuals without any one person owning the interest. Recusing a person while preserving the institutional incentive changes the name on the decision, not the influence architecture.

Intervention Logic

The intervention follows a staged control loop. Each stage produces an explicit object that the next stage can inspect. The sequence may be implemented through forms and workflow, but its core is governance rather than software.

Stage 1: Establish role, duty, and matter

State what decision or activity is in scope, who has formal and de facto influence, which beneficiary or public purpose governs, and when the duty begins and ends. Include agenda, evidence, criteria, access, recommendation, approval, implementation, oversight, and appeal. Map shadow decision makers such as chiefs of staff, assistants, sponsors, technical advisors, and people who control assignments or information.

The output is a decision-role map. If the role or duty is undefined, a reviewer cannot distinguish a conflict from ordinary stakeholder interest. If the matter is defined too narrowly, linked transactions or downstream implementation can evade control. If it is defined too broadly, people can be excluded indefinitely from unrelated work.

Stage 4: Classify and assess influence

Classify the conflict as actual, potential, apparent, or not material. An actual conflict presently pulls against the duty or compromises the person's ability to act. A potential conflict could foreseeably become active as facts or roles change. An apparent conflict would cause an informed reasonable observer to question impartiality even without proof of altered behavior. A nonmaterial interest has no plausible or consequential influence path for the defined matter.

Then assess materiality. Examine the value or importance of the interest, proximity to the matter, discretion over the result, control over information, dependence on a counterparty, consequence to affected people, substitutability of the actor, duration, probability, reversibility, and cumulative pattern. Record evidence, uncertainty, and what new fact would change the classification.

Stage 5: Secure independent review

Screen the reviewer for the same matter. Independence requires separation from the interested person, sponsor, management chain, counterparty, funding dependency, and threatened reputation. The reviewer needs competence, access to underlying evidence, authority to impose or escalate controls, a recusal path, protection from retaliation, and a route for conflicts involving senior leadership or the governing body.

For routine low-risk cases, a trained conflict officer may decide. High-consequence, contested, institutional, senior, or reviewer-level conflicts may require an independent committee, external member, audit function, court-like forum, or regulator. The design should avoid both managerial self-certification and a centralized ethics bottleneck that cannot meet service targets.

Stage 6: Select a proportionate mitigation

Choose the least burdensome effective control, escalating until residual risk is accepted independently. The hierarchy commonly moves through:

1. documented no-conflict or nonmaterial finding;
2. disclosure to relevant participants or affected parties;
3. monitoring, supervision, or additional review;
4. restriction from selected tasks, contacts, criteria, evidence, or information;
5. scoped recusal with decision-right transfer;
6. information firewall and communication boundaries;
7. reassignment, compensation change, reporting separation, or role redesign;
8. divestiture, relinquishment, blind management, cooling-off, or structural separation;
9. disqualification, prohibition, or stopping the decision.

Controls can be combined in a conflict management plan. Each plan states the influence path, control bundle, owners, evidence, alternate, milestones, communications, residual-risk threshold, expiry, and review trigger. Disclosure-only responses must explain why notice interrupts the material path. Recusal-only responses must show how agenda, information, informal influence, implementation, and review are controlled.

Stage 7: Preserve decision continuity

Every removed right needs a named competent alternate. Transfer decision, recommendation, access, implementation, and review rights explicitly. Provide the alternate with independent resources and prohibit shadow instruction. Record accidental exposure and define when ordinary rights resume. If no safe alternate exists and the decision is urgent, use the exception process rather than allowing covert participation.

Stage 8: Govern exceptions

An exception requires evidence that exclusion would defeat a legal entitlement, protected representation, quorum, scarce expertise, urgent safety need, or service-continuity obligation. Limit participation to what is necessary—for example, factual briefing without deliberation or a nonbinding technical opinion. Add counterexperts, an independent chair, balanced membership, disclosure, separate approval, recording, enhanced review, or post-decision audit. Set an expiry and prohibit automatic renewal.

Stage 9: Record, communicate, verify, and remedy

Preserve the existence and type of interest, classification, reviewer independence, mitigation, rationale, recusal or exception, implementation evidence, dissent, and challenge path. Use privacy tiers: an affected party may need to know that a financial or relational conflict was independently reviewed and controlled without receiving account numbers or irrelevant family details.

Verify the actual control. Check access changes, meeting participation, communications, alternate authority, ownership transfer, structural completion, exception expiry, and decision evidence proportionately. Investigate credible breaches through an independent, fair process. If a breach could affect the outcome, review the decision itself. Possible remedies include repeating an evaluation, replacing a reviewer, reopening a bid, rescinding or ratifying a transaction through an unconflicted process, correcting a publication, notifying patients, compensating harm, returning funds, changing policy, or referring suspected corruption to specialized authorities.

Key Components

Component	Description
Decision Role and Fiduciary Duty ↗	Without a declared role and beneficiary, an interest cannot be evaluated as conflicting, and ordinary expertise or stakeholder participation can be mistaken for disqualifying bias. Semantic canonical mapping retained the complete legacy component record: {"slug":"decision_role_and_fiduciary_duty","name":"Decision Role and Fiduciary Duty","component_type":"role_and_duty_boundary","definition":"Defines the decision, advisory, review, procurement, oversight, research, or representation role whose judgment must be protected, including the duty owed and the people whose interests govern.","purpose":"Without a declared role and beneficiary, an interest cannot be evaluated as conflicting, and ordinary expertise or stakeholder participation can be mistaken for disqualifying bias.","required_fields":["decision_or_matter","role_holder","formal_and_de_facto_authority","duty_and_beneficiary","decision_stage","term_and_jurisdiction","delegation_limits","role_owner"],"validation_questions":["Which duty is vulnerable?","Who can shape the outcome without signing it?","Whose interests must prevail?","Does the duty continue after formal service ends?"],"failure_signals":["undefined_duty","shadow_decider","nominal_independence","post_role_influence"],"safeguards":["plain_language_mandate","de_facto_authority_map","beneficiary_review","role_exit_controls"],"implementation_notes":"Implement Decision Role and Fiduciary Duty as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Interest and Relationship Inventory ↗	A usable inventory turns vague ethics expectations into reviewable facts while avoiding indiscriminate collection of private information unrelated to a decision. Semantic canonical mapping retained the complete legacy component record: {"slug":"interest_and_relationship_inventory","name":"Interest and Relationship Inventory","component_type":"disclosure_inventory","definition":"Maintains a proportionate inventory of financial, professional, familial, political, intellectual, competitive, and dependency relationships that could create divided loyalty or influence.","purpose":"A usable inventory turns vague ethics expectations into reviewable facts while avoiding indiscriminate collection of private information unrelated to a decision.","required_fields":["covered_persons","interest_categories","relationship_categories","value_or_dependency_band","counterparty","start_and_end_dates","privacy_classification","update_owner"],"validation_questions":["Are indirect and beneficial interests included?","Can a dependency matter without money changing hands?","Is the inventory current at decision time?","Is irrelevant private information minimized?"],"failure_signals":["omitted_indirect_interest","stale_register","privacy_overcollection","relationship_blind_spot"],"safeguards":["beneficial_ownership_attestation","purpose_limitation","secure_register","event_driven_update"],"implementation_notes":"Implement Interest and Relationship Inventory as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Conflict Scope and Affected-Party Map ↗	Conflicts are matter-specific. This map prevents both blanket exclusion and artificially narrow scoping that ignores linked decisions or affected beneficiaries. Semantic canonical mapping retained the complete legacy component record: {"slug":"conflict_scope_and_affected_party_map","name":"Conflict Scope and Affected-Party Map","component_type":"scope_and_impact_boundary","definition":"Connects the role and disclosed interests to the exact matter, counterparties, alternatives, affected parties, rights, resources, and downstream decisions that could be influenced.","purpose":"Conflicts are matter-specific. This map prevents both blanket exclusion and artificially narrow scoping that ignores linked decisions or affected beneficiaries.","required_fields":["matter_scope","linked_matters","counterparties","affected_parties","decision_rights","resource_or_rights_at_stake","temporal_scope","scope_reviewer"],"validation_questions":["Could the interest affect agenda setting, evidence, criteria, or implementation?","Which linked matters inherit the risk?","Who bears harm without standing?","When does the conflict cease to be material?"],"failure_signals":["scope_fragmentation","affected_party_omission","agenda_influence_hidden","permanent_overbreadth"],"safeguards":["linked_matter_test","affected_party_check","independent_scope_confirmation","expiry_rule"],"implementation_notes":"Implement Conflict Scope and Affected-Party Map as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Disclosure Trigger and Update Rule ↗	Conflict management fails when disclosure is optional, late, addressed to the wrong recipient, or treated as a one-time form rather than a continuing duty. Semantic canonical mapping retained the complete legacy component record: {"slug":"disclosure_trigger_and_update_rule","name":"Disclosure Trigger and Update Rule","component_type":"event_driven_disclosure_control","definition":"States who must disclose what, to whom, by when, and upon which appointment, transaction, relationship, gift, role change, new information, or recurring certification event.","purpose":"Conflict management fails when disclosure is optional, late, addressed to the wrong recipient, or treated as a one-time form rather than a continuing duty.","required_fields":["covered_actor","trigger_event","disclosure_content","recipient","deadline","material_change_threshold","recertification_interval","non_disclosure_consequence"],"validation_questions":["Does disclosure precede influence?","Can observers report an undisclosed conflict safely?","Are changes captured between annual forms?","Is innocent uncertainty distinguished from concealment?"],"failure_signals":["late_disclosure","annual_form_only","wrong_recipient","silent_noncompliance"],"safeguards":["predecision_attestation","event_notification","protected_reporting","graduated_enforcement"],"implementation_notes":"Implement Disclosure Trigger and Update Rule as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Actual, Potential, and Apparent Conflict Classification ↗	The three-part taxonomy supports proportionate action and protects legitimacy without claiming that every appearance proves corruption or that unproven influence can be ignored. Semantic canonical mapping retained the complete legacy component record: {"slug":"actual_potential_apparent_conflict_classification","name":"Actual, Potential, and Apparent Conflict Classification","component_type":"conflict_taxonomy","definition":"Classifies whether an interest presently impairs duty, could foreseeably impair it, or would reasonably undermine confidence even if no improper action can be shown.","purpose":"The three-part taxonomy supports proportionate action and protects legitimacy without claiming that every appearance proves corruption or that unproven influence can be ignored.","required_fields":["classification","factual_basis","reasonable_observer_test","timing","probability","severity","confidence","reviewer"],"validation_questions":["Is the interest active now or contingent?","Would an informed reasonable observer question impartiality?","What evidence would change the class?","Is stigma avoided while risk is controlled?"],"failure_signals":["actual_conflict_minimized","appearance_weaponized","potential_risk_ignored","classification_without_evidence"],"safeguards":["documented_reasoning","neutral_language","evidence_threshold","appeal_or_reconsideration"],"implementation_notes":"Implement Actual, Potential, and Apparent Conflict Classification as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Materiality and Influence Assessment ↗	Materiality separates trivial interests from conflicts requiring removal and makes mitigation proportional to both decision consequence and the actor’s real influence. Semantic canonical mapping retained the complete legacy component record: {"slug":"materiality_and_influence_assessment","name":"Materiality and Influence Assessment","component_type":"risk_assessment","definition":"Assesses the magnitude, likelihood, proximity, discretion, information advantage, dependency, substitutability, and reversibility through which an interest could distort judgment or public confidence.","purpose":"Materiality separates trivial interests from conflicts requiring removal and makes mitigation proportional to both decision consequence and the actor’s real influence.","required_fields":["interest_magnitude","decision_consequence","influence_path","discretion_level","information_asymmetry","dependency","reversibility","residual_risk"],"validation_questions":["Can the person set criteria or control information?","Would the outcome materially affect the interest?","Is influence direct, indirect, or cumulative?","Can harm be corrected after the decision?"],"failure_signals":["dollar_threshold_only","formal_vote_only","dependency_ignored","cumulative_influence_missed"],"safeguards":["multi_factor_matrix","influence_channel_map","independent_scoring","tail_risk_override"],"implementation_notes":"Implement Materiality and Influence Assessment as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Confidentiality and Safe Reporting Channel ↗	People disclose sensitive relationships only when information is protected and uncertainty can be raised without punishment; secrecy, however, cannot become immunity from accountable review. Semantic canonical mapping retained the complete legacy component record: {"slug":"confidentiality_and_safe_reporting_channel","name":"Confidentiality and Safe Reporting Channel","component_type":"protected_information_channel","definition":"Provides secure disclosure, advice, correction, and third-party reporting channels with need-to-know access, privacy limits, anti-retaliation protections, and a path for urgent concerns.","purpose":"People disclose sensitive relationships only when information is protected and uncertainty can be raised without punishment; secrecy, however, cannot become immunity from accountable review.","required_fields":["intake_channel","authorized_recipients","confidentiality_limit","retention_rule","anti_retaliation_rule","anonymous_option","urgent_path","breach_response"],"validation_questions":["Can someone seek advice before a breach?","Who may access raw disclosure data?","What must be revealed to affected parties?","How are malicious allegations handled?"],"failure_signals":["retaliation","confidentiality_promise_overreach","data_leak","anonymous_claim_abuse"],"safeguards":["need_to_know_access","protected_advice","minimum_necessary_notice","allegation_triage"],"implementation_notes":"Implement Confidentiality and Safe Reporting Channel as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Independent Conflict Review Authority ↗	Self-assessment and supervisor-only review are unreliable when the same incentives shape the reviewer. Independence must include appointment, information access, authority, and protection from retaliation. Semantic canonical mapping retained the complete legacy component record: {"slug":"independent_conflict_review_authority","name":"Independent Conflict Review Authority","component_type":"independent_governance","definition":"Assigns a competent reviewer or panel sufficiently separate from the conflicted person, sponsor, management chain, and interested counterparties to classify and resolve conflicts.","purpose":"Self-assessment and supervisor-only review are unreliable when the same incentives shape the reviewer. Independence must include appointment, information access, authority, and protection from retaliation.","required_fields":["reviewer_identity","appointment_basis","independence_test","competence","access_rights","decision_authority","recusal_rule","escalation_path"],"validation_questions":["Who reviews the reviewer?","Can the authority obtain underlying evidence?","Is it funded or appointed by an interested actor?","Can it impose or only recommend controls?"],"failure_signals":["reviewer_conflict","nominal_independence","insufficient_access","advisory_only_theater"],"safeguards":["reviewer_recusal","external_member","protected_budget","binding_authority_or_escalation"],"implementation_notes":"Implement Independent Conflict Review Authority as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Mitigation Hierarchy and Selection Rule ↗	A hierarchy prevents both symbolic disclosure-only responses and reflexive exclusion. Selection is tied to influence paths, consequence, feasibility, rights, expertise scarcity, and residual legitimacy risk. Semantic canonical mapping retained the complete legacy component record: {"slug":"mitigation_hierarchy_and_selection_rule","name":"Mitigation Hierarchy and Selection Rule","component_type":"proportionate_control_selection","definition":"Selects the least burdensome control that reduces residual risk to an accepted level, moving from disclosure and monitoring through restriction, recusal, separation, divestiture, reassignment, or disqualification.","purpose":"A hierarchy prevents both symbolic disclosure-only responses and reflexive exclusion. Selection is tied to influence paths, consequence, feasibility, rights, expertise scarcity, and residual legitimacy risk.","required_fields":["available_controls","selection_criteria","necessity_test","proportionality_test","residual_risk_target","implementation_owner","duration","review_trigger"],"validation_questions":["Does the control block the actual influence path?","Is a less restrictive control equally effective?","Does expertise scarcity justify limited participation?","Who verifies the control works?"],"failure_signals":["disclosure_as_cure","overbroad_ban","control_mismatch","paper_mitigation"],"safeguards":["control_ladder","residual_risk_test","rights_impact_review","verification_plan"],"implementation_notes":"Implement Mitigation Hierarchy and Selection Rule as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Recusal and Decision-Rights Transfer ↗	Recusal is ineffective if it covers only the final vote, leaves informal influence intact, or creates an unowned decision. A transfer contract preserves continuity and records the boundary. Semantic canonical mapping retained the complete legacy component record: {"slug":"recusal_and_decision_rights_transfer","name":"Recusal and Decision-Rights Transfer","component_type":"recusal_and_continuity","definition":"Removes the conflicted actor from specified agenda, information, deliberation, recommendation, approval, implementation, or review rights and transfers each right to a competent alternate.","purpose":"Recusal is ineffective if it covers only the final vote, leaves informal influence intact, or creates an unowned decision. A transfer contract preserves continuity and records the boundary.","required_fields":["recusal_scope","trigger","excluded_activities","alternate_decider","authority_transfer","communication_limit","return_condition","recusal_record"],"validation_questions":["Does recusal include agenda and evidence shaping?","Can the alternate act independently and competently?","Who handles accidental exposure?","When may ordinary rights resume?"],"failure_signals":["vote_only_recusal","proxy_influence","decision_vacuum","indefinite_exclusion"],"safeguards":["full_lifecycle_scope","named_alternate","meeting_and_access_controls","expiry_and_reentry_review"],"implementation_notes":"Implement Recusal and Decision-Rights Transfer as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Information Firewall and Access Control ↗	Interests often create harm through privileged information even when the person does not decide. Firewalls require technical, procedural, spatial, and behavioral controls with observable exceptions. Semantic canonical mapping retained the complete legacy component record: {"slug":"information_firewall_and_access_control","name":"Information Firewall and Access Control","component_type":"information_separation","definition":"Restricts sensitive case, bid, personnel, market, research, enforcement, or deliberative information so a conflicted interest cannot exploit or shape it while preserving necessary operational access.","purpose":"Interests often create harm through privileged information even when the person does not decide. Firewalls require technical, procedural, spatial, and behavioral controls with observable exceptions.","required_fields":["protected_information","conflicted_population","access_policy","technical_controls","communication_protocol","exception_approval","monitoring","breach_response"],"validation_questions":["Can informal channels bypass the firewall?","Are role changes reflected promptly?","Does the restriction preserve needed service?","Are access exceptions logged and reviewed?"],"failure_signals":["shared_inbox_bypass","stale_permissions","oral_side_channel","blanket_denial"],"safeguards":["least_privilege","segregated_workspace","communication_attestation","access_log_review"],"implementation_notes":"Implement Information Firewall and Access Control as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Divestiture, Separation, or Role Redesign ↗	Persistent conflicts require structural action. A one-time recusal does not fix incentives embedded in compensation, ownership, dual roles, funding, governance seats, or organizational dependency. Semantic canonical mapping retained the complete legacy component record: {"slug":"divestiture_separation_or_role_redesign","name":"Divestiture, Separation, or Role Redesign","component_type":"structural_mitigation","definition":"Changes ownership, reporting, compensation, duties, staffing, sponsorship, or institutional structure when disclosure, recusal, and firewalls cannot adequately remove continuing influence or dependency.","purpose":"Persistent conflicts require structural action. A one-time recusal does not fix incentives embedded in compensation, ownership, dual roles, funding, governance seats, or organizational dependency.","required_fields":["structural_source","redesign_options","ownership_or_compensation_change","role_change","separation_boundary","transition_plan","hardship_assessment","verification"],"validation_questions":["Can the interest be relinquished or placed beyond control?","Would reassignment merely move the conflict?","Does separation create service or rights harm?","Is the new structure independently verified?"],"failure_signals":["nominal_divestiture","friendly_transfer","role_title_only_change","dependency_persistence"],"safeguards":["beneficial_control_test","cooling_off_period","independent_transition_review","ongoing_attestation"],"implementation_notes":"Implement Divestiture, Separation, or Role Redesign as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Exception Necessity and Proportionality Rule ↗	Rigid conflict rules can disenfranchise affected groups, eliminate scarce expertise, or halt urgent decisions. Exceptions must not become convenience waivers or secret permissions. Semantic canonical mapping retained the complete legacy component record: {"slug":"exception_necessity_and_proportionality_rule","name":"Exception Necessity and Proportionality Rule","component_type":"bounded_exception_governance","definition":"Allows narrowly bounded participation when expertise, emergency, representation, legal entitlement, quorum, or service continuity makes complete exclusion infeasible, with reasons and compensating safeguards.","purpose":"Rigid conflict rules can disenfranchise affected groups, eliminate scarce expertise, or halt urgent decisions. Exceptions must not become convenience waivers or secret permissions.","required_fields":["exception_ground","necessity_evidence","participation_scope","compensating_controls","approver","duration","notice","post_event_review"],"validation_questions":["Is participation truly necessary?","Can advice be separated from decision authority?","What independent checks compensate?","Will the exception expire automatically?"],"failure_signals":["convenience_waiver","expertise_monopoly","secret_exception","emergency_ratchet"],"safeguards":["written_necessity_finding","minimum_participation","independent_counterweight","automatic_expiry"],"implementation_notes":"Implement Exception Necessity and Proportionality Rule as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Decision Record, Notice, and Challenge Path ↗	Trust depends on evidence that conflicts were handled, not indiscriminate publication of private facts. A reviewable record supports consistency, audit, appeal, and organizational learning. Semantic canonical mapping retained the complete legacy component record: {"slug":"decision_record_notice_and_challenge_path","name":"Decision Record, Notice, and Challenge Path","component_type":"transparency_and_review","definition":"Records disclosure, classification, reviewer independence, mitigation, recusals, exceptions, rationale, implementation, and material dissent, and provides proportionate notice and a correction or challenge path.","purpose":"Trust depends on evidence that conflicts were handled, not indiscriminate publication of private facts. A reviewable record supports consistency, audit, appeal, and organizational learning.","required_fields":["matter_identifier","disclosure_summary","classification","mitigation_decision","rationale","recusal_or_exception","notice_level","challenge_and_correction_path"],"validation_questions":["Can an affected party understand how impartiality was protected?","Is confidential detail minimized?","Can errors be corrected before harm?","Are comparable cases treated consistently?"],"failure_signals":["secret_resolution","privacy_dump","unreasoned_decision","no_correction_path"],"safeguards":["tiered_notice","reason_record","protected_appendix","timely_review_window"],"implementation_notes":"Implement Decision Record, Notice, and Challenge Path as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Compliance Monitoring, Enforcement, and Remedy ↗	Policies without verification reward concealment. Enforcement must distinguish uncertainty, negligence, reckless disregard, concealment, retaliation, and corrupt action while prioritizing restoration and systemic correction. Semantic canonical mapping retained the complete legacy component record: {"slug":"compliance_monitoring_enforcement_and_remedy","name":"Compliance Monitoring, Enforcement, and Remedy","component_type":"assurance_and_response","definition":"Tests whether disclosure, access, recusal, separation, and mitigation obligations are followed, investigates credible breaches, applies proportionate consequences, and repairs tainted decisions or affected-party harm.","purpose":"Policies without verification reward concealment. Enforcement must distinguish uncertainty, negligence, reckless disregard, concealment, retaliation, and corrupt action while prioritizing restoration and systemic correction.","required_fields":["monitoring_plan","control_evidence","breach_intake","investigation_authority","severity_class","consequence_rule","decision_remedy","systemic_corrective_action"],"validation_questions":["Can compliance be verified without pervasive surveillance?","What happens to a tainted decision?","Are retaliation and concealment treated distinctly?","Can affected parties obtain remedy?"],"failure_signals":["paper_compliance","selective_enforcement","punishment_without_repair","monitoring_overreach"],"safeguards":["risk_based_testing","independent_investigation","graduated_consequences","decision_reconsideration"],"implementation_notes":"Implement Compliance Monitoring, Enforcement, and Remedy as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}
Periodic Recertification and Policy Review ↗	Conflict landscapes change as roles, ownership, relationships, technologies, markets, and public expectations change. Review prevents stale controls and learns from both breaches and overrestriction. Semantic canonical mapping retained the complete legacy component record: {"slug":"periodic_recertification_and_policy_review","name":"Periodic Recertification and Policy Review","component_type":"adaptive_review","definition":"Revalidates interests, roles, mitigation plans, reviewer independence, thresholds, exceptions, outcomes, burden, and policy effectiveness on a declared cadence and after material events.","purpose":"Conflict landscapes change as roles, ownership, relationships, technologies, markets, and public expectations change. Review prevents stale controls and learns from both breaches and overrestriction.","required_fields":["recertification_population","cadence","event_triggers","policy_metrics","case_sampling","stakeholder_feedback","revision_authority","version_and_effective_date"],"validation_questions":["Are disclosures and mitigation plans still accurate?","Which controls fail or burden participation?","Do patterns reveal institutional capture?","Are policy changes communicated and implemented?"],"failure_signals":["stale_mitigation","ritual_recertification","threshold_drift","unlearned_pattern"],"safeguards":["event_driven_review","outcome_sampling","affected_party_feedback","versioned_policy_change"],"implementation_notes":"Implement Periodic Recertification and Policy Review as an explicit governed object rather than an informal expectation. Assign an owner, effective date, evidence source, access rule, change trigger, and downstream integration. Calibrate detail to consequence and privacy; a low-risk advisory matter may need a brief record, while a procurement, enforcement, clinical, research, or fiduciary decision may require corroborated evidence and independent signoff.","assurance_notes":"Sample both positive and negative classifications. Verify that the object changed actual rights, information, participation, or structure where required; check consistency across comparable matters; inspect exceptions and overrides; and ask affected parties whether the control was understandable, timely, and safe to challenge.","boundary_notes":"This component is necessary to the parent lifecycle but is not a standalone archetype. It should be paired with the other conflict components when its output affects classification, mitigation, enforcement, or recertification, and it must not be used as proof that the complete conflict has been controlled."}

Common Mechanisms

Mechanism	Description
Conflict-of-Interest Disclosure Register (`conflict_of_interest_disclosure_register`) ↗	Type: implementation_pattern A secure, purpose-limited register linking covered roles, matters, interests, attestations, review status, and mitigation plans. Selection constraints and retained implementation evidence: Recurring decisions with identifiable covered persons and a governance office able to protect sensitive data.; Complete legacy mechanism record retained: {"slug":"conflict_of_interest_disclosure_register","name":"Conflict-of-Interest Disclosure Register","mechanism_type":"implementation_pattern","purpose":"A secure, purpose-limited register linking covered roles, matters, interests, attestations, review status, and mitigation plans.","fit_conditions":["Recurring decisions with identifiable covered persons and a governance office able to protect sensitive data."],"minimum_configuration":["role roster","interest taxonomy","event triggers","privacy tiers","review workflow","retention schedule"],"parent_components_supported":["inventory","disclosure","classification","record","recertification"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Conflict-of-Interest Disclosure Register.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["privacy overcollection","stale annual forms","false reassurance"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Conflict-of-Interest Disclosure Register is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Pre-Decision Conflict Screen (`predecision_conflict_screen`) ↗	Type: implementation_pattern A hold point before agenda setting, assignment, evaluation, procurement, grant, hiring, review, or adjudication that checks relevant disclosures and relationships. Selection constraints and retained implementation evidence: High-consequence or contestable matters where influence occurs before final approval.; Complete legacy mechanism record retained: {"slug":"predecision_conflict_screen","name":"Pre-Decision Conflict Screen","mechanism_type":"implementation_pattern","purpose":"A hold point before agenda setting, assignment, evaluation, procurement, grant, hiring, review, or adjudication that checks relevant disclosures and relationships.","fit_conditions":["High-consequence or contestable matters where influence occurs before final approval."],"minimum_configuration":["matter roster","participant roster","matching rules","human review","hold release","urgent override"],"parent_components_supported":["scope","trigger","classification","assessment","review authority"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Pre-Decision Conflict Screen.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["keyword false positives","late screening","rubber-stamp release"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Pre-Decision Conflict Screen is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Recusal Protocol (`recusal_protocol`) ↗	Type: implementation_pattern A documented process that scopes withdrawal across the full decision lifecycle and transfers every excluded right to a named alternate. Selection constraints and retained implementation evidence: An identifiable actor can be separated without destroying necessary expertise or continuity.; Complete legacy mechanism record retained: {"slug":"recusal_protocol","name":"Recusal Protocol","mechanism_type":"implementation_pattern","purpose":"A documented process that scopes withdrawal across the full decision lifecycle and transfers every excluded right to a named alternate.","fit_conditions":["An identifiable actor can be separated without destroying necessary expertise or continuity."],"minimum_configuration":["scope matrix","alternate decider","meeting rule","access change","communication rule","return test"],"parent_components_supported":["mitigation selection","recusal","firewall","record","monitoring"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Recusal Protocol.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["vote-only recusal","proxy influence","decision vacuum"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Recusal Protocol is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Independent Conflict Review Panel (`independent_review_panel`) ↗	Type: implementation_pattern A standing or ad hoc panel with protected appointment, competence, access, recusal, binding authority, and appeal arrangements. Selection constraints and retained implementation evidence: Senior, institutional, disputed, reviewer-level, or high-legitimacy conflicts.; Complete legacy mechanism record retained: {"slug":"independent_review_panel","name":"Independent Conflict Review Panel","mechanism_type":"implementation_pattern","purpose":"A standing or ad hoc panel with protected appointment, competence, access, recusal, binding authority, and appeal arrangements.","fit_conditions":["Senior, institutional, disputed, reviewer-level, or high-legitimacy conflicts."],"minimum_configuration":["charter","appointment safeguards","quorum","conflict screen","evidence powers","decision template"],"parent_components_supported":["classification","assessment","independent authority","exception","challenge"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Independent Conflict Review Panel.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["captured panel","slow review","confidentiality leakage"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Independent Conflict Review Panel is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Information Firewall (`information_firewall`) ↗	Type: implementation_pattern Technical and procedural isolation of protected information, communications, workspaces, and deliberation from conflicted actors and their proxies. Selection constraints and retained implementation evidence: Information advantage is a material influence path and access can be precisely bounded.; Complete legacy mechanism record retained: {"slug":"information_firewall","name":"Information Firewall","mechanism_type":"implementation_pattern","purpose":"Technical and procedural isolation of protected information, communications, workspaces, and deliberation from conflicted actors and their proxies.","fit_conditions":["Information advantage is a material influence path and access can be precisely bounded."],"minimum_configuration":["data map","access roles","segregated channels","exception approval","logging","breach playbook"],"parent_components_supported":["firewall","recusal","monitoring","record"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Information Firewall.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["oral side channels","stale privileges","blanket operational blockage"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Information Firewall is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Blind Trust or Divestiture Plan (`blind_trust_or_divestiture_plan`) ↗	Type: implementation_pattern A verified transfer, sale, relinquishment, or independent management arrangement that removes beneficial control over a persistent financial interest. Selection constraints and retained implementation evidence: Continuing ownership cannot be managed through episodic recusal and legal structures permit effective separation.; Complete legacy mechanism record retained: {"slug":"blind_trust_or_divestiture_plan","name":"Blind Trust or Divestiture Plan","mechanism_type":"implementation_pattern","purpose":"A verified transfer, sale, relinquishment, or independent management arrangement that removes beneficial control over a persistent financial interest.","fit_conditions":["Continuing ownership cannot be managed through episodic recusal and legal structures permit effective separation."],"minimum_configuration":["asset inventory","independence criteria","communication prohibition","valuation","completion proof","recertification"],"parent_components_supported":["inventory","structural mitigation","independent review","monitoring"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Blind Trust or Divestiture Plan.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["nominal trustee","friendly transfer","hidden beneficial control"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Blind Trust or Divestiture Plan is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Role Separation and Decision Transfer (`role_separation_and_decision_transfer`) ↗	Type: implementation_pattern A structural reassignment of duties, reporting, sponsorship, evaluation, or approval rights to remove incompatible loyalties while preserving service. Selection constraints and retained implementation evidence: The conflict is embedded in a dual role rather than a single transaction.; Complete legacy mechanism record retained: {"slug":"role_separation_and_decision_transfer","name":"Role Separation and Decision Transfer","mechanism_type":"implementation_pattern","purpose":"A structural reassignment of duties, reporting, sponsorship, evaluation, or approval rights to remove incompatible loyalties while preserving service.","fit_conditions":["The conflict is embedded in a dual role rather than a single transaction."],"minimum_configuration":["role map","incompatibility test","replacement authority","handoff","capacity support","review date"],"parent_components_supported":["role boundary","scope","structural mitigation","record","review"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Role Separation and Decision Transfer.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["title-only redesign","unfunded replacement","shadow influence"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Role Separation and Decision Transfer is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Gift and Outside-Activity Approval Workflow (`gift_outside_activity_approval_workflow`) ↗	Type: implementation_pattern A thresholded intake and preapproval process for gifts, hospitality, employment, board service, consulting, political activity, and other external commitments. Selection constraints and retained implementation evidence: External benefits or roles can create actual, potential, or apparent conflicts.; Complete legacy mechanism record retained: {"slug":"gift_outside_activity_approval_workflow","name":"Gift and Outside-Activity Approval Workflow","mechanism_type":"implementation_pattern","purpose":"A thresholded intake and preapproval process for gifts, hospitality, employment, board service, consulting, political activity, and other external commitments.","fit_conditions":["External benefits or roles can create actual, potential, or apparent conflicts."],"minimum_configuration":["covered benefits","thresholds","prohibited class","preapproval","public or internal notice","sanctions"],"parent_components_supported":["inventory","trigger","classification","assessment","mitigation"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Gift and Outside-Activity Approval Workflow.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["threshold gaming","split benefits","manager favoritism"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Gift and Outside-Activity Approval Workflow is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Conflict Management Plan (`conflict_management_plan`) ↗	Type: implementation_pattern A matter- or role-specific package combining disclosure, restrictions, recusals, supervision, firewalls, structural changes, evidence, owners, and expiry. Selection constraints and retained implementation evidence: No single control adequately addresses several influence paths, but complete disqualification is unnecessary or infeasible.; Complete legacy mechanism record retained: {"slug":"conflict_management_plan","name":"Conflict Management Plan","mechanism_type":"implementation_pattern","purpose":"A matter- or role-specific package combining disclosure, restrictions, recusals, supervision, firewalls, structural changes, evidence, owners, and expiry.","fit_conditions":["No single control adequately addresses several influence paths, but complete disqualification is unnecessary or infeasible."],"minimum_configuration":["risk statement","control bundle","owners","milestones","evidence","residual risk","expiry"],"parent_components_supported":["all mitigation and assurance components"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Conflict Management Plan.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["generic boilerplate","unclear owners","permanent exceptions"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Conflict Management Plan is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}
Post-Decision Conflict Audit (`post_decision_conflict_audit`) ↗	Type: implementation_pattern Risk-based retrospective testing of disclosures, access, communications, decisions, outcomes, and remedies to detect control failure and institutional patterns. Selection constraints and retained implementation evidence: High-consequence portfolios, sampled routine matters, complaints, anomalies, or policy review.; Complete legacy mechanism record retained: {"slug":"post_decision_conflict_audit","name":"Post-Decision Conflict Audit","mechanism_type":"implementation_pattern","purpose":"Risk-based retrospective testing of disclosures, access, communications, decisions, outcomes, and remedies to detect control failure and institutional patterns.","fit_conditions":["High-consequence portfolios, sampled routine matters, complaints, anomalies, or policy review."],"minimum_configuration":["sampling rule","evidence access","independent auditor","finding classes","reconsideration rule","trend analysis"],"parent_components_supported":["record","monitoring","remedy","recertification"],"implementation_steps":["Define the decision population, duty, interest categories, influence paths, and consequence threshold for Post-Decision Conflict Audit.","Assign a screened owner and independent review or escalation authority; document their access, authority, recusal, privacy, and service obligations.","Configure the minimum fields, triggers, workflow states, evidence, alternate decision arrangements, exception conditions, and expiry.","Pilot with historical and live cases, including a true conflict, a potential conflict, an apparent conflict, a reviewer conflict, a nonmaterial interest, and an urgent exception.","Integrate with rosters, case records, access controls, meeting processes, procurement or research systems only to the extent necessary for the declared purpose.","Measure timeliness, match quality, control completion, residual risk, continuity, privacy burden, challenge safety, and remedy; revise before scaling."],"validation_signals":["a matter cannot pass the relevant hold point without completed review or a recorded bounded exception","the mechanism changes actual participation, authority, access, ownership, or verification where the risk requires it","reviewers can explain the factual basis, influence path, selected control, residual risk, and alternatives considered","alternate owners can complete the decision without shadow direction from the conflicted actor","records support audit, affected-party challenge, privacy, correction, expiry, and remedy"],"misuse_risks":["hindsight bias","punitive fishing","no decision remedy"],"safeguards":["independent_review","least_restrictive_effective_control","purpose_limited_data","named_alternate_and_continuity","recorded_exception_and_expiry","risk_based_assurance_and_remedy"],"non_equivalence":"Post-Decision Conflict Audit is an implementation option, not the complete parent. It does not alone define all roles and duties, collect every relevant interest, classify and assess conflicts, choose among the full control hierarchy, govern institutional conflicts and exceptions, verify compliance, repair tainted decisions, and recertify the policy."}

• Blind Trust or Divestiture Plan
• Conflict Management Plan
• Conflict-of-Interest Disclosure Register
• Gift and Outside-Activity Approval Workflow
• Independent Conflict Review Panel
• Information Firewall
• Post-Decision Conflict Audit
• Pre-Decision Conflict Screen
• Recusal Protocol
• Role Separation and Decision Transfer

Parameter / Tuning Dimensions

The archetype is stable, but implementation parameters must reflect consequence, volume, privacy, and available independent capacity. Parameters should be declared, justified, monitored, and revised rather than hidden in software or informal custom.

Materiality and evidence

• Value bands: financial thresholds aid triage but remain one factor among consequence, discretion, proximity, dependency, and information.
• Influence threshold: define when advice, agenda, access, recommendation, implementation, or review creates material participation.
• Reasonable-observer standard: specify what facts the observer is assumed to know so “appearance” is neither public rumor nor insider rationalization.
• Confidence labels: use explicit uncertainty and escalation rules for incomplete ownership, relationship, or identity evidence.
• Tail-risk override: allow high-consequence irreversible matters to require stronger controls despite low probability.

Independence

• Reviewer separation: tune separation by matter consequence and institutional exposure. A line manager may handle routine gifts but not a conflict involving leadership, revenue, or the manager's own incentives.
• Appointment and removal: define who selects, funds, evaluates, and can remove reviewers. Independence weakens when these rights sit with the interested actor.
• Evidence powers: specify access to registers, communications, ownership, contracts, meeting records, and technical systems, subject to necessity and rights limits.
• Binding authority: distinguish advice, approval, order, veto, escalation, and appeal. Do not imply authority that the reviewer lacks.
• Capacity: size caseload, expertise, response time, and external-review availability to avoid a nominal control that becomes a bottleneck.

Control strength and duration

• Residual-risk threshold: define who accepts residual risk and what evidence supports acceptance.
• Recusal scope: tune excluded stages and channels to the influence map; final-vote absence is rarely the default full scope.
• Firewall strictness: balance least privilege, operational need, emergency access, monitoring, and privacy.
• Alternate competence: define minimum expertise, authority, independence, resources, and time for the substitute.
• Structural-control threshold: state when repeated recusal or monitoring is no longer adequate and role redesign, divestiture, or separation is required.
• Expiry and reentry: controls should end when the matter or influence path ends, after independent review; structural conflicts may require continuing recertification.

Transparency, privacy, and challenge

• Notice tier: choose public, affected-party, participant, governing-body, confidential reviewer, and protected-appendix levels.
• Data minimization: collect the least detail that permits identity, materiality, control, audit, and correction.
• Retention: retain enough for challenge, consistency, remedy, and legal duties, then dispose securely.
• Challenge window: allow correction before irreversible harm where feasible; provide post-decision remedy when urgency prevents prior review.
• Anti-retaliation response: set rapid protection, investigation, interim measures, and remedy standards.

Assurance and enforcement

• Sampling rate: prioritize consequence, anomaly, repeat counterparties, exceptions, leadership cases, and negative classifications while retaining random samples.
• Evidence depth: match meeting, access, communication, ownership, and outcome review to risk; avoid universal surveillance.
• Severity classification: distinguish uncertainty, error, negligence, reckless disregard, concealment, retaliation, and corruption.
• Decision-remedy threshold: state when a breach requires reconsideration, repetition, voiding, ratification, notice, compensation, or referral.
• Policy-change threshold: use pattern frequency, control failure, overexclusion, privacy burden, latency, and affected-party confidence to trigger redesign.

Parameter choices should be versioned and reviewable. If a system automatically matches people to entities or applies thresholds, store explanations, confidence, source freshness, overrides, and correction outcomes. A parameter is not neutral merely because it is encoded in software.

Invariants to Preserve

Implementations may vary, but the following properties must remain true:

1. A conflict is defined against a real duty and matter. An interest alone is not misconduct, and a viewpoint alone is not disqualifying.
2. Relevant interests are surfaced before influence. Annual disclosure does not replace event-driven screening at assignment, access, or material change.
3. Influence includes more than the final decision. Agenda, evidence, criteria, information, recommendation, implementation, and review remain in scope.
4. Actual, potential, and apparent conflicts stay distinct. Each classification uses facts, confidence, neutral language, and a correction path.
5. Materiality is multi-factor. Money is not the only interest, and formal voting power is not the only influence.
6. The reviewer is screened for the same conflict. Independence includes appointment, funding, evidence access, authority, recusal, and escalation.
7. Disclosure is not treated as mitigation by itself. The selected control must break or sufficiently reduce the identified influence path.
8. Controls are proportionate. Use the least restrictive effective control and consider privacy, due process, expertise, representation, livelihood, and service continuity.
9. Recusal transfers rights. Every excluded decision or implementation responsibility has a competent, independent, resourced alternate.
10. Information access is governed separately from voting. Privileged information cannot remain available merely because formal authority moved.
11. Persistent conflicts receive structural treatment. Repeated episodic waivers do not substitute for ownership, role, compensation, reporting, or institutional redesign.
12. Exceptions are necessary and expiring. Minimum participation, compensating safeguards, independent approval, notice, and post-event review remain mandatory.
13. Privacy and accountability coexist. The regime protects irrelevant personal detail while preserving reasons, correction, challenge, audit, and remedy.
14. Reporters and affected parties can act safely. Retaliation, stigma, selective enforcement, and malicious allegations all receive governed responses.
15. A breach triggers decision review. Personnel sanctions do not replace assessment and repair of the tainted outcome.
16. The system learns. Active plans, negative classifications, institutional patterns, exceptions, burden, and outcomes are periodically recertified and used to change policy.

These invariants are acceptance tests. An implementation that has a form but no independent reviewer, a recusal but no alternate, a firewall but no side-channel controls, an exception but no expiry, or an investigation but no outcome remedy is incomplete even if the policy uses conflict-of-interest terminology.

Target Outcomes

The primary outcome is that entrusted decisions are made and can be defended without material distortion from competing interests. That outcome has several observable dimensions.

Integrity and legitimacy

• relevant interests are disclosed and reviewed before participation;
• affected parties can understand, at the appropriate privacy tier, how impartiality was protected;
• actual, potential, apparent, and nonmaterial findings are consistent across comparable cases;
• senior, institutional, sponsor, and reviewer conflicts receive at least as much scrutiny as ordinary employee cases;
• public or participant confidence improves because reasons and controls are credible rather than performative.

Control effectiveness

• recusals cover the material influence stages and transfer all excluded rights;
• access changes, communication boundaries, structural controls, and exceptions are implemented and verifiable;
• alternates make decisions competently without shadow direction;
• residual risk is explicitly accepted by an independent authority rather than silently inherited;
• repeated reliance on weak controls decreases when structural mitigation is warranted.

Continuity and proportionality

• decisions continue within service targets despite recusal or separation;
• scarce expertise and protected representation are retained through narrow, counterweighted participation where necessary;
• false matches and nonmaterial interests are corrected quickly;
• privacy collection, publication, and retention remain tied to purpose;
• the regime does not disproportionately exclude marginalized, networked, or small-field participants.

Assurance and remedy

• active plans and exceptions have owners, evidence, expiry, and review;
• credible undisclosed conflicts and retaliation are detected and investigated safely;
• tainted decisions are reconsidered and affected-party harm is repaired;
• patterns reveal institutional dependencies, captured reviewers, threshold gaming, and control gaps;
• policy revisions respond to outcomes, burden, confidence, and failure evidence.

Useful indicators include preparticipation disclosure rate, material-change update latency, independent review time, verified-control completion, recusal-transfer completeness, firewall exceptions, undisclosed-conflict detection, retaliation, exception expiry, tainted-decision remedy completion, repeated counterparty or sponsor concentration, false-positive burden, overexclusion, affected-party comprehension, and recertification completion. Metrics should be interpreted together: a rising disclosure count may reflect stronger reporting rather than more misconduct; a very low conflict rate may reveal underdetection; a very high disqualification rate may reveal overbroad rules.

The archetype should not promise zero conflicts. Roles and institutions inevitably encounter competing interests. Success means conflicts are surfaced, assessed, controlled, explained, verified, and repaired in a way that preserves both the governing duty and legitimate participation.

Tradeoffs

Conflict governance balances values that can pull against one another. Mature implementation makes these tradeoffs explicit instead of letting one side dominate by default.

Transparency versus privacy

Publishing interests can support accountability and informed challenge, but excessive detail can expose private relationships, create security risks, deter service, or enable harassment. Tiered notice is the main response: disclose the existence and category of a conflict, the reviewer, control, and rationale to the audience that needs them; place sensitive evidence in a protected appendix; retain it only as long as necessary for audit, challenge, and remedy.

Independence versus domain expertise

The most independent reviewer may lack technical context, while the most knowledgeable expert may share professional networks, sponsors, or intellectual commitments. Combine independence and competence through mixed panels, external members, counterexperts, masked materials, independent chairs, and separation of factual advice from decision authority. Do not use expertise as a blanket waiver or independence as a reason to accept uninformed review.

Risk reduction versus participation and representation

Blanket exclusion can silence affected groups, remove statutory representation, or concentrate authority among people whose conflicts are simply less visible. Assess whether the person's stake is the reason they are legitimately at the table, distinguish representation from fiduciary neutrality, and narrow their role only where duty and interest genuinely conflict. Use voice-without-final-authority, balanced panels, recorded dissent, or independent approval when appropriate.

Control strength versus service continuity

Recusal, transfer, and firewalls can delay urgent work or create an unqualified substitute. Plan alternate capacity before conflicts arise, maintain escalation lanes, and define emergency participation with compensating review. If the same “emergency” repeats, redesign staffing and authority rather than perpetuating waivers.

Detection versus surveillance

Entity matching, access logs, communication review, and relationship data can expose hidden conflicts, but broad monitoring can invade privacy and chill legitimate association. Limit data and assurance to declared roles, matters, influence paths, risk, and retention periods. Require explanation and human review for automated matches. Use targeted sampling and escalation rather than universal communication inspection.

Failure Modes

Failure analysis should identify the broken influence path, control, and recovery—not only the person associated with the event.

Disclosure without action

Signal: the register is complete, but conflicted people retain the same access and influence. Cause: transparency is treated as consent or reputational protection. Recovery: reassess materiality independently, select a control from the hierarchy, name owners and alternates, verify implementation, and review decisions made while the gap persisted.

Self-review or captured review

Signal: cases involving leadership, revenue, sponsors, or the ethics function are consistently classified as nonmaterial. Cause: appointment, funding, reporting, or reputation ties the reviewer to the same interest. Recovery: recuse the reviewer, use an external or separately governed authority, disclose the reviewer conflict, resample prior comparable cases, and redesign appointment and escalation rights.

Vote-only recusal

Signal: the actor leaves the final meeting but authored criteria, selected evidence, briefed the replacement, or directs implementation. Cause: the decision was modeled as a moment rather than a lifecycle. Recovery: map all stages, expand recusal, transfer access and rights, appoint an independent alternate, examine proxy communication, and reconsider the outcome if prior influence was material.

Paper firewall

Signal: formal permissions changed, but shared accounts, copied documents, assistants, oral briefings, or informal messaging preserve access. Cause: technical control was separated from work practice. Recovery: map side channels, update permissions and rosters, segregate workspaces, govern communications and exceptions, sample logs proportionately, and train alternates and support staff.

Nominal divestiture or role redesign

Signal: assets move to a friendly party, the interested person still communicates with a trustee, or duties move on paper but reporting and influence remain. Cause: legal form is mistaken for removal of beneficial control or dependency. Recovery: test actual control, economic benefit, appointment, communications, and shadow authority; require independent completion evidence; extend cooling-off; or use disqualification.

Blanket exclusion

Signal: panels lose all experienced or affected members, decisions slow, and the remaining group has less visible but similar interests. Cause: zero-risk aspiration or fear of criticism. Recovery: reassess materiality, choose the least restrictive effective control, add balanced expertise and independent authority, separate advice from decision rights, and monitor representation and quality.

Exception ratchet

Signal: scarce expertise, urgency, or quorum waivers recur and renew automatically. Cause: exceptions substitute for capacity and structural planning. Recovery: require fresh necessity evidence, minimum participation, counterweights, expiry, trend review, alternate-capacity investment, and redesign when the same condition repeats.

Selective enforcement and retaliation

Signal: junior or disfavored actors are disciplined while senior cases are waived; reporters lose assignments or status. Cause: enforcement power shares hierarchy or political interests. Recovery: protect reporters immediately, investigate independently, audit comparable cases, remedy retaliation, disclose consistency findings, and move enforcement authority.

Punishment without remedy

Signal: an employee is sanctioned, but the award, contract, publication, access, or clinical outcome stands without review. Cause: the response protects the institution rather than the duty or affected party. Recovery: trace the influence, assess taint, repeat or reopen the decision, notify and compensate where appropriate, remove residual access, and correct the system defect.

Neighbor Distinctions

The target has 12 accepted related-only neighbors. They are companions, bounded owners, or sources of components; none owns the complete conflict lifecycle.

Adjudication Process Design

Adjudication applies defined standards to evidence through an impartial forum with reasons, remedy, and appeal. It may resolve a contested conflict classification, sanction, or challenge.

Alignment Governance and Dispute Resolution

Alignment governance gives multi-actor misalignment a forum, authority boundaries, escalation, mediation, and follow-through. Its Recusal Protocol is a useful mechanism.

Antagonism Screening and Separation

Antagonism screening detects harmful combinations and separates, sequences, or redesigns them. A Conflict-of-Interest Check is one listed mechanism.

Authority Legitimacy and Consent Foundations

This neighbor grounds authority in mandate, consent or representation, competence, public reasons, voice, and accountability. A Conflict-of-Interest Guardrail supports that legitimacy.

Checks-and-Balances Architecture

Checks and balances distributes authority so one actor can review, limit, correct, or block another. It does not ensure that the checking actor is free from shared funding, relationships, appointments, or incentives.

Final Override Prevention

Final Override Prevention protects a sovereign decision holder from unilateral substitution while preserving review and exception. A sovereign holder can still be conflicted, and a conflict reviewer can still overreach.

Independent Verification Oversight

Independent Verification Oversight sends validity judgments to separated verifiers with evidence access and challenge authority. Its conflict_of_interest_screening_and_recusal mechanism demonstrates overlap.

Objective Weighting Governance

Objective weighting makes value judgments in multiobjective decisions visible and reviewable. A person may manipulate weights because of a conflict, but hidden weights can also arise without personal interest.

Outside-Authority Influence Channel Mapping

Influence mapping traces money, information, access, dependency, relationships, reputation, and pressure over sovereign decisions. It includes conflict disclosure and recusal/firewall mechanisms.

Principal–Agent Alignment

Principal–Agent Alignment designs incentives, information, discretion, monitoring, accountability, risk sharing, and exit. Its Conflict-of-Interest Control is one component.

Relation Constraint Enforcement

Relation constraints define valid relationships and reject unsafe relational states. A Conflict-of-Interest Check can prevent an incompatible role combination.

Source Provenance Triangulation

Provenance triangulation traces source type, origin, perspective, corroboration, and confidence. It helps identify interested evidence and can strengthen a conflict assessment.

Procedural Fairness Design as the rejected merge anchor

The frozen candidate family proposed aliasing Conflict-of-Interest Mitigation to Procedural Fairness Design but also instructed reviewers to keep the governance family plural and flagged the candidate high_importance and do_not_overmerge. Procedural fairness governs notice, voice, evidence, impartiality, consistency, reasons, review, and remedy across processes.

Cross-Domain Examples

These examples show how the same contract transfers while domain vocabulary and control strength change.

Public procurement: evaluator tied to a bidder

A city forms a panel to procure emergency communications equipment. One technical evaluator previously consulted for a bidder and is negotiating future work with another. The decision-role map includes specification drafting, bidder questions, access to proposals, scoring, negotiation, recommendation, award, and implementation acceptance. The evaluator discloses both relationships before proposal access.

An independent procurement-integrity officer maps the potential benefit, professional dependence, information advantage, and the evaluator's ability to shape criteria. The first relationship is an apparent and potential conflict; the active employment negotiation is actual. Disclosure alone is insufficient. The officer removes the evaluator from bidder communications, proposal access, scoring, negotiation, and acceptance; transfers those rights to a qualified alternate; records the recusal; and prohibits informal briefing. Because the evaluator has rare technical knowledge, the panel permits a written, publicly logged explanation of preexisting interoperability requirements before bids are opened, reviewed by a counterexpert and not tailored to any bidder.

Access logs and meeting records verify the boundary. If the negotiation was concealed until after award, the city audits criteria, communications, scores, and negotiations, uses an unconflicted panel to assess taint, and repeats or reopens the decision where influence could have changed the result. Personnel consequences do not replace contract remedy.

Research funding: small expert community

A foundation reviews grants in a narrow field. Nearly every qualified reviewer has collaborated or competed with some applicants. A blanket three-year coauthorship ban would leave no panel and exclude emerging researchers whose networks are dense. The foundation defines the reviewer duty, maps collaboration, mentorship, institutional, sponsorship, rivalry, and unpublished-work access, and distinguishes ordinary field familiarity from material dependence or direct competition.

Automated publication matching flags relationships but supplies confidence and allows correction. An independent scientific editor classifies cases. Recent close collaborators and direct competitors are recused from scoring and deliberation; weaker intellectual disagreement is documented but not treated as a conflict. The panel uses masked materials where scientifically suitable, balances perspectives, separates factual consultation from scoring, and records an expertise-scarcity exception when no substitute exists. An independent chair and second reviewer provide counterweights. Post-award sampling checks whether exceptions, scores, and funding patterns systematically favor a network or sponsor.

Clinical care: referral and ownership interest

A physician recommends a procedure at a facility in which the physician has an ownership interest. The governing duty is patient welfare and informed choice. Materiality considers expected financial benefit, alternatives, clinical necessity, referral discretion, urgency, and the patient's ability to obtain another opinion. The interest is actual because the recommendation can produce direct benefit.

The mitigation may combine patient notice, an independent clinical opinion, presentation of medically reasonable alternatives, separation of financial staff from clinical choice, and referral transfer. In an emergency with no equivalent clinician, the physician may provide necessary care under a documented necessity exception, with later review. The organization monitors referral patterns and outcomes rather than treating a signed disclosure as cure. If information was withheld and choice was affected, remedy may include renewed consent, fee correction, external review, and institutional redesign.

Corporate board: related-party transaction

A director owns a material interest in a supplier proposed for a long-term contract. The board maps the director's agenda, information, negotiation, influence, vote, and oversight roles. An independent committee with its own advisors reviews beneficial ownership, alternatives, pricing, fairness, and institutional need. The director is excluded from relevant materials, deliberation, negotiation, vote, and implementation oversight, and cannot appoint or direct the committee.

The record discloses the category and mitigation to shareholders at the required level while protecting unnecessary account details. If the company cannot obtain an independent decision path because the controlling owner appoints every reviewer, external valuation, minority approval, regulatory review, or declining the transaction may be required. A formal recusal does not cure controlling-owner pressure.

Regulation: revolving door and data dependence

A regulatory unit evaluates a rule affecting an industry that supplies most of its technical data and hires many former staff. Individual disclosure captures employment negotiations, prior roles, investments, and family ties. Institutional mapping captures data dependence, advisory-group composition, appropriations, political pressure, and post-service labor markets.

Controls include cooling-off, reassignment, external technical replication, balanced consultation, public reason records, independent review of key evidence, and diversified data sources. The unit audits whether meetings, draft changes, exceptions, and enforcement outcomes cluster around particular firms. Because capture is systemic, recusing one official is insufficient; institutional dependency and reviewer appointment require structural controls.

AI product safety: evaluator under launch pressure

A company creates a model-safety evaluation team, but the team lead's compensation and promotion depend on the product's launch date. External auditors also rely on future contracts from the company. The role map distinguishes model development, benchmark selection, red-team access, acceptance criteria, launch approval, incident review, and public claims. The compensation tie is an institutional actual conflict; auditor dependency is potential and apparent.

The company separates launch authority from evaluation, gives the safety function protected access and escalation, uses independently selected auditors with conflict screens, records benchmark and acceptance changes, and prohibits product leadership from suppressing findings. High-severity failures trigger a hold point. A bounded emergency release exception requires a documented necessity, minimum functionality, enhanced monitoring, independent approval, public or customer notice as appropriate, and expiry. Post-launch incident review examines whether conflicted incentives altered evidence or thresholds.

Non-Examples

The archetype should not become a catch-all label for bias, disagreement, ethics, or bad decisions.

• Two departments disagree, but neither owes a divided duty or holds a competing interest. Use alignment governance, decision rights, or dispute resolution.
• Evidence is weak or provenance unclear without a competing interest. Use verification or provenance controls.
• A person has expertise, a viewpoint, political beliefs, or lived experience. Perspective is not a conflict unless it creates a competing duty in a defined role and matter.
• An affected resident participates in consultation or representation. Stake may be the legitimate basis for voice, not a disqualification.
• General delegated incentives need improvement. Use Principal–Agent Alignment unless a specific competing interest requires this contract.
• An organization needs separation of powers, appeal, or ordinary fair process without divided loyalty. Use Checks-and-Balances Architecture or Procedural Fairness Design.
• A general security policy restricts data access. A conflict firewall is specifically tied to an interest-to-information influence path.
• A person completes a disclosure form. That is intake, not classification, mitigation, independent review, continuity, assurance, or remedy.
• A person leaves the final vote but retains agenda, evidence, access, briefing, or implementation control. That is incomplete recusal.
• A committee is called independent while the interested actor appoints, funds, removes, or controls its information. That is nominal independence.
• A policy publishes irrelevant family, social, or financial details. That is privacy overreach, not mature transparency.
• A rumor about “appearance” removes a critic without a duty, factual basis, informed-observer test, or appeal. That is weaponization.
• A blanket ban removes all experts or affected representatives without materiality and proportionality review. That is overcorrection.
• An emergency exception lacks necessity, narrowed participation, counterweights, notice, expiry, or later review. That is bypass.
• A trust, transfer, or role change leaves beneficial control and shadow influence intact. That is structural theater.
• A person is disciplined but the tainted decision is not reviewed. That is enforcement without remedy.
• Bribery, fraud, corruption, insider trading, or other crimes require specialized legal and investigative authority; conflict governance can preserve evidence and refer, but cannot replace it.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

• Conflict of Interest: Competing incentives.

Also references 9 related abstractions

• Accountability: Responsibility for actions.
• Agency Problem: Misaligned incentives.
• Competition: Rivalrous pursuit of a scarce prize where one party's gain is another's loss.
• Impartiality: Treatment that depends only on relevant features and is invariant under the identity of the party involved.
• Information Asymmetry: Parties to an interaction hold unequal private knowledge.
• Procedural Fairness (Due Process): Due process.
• Regulatory Capture: Regulated agents gain influence over institution redirecting it.
• Role: A bundle of expected behaviours attached to a social position.
• Role Conflict: Conflicting roles.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Transaction-Specific Conflict Control · other · recognized

A bounded procurement, investment, grant, hiring, licensing, related-party, or contracting decision has identifiable participants and counterparties.

• Distinct from parent: Not equivalent to general procurement integrity or transaction approval; it preserves the parent interest-to-influence-to-control lifecycle for one matter.
• Use when: The specialization materially changes how Conflict-of-Interest Mitigation is configured while preserving its invariants.
• Common mechanisms: conflict of interest disclosure register, predecision conflict screen

Standing Institutional Conflict Governance · other · recognized

An organization itself depends on revenue, funding, appointments, sponsors, data, reputation, or future employment connected to the matters it governs.

• Distinct from parent: Not reducible to aggregating individual disclosures; the interested entity may own the appointment, information, enforcement, and remedy architecture.
• Use when: The specialization materially changes how Conflict-of-Interest Mitigation is configured while preserving its invariants.
• Common mechanisms: conflict of interest disclosure register, predecision conflict screen

Expert and Peer-Review Conflict Management · other · recognized

Research, clinical, technical, editorial, standards, accreditation, or professional review occurs in a small expert network where collaboration, competition, sponsorship, and intellectual commitments are common.

• Distinct from parent: Not equivalent to source provenance or independent verification; it governs when expert judgment is divided and how expertise can be retained safely.
• Use when: The specialization materially changes how Conflict-of-Interest Mitigation is configured while preserving its invariants.
• Common mechanisms: conflict of interest disclosure register, predecision conflict screen

Automated Matching and Human Conflict Review · other · recognized

Large volumes of people, entities, ownership, publications, employment, cases, or transactions justify automated relationship matching before contextual human review.

• Distinct from parent: The automated match is a detection aid, never the final conflict classification, mitigation decision, or sanction.
• Use when: The specialization materially changes how Conflict-of-Interest Mitigation is configured while preserving its invariants.
• Common mechanisms: conflict of interest disclosure register, predecision conflict screen