{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Action_Transition_to_State_DOT",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Remain at the consulting firm and decline the DOT offer",
    "Accept the DOT role but negotiate a formal ethics agreement clarifying permissible outside activities before starting",
    "Accept the DOT role in a non-regulatory capacity that avoids direct oversight of private firms"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought career advancement, greater stability, or a sense of public service by transitioning from private consulting to a government role, bringing specialized airport design expertise into a public-sector traffic engineering position. The move likely represented a deliberate pursuit of different professional responsibilities and a public-interest mission.",
  "proeth-scenario:consequencesIfAlternative": [
    "Engineer A retains full freedom to pursue private consulting and airport work but foregoes the public-service opportunity and any associated career benefits; no conflict of interest arises",
    "A pre-negotiated ethics agreement would have created clear boundaries from day one, potentially preventing the later dilemma entirely and modeling best-practice onboarding ethics",
    "A non-regulatory DOT role would reduce but not necessarily eliminate conflict-of-interest exposure, depending on how interconnected DOT divisions are \u2014 it might only delay rather than resolve the tension"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that career transitions between the private and public sectors are not ethically neutral events \u2014 they create new, binding obligations and fundamentally reframe what constitutes a conflict of interest. Students learn that accepting public employment is itself a moral commitment, not merely an employment contract.",
  "proeth-scenario:ethicalTension": "Private-sector professional freedom and entrepreneurial opportunity vs. the heightened fiduciary duties, conflict-of-interest restrictions, and public trust obligations inherent in government employment. The engineer\u0027s accumulated private expertise becomes both an asset and a potential liability in the public role.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The integrity of the public regulatory role is established here; if Engineer A does not fully appreciate the ethical transformation this career shift requires, all subsequent decisions are compromised. Public trust in the DOT\u0027s impartiality is at risk from the outset.",
  "proeth:description": "Engineer A made a deliberate career decision to leave private consulting and accept full-time employment as a traffic engineer with the State DOT traffic engineering division. This transition fundamentally shifted his professional obligations and created a new set of fiduciary duties to a public employer.",
  "proeth:foreseenUnintendedEffects": [
    "Departure from airport design expertise and prior professional relationships",
    "Assumption of public servant obligations and fiduciary duties to the state",
    "Potential future constraints on private consulting activities"
  ],
  "proeth:fulfillsObligation": [
    "Commitment to new employer as faithful agent and trustee (NSPE Code III.6.b)",
    "Acceptance of public service role with attendant ethical responsibilities",
    "Transparent departure from prior private employment"
  ],
  "proeth:guidedByPrinciple": [
    "Faithful agency and trusteeship to employer",
    "Public welfare as primary obligation",
    "Professional integrity in transitioning between roles"
  ],
  "proeth:hasAgent": "Engineer A (Traffic Engineer, State DOT / formerly Airport Designer, Consulting Firm)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private consulting career continuity vs. public sector employment",
    "proeth:resolutionReasoning": "Engineer A resolved in favor of government employment, accepting the associated obligations and constraints on outside professional activities"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure full-time government employment as a traffic engineer, shifting professional focus from airport design to state highway traffic engineering",
  "proeth:requiresCapability": [
    "Traffic engineering knowledge",
    "Contract and plan review skills",
    "Regulatory familiarity with state highway system requirements"
  ],
  "proeth:temporalMarker": "Prior to current employment; pre-DOT period",
  "proeth:withinCompetence": true,
  "rdfs:label": "Transition to State DOT"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Action_Reviewing_Private_Firm_Contracts",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Recuse himself from reviewing plans submitted by his former consulting firm even before any moonlighting arrangement is proposed",
    "Request that DOT establish a formal recusal and ethics screening protocol for all engineers with prior private-sector experience",
    "Continue reviews without any special precautions, relying solely on personal integrity"
  ],
  "proeth-scenario:characterMotivation": "Engineer A performs this duty as a core professional responsibility of his DOT position \u2014 applying technical expertise to protect public safety on the state highway system and ensuring private entities comply with regulatory standards. It reflects both job obligation and professional identity as a traffic engineering specialist.",
  "proeth-scenario:consequencesIfAlternative": [
    "Proactive recusal would demonstrate ethical foresight and protect impartiality, though it might raise questions about Engineer A\u0027s objectivity and require workload redistribution",
    "Institutionalizing an ethics screening protocol would benefit the DOT broadly and signal organizational commitment to conflict-of-interest management, though it requires administrative investment",
    "Relying solely on personal integrity without structural safeguards is widely regarded as insufficient in public ethics frameworks \u2014 it leaves both the engineer and the institution vulnerable to legitimate criticism even if no actual bias occurs"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that regulatory authority over private entities is the epicenter of public-sector conflict-of-interest concerns. Students learn that the power to approve, reject, or condition private firm work is precisely what makes outside employment with those same firms ethically untenable, regardless of the engineer\u0027s subjective good intentions.",
  "proeth-scenario:ethicalTension": "Objective regulatory authority and impartiality vs. the risk that personal relationships with former colleagues at private firms \u2014 or future private employment interests \u2014 could consciously or unconsciously bias technical reviews. The engineer\u0027s insider knowledge of consulting firm practices is simultaneously an asset to quality review and a source of relational conflict.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Public safety on state highways, the integrity of the procurement and review process, equal treatment of all private firms submitting plans, and the DOT\u0027s institutional credibility. Biased reviews \u2014 even unintentional \u2014 could result in unsafe traffic signal installations or give favored firms a competitive advantage.",
  "proeth:description": "As part of his ongoing duties, Engineer A reviews contracts and traffic signal plans, specifications, and estimates submitted by outside entities (developers and municipalities) for traffic signal work on the state highway system. This is a continuous professional duty exercised in his capacity as a public employee with regulatory authority over private entities.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer A holds regulatory authority over municipalities whose airport projects he might simultaneously serve through private consulting",
    "Decisions made in this role could affect the same municipalities he might represent in a private capacity"
  ],
  "proeth:fulfillsObligation": [
    "Faithful agent and trustee to public employer (NSPE Code III.6.b)",
    "Protection of public safety through rigorous plan review",
    "Objective and impartial exercise of regulatory authority"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety and welfare as paramount obligation",
    "Impartiality and objectivity in regulatory review",
    "Avoidance of conflicts of interest in public service"
  ],
  "proeth:hasAgent": "Engineer A (Traffic Engineer, State DOT)",
  "proeth:hasMentalState": "dutiful and deliberate",
  "proeth:intendedOutcome": "Ensure submitted traffic signal plans and contracts meet state standards, protecting public safety and the integrity of the state highway system",
  "proeth:requiresCapability": [
    "Traffic engineering expertise",
    "Plan and specification review",
    "Knowledge of state highway standards and procurement regulations"
  ],
  "proeth:temporalMarker": "Ongoing; throughout current DOT employment",
  "proeth:withinCompetence": true,
  "rdfs:label": "Reviewing Private Firm Contracts"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Action_Accepting_Part-Time_Moonlighting_Approach",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Immediately and unambiguously decline the offer, citing the conflict of interest inherent in his DOT regulatory role",
    "Consult the DOT ethics officer or state ethics board before making any decision, and abide by their formal guidance",
    "Accept the offer conditionally, proposing a formal ethics screen that would exclude him from all DOT decisions touching municipalities or projects related to the consulting firm"
  ],
  "proeth-scenario:characterMotivation": "Engineer A may be motivated by financial gain, loyalty to former colleagues, a desire to maintain expertise in airport design, professional restlessness in a regulatory role, or a genuine belief that the two roles are sufficiently distinct to be compatible. The familiarity and trust built with the former firm makes the offer feel reasonable rather than alarming.",
  "proeth-scenario:consequencesIfAlternative": [
    "Immediate declination is the ethically cleanest outcome \u2014 it preserves public trust, avoids all conflict-of-interest exposure, and models the standard the BER ultimately endorses; the cost is foregone income and possible strain on the former professional relationship",
    "Seeking formal ethics guidance demonstrates good faith and institutional respect; the ethics officer would likely advise declination, but the process itself protects Engineer A from accusations of unilateral self-dealing and creates a documented record",
    "A formal ethics screen might satisfy minimum disclosure requirements but the BER analysis suggests it would be insufficient given the structural interconnection of highway and airport infrastructure \u2014 the conflict is systemic, not merely transactional"
  ],
  "proeth-scenario:decisionSignificance": "This is the central moral decision point of the case. Students learn that entertaining a conflicted arrangement \u2014 rather than declining it immediately \u2014 is itself an ethically significant act. The case illustrates the concept of \u0027the appearance of impropriety\u0027 and why the BER holds that even well-intentioned dual roles can be structurally unacceptable regardless of personal integrity.",
  "proeth-scenario:ethicalTension": "Personal financial interest and professional loyalty to former colleagues vs. undivided loyalty to the public employer and the impartiality required of a regulatory official. Additionally, self-assessment bias \u2014 the tendency to believe one can manage conflicts that objective observers would find disqualifying \u2014 creates tension between subjective confidence and objective ethical standards.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s professional reputation and license, the DOT\u0027s institutional integrity, fair competition among consulting firms seeking municipal contracts, and public confidence in the impartiality of state infrastructure regulation. If the arrangement proceeds and is later discovered, consequences could include termination, ethics violations, and damage to the former firm.",
  "proeth:description": "Engineer A entertains and engages with his former consulting firm\u0027s proposal to work part-time seeking municipal airport contracts while maintaining his full-time DOT position. The very act of seriously considering and not immediately declining this arrangement constitutes a volitional decision point with ethical implications.",
  "proeth:foreseenUnintendedEffects": [
    "Creation of actual or apparent conflict of interest between regulatory authority over municipalities and private consulting for those same municipalities",
    "Potential compromise of impartiality in state highway review duties",
    "Risk of using public resources or position to benefit private consulting activities",
    "Professional liability exposure for State DOT employer"
  ],
  "proeth:fulfillsObligation": [
    "Legitimate professional interest in maintaining and applying prior expertise",
    "Consideration of part-time work that is facially distinct from primary employment domain"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of actual and apparent conflicts of interest",
    "Faithful agency to public employer",
    "Transparency with employer regarding outside activities",
    "Protection of public trust in government engineering functions"
  ],
  "proeth:hasAgent": "Engineer A (Traffic Engineer, State DOT / Prospective Part-Time Consultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Personal professional and financial interest in moonlighting vs. undivided fiduciary duty to public employer",
    "proeth:resolutionReasoning": "BER determines the dual role creates an unacceptable conflict of interest; Engineer A should decline the part-time role, as employer consent alone is insufficient to cure the ethical violation given the infrastructure interdependencies and his regulatory authority over the same municipalities"
  },
  "proeth:hasMentalState": "deliberate and self-interested",
  "proeth:intendedOutcome": "Leverage prior airport design expertise for additional professional engagement and financial benefit while retaining government employment",
  "proeth:requiresCapability": [
    "Airport design and master planning expertise (from prior consulting experience)",
    "Municipal contract solicitation and business development",
    "FAA qualifications-based selection procedure knowledge"
  ],
  "proeth:temporalMarker": "Present; at the time of the case",
  "proeth:violatesObligation": [
    "Faithful agent and trustee obligation to State DOT employer (NSPE Code III.6.b)",
    "Obligation to avoid conflicts of interest (NSPE Code II.4.d)",
    "Obligation to avoid conduct that compromises professional integrity or creates appearance of impropriety (NSPE Code II.4.e)",
    "Obligation to disclose potential conflicts to employer before proceeding"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accepting Part-Time Moonlighting Approach"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Action_Disclosing_Dual_Employment_to_Employers",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose to the DOT ethics officer only and await a formal written determination before disclosing to the consulting firm",
    "Disclose to both employers simultaneously in writing, with a detailed description of all potential conflict scenarios and proposed mitigation measures",
    "Proceed with the arrangement without disclosure, relying on the assumption that both employers would approve if asked"
  ],
  "proeth-scenario:characterMotivation": "If Engineer A proceeds with the dual role, disclosure is motivated by a combination of legal compliance, professional ethics obligations under the NSPE Code, and self-protection \u2014 creating a documented record that both employers were aware of and consented to the arrangement. It may also reflect a genuine desire to act transparently rather than covertly.",
  "proeth-scenario:consequencesIfAlternative": [
    "Disclosing first to the DOT ethics officer is procedurally sound and ensures the public employer\u0027s interests are protected before any private commitment is made; it may result in the DOT prohibiting the arrangement, effectively resolving the dilemma",
    "Simultaneous written disclosure with conflict mapping demonstrates maximum transparency and professional rigor; it creates a strong record but also formally documents the structural conflicts, making it harder for either employer to claim ignorance if problems arise later",
    "Proceeding without disclosure compounds every ethical violation \u2014 it adds deception and breach of fiduciary duty to the underlying conflict, and eliminates any possibility of good-faith defense if the arrangement is later scrutinized"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students the critical distinction between procedural ethics compliance (disclosure and consent) and substantive ethics compliance (actually avoiding conflicts). Students learn that \u0027I told my employer\u0027 is not a complete ethical defense when the underlying arrangement is structurally conflicted. This challenges the common misconception that transparency alone resolves conflicts of interest.",
  "proeth-scenario:ethicalTension": "The duty of transparency and honest dealing with employers vs. the risk that disclosure, while necessary, creates a false sense of ethical resolution \u2014 i.e., that informed consent from employers is sufficient to neutralize a structural conflict of interest. The BER\u0027s analysis reveals that disclosure is a necessary but not sufficient condition: consent does not make an otherwise unacceptable conflict acceptable.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If disclosure is omitted, Engineer A faces compounded ethics violations \u2014 both the conflict itself and the concealment. If disclosure is made but treated as sufficient, both employers may be lulled into accepting an arrangement that still compromises public integrity. The DOT\u0027s regulatory credibility and the consulting firm\u0027s competitive standing remain at risk even with disclosed consent.",
  "proeth:description": "Should Engineer A proceed with the part-time arrangement, he would be obligated to proactively disclose the dual employment to both the State DOT and the consulting firm, and obtain their informed consent before commencing outside work. This disclosure action is a conditional but ethically mandatory step identified by the BER as a minimum threshold requirement derived from Case 97-1 precedent.",
  "proeth:foreseenUnintendedEffects": [
    "State DOT may deny consent, foreclosing the part-time opportunity",
    "Disclosure may trigger formal conflict-of-interest review under state ethics laws",
    "Even with consent, BER finds the ethical violation persists due to infrastructure interdependencies"
  ],
  "proeth:fulfillsObligation": [
    "Transparency and honesty with employer (NSPE Code III.6.b)",
    "Disclosure of potential conflicts of interest (NSPE Code II.4.d)",
    "Good faith compliance with Case 97-1 procedural requirements"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency and full disclosure to employers",
    "Good faith effort to identify and mitigate conflicts",
    "Respect for employer authority to assess and manage conflicts"
  ],
  "proeth:hasAgent": "Engineer A (Traffic Engineer, State DOT / Prospective Part-Time Consultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Transparency obligation vs. risk that disclosure forecloses the private opportunity",
    "proeth:resolutionReasoning": "Disclosure is ethically required regardless of outcome; Engineer A cannot ethically proceed with dual employment without it, and even with disclosure and consent, the BER concludes the arrangement remains ethically impermissible"
  },
  "proeth:hasMentalState": "obligatory and deliberate",
  "proeth:intendedOutcome": "Ensure both employers are fully informed of the dual role, enabling them to assess conflicts and provide or withhold consent, thereby satisfying the minimum transparency requirement for dual employment",
  "proeth:requiresCapability": [
    "Understanding of conflict-of-interest disclosure obligations",
    "Knowledge of applicable NSPE Code provisions and Case 97-1 precedent",
    "Ability to clearly communicate the nature and scope of proposed dual activities"
  ],
  "proeth:temporalMarker": "Conditional future; required prior to commencing any dual employment",
  "proeth:violatesObligation": [
    "Underlying conflict of interest obligation remains violated even after disclosure per BER analysis (NSPE Code II.4.e)",
    "Faithful agent obligation is not fully cured by disclosure alone given the structural conflict"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Disclosing Dual Employment to Employers"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Action_Monitoring_and_Addressing_Emerging_Conflicts",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Establish a formal, documented recusal log reviewed periodically by the DOT ethics officer to provide external accountability for conflict monitoring",
    "Propose that the consulting firm assign him only to airport projects in municipalities with no connection to the state highway system, structurally limiting the overlap",
    "Recognize that the monitoring burden is itself evidence that the arrangement is unworkable, and use the complexity of required safeguards as the basis for withdrawing from the dual role entirely"
  ],
  "proeth-scenario:characterMotivation": "If the dual role proceeds, ongoing monitoring is motivated by the engineer\u0027s professional obligation to uphold public trust, avoid harm, and fulfill the conditions under which employer consent was granted. It reflects an understanding that conflicts of interest are dynamic \u2014 they evolve as project portfolios change \u2014 and cannot be managed through a one-time disclosure alone.",
  "proeth-scenario:consequencesIfAlternative": [
    "A formal recusal log with external review adds structural accountability and reduces reliance on self-assessment alone; it is the strongest mitigation available within the dual-role framework, though it does not eliminate the underlying structural conflict identified by the BER",
    "Geographically or jurisdictionally limiting the consulting scope reduces but cannot eliminate conflict exposure, since highway and airport infrastructure interact at the state planning level regardless of specific municipal boundaries",
    "Recognizing the monitoring burden as diagnostic of an unworkable arrangement and withdrawing is the ethically mature resolution \u2014 it transforms the ongoing monitoring obligation from a burden into a clarifying signal, and aligns with the BER\u0027s ultimate conclusion that the dual role should not proceed"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that conflict-of-interest management is an ongoing process, not a one-time event. Students learn the concept of \u0027rolling recusal\u0027 and the professional duty of affirmative self-governance. The case also demonstrates why the BER ultimately concludes this ongoing burden is unreasonable and structurally unworkable \u2014 the monitoring obligation itself reveals the depth of the conflict.",
  "proeth-scenario:ethicalTension": "The practical difficulty and cognitive burden of continuous self-monitoring vs. the professional obligation to proactively identify and address conflicts as they emerge. There is also tension between the engineer\u0027s natural inclination to believe he can compartmentalize his roles objectively and the structural reality that dual loyalties create unconscious bias that self-monitoring cannot reliably detect.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Ongoing public safety and regulatory integrity on the state highway system; fair competition among firms seeking municipal airport contracts; Engineer A\u0027s professional license and reputation over the long term; and the DOT\u0027s ability to defend its regulatory decisions against challenges based on the engineer\u0027s divided loyalties. Failure to monitor effectively could result in compromised infrastructure decisions affecting public safety.",
  "proeth:description": "If dual employment were to proceed, Engineer A would be obligated to continuously monitor his activities in both roles for emerging conflicts of interest and take affirmative steps to address them, including recusal from state highway decisions that could affect municipalities he simultaneously serves as a private consultant. This is an ongoing volitional obligation identified by the BER as a conditional but mandatory professional duty.",
  "proeth:foreseenUnintendedEffects": [
    "Frequent recusal from state highway decisions could impair Engineer A\u0027s effectiveness as a DOT employee",
    "Difficulty in cleanly separating highway and airport decisions given infrastructure interdependencies",
    "Ongoing monitoring burden may itself constitute an inappropriate use of professional attention paid for by the public employer"
  ],
  "proeth:fulfillsObligation": [
    "Proactive conflict-of-interest management (NSPE Code II.4.d)",
    "Faithful agent obligation through active recusal and disclosure when conflicts arise (NSPE Code III.6.b)",
    "Avoidance of conduct that compromises professional integrity (NSPE Code II.4.e)"
  ],
  "proeth:guidedByPrinciple": [
    "Proactive rather than reactive conflict management",
    "Faithful agency requiring ongoing vigilance, not merely initial disclosure",
    "Protection of public trust in government engineering decisions",
    "Avoidance of appearance of impropriety"
  ],
  "proeth:hasAgent": "Engineer A (Traffic Engineer, State DOT / Part-Time Consultant, if dual employment accepted)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Effective performance of public duties vs. management of recurring private consulting conflicts",
    "proeth:resolutionReasoning": "BER concludes that the structural and recurring nature of the conflicts makes ongoing monitoring an insufficient remedy; the ethical resolution is to decline the dual employment rather than attempt to manage inherently conflicting obligations through continuous vigilance"
  },
  "proeth:hasMentalState": "obligatory and vigilant",
  "proeth:intendedOutcome": "Prevent actual conflicts of interest from materializing into ethical violations by proactively identifying situations where dual roles intersect and taking corrective action such as recusal or disclosure",
  "proeth:requiresCapability": [
    "Sophisticated conflict-of-interest identification and analysis",
    "Knowledge of recusal procedures and government ethics requirements",
    "Ability to maintain strict separation between public regulatory duties and private consulting activities"
  ],
  "proeth:temporalMarker": "Conditional ongoing obligation; throughout any period of dual employment",
  "proeth:violatesObligation": [
    "BER finds the structural conflict cannot be fully managed through monitoring alone; the underlying ethical violation persists",
    "Obligation to avoid placing oneself in a position where conflicts are structurally foreseeable and recurring"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Monitoring and Addressing Emerging Conflicts"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Event_Prior_Airport_Design_Experience_Accumulated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the expertise an engineer gains at one firm \u0027belong\u0027 to that firm in any ethical sense, and how should it be used after departure?",
    "At what point does accumulated specialized knowledge become a source of conflict rather than merely a professional asset?",
    "How should engineers proactively manage the long-term implications of the expertise they develop early in their careers?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral at time of occurrence; retrospectively significant as the source of Engineer A\u0027s marketability to the former firm; may evoke professional pride in Engineer A and strategic interest from the consulting firm",
  "proeth-scenario:ethicalImplications": "Raises questions about the portability of professional knowledge across employment contexts and the obligations engineers carry from prior employers; previews the tension between personal career development and institutional loyalty",
  "proeth-scenario:learningMoment": "Illustrates how professional experience and expertise, while valuable, can create latent conflicts of interest when career paths intersect across sectors. Students should recognize that prior employment relationships carry ongoing ethical weight.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "consulting_firm": "Invests in Engineer A\u0027s development, creating future incentive to re-engage him as a part-time resource",
    "engineer_a": "Gains specialized expertise that increases future employability but also creates future conflict-of-interest exposure",
    "public": "Indirectly benefits from a more experienced engineer entering public service; also indirectly exposed to future conflict risks",
    "state_dot": "Unaware at this stage; will later benefit from Engineer A\u0027s broader infrastructure knowledge but also inherit conflict risks"
  },
  "proeth:activatesConstraint": [
    "Competence_Maintenance_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/144#Action_N_A__exogenous_career_development_event_",
  "proeth:causesStateChange": "Engineer A gains specialized airport design credentials and institutional knowledge of consulting firm practices, creating a latent conflict potential upon future employment transitions",
  "proeth:createsObligation": [
    "Maintain_Confidentiality_Of_Firm_Knowledge",
    "Avoid_Misuse_Of_Prior_Employer_Information"
  ],
  "proeth:description": "Engineer A accumulated specialized airport design expertise during employment at the consulting firm, establishing a professional background that would later create both opportunity and conflict. This experience forms the foundational condition enabling the future dual-role dilemma.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Pre-DOT employment period",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Prior Airport Design Experience Accumulated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Event_DOT_Traffic_Engineer_Role_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What ethical obligations attach automatically when an engineer moves from private consulting to a public regulatory role?",
    "Should Engineer A have proactively disclosed his prior consulting firm relationship to DOT leadership upon starting the role, even before any conflict materialized?",
    "How does the public\u0027s interest in impartial government review differ from a private client\u0027s interest in competent engineering service?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Likely positive for Engineer A (new opportunity, career advancement); neutral to positive for DOT (gaining experienced engineer); potentially noted with strategic interest by former consulting firm",
  "proeth-scenario:ethicalImplications": "Highlights the categorical ethical shift between private and public employment; raises the principle that public roles carry fiduciary duties to the public that constrain personal economic freedom in ways private employment does not",
  "proeth-scenario:learningMoment": "Demonstrates that assuming a public-sector role is not merely a career change but an ethical status change \u2014 new constraints and obligations attach automatically to the role, regardless of the individual\u0027s intentions.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "consulting_firm": "Loses Engineer A as full-time employee but gains a former colleague now positioned within the regulatory body that reviews their contracts",
    "engineer_a": "Gains public-sector authority and stability but accepts heightened ethical constraints on outside employment and financial interests",
    "public": "Gains a public servant responsible for ensuring private firm compliance with state highway standards; public trust is now at stake",
    "state_dot": "Gains a technically competent reviewer with infrastructure breadth; unknowingly acquires latent conflict-of-interest risk tied to Engineer A\u0027s prior employment"
  },
  "proeth:activatesConstraint": [
    "Public_Servant_Impartiality_Constraint",
    "Conflict_Of_Interest_Prohibition",
    "No_Private_Gain_From_Public_Role_Constraint",
    "Confidentiality_Of_Government_Information"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/144#Action_Transition_to_State_DOT",
  "proeth:causesStateChange": "Engineer A transitions from private-sector obligations to public-sector obligations; review authority over private firms (potentially including former employer) is now vested in Engineer A; public trust becomes a primary constraint",
  "proeth:createsObligation": [
    "Impartial_Review_Of_Private_Contracts",
    "Avoid_Preferential_Treatment_Of_Former_Employer",
    "Disclose_Conflicts_To_DOT_Supervisor",
    "Uphold_Public_Trust_In_Government_Role"
  ],
  "proeth:description": "Upon completing the transition to the State DOT, Engineer A\u0027s new professional role as a traffic engineer becomes formally operative, conferring specific public-sector responsibilities including review authority over private firm contracts and traffic signal plans on the state highway system. This role establishment is the outcome of the transition action.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Immediately following Transition to State DOT action",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "DOT Traffic Engineer Role Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Event_Contract_Review_Authority_Activated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should Engineer A be recused from reviewing any contract submitted by his former employer, or only those where he has specific knowledge that could bias his judgment?",
    "How does the existence of regulatory authority over a former employer change the ethical calculus compared to simply working alongside them?",
    "What institutional safeguards should the DOT have in place to manage the recurring conflict potential in Engineer A\u0027s review role?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Potentially uncomfortable for Engineer A when former colleagues\u0027 work appears for review; possible temptation toward either favoritism or overcorrection; anxiety about perceived impartiality among private firms",
  "proeth-scenario:ethicalImplications": "Reveals the structural nature of conflicts of interest in regulatory contexts; demonstrates that impartiality is an ongoing institutional obligation, not merely a personal virtue; raises questions about the adequacy of disclosure alone as a remedy",
  "proeth-scenario:learningMoment": "Shows that conflicts of interest are not single events but structural conditions that recur throughout a professional relationship; engineers in regulatory roles must develop systematic conflict-screening habits, not just react to obvious cases.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "consulting_firm": "Subject to review by a former colleague who has insider knowledge of their practices and standards",
    "engineer_a": "Faces recurring ethical navigation challenges each time former employer or colleagues submit work for review",
    "other_private_firms": "May perceive competitive disadvantage if Engineer A shows favoritism toward former employer, or advantage if he overcorrects",
    "public": "Depends on impartial review for highway safety; undermined if review process is compromised by personal relationships",
    "state_dot": "Institutional integrity at risk if conflict-of-interest protocols are not followed"
  },
  "proeth:activatesConstraint": [
    "Impartiality_In_Government_Review",
    "Recusal_If_Conflict_Detected",
    "No_Preferential_Treatment_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/144#Action_Reviewing_Private_Firm_Contracts",
  "proeth:causesStateChange": "Each contract review cycle creates a recurring potential conflict trigger; the structural proximity of Engineer A\u0027s regulatory authority to his former employer\u0027s business interests becomes an ongoing ethical pressure point",
  "proeth:createsObligation": [
    "Screen_Each_Contract_For_Personal_Conflicts",
    "Recuse_From_Former_Employer_Reviews_If_Required",
    "Maintain_Documented_Impartial_Review_Record"
  ],
  "proeth:description": "As a direct and ongoing consequence of his DOT role, Engineer A regularly exercises governmental review authority over contracts submitted by private engineering firms, including potentially his former employer. This creates a structural condition of regulatory power over parties with whom he has prior professional relationships.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Ongoing throughout DOT employment, beginning after role establishment",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Contract Review Authority Activated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Event_Former_Firm_Re-Engagement_Approach_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer A have an ethical obligation to report the approach to his DOT supervisor even if he intends to decline?",
    "What does the consulting firm\u0027s decision to approach Engineer A reveal about their own ethical posture, and does it matter?",
    "At what point does a business proposition cross the line into an attempt to improperly leverage a government employee\u0027s position?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A may feel flattered by the approach but also immediately apprehensive about ethical implications; consulting firm representatives likely view this as a straightforward business proposition; DOT colleagues and supervisors (if aware) would likely be alarmed",
  "proeth-scenario:ethicalImplications": "Exposes the asymmetry between private business interests and public-sector ethical constraints; raises the question of whether the appearance of impropriety alone \u2014 independent of actual wrongdoing \u2014 constitutes an ethical violation; highlights NSPE Code provisions on conflicts of interest and public trust",
  "proeth-scenario:learningMoment": "Illustrates that ethical dilemmas are often imposed by external actors rather than self-generated; engineers must recognize that the moment of approach \u2014 not just the moment of acceptance \u2014 triggers ethical obligations. The approach itself demands a response grounded in professional ethics codes.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "consulting_firm": "Has initiated a situation that, if mishandled, could expose them to accusations of attempting to improperly leverage a government contact",
    "engineer_a": "Placed in an unwanted ethical dilemma; professional integrity and career security immediately at risk regardless of decision made",
    "municipal_airports": "May unknowingly become the subject of contracts influenced by an engineer with compromised independence",
    "public": "Public interest in impartial government engineering review is directly threatened by the potential for Engineer A to serve dual masters",
    "state_dot": "Institutional integrity potentially compromised by the mere existence of the approach, even if Engineer A declines"
  },
  "proeth:activatesConstraint": [
    "Conflict_Of_Interest_Prohibition",
    "Dual_Employment_Disclosure_Requirement",
    "Public_Trust_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/144#Action_N_A__exogenous_action_by_consulting_firm__precedes",
  "proeth:causesStateChange": "Engineer A\u0027s ethical status shifts from latent conflict risk to active conflict decision point; the dilemma is now concrete and requires resolution; both acceptance and refusal carry ethical weight",
  "proeth:createsObligation": [
    "Evaluate_Conflict_Before_Responding",
    "Consult_DOT_Ethics_Guidelines",
    "Disclose_Approach_To_DOT_Supervisor_If_Accepting",
    "Consider_Refusal_If_Conflict_Unresolvable"
  ],
  "proeth:description": "The consulting firm\u0027s decision to approach Engineer A for part-time work constitutes an exogenous event from Engineer A\u0027s perspective \u2014 an external actor initiating contact that places him in an ethically charged situation he did not seek. The approach itself immediately activates conflict-of-interest considerations regardless of Engineer A\u0027s response.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Current point in time (present moment of the case narrative)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Former Firm Re-Engagement Approach Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Event_Dual_Role_Conflict_Condition_Crystallized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "The BER concludes this conflict is unacceptable even with employer awareness and consent \u2014 what distinguishes an unacceptable conflict from one that can be managed through disclosure?",
    "How does the interconnected nature of highway and airport infrastructure transform what might seem like a manageable dual role into an irresolvable conflict?",
    "If Engineer A\u0027s DOT supervisor explicitly approves the dual role, does that approval eliminate the ethical problem? Why or why not?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A may initially feel the situation is manageable through disclosure; growing unease as the structural nature of the conflict becomes clear; DOT supervisors (if aware) would feel institutional alarm; consulting firm may be indifferent to the ethical severity; public remains unaware but is the most significantly harmed party",
  "proeth-scenario:ethicalImplications": "Reveals the limits of consent and disclosure as ethical remedies; demonstrates that public trust obligations are not waivable by employer consent alone; highlights NSPE Code Section III.4 on conflicts of interest and the principle that engineers must not allow financial interests to compromise professional judgment in public-sector roles",
  "proeth-scenario:learningMoment": "Demonstrates that disclosure alone does not resolve a structural conflict of interest; some conflicts are irresolvable through transparency and require role termination. Students must understand the difference between a manageable conflict (mitigated by disclosure) and an unacceptable conflict (requiring structural remedy).",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "consulting_firm": "Risk of being seen as having improperly leveraged a government contact; contracts obtained during this period potentially subject to challenge",
    "engineer_a": "Professional reputation, license, and employment at risk; potential disciplinary action from state engineering board; personal liability if conflict influences any review decisions",
    "nspe_and_engineering_profession": "Case becomes a precedent-setting example of dual-role conflict in public-private engineering contexts",
    "public": "Government review process integrity undermined; highway and airport infrastructure decisions potentially influenced by private financial interests",
    "state_dot": "Institutional integrity compromised; regulatory decisions potentially tainted; public accountability obligations triggered"
  },
  "proeth:activatesConstraint": [
    "Conflict_Of_Interest_Prohibition",
    "Public_Trust_Protection_Constraint",
    "Appearance_Of_Impropriety_Avoidance_Constraint",
    "Duty_To_Resign_Or_Recuse_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/144#Action_Accepting_Part-Time_Moonlighting_Approach",
  "proeth:causesStateChange": "Engineer A\u0027s professional status shifts from \u0027latent conflict risk\u0027 to \u0027active conflict of interest\u0027; the BER conclusion that this creates an unacceptable conflict means the ethical violation is now in existence, not merely threatened; remediation requires structural change, not disclosure alone",
  "proeth:createsObligation": [
    "Immediately_Disclose_To_Both_Employers",
    "Seek_Ethics_Guidance_From_DOT",
    "Evaluate_Whether_Conflict_Is_Resolvable",
    "Consider_Terminating_One_Role",
    "Recuse_From_All_Reviews_Touching_Former_Firm_Interests"
  ],
  "proeth:description": "Upon Engineer A\u0027s acceptance of the part-time arrangement, a concrete and irresolvable structural conflict of interest comes into existence: Engineer A simultaneously holds regulatory review authority over private engineering firms at the DOT and serves as a paid consultant to one such firm seeking government contracts. This is not merely a risk of conflict but an actual conflict state.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon acceptance of part-time role (outcome of Accepting Part-Time Moonlighting Approach action)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Dual Role Conflict Condition Crystallized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#Event_Infrastructure_Interconnection_Overlap_Recognized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How should an engineer assess whether two professional roles are sufficiently separated to avoid conflict, and what factors should be considered beyond job title?",
    "Does the physical and administrative interconnection of infrastructure systems create ethical obligations that go beyond what the formal job descriptions would suggest?",
    "If Engineer A could demonstrate that he would never personally review any project touching airports, would that be sufficient to resolve the conflict? Why does the BER conclude it would not?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Potentially alarming for Engineer A as he recognizes the conflict is broader than initially appreciated; validating for ethics reviewers who identified the systemic nature; sobering for the consulting firm if they had assumed the roles were separable",
  "proeth-scenario:ethicalImplications": "Demonstrates that conflict-of-interest analysis must be substantive and domain-aware, not merely formal; reveals that the appearance of impropriety can exist even when no specific improper act has occurred; highlights the systemic nature of public trust obligations in infrastructure engineering",
  "proeth-scenario:learningMoment": "Engineers and students must learn to assess conflicts not just at the level of specific tasks but at the level of domain overlap. Two roles may appear distinct in title but be deeply interconnected in practice. Systemic conflict analysis requires asking: \u0027Do these professional domains touch each other in ways that compromise independent judgment?\u0027",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "consulting_firm": "The business rationale for the arrangement is undermined if the conflict cannot be managed",
    "engineer_a": "The scope of required recusal and the impossibility of clean role separation becomes clear; the path to compliance requires choosing one role",
    "engineering_ethics_community": "This finding strengthens the precedent that infrastructure domain overlap must be considered when evaluating dual-role conflicts",
    "public": "The full extent of the public interest risk becomes visible \u2014 not just discrete contract reviews but systemic infrastructure planning integrity",
    "state_dot": "Realizes that the conflict contaminates a broader range of Engineer A\u0027s work than initially apparent"
  },
  "proeth:activatesConstraint": [
    "Infrastructure_Interconnection_Conflict_Constraint",
    "Expanded_Recusal_Scope_Constraint",
    "Conflict_Of_Interest_Prohibition"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/144#Action_Accepting_Part-Time_Moonlighting_Approach__enablin",
  "proeth:causesStateChange": "The ethical analysis shifts from \u0027can this conflict be managed?\u0027 to \u0027this conflict is categorically unacceptable\u0027; the infrastructure interconnection finding closes off the option of compartmentalization as a remedy",
  "proeth:createsObligation": [
    "Acknowledge_That_Disclosure_Is_Insufficient_Remedy",
    "Recognize_Conflict_As_Structural_Not_Incidental",
    "Advise_Engineer_A_To_Terminate_One_Role"
  ],
  "proeth:description": "The discussion section establishes as a factual finding that highway and airport infrastructure are operationally interconnected, meaning Engineer A\u0027s DOT traffic engineering role and his airport consulting work cannot be cleanly separated into non-overlapping domains. This recognition transforms the perceived scope of the conflict from narrow to systemic.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During ethical analysis (Discussion section); operative throughout the dual-role period",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Infrastructure Interconnection Overlap Recognized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#CausalChain_7a26d526",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon completing the transition to the State DOT, Engineer A\u0027s new professional role as a traffic engineer directly activated his governmental review authority over contracts and traffic signal plans submitted by private consulting firms, including his former employer.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A makes deliberate volitional decision to leave private consulting and accept full-time DOT employment",
      "proeth:element": "Transition to State DOT (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A\u0027s new professional identity and institutional role as a state traffic engineer is formally constituted",
      "proeth:element": "DOT Traffic Engineer Role Established (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A begins regularly exercising governmental review authority over contracts submitted by private firms, including his former employer",
      "proeth:element": "Contract Review Authority Activated (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A performs ongoing review duties, creating a structural oversight relationship with his former consulting firm",
      "proeth:element": "Reviewing Private Firm Contracts (Action 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The combination of review authority and former-firm relationship establishes the precondition for irresolvable conflict of interest",
      "proeth:element": "Dual Role Conflict Condition Crystallized (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Transition to State DOT (Action 1)",
  "proeth:counterfactual": "Had Engineer A remained in private consulting or declined the DOT position, no governmental review authority over former firm contracts would have been established, and the structural conflict condition could not have crystallized",
  "proeth:effect": "Contract Review Authority Activated (Event 3)",
  "proeth:necessaryFactors": [
    "Deliberate career decision to leave private consulting",
    "Acceptance of full-time DOT employment",
    "Institutional assignment of contract review duties to Engineer A\u0027s role"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of DOT employment acceptance + role-based authority assignment + ongoing submission of contracts by private firms"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#CausalChain_e2ffb1d2",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A accumulated specialized airport design expertise during employment at the consulting firm, which directly motivated the consulting firm\u0027s decision to approach Engineer A for part-time work, constituting the exogenous triggering event for the dual-role conflict scenario.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A develops specialized expertise in airport design during private consulting tenure",
      "proeth:element": "Prior Airport Design Experience Accumulated (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A moves to DOT, taking specialized knowledge into a regulatory context",
      "proeth:element": "Transition to State DOT (Action 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Highway and airport infrastructure domains are factually interconnected, expanding the scope of potential conflict",
      "proeth:element": "Infrastructure Interconnection Overlap Recognized (Event 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Consulting firm, recognizing Engineer A\u0027s expertise and accessibility, approaches him for part-time airport design work",
      "proeth:element": "Former Firm Re-Engagement Approach Occurs (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A entertains the proposal, triggering the full ethical conflict scenario",
      "proeth:element": "Accepting Part-Time Moonlighting Approach (Action 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Prior Airport Design Experience Accumulated (Event 1)",
  "proeth:counterfactual": "Without the specialized airport design expertise accumulated during prior employment, the consulting firm would have had no particular incentive to approach Engineer A for part-time engagement; the re-engagement approach would not have occurred in this form",
  "proeth:effect": "Former Firm Re-Engagement Approach Occurs (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s possession of specialized airport design expertise",
    "Consulting firm\u0027s operational need for that specific expertise",
    "Engineer A\u0027s accessibility as a former employee known to the firm"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Consulting Firm (shared with Engineer A)",
  "proeth:sufficientFactors": [
    "Combination of specialized expertise + firm need + prior professional relationship + Engineer A\u0027s new DOT position creating regulatory access"
  ],
  "proeth:withinAgentControl": false
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#CausalChain_f7168153",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon Engineer A\u0027s acceptance of the part-time arrangement, a concrete and irresolvable structural conflict of interest crystallizes, as Engineer A simultaneously holds governmental review authority over the very firm for which he is performing compensated private work.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A holds active governmental review authority over private firm contracts including former employer",
      "proeth:element": "Contract Review Authority Activated (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Consulting firm approaches Engineer A with part-time work proposal",
      "proeth:element": "Former Firm Re-Engagement Approach Occurs (Event 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A makes volitional decision to entertain and engage with the proposal rather than declining outright",
      "proeth:element": "Accepting Part-Time Moonlighting Approach (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Acceptance creates simultaneous reviewer-reviewee and employer-employee relationship between Engineer A and the consulting firm",
      "proeth:element": "Dual Role Conflict Condition Crystallized (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Ethical obligation to disclose is triggered, but disclosure alone cannot resolve the structural conflict already crystallized",
      "proeth:element": "Disclosing Dual Employment to Employers (Action 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accepting Part-Time Moonlighting Approach (Action 3)",
  "proeth:counterfactual": "Had Engineer A declined the part-time arrangement, no dual-role conflict would have crystallized; the approach by the firm alone was insufficient to create the conflict without Engineer A\u0027s acceptance",
  "proeth:effect": "Dual Role Conflict Condition Crystallized (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s volitional acceptance of the part-time arrangement",
    "Pre-existing DOT contract review authority over the consulting firm",
    "Absence of effective recusal or institutional separation mechanisms",
    "Infrastructure domain overlap making separation of duties practically impossible"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of active DOT review authority + simultaneous private compensation from reviewed firm + domain overlap = irresolvable structural conflict"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#CausalChain_68268d66",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "If dual employment were to proceed, Engineer A would be obligated to continuously monitor his activities, as the crystallized structural conflict generates an ongoing and dynamic ethical compliance burden that cannot be resolved through a single disclosure but requires perpetual vigilance.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A accepts dual employment, initiating the conflict condition",
      "proeth:element": "Accepting Part-Time Moonlighting Approach (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Structural conflict between reviewer and reviewed roles becomes concrete and ongoing",
      "proeth:element": "Dual Role Conflict Condition Crystallized (Event 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Initial disclosure obligation triggered but insufficient to resolve ongoing conflict",
      "proeth:element": "Disclosing Dual Employment to Employers (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A continues to encounter former firm contracts in DOT review capacity, generating recurring conflict instances",
      "proeth:element": "Reviewing Private Firm Contracts (Action 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A bears perpetual obligation to identify, disclose, and manage each new conflict instance as it arises",
      "proeth:element": "Monitoring and Addressing Emerging Conflicts (Action 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Dual Role Conflict Condition Crystallized (Event 5)",
  "proeth:counterfactual": "Without the crystallized dual-role conflict, no continuous monitoring obligation would arise; the monitoring duty is entirely derivative of and caused by the conflict condition",
  "proeth:effect": "Monitoring and Addressing Emerging Conflicts (Action 5)",
  "proeth:necessaryFactors": [
    "Crystallization of the dual-role conflict condition",
    "Engineer A\u0027s continuation in both roles simultaneously",
    "Ongoing submission of contracts by the consulting firm to DOT for review",
    "Professional ethics code obligations binding on Engineer A"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Crystallized conflict + ongoing dual employment + professional ethics obligations = mandatory continuous monitoring requirement"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/144#",
    "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/144#CausalChain_29bcfd36",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The discussion section establishes as a factual finding that highway and airport infrastructure are interconnected, which directly expands the scope of Engineer A\u0027s conflict of interest beyond a narrow domain, making it effectively impossible to segregate his DOT review duties from his private airport design work and thereby rendering the conflict irresolvable rather than merely manageable.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A develops expertise spanning both airport and highway-adjacent infrastructure",
      "proeth:element": "Prior Airport Design Experience Accumulated (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A\u0027s DOT role covers traffic and highway infrastructure with review authority",
      "proeth:element": "DOT Traffic Engineer Role Established (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Factual finding establishes that the two infrastructure domains are not separable, eliminating the possibility of clean role segregation",
      "proeth:element": "Infrastructure Interconnection Overlap Recognized (Event 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A accepts private work despite known domain overlap, compounding the conflict",
      "proeth:element": "Accepting Part-Time Moonlighting Approach (Action 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Domain interconnection transforms what might have been a manageable conflict into an irresolvable structural one",
      "proeth:element": "Dual Role Conflict Condition Crystallized (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Infrastructure Interconnection Overlap Recognized (Event 6)",
  "proeth:counterfactual": "If highway and airport infrastructure were entirely separate domains with no overlap, Engineer A might have argued for a manageable conflict with appropriate recusal; the infrastructure interconnection forecloses this argument and escalates the conflict to irresolvable status",
  "proeth:effect": "Dual Role Conflict Condition Crystallized (Event 5)",
  "proeth:necessaryFactors": [
    "Factual interconnection between highway and airport infrastructure domains",
    "Engineer A\u0027s DOT role covering highway/traffic infrastructure",
    "Engineer A\u0027s proposed private work covering airport design",
    "Absence of a clean domain boundary enabling effective role separation"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineer A (shared with institutional actors)",
  "proeth:sufficientFactors": [
    "Domain interconnection + dual role acceptance + absence of effective recusal mechanism = irresolvable rather than merely manageable conflict"
  ],
  "proeth:withinAgentControl": false
}