{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Action_Deciding_to_Support_Prior_Stamped_Work",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Fully withdraw from any connection to the stamped work, treating the employment change as a complete severance of all prior professional obligations",
    "Seek formal legal and ethical guidance on the precise boundaries of permissible \u0027support\u0027 before taking any action related to the stamped document",
    "Proactively communicate to the former employer and client that Engineer A remains available to support the technical work, while clearly documenting the boundaries of that support"
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognized a continuing professional obligation to support and stand behind the technical work he personally certified, viewing this duty as independent of \u2014 and not negated by \u2014 the employment change. Engineer A sought to honor the professional commitment embodied in the stamp while simultaneously respecting the boundaries established by the isolation arrangement.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full withdrawal might seem to simplify the conflict but would actually violate Engineer A\u0027s professional obligations to stand behind certified work and could expose the former client to unfair harm in the proceeding.",
    "Seeking formal guidance before acting would be the most prudent approach, ensuring that Engineer A\u0027s \u0027support\u0027 is clearly defined, documented, and defensible \u2014 though it introduces delay and uncertainty.",
    "Proactive communication with the former employer and client would demonstrate transparency and good faith, but risks creating new channels of contact that could complicate the isolation arrangement or be misinterpreted by the State."
  ],
  "proeth-scenario:decisionSignificance": "This action highlights a subtle but important distinction in engineering ethics: the obligation to support one\u0027s certified work is real and enduring, but it must be carefully bounded when that work is embedded in an adversarial legal proceeding where the engineer now has a conflicting affiliation. Students should grapple with how to honor professional certification duties without crossing into prohibited conduct.",
  "proeth-scenario:ethicalTension": "The duty to stand behind certified professional work and support its technical integrity conflicts with the risk that any continued involvement with the stamped document \u2014 even in a supportive, non-adversarial capacity \u2014 could be perceived as, or could inadvertently become, a form of improper participation in an ongoing adversarial proceeding, blurring the lines the isolation arrangement was designed to maintain.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "If Engineer A\u0027s \u0027support\u0027 for the stamped work is interpreted \u2014 or actually functions \u2014 as covert assistance to the former client against the State, it could breach Engineer A\u0027s duties to the new employer. Conversely, if Engineer A abandons the stamped work entirely, the private client\u0027s technical case could be weakened, raising questions about the reliability of certified engineering documents in adversarial proceedings.",
  "proeth:description": "Engineer A determined that he can and should continue to support the technical work he performed and which was included in the stamped report, while simultaneously refraining from actively representing the State\u0027s adversarial interest in the same proceeding. This reflects Engineer A\u0027s view that his professional obligation to stand behind certified work is distinct from prohibited adversarial participation.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer A\u0027s expressed willingness to support prior work could be perceived as continued loyalty to the former private client, creating appearance issues in his current State employment",
    "Any public statement supporting the prior work could be construed as participating in the proceeding, even if not on behalf of the State",
    "The distinction between \u0027supporting prior work\u0027 and \u0027adversarial participation\u0027 may be difficult to maintain in practice during cross-examination or mediation"
  ],
  "proeth:fulfillsObligation": [
    "Professional duty to stand behind stamped and certified engineering work",
    "Obligation not to repudiate technically sound prior work without cause",
    "Duty of honesty and integrity in professional matters"
  ],
  "proeth:guidedByPrinciple": [
    "Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession (NSPE Code)",
    "Professional accountability for stamped and certified documents",
    "Engineer as faithful agent and trustee to former client (NSPE Code Section II.4)",
    "Distinction between advocacy (prohibited) and technical integrity (required)"
  ],
  "proeth:hasAgent": "Engineer A (State Employee, former Private Firm Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Integrity of stamped professional work vs. prohibition on adversarial participation in the same proceeding",
    "proeth:resolutionReasoning": "The discussion concludes that Engineer A should remain silent and isolated, refraining from active participation; \u0027remaining silent\u0027 is characterized as not \u0027representing the client\u0027 but rather honoring obligations through non-participation, suggesting that passive support of prior work is permissible but active participation is not"
  },
  "proeth:hasMentalState": "deliberate and conflicted",
  "proeth:intendedOutcome": "Maintain professional integrity by not abandoning or repudiating technically sound work that bears his professional stamp, while avoiding active participation in the adversarial proceedings on behalf of the State",
  "proeth:requiresCapability": [
    "Technical expertise in water-rights analysis to assess continued validity of prior work",
    "Ethical judgment to distinguish permissible passive support from prohibited adversarial participation",
    "Self-awareness of the boundaries imposed by conflict-of-interest obligations"
  ],
  "proeth:temporalMarker": "Ongoing during steps 3-5 of the court process, after joining the State",
  "proeth:violatesObligation": [
    "Risk of violating the prohibition on participating in a proceeding where specialized knowledge was gained for a former client, if \u0027supporting prior work\u0027 crosses into active participation",
    "Potential tension with the duty to remain fully isolated from the case as required by the discussion\u0027s conclusion"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Deciding to Support Prior Stamped Work"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Action_Refraining_from_Disclosing_Confidential_Informatio",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose confidential technical information to the State, rationalizing that the public interest in water-rights allocation justifies overriding private confidentiality",
    "Seek a formal ethics opinion or legal ruling on whether any of the information Engineer A holds is actually confidential versus general professional knowledge",
    "Voluntarily recuse from all State employment related to water resources until the proceeding concludes, to eliminate any structural pressure to disclose"
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognized and honored a post-employment duty of confidentiality, understanding that the technical processes, strategic information, and business affairs learned while working for the private firm remain protected even after the employment relationship ends \u2014 and that disclosing such information to an adversary in the same proceeding would be a serious ethical and potentially legal violation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Disclosing confidential information \u2014 even with a public-interest rationalization \u2014 would constitute a serious violation of the NSPE Code of Ethics, expose Engineer A to license revocation and civil liability, and set a dangerous precedent undermining the confidentiality protections that make client-engineer relationships viable.",
    "Seeking a formal ruling on the boundaries of confidentiality would be a responsible and defensible approach, helping Engineer A distinguish between protected client-specific information and general engineering knowledge that can legitimately inform new work \u2014 though it requires time and may not resolve all ambiguities.",
    "Voluntary recusal from all water-resources work would provide the strongest ethical protection but could be professionally and financially damaging to Engineer A and might be seen as an overreaction if the isolation arrangement is genuinely effective."
  ],
  "proeth-scenario:decisionSignificance": "Post-employment confidentiality obligations are a critical and often underappreciated aspect of engineering ethics. Students should understand that confidentiality duties do not expire at the end of employment, and that accepting a position with an adversary in an ongoing proceeding creates a structural temptation to misuse protected information that must be actively and consciously resisted.",
  "proeth-scenario:ethicalTension": "Engineer A\u0027s duty of loyalty and confidentiality to the former employer and client conflicts with the implicit expectation \u2014 and possibly explicit pressure \u2014 from the new employer (the State) to contribute all relevant knowledge and expertise to the State\u0027s case. The engineer is caught between two competing loyalties, with confidential knowledge as the contested resource.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Disclosure of confidential information could irreparably harm the former client\u0027s legal and technical position in the water-rights proceeding, expose Engineer A to professional discipline and potential legal liability, undermine public trust in the engineering profession\u0027s handling of sensitive information, and taint the State\u0027s case if it were later revealed to have been built on improperly obtained confidential knowledge.",
  "proeth:description": "Engineer A decided not to disclose confidential technical processes or business affairs of the former private employer and client to the State, despite his new employment with the State as an objector in the same proceeding. This ongoing decision reflects Engineer A\u0027s recognition of his post-employment confidentiality obligations.",
  "proeth:foreseenUnintendedEffects": [
    "Limits the State\u0027s ability to benefit from Engineer A\u0027s insider knowledge of the opposing party\u0027s technical approach",
    "May create tension with Engineer A\u0027s duty of loyalty to his current employer, the State",
    "Demonstrates professional integrity but may be perceived as a limitation on Engineer A\u0027s usefulness to the State"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code obligation not to disclose confidential information concerning business affairs or technical processes of a former employer or client without consent",
    "Duty to protect the intellectual property and strategic interests of the former private firm and its client",
    "Obligation to maintain the integrity of the court process by not enabling improper use of insider knowledge"
  ],
  "proeth:guidedByPrinciple": [
    "Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer (NSPE Code)",
    "Integrity and honesty in professional dealings",
    "Protection of public trust in engineering as a profession"
  ],
  "proeth:hasAgent": "Engineer A (State Employee, former Private Firm Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Duty to current employer (State) vs. ongoing confidentiality obligations to former employer and client",
    "proeth:resolutionReasoning": "NSPE Code is unambiguous; confidentiality obligations to former clients persist after employment ends and take precedence over the new employer\u0027s interest in leveraging insider knowledge; this is reinforced by the discussion\u0027s conclusion that Engineer A cannot participate or represent the State\u0027s interest without former client and employer consent"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Honor post-employment confidentiality obligations to the former private firm and its client by ensuring that proprietary technical processes, business strategies, and case-specific information learned during prior employment are not shared with the State as adversary",
  "proeth:requiresCapability": [
    "Judgment to identify what information is confidential vs. publicly available",
    "Ethical discipline to refrain from sharing information that could benefit current employer",
    "Knowledge of NSPE Code confidentiality provisions and their post-employment applicability"
  ],
  "proeth:temporalMarker": "Ongoing from the moment of joining the State through the duration of the court proceedings",
  "proeth:withinCompetence": true,
  "rdfs:label": "Refraining from Disclosing Confidential Information"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Action_Stamping_Final_Analysis_Document",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline to co-stamp and request that only the lead engineer certify the document",
    "Delay stamping until fully satisfied with every aspect of the analysis, even if it slows the proceeding",
    "Stamp the document with a qualifying notation disclosing limited scope of personal review"
  ],
  "proeth-scenario:characterMotivation": "Engineer A was fulfilling a professional and contractual obligation to certify completed technical work, affirming personal accountability for the accuracy and integrity of the water-rights analysis on behalf of the private firm\u0027s client.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining to co-stamp might have reduced Engineer A\u0027s formal ethical entanglement with the client\u0027s case, but could have raised questions about the completeness of the certification and Engineer A\u0027s professional contribution to the work.",
    "Delaying stamping would have upheld rigorous professional standards but could have created contractual and timeline conflicts with the firm and client, potentially damaging professional relationships.",
    "A qualifying notation might have clarified the scope of Engineer A\u0027s responsibility but could be seen as an irregular or non-standard practice, potentially undermining the document\u0027s legal standing in the court proceeding."
  ],
  "proeth-scenario:decisionSignificance": "A professional stamp is not merely a procedural formality; it is a durable ethical commitment that survives employment changes and can create ongoing obligations and conflicts in multi-year proceedings. Students should understand that certification decisions carry long-term consequences beyond the immediate project context.",
  "proeth-scenario:ethicalTension": "The act of stamping creates a lasting professional bond to the work and the client it serves, even after employment ends \u2014 pitting the engineer\u0027s enduring duty to stand behind certified work against future employment flexibility and the possibility of later adversarial realignment.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The integrity of the water-rights analysis, the private client\u0027s legal and technical standing in an ongoing court proceeding, Engineer A\u0027s professional reputation, and the foundational trust in licensed engineering certification are all placed at risk. If the stamped work is later challenged or undermined by Engineer A\u0027s own actions, the legitimacy of the entire proceeding could be questioned.",
  "proeth:description": "Engineer A and a colleague affixed their professional stamps to the final water-rights analysis document, formally certifying the work completed through step 2 of the court process. This act constituted an explicit assumption of professional responsibility for the accuracy and integrity of the analysis.",
  "proeth:foreseenUnintendedEffects": [
    "Creates an ongoing professional obligation to stand behind the stamped work through subsequent court proceedings",
    "Establishes a permanent record of Engineer A\u0027s professional involvement in this specific proceeding"
  ],
  "proeth:fulfillsObligation": [
    "Professional responsibility to certify only work personally reviewed and approved",
    "Duty to provide technically competent engineering support for the client\u0027s application",
    "Obligation to act as faithful agent and trustee to the private firm\u0027s client"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence and integrity in certification",
    "Engineer as faithful agent and trustee (NSPE Code Section II.4)",
    "Public safety and accuracy in documents entering the court record"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Engineer, Private Firm)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Formally certify the completed water-rights analysis as professionally sound and legally defensible, enabling the client to advance the court process",
  "proeth:requiresCapability": [
    "Water-rights analysis expertise",
    "Quantification of water resources",
    "Knowledge of terms and conditions for future water use",
    "Professional licensure in relevant jurisdiction"
  ],
  "proeth:temporalMarker": "After completing step 2 (engineering support), prior to resignation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Stamping Final Analysis Document"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Action_Resigning_from_Private_Firm",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the State position specifically because of the active conflict with the ongoing water-rights case",
    "Accept the State position but immediately and proactively disclose the conflict to both the former employer and the State before starting work",
    "Negotiate a delayed start date with the State until the water-rights proceeding concludes or reaches a stage where the conflict is resolved"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought career advancement or a change in professional direction by accepting a position with the State, likely motivated by personal, financial, or professional growth considerations, without necessarily anticipating \u2014 or perhaps while underestimating \u2014 the severity of the conflict of interest that would arise from the State\u0027s active role as an objector in the very proceeding Engineer A had just supported.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the position would have fully eliminated the conflict of interest but at significant personal career cost, and may have been an overly cautious response if robust isolation procedures were available.",
    "Proactive disclosure before starting work \u2014 rather than after \u2014 would have demonstrated exemplary ethical conduct, allowed all parties to negotiate informed consent arrangements early, and potentially strengthened trust with both employers.",
    "Negotiating a delayed start would have avoided the conflict during the most sensitive phases of the proceeding but may not have been feasible given the multi-year timeline of the case and the State\u0027s hiring needs."
  ],
  "proeth-scenario:decisionSignificance": "Career transitions in engineering can create profound and non-obvious conflicts of interest, especially in long-running regulatory or legal proceedings. Students should learn to conduct a thorough conflict-of-interest analysis before accepting new employment, and to recognize that switching sides \u2014 even unintentionally \u2014 in an adversarial proceeding raises serious ethical red flags under codes of professional conduct.",
  "proeth-scenario:ethicalTension": "An engineer\u0027s right to pursue legitimate employment opportunities conflicts directly with the duty of loyalty and confidentiality owed to a former employer and client, particularly when the new employer is an active adversary in an ongoing legal proceeding in which the engineer played a certified technical role.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s professional license and reputation, the fairness and integrity of the water-rights proceeding, the private firm\u0027s client\u0027s legal interests, the State\u0027s credibility as an objector, and public confidence in the impartiality of licensed engineers who participate in regulatory processes are all at risk.",
  "proeth:description": "Engineer A voluntarily resigned from the private engineering firm after completing step 2 of the water-rights proceeding, choosing to accept employment with the State, which is an active objector in the very same case. This decision created the foundational conflict-of-interest situation analyzed throughout the case.",
  "proeth:foreseenUnintendedEffects": [
    "Creates a direct conflict of interest by joining an objector in the same proceeding where Engineer A stamped documents for the opposing party",
    "Triggers confidentiality and loyalty obligations to the former employer and client that persist post-resignation",
    "Places Engineer A in a position where his specialized knowledge of the case becomes an ethical liability rather than an asset"
  ],
  "proeth:fulfillsObligation": [
    "Engineer\u0027s right to professional autonomy and career advancement",
    "General duty to disclose known or potential conflicts of interest upon becoming aware of them"
  ],
  "proeth:guidedByPrinciple": [
    "Professional independence and autonomy",
    "Disclosure of conflicts of interest to all affected parties",
    "Avoiding representation of adversary interests in proceedings where specialized knowledge was gained on behalf of a former client (NSPE Code)"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Engineer, transitioning from Private Firm to State employment)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Personal career autonomy vs. ongoing fiduciary obligations to former employer and client",
    "proeth:resolutionReasoning": "Engineer A proceeded with resignation and new employment, with the conflict subsequently managed through institutional isolation rather than obtaining consent from former employer and client, which the discussion notes would likely not have been granted"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Advance Engineer A\u0027s career by accepting a position with the State",
  "proeth:requiresCapability": [
    "Self-assessment of conflict-of-interest implications",
    "Knowledge of professional ethics obligations upon changing employers",
    "Understanding of water-rights court process and the State\u0027s adversarial role"
  ],
  "proeth:temporalMarker": "After completing step 2, before steps 3-5 of the court process commenced or concluded",
  "proeth:violatesObligation": [
    "Potential violation of duty not to place oneself in a position adverse to a former client\u0027s interests in the same specific proceeding without consent (NSPE Code)",
    "Risk of compromising confidentiality obligations to former employer and client by proximity to the adversarial party"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Resigning from Private Firm"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Action_Electing_Isolation_from_State_s_Case",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Allow Engineer A to participate in the State\u0027s case after obtaining written consent from the former employer and private client",
    "Implement isolation without formally notifying the former employer or client, treating it as an internal administrative matter",
    "Transfer Engineer A to an entirely different division or geographic assignment with no connection to water-rights work"
  ],
  "proeth-scenario:characterMotivation": "Engineer A and the State recognized that Engineer A\u0027s prior certified work for the opposing party created an untenable conflict of interest, and both parties acted to manage that conflict responsibly by erecting an ethical wall \u2014 isolating Engineer A from all aspects of the State\u0027s involvement in the case to prevent improper use of privileged knowledge and to preserve the integrity of the proceeding.",
  "proeth-scenario:consequencesIfAlternative": [
    "Obtaining written consent from the former employer and client would have been the most ethically robust solution, converting a unilateral safeguard into a fully informed, consensual arrangement \u2014 but it requires cooperation from parties who may have strong reasons to withhold consent.",
    "Failing to notify the former employer or client of the isolation arrangement, even if the isolation itself is genuine, denies those parties the ability to verify or challenge its adequacy, potentially leaving them unknowingly exposed to risk.",
    "A full reassignment would have provided the strongest structural separation but may have been disproportionate, impractical, or unfair to Engineer A depending on the scope of the State\u0027s water-rights work."
  ],
  "proeth-scenario:decisionSignificance": "Isolation or \u0027ethical wall\u0027 arrangements are a recognized but imperfect mechanism for managing conflicts of interest in professional settings. Students should understand both the value and the limitations of such arrangements: they can be effective safeguards, but they do not fully eliminate the underlying conflict and may not be sufficient without the informed consent of affected parties.",
  "proeth-scenario:ethicalTension": "The State\u0027s operational interest in leveraging all available talent and expertise among its employees conflicts with the ethical imperative to protect the former client\u0027s confidential information and to prevent the appearance \u2014 or reality \u2014 of Engineer A\u0027s prior work being weaponized against the very party it was meant to serve.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If isolation is improperly implemented or later breached \u2014 even inadvertently \u2014 the integrity of the water-rights proceeding could be compromised, the private firm\u0027s client could suffer legal harm, Engineer A could face disciplinary action, and the State\u0027s case could be tainted or dismissed. The reputational stakes for all parties are high.",
  "proeth:description": "Upon joining the State, Engineer A (in coordination with the State as employer) decided to be isolated from the State\u0027s involvement in the specific water-rights case where the former private firm\u0027s client is the applicant. This decision was made to manage the conflict of interest created by Engineer A\u0027s prior work and stamped document on behalf of the opposing party.",
  "proeth:foreseenUnintendedEffects": [
    "Limits the State\u0027s ability to leverage Engineer A\u0027s specialized expertise in the case",
    "Engineer A\u0027s professional knowledge and judgment remain underutilized by his current employer in this matter",
    "Does not fully resolve the conflict of interest since no consent was obtained from former employer and client"
  ],
  "proeth:fulfillsObligation": [
    "Duty not to participate in or represent an adversary interest in a specific proceeding where specialized knowledge was gained for a former client without consent (NSPE Code)",
    "Obligation to protect confidential information of former employer and client",
    "Duty to disclose conflicts of interest to current employer",
    "Obligation to act so as not to compromise the integrity of the court proceedings"
  ],
  "proeth:guidedByPrinciple": [
    "Engineers shall not disclose confidential information of former clients without consent (NSPE Code)",
    "Engineers shall not participate in or represent an adversary interest in a specific proceeding where specialized knowledge was gained for a former client without consent of all interested parties (NSPE Code)",
    "Avoidance of appearance of impropriety in adversarial proceedings",
    "Protection of public trust in engineering judgment and court processes"
  ],
  "proeth:hasAgent": "Engineer A (newly employed State Engineer) and the State (as institutional employer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "State\u0027s operational interest in Engineer A\u0027s expertise vs. Engineer A\u0027s ethical obligations to former employer and client",
    "proeth:resolutionReasoning": "Isolation was chosen as the practical management mechanism, consistent with the discussion\u0027s conclusion that Engineer A must remain isolated and that the State should formally assign him other duties; however, the discussion also implies this is an imperfect resolution since consent from former parties was not secured"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Prevent Engineer A from participating in or representing the State\u0027s adversarial interest in a proceeding where he gained specialized knowledge on behalf of the opposing private client, thereby honoring confidentiality and loyalty obligations to the former employer and client",
  "proeth:requiresCapability": [
    "Self-assessment of conflict-of-interest scope and duration",
    "Institutional conflict-of-interest management procedures",
    "Knowledge of NSPE Code obligations regarding former clients in adversarial proceedings",
    "Administrative capacity to reassign duties within the State agency"
  ],
  "proeth:temporalMarker": "Upon commencement of State employment, during steps 3-5 of the court process",
  "proeth:violatesObligation": [
    "Isolation alone does not fully satisfy the NSPE Code requirement to obtain consent from former employer and client before any participation; the discussion notes consent was not obtained"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Electing Isolation from State\u0027s Case"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Water-Rights_Proceeding_Initiated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why does the adversarial nature of a proceeding matter when assessing an engineer\u0027s professional obligations?",
    "At what point should an engineer assess whether future employment opportunities could conflict with a current engagement?",
    "How does the multi-year timeline of such proceedings extend an engineer\u0027s ethical obligations beyond the immediate work?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral at this stage for Engineer A; procedural and administrative in character; stakeholders begin positioning themselves strategically",
  "proeth-scenario:ethicalImplications": "Reveals how the structure of legal proceedings imposes long-duration ethical constraints on engineers; highlights the tension between an engineer\u0027s career mobility and loyalty to ongoing client matters",
  "proeth-scenario:learningMoment": "Students should recognize that adversarial legal proceedings create heightened confidentiality and loyalty obligations from the very beginning of engagement, not merely when conflicts become obvious.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Enters a legally complex, adversarial context whose full implications may not yet be apparent",
    "private_client": "Relies on engineering firm to navigate a prolonged adversarial process",
    "private_firm": "Accepts engagement knowing the State is an active adversary",
    "state": "Formally committed to opposing the application, establishing future conflict potential"
  },
  "proeth:activatesConstraint": [
    "Adversarial_Proceeding_Confidentiality_Constraint",
    "Multi-Party_Conflict_Awareness_Constraint"
  ],
  "proeth:causesStateChange": "A legally structured, adversarial engineering context is established; the State is formally positioned as an objector; the proceeding\u0027s multi-year timeline is set in motion",
  "proeth:createsObligation": [
    "Obligation_to_Identify_Conflicting_Parties",
    "Obligation_to_Maintain_Client_Loyalty_Throughout_Proceeding"
  ],
  "proeth:description": "A formal water-rights proceeding was commenced, triggering a multi-step, multi-year legal and engineering process involving multiple parties including the State as an objector. This exogenous event established the adversarial context in which all subsequent professional obligations arose.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Before Engineer A\u0027s involvement; pre-case background",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Water-Rights Proceeding Initiated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Conflict_of_Interest_Materializes",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what point did Engineer A have an obligation to foresee and prevent this conflict, and was that point before or after accepting the State position?",
    "What is the difference between a conflict of interest that can be resolved by consent and one that cannot \u2014 and which applies here?",
    "How should institutions like the State structure their hiring processes to detect and manage these conflicts before employment begins?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Potential anxiety and alarm for Engineer A upon recognizing the conflict; concern and possible frustration for the private firm and client upon learning of the employment change; institutional concern at the State about managing the conflict properly",
  "proeth-scenario:ethicalImplications": "Reveals the structural nature of conflicts of interest in adversarial proceedings; highlights tension between individual career rights and systemic integrity of legal processes; raises questions about institutional responsibility in managing employee conflicts",
  "proeth-scenario:learningMoment": "Conflicts of interest are not always the result of bad intentions \u2014 they can arise automatically from career transitions, and recognizing them promptly and structurally is itself an ethical obligation.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional standing at risk; must navigate competing loyalties; career advancement potentially constrained by isolation requirement",
    "private_firm_and_client": "Confidential work product and litigation strategy now potentially exposed to an adversary\u0027s employer; trust in Engineer A\u0027s integrity tested",
    "proceeding_integrity": "Risk of unfair advantage or appearance of impropriety if conflict is not managed; public trust in regulatory process at stake",
    "state": "Institutional obligation to manage conflict arises; failure to isolate Engineer A could compromise the State\u0027s case and expose it to legal challenge"
  },
  "proeth:activatesConstraint": [
    "Conflict_of_Interest_Prohibition_Constraint",
    "Duty_of_Loyalty_to_Former_Client_Constraint",
    "Confidentiality_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/75#Action_Resigning_from_Private_Firm",
  "proeth:causesStateChange": "Engineer A transitions from a position of single-client loyalty to a structurally conflicted position; dual obligations to former private client and new State employer are now irreconcilable without consent and isolation",
  "proeth:createsObligation": [
    "Obligation_to_Disclose_Conflict_to_Relevant_Parties",
    "Obligation_to_Seek_Consent_from_Former_Employer_and_Client",
    "Obligation_to_Refrain_from_Participating_in_State_Case",
    "Obligation_to_Implement_Isolation_Measures"
  ],
  "proeth:description": "Upon Engineer A accepting employment with the State \u2014 which is an active objector in the same water-rights proceeding \u2014 a direct and concrete conflict of interest came into existence. This event is the automatic result of two previously independent facts (Engineer A\u0027s prior work for the applicant and Engineer A\u0027s new employment with an adversary) converging.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "At the moment Engineer A accepted State employment",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Conflict of Interest Materializes"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Steps_1_2_Completed_by_Engineer_A",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What does co-stamping a document in an adversarial proceeding commit an engineer to, beyond the moment of signing?",
    "Should engineers consider their potential career trajectory before accepting work in long-duration adversarial proceedings?",
    "How does the existence of stamped work product change an engineer\u0027s obligations if they later change employers?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Sense of professional accomplishment for Engineer A; routine satisfaction for the private firm; no alarm at this stage",
  "proeth-scenario:ethicalImplications": "Highlights how professional licensure creates durable accountability; raises questions about the long-term nature of engineering responsibility in legal proceedings",
  "proeth-scenario:learningMoment": "Stamping a document is not merely a formality \u2014 it creates enduring professional accountability that persists even after employment ends, extending obligations into future phases of a proceeding.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Formally bound to the work product; professional seal creates lasting accountability",
    "private_client": "Engineering support secured for first two steps; relies on continued integrity of that work",
    "private_firm": "Deliverable completed; client served; proceeding advanced",
    "state": "Opposing engineering analysis now formally on record"
  },
  "proeth:activatesConstraint": [
    "Professional_Competence_Constraint",
    "Client_Confidentiality_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/75#Action_Stamping_Final_Analysis_Document",
  "proeth:causesStateChange": "Engineer A has formally contributed substantive engineering work to an adversarial proceeding; a professional and legal record now exists tying Engineer A to the private client\u0027s position",
  "proeth:createsObligation": [
    "Obligation_to_Stand_Behind_Stamped_Analysis",
    "Obligation_to_Protect_Confidential_Work_Product_Post-Employment"
  ],
  "proeth:description": "Engineer A completed the application support (Step 1) and engineering analysis support (Step 2) for the private firm\u0027s client in the water-rights proceeding. This outcome marks the formal conclusion of Engineer A\u0027s active technical contribution to the case while employed at the private firm.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Prior to or concurrent with Engineer A\u0027s resignation",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Steps 1\u20132 Completed by Engineer A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Isolation_Formally_Implemented",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is isolation alone sufficient to resolve the ethical conflict, or does it merely manage it \u2014 and what is the difference?",
    "What are the limits of isolation as a conflict management tool, and when does it fail?",
    "Who bears responsibility for ensuring the isolation is maintained \u2014 Engineer A, the State, or both \u2014 and how should that responsibility be enforced?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Relief for Engineer A that the conflict is being managed; possible frustration at career constraint; reassurance for the private client that their interests are being protected; institutional confidence at the State that proper procedures are followed",
  "proeth-scenario:ethicalImplications": "Demonstrates that institutional processes can operationalize ethical obligations but cannot replace individual ethical responsibility; raises questions about the adequacy of procedural solutions to substantive conflicts; highlights the shared nature of ethical obligation between individual engineers and their employing institutions",
  "proeth-scenario:learningMoment": "Isolation is a recognized and legitimate mechanism for managing conflicts of interest, but it is not self-executing \u2014 it requires active institutional commitment, ongoing monitoring, and does not substitute for consent from affected parties.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Career at State proceeds but with a defined constraint; professional integrity preserved; potential resentment at limited role",
    "private_firm_and_client": "Confidential information and work product protected from adversarial use; trust in process partially restored",
    "proceeding": "Fairness of adversarial process protected; risk of improper advantage reduced",
    "state": "Institutional integrity preserved; legal challenge to proceeding on conflict grounds reduced; administrative burden of maintaining isolation created"
  },
  "proeth:activatesConstraint": [
    "Isolation_Maintenance_Constraint",
    "Non-Disclosure_of_Prior_Confidential_Work_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/75#Action_Electing_Isolation_from_State_s_Case",
  "proeth:causesStateChange": "Engineer A is formally walled off from the State\u0027s case; institutional protocols are in place; the conflict is managed but not resolved; Engineer A\u0027s participation in the proceeding on either side is suspended pending consent",
  "proeth:createsObligation": [
    "Obligation_to_Sustain_Isolation_for_Proceeding_Duration",
    "Obligation_to_Refrain_from_Any_Indirect_Participation",
    "Obligation_to_Seek_Consent_Before_Any_Participation"
  ],
  "proeth:description": "Upon joining the State, Engineer A was formally isolated from the State\u0027s case in the water-rights proceeding. This outcome \u2014 whether initiated by Engineer A, the State, or both \u2014 represents the institutional recognition and operationalization of the conflict-of-interest constraint.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon or shortly after Engineer A joining the State",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Isolation Formally Implemented"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Prior_BER_Precedent_Applicable",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the existence of prior ethical precedent change an engineer\u0027s responsibility to recognize and manage conflicts of interest?",
    "What does it mean for the engineering profession that BER Case No. 98-4 and the current case share the same structural conflict \u2014 is this a systemic problem requiring systemic solutions?",
    "Should engineering ethics education include adversarial proceeding conflicts as a standard topic, given the recurrence of this pattern?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Sobering for Engineer A \u2014 the situation is not novel or ambiguous; the profession has already grappled with this and reached clear conclusions; validates the seriousness of the obligations",
  "proeth-scenario:ethicalImplications": "Illustrates the role of institutional memory and precedent in professional ethics; highlights the expectation that licensed engineers are familiar with established ethical standards; raises questions about how well the profession communicates its ethical precedents to practitioners",
  "proeth-scenario:learningMoment": "Engineering ethics is not decided anew in each case \u2014 precedent exists, and engineers are expected to know and apply it. The existence of prior BER cases on conflict of interest in adversarial proceedings means that ignorance of these obligations is not a defense.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Prior precedent removes ambiguity; Engineer A cannot claim ignorance of applicable standards",
    "engineering_profession": "Demonstrates the profession\u0027s capacity for self-regulation through precedent-based ethical reasoning",
    "private_firm_and_client": "Reassured that established ethical norms protect their interests",
    "state": "Institutional obligations to isolate Engineer A are reinforced by professional ethical standards, not merely internal policy"
  },
  "proeth:activatesConstraint": [
    "Precedent_Consistency_Constraint",
    "Conflict_of_Interest_Prohibition_Constraint"
  ],
  "proeth:causesStateChange": "The ethical analysis is anchored to established precedent; Engineer A\u0027s obligations are clarified and reinforced by prior BER reasoning; the conclusion that consent is required before any participation is normatively grounded",
  "proeth:createsObligation": [
    "Obligation_to_Apply_Established_Ethical_Standards_to_Current_Situation",
    "Obligation_to_Remain_Isolated_Without_Consent_per_Precedent"
  ],
  "proeth:description": "The Board of Ethical Review\u0027s prior case No. 98-4, addressing analogous conflict-of-interest dynamics in adversarial proceedings, became applicable to Engineer A\u0027s situation. This exogenous event \u2014 the existence of established ethical precedent \u2014 shapes and constrains the normative analysis of Engineer A\u0027s obligations.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Referenced during ethical analysis; precedent pre-dates current case",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Prior BER Precedent Applicable"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Consent_Requirement_Triggered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What should Engineer A do if the former employer or private client refuses to grant consent \u2014 and does that refusal itself tell us anything about the legitimacy of the conflict concern?",
    "Is there any circumstance in which Engineer A could participate in the State\u0027s case without consent, and if so, what would justify it?",
    "How should the consent process be structured \u2014 who initiates it, what information must be disclosed, and what form should consent take?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Constraint and potential frustration for Engineer A; protective reassurance for the private client; institutional clarity for the State about what is required before Engineer A can contribute",
  "proeth-scenario:ethicalImplications": "Reveals the power dynamics embedded in conflict-of-interest resolution; highlights that ethical obligations can create asymmetric constraints that limit professional autonomy; raises questions about the adequacy of consent as a mechanism when parties have adversarial interests",
  "proeth-scenario:learningMoment": "Consent from affected parties is not a courtesy in conflict-of-interest situations \u2014 it is a mandatory ethical prerequisite. The absence of consent does not merely create risk; it creates a prohibition.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional autonomy constrained; must navigate a consent process that may be refused; career at State limited until consent obtained or proceeding concluded",
    "private_firm_and_client": "Hold meaningful power over Engineer A\u0027s participation; can protect their interests by withholding or conditioning consent",
    "proceeding": "Integrity protected by consent requirement; adversarial fairness maintained",
    "state": "Cannot deploy Engineer A\u0027s expertise in this matter without triggering ethical violation; must plan around Engineer A\u0027s constraint"
  },
  "proeth:activatesConstraint": [
    "Consent_Required_Before_Participation_Constraint",
    "Prohibition_on_Unilateral_Participation_Constraint",
    "Duty_of_Loyalty_to_Former_Client_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/75#Action_Resigning_from_Private_Firm",
  "proeth:causesStateChange": "Engineer A\u0027s ability to participate in the State\u0027s case is legally and ethically suspended; participation without consent would constitute a violation of professional obligations regardless of isolation measures already in place",
  "proeth:createsObligation": [
    "Obligation_to_Seek_Informed_Consent_from_Former_Employer",
    "Obligation_to_Seek_Informed_Consent_from_Private_Client",
    "Obligation_to_Refrain_from_Participation_Until_Consent_Obtained"
  ],
  "proeth:description": "As an automatic consequence of the conflict of interest materializing and the isolation being implemented, the requirement that Engineer A obtain consent from the former employer and private client before any participation in the State\u0027s case became operative. This is not a decision but an automatic normative trigger arising from the confluence of prior engagement, adversarial context, and employment transition.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Concurrent with conflict materialization; operative throughout remaining proceeding",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Consent Requirement Triggered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#Event_Proceeding_Continues_Post-Transition",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How should an engineer plan for the possibility that a current engagement will outlast their current employment?",
    "What institutional mechanisms should the State have in place to monitor and maintain isolation over a multi-year proceeding?",
    "Does the length of the proceeding change the ethical calculus for Engineer A in any way?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Sustained professional anxiety for Engineer A, who cannot simply \u0027move on\u0027; ongoing uncertainty for the private client about the integrity of their engineering support; institutional vigilance required at the State",
  "proeth-scenario:ethicalImplications": "Illustrates the temporal depth of engineering ethics obligations; challenges the assumption that obligations end with employment; raises questions about the sustainability of isolation as a conflict management tool over long time horizons",
  "proeth-scenario:learningMoment": "Engineering ethical obligations in adversarial proceedings do not expire when employment ends \u2014 they persist for the full duration of the matter, which may span years and multiple professional transitions.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional constraints persist indefinitely until proceeding concludes; career at State is shadowed by prior engagement",
    "private_firm_and_client": "Continued reliance on the integrity of Engineer A\u0027s prior work; vulnerability to any breach of confidentiality",
    "proceeding": "Integrity of adversarial process depends on sustained management of Engineer A\u0027s conflict",
    "state": "Must maintain isolation protocols for an extended, indeterminate period"
  },
  "proeth:activatesConstraint": [
    "Ongoing_Isolation_Requirement_Constraint",
    "Prohibition_on_Participation_Without_Consent_Constraint"
  ],
  "proeth:causesStateChange": "The adversarial context in which Engineer A\u0027s conflict is embedded remains live; Engineer A\u0027s obligations of isolation and non-participation are not time-limited but extend through all remaining steps of the proceeding",
  "proeth:createsObligation": [
    "Obligation_to_Maintain_Isolation_for_Duration_of_Proceeding",
    "Obligation_to_Avoid_Indirect_Participation_in_State_Case"
  ],
  "proeth:description": "The water-rights proceeding remained active and ongoing after Engineer A\u0027s employment transition, with Steps 3 through 5 (objections, rebuttal, and mediation/trial) yet to be completed. This exogenous continuation of the proceeding means that Engineer A\u0027s prior work product remains live and contested in an adversarial forum.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Ongoing after Engineer A joined the State",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Proceeding Continues Post-Transition"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#CausalChain_2f6a1fd0",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A and a colleague affixed their professional stamps to the final water-rights analysis document, creating a professional record of authorship that later became the basis for the conflict when Engineer A joined the opposing State agency.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A professionally stamps the water-rights analysis, creating a formal record of authorship and technical responsibility",
      "proeth:element": "Stamping Final Analysis Document (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A completes the substantive engineering work for the private firm, establishing deep technical involvement",
      "proeth:element": "Steps 1\u20132 Completed by Engineer A (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A voluntarily transitions away from the private firm, severing the employment relationship but not the professional record",
      "proeth:element": "Resigning from Private Firm (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The water-rights proceeding remains active, keeping Engineer A\u0027s prior stamped work relevant and contested",
      "proeth:element": "Proceeding Continues Post-Transition (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s new State employment as an objector in the same proceeding creates a direct conflict with prior private-firm work",
      "proeth:element": "Conflict of Interest Materializes (Event 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Stamping Final Analysis Document (Action 1)",
  "proeth:counterfactual": "Without the professional stamp, Engineer A\u0027s prior involvement would be less formally documented and the conflict might not have triggered the same ethical obligations; without the State employment, no conflict would arise at all",
  "proeth:effect": "Conflict of Interest Materializes (Event 3)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s professional stamp affixed to the document",
    "Engineer A\u0027s subsequent employment with the State as an active objector",
    "The water-rights proceeding remaining active and ongoing"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Stamped professional authorship + transition to opposing employer + active proceeding = conflict of interest materializes"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#CausalChain_b9682c67",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon joining the State, Engineer A (in coordination with the State as employer) decided to be isolated from the State\u0027s case, which directly produced the formal isolation mechanism documented in Event 5.",
  "proeth:causalSequence": [
    {
      "proeth:description": "The conflict is recognized upon Engineer A joining the State",
      "proeth:element": "Conflict of Interest Materializes (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "BER Case No. 98-4 provides ethical guidance on appropriate conflict management, including isolation",
      "proeth:element": "Prior BER Precedent Applicable (Event 6)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A and the State jointly decide on isolation as the conflict mitigation strategy",
      "proeth:element": "Electing Isolation from State\u0027s Case (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The isolation is operationalized within the State\u0027s organizational structure",
      "proeth:element": "Isolation Formally Implemented (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Isolation implementation, combined with the underlying conflict, triggers the formal consent requirement",
      "proeth:element": "Consent Requirement Triggered (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Electing Isolation from State\u0027s Case (Action 3)",
  "proeth:counterfactual": "Without Engineer A\u0027s election of isolation (or without the State\u0027s cooperation), the formal isolation mechanism would not have been implemented, leaving the conflict unmitigated and potentially violating ethics codes",
  "proeth:effect": "Isolation Formally Implemented (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s volitional decision to accept isolation",
    "State\u0027s cooperation and coordination in implementing the isolation",
    "Existence of an active conflict requiring mitigation"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A and State (joint decision-makers)",
  "proeth:sufficientFactors": [
    "Mutual agreement between Engineer A and State + active conflict = formal isolation implemented"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#CausalChain_9ac06d93",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A determined that he can and should continue to support the technical work he performed and stamped, while simultaneously deciding not to disclose confidential technical processes or business affairs of the former employer \u2014 creating a dual obligation that shapes the boundaries of permissible support.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A\u0027s professional stamp creates ongoing responsibility for and ownership of the technical work",
      "proeth:element": "Stamping Final Analysis Document (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "The conflict creates pressure to define the scope of Engineer A\u0027s permissible continued involvement",
      "proeth:element": "Conflict of Interest Materializes (Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A determines that supporting the technical integrity of prior stamped work is both permissible and professionally obligatory",
      "proeth:element": "Deciding to Support Prior Stamped Work (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A simultaneously constrains the scope of support by refusing to disclose former employer\u0027s confidential processes or business affairs",
      "proeth:element": "Refraining from Disclosing Confidential Information (Action 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The bounded support posture \u2014 supporting stamped work without disclosing confidences \u2014 operates within the consent and isolation framework",
      "proeth:element": "Consent Requirement Triggered (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Deciding to Support Prior Stamped Work (Action 4)",
  "proeth:counterfactual": "Without the decision to support prior work, no tension with confidentiality obligations would arise; without the confidentiality constraint, Engineer A\u0027s support could be unrestricted \u2014 the interaction of both decisions defines the ethical boundary",
  "proeth:effect": "Refraining from Disclosing Confidential Information (Action 5)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s prior stamped authorship creating a legitimate basis for continued technical support",
    "The existence of confidential information from the former private firm",
    "The ongoing water-rights proceeding requiring technical testimony or analysis"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Legitimate support interest + confidentiality obligation + active proceeding = constrained but permissible continued involvement in defending prior work"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#CausalChain_983f439c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A formal water-rights proceeding was commenced, triggering a multi-step, multi-year legal and engineering process that required Engineer A to complete application support (Step 1) and engineering analysis support (Step 2) on behalf of the private firm.",
  "proeth:causalSequence": [
    {
      "proeth:description": "The formal proceeding creates the legal and engineering context requiring professional analysis",
      "proeth:element": "Water-Rights Proceeding Initiated (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A performs and completes the substantive engineering work for the private firm",
      "proeth:element": "Steps 1\u20132 Completed by Engineer A (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A professionally stamps the completed analysis, creating a formal record of authorship",
      "proeth:element": "Stamping Final Analysis Document (Action 1)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A departs the private firm, creating the conditions for a future employment transition",
      "proeth:element": "Resigning from Private Firm (Action 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s new State employment in the same active proceeding produces the conflict that drives all subsequent ethical obligations",
      "proeth:element": "Conflict of Interest Materializes (Event 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Water-Rights Proceeding Initiated (Event 1)",
  "proeth:counterfactual": "Without the water-rights proceeding being initiated, there would be no engineering analysis to perform, no document to stamp, and no subsequent conflict \u2014 the proceeding is the foundational triggering event for the entire causal chain",
  "proeth:effect": "Steps 1\u20132 Completed by Engineer A (Event 2)",
  "proeth:necessaryFactors": [
    "Formal initiation of the water-rights proceeding",
    "Private firm\u0027s need for engineering analysis support",
    "Engineer A\u0027s assignment to and acceptance of the work"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Private engineering firm (assignment); Engineer A (execution)",
  "proeth:sufficientFactors": [
    "Proceeding initiation + firm assignment + Engineer A\u0027s professional execution = completion of Steps 1 and 2"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/75#",
    "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/75#CausalChain_f705ccec",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As an automatic consequence of the conflict of interest materializing and the isolation being implemented, a consent requirement was triggered, meaning that affected parties must provide informed consent for Engineer A\u0027s continued involvement in any capacity touching the proceeding.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A\u0027s dual role \u2014 prior private-firm analyst and new State employee-objector \u2014 creates a recognized conflict",
      "proeth:element": "Conflict of Interest Materializes (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Established ethical precedent from BER Case No. 98-4 provides the governing framework for how the conflict must be managed",
      "proeth:element": "Prior BER Precedent Applicable (Event 6)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A and the State coordinate to formally isolate Engineer A from the State\u0027s active case as a conflict mitigation measure",
      "proeth:element": "Electing Isolation from State\u0027s Case (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The isolation is operationalized, creating a structural barrier between Engineer A and the State\u0027s litigation strategy",
      "proeth:element": "Isolation Formally Implemented (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The combination of the conflict and isolation automatically triggers the obligation to obtain informed consent from affected parties",
      "proeth:element": "Consent Requirement Triggered (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Conflict of Interest Materializes (Event 3)",
  "proeth:counterfactual": "Without the conflict of interest materializing, no consent requirement would be triggered; the consent requirement is a direct legal and ethical consequence of the conflict itself",
  "proeth:effect": "Consent Requirement Triggered (Event 7)",
  "proeth:necessaryFactors": [
    "Conflict of interest formally materializing upon Engineer A joining the State",
    "The isolation mechanism being implemented as a response",
    "Applicable professional ethics rules requiring consent in dual-loyalty conflict scenarios"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); State as employer (secondary)",
  "proeth:sufficientFactors": [
    "Materialized conflict + isolation implementation + governing ethics rules = automatic triggering of consent requirement"
  ],
  "proeth:withinAgentControl": true
}