{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Action_Accepting_Dual_Public_Roles",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the planning board appointment entirely, retaining only the county engineer role and private practice.",
    "Resign from private consulting upon accepting dual public roles, eliminating the financial conflict.",
    "Accept all roles but establish a written recusal policy committing to abstain from any matter involving his private clients."
  ],
  "proeth-scenario:characterMotivation": "Doe likely sought to maximize personal income and professional influence by leveraging multiple simultaneous roles, believing he could compartmentalize his duties or that his competence justified the arrangement. He may also have rationalized that holding all three roles made him uniquely effective at coordinating county development matters.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the planning board seat would have eliminated the voting conflict entirely; Doe would retain public influence through the county engineer role without the appearance of self-dealing, and no ethics violation would arise from role structure alone.",
    "Resigning from private consulting would have removed the financial interest that corrupts both his official recommendation and his vote; he could serve both public roles with undivided loyalty to the public interest.",
    "A proactive recusal policy, if rigorously followed, could have mitigated but not fully eliminated structural tension; however, it would have demonstrated good faith and prevented Actions 3 and 4, likely avoiding a formal ethics violation \u2014 though the dual public role itself might still warrant scrutiny."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how structural conflicts of interest \u2014 not just individual acts of misconduct \u2014 are themselves ethical violations. Students learn that accepting incompatible roles is a foundational ethical failure, not merely a procedural oversight, and that the Code of Ethics demands proactive avoidance of conflict-of-interest conditions before they materialize.",
  "proeth-scenario:ethicalTension": "Public servant impartiality vs. personal financial ambition; the engineer\u0027s duty to serve the public interest vs. the individual\u0027s right to pursue a private livelihood; loyalty to multiple principals (county, planning board, private clients) whose interests are structurally incompatible.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public trust in governmental impartiality, integrity of the county planning process, fairness to competing developers, Doe\u0027s professional license and reputation, and the broader credibility of the engineering profession.",
  "proeth:description": "Doe chose to simultaneously hold the positions of county engineer and county planning board member while also maintaining a private consulting practice, creating the structural conditions for all subsequent conflicts of interest.",
  "proeth:foreseenUnintendedEffects": [
    "Structural conflict of interest between private financial interests and public duties",
    "Divided loyalties across three distinct professional roles",
    "Exposure to ethical violations whenever private consulting work intersected with public responsibilities"
  ],
  "proeth:fulfillsObligation": [
    "Fulfillment of professional employment obligations to county government",
    "Fulfillment of professional obligations to private consulting clients"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflict of interest",
    "Undivided loyalty to employer and client",
    "Public trust in governmental engineering roles",
    "Impartiality in public service decision-making"
  ],
  "proeth:hasAgent": "John Doe (County Engineer / Planning Board Member / Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private financial interest and professional ambition vs. public duty and impartiality",
    "proeth:resolutionReasoning": "Doe implicitly prioritized personal financial and professional interests by maintaining all three roles without apparent recusal policies or structural separation, contrary to the absolute prohibition of Section 8(b)"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maintain multiple income streams and professional roles simultaneously, leveraging public positions alongside private consulting work",
  "proeth:requiresCapability": [
    "Understanding of professional ethics obligations",
    "Knowledge of conflict-of-interest rules governing public servants",
    "Judgment to recognize structural incompatibility of roles"
  ],
  "proeth:temporalMarker": "Prior to and concurrent with all subsequent actions; background condition established before Step 1",
  "proeth:violatesObligation": [
    "Section 8: Duty to endeavor to avoid conflicts of interest with employer or client",
    "Section 8(b): Absolute prohibition on participating in considerations or actions regarding services provided in private practice while serving in public capacity",
    "Axiomatic professional duty not to take actions that divide loyalties between employer/client and personal interests (per Case No. 60-5)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accepting Dual Public Roles"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Action_Preparing_Private_Consulting_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the private consulting engagement on the grounds that the subdivision would require approval from bodies on which he serves.",
    "Accept the engagement but immediately disclose the conflict to the county and planning board, and request reassignment of the approval review to independent officials.",
    "Refer the prospective client to another qualified consulting engineer, avoiding the conflict entirely while still serving the client\u0027s needs."
  ],
  "proeth-scenario:characterMotivation": "Doe sought private consulting fees and professional engagement, likely viewing the subdivision project as a routine business opportunity. He may have rationalized that his technical preparation of the plans was a separate, purely private act insulated from his public roles, or that his expertise made him the most qualified person for the work.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the engagement would have prevented any financial stake from forming, keeping Doe\u0027s subsequent official acts free from self-interest; the client would seek another engineer, and the approval process would proceed without taint.",
    "Disclosure and reassignment would have demonstrated ethical transparency and could have preserved the integrity of the approval process, though it would require institutional willingness to appoint a neutral reviewer \u2014 a procedurally sound and ethically defensible path.",
    "Referring the client to a colleague would have served the public interest, preserved the client relationship professionally, and protected Doe\u0027s integrity across all three roles, representing the cleanest resolution at this stage."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that the conflict of interest is created at the moment a public official acquires a private financial stake in a matter subject to their official authority \u2014 not merely when they act on it. Students learn that the preparation of the plans, not just the vote, is ethically compromised because it initiates a chain of self-dealing.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s right to earn a livelihood through private practice vs. the obligation to avoid situations where private financial interests conflict with public duties; technical competence and professional service vs. the corrupting effect of self-interest on subsequent official judgment.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Financial integrity of the planning approval process, equal treatment of all developers seeking county approval, the objectivity of Doe\u0027s future official acts, and the public\u0027s right to unbiased governmental review of development proposals.",
  "proeth:description": "Doe, acting in his capacity as a private consulting engineer, prepared the engineering plans for a subdivision development, thereby creating a direct personal and financial interest in the approval of those plans by the very governmental body on which he served.",
  "proeth:foreseenUnintendedEffects": [
    "Creation of a personal financial stake in the governmental approval of those plans",
    "Placement of himself in a position where his public duties as county engineer and planning board member would directly intersect with his private financial interest",
    "Foreseeable requirement that he, in his public roles, would need to evaluate and act upon his own privately prepared work"
  ],
  "proeth:fulfillsObligation": [
    "Contractual obligation to private consulting client to prepare competent engineering plans"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflict of interest",
    "Separation of private financial interests from public regulatory duties",
    "Public trust in governmental engineering oversight",
    "Impartiality in public service"
  ],
  "proeth:hasAgent": "John Doe (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private consulting financial interest and client loyalty vs. public duty of impartiality as county engineer and planning board member",
    "proeth:resolutionReasoning": "Doe prioritized private financial and client interests over his public duties, in direct violation of the absolute prohibition of Section 8(b), which admits no exceptions even with full disclosure for engineers in public service"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill private consulting contract obligations, earn consulting fees, and produce approvable subdivision development plans for his private client",
  "proeth:requiresCapability": [
    "Subdivision development engineering and plan preparation",
    "Knowledge of applicable engineering standards and local planning requirements",
    "Professional judgment to recognize conflict-of-interest implications of accepting the engagement"
  ],
  "proeth:temporalMarker": "Step 1 \u2014 first in the sequence of events; prior to any recommendation or vote",
  "proeth:violatesObligation": [
    "Section 8: Duty to endeavor to avoid conflicts of interest with employer (county government) or client",
    "Section 8(b): Prohibition on providing private engineering services that will foreseeably require participation in governmental consideration or action in one\u0027s public capacity",
    "Axiomatic duty not to divide loyalties between private client and public employer (per Case No. 60-5)",
    "Duty of loyalty and impartiality owed to county government as county engineer",
    "Duty of impartiality owed to the public as planning board member"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Preparing Private Consulting Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Action_Recommending_Own_Plans_Officially",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Recuse himself from making any official recommendation on the plans, formally disclosing his private consulting relationship to the planning board and county.",
    "Withdraw the consulting engagement retroactively and return fees received, then make the official recommendation from a position of restored impartiality.",
    "Submit the plans for independent technical review by a neutral third-party engineer before issuing any county engineer recommendation."
  ],
  "proeth-scenario:characterMotivation": "Doe used his official county engineer authority to advance the approval of plans from which he stood to benefit financially, likely motivated by the desire to secure project completion and consulting fees. He may have rationalized that his technical assessment was genuinely favorable and that his recommendation reflected honest professional judgment, blurring the line between legitimate expertise and self-interested advocacy.",
  "proeth-scenario:consequencesIfAlternative": [
    "Formal recusal with disclosure would have protected the integrity of the county engineer\u0027s office, informed the planning board of the conflict, and allowed an independent recommendation to be made \u2014 likely the minimum ethically required action at this stage.",
    "Withdrawing from the consulting engagement would have been extraordinary but would have demonstrated a commitment to public duty over private gain; however, the prior financial relationship would still require disclosure to fully cleanse the process.",
    "Commissioning independent review would have added procedural integrity and public accountability, though it would not by itself resolve the conflict of interest inherent in Doe issuing the final recommendation \u2014 disclosure and recusal would still be necessary."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the concept of using public office for private gain \u2014 a core violation in engineering ethics and public service ethics alike. Students learn that even if the plans were technically sound, the recommendation is ethically void because it cannot be distinguished from self-interested advocacy, and that the integrity of public processes depends on the absence of financial conflicts, not merely the absence of provably biased outcomes.",
  "proeth-scenario:ethicalTension": "The obligation to provide honest, expert technical recommendations in the public interest vs. the corrupting influence of personal financial gain; the duty of a public official to serve the county impartially vs. the temptation to leverage official authority for private benefit; the appearance of impropriety vs. a subjective belief in one\u0027s own objectivity.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The credibility and independence of the county engineer\u0027s office, the reliability of official technical recommendations as a public resource, potential harm to the county if substandard plans are rubber-stamped through self-interest, and Doe\u0027s exposure to professional discipline and legal liability.",
  "proeth:description": "Doe, acting in his official capacity as county engineer, formally recommended approval of the subdivision development plans he had personally prepared as a private consulting engineer, thereby using his public authority to advance his own private financial interests.",
  "proeth:foreseenUnintendedEffects": [
    "Use of public authority to benefit private consulting client and personal financial interest",
    "Undermining of the objectivity and impartiality expected of the county engineer role",
    "Progression of the conflict of interest to a second, more direct stage of ethical violation",
    "Placement of the planning board in a position of receiving a recommendation from a conflicted official"
  ],
  "proeth:fulfillsObligation": [
    "Procedural obligation of county engineer to submit plans with recommendation to planning board (fulfilled in form but not in substance due to conflict)"
  ],
  "proeth:guidedByPrinciple": [
    "Impartiality in public service",
    "Separation of private financial interest from public regulatory authority",
    "Objectivity in professional engineering recommendations",
    "Public trust and accountability in governmental roles"
  ],
  "proeth:hasAgent": "John Doe (County Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Official procedural duty to recommend plans vs. ethical obligation to recuse from conflicted matters",
    "proeth:resolutionReasoning": "Doe chose to exercise his official recommendation authority despite the direct conflict, prioritizing procedural role fulfillment and private interest advancement over the absolute ethical prohibition; the discussion notes this action alone constitutes a violation of Section 8(b) independent of the subsequent vote"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill official county engineer duty to submit and recommend plans to the planning board, while simultaneously advancing the approval of plans in which he had a private financial interest",
  "proeth:requiresCapability": [
    "Engineering review and evaluation of subdivision development plans",
    "Official recommendation authority as county engineer",
    "Knowledge of ethical obligations requiring recusal in conflicted matters"
  ],
  "proeth:temporalMarker": "Step 2 \u2014 after preparing plans in private capacity; prior to planning board vote",
  "proeth:violatesObligation": [
    "Section 8(b): Explicit prohibition on participating in considerations or actions with respect to services provided by the engineer in private engineering practice while serving in public capacity",
    "Section 8: Duty to avoid conflicts of interest with public employer",
    "Duty of impartiality and objectivity in official county engineer recommendations",
    "Axiomatic duty not to divide loyalties between private financial interests and public employer obligations (per Case No. 60-5)",
    "Public trust reposed in the county engineer to provide unbiased professional recommendations"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Recommending Own Plans Officially"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Action_Voting_to_Approve_Own_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Recuse himself from the vote, publicly disclosing his dual role as the plans\u0027 author and the recommending county engineer, and abstain from the planning board decision entirely.",
    "Resign from the planning board before the vote, acknowledging that the accumulation of roles had created an untenable conflict of interest.",
    "Move to table the approval vote and request that the full conflict of interest be reviewed by the county ethics board or legal counsel before any vote proceeds."
  ],
  "proeth-scenario:characterMotivation": "Doe cast the deciding or contributing vote to approve plans he had created and recommended, completing the self-interested cycle and securing the outcome from which he financially benefited. His motivation was the realization of the consulting fees and professional success tied to project approval. He may have continued to rationalize that his vote reflected genuine merit-based judgment, or he may have felt that having already compromised in earlier steps, withdrawal at this point was futile or too costly.",
  "proeth-scenario:consequencesIfAlternative": [
    "Recusal and public disclosure at the vote stage would have been the minimum ethically required action; it would have preserved the planning board\u0027s integrity for this decision, created a public record of the conflict, and likely triggered a broader review of Doe\u0027s prior actions \u2014 a painful but professionally responsible outcome.",
    "Resignation from the planning board, while disruptive, would have been a strong signal of ethical accountability and would have removed the most direct conflict; it would not have retroactively cured the earlier violations but would have prevented the final and most egregious one.",
    "Tabling the vote for ethics review would have introduced institutional accountability into the process, potentially protecting the county from a tainted approval, and would have demonstrated that Doe prioritized process integrity over personal outcome \u2014 though it would also have invited scrutiny of all his prior actions in the matter."
  ],
  "proeth-scenario:decisionSignificance": "Represents the culmination and most visible manifestation of the conflict of interest, making it the strongest teaching moment about the complete cycle of self-dealing. Students learn that each role \u2014 consultant, recommending official, voting member \u2014 represents a distinct ethical obligation, and that violating all three simultaneously constitutes a comprehensive breach of the Code of Ethics. It also teaches that prior ethical failures do not justify further ones, and that recusal remains available and required at every stage.",
  "proeth-scenario:ethicalTension": "The democratic and fiduciary duty of a planning board member to vote in the public interest vs. the overwhelming private financial interest in approval; the principle that no person should be a judge in their own cause vs. the practical temptation to complete what was already set in motion; the compounding effect of prior ethical failures making correction feel increasingly difficult.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The entire legitimacy of the subdivision approval, public confidence in county governance, the rights of citizens and competing developers to an impartial process, Doe\u0027s professional license and standing with NSPE, potential legal consequences for the county, and the precedent set for future conflicts of interest in local government engineering.",
  "proeth:description": "Doe, acting in his capacity as a county planning board member, cast a vote to approve the subdivision development plans he had personally prepared as a consulting engineer and had officially recommended in his capacity as county engineer, completing a full cycle of self-interested decision-making across all three of his roles.",
  "proeth:foreseenUnintendedEffects": [
    "Completion of a full conflict-of-interest cycle in which Doe created, recommended, and approved his own work across three distinct roles",
    "Direct use of public voting authority to benefit private financial interests",
    "Corruption of the planning board\u0027s impartial decision-making process",
    "Undermining of public confidence in county planning and engineering oversight"
  ],
  "proeth:fulfillsObligation": [
    "Procedural obligation to participate in planning board votes (fulfilled in form but fundamentally corrupted by conflict of interest)"
  ],
  "proeth:guidedByPrinciple": [
    "Impartiality in public service decision-making",
    "Absolute separation of private financial interest from public voting authority",
    "Public trust and accountability in governmental bodies",
    "Non-participation in matters where personal interest exists"
  ],
  "proeth:hasAgent": "John Doe (Planning Board Member)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private financial interest and client obligation vs. absolute public duty of impartiality as planning board member under Section 8(b)",
    "proeth:resolutionReasoning": "Doe chose to vote, prioritizing private financial interest and procedural role fulfillment over the absolute ethical prohibition; this action represents the culmination and most direct violation in the conflict-of-interest cycle, as it involved the direct exercise of public voting power to approve his own privately prepared work, with no available ethical justification under the Code"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Exercise planning board voting authority to approve the subdivision development plans, thereby securing the approval his private consulting client required and completing his official board duties",
  "proeth:requiresCapability": [
    "Planning board deliberation and voting authority",
    "Engineering judgment to evaluate subdivision development plans",
    "Knowledge of ethical obligations requiring recusal when voting on matters involving personal financial interest"
  ],
  "proeth:temporalMarker": "Step 3 \u2014 final action in the sequence; after preparing plans and recommending them officially",
  "proeth:violatesObligation": [
    "Section 8(b): Explicit and absolute prohibition on participating in considerations or actions with respect to services provided by the engineer in private practice while serving on a governmental body",
    "Section 8: Duty to avoid conflicts of interest with public employer",
    "Section 8(a): Duty to inform employer or client of business connections influencing judgment (though the discussion notes disclosure does not excuse the Section 8(b) violation)",
    "Duty of impartiality as a planning board member to the public",
    "Axiomatic duty not to divide loyalties between private interests and public employer (per Case No. 60-5)",
    "Public trust reposed in planning board members to vote without personal financial stake in outcomes"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Voting to Approve Own Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Event_Prior_Ethics_Cases_Decided",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why does it matter that NSPE had already decided similar cases before John Doe\u0027s conduct? Does prior precedent change the moral or professional weight of his actions?",
    "How should a practicing engineer stay informed about evolving ethics rulings and code changes?",
    "What does the existence of multiple prior cases on the same issue tell us about systemic pressures that push engineers toward dual-role conflicts?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral for most parties at this stage; retrospectively significant \u2014 students and practitioners may feel reassured that the profession has grappled with these issues before, or unsettled that the same problems recur.",
  "proeth-scenario:ethicalImplications": "Reveals that professional ethics operates as a living normative system with institutional memory; raises questions about whether engineers have a duty of ongoing ethical education and whether the profession adequately disseminates its own rulings.",
  "proeth-scenario:learningMoment": "Illustrates that engineering ethics is not static \u2014 it evolves through case adjudication and code revision. Students should understand that prior rulings create constructive notice and that ignorance of established precedent is not a defense.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineering_profession": "Normative baseline created; engineers on notice that dual-role conflicts are recognized ethical violations",
    "john_doe": "Indirectly placed on constructive notice that his type of conduct has been scrutinized and condemned in prior cases",
    "nspe": "Institutional credibility established through consistent adjudication of conflict-of-interest cases",
    "public": "Marginally protected by existence of precedent discouraging dual-role conflicts"
  },
  "proeth:activatesConstraint": [
    "Historical_Precedent_Reference_Constraint"
  ],
  "proeth:causesStateChange": "A body of precedent on dual-role conflicts is established under the old Canons, creating a reference baseline against which future conduct and the new Code will be measured.",
  "proeth:createsObligation": [
    "Obligation_To_Consult_Prior_Rulings",
    "Obligation_To_Recognize_Evolving_Standards"
  ],
  "proeth:description": "NSPE adjudicated related ethics cases (60-5, 62-7, 62-21, 63-5) under the older Canons of Ethics, establishing precedent for conflict-of-interest analysis in dual-role engineering scenarios.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to main events (1960s, before new Code promulgation)",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Prior Ethics Cases Decided"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Event_New_Code_of_Ethics_Promulgated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When a professional code is revised, what obligations does that revision place on practitioners who were already operating under the old standard?",
    "Does the promulgation of a new, clearer Code make John Doe\u0027s subsequent conduct more or less culpable than if he had acted under the older Canons?",
    "Who bears responsibility for ensuring that practicing engineers are aware of and comply with newly promulgated codes?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "For the profession broadly: a sense of progress and clarification. For engineers in dual roles: potential anxiety as standards tighten. For John Doe retrospectively: the new Code renders his subsequent conduct indefensible under a clearer standard.",
  "proeth-scenario:ethicalImplications": "Highlights the tension between the stability of professional norms and the need for evolution; raises questions about retroactive moral judgment and the adequacy of professional self-regulation as a mechanism for protecting the public.",
  "proeth-scenario:learningMoment": "Demonstrates that professional codes evolve in response to real cases and that engineers are responsible for knowing current standards. The gap between old Canons and new Code is not a safe harbor \u2014 it is a zone of heightened responsibility.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineering_profession": "Clearer guidance on conflict of interest; higher accountability expectations",
    "john_doe": "Now subject to a more explicit and demanding ethical framework \u2014 his subsequent conduct occurs with no ambiguity about applicable standards",
    "nspe": "Institutional authority reinforced; updated standards signal responsiveness to real-world conflicts",
    "public": "Stronger professional self-regulation theoretically increases protection of public interest in government engineering decisions"
  },
  "proeth:activatesConstraint": [
    "New_Code_Compliance_Constraint",
    "Conflict_Of_Interest_Prohibition_Constraint",
    "Public_Interest_Primacy_Constraint"
  ],
  "proeth:causesStateChange": "The operative normative framework governing John Doe\u0027s subsequent conduct shifts from the older Canons to the new Code of Ethics; the standards against which his actions will be judged are now more explicit and evolved.",
  "proeth:createsObligation": [
    "Obligation_To_Comply_With_New_Code",
    "Obligation_To_Familiarize_With_Revised_Standards",
    "Obligation_To_Avoid_Conflicts_Of_Interest_Under_New_Framework"
  ],
  "proeth:description": "Following the prior ethics case decisions, NSPE promulgated a new Code of Ethics that superseded the older Canons, establishing a revised and more explicit normative framework governing conflicts of interest and dual-role conduct.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After prior cases decided; before John Doe\u0027s conduct",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "New Code of Ethics Promulgated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Event_Conflict_of_Interest_Materialized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At exactly what point did John Doe\u0027s conflict of interest become irreconcilable, and what should he have done at that moment?",
    "Is it possible to hold multiple public and private roles without conflict, and if so, what structural safeguards would be required?",
    "Who else in this scenario had an obligation to identify and address the conflict \u2014 was John Doe the only responsible party?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "For John Doe: possibly normalized or rationalized, suggesting a troubling desensitization to conflict. For county officials and the public: if aware, a sense of alarm and breach of trust. For the subdivision client: relief that their engineer controls the approval process, raising its own ethical concerns.",
  "proeth-scenario:ethicalImplications": "Exposes the structural corruption that occurs when the same individual occupies creator, evaluator, and approver roles simultaneously; reveals how self-interest can be institutionally laundered through official processes; raises questions about systemic design of public oversight roles.",
  "proeth-scenario:learningMoment": "The conflict of interest is not merely technical \u2014 it structurally corrupts every subsequent official act. Students should understand that the moment of conflict materialization is when the ethical obligation to disclose or recuse becomes mandatory, not optional.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "county_government": "Institutional integrity of planning and engineering review processes undermined",
    "john_doe": "Exposed to professional disciplinary action, reputational damage, and potential legal liability; financial benefit from consulting fee now tainted",
    "nspe": "Case becomes a teaching example of the exact conduct the new Code was designed to prevent",
    "public": "Land use decisions affecting community development made through a conflicted process, potentially prioritizing private interest over public welfare",
    "subdivision_client": "Plans approved through a compromised process \u2014 approval may be legally vulnerable to challenge"
  },
  "proeth:activatesConstraint": [
    "Conflict_Of_Interest_Prohibition_Constraint",
    "Public_Interest_Primacy_Constraint",
    "Duty_To_Disclose_Or_Recuse_Constraint",
    "Impartiality_Of_Public_Role_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/143#Action_Preparing_Private_Consulting_Plans",
  "proeth:causesStateChange": "The situation transitions from a latent structural risk (holding multiple roles) to an active, concrete conflict of interest with direct financial and professional self-interest implications for John Doe across all three of his simultaneous capacities.",
  "proeth:createsObligation": [
    "Obligation_To_Disclose_Conflict_To_Relevant_Authorities",
    "Obligation_To_Recuse_From_Recommendation_And_Vote",
    "Obligation_To_Cease_Private_Consulting_On_Matters_Under_Official_Review",
    "Obligation_To_Protect_Public_Interest_Over_Private_Gain"
  ],
  "proeth:description": "Upon John Doe preparing private consulting plans and then occupying the roles of county engineer and planning board member simultaneously, a concrete, tripartite conflict of interest came into existence \u2014 the same individual stood as creator, official recommender, and approving voter of the same plans.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Upon completion of consulting plan preparation and exercise of official roles",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Conflict of Interest Materialized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Event_Official_Recommendation_Issued",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the institutional weight of an official county engineer recommendation change the ethical gravity of John Doe\u0027s conflict compared to a merely private opinion?",
    "What obligations did the planning board members have to independently verify the basis and independence of the county engineer\u0027s recommendation?",
    "If the conflict were disclosed at this stage but after the recommendation was issued, would that be sufficient to remedy the ethical violation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "For John Doe: possible cognitive dissonance or rationalization (\u0027I know these plans are good\u0027). For planning board members: false confidence in an apparently independent professional recommendation. For the public: unknowing reliance on a compromised institutional process.",
  "proeth-scenario:ethicalImplications": "Illustrates how official roles amplify the harm of conflicts of interest by lending institutional legitimacy to self-interested judgments; reveals the downstream corruption of deliberative processes; raises questions about the integrity of public records and the reliance interests of other decision-makers.",
  "proeth-scenario:learningMoment": "An official recommendation carries institutional authority that amplifies the harm of a conflict of interest \u2014 it does not merely reflect personal bias but actively shapes downstream decisions. Students should understand that official acts by conflicted individuals corrupt the entire decision chain.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "county_government": "Official record contains a tainted recommendation that may expose decisions to legal challenge",
    "john_doe": "Official act now on record that compounds his ethical violation; professional credibility further undermined",
    "planning_board": "Deliberative process corrupted by reliance on a conflicted recommendation without knowledge of the conflict",
    "public": "Land use decision-making process compromised without public awareness or opportunity for objection",
    "subdivision_client": "Approval process advanced through conflicted channels, creating legal vulnerability"
  },
  "proeth:activatesConstraint": [
    "Impartiality_Of_Official_Recommendation_Constraint",
    "Conflict_Of_Interest_Prohibition_Constraint",
    "Public_Record_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/143#Action_Recommending_Own_Plans_Officially",
  "proeth:causesStateChange": "An official county engineering recommendation \u2014 tainted by undisclosed conflict of interest \u2014 now exists in the public record and will foreseeably influence the planning board\u0027s deliberation and vote.",
  "proeth:createsObligation": [
    "Obligation_Of_Planning_Board_To_Scrutinize_Recommendation_Source",
    "Obligation_To_Disclose_Conflict_Before_Board_Relies_On_Recommendation",
    "Obligation_To_Withdraw_Tainted_Recommendation"
  ],
  "proeth:description": "As a direct outcome of John Doe\u0027s act of recommending his own plans in his capacity as county engineer, an official county recommendation in favor of the subdivision plans entered the formal record, carrying the institutional weight of the county engineer\u0027s professional endorsement.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After private consulting plans were prepared; before planning board vote",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Official Recommendation Issued"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Event_Approval_Vote_Recorded",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is John Doe\u0027s conduct at the voting stage more or less culpable than at the plan preparation stage, or are all three acts equally serious? Why?",
    "What remedies \u2014 professional, legal, and institutional \u2014 should be available when an official approval is obtained through this kind of tripartite self-dealing?",
    "How should public bodies be structurally designed to prevent a single individual from occupying creator, recommender, and approver roles for the same matter?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "For John Doe: possible relief that the process is complete, or dawning realization of exposure. For other planning board members: potential retroactive alarm upon learning of the conflict. For the public: a sense of betrayal if the conflict becomes known. For the subdivision client: satisfaction that approval was obtained, potentially unaware of or indifferent to the ethical process failures.",
  "proeth-scenario:ethicalImplications": "Represents the complete corruption of a public decision-making process by private self-interest; reveals how structural role conflicts, when unaddressed, inevitably produce outcomes that subordinate public welfare to private gain; raises fundamental questions about the design of public oversight institutions, the enforceability of professional ethics codes, and the relationship between legal permissibility and ethical obligation.",
  "proeth-scenario:learningMoment": "The completion of the tripartite self-dealing cycle \u2014 creator, recommender, approver \u2014 represents the fullest possible realization of a conflict of interest in a public engineering role. Students should understand that each step compounded the violation and that the final vote crystallized all prior ethical failures into a concrete, harmful outcome.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "county_government": "Official approval potentially void or voidable; legal and reputational risk",
    "john_doe": "Maximum ethical and professional exposure \u2014 all three roles have now been compromised; subject to disciplinary action, potential license revocation, and civil liability",
    "nspe": "Case exemplifies the precise conduct the new Code prohibits; becomes precedent for future enforcement",
    "planning_board": "Institutional legitimacy of the board\u0027s decision compromised; other members may face questions about due diligence",
    "public": "Community development decision made through fully corrupted process; potential for land use harms if plans were not independently sound",
    "subdivision_client": "Approval legally vulnerable; development investment at risk if approval is rescinded or challenged"
  },
  "proeth:activatesConstraint": [
    "Conflict_Of_Interest_Prohibition_Constraint",
    "Public_Interest_Primacy_Constraint",
    "Validity_Of_Official_Decision_Constraint",
    "Duty_To_Correct_Tainted_Approval_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/143#Action_Voting_to_Approve_Own_Plans",
  "proeth:causesStateChange": "The subdivision plans are now officially approved through a fully compromised process. The conflict of interest has produced a concrete governmental outcome \u2014 a land use approval \u2014 that affects third parties and the public, and that may be legally and professionally challengeable.",
  "proeth:createsObligation": [
    "Obligation_To_Report_Conflict_To_NSPE_Or_Licensing_Board",
    "Obligation_To_Seek_Rescission_Of_Tainted_Approval",
    "Obligation_Of_County_To_Review_Decision_Validity",
    "Obligation_To_Disclose_Conflict_To_Affected_Public"
  ],
  "proeth:description": "As a direct outcome of John Doe voting in his planning board capacity, an official vote approving the subdivision plans \u2014 plans he personally created and officially recommended \u2014 was recorded, completing the tripartite self-dealing cycle.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After official recommendation issued; final stage of approval process",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Approval Vote Recorded"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#Event_Ethics_Case_Submitted_to_NSPE",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is professional self-regulation through bodies like NSPE sufficient to deter the kind of conduct John Doe engaged in, or are external legal or governmental mechanisms also necessary?",
    "How should the existence of prior NSPE cases on the same issue affect the severity of any sanction imposed on John Doe?",
    "What changes to professional licensing or public employment law might more effectively prevent the structural conditions that enabled John Doe\u0027s conflict of interest?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "For John Doe: anxiety, defensiveness, and potential regret. For the profession: a moment of collective accountability. For the public: reassurance that self-regulatory mechanisms exist, tempered by concern about whether they are sufficient. For NSPE: institutional responsibility to issue clear, consistent guidance.",
  "proeth-scenario:ethicalImplications": "Highlights the role of professional institutions in constructing and enforcing ethical norms; raises questions about the adequacy of self-regulation; reveals the tension between individual accountability and systemic reform; demonstrates how individual cases shape collective professional standards.",
  "proeth-scenario:learningMoment": "Professional ethics review is not merely punitive \u2014 it is norm-generative. The NSPE\u0027s analysis of this case produces guidance that shapes the conduct of all engineers, not just John Doe. Students should understand that individual cases have systemic normative consequences.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "engineering_profession": "Normative clarification issued; practitioners on notice of consequences for dual-role conflicts",
    "future_engineers": "Case becomes part of the ethics education canon, shaping professional norms for future practitioners",
    "john_doe": "Professional reputation formally at risk; potential disciplinary sanction; conduct now permanently part of professional ethics record",
    "nspe": "Opportunity to reinforce new Code standards and demonstrate institutional responsiveness; precedent-setting responsibility",
    "public": "Institutional accountability mechanism activated, though outcome depends on adequacy of sanctions"
  },
  "proeth:activatesConstraint": [
    "Professional_Disciplinary_Review_Constraint",
    "New_Code_Compliance_Constraint",
    "Precedent_Consistency_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/143#Action_Voting_to_Approve_Own_Plans",
  "proeth:causesStateChange": "John Doe\u0027s conduct transitions from a completed private ethical failure to a matter of formal professional institutional scrutiny, with potential consequences for his license, reputation, and the broader normative guidance issued to the profession.",
  "proeth:createsObligation": [
    "Obligation_Of_NSPE_To_Analyze_Against_New_Code",
    "Obligation_To_Reference_Prior_Cases_60-5_62-7_62-21_63-5",
    "Obligation_To_Issue_Guidance_For_Future_Practitioners"
  ],
  "proeth:description": "The conduct of John Doe became the subject of an NSPE ethics case review, triggering formal analysis of his tripartite role conflict against the new Code of Ethics and prior precedents.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After approval vote recorded; during Discussion/analysis phase",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Ethics Case Submitted to NSPE"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#CausalChain_fb7ffa44",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon John Doe preparing private consulting plans and then occupying the roles of county engineer and county planning board member, a conflict of interest materialized",
  "proeth:causalSequence": [
    {
      "proeth:description": "Doe voluntarily accepts and retains both the county engineer and county planning board member positions concurrently",
      "proeth:element": "Accepting Dual Public Roles (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Doe simultaneously prepares engineering plans for a subdivision in his private consulting capacity, creating a private financial interest",
      "proeth:element": "Preparing Private Consulting Plans (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "The intersection of private financial interest with dual public authority roles produces a structural conflict of interest",
      "proeth:element": "Conflict of Interest Materialized (Event 3)",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Accepting Dual Public Roles (Action 1)",
  "proeth:counterfactual": "Had Doe declined either the county engineer or planning board role, or had he recused himself from matters involving his private clients, the conflict of interest would not have materialized in its full form",
  "proeth:effect": "Conflict of Interest Materialized (Event 3)",
  "proeth:necessaryFactors": [
    "Simultaneous holding of county engineer position",
    "Simultaneous holding of county planning board member position",
    "Existence of private consulting work intersecting with public duties",
    "Absence of recusal or disclosure mechanisms"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Combination of dual public authority roles + private financial interest in subdivision plans = structural conflict of interest",
    "No single role alone would have created the full conflict; overlap of all three roles was sufficient"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#CausalChain_e166172e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Doe, acting in his official capacity as county engineer, formally recommended approval of the subdivision plans that he himself had prepared in his private consulting capacity",
  "proeth:causalSequence": [
    {
      "proeth:description": "Doe holds county engineer position with authority to recommend subdivision plan approvals",
      "proeth:element": "Accepting Dual Public Roles (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Doe authors the subdivision engineering plans in his private capacity, creating a direct personal stake in their approval",
      "proeth:element": "Preparing Private Consulting Plans (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Private authorship and official review authority converge on the same set of plans",
      "proeth:element": "Conflict of Interest Materialized (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Doe uses his county engineer authority to formally recommend approval of his own privately prepared plans",
      "proeth:element": "Recommending Own Plans Officially (Action 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "A formal county engineer recommendation enters the public record, lending official credibility to Doe\u0027s private work",
      "proeth:element": "Official Recommendation Issued (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Preparing Private Consulting Plans (Action 2)",
  "proeth:counterfactual": "Had Doe not prepared the private plans, there would have been no self-recommendation; had he recused himself as county engineer, a different official would have issued the recommendation",
  "proeth:effect": "Recommending Own Plans Officially (Action 3)",
  "proeth:necessaryFactors": [
    "Existence of privately prepared plans requiring official county engineer review",
    "Doe\u0027s occupancy of the county engineer role with authority to issue formal recommendations",
    "Absence of a substitute reviewer or recusal mechanism",
    "Plans reaching the stage of formal county review"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Private authorship of plans + official review authority over those same plans + no recusal = self-recommendation outcome",
    "Any one factor absent (e.g., recusal) would have broken the causal link"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#CausalChain_0bda89a4",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct outcome of John Doe voting in his planning board capacity, an official vote approving the subdivision plans was recorded",
  "proeth:causalSequence": [
    {
      "proeth:description": "Doe holds planning board membership with voting authority over subdivision approvals",
      "proeth:element": "Accepting Dual Public Roles (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Doe authors the subdivision plans privately, creating a financial interest in their approval",
      "proeth:element": "Preparing Private Consulting Plans (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Doe recommends his own plans in his county engineer capacity, compounding the conflict",
      "proeth:element": "Recommending Own Plans Officially (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Doe casts a planning board vote approving the same plans he authored and recommended",
      "proeth:element": "Voting to Approve Own Plans (Action 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "An official planning board approval is recorded, completing a three-role conflict of interest cycle",
      "proeth:element": "Approval Vote Recorded (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Voting to Approve Own Plans (Action 4)",
  "proeth:counterfactual": "Had Doe abstained or recused himself from the planning board vote, his personal influence on the approval outcome would have been eliminated; the vote may still have passed, but without Doe\u0027s ethically compromised participation",
  "proeth:effect": "Approval Vote Recorded (Event 5)",
  "proeth:necessaryFactors": [
    "Doe\u0027s membership on the county planning board with voting authority",
    "The subdivision plans reaching the planning board for a vote",
    "Doe casting his vote rather than abstaining or recusing himself",
    "The vote count being sufficient for approval (Doe\u0027s vote being material to the outcome)"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Planning board member status + vote cast on own plans + no abstention = recorded approval vote attributable to Doe",
    "If Doe\u0027s vote was the deciding vote, his participation alone was sufficient to determine the outcome; even if not decisive, his participation contributed to the sufficient set"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#CausalChain_56709f84",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following the prior ethics case decisions, NSPE promulgated a new Code of Ethics that superseded the older Canons, establishing the normative framework under which Doe\u0027s conduct became the subject of an NSPE ethics case review",
  "proeth:causalSequence": [
    {
      "proeth:description": "NSPE adjudicates related cases under older Canons, establishing precedent and identifying gaps in ethical guidance",
      "proeth:element": "Prior Ethics Cases Decided (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "NSPE issues updated Code of Ethics superseding older Canons, creating binding standards for conflict-of-interest situations",
      "proeth:element": "New Code of Ethics Promulgated (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Doe\u0027s conduct produces a textbook conflict of interest squarely within the new Code\u0027s prohibitions",
      "proeth:element": "Conflict of Interest Materialized (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The full cycle of conflicted conduct is completed and documented in official county records",
      "proeth:element": "Approval Vote Recorded (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Doe\u0027s documented conduct triggers formal NSPE ethics review under the new Code framework",
      "proeth:element": "Ethics Case Submitted to NSPE (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "New Code of Ethics Promulgated (Event 2)",
  "proeth:counterfactual": "Had the new Code of Ethics not been promulgated, or had Doe\u0027s conduct not violated its provisions, the formal ethics case submission would lack a normative foundation; the case might still have been submitted under older canons but would be evaluated under a superseded framework",
  "proeth:effect": "Ethics Case Submitted to NSPE (Event 6)",
  "proeth:necessaryFactors": [
    "Existence of an applicable NSPE Code of Ethics with conflict-of-interest provisions",
    "Doe\u0027s conduct falling within the scope of the Code\u0027s prohibitions",
    "A complainant or reviewing body with standing to submit the case",
    "Prior precedent cases (Event 1) establishing interpretive context"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "John Doe (primary); NSPE (institutional framework)",
  "proeth:sufficientFactors": [
    "Promulgated Code of Ethics + Doe\u0027s documented conflicted conduct + NSPE review jurisdiction = sufficient basis for ethics case submission",
    "Without the Code, Doe\u0027s conduct would lack a formal normative standard against which to be judged"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/143#",
    "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/143#CausalChain_83d6ff2a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The conduct of John Doe became the subject of an NSPE ethics case review, triggering formal analysis of whether his simultaneous private and public roles violated the Code of Ethics",
  "proeth:causalSequence": [
    {
      "proeth:description": "Doe establishes the structural precondition for conflict by holding two public roles with authority over the same subject matter",
      "proeth:element": "Accepting Dual Public Roles (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Doe introduces a private financial interest into matters subject to his own official authority",
      "proeth:element": "Preparing Private Consulting Plans (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "All three roles converge on the same subdivision matter, producing a fully realized conflict of interest",
      "proeth:element": "Conflict of Interest Materialized (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Doe completes the conflicted cycle by both recommending and voting to approve his own plans, creating a documented record of the ethical violation",
      "proeth:element": "Official Recommendation Issued and Approval Vote Recorded (Events 4 \u0026 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The documented pattern of conflicted conduct triggers formal NSPE ethics review under the new Code of Ethics",
      "proeth:element": "Ethics Case Submitted to NSPE (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Conflict of Interest Materialized (Event 3)",
  "proeth:counterfactual": "Had the conflict of interest not materialized \u2014 for example, had Doe recused himself at any stage \u2014 there would be no documented conflicted conduct to submit for ethics review; the case would lack a factual predicate",
  "proeth:effect": "Ethics Case Submitted to NSPE (Event 6)",
  "proeth:necessaryFactors": [
    "Doe\u0027s actual conflicted conduct across three roles",
    "The conflict being of sufficient severity and documentation to warrant formal review",
    "NSPE\u0027s jurisdiction and the new Code\u0027s applicability",
    "A triggering submission by a complainant or reviewing body"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "John Doe",
  "proeth:sufficientFactors": [
    "Materialized conflict of interest + official actions taken under conflict + NSPE Code applicability = sufficient basis for formal ethics case",
    "The combination of all three conflicted actions (private authorship, official recommendation, planning board vote) created an undeniable and documented pattern sufficient to compel review"
  ],
  "proeth:withinAgentControl": true
}