37 entities 9 actions 6 events 8 causal chains 13 temporal relations
Timeline Overview
Action Event 15 sequenced markers
DOT Engineer Accepts Part-Time Consulting Offer BER Case 02-8, 2002
Municipal Conflict Potential Identified BER Case 02-8 (2002) — at time of approach
DOE Engineer Testifies Without Full Disclosure BER Case 07-12, 2007
DOE Engineer Uses DOE-Branded Presentation BER Case 07-12, 2007, during regulatory hearing testimony
DOE Affiliation Misperception Created BER Case 07-12 (2007) — during testimony
Doe Prepares Private Subdivision Plans BER Case 67-1, 1967
Doe Recommends His Own Plans BER Case 67-1, 1967, after plan preparation
Doe Votes to Approve Own Plans BER Case 67-1, 1967, after official recommendation
Doe Triple Role Conflict Emerges BER Case 67-1 (1967)
Plans Approved Under Conflict BER Case 67-1 (1967) — subsequent to plan preparation
Engineer A Accepts Forensic Expert Engagement Present case, at time of engagement acceptance
Engineer A Discloses Committee Role to Attorney X Present case, upon discovery of Engineer B's subcommittee membership
Engineer A Avoids Ex Parte Litigation Communications with Engineer B Present case, throughout duration of litigation engagement
Engineer B Subcommittee Membership Discovered Present case — upon Engineer A's review of the engagement
Conflict Disclosure Record Established Present case — following Engineer A's discovery of Engineer B's role
OWL-Time Temporal Structure 13 relations time: = w3.org/2006/time
BER Case 67-1 time:before BER Case 02-8
BER Case 02-8 time:before BER Case 07-12
BER Case 67-1 time:before BER Case 07-12
BER Case 07-12 time:before present case (Engineer A / Attorney X)
Doe's preparation of subdivision plans (as private consultant) time:before Doe's recommendation of approval (as county engineer)
Doe's recommendation of approval (as county engineer) time:before Doe's vote to approve (as planning board member)
Engineer A's prior consulting work (airport design) time:before Engineer A's employment with State DOT
Engineer A's employment with State DOT time:intervalOverlaps Engineer A's proposed part-time consulting for former firm
Engineer A (BER 07-12) serving on State X Environmental Quality Council time:intervalOverlaps Engineer A (BER 07-12) testifying for coal bed methane company
Engineer A (BER 07-12) testifying at hearing time:before newspaper article reporting on hearing
Engineer A chairing boiler code standards and safety committee time:intervalOverlaps Engineer A serving as forensic expert for Attorney X
Engineer B serving on subcommittee chaired by Engineer A time:intervalOverlaps Engineer B serving as plaintiff's forensic expert
Engineer A's disclosure to Attorney X time:before Engineer A's engagement as expert witness
Extracted Actions (9)
Volitional professional decisions with intentions and ethical context

Description: Engineer John Doe, while serving as county engineer and planning board member, chose to prepare subdivision development plans in his capacity as a private consulting engineer, creating a direct conflict with his public roles.

Temporal Marker: BER Case 67-1, 1967

Mental State: deliberate

Intended Outcome: Secure private consulting revenue by preparing subdivision plans for a client

Fulfills Obligations:
  • Providing engineering services within his technical competence
Guided By Principles:
  • Integrity in public service
  • Avoidance of conflicts of interest
  • Faithful agency
Required Capabilities:
Civil/site engineering for subdivision design Knowledge of local planning and approval processes
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Doe sought to leverage his unique insider knowledge of county planning priorities and his established professional reputation to win private consulting business, likely motivated by financial gain and professional ambition, while perhaps rationalizing that his expertise made him the most qualified person for the work.

Ethical Tension: Personal financial interest vs. fiduciary duty to the public; the engineer's private economic benefit directly conflicts with his obligation to serve the county impartially and without self-dealing. The tension also exists between professional competence (he may genuinely be qualified) and structural integrity of public governance.

Learning Significance: Illustrates how conflicts of interest can be structural and systemic rather than merely situational — holding multiple roles simultaneously creates inherent ethical jeopardy regardless of intent. Teaches that an engineer must evaluate not just whether they can perform work competently, but whether the role configuration itself is permissible.

Stakes: Public trust in government planning processes, integrity of land use decisions, fairness to competing private engineers who lack insider access, potential legal liability for the county, and the foundational principle that public servants must not profit from their public authority.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline the private consulting engagement entirely and refer the client to another qualified engineer
  • Resign from one or both public roles before accepting the private work
  • Disclose the potential conflict to county leadership and seek a formal ethics ruling before proceeding

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_Doe_Prepares_Private_Subdivision_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the private consulting engagement entirely and refer the client to another qualified engineer",
    "Resign from one or both public roles before accepting the private work",
    "Disclose the potential conflict to county leadership and seek a formal ethics ruling before proceeding"
  ],
  "proeth-scenario:characterMotivation": "Doe sought to leverage his unique insider knowledge of county planning priorities and his established professional reputation to win private consulting business, likely motivated by financial gain and professional ambition, while perhaps rationalizing that his expertise made him the most qualified person for the work.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining preserves public integrity and Doe\u0027s impartiality but foregoes private income; the client finds another engineer and the process remains untainted",
    "Resigning from public roles before accepting private work would eliminate the structural conflict but would deprive the county of his expertise and potentially raise questions about his motivations for resigning",
    "Seeking a formal ethics ruling would demonstrate good faith and transparency, potentially resulting in an approved recusal arrangement or a clear prohibition, either of which would be preferable to the undisclosed conflict that actually occurred"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how conflicts of interest can be structural and systemic rather than merely situational \u2014 holding multiple roles simultaneously creates inherent ethical jeopardy regardless of intent. Teaches that an engineer must evaluate not just whether they can perform work competently, but whether the role configuration itself is permissible.",
  "proeth-scenario:ethicalTension": "Personal financial interest vs. fiduciary duty to the public; the engineer\u0027s private economic benefit directly conflicts with his obligation to serve the county impartially and without self-dealing. The tension also exists between professional competence (he may genuinely be qualified) and structural integrity of public governance.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public trust in government planning processes, integrity of land use decisions, fairness to competing private engineers who lack insider access, potential legal liability for the county, and the foundational principle that public servants must not profit from their public authority.",
  "proeth:description": "Engineer John Doe, while serving as county engineer and planning board member, chose to prepare subdivision development plans in his capacity as a private consulting engineer, creating a direct conflict with his public roles.",
  "proeth:foreseenUnintendedEffects": [
    "Plans would require approval by the very governmental body on which Doe served",
    "His public role would be compromised by his private financial interest in plan approval"
  ],
  "proeth:fulfillsObligation": [
    "Providing engineering services within his technical competence"
  ],
  "proeth:guidedByPrinciple": [
    "Integrity in public service",
    "Avoidance of conflicts of interest",
    "Faithful agency"
  ],
  "proeth:hasAgent": "John Doe (County Engineer, Planning Board Member, and Private Consultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private consulting interest vs. Public impartiality",
    "proeth:resolutionReasoning": "Doe prioritized private financial gain over public integrity, which the BER found to be a clear ethical violation regardless of whether he ultimately voted on his own plans"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure private consulting revenue by preparing subdivision plans for a client",
  "proeth:requiresCapability": [
    "Civil/site engineering for subdivision design",
    "Knowledge of local planning and approval processes"
  ],
  "proeth:temporalMarker": "BER Case 67-1, 1967",
  "proeth:violatesObligation": [
    "Obligation to avoid conflicts of interest between private practice and public role",
    "Obligation to act as faithful agent and trustee to the public",
    "Obligation to avoid situations where private interest could influence public duty"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Doe Prepares Private Subdivision Plans"
}

Description: As county engineer, John Doe formally recommended approval of the subdivision plans he had privately prepared, directly using his public authority to advance his private work product.

Temporal Marker: BER Case 67-1, 1967, after plan preparation

Mental State: deliberate

Intended Outcome: Advance the approval of plans he prepared privately by leveraging his official recommendation authority

Guided By Principles:
  • Honesty and integrity in public service
  • Avoidance of self-dealing
  • Transparency
Required Capabilities:
Engineering review of subdivision plans Knowledge of county approval standards
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Having already prepared the plans and invested professional effort, Doe was motivated by consistency and sunk-cost reasoning — he needed the plans approved to fulfill his private contract and earn his fee. He may have rationalized that recommending his own work was simply an honest professional assessment of quality plans.

Ethical Tension: Duty of impartial professional judgment as a public official vs. self-interest in validating and advancing one's own private work product; the engineer's obligation to evaluate plans objectively is fatally compromised when he is simultaneously the author of those plans and a financial beneficiary of their approval.

Learning Significance: Demonstrates the escalation dynamic in conflicts of interest — each compromised action makes the next one feel more necessary and justified. Teaches that using public authority to advance private work product is a textbook abuse of official position, and that the harm is not merely theoretical but structural: the recommendation process itself is corrupted.

Stakes: Legitimacy of the county engineer's professional recommendation function, fairness to other developers whose plans are evaluated by the same official, potential legal challenges to the approval, and erosion of public confidence in the planning process.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Recuse himself from the review and recommendation process for this specific project, delegating it to a deputy or independent reviewer
  • Withdraw the private consulting engagement before the recommendation phase and return any fees received
  • Disclose the conflict publicly in the official record before making any recommendation, allowing the county to decide how to proceed

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_Doe_Recommends_His_Own_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Recuse himself from the review and recommendation process for this specific project, delegating it to a deputy or independent reviewer",
    "Withdraw the private consulting engagement before the recommendation phase and return any fees received",
    "Disclose the conflict publicly in the official record before making any recommendation, allowing the county to decide how to proceed"
  ],
  "proeth-scenario:characterMotivation": "Having already prepared the plans and invested professional effort, Doe was motivated by consistency and sunk-cost reasoning \u2014 he needed the plans approved to fulfill his private contract and earn his fee. He may have rationalized that recommending his own work was simply an honest professional assessment of quality plans.",
  "proeth-scenario:consequencesIfAlternative": [
    "Recusal would preserve the integrity of the recommendation process and signal ethical awareness, though it would raise questions about why he accepted the private work in the first place",
    "Withdrawing from the private engagement at this stage would be disruptive to the client but would stop the conflict from compounding further; financial and reputational costs would be moderate",
    "Public disclosure would be transparent but would likely trigger an ethics investigation and could invalidate any subsequent recommendation, making it a high-risk but ethically correct choice"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates the escalation dynamic in conflicts of interest \u2014 each compromised action makes the next one feel more necessary and justified. Teaches that using public authority to advance private work product is a textbook abuse of official position, and that the harm is not merely theoretical but structural: the recommendation process itself is corrupted.",
  "proeth-scenario:ethicalTension": "Duty of impartial professional judgment as a public official vs. self-interest in validating and advancing one\u0027s own private work product; the engineer\u0027s obligation to evaluate plans objectively is fatally compromised when he is simultaneously the author of those plans and a financial beneficiary of their approval.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Legitimacy of the county engineer\u0027s professional recommendation function, fairness to other developers whose plans are evaluated by the same official, potential legal challenges to the approval, and erosion of public confidence in the planning process.",
  "proeth:description": "As county engineer, John Doe formally recommended approval of the subdivision plans he had privately prepared, directly using his public authority to advance his private work product.",
  "proeth:foreseenUnintendedEffects": [
    "Public trust in the impartiality of the county engineer\u0027s recommendations would be undermined",
    "The planning board would unknowingly evaluate plans on a biased recommendation"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and integrity in public service",
    "Avoidance of self-dealing",
    "Transparency"
  ],
  "proeth:hasAgent": "John Doe (County Engineer acting in official capacity)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Official duty to recommend vs. Obligation to recuse due to conflict",
    "proeth:resolutionReasoning": "Doe chose to exercise his official authority in a self-interested manner rather than disclosing the conflict and recusing, which the BER identified as independently unethical even absent the planning board vote"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Advance the approval of plans he prepared privately by leveraging his official recommendation authority",
  "proeth:requiresCapability": [
    "Engineering review of subdivision plans",
    "Knowledge of county approval standards"
  ],
  "proeth:temporalMarker": "BER Case 67-1, 1967, after plan preparation",
  "proeth:violatesObligation": [
    "Obligation to avoid using public authority to benefit private interests",
    "Obligation to disclose conflicts of interest to relevant parties",
    "Obligation to act as faithful agent to the public body he served"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Doe Recommends His Own Plans"
}

Description: As a planning board member, John Doe voted to approve the subdivision plans he had privately prepared and officially recommended, completing a three-role conflict of interest.

Temporal Marker: BER Case 67-1, 1967, after official recommendation

Mental State: deliberate

Intended Outcome: Secure final governmental approval of plans he prepared and recommended, completing the approval cycle to benefit his private client and consulting practice

Guided By Principles:
  • Impartiality in public roles
  • Public safety and welfare over private gain
  • Integrity
Required Capabilities:
Evaluation of engineering plans for planning purposes Understanding of public approval standards
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Doe completed the logical endpoint of his three-role involvement — having prepared and recommended the plans, voting to approve them was the final step needed to fulfill his private contract. At this stage, he may have felt committed and unable to reverse course without exposing the entire conflict, creating a self-reinforcing trap of his own making.

Ethical Tension: The duty of a planning board member to vote in the public interest vs. the private financial interest in approving one's own work; democratic governance requires that voting authority be exercised free from personal financial stakes. This action also creates tension between institutional loyalty (completing the board's work) and personal integrity.

Learning Significance: Represents the climax of a cascading conflict of interest — the point at which all three roles converge in a single corrupt act. Teaches that conflicts of interest, if not addressed at the first opportunity, tend to compound and become progressively harder to escape. Also illustrates why prophylactic recusal rules exist: to prevent exactly this kind of structural capture.

Stakes: The validity of the planning board's decision, potential grounds for legal challenge by affected parties, Doe's professional license and reputation, the county's legal exposure, and the broader public interest in land use decisions made without self-dealing.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Abstain from the vote and publicly declare the conflict of interest before the board
  • Vote to table the application pending assignment to a conflict-free review process
  • Resign from the planning board immediately before the vote to avoid casting a conflicted ballot

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_Doe_Votes_to_Approve_Own_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Abstain from the vote and publicly declare the conflict of interest before the board",
    "Vote to table the application pending assignment to a conflict-free review process",
    "Resign from the planning board immediately before the vote to avoid casting a conflicted ballot"
  ],
  "proeth-scenario:characterMotivation": "Doe completed the logical endpoint of his three-role involvement \u2014 having prepared and recommended the plans, voting to approve them was the final step needed to fulfill his private contract. At this stage, he may have felt committed and unable to reverse course without exposing the entire conflict, creating a self-reinforcing trap of his own making.",
  "proeth-scenario:consequencesIfAlternative": [
    "Abstaining with public disclosure would be the minimum ethical requirement at this stage; it would likely trigger an ethics inquiry but would prevent the most egregious act of self-approval",
    "Tabling the application would protect the process but would delay the client\u0027s project and expose the conflict, likely leading to investigation of the earlier recommendation as well",
    "Resigning before the vote would be dramatic and disruptive but would demonstrate a belated recognition of impropriety; it would not undo the earlier recommendation conflict but would prevent the voting conflict"
  ],
  "proeth-scenario:decisionSignificance": "Represents the climax of a cascading conflict of interest \u2014 the point at which all three roles converge in a single corrupt act. Teaches that conflicts of interest, if not addressed at the first opportunity, tend to compound and become progressively harder to escape. Also illustrates why prophylactic recusal rules exist: to prevent exactly this kind of structural capture.",
  "proeth-scenario:ethicalTension": "The duty of a planning board member to vote in the public interest vs. the private financial interest in approving one\u0027s own work; democratic governance requires that voting authority be exercised free from personal financial stakes. This action also creates tension between institutional loyalty (completing the board\u0027s work) and personal integrity.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The validity of the planning board\u0027s decision, potential grounds for legal challenge by affected parties, Doe\u0027s professional license and reputation, the county\u0027s legal exposure, and the broader public interest in land use decisions made without self-dealing.",
  "proeth:description": "As a planning board member, John Doe voted to approve the subdivision plans he had privately prepared and officially recommended, completing a three-role conflict of interest.",
  "proeth:foreseenUnintendedEffects": [
    "Complete collapse of any separation between private interest and public decision-making",
    "Invalidation of the integrity of the public approval process"
  ],
  "proeth:guidedByPrinciple": [
    "Impartiality in public roles",
    "Public safety and welfare over private gain",
    "Integrity"
  ],
  "proeth:hasAgent": "John Doe (Planning Board Member acting in official capacity)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Board participation duty vs. Conflict-of-interest recusal obligation",
    "proeth:resolutionReasoning": "Doe prioritized completing the approval cycle, which the BER found to be the most egregious element of a multi-layered ethical violation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure final governmental approval of plans he prepared and recommended, completing the approval cycle to benefit his private client and consulting practice",
  "proeth:requiresCapability": [
    "Evaluation of engineering plans for planning purposes",
    "Understanding of public approval standards"
  ],
  "proeth:temporalMarker": "BER Case 67-1, 1967, after official recommendation",
  "proeth:violatesObligation": [
    "Obligation to avoid conflicts of interest in public decision-making",
    "Obligation to recuse from votes where personal interest exists",
    "Duty of faithful and impartial public service",
    "Obligation to protect the public interest"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Doe Votes to Approve Own Plans"
}

Description: Engineer A (BER 02-8), while employed as a state DOT traffic engineer, chose to accept an offer from his former consulting firm to perform part-time airport design consulting for municipalities, despite his ongoing public employment role that involved relationships with those same municipalities.

Temporal Marker: BER Case 02-8, 2002

Mental State: deliberate

Intended Outcome: Supplement income through part-time consulting while maintaining state employment, leveraging prior airport design expertise

Guided By Principles:
  • Faithful agency to public employer
  • Avoidance of conflicts of interest
  • Public trust and transparency
Required Capabilities:
Airport design engineering Municipal consulting and contract management
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: The DOT engineer was motivated by financial supplementation, a desire to maintain ties with his former firm and private-sector skills, and possibly a belief that airport design work was sufficiently distinct from his DOT highway-focused duties to avoid meaningful conflict. He may have genuinely believed the work would not intersect with his public responsibilities.

Ethical Tension: The engineer's right to pursue professional development and supplemental income vs. his duty of undivided loyalty to his public employer; the tension is sharpened by the fact that his DOT role involves relationships with the same municipalities that would be his consulting clients, creating potential for preferential treatment or divided loyalties in both directions.

Learning Significance: Illustrates that conflicts of interest in public employment extend beyond direct subject-matter overlap — the identity of the clients (municipalities) rather than the technical content of the work (airport vs. highway) is what creates the conflict. Teaches that engineers must analyze conflicts holistically, considering all dimensions of their professional relationships.

Stakes: The integrity of the DOT engineer's public duties, fairness to municipalities that interact with him in his official capacity, his state employment terms and potential disciplinary action, the former firm's reputation, and the principle that public employees must not use their positions to benefit private clients.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline the offer and explain to the former firm that his current DOT role creates an irreconcilable conflict
  • Seek a formal opinion from his state ethics office or DOT ethics officer before accepting or declining
  • Accept only if the firm agrees to exclude any municipalities that fall within his DOT jurisdiction or with which he has official dealings

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_DOT_Engineer_Accepts_Part-Time_Consulting_Offer",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the offer and explain to the former firm that his current DOT role creates an irreconcilable conflict",
    "Seek a formal opinion from his state ethics office or DOT ethics officer before accepting or declining",
    "Accept only if the firm agrees to exclude any municipalities that fall within his DOT jurisdiction or with which he has official dealings"
  ],
  "proeth-scenario:characterMotivation": "The DOT engineer was motivated by financial supplementation, a desire to maintain ties with his former firm and private-sector skills, and possibly a belief that airport design work was sufficiently distinct from his DOT highway-focused duties to avoid meaningful conflict. He may have genuinely believed the work would not intersect with his public responsibilities.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining preserves his public integrity and avoids all conflict risk, though it sacrifices income and may strain the relationship with his former firm",
    "Seeking a formal ethics opinion is the most professionally responsible approach \u2014 it protects him legally, demonstrates good faith, and produces a documented record of compliance regardless of the outcome",
    "Conditional acceptance with jurisdictional carve-outs might reduce but not eliminate the conflict, and would require ongoing monitoring to ensure no overlap develops, creating administrative complexity and residual risk"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that conflicts of interest in public employment extend beyond direct subject-matter overlap \u2014 the identity of the clients (municipalities) rather than the technical content of the work (airport vs. highway) is what creates the conflict. Teaches that engineers must analyze conflicts holistically, considering all dimensions of their professional relationships.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s right to pursue professional development and supplemental income vs. his duty of undivided loyalty to his public employer; the tension is sharpened by the fact that his DOT role involves relationships with the same municipalities that would be his consulting clients, creating potential for preferential treatment or divided loyalties in both directions.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The integrity of the DOT engineer\u0027s public duties, fairness to municipalities that interact with him in his official capacity, his state employment terms and potential disciplinary action, the former firm\u0027s reputation, and the principle that public employees must not use their positions to benefit private clients.",
  "proeth:description": "Engineer A (BER 02-8), while employed as a state DOT traffic engineer, chose to accept an offer from his former consulting firm to perform part-time airport design consulting for municipalities, despite his ongoing public employment role that involved relationships with those same municipalities.",
  "proeth:foreseenUnintendedEffects": [
    "Potential conflict of interest in dealings with municipalities in both his state highway and private airport roles",
    "Appearance of impropriety even if substantive conflicts did not materialize",
    "Risk of using state resources or influence in private work"
  ],
  "proeth:guidedByPrinciple": [
    "Faithful agency to public employer",
    "Avoidance of conflicts of interest",
    "Public trust and transparency"
  ],
  "proeth:hasAgent": "Engineer A (BER 02-8) (State DOT Traffic Engineer and prospective part-time private consultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private professional opportunity vs. Public employment integrity",
    "proeth:resolutionReasoning": "The BER found that even though the technical domains differed, the shared municipal relationships created an inextricable conflict, and Engineer A should have declined the consulting engagement"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Supplement income through part-time consulting while maintaining state employment, leveraging prior airport design expertise",
  "proeth:requiresCapability": [
    "Airport design engineering",
    "Municipal consulting and contract management"
  ],
  "proeth:temporalMarker": "BER Case 02-8, 2002",
  "proeth:violatesObligation": [
    "Obligation to avoid conflicts of interest between public employment and private consulting",
    "Obligation to serve as faithful agent and trustee to the state DOT",
    "Obligation to avoid situations creating appearance of impropriety",
    "Obligation to avoid use of public resources for private benefit"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "DOT Engineer Accepts Part-Time Consulting Offer"
}

Description: Engineer A (BER 07-12), a DOE employee consulting privately for coal bed methane companies, chose to testify as an expert witness before the State Y Environmental Quality Council without clearly disclosing his DOE employment status or his private consulting relationship with the coal bed methane industry.

Temporal Marker: BER Case 07-12, 2007

Mental State: deliberate

Intended Outcome: Provide expert testimony on behalf of the coal bed methane company while maintaining ambiguity about his affiliations, potentially leveraging DOE credibility for private client benefit

Guided By Principles:
  • Honesty and integrity in professional practice
  • Full disclosure of conflicts of interest
  • Faithful agency to employer
  • Public trust in expert testimony
Required Capabilities:
Coal bed methane technical expertise Expert witness testimony skills Regulatory proceeding participation
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: The DOE engineer was motivated by advocacy for the coal bed methane industry (which was paying him privately) and perhaps a genuine belief in the technical merits of his testimony. He may have rationalized that his DOE expertise lent credibility to the proceedings and that his private consulting was a separate matter that did not need to be foregrounded in testimony.

Ethical Tension: The duty of candor and full disclosure as an expert witness vs. the desire to maximize the persuasive impact of testimony by presenting as a neutral government expert; the tension also involves loyalty to his private paying client vs. his obligation to the adjudicative body and the public interest in accurate, unbiased expert testimony.

Learning Significance: Teaches that expert witness testimony carries a heightened duty of transparency because adjudicators and the public rely on it as objective technical truth. Failure to disclose dual roles is not merely an omission — it is an active misrepresentation by silence. Also illustrates that engineers cannot compartmentalize professional identities when those identities are material to the weight given their testimony.

Stakes: The integrity of the Environmental Quality Council's decision-making process, the rights of parties who relied on the testimony as independent expert opinion, the engineer's professional license and federal employment, potential legal consequences for false or misleading testimony before a regulatory body, and public trust in government scientific expertise.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Fully disclose both his DOE employment and his private consulting relationship with coal bed methane companies at the outset of testimony
  • Decline to testify as a paid expert while employed by DOE, offering instead to provide purely personal professional opinion without compensation
  • Seek DOE ethics office approval and guidance on permissible testimony parameters before agreeing to testify

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_DOE_Engineer_Testifies_Without_Full_Disclosure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Fully disclose both his DOE employment and his private consulting relationship with coal bed methane companies at the outset of testimony",
    "Decline to testify as a paid expert while employed by DOE, offering instead to provide purely personal professional opinion without compensation",
    "Seek DOE ethics office approval and guidance on permissible testimony parameters before agreeing to testify"
  ],
  "proeth-scenario:characterMotivation": "The DOE engineer was motivated by advocacy for the coal bed methane industry (which was paying him privately) and perhaps a genuine belief in the technical merits of his testimony. He may have rationalized that his DOE expertise lent credibility to the proceedings and that his private consulting was a separate matter that did not need to be foregrounded in testimony.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full disclosure would allow the Council to appropriately weigh his testimony with knowledge of his interests; it might reduce his persuasive impact but would preserve his integrity and comply with ethical obligations",
    "Declining paid testimony eliminates the financial conflict but does not resolve the DOE affiliation question; a middle path that avoids the most egregious conflict while preserving some participation",
    "Seeking DOE ethics approval would likely result in either clear permission with conditions or a prohibition, either of which would provide legal and ethical protection and prevent the situation that actually occurred"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that expert witness testimony carries a heightened duty of transparency because adjudicators and the public rely on it as objective technical truth. Failure to disclose dual roles is not merely an omission \u2014 it is an active misrepresentation by silence. Also illustrates that engineers cannot compartmentalize professional identities when those identities are material to the weight given their testimony.",
  "proeth-scenario:ethicalTension": "The duty of candor and full disclosure as an expert witness vs. the desire to maximize the persuasive impact of testimony by presenting as a neutral government expert; the tension also involves loyalty to his private paying client vs. his obligation to the adjudicative body and the public interest in accurate, unbiased expert testimony.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The integrity of the Environmental Quality Council\u0027s decision-making process, the rights of parties who relied on the testimony as independent expert opinion, the engineer\u0027s professional license and federal employment, potential legal consequences for false or misleading testimony before a regulatory body, and public trust in government scientific expertise.",
  "proeth:description": "Engineer A (BER 07-12), a DOE employee consulting privately for coal bed methane companies, chose to testify as an expert witness before the State Y Environmental Quality Council without clearly disclosing his DOE employment status or his private consulting relationship with the coal bed methane industry.",
  "proeth:foreseenUnintendedEffects": [
    "Misleading the regulatory council about the independence and basis of his testimony",
    "Conflating his DOE role with his private consulting role",
    "Undermining the integrity of the regulatory hearing process"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and integrity in professional practice",
    "Full disclosure of conflicts of interest",
    "Faithful agency to employer",
    "Public trust in expert testimony"
  ],
  "proeth:hasAgent": "Engineer A (BER 07-12) (DOE Employee and private consultant retained by coal bed methane company)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client advocacy vs. Honesty and full disclosure in expert testimony",
    "proeth:resolutionReasoning": "Engineer A chose to allow ambiguity to persist, which the BER found constituted an intentional or negligent misrepresentation regardless of which interpretation was applied"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide expert testimony on behalf of the coal bed methane company while maintaining ambiguity about his affiliations, potentially leveraging DOE credibility for private client benefit",
  "proeth:requiresCapability": [
    "Coal bed methane technical expertise",
    "Expert witness testimony skills",
    "Regulatory proceeding participation"
  ],
  "proeth:temporalMarker": "BER Case 07-12, 2007",
  "proeth:violatesObligation": [
    "Obligation to be truthful and honest in professional reports and testimony",
    "Obligation to fully disclose affiliations and conflicts of interest",
    "Obligation to serve as faithful agent to DOE without private conflicts in the same domain",
    "Obligation to avoid misleading clients, employers, and the public"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "DOE Engineer Testifies Without Full Disclosure"
}

Description: Engineer A (BER 07-12) chose to use a PowerPoint presentation bearing his US DOE job title and affiliation during testimony that was paid for by a private coal bed methane company, creating a misleading impression of governmental endorsement or official capacity.

Temporal Marker: BER Case 07-12, 2007, during regulatory hearing testimony

Mental State: deliberate or negligent (ambiguous per BER)

Intended Outcome: Present technical information effectively, with possible intent to leverage DOE institutional credibility to strengthen testimony on behalf of private client

Guided By Principles:
  • Honesty and transparency in professional representations
  • Avoidance of misrepresentation
  • Separation of public and private roles
Required Capabilities:
Technical presentation skills Coal bed methane domain expertise Expert witness communication
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: The engineer used his DOE-branded presentation likely because it was the most polished and authoritative version of his technical material, and because the DOE affiliation lent institutional credibility that strengthened the coal bed methane company's legal position. He may not have fully considered the misleading impression this created, or may have rationalized that he was merely presenting his own research.

Ethical Tension: The engineer's interest in presenting compelling, credible testimony vs. the duty not to misrepresent one's capacity or create false impressions of institutional endorsement; there is also tension between serving his paying private client effectively and his obligation not to deceive the adjudicative body about the nature and source of his expertise.

Learning Significance: Illustrates that misrepresentation does not require explicit false statements — using official branding in a private, paid capacity creates a false impression of government endorsement that is itself a form of deception. Teaches that engineers must actively manage the signals their professional materials send, particularly when those signals could mislead decision-makers about the independence or institutional backing of technical opinions.

Stakes: The credibility and legitimacy of the regulatory proceeding, the engineer's potential violation of federal ethics rules regarding use of government resources and position for private gain, the coal bed methane company's legal exposure if the testimony is later challenged, and the broader public interest in regulatory processes free from manufactured impressions of government support.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Create a new presentation that clearly identifies him as a private consultant and does not display his DOE title or affiliation
  • Add an explicit disclaimer slide at the beginning of the presentation stating that the views expressed are his own and do not represent the DOE
  • Withdraw from the engagement rather than present material that cannot be fairly used without implying government endorsement

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_DOE_Engineer_Uses_DOE-Branded_Presentation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Create a new presentation that clearly identifies him as a private consultant and does not display his DOE title or affiliation",
    "Add an explicit disclaimer slide at the beginning of the presentation stating that the views expressed are his own and do not represent the DOE",
    "Withdraw from the engagement rather than present material that cannot be fairly used without implying government endorsement"
  ],
  "proeth-scenario:characterMotivation": "The engineer used his DOE-branded presentation likely because it was the most polished and authoritative version of his technical material, and because the DOE affiliation lent institutional credibility that strengthened the coal bed methane company\u0027s legal position. He may not have fully considered the misleading impression this created, or may have rationalized that he was merely presenting his own research.",
  "proeth-scenario:consequencesIfAlternative": [
    "Creating a disclosure-appropriate presentation is the most straightforward solution \u2014 it preserves the technical content while eliminating the misleading branding, though it requires additional preparation effort",
    "A disclaimer slide is a minimal but meaningful step that partially mitigates the misrepresentation risk, though it may not fully counteract the visual authority of DOE branding throughout the presentation",
    "Withdrawing is the most conservative option and would eliminate all risk, but would breach the private consulting agreement and potentially expose the engineer to contractual liability while also depriving the company of its expert"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that misrepresentation does not require explicit false statements \u2014 using official branding in a private, paid capacity creates a false impression of government endorsement that is itself a form of deception. Teaches that engineers must actively manage the signals their professional materials send, particularly when those signals could mislead decision-makers about the independence or institutional backing of technical opinions.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s interest in presenting compelling, credible testimony vs. the duty not to misrepresent one\u0027s capacity or create false impressions of institutional endorsement; there is also tension between serving his paying private client effectively and his obligation not to deceive the adjudicative body about the nature and source of his expertise.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The credibility and legitimacy of the regulatory proceeding, the engineer\u0027s potential violation of federal ethics rules regarding use of government resources and position for private gain, the coal bed methane company\u0027s legal exposure if the testimony is later challenged, and the broader public interest in regulatory processes free from manufactured impressions of government support.",
  "proeth:description": "Engineer A (BER 07-12) chose to use a PowerPoint presentation bearing his US DOE job title and affiliation during testimony that was paid for by a private coal bed methane company, creating a misleading impression of governmental endorsement or official capacity.",
  "proeth:foreseenUnintendedEffects": [
    "Audience and media would associate testimony with DOE official position",
    "Newspaper would report him as a \u0027US DOE researcher\u0027 rather than a private consultant",
    "Regulatory body would be misled about the independence and sponsorship of the testimony"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and transparency in professional representations",
    "Avoidance of misrepresentation",
    "Separation of public and private roles"
  ],
  "proeth:hasAgent": "Engineer A (BER 07-12) (DOE Employee testifying as private consultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Testimony effectiveness for private client vs. Accurate representation of role and affiliation",
    "proeth:resolutionReasoning": "The BER found the use of DOE branding in a privately paid consulting context to be entirely inappropriate, whether the result of carelessness or intentional misrepresentation"
  },
  "proeth:hasMentalState": "deliberate or negligent (ambiguous per BER)",
  "proeth:intendedOutcome": "Present technical information effectively, with possible intent to leverage DOE institutional credibility to strengthen testimony on behalf of private client",
  "proeth:requiresCapability": [
    "Technical presentation skills",
    "Coal bed methane domain expertise",
    "Expert witness communication"
  ],
  "proeth:temporalMarker": "BER Case 07-12, 2007, during regulatory hearing testimony",
  "proeth:violatesObligation": [
    "Obligation to be truthful and avoid misleading representations in professional practice",
    "Obligation to clearly distinguish private consulting role from public employment role",
    "Obligation to avoid using public employment status to benefit private clients",
    "Obligation of faithful agency to DOE employer"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "DOE Engineer Uses DOE-Branded Presentation"
}

Description: Engineer A, in the present case, chose to accept Attorney X's request to conduct a forensic investigation and potentially serve as an expert witness for a boiler manufacturer defendant, despite holding the position of chair of a boiler code standards and safety committee within a professional engineering society.

Temporal Marker: Present case, at time of engagement acceptance

Mental State: deliberate

Intended Outcome: Provide forensic engineering expertise to the defense in a pressure vessel explosion personal injury case and fulfill a professional consulting engagement

Fulfills Obligations:
  • Exercising professional competence in forensic engineering within his area of expertise
  • Responding to legitimate professional request for expert services
Guided By Principles:
  • Competent professional service
  • Honest and objective forensic engineering
  • Public safety through expert participation in litigation
Required Capabilities:
Mechanical engineering expertise Forensic engineering investigation methods Pressure vessel and boiler safety knowledge Expert witness testimony skills
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A was likely motivated by financial compensation for forensic work, intellectual interest in a technically complex boiler safety case, and professional desire to contribute expertise to the legal process. He may have initially viewed his committee chairmanship as an asset (demonstrating expertise) rather than a liability (creating a conflict), particularly before discovering Engineer B's subcommittee membership.

Ethical Tension: The engineer's legitimate interest in practicing forensic engineering and earning compensation vs. his duty of impartiality and independence as chair of the standards committee that governs the very technical domain at issue; accepting the engagement risks compromising both his forensic objectivity and the perceived neutrality of the standards committee he leads.

Learning Significance: Teaches that conflicts of interest in expert witness work are not limited to financial relationships — positional authority in a technical standards body creates structural conflicts when that body's standards are directly at issue in litigation. Also illustrates that the discovery of additional conflict factors (Engineer B's subcommittee role) after initial acceptance creates an obligation to reassess, not merely disclose.

Stakes: The integrity of the boiler code standards committee, the fairness of the litigation to both parties, Engineer A's professional reputation and potential liability if the conflict is later challenged, the defendant manufacturer's legal strategy if their expert is disqualified, and the broader credibility of engineering standards bodies whose members serve as expert witnesses.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline the engagement entirely, citing his committee chairmanship as an irreconcilable structural conflict
  • Accept the engagement conditionally, pending review of all conflict factors and formal disclosure to all parties, with willingness to withdraw if conflicts cannot be managed
  • Consult with the professional engineering society's ethics board before accepting to determine whether the chairmanship role creates a disqualifying conflict

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_Engineer_A_Accepts_Forensic_Expert_Engagement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the engagement entirely, citing his committee chairmanship as an irreconcilable structural conflict",
    "Accept the engagement conditionally, pending review of all conflict factors and formal disclosure to all parties, with willingness to withdraw if conflicts cannot be managed",
    "Consult with the professional engineering society\u0027s ethics board before accepting to determine whether the chairmanship role creates a disqualifying conflict"
  ],
  "proeth-scenario:characterMotivation": "Engineer A was likely motivated by financial compensation for forensic work, intellectual interest in a technically complex boiler safety case, and professional desire to contribute expertise to the legal process. He may have initially viewed his committee chairmanship as an asset (demonstrating expertise) rather than a liability (creating a conflict), particularly before discovering Engineer B\u0027s subcommittee membership.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining is the most conservative and protective choice \u2014 it eliminates all conflict risk and preserves the committee\u0027s perceived neutrality, though it foregoes the engagement\u0027s professional and financial benefits",
    "Conditional acceptance with full disclosure and a structured review process is a reasonable middle path that demonstrates good faith, though it creates uncertainty for Attorney X and the defendant client",
    "Seeking a society ethics opinion before accepting is ideal from a governance standpoint \u2014 it produces authoritative guidance and demonstrates that Engineer A takes his institutional responsibilities seriously, but may delay the engagement beyond practical litigation timelines"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that conflicts of interest in expert witness work are not limited to financial relationships \u2014 positional authority in a technical standards body creates structural conflicts when that body\u0027s standards are directly at issue in litigation. Also illustrates that the discovery of additional conflict factors (Engineer B\u0027s subcommittee role) after initial acceptance creates an obligation to reassess, not merely disclose.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s legitimate interest in practicing forensic engineering and earning compensation vs. his duty of impartiality and independence as chair of the standards committee that governs the very technical domain at issue; accepting the engagement risks compromising both his forensic objectivity and the perceived neutrality of the standards committee he leads.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The integrity of the boiler code standards committee, the fairness of the litigation to both parties, Engineer A\u0027s professional reputation and potential liability if the conflict is later challenged, the defendant manufacturer\u0027s legal strategy if their expert is disqualified, and the broader credibility of engineering standards bodies whose members serve as expert witnesses.",
  "proeth:description": "Engineer A, in the present case, chose to accept Attorney X\u0027s request to conduct a forensic investigation and potentially serve as an expert witness for a boiler manufacturer defendant, despite holding the position of chair of a boiler code standards and safety committee within a professional engineering society.",
  "proeth:foreseenUnintendedEffects": [
    "Potential appearance of conflict given his committee chairmanship over the same technical domain",
    "Risk of organizational conflict if opposing expert Engineer B is discovered to be a subcommittee member under his authority"
  ],
  "proeth:fulfillsObligation": [
    "Exercising professional competence in forensic engineering within his area of expertise",
    "Responding to legitimate professional request for expert services"
  ],
  "proeth:guidedByPrinciple": [
    "Competent professional service",
    "Honest and objective forensic engineering",
    "Public safety through expert participation in litigation"
  ],
  "proeth:hasAgent": "Engineer A (Present case) (Mechanical engineer, forensic expert, and boiler code committee chair)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private forensic consulting role vs. Volunteer public-benefit standards committee role",
    "proeth:resolutionReasoning": "The BER distinguished this case from prior cases, finding that Engineer A\u0027s volunteer standards role is independent of his private forensic expertise, and that no direct conflict exists absent other undisclosed business relationships, provided disclosure obligations are honored"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide forensic engineering expertise to the defense in a pressure vessel explosion personal injury case and fulfill a professional consulting engagement",
  "proeth:requiresCapability": [
    "Mechanical engineering expertise",
    "Forensic engineering investigation methods",
    "Pressure vessel and boiler safety knowledge",
    "Expert witness testimony skills"
  ],
  "proeth:temporalMarker": "Present case, at time of engagement acceptance",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Accepts Forensic Expert Engagement"
}

Description: Engineer A is obligated to, and must choose to, fully disclose to Attorney X his role as chairman of the boiler code standards and safety committee and the fact that opposing expert Engineer B is a member of one of his subcommittees, as required by his ethical duties of transparency.

Temporal Marker: Present case, upon discovery of Engineer B's subcommittee membership

Mental State: deliberate

Intended Outcome: Ensure Attorney X is fully informed of the organizational relationship between Engineer A and Engineer B so that informed decisions can be made about the engagement and any necessary legal or ethical steps

Fulfills Obligations:
  • Obligation to fully disclose conflicts of interest or potential conflicts to retaining counsel
  • Obligation to be honest and transparent in professional relationships
  • Obligation to act as faithful agent to the client with full candor
Guided By Principles:
  • Full and timely disclosure of material relationships
  • Honesty and integrity in professional practice
  • Faithful agency to client with transparency
Required Capabilities:
Professional judgment about conflict identification Clear communication of organizational relationships to legal counsel
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A is ethically and professionally obligated to disclose — this is less a voluntary motivation than a mandatory duty. However, his willingness to make full disclosure reflects professional integrity, an understanding that Attorney X needs complete information to assess litigation strategy, and recognition that concealing these facts would expose him to far greater professional and legal risk than disclosure.

Ethical Tension: The duty of full transparency to the retaining attorney vs. the potential concern that complete disclosure might lead to his disqualification from a professionally and financially attractive engagement; there is also tension between his role as a zealous litigation supporter for the defendant and his independent obligation as a professional to ensure the legal process has accurate information about all experts' relationships.

Learning Significance: Teaches that disclosure obligations in expert witness contexts are not merely aspirational — they are mandatory professional duties that protect the integrity of the legal process, the retaining attorney's ability to make informed strategic decisions, and the engineer's own professional standing. Also illustrates that disclosure is not the end of the analysis but the beginning: after disclosure, both parties must evaluate whether the engagement can ethically proceed.

Stakes: Attorney X's ability to make an informed decision about expert selection, the defendant manufacturer's litigation strategy, the fairness of proceedings to the plaintiff if Engineer A's committee authority could be used inappropriately, Engineer A's professional license and reputation if non-disclosure is later discovered, and the integrity of the expert witness system.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Disclose the committee chairmanship but omit or minimize the significance of Engineer B's subcommittee membership, hoping the attorney will not probe further
  • Delay disclosure until after formally accepting the engagement, treating it as a subsequent development rather than a threshold consideration
  • Disclose everything and proactively recommend that Attorney X seek independent ethics guidance before proceeding with the engagement

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_Engineer_A_Discloses_Committee_Role_to_Attorney_X",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose the committee chairmanship but omit or minimize the significance of Engineer B\u0027s subcommittee membership, hoping the attorney will not probe further",
    "Delay disclosure until after formally accepting the engagement, treating it as a subsequent development rather than a threshold consideration",
    "Disclose everything and proactively recommend that Attorney X seek independent ethics guidance before proceeding with the engagement"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is ethically and professionally obligated to disclose \u2014 this is less a voluntary motivation than a mandatory duty. However, his willingness to make full disclosure reflects professional integrity, an understanding that Attorney X needs complete information to assess litigation strategy, and recognition that concealing these facts would expose him to far greater professional and legal risk than disclosure.",
  "proeth-scenario:consequencesIfAlternative": [
    "Partial disclosure is ethically insufficient and strategically dangerous \u2014 if Engineer B\u0027s subcommittee membership is later discovered, the incomplete disclosure will appear deliberately deceptive and could result in disqualification, sanctions, and disciplinary proceedings",
    "Delayed disclosure treats a threshold conflict as an afterthought and deprives Attorney X of information needed for initial engagement decisions; it also weakens the argument that Engineer A acted in good faith",
    "Proactive recommendation of independent ethics review is the most professionally responsible option \u2014 it demonstrates that Engineer A prioritizes process integrity over his own participation and gives Attorney X the clearest possible picture of the risks involved"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that disclosure obligations in expert witness contexts are not merely aspirational \u2014 they are mandatory professional duties that protect the integrity of the legal process, the retaining attorney\u0027s ability to make informed strategic decisions, and the engineer\u0027s own professional standing. Also illustrates that disclosure is not the end of the analysis but the beginning: after disclosure, both parties must evaluate whether the engagement can ethically proceed.",
  "proeth-scenario:ethicalTension": "The duty of full transparency to the retaining attorney vs. the potential concern that complete disclosure might lead to his disqualification from a professionally and financially attractive engagement; there is also tension between his role as a zealous litigation supporter for the defendant and his independent obligation as a professional to ensure the legal process has accurate information about all experts\u0027 relationships.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Attorney X\u0027s ability to make an informed decision about expert selection, the defendant manufacturer\u0027s litigation strategy, the fairness of proceedings to the plaintiff if Engineer A\u0027s committee authority could be used inappropriately, Engineer A\u0027s professional license and reputation if non-disclosure is later discovered, and the integrity of the expert witness system.",
  "proeth:description": "Engineer A is obligated to, and must choose to, fully disclose to Attorney X his role as chairman of the boiler code standards and safety committee and the fact that opposing expert Engineer B is a member of one of his subcommittees, as required by his ethical duties of transparency.",
  "proeth:foreseenUnintendedEffects": [
    "Attorney X may reconsider the engagement or seek different expert",
    "Disclosure may complicate litigation strategy for the defense",
    "Transparency may reduce Engineer A\u0027s competitive advantage as an expert"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to fully disclose conflicts of interest or potential conflicts to retaining counsel",
    "Obligation to be honest and transparent in professional relationships",
    "Obligation to act as faithful agent to the client with full candor"
  ],
  "proeth:guidedByPrinciple": [
    "Full and timely disclosure of material relationships",
    "Honesty and integrity in professional practice",
    "Faithful agency to client with transparency"
  ],
  "proeth:hasAgent": "Engineer A (Present case) (Forensic expert and boiler code committee chair)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Full disclosure obligation vs. Risk of losing or complicating the engagement",
    "proeth:resolutionReasoning": "The BER identifies disclosure as a clear and mandatory obligation; Engineer A must prioritize transparency over engagement preservation, consistent with the principle that honesty and integrity are non-negotiable in forensic engineering"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Ensure Attorney X is fully informed of the organizational relationship between Engineer A and Engineer B so that informed decisions can be made about the engagement and any necessary legal or ethical steps",
  "proeth:requiresCapability": [
    "Professional judgment about conflict identification",
    "Clear communication of organizational relationships to legal counsel"
  ],
  "proeth:temporalMarker": "Present case, upon discovery of Engineer B\u0027s subcommittee membership",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Discloses Committee Role to Attorney X"
}

Description: Engineer A must choose to refrain from engaging in any written or verbal communications with Engineer B regarding the pending litigation without direction from legal counsel, while still maintaining appropriate professional conduct in his committee chair role.

Temporal Marker: Present case, throughout duration of litigation engagement

Mental State: deliberate

Intended Outcome: Protect the integrity of the litigation process, avoid improper influence on the opposing expert through his organizational authority, and preserve the fairness of both the legal proceedings and the committee governance structure

Fulfills Obligations:
  • Obligation to respect the professional role and independence of Engineer B as a subcommittee member
  • Obligation to maintain integrity of the litigation process
  • Obligation to avoid using organizational authority to improperly influence opposing expert
Guided By Principles:
  • Respect for colleagues' professional independence
  • Integrity and fairness in adversarial professional proceedings
  • Avoidance of improper influence through positional authority
Required Capabilities:
Professional judgment about appropriate boundaries between organizational and adversarial roles Coordination with legal counsel on permissible communications Committee governance skills
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A is motivated by his understanding of litigation protocol, his duty to the defendant client, and his recognition that any direct communication with the opposing expert about the case could constitute improper ex parte contact, potentially tainting the proceedings or exposing him to accusations of attempting to influence the opposing expert through his committee authority.

Ethical Tension: The ongoing professional relationship and committee responsibilities that Engineer A and Engineer B share as chair and subcommittee member vs. the requirement that litigation adversaries communicate only through proper legal channels; there is also tension between maintaining collegial professional relationships within the engineering society and the adversarial posture required in litigation.

Learning Significance: Teaches that accepting a forensic expert role requires careful compartmentalization of professional relationships — the engineer must simultaneously maintain appropriate professional conduct in non-litigation contexts while strictly avoiding any litigation-related communications that bypass legal counsel. Also illustrates that the committee chair role creates a unique power dynamic that makes even innocent professional communications potentially coercive or improper.

Stakes: The integrity of the litigation process, the rights of both parties to have their experts operate without improper influence or contact, Engineer A's potential liability for witness tampering or improper contact if boundaries are crossed, the professional relationship between Engineer A and Engineer B within the standards committee, and the engineering society's reputation if its committee structure is perceived as being leveraged in litigation.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Temporarily recuse himself from chairing Engineer B's subcommittee for the duration of the litigation to eliminate the structural power imbalance entirely
  • Communicate with Engineer B about committee matters only through formal written channels with copies to legal counsel, creating a documented record of appropriate boundaries
  • Seek guidance from the engineering society's leadership about how to manage the committee relationship during pending litigation involving both a chair and a subcommittee member as opposing experts

Narrative Role: resolution

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Action_Engineer_A_Avoids_Ex_Parte_Litigation_Communicatio",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Temporarily recuse himself from chairing Engineer B\u0027s subcommittee for the duration of the litigation to eliminate the structural power imbalance entirely",
    "Communicate with Engineer B about committee matters only through formal written channels with copies to legal counsel, creating a documented record of appropriate boundaries",
    "Seek guidance from the engineering society\u0027s leadership about how to manage the committee relationship during pending litigation involving both a chair and a subcommittee member as opposing experts"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by his understanding of litigation protocol, his duty to the defendant client, and his recognition that any direct communication with the opposing expert about the case could constitute improper ex parte contact, potentially tainting the proceedings or exposing him to accusations of attempting to influence the opposing expert through his committee authority.",
  "proeth-scenario:consequencesIfAlternative": [
    "Temporary recusal from the subcommittee is the cleanest structural solution \u2014 it eliminates the power imbalance and any appearance of impropriety, though it may disrupt committee work and require explanation to society leadership",
    "Formal written-only communication with legal counsel copies creates a protective record and maintains transparency, though it may feel awkward in a collegial professional society context and could signal the conflict to other committee members",
    "Seeking engineering society guidance is prudent institutional behavior that protects both Engineer A and the society, produces documented guidance, and may result in formal protocols that benefit future similar situations \u2014 though it requires disclosure of the litigation involvement to society leadership"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that accepting a forensic expert role requires careful compartmentalization of professional relationships \u2014 the engineer must simultaneously maintain appropriate professional conduct in non-litigation contexts while strictly avoiding any litigation-related communications that bypass legal counsel. Also illustrates that the committee chair role creates a unique power dynamic that makes even innocent professional communications potentially coercive or improper.",
  "proeth-scenario:ethicalTension": "The ongoing professional relationship and committee responsibilities that Engineer A and Engineer B share as chair and subcommittee member vs. the requirement that litigation adversaries communicate only through proper legal channels; there is also tension between maintaining collegial professional relationships within the engineering society and the adversarial posture required in litigation.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "The integrity of the litigation process, the rights of both parties to have their experts operate without improper influence or contact, Engineer A\u0027s potential liability for witness tampering or improper contact if boundaries are crossed, the professional relationship between Engineer A and Engineer B within the standards committee, and the engineering society\u0027s reputation if its committee structure is perceived as being leveraged in litigation.",
  "proeth:description": "Engineer A must choose to refrain from engaging in any written or verbal communications with Engineer B regarding the pending litigation without direction from legal counsel, while still maintaining appropriate professional conduct in his committee chair role.",
  "proeth:foreseenUnintendedEffects": [
    "Normal committee governance interactions with Engineer B may need to be carefully managed or limited",
    "Engineer B may perceive committee interactions differently given the adversarial litigation context",
    "Failure to maintain this separation could compromise both the litigation and the committee\u0027s integrity"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to respect the professional role and independence of Engineer B as a subcommittee member",
    "Obligation to maintain integrity of the litigation process",
    "Obligation to avoid using organizational authority to improperly influence opposing expert"
  ],
  "proeth:guidedByPrinciple": [
    "Respect for colleagues\u0027 professional independence",
    "Integrity and fairness in adversarial professional proceedings",
    "Avoidance of improper influence through positional authority"
  ],
  "proeth:hasAgent": "Engineer A (Present case) (Forensic expert, committee chair, and adversary to Engineer B in litigation)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Committee governance responsibilities vs. Litigation adversarial boundaries",
    "proeth:resolutionReasoning": "The BER requires Engineer A to be respectful of Engineer B\u0027s committee role while strictly avoiding any litigation-related communications without legal counsel guidance, effectively requiring careful compartmentalization of the two professional relationships"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Protect the integrity of the litigation process, avoid improper influence on the opposing expert through his organizational authority, and preserve the fairness of both the legal proceedings and the committee governance structure",
  "proeth:requiresCapability": [
    "Professional judgment about appropriate boundaries between organizational and adversarial roles",
    "Coordination with legal counsel on permissible communications",
    "Committee governance skills"
  ],
  "proeth:temporalMarker": "Present case, throughout duration of litigation engagement",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Avoids Ex Parte Litigation Communications with Engineer B"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changes

Description: John Doe's simultaneous service as county engineer, planning board member, and private consultant creates an inherent structural conflict of interest that becomes apparent when his private work intersects with his official duties. This conflict is not a single decision but an ongoing state condition triggered by role accumulation.

Temporal Marker: BER Case 67-1 (1967)

Activates Constraints:
  • Conflict_of_Interest_Prohibition
  • Public_Trust_Preservation
  • Impartiality_Requirement
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Public and colleagues may feel a diffuse unease or betrayal upon recognizing the structural impropriety; Doe himself may rationalize the arrangement as manageable, experiencing cognitive dissonance rather than alarm

Stakeholder Consequences:
  • john_doe: Professional reputation vulnerable to challenge; legal exposure for decisions made under conflict
  • county_government: Official decisions tainted by appearance of impropriety; institutional credibility undermined
  • public: Loss of assurance that planning decisions reflect public interest rather than private gain
  • engineering_profession: Precedent-setting case that defines conflict-of-interest norms for decades

Learning Moment: Structural conflicts of interest arise automatically from role combinations, not only from specific corrupt acts; engineers must proactively audit their role portfolios for incompatibilities before they manifest in decisions

Ethical Implications: Reveals that structural position alone can compromise integrity independent of intent; highlights tension between professional opportunity and public trust obligations; demonstrates that self-regulation requires engineers to recognize conflicts before external parties identify them

Discussion Prompts:
  • Can a conflict of interest exist even if the engineer acts with complete subjective good faith? Why or why not?
  • At what point in Doe's role accumulation did an ethical obligation to disclose or withdraw arise?
  • How should professional codes distinguish between the appearance of conflict and actual conflict, and does the distinction matter ethically?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Event_Doe_Triple_Role_Conflict_Emerges",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Can a conflict of interest exist even if the engineer acts with complete subjective good faith? Why or why not?",
    "At what point in Doe\u0027s role accumulation did an ethical obligation to disclose or withdraw arise?",
    "How should professional codes distinguish between the appearance of conflict and actual conflict, and does the distinction matter ethically?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Public and colleagues may feel a diffuse unease or betrayal upon recognizing the structural impropriety; Doe himself may rationalize the arrangement as manageable, experiencing cognitive dissonance rather than alarm",
  "proeth-scenario:ethicalImplications": "Reveals that structural position alone can compromise integrity independent of intent; highlights tension between professional opportunity and public trust obligations; demonstrates that self-regulation requires engineers to recognize conflicts before external parties identify them",
  "proeth-scenario:learningMoment": "Structural conflicts of interest arise automatically from role combinations, not only from specific corrupt acts; engineers must proactively audit their role portfolios for incompatibilities before they manifest in decisions",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "county_government": "Official decisions tainted by appearance of impropriety; institutional credibility undermined",
    "engineering_profession": "Precedent-setting case that defines conflict-of-interest norms for decades",
    "john_doe": "Professional reputation vulnerable to challenge; legal exposure for decisions made under conflict",
    "public": "Loss of assurance that planning decisions reflect public interest rather than private gain"
  },
  "proeth:activatesConstraint": [
    "Conflict_of_Interest_Prohibition",
    "Public_Trust_Preservation",
    "Impartiality_Requirement"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/129#Action_Doe_Prepares_Private_Subdivision_Plans",
  "proeth:causesStateChange": "Doe transitions from holding multiple roles independently to a state where those roles actively conflict; ethical violation condition is now structurally present regardless of subsequent actions",
  "proeth:createsObligation": [
    "Disclose_Conflicting_Roles",
    "Recuse_From_Conflicted_Decisions",
    "Cease_Private_Work_Conflicting_With_Official_Duties"
  ],
  "proeth:description": "John Doe\u0027s simultaneous service as county engineer, planning board member, and private consultant creates an inherent structural conflict of interest that becomes apparent when his private work intersects with his official duties. This conflict is not a single decision but an ongoing state condition triggered by role accumulation.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "BER Case 67-1 (1967)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Doe Triple Role Conflict Emerges"
}

Description: Doe's private subdivision plans receive official approval through a process in which Doe himself participates both as recommending engineer and as voting board member, completing the full cycle of conflicted self-dealing. This outcome is the realized harm of the structural conflict.

Temporal Marker: BER Case 67-1 (1967) — subsequent to plan preparation

Activates Constraints:
  • Decision_Validity_Challenge_Constraint
  • Public_Record_Integrity_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: For the public, a retrospective sense of betrayal when the conflict is revealed; for Doe, potential rationalization that the plans were technically sound; for oversight bodies, institutional embarrassment

Stakeholder Consequences:
  • john_doe: Exposure to professional sanctions, potential reversal of approved work, reputational damage
  • county_government: Legal liability for approvals made under undisclosed conflict; precedent for challenging other decisions
  • public: Uncertainty about whether approved subdivision serves public interest or private profit
  • engineering_profession: Case becomes landmark reference for conflict-of-interest standards in dual-role situations

Learning Moment: The completion of a conflicted decision loop — where the same person recommends and approves their own private work — represents the maximum realization of conflict-of-interest harm; students should understand that each step in this chain was an opportunity for prevention

Ethical Implications: Demonstrates that procedural integrity is independently valuable from substantive outcome quality; reveals how concentration of authority enables self-dealing even by otherwise competent professionals; raises questions about whether good outcomes can justify compromised processes

Discussion Prompts:
  • Should the technical quality of Doe's plans be relevant to the ethical evaluation of the approval process?
  • What institutional safeguards should exist to prevent a single official from controlling both the technical recommendation and the approval vote?
  • If the plans were objectively good for the county, does that mitigate or eliminate the ethical violation?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Event_Plans_Approved_Under_Conflict",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Should the technical quality of Doe\u0027s plans be relevant to the ethical evaluation of the approval process?",
    "What institutional safeguards should exist to prevent a single official from controlling both the technical recommendation and the approval vote?",
    "If the plans were objectively good for the county, does that mitigate or eliminate the ethical violation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "For the public, a retrospective sense of betrayal when the conflict is revealed; for Doe, potential rationalization that the plans were technically sound; for oversight bodies, institutional embarrassment",
  "proeth-scenario:ethicalImplications": "Demonstrates that procedural integrity is independently valuable from substantive outcome quality; reveals how concentration of authority enables self-dealing even by otherwise competent professionals; raises questions about whether good outcomes can justify compromised processes",
  "proeth-scenario:learningMoment": "The completion of a conflicted decision loop \u2014 where the same person recommends and approves their own private work \u2014 represents the maximum realization of conflict-of-interest harm; students should understand that each step in this chain was an opportunity for prevention",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "county_government": "Legal liability for approvals made under undisclosed conflict; precedent for challenging other decisions",
    "engineering_profession": "Case becomes landmark reference for conflict-of-interest standards in dual-role situations",
    "john_doe": "Exposure to professional sanctions, potential reversal of approved work, reputational damage",
    "public": "Uncertainty about whether approved subdivision serves public interest or private profit"
  },
  "proeth:activatesConstraint": [
    "Decision_Validity_Challenge_Constraint",
    "Public_Record_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/129#Action_Doe_Votes_to_Approve_Own_Plans",
  "proeth:causesStateChange": "Official approval record now exists for plans prepared by the approving official; approval is legally and ethically suspect; downstream reliance on approval creates compounding harm potential",
  "proeth:createsObligation": [
    "Review_Tainted_Approval_For_Validity",
    "Report_Conflict_To_Governing_Body",
    "Consider_Rescission_Of_Approval"
  ],
  "proeth:description": "Doe\u0027s private subdivision plans receive official approval through a process in which Doe himself participates both as recommending engineer and as voting board member, completing the full cycle of conflicted self-dealing. This outcome is the realized harm of the structural conflict.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "BER Case 67-1 (1967) \u2014 subsequent to plan preparation",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Plans Approved Under Conflict"
}

Description: When the state DOT traffic engineer is approached about part-time consulting for a former firm, the potential for conflicts at the municipal level becomes immediately apparent as an automatic consequence of the role combination, before any work is actually performed.

Temporal Marker: BER Case 02-8 (2002) — at time of approach

Activates Constraints:
  • Conflict_of_Interest_Pre-Screening_Constraint
  • Government_Employment_Outside_Work_Constraint
  • Impartiality_Preservation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer may feel excitement at professional opportunity and financial benefit; simultaneous anxiety about navigating dual loyalties; former firm may feel confident the arrangement is manageable

Stakeholder Consequences:
  • dot_engineer: Career risk if conflict materializes without prior disclosure; financial opportunity if properly managed
  • former_firm: Risk of tainting work product if conflict is later discovered; competitive advantage if engineer's DOT knowledge is improperly leveraged
  • municipalities: Risk of biased technical reviews if engineer's private work influences official DOT positions
  • public: Potential for traffic safety decisions influenced by private financial interests

Learning Moment: Conflict potential arises at the moment of approach, not at the moment of acceptance; engineers have pre-decisional obligations to screen for conflicts before agreeing to any engagement that could compromise their primary duties

Ethical Implications: Highlights the prophylactic nature of conflict-of-interest rules — they apply before harm occurs; reveals tension between individual economic freedom and public servant obligations; raises questions about the adequacy of self-screening versus institutional review

Discussion Prompts:
  • Does the mere approach by a former employer create any ethical obligations for the DOT engineer before they decide whether to accept?
  • How should an engineer weigh financial opportunity against institutional loyalty and public trust obligations?
  • What screening process should exist within government agencies to manage outside employment requests?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Event_Municipal_Conflict_Potential_Identified",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the mere approach by a former employer create any ethical obligations for the DOT engineer before they decide whether to accept?",
    "How should an engineer weigh financial opportunity against institutional loyalty and public trust obligations?",
    "What screening process should exist within government agencies to manage outside employment requests?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer may feel excitement at professional opportunity and financial benefit; simultaneous anxiety about navigating dual loyalties; former firm may feel confident the arrangement is manageable",
  "proeth-scenario:ethicalImplications": "Highlights the prophylactic nature of conflict-of-interest rules \u2014 they apply before harm occurs; reveals tension between individual economic freedom and public servant obligations; raises questions about the adequacy of self-screening versus institutional review",
  "proeth-scenario:learningMoment": "Conflict potential arises at the moment of approach, not at the moment of acceptance; engineers have pre-decisional obligations to screen for conflicts before agreeing to any engagement that could compromise their primary duties",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "dot_engineer": "Career risk if conflict materializes without prior disclosure; financial opportunity if properly managed",
    "former_firm": "Risk of tainting work product if conflict is later discovered; competitive advantage if engineer\u0027s DOT knowledge is improperly leveraged",
    "municipalities": "Risk of biased technical reviews if engineer\u0027s private work influences official DOT positions",
    "public": "Potential for traffic safety decisions influenced by private financial interests"
  },
  "proeth:activatesConstraint": [
    "Conflict_of_Interest_Pre-Screening_Constraint",
    "Government_Employment_Outside_Work_Constraint",
    "Impartiality_Preservation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/129#Action_DOT_Engineer_Accepts_Part-Time_Consulting_Offer",
  "proeth:causesStateChange": "Engineer moves from single-employer state to potential dual-role state; conflict risk condition is activated even before acceptance; obligation to screen precedes any decision to accept",
  "proeth:createsObligation": [
    "Conduct_Conflict_Screening_Before_Acceptance",
    "Disclose_Potential_Engagement_To_DOT_Ethics_Office",
    "Identify_All_Municipalities_Where_Conflict_Could_Arise"
  ],
  "proeth:description": "When the state DOT traffic engineer is approached about part-time consulting for a former firm, the potential for conflicts at the municipal level becomes immediately apparent as an automatic consequence of the role combination, before any work is actually performed.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "BER Case 02-8 (2002) \u2014 at time of approach",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Municipal Conflict Potential Identified"
}

Description: When the DOE engineer uses DOE-branded presentation materials while testifying as a private consultant, the audience automatically perceives the testimony as carrying DOE institutional authority, creating a misrepresentation outcome that occurs as a consequence of the presentation choice rather than as a separately intended deception.

Temporal Marker: BER Case 07-12 (2007) — during testimony

Activates Constraints:
  • Truthfulness_In_Public_Statements_Constraint
  • Affiliation_Disclosure_Constraint
  • Institutional_Representation_Accuracy_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer may be unaware of the perceptual impact, experiencing confidence rather than guilt; opposing parties may feel deceived upon discovering the private capacity; tribunal may feel manipulated if misrepresentation is later revealed

Stakeholder Consequences:
  • doe_engineer: Risk of professional sanctions for misrepresentation; potential invalidation of testimony; DOE employment jeopardy
  • coal_bed_methane_company: Testimony advantage gained through misrepresentation may be challenged or reversed
  • opposing_parties: Prejudiced by testimony that appeared to carry government institutional authority
  • doe_institution: Institutional reputation implicated in private litigation without authorization
  • tribunal: Record potentially compromised by misattributed expert testimony

Learning Moment: Misrepresentation can occur through omission and context as much as through affirmative false statements; engineers must actively manage how their institutional affiliations are perceived, especially when operating in dual capacities

Ethical Implications: Reveals that honesty obligations extend to managing reasonable audience inferences, not just literal statement accuracy; highlights the special responsibilities of expert witnesses to courts and public processes; demonstrates how institutional credibility can be inappropriately leveraged for private benefit

Discussion Prompts:
  • Is there a meaningful ethical difference between actively claiming DOE authority and passively allowing DOE branding to imply it?
  • What affirmative disclosure obligations does an expert witness have regarding the capacity in which they are testifying?
  • How should professional codes address the use of institutional resources and branding in private consulting engagements?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Event_DOE_Affiliation_Misperception_Created",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is there a meaningful ethical difference between actively claiming DOE authority and passively allowing DOE branding to imply it?",
    "What affirmative disclosure obligations does an expert witness have regarding the capacity in which they are testifying?",
    "How should professional codes address the use of institutional resources and branding in private consulting engagements?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer may be unaware of the perceptual impact, experiencing confidence rather than guilt; opposing parties may feel deceived upon discovering the private capacity; tribunal may feel manipulated if misrepresentation is later revealed",
  "proeth-scenario:ethicalImplications": "Reveals that honesty obligations extend to managing reasonable audience inferences, not just literal statement accuracy; highlights the special responsibilities of expert witnesses to courts and public processes; demonstrates how institutional credibility can be inappropriately leveraged for private benefit",
  "proeth-scenario:learningMoment": "Misrepresentation can occur through omission and context as much as through affirmative false statements; engineers must actively manage how their institutional affiliations are perceived, especially when operating in dual capacities",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "coal_bed_methane_company": "Testimony advantage gained through misrepresentation may be challenged or reversed",
    "doe_engineer": "Risk of professional sanctions for misrepresentation; potential invalidation of testimony; DOE employment jeopardy",
    "doe_institution": "Institutional reputation implicated in private litigation without authorization",
    "opposing_parties": "Prejudiced by testimony that appeared to carry government institutional authority",
    "tribunal": "Record potentially compromised by misattributed expert testimony"
  },
  "proeth:activatesConstraint": [
    "Truthfulness_In_Public_Statements_Constraint",
    "Affiliation_Disclosure_Constraint",
    "Institutional_Representation_Accuracy_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/129#Action_DOE_Engineer_Uses_DOE-Branded_Presentation",
  "proeth:causesStateChange": "Testimony record now contains implicit misrepresentation of institutional affiliation; legal and professional record is potentially tainted; DOE\u0027s institutional position may be incorrectly inferred from private expert testimony",
  "proeth:createsObligation": [
    "Immediately_Clarify_Capacity_Of_Testimony",
    "Disclose_Private_Consultant_Relationship",
    "Correct_Any_Record_That_Misattributes_Testimony_To_DOE"
  ],
  "proeth:description": "When the DOE engineer uses DOE-branded presentation materials while testifying as a private consultant, the audience automatically perceives the testimony as carrying DOE institutional authority, creating a misrepresentation outcome that occurs as a consequence of the presentation choice rather than as a separately intended deception.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "BER Case 07-12 (2007) \u2014 during testimony",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "DOE Affiliation Misperception Created"
}

Description: Engineer A discovers that Engineer B, who serves as the plaintiff's expert witness in the boiler litigation, is also a member of a subcommittee that Engineer A chairs, creating an automatic dual-relationship condition with implications for both the litigation and the committee's integrity.

Temporal Marker: Present case — upon Engineer A's review of the engagement

Activates Constraints:
  • Adversarial_Relationship_Disclosure_Constraint
  • Committee_Integrity_Preservation_Constraint
  • Conflict_of_Interest_Prohibition
  • Ex_Parte_Communication_Prohibition
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A likely experiences alarm and discomfort at the discovery; concern about professional obligations pulling in multiple directions; potential awkwardness about the authority differential with Engineer B; Attorney X may feel frustration at the complication; Engineer B may feel vulnerable given the power imbalance

Stakeholder Consequences:
  • engineer_a: Must navigate competing professional obligations; risk of appearing to leverage committee authority over opposing expert; potential need to withdraw from lucrative engagement
  • engineer_b: Professional vulnerability due to power imbalance with committee chair who is now litigation adversary; risk of committee participation being chilled by litigation dynamic
  • attorney_x: Retained expert may need to withdraw or disclose complications that affect case strategy
  • boiler_manufacturer_defendant: Expert witness situation becomes complicated; case preparation may be disrupted
  • plaintiff: Risk that committee chair's authority over their expert creates improper pressure
  • boiler_code_committee: Committee integrity threatened by litigation dynamics between chair and subcommittee member
  • public_safety: Boiler code standards process may be compromised if committee relationships are tainted by litigation adversarialism

Learning Moment: Discovery of a pre-existing professional relationship with an opposing party is itself an ethically significant event that triggers immediate disclosure and assessment obligations; the power differential between a committee chair and a subcommittee member adds a dimension of potential coercion that makes this conflict qualitatively more serious than a simple peer conflict

Ethical Implications: Reveals how power differentials within professional hierarchies can transform ordinary conflicts of interest into potential coercion situations; highlights the intersection of standards-body integrity with adversarial legal proceedings; raises questions about whether public safety bodies (like boiler code committees) require heightened conflict protections because their work affects the public beyond the immediate parties

Discussion Prompts:
  • Does Engineer A's authority over Engineer B's subcommittee participation create a coercive dynamic that makes this conflict more serious than one between professional equals? How should that power differential affect the ethical analysis?
  • Should Engineer A be required to withdraw from the expert engagement, the committee role, or both? What factors should govern that determination?
  • What obligations does Engineer A have to Engineer B directly, given the discovery of their dual relationship — and does Engineer B have any right to know about Engineer A's expert role before the litigation proceeds?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Event_Engineer_B_Subcommittee_Membership_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer A\u0027s authority over Engineer B\u0027s subcommittee participation create a coercive dynamic that makes this conflict more serious than one between professional equals? How should that power differential affect the ethical analysis?",
    "Should Engineer A be required to withdraw from the expert engagement, the committee role, or both? What factors should govern that determination?",
    "What obligations does Engineer A have to Engineer B directly, given the discovery of their dual relationship \u2014 and does Engineer B have any right to know about Engineer A\u0027s expert role before the litigation proceeds?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences alarm and discomfort at the discovery; concern about professional obligations pulling in multiple directions; potential awkwardness about the authority differential with Engineer B; Attorney X may feel frustration at the complication; Engineer B may feel vulnerable given the power imbalance",
  "proeth-scenario:ethicalImplications": "Reveals how power differentials within professional hierarchies can transform ordinary conflicts of interest into potential coercion situations; highlights the intersection of standards-body integrity with adversarial legal proceedings; raises questions about whether public safety bodies (like boiler code committees) require heightened conflict protections because their work affects the public beyond the immediate parties",
  "proeth-scenario:learningMoment": "Discovery of a pre-existing professional relationship with an opposing party is itself an ethically significant event that triggers immediate disclosure and assessment obligations; the power differential between a committee chair and a subcommittee member adds a dimension of potential coercion that makes this conflict qualitatively more serious than a simple peer conflict",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "Retained expert may need to withdraw or disclose complications that affect case strategy",
    "boiler_code_committee": "Committee integrity threatened by litigation dynamics between chair and subcommittee member",
    "boiler_manufacturer_defendant": "Expert witness situation becomes complicated; case preparation may be disrupted",
    "engineer_a": "Must navigate competing professional obligations; risk of appearing to leverage committee authority over opposing expert; potential need to withdraw from lucrative engagement",
    "engineer_b": "Professional vulnerability due to power imbalance with committee chair who is now litigation adversary; risk of committee participation being chilled by litigation dynamic",
    "plaintiff": "Risk that committee chair\u0027s authority over their expert creates improper pressure",
    "public_safety": "Boiler code standards process may be compromised if committee relationships are tainted by litigation adversarialism"
  },
  "proeth:activatesConstraint": [
    "Adversarial_Relationship_Disclosure_Constraint",
    "Committee_Integrity_Preservation_Constraint",
    "Conflict_of_Interest_Prohibition",
    "Ex_Parte_Communication_Prohibition"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/129#Action_Engineer_A_Accepts_Forensic_Expert_Engagement",
  "proeth:causesStateChange": "Engineer A\u0027s professional relationships now include a supervisory/authority relationship with Engineer B in committee context simultaneously with an adversarial relationship in litigation; both relationships are compromised by the other\u0027s existence; a structural conflict condition is now active",
  "proeth:createsObligation": [
    "Disclose_Dual_Relationship_To_All_Affected_Parties",
    "Assess_Whether_Committee_Role_Must_Be_Suspended",
    "Avoid_All_Ex_Parte_Litigation_Communications_With_Engineer_B",
    "Notify_Committee_Governance_Of_Potential_Conflict",
    "Evaluate_Whether_To_Withdraw_From_Expert_Engagement_Or_Committee_Role"
  ],
  "proeth:description": "Engineer A discovers that Engineer B, who serves as the plaintiff\u0027s expert witness in the boiler litigation, is also a member of a subcommittee that Engineer A chairs, creating an automatic dual-relationship condition with implications for both the litigation and the committee\u0027s integrity.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Present case \u2014 upon Engineer A\u0027s review of the engagement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer B Subcommittee Membership Discovered"
}

Description: When Engineer A discloses their committee chair role to Attorney X, a formal record of the conflict is created, which automatically shifts the ethical and legal responsibility landscape — Attorney X now has constructive knowledge of the conflict and Engineer A has satisfied an initial disclosure obligation.

Temporal Marker: Present case — following Engineer A's discovery of Engineer B's role

Activates Constraints:
  • Attorney_Informed_Consent_Requirement
  • Broader_Disclosure_Adequacy_Constraint
  • Continuing_Disclosure_Obligation
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A likely feels partial relief at having disclosed but residual anxiety about whether disclosure is sufficient; Attorney X may feel concern about case complications or confidence that the issue is now managed; the disclosure creates a moment of professional accountability

Stakeholder Consequences:
  • engineer_a: Partial satisfaction of disclosure obligations; continuing exposure if broader disclosure is required
  • attorney_x: Now has actual knowledge of conflict and bears responsibility for advising client and potentially the court
  • boiler_manufacturer_defendant: Client must now be informed by Attorney X of the expert's conflict situation
  • committee: Remains unaware of conflict affecting its chair's impartiality in a matter involving a subcommittee member
  • engineer_b: Remains unaware that their committee chair is an adversary in their current litigation

Learning Moment: Disclosure to a retaining attorney is a necessary but potentially insufficient response to a conflict of interest; engineers must assess whether the scope of their disclosure matches the scope of the conflict's impact — a conflict affecting a public standards body may require disclosure beyond the immediate legal engagement

Ethical Implications: Reveals that disclosure is a process with multiple potential recipients, not a single act; highlights the difference between satisfying one's own ethical obligations and actually eliminating the conflict's harmful potential; raises questions about the adequacy of self-disclosure versus third-party oversight in managing expert witness conflicts

Discussion Prompts:
  • Is disclosure to Attorney X sufficient to satisfy Engineer A's ethical obligations, or does the committee role create disclosure obligations to additional parties such as the committee, the court, or Engineer B?
  • After disclosing to Attorney X, what factors should Engineer A consider in deciding whether to continue the engagement?
  • Does Attorney X now have an independent obligation to disclose the conflict to the court, and how does that interact with attorney-client privilege?
Tension: medium Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/129#Event_Conflict_Disclosure_Record_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is disclosure to Attorney X sufficient to satisfy Engineer A\u0027s ethical obligations, or does the committee role create disclosure obligations to additional parties such as the committee, the court, or Engineer B?",
    "After disclosing to Attorney X, what factors should Engineer A consider in deciding whether to continue the engagement?",
    "Does Attorney X now have an independent obligation to disclose the conflict to the court, and how does that interact with attorney-client privilege?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely feels partial relief at having disclosed but residual anxiety about whether disclosure is sufficient; Attorney X may feel concern about case complications or confidence that the issue is now managed; the disclosure creates a moment of professional accountability",
  "proeth-scenario:ethicalImplications": "Reveals that disclosure is a process with multiple potential recipients, not a single act; highlights the difference between satisfying one\u0027s own ethical obligations and actually eliminating the conflict\u0027s harmful potential; raises questions about the adequacy of self-disclosure versus third-party oversight in managing expert witness conflicts",
  "proeth-scenario:learningMoment": "Disclosure to a retaining attorney is a necessary but potentially insufficient response to a conflict of interest; engineers must assess whether the scope of their disclosure matches the scope of the conflict\u0027s impact \u2014 a conflict affecting a public standards body may require disclosure beyond the immediate legal engagement",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "Now has actual knowledge of conflict and bears responsibility for advising client and potentially the court",
    "boiler_manufacturer_defendant": "Client must now be informed by Attorney X of the expert\u0027s conflict situation",
    "committee": "Remains unaware of conflict affecting its chair\u0027s impartiality in a matter involving a subcommittee member",
    "engineer_a": "Partial satisfaction of disclosure obligations; continuing exposure if broader disclosure is required",
    "engineer_b": "Remains unaware that their committee chair is an adversary in their current litigation"
  },
  "proeth:activatesConstraint": [
    "Attorney_Informed_Consent_Requirement",
    "Broader_Disclosure_Adequacy_Constraint",
    "Continuing_Disclosure_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/129#Action_Engineer_A_Discloses_Committee_Role_to_Attorney_X",
  "proeth:causesStateChange": "Attorney X now bears shared responsibility for managing the disclosed conflict; Engineer A\u0027s initial disclosure obligation is satisfied but broader obligations remain active; the engagement continues under a disclosed-conflict condition rather than an undisclosed-conflict condition",
  "proeth:createsObligation": [
    "Assess_Whether_Disclosure_To_Attorney_X_Alone_Is_Sufficient",
    "Consider_Disclosure_To_Court_Or_Tribunal",
    "Consider_Disclosure_To_Committee_Governance",
    "Monitor_For_Additional_Conflicts_Throughout_Engagement",
    "Document_Disclosure_For_Professional_Record"
  ],
  "proeth:description": "When Engineer A discloses their committee chair role to Attorney X, a formal record of the conflict is created, which automatically shifts the ethical and legal responsibility landscape \u2014 Attorney X now has constructive knowledge of the conflict and Engineer A has satisfied an initial disclosure obligation.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Present case \u2014 following Engineer A\u0027s discovery of Engineer B\u0027s role",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Conflict Disclosure Record Established"
}
Causal Chains (8)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: John Doe's simultaneous service as county engineer, planning board member, and private consultant creates a conflict

Necessary Factors (NESS):
  • Doe's active role as county engineer
  • Doe's active role as planning board member
  • Doe's decision to accept private consulting work on subdivision plans subject to county review
Sufficient Factors:
  • Combination of public authority roles + private financial interest in the same matter being reviewed
Counterfactual Test: Had Doe declined the private consulting engagement or recused himself from one of his public roles, the triple conflict would not have materialized
Responsibility Attribution:

Agent: John Doe
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Doe Prepares Private Subdivision Plans
    Doe accepts private consulting engagement and prepares subdivision plans while holding dual public roles
  2. Dual Public Role Activation
    The same plans Doe prepared privately are submitted for official county review, activating both his county engineer and planning board roles
  3. Doe Triple Role Conflict Emerges
    Doe's three simultaneous capacities — private preparer, official recommender, and voting approver — converge on the same matter
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_0145f6b3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "John Doe\u0027s simultaneous service as county engineer, planning board member, and private consultant creates a conflict",
  "proeth:causalSequence": [
    {
      "proeth:description": "Doe accepts private consulting engagement and prepares subdivision plans while holding dual public roles",
      "proeth:element": "Doe Prepares Private Subdivision Plans",
      "proeth:step": 1
    },
    {
      "proeth:description": "The same plans Doe prepared privately are submitted for official county review, activating both his county engineer and planning board roles",
      "proeth:element": "Dual Public Role Activation",
      "proeth:step": 2
    },
    {
      "proeth:description": "Doe\u0027s three simultaneous capacities \u2014 private preparer, official recommender, and voting approver \u2014 converge on the same matter",
      "proeth:element": "Doe Triple Role Conflict Emerges",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Doe Prepares Private Subdivision Plans",
  "proeth:counterfactual": "Had Doe declined the private consulting engagement or recused himself from one of his public roles, the triple conflict would not have materialized",
  "proeth:effect": "Doe Triple Role Conflict Emerges",
  "proeth:necessaryFactors": [
    "Doe\u0027s active role as county engineer",
    "Doe\u0027s active role as planning board member",
    "Doe\u0027s decision to accept private consulting work on subdivision plans subject to county review"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Combination of public authority roles + private financial interest in the same matter being reviewed"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Doe's private subdivision plans receive official approval through a process in which Doe himself participated as recommender

Necessary Factors (NESS):
  • Doe's formal recommendation in his capacity as county engineer
  • Doe's vote in his capacity as planning board member
  • Absence of recusal or disclosure to other board members
Sufficient Factors:
  • Doe's recommendation + Doe's vote + lack of independent scrutiny of the conflict = approval tainted by undisclosed self-interest
Counterfactual Test: Had Doe recused himself from both the recommendation and the vote, the plans would have been evaluated by disinterested parties, and the approval process would not have been compromised
Responsibility Attribution:

Agent: John Doe
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Doe Prepares Private Subdivision Plans
    Doe creates plans privately, establishing a financial interest in their approval
  2. Doe Recommends His Own Plans
    Doe uses his county engineer authority to formally recommend approval of his own plans
  3. Doe Votes to Approve Own Plans
    Doe uses his planning board vote to further advance approval of the same plans
  4. Plans Approved Under Conflict
    Official approval is granted through a process corrupted by Doe's undisclosed self-interest at every decision point
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_5e907ace",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Doe\u0027s private subdivision plans receive official approval through a process in which Doe himself participated as recommender",
  "proeth:causalSequence": [
    {
      "proeth:description": "Doe creates plans privately, establishing a financial interest in their approval",
      "proeth:element": "Doe Prepares Private Subdivision Plans",
      "proeth:step": 1
    },
    {
      "proeth:description": "Doe uses his county engineer authority to formally recommend approval of his own plans",
      "proeth:element": "Doe Recommends His Own Plans",
      "proeth:step": 2
    },
    {
      "proeth:description": "Doe uses his planning board vote to further advance approval of the same plans",
      "proeth:element": "Doe Votes to Approve Own Plans",
      "proeth:step": 3
    },
    {
      "proeth:description": "Official approval is granted through a process corrupted by Doe\u0027s undisclosed self-interest at every decision point",
      "proeth:element": "Plans Approved Under Conflict",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Doe Recommends His Own Plans",
  "proeth:counterfactual": "Had Doe recused himself from both the recommendation and the vote, the plans would have been evaluated by disinterested parties, and the approval process would not have been compromised",
  "proeth:effect": "Plans Approved Under Conflict",
  "proeth:necessaryFactors": [
    "Doe\u0027s formal recommendation in his capacity as county engineer",
    "Doe\u0027s vote in his capacity as planning board member",
    "Absence of recusal or disclosure to other board members"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Doe\u0027s recommendation + Doe\u0027s vote + lack of independent scrutiny of the conflict = approval tainted by undisclosed self-interest"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Doe's private subdivision plans receive official approval through a process in which Doe himself participated as voting board member

Necessary Factors (NESS):
  • Doe's casting of an affirmative vote as planning board member
  • Doe's undisclosed financial interest in the outcome
  • Absence of recusal mechanism or ethics challenge before the vote
Sufficient Factors:
  • Doe's vote as a board member, combined with his prior recommendation as county engineer, provided the decisive institutional weight needed to secure approval
Counterfactual Test: Without Doe's vote, the board's deliberation would have proceeded without the conflict-tainted input; approval might still have occurred but through an untainted process
Responsibility Attribution:

Agent: John Doe
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Doe Triple Role Conflict Emerges
    Conflict is structurally present but undisclosed as plans enter the approval pipeline
  2. Doe Recommends His Own Plans
    Doe's official recommendation lends institutional credibility to plans he privately prepared
  3. Doe Votes to Approve Own Plans
    Doe's board vote provides the final procedural act completing the tainted approval
  4. Plans Approved Under Conflict
    Approval is recorded as official county action despite being driven by a single conflicted actor at every stage
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_55a5b8ab",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Doe\u0027s private subdivision plans receive official approval through a process in which Doe himself participated as voting board member",
  "proeth:causalSequence": [
    {
      "proeth:description": "Conflict is structurally present but undisclosed as plans enter the approval pipeline",
      "proeth:element": "Doe Triple Role Conflict Emerges",
      "proeth:step": 1
    },
    {
      "proeth:description": "Doe\u0027s official recommendation lends institutional credibility to plans he privately prepared",
      "proeth:element": "Doe Recommends His Own Plans",
      "proeth:step": 2
    },
    {
      "proeth:description": "Doe\u0027s board vote provides the final procedural act completing the tainted approval",
      "proeth:element": "Doe Votes to Approve Own Plans",
      "proeth:step": 3
    },
    {
      "proeth:description": "Approval is recorded as official county action despite being driven by a single conflicted actor at every stage",
      "proeth:element": "Plans Approved Under Conflict",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Doe Votes to Approve Own Plans",
  "proeth:counterfactual": "Without Doe\u0027s vote, the board\u0027s deliberation would have proceeded without the conflict-tainted input; approval might still have occurred but through an untainted process",
  "proeth:effect": "Plans Approved Under Conflict",
  "proeth:necessaryFactors": [
    "Doe\u0027s casting of an affirmative vote as planning board member",
    "Doe\u0027s undisclosed financial interest in the outcome",
    "Absence of recusal mechanism or ethics challenge before the vote"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Doe\u0027s vote as a board member, combined with his prior recommendation as county engineer, provided the decisive institutional weight needed to secure approval"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: When the state DOT traffic engineer is approached about part-time consulting for a former firm, the potential for conflict is identified

Necessary Factors (NESS):
  • Engineer A's current employment as a state DOT traffic engineer with regulatory authority
  • The consulting offer coming from a firm whose work intersects with DOT regulatory decisions
  • Engineer A's decision to accept rather than decline the offer
Sufficient Factors:
  • Active DOT regulatory role + acceptance of consulting engagement from regulated-sector firm = sufficient to create conflict potential requiring disclosure and authorization
Counterfactual Test: Had Engineer A declined the offer or had the offer come from a firm with no nexus to DOT-regulated activities, the conflict potential would not have arisen
Responsibility Attribution:

Agent: Engineer A (BER 02-8)
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. DOT Engineer Accepts Part-Time Consulting Offer
    Engineer A accepts consulting engagement while holding active DOT regulatory position
  2. Overlap Between Consulting Scope and DOT Authority Recognized
    The subject matter of the consulting work is identified as intersecting with Engineer A's DOT responsibilities
  3. Municipal Conflict Potential Identified
    The structural conflict between private consulting income and public regulatory duty is formally recognized
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_b2232a76",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "When the state DOT traffic engineer is approached about part-time consulting for a former firm, the potential for conflict is identified",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A accepts consulting engagement while holding active DOT regulatory position",
      "proeth:element": "DOT Engineer Accepts Part-Time Consulting Offer",
      "proeth:step": 1
    },
    {
      "proeth:description": "The subject matter of the consulting work is identified as intersecting with Engineer A\u0027s DOT responsibilities",
      "proeth:element": "Overlap Between Consulting Scope and DOT Authority Recognized",
      "proeth:step": 2
    },
    {
      "proeth:description": "The structural conflict between private consulting income and public regulatory duty is formally recognized",
      "proeth:element": "Municipal Conflict Potential Identified",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "DOT Engineer Accepts Part-Time Consulting Offer",
  "proeth:counterfactual": "Had Engineer A declined the offer or had the offer come from a firm with no nexus to DOT-regulated activities, the conflict potential would not have arisen",
  "proeth:effect": "Municipal Conflict Potential Identified",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s current employment as a state DOT traffic engineer with regulatory authority",
    "The consulting offer coming from a firm whose work intersects with DOT regulatory decisions",
    "Engineer A\u0027s decision to accept rather than decline the offer"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (BER 02-8)",
  "proeth:sufficientFactors": [
    "Active DOT regulatory role + acceptance of consulting engagement from regulated-sector firm = sufficient to create conflict potential requiring disclosure and authorization"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: When the DOE engineer uses DOE-branded presentation materials while testifying as a private consultant, a misperception of DOE affiliation is created

Necessary Factors (NESS):
  • Engineer A's use of presentation materials bearing official DOE job title and affiliation
  • Engineer A's actual role in the testimony being that of a private consultant, not a DOE representative
  • Audience's reasonable reliance on the branding as indicative of official DOE endorsement
Sufficient Factors:
  • DOE-branded materials + private consulting context + no explicit disclaimer = sufficient to create misleading impression of institutional backing
Counterfactual Test: Had Engineer A used neutral presentation materials or explicitly stated that the views were personal and not DOE's, the misperception would not have been created
Responsibility Attribution:

Agent: Engineer A (BER 07-12)
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. DOE Engineer Testifies Without Full Disclosure
    Engineer A testifies as private consultant for coal bed methane companies without disclosing the dual role to the audience
  2. DOE Engineer Uses DOE-Branded Presentation
    Engineer A deploys presentation materials displaying DOE job title and affiliation during private testimony
  3. DOE Affiliation Misperception Created
    Audience reasonably but incorrectly infers that Engineer A's testimony carries official DOE institutional endorsement
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_9f4e1cd8",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "When the DOE engineer uses DOE-branded presentation materials while testifying as a private consultant, a misperception of DOE affiliation is created",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A testifies as private consultant for coal bed methane companies without disclosing the dual role to the audience",
      "proeth:element": "DOE Engineer Testifies Without Full Disclosure",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A deploys presentation materials displaying DOE job title and affiliation during private testimony",
      "proeth:element": "DOE Engineer Uses DOE-Branded Presentation",
      "proeth:step": 2
    },
    {
      "proeth:description": "Audience reasonably but incorrectly infers that Engineer A\u0027s testimony carries official DOE institutional endorsement",
      "proeth:element": "DOE Affiliation Misperception Created",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "DOE Engineer Uses DOE-Branded Presentation",
  "proeth:counterfactual": "Had Engineer A used neutral presentation materials or explicitly stated that the views were personal and not DOE\u0027s, the misperception would not have been created",
  "proeth:effect": "DOE Affiliation Misperception Created",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s use of presentation materials bearing official DOE job title and affiliation",
    "Engineer A\u0027s actual role in the testimony being that of a private consultant, not a DOE representative",
    "Audience\u0027s reasonable reliance on the branding as indicative of official DOE endorsement"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (BER 07-12)",
  "proeth:sufficientFactors": [
    "DOE-branded materials + private consulting context + no explicit disclaimer = sufficient to create misleading impression of institutional backing"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A discovers that Engineer B serves on a subcommittee chaired by Engineer A, triggering the obligation to disclose the committee chair role to Attorney X

Necessary Factors (NESS):
  • Engineer A's pre-existing role as chairman of the relevant committee
  • Engineer B's membership on Engineer A's subcommittee
  • Engineer A's acceptance of the forensic expert engagement placing them in adversarial relationship with Engineer B
Sufficient Factors:
  • Discovery of Engineer B's subcommittee membership + Engineer A's chair role + active litigation adversarial relationship = sufficient to trigger mandatory disclosure obligation
Counterfactual Test: Had Engineer B not been a member of Engineer A's subcommittee, no committee-based conflict would exist and no disclosure on this ground would be required
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Engineer A Accepts Forensic Expert Engagement
    Engineer A agrees to serve as forensic expert for Attorney X in boiler litigation where Engineer B is opposing expert
  2. Engineer B Subcommittee Membership Discovered
    Engineer A learns that Engineer B serves on a subcommittee that Engineer A chairs, creating a supervisory/collegial conflict
  3. Conflict Disclosure Obligation Activated
    The discovery triggers Engineer A's professional ethics obligation to disclose the relationship to Attorney X
  4. Engineer A Discloses Committee Role to Attorney X
    Engineer A makes full disclosure of the committee chair relationship to Attorney X, creating a formal record
  5. Conflict Disclosure Record Established
    A documented record of the conflict and its disclosure is established, enabling Attorney X to make an informed decision about Engineer A's continued engagement
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_dcc8707f",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A discovers that Engineer B serves on a subcommittee chaired by Engineer A, triggering the obligation to disclose the committee chair role to Attorney X",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A agrees to serve as forensic expert for Attorney X in boiler litigation where Engineer B is opposing expert",
      "proeth:element": "Engineer A Accepts Forensic Expert Engagement",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A learns that Engineer B serves on a subcommittee that Engineer A chairs, creating a supervisory/collegial conflict",
      "proeth:element": "Engineer B Subcommittee Membership Discovered",
      "proeth:step": 2
    },
    {
      "proeth:description": "The discovery triggers Engineer A\u0027s professional ethics obligation to disclose the relationship to Attorney X",
      "proeth:element": "Conflict Disclosure Obligation Activated",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A makes full disclosure of the committee chair relationship to Attorney X, creating a formal record",
      "proeth:element": "Engineer A Discloses Committee Role to Attorney X",
      "proeth:step": 4
    },
    {
      "proeth:description": "A documented record of the conflict and its disclosure is established, enabling Attorney X to make an informed decision about Engineer A\u0027s continued engagement",
      "proeth:element": "Conflict Disclosure Record Established",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Subcommittee Membership Discovered",
  "proeth:counterfactual": "Had Engineer B not been a member of Engineer A\u0027s subcommittee, no committee-based conflict would exist and no disclosure on this ground would be required",
  "proeth:effect": "Engineer A Discloses Committee Role to Attorney X",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s pre-existing role as chairman of the relevant committee",
    "Engineer B\u0027s membership on Engineer A\u0027s subcommittee",
    "Engineer A\u0027s acceptance of the forensic expert engagement placing them in adversarial relationship with Engineer B"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Discovery of Engineer B\u0027s subcommittee membership + Engineer A\u0027s chair role + active litigation adversarial relationship = sufficient to trigger mandatory disclosure obligation"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A must choose to refrain from engaging in any written or verbal communications with Engineer B regarding the litigation matter

Necessary Factors (NESS):
  • Engineer A's acceptance of the forensic expert role placing them in formal adversarial position
  • Engineer B's role as opposing expert witness for the plaintiff
  • The existence of active litigation creating ex parte communication prohibitions
Sufficient Factors:
  • Active litigation + adversarial expert roles on opposing sides + committee relationship creating informal communication channels = sufficient to require explicit avoidance of ex parte contact
Counterfactual Test: Had Engineer A not accepted the forensic engagement, no litigation-based ex parte communication prohibition would apply to their interactions with Engineer B
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Engineer A Accepts Forensic Expert Engagement
    Engineer A enters the litigation as Attorney X's forensic expert, establishing adversarial posture
  2. Engineer B Subcommittee Membership Discovered
    Engineer A learns Engineer B is both the opposing expert and a member of Engineer A's own subcommittee
  3. Dual Relationship Risk Recognized
    The committee relationship is identified as a channel through which improper ex parte litigation communications could inadvertently occur
  4. Engineer A Avoids Ex Parte Litigation Communications with Engineer B
    Engineer A actively refrains from any litigation-related communications with Engineer B outside proper legal channels
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_d766d513",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A must choose to refrain from engaging in any written or verbal communications with Engineer B regarding the litigation matter",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A enters the litigation as Attorney X\u0027s forensic expert, establishing adversarial posture",
      "proeth:element": "Engineer A Accepts Forensic Expert Engagement",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A learns Engineer B is both the opposing expert and a member of Engineer A\u0027s own subcommittee",
      "proeth:element": "Engineer B Subcommittee Membership Discovered",
      "proeth:step": 2
    },
    {
      "proeth:description": "The committee relationship is identified as a channel through which improper ex parte litigation communications could inadvertently occur",
      "proeth:element": "Dual Relationship Risk Recognized",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A actively refrains from any litigation-related communications with Engineer B outside proper legal channels",
      "proeth:element": "Engineer A Avoids Ex Parte Litigation Communications with Engineer B",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Engineer A Accepts Forensic Expert Engagement",
  "proeth:counterfactual": "Had Engineer A not accepted the forensic engagement, no litigation-based ex parte communication prohibition would apply to their interactions with Engineer B",
  "proeth:effect": "Engineer A Avoids Ex Parte Litigation Communications with Engineer B",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s acceptance of the forensic expert role placing them in formal adversarial position",
    "Engineer B\u0027s role as opposing expert witness for the plaintiff",
    "The existence of active litigation creating ex parte communication prohibitions"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Active litigation + adversarial expert roles on opposing sides + committee relationship creating informal communication channels = sufficient to require explicit avoidance of ex parte contact"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: When Engineer A discloses their committee chair role to Attorney X, a formal record of the conflict is established

Necessary Factors (NESS):
  • Engineer A's act of making the disclosure to Attorney X
  • The disclosure being sufficiently complete to document the nature and scope of the committee relationship
  • Attorney X receiving and acknowledging the disclosure
Sufficient Factors:
  • Complete disclosure of committee chair role + Attorney X's receipt = sufficient to establish a formal conflict record enabling informed client decision-making
Counterfactual Test: Without Engineer A's disclosure, no formal conflict record would exist; Attorney X would proceed without knowledge of the relationship, and the conflict would remain hidden and unmanaged
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Engineer B Subcommittee Membership Discovered
    Engineer A identifies the conflict-creating relationship between their committee role and Engineer B's opposing expert status
  2. Engineer A Discloses Committee Role to Attorney X
    Engineer A makes full, formal disclosure of the committee chair relationship to Attorney X
  3. Conflict Disclosure Record Established
    A documented record exists enabling Attorney X to make an informed decision and protecting Engineer A's professional standing
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/129#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/129#CausalChain_c95a0ab4",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "When Engineer A discloses their committee chair role to Attorney X, a formal record of the conflict is established",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A identifies the conflict-creating relationship between their committee role and Engineer B\u0027s opposing expert status",
      "proeth:element": "Engineer B Subcommittee Membership Discovered",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A makes full, formal disclosure of the committee chair relationship to Attorney X",
      "proeth:element": "Engineer A Discloses Committee Role to Attorney X",
      "proeth:step": 2
    },
    {
      "proeth:description": "A documented record exists enabling Attorney X to make an informed decision and protecting Engineer A\u0027s professional standing",
      "proeth:element": "Conflict Disclosure Record Established",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Engineer A Discloses Committee Role to Attorney X",
  "proeth:counterfactual": "Without Engineer A\u0027s disclosure, no formal conflict record would exist; Attorney X would proceed without knowledge of the relationship, and the conflict would remain hidden and unmanaged",
  "proeth:effect": "Conflict Disclosure Record Established",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s act of making the disclosure to Attorney X",
    "The disclosure being sufficiently complete to document the nature and scope of the committee relationship",
    "Attorney X receiving and acknowledging the disclosure"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Complete disclosure of committee chair role + Attorney X\u0027s receipt = sufficient to establish a formal conflict record enabling informed client decision-making"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (13)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
BER Case 67-1 before
Entity1 is before Entity2
BER Case 02-8 time:before
http://www.w3.org/2006/time#before
Thirty-five years later in BER Case No. 02-8 — placing 67-1 (1967) strictly before 02-8 (2002)
BER Case 02-8 before
Entity1 is before Entity2
BER Case 07-12 time:before
http://www.w3.org/2006/time#before
More recently, in BER Case 07-12 — placing 02-8 (2002) strictly before 07-12 (2007)
BER Case 67-1 before
Entity1 is before Entity2
BER Case 07-12 time:before
http://www.w3.org/2006/time#before
Timeline summary places 1967 case first, 2007 case described as 'more recently' relative to both ear... [more]
BER Case 07-12 before
Entity1 is before Entity2
present case (Engineer A / Attorney X) time:before
http://www.w3.org/2006/time#before
The discussion transitions from BER Case 07-12 with 'Turning to the facts in the present case,' indi... [more]
Doe's preparation of subdivision plans (as private consultant) before
Entity1 is before Entity2
Doe's recommendation of approval (as county engineer) time:before
http://www.w3.org/2006/time#before
Doe prepared the plans for a subdivision development in his capacity as a consulting engineer; then,... [more]
Doe's recommendation of approval (as county engineer) before
Entity1 is before Entity2
Doe's vote to approve (as planning board member) time:before
http://www.w3.org/2006/time#before
As a member of the county planning board, he later voted to approve those plans
Engineer A's prior consulting work (airport design) before
Entity1 is before Entity2
Engineer A's employment with State DOT time:before
http://www.w3.org/2006/time#before
Prior to Engineer A's employment with the State DOT's traffic engineering division, Engineer A perfo... [more]
Engineer A's employment with State DOT overlaps
Entity1 starts before Entity2 and ends during Entity2
Engineer A's proposed part-time consulting for former firm time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Engineer A was approached by his former consulting engineering firm to serve on a part-time basis...... [more]
Engineer A (BER 07-12) serving on State X Environmental Quality Council overlaps
Entity1 starts before Entity2 and ends during Entity2
Engineer A (BER 07-12) testifying for coal bed methane company time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Engineer A served on the State X Environmental Quality Council...Engineer A was retained to testify ... [more]
Engineer A (BER 07-12) testifying at hearing before
Entity1 is before Entity2
newspaper article reporting on hearing time:before
http://www.w3.org/2006/time#before
Later, a newspaper article on the hearing reported that a 'US DOE researcher' testified at the heari... [more]
Engineer A chairing boiler code standards and safety committee overlaps
Entity1 starts before Entity2 and ends during Entity2
Engineer A serving as forensic expert for Attorney X time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Engineer A, who chairs a boiler code standards and safety committee...has been requested by Attorney... [more]
Engineer B serving on subcommittee chaired by Engineer A overlaps
Entity1 starts before Entity2 and ends during Entity2
Engineer B serving as plaintiff's forensic expert time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Engineer A learns that the forensic engineering expert for the plaintiff, Engineer B, is a member of... [more]
Engineer A's disclosure to Attorney X before
Entity1 is before Entity2
Engineer A's engagement as expert witness time:before
http://www.w3.org/2006/time#before
Engineer A has an obligation to (1) fully disclose to Attorney X his role as the chairman of the boi... [more]
About Allen Relations & OWL-Time

Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.

Each relation includes both a ProEthica custom property and a time:* OWL-Time property for maximum compatibility.