{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Action_Accepts_Government_Dam_Retention",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the government retention due to anticipated conflicts with existing or prospective clients in the dam/construction sector.",
    "Accept the retention but proactively document and disclose the scope of confidential information received, establishing clear boundaries for future use.",
    "Accept the retention with an explicit written agreement clarifying that the engagement creates no ongoing exclusivity but does create permanent confidentiality obligations."
  ],
  "proeth-scenario:characterMotivation": "Engineer A accepts a legitimate, well-defined government engagement aligned with professional expertise \u2014 likely motivated by professional duty, financial compensation, and the opportunity to contribute technical knowledge to a matter of public concern (dam failure investigation). No ethical red flags exist at this stage; the motivation is straightforwardly professional.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining avoids any future conflict but foregoes a legitimate professional opportunity and may damage Engineer A\u0027s relationship with a significant government client; no ethical violation occurs.",
    "Proactive documentation does not prevent the later conflict but creates a clearer evidentiary record of what was confidential, potentially making Engineer A more acutely aware of the constraints before accepting the contractor engagement.",
    "An explicit written agreement clarifying confidentiality obligations could serve as a self-reminder and professional safeguard, though it would not change the underlying ethical rule \u2014 it might, however, prompt Engineer A to think twice before accepting adverse work later."
  ],
  "proeth-scenario:decisionSignificance": "Establishes the foundational principle that forming a client-engineer relationship is not a trivial act \u2014 it creates lasting legal and ethical obligations (confidentiality, loyalty, conflict-of-interest avoidance) that survive the termination of the engagement. Students should recognize that every new client relationship plants the seeds of potential future conflicts.",
  "proeth-scenario:ethicalTension": "Minimal tension at this stage, but latent: accepting any client engagement creates confidentiality and loyalty obligations that may constrain future work. The tension between maximizing future professional opportunities and honoring the full scope of duties owed to a current client is seeded here, even if not yet visible.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The U.S. government entrusts Engineer A with sensitive technical and potentially legally significant information about the dam failure. If that information is later misused, public trust in the engineering profession is damaged, the government\u0027s legal position may be compromised, and Engineer A\u0027s professional license and reputation are at risk.",
  "proeth:description": "Engineer A voluntarily enters into a retainer agreement with the U.S. government to study the causes of a dam failure, thereby establishing a formal client-engineer relationship with attendant confidentiality and loyalty obligations.",
  "proeth:foreseenUnintendedEffects": [
    "Accumulation of privileged and specialized knowledge about the dam failure that could create future conflicts of interest",
    "Creation of a former-client relationship that would constrain future engagements under the 1981 Code"
  ],
  "proeth:fulfillsObligation": [
    "Duty to serve clients faithfully (NSPE Code Section III.4)",
    "Obligation to provide competent professional services",
    "Obligation to act in the public interest by investigating a public infrastructure failure"
  ],
  "proeth:guidedByPrinciple": [
    "Fidelity to client",
    "Competence and professional service",
    "Public safety and welfare"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Forensic Consultant)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide professional forensic engineering services to the U.S. government and fulfill the contracted scope of investigating dam failure causes",
  "proeth:requiresCapability": [
    "Forensic engineering analysis",
    "Dam and hydraulic infrastructure expertise",
    "Technical investigation and reporting"
  ],
  "proeth:temporalMarker": "Initial engagement, prior to dam failure investigation completion",
  "proeth:withinCompetence": true,
  "rdfs:label": "Accepts Government Dam Retention"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Action_Completes_and_Terminates_Government_Retainer",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Upon completing the government work, proactively consult with an ethics advisor or legal counsel about what future engagements would be permissible given the knowledge gained.",
    "Upon termination, send a formal closing letter to the U.S. government explicitly acknowledging ongoing confidentiality obligations and self-imposing a recusal from dam-related adverse work.",
    "Decline full payment in exchange for a formal release that clarifies the scope of post-engagement obligations, creating mutual clarity about what Engineer A may and may not do going forward."
  ],
  "proeth-scenario:characterMotivation": "Engineer A completes the contracted scope of work, receives full payment, and naturally concludes the engagement. The motivation is straightforward professional closure \u2014 fulfilling contractual obligations and moving on to new work. Engineer A may mistakenly believe that the end of the retainer extinguishes all special obligations to the U.S. government.",
  "proeth-scenario:consequencesIfAlternative": [
    "Consulting an ethics advisor before accepting any new dam-related work would likely have prevented the subsequent violation entirely \u2014 the advisor would have flagged the conflict under Section III.4.b. before Engineer A accepted the contractor engagement.",
    "A proactive closing letter acknowledging confidentiality obligations would create a written record of Engineer A\u0027s awareness of those duties, making it far less likely he would later accept the adverse contractor engagement without at least pausing to seek consent.",
    "Negotiating a formal release is unusual and may be impractical, but it would force both parties to explicitly confront post-engagement obligations \u2014 likely resulting in the government imposing restrictions that would have blocked the subsequent conflict."
  ],
  "proeth-scenario:decisionSignificance": "This action is the critical teaching moment about the distinction between contractual obligations (which terminate) and ethical obligations (which do not). Students must understand that \u0027former client\u0027 status is not a clean slate \u2014 NSPE Code Section III.4.b. explicitly governs conduct toward former clients, and the transition from active client to former client does not reset the ethical clock.",
  "proeth-scenario:ethicalTension": "The core tension is between the common assumption that obligations end when a contract ends versus the ethical and legal reality that certain duties \u2014 particularly confidentiality and the prohibition on adverse representation using privileged knowledge \u2014 survive contract termination indefinitely. Engineer A\u0027s sense of freedom upon closure conflicts with the enduring nature of former-client duties.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If Engineer A incorrectly treats termination of the retainer as full ethical discharge, he becomes vulnerable to accepting conflicting engagements. The U.S. government\u0027s confidential technical and legal information remains at risk of being used adversely. Engineer A\u0027s professional standing, license, and reputation are increasingly at stake as the story moves forward.",
  "proeth:description": "Engineer A concludes the government investigation, accepts full payment, and allows the retainer relationship with the U.S. government to terminate, transitioning from active client to former-client status.",
  "proeth:foreseenUnintendedEffects": [
    "Termination of active retainer does not extinguish ethical obligations regarding privileged knowledge under the 1981 Code",
    "Transition to former-client status creates a new regulatory constraint under Section III.4.b. that may not have been fully appreciated"
  ],
  "proeth:fulfillsObligation": [
    "Completion of contracted professional services",
    "Delivery of investigative findings to the client"
  ],
  "proeth:guidedByPrinciple": [
    "Fidelity to client through completion of engagement",
    "Professional accountability"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Forensic Consultant)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Formally close the government engagement, receive compensation, and free himself from ongoing obligations to the U.S. government so as to pursue subsequent professional work",
  "proeth:requiresCapability": [
    "Professional judgment regarding engagement closure",
    "Awareness of post-engagement ethical obligations"
  ],
  "proeth:temporalMarker": "Intermediate point, after government investigation is complete and before contractor engagement",
  "proeth:withinCompetence": true,
  "rdfs:label": "Completes and Terminates Government Retainer"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Action_Accepts_Contractor_Adverse_Retention",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the contractor engagement outright upon recognizing that the contractor is in an adverse legal proceeding against his former client, the U.S. government.",
    "Before accepting, disclose the prior government engagement to the contractor and seek written, informed consent from the U.S. government as required by Section III.4.b.",
    "Accept a limited consulting role for the contractor that explicitly excludes any use of information, analysis, or opinions derived from the government engagement, with written acknowledgment from both parties."
  ],
  "proeth-scenario:characterMotivation": "Engineer A is likely motivated by financial opportunity, professional demand for his specialized expertise in dam engineering, and possibly a rationalization that the government engagement is \u0027over\u0027 and therefore no longer constraining. He may also genuinely believe \u2014 incorrectly \u2014 that his technical knowledge is general expertise rather than privileged information gained from a specific client relationship. There may also be implicit pressure or flattery from the contractor seeking his unique insider knowledge.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining is the cleanest ethical resolution \u2014 no violation occurs, Engineer A\u0027s integrity is preserved, and both the contractor and the government are protected. Engineer A foregoes the fee but avoids all professional and legal risk.",
    "Seeking consent from the U.S. government is the procedurally correct path under Section III.4.b. The government would likely decline consent given the adversarial nature of the proceeding, effectively producing the same outcome as declining \u2014 but Engineer A would have acted ethically by following the required procedure.",
    "A limited role with explicit exclusions is theoretically possible but practically very difficult to enforce and verify; it also may not satisfy Section III.4.b., which prohibits the engagement itself absent consent, not merely the disclosure of specific information. This alternative carries significant residual ethical and legal risk."
  ],
  "proeth-scenario:decisionSignificance": "This is the primary teaching moment of the entire case. It demonstrates a clear violation of NSPE Code Section III.4.b. and illustrates how the 1981 revision of the Code closed a loophole that existed under the 1976 Code. Students should learn: (1) that adverse representation of former clients using knowledge gained from the prior engagement is prohibited without consent; (2) that the contractor\u0027s interests, however legitimate, do not override Engineer A\u0027s ethical obligations; and (3) that the appearance of a conflict is itself professionally damaging, regardless of whether confidential information is actually disclosed.",
  "proeth-scenario:ethicalTension": "This action crystallizes the central ethical conflict of the case: the tension between an engineer\u0027s right (and financial incentive) to practice their profession freely versus the duty of loyalty and confidentiality owed to former clients. Secondary tensions include: specialized knowledge as a professional asset versus specialized knowledge as a confidential trust; serving a new client\u0027s legitimate legal interests versus protecting a former client from adverse use of privileged information.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Maximum stakes: Engineer A risks violation of the NSPE Code of Ethics, potential disciplinary action including license revocation, civil liability for breach of fiduciary duty, damage to professional reputation, compromise of the U.S. government\u0027s legal position in the contractor\u0027s claim, and erosion of public trust in the engineering profession\u0027s integrity. The contractor also risks having its case tainted by association with a conflicted expert.",
  "proeth:description": "Engineer A accepts retention by the contractor who has filed a claim against the U.S. government \u2014 his former client \u2014 for additional compensation, without obtaining the U.S. government\u0027s consent, thereby placing himself in an adversarial position against a former client using knowledge gained during that prior engagement.",
  "proeth:foreseenUnintendedEffects": [
    "Risk of disclosing privileged and confidential information obtained during government engagement",
    "Potential violation of NSPE Code Section III.4.b. if former client consent was not obtained",
    "Creation of appearance of impropriety by leveraging insider government knowledge against the government",
    "Exposure of Engineer A to professional disciplinary action"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to provide competent professional services to the new client (contractor)",
    "General duty to apply engineering expertise to legal proceedings"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflicts of interest",
    "Protection of former client confidentiality",
    "Integrity and impartiality in expert witness roles",
    "Fidelity to the profession\u0027s ethical standards"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Expert Witness)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Post-engagement professional freedom versus former-client confidentiality and anti-adversarial representation obligations",
    "proeth:resolutionReasoning": "The Board determined that the 1981 Code Section III.4.b. unambiguously requires affirmative consent from the former client (U.S. government) before Engineer A could represent the contractor in an adverse proceeding; absent that consent, the engagement is ethically impermissible regardless of whether the prior retainer had formally ended"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide expert witness services and engineering expertise to the contractor to support its compensation claim against the U.S. government, likely for professional compensation and continued practice",
  "proeth:requiresCapability": [
    "Forensic engineering expert witness testimony",
    "Knowledge of dam engineering and failure analysis",
    "Legal proceeding participation and opinion formation",
    "Ethical conflict-of-interest analysis prior to accepting engagement"
  ],
  "proeth:temporalMarker": "Critical decision point, after government retainer is terminated and contractor claim is filed",
  "proeth:violatesObligation": [
    "NSPE Code Section III.4.b. (1981) \u2014 prohibition on representing an adversary interest in a specific project or proceeding in which specialized knowledge was gained on behalf of a former client without consent of all interested parties",
    "Duty of loyalty and confidentiality to former client (U.S. government)",
    "Obligation to avoid conflicts of interest (NSPE Code Section III.4)",
    "Duty to protect privileged and confidential client information beyond the term of engagement"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accepts Contractor Adverse Retention"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Action_Forgoes_Consent-Seeking_from_Former_Client",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Contact the U.S. government\u0027s contracting officer or legal counsel, disclose the contractor\u0027s approach, and formally request consent to represent the contractor \u2014 accepting the outcome whatever it may be.",
    "Consult the NSPE Ethics Hotline or a professional ethics board before accepting the engagement to obtain an independent assessment of whether the engagement is permissible.",
    "Withdraw from the contractor engagement upon self-reflection or upon being advised by a colleague or counsel that the consent requirement had been overlooked, and notify the contractor of the conflict."
  ],
  "proeth-scenario:characterMotivation": "Engineer A\u0027s failure to seek consent likely stems from one or more of the following: (1) ignorance of or inattention to the 1981 revision of the Code introducing Section III.4.b.; (2) a rationalization that the prior engagement is fully concluded and therefore no consent is needed; (3) an assumption that general professional knowledge is not \u0027specialized knowledge gained from a former client\u0027 within the meaning of the Code; or (4) financial and professional incentives that unconsciously discourage scrutiny of the ethical constraints. This is a sin of omission rather than active deception, but it is no less a violation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Formally requesting consent is the ethically required action and the only path to a permissible engagement. If consent is granted, Engineer A may proceed; if refused (the likely outcome), Engineer A must decline. Either way, Engineer A has acted with integrity and in compliance with Section III.4.b., and no violation occurs.",
    "Consulting the NSPE Ethics Hotline or a peer ethics review process would almost certainly surface the conflict and the consent requirement, allowing Engineer A to correct course before a violation is committed. This also demonstrates the value of institutional ethics resources as a practical safeguard.",
    "Withdrawing after the fact, while not preventing the initial violation, is a mitigating action that limits harm \u2014 it demonstrates good faith, reduces the risk of actual confidential information being used adversely, and may be considered favorably in any subsequent disciplinary proceeding. It is the ethical \u0027recovery\u0027 option once the omission is recognized."
  ],
  "proeth-scenario:decisionSignificance": "This action teaches students about the ethical significance of procedural obligations \u2014 the requirement to seek consent is not merely bureaucratic but serves substantive purposes: it protects the former client, forces the engineer to confront the conflict explicitly, and creates a documented record of ethical deliberation. Omitting a required procedural step is itself a violation, independent of whether the underlying action (taking the engagement) would ultimately have been approved. Students should also learn about the dangers of motivated reasoning in ethics \u2014 the tendency to skip steps that would likely produce an unwanted answer.",
  "proeth-scenario:ethicalTension": "The tension here is between procedural ethical compliance (following the explicit consent requirement of Section III.4.b.) and the practical inconvenience and likely futility of seeking that consent \u2014 Engineer A may have anticipated (correctly) that the U.S. government would refuse consent, making the consent-seeking step feel like a formality that would simply block a lucrative engagement. This illustrates how engineers may rationalize skipping procedural safeguards when they predict an unfavorable outcome. There is also tension between self-interest and the spirit of the Code.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "By failing to seek consent, Engineer A forecloses the only legitimate pathway to accepting the contractor engagement. This omission transforms what might have been a curable procedural deficiency into a clear, unambiguous Code violation. The stakes include: professional discipline, reputational damage, potential invalidation of any expert opinions Engineer A provides in the contractor\u0027s claim, and a precedent-setting ethics case that affects the entire profession.",
  "proeth:description": "Engineer A proceeds to accept the contractor engagement without taking the affirmative step of seeking or obtaining consent from the U.S. government \u2014 his former client \u2014 as required by NSPE Code Section III.4.b., thereby omitting a procedurally and ethically mandatory action.",
  "proeth:foreseenUnintendedEffects": [
    "Violation of Section III.4.b. due to absence of required consent",
    "Exposure of privileged government information in adversarial proceedings",
    "Risk of professional disciplinary action",
    "Undermining of trust in the engineering profession\u0027s ethical standards"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency with all parties in potential conflict situations",
    "Proactive conflict-of-interest identification and resolution",
    "Respect for former client relationships and associated ethical obligations"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Expert Witness)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Procedural expediency and self-interest in securing engagement versus mandatory ethical compliance requiring affirmative former-client consent",
    "proeth:resolutionReasoning": "There is no permissible resolution that allows Engineer A to bypass the consent requirement; the only ethically compliant paths were to seek and obtain government consent or to decline the contractor engagement"
  },
  "proeth:hasMentalState": "deliberate omission \u2014 Engineer A made a conscious choice to accept the engagement without pursuing the consent process, whether through oversight, misunderstanding of the 1981 Code, or deliberate disregard",
  "proeth:intendedOutcome": "Proceed with contractor engagement without delay or potential refusal from the government, thereby securing the new professional engagement",
  "proeth:requiresCapability": [
    "Knowledge of current NSPE Code of Ethics requirements",
    "Conflict-of-interest identification and management",
    "Professional communication with former clients regarding consent"
  ],
  "proeth:temporalMarker": "At or before acceptance of contractor retention, after government retainer terminated",
  "proeth:violatesObligation": [
    "NSPE Code Section III.4.b. (1981) \u2014 affirmative obligation to obtain consent of all interested parties before representing adversary interest using specialized former-client knowledge",
    "General duty of transparency and good faith toward former client",
    "Obligation to proactively identify and resolve conflicts of interest before accepting engagements"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Forgoes Consent-Seeking from Former Client"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_1981_Code_Revision_Enacted",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Case 76-3 reached a similar ethical conclusion under the 1976 Code even without an explicit provision. What does this suggest about the relationship between explicit code rules and underlying ethical principles?",
    "Should engineers be held to the ethical standards that existed when they formed a professional relationship, or to the standards in force when they take subsequent actions? How does this affect the analysis of Engineer A\u0027s situation?",
    "The 1981 revision places the burden of obtaining consent on the engineer. Is this the right allocation of burden, or should the Code place obligations on former clients to assert their interests within a specified timeframe?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Institutional confidence for NSPE in having addressed an identified gap; professional obligation for all engineers to update their understanding of applicable standards; no immediate emotional salience for individuals in this case, but significant retrospective importance",
  "proeth-scenario:ethicalImplications": "Illustrates that professional ethics is not static\u2014it evolves through the interaction of cases, institutional reflection, and deliberate standard-setting; raises questions about the retroactive application of new standards to relationships formed under prior rules; demonstrates the importance of professional continuing education to maintain awareness of evolving obligations",
  "proeth-scenario:learningMoment": "Professional ethical codes are living documents that evolve in response to identified gaps and real cases. The 1981 revision demonstrates that the engineering profession takes its self-regulatory function seriously and updates its standards when case analysis reveals inadequacies. Students should understand that knowing the current code\u2014not just historical versions\u2014is a professional obligation.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Now subject to a clearer and more stringent standard than existed under the 1976 Code; cannot claim ambiguity as a defense",
    "engineering_profession": "Professional self-regulation demonstrated through responsive code evolution; credibility of the ethics process enhanced",
    "future_clients": "Greater confidence that confidential information shared with engineers will be protected even after engagement ends",
    "us_government": "As a client of engineers, benefits from stronger protections against adverse use of confidential information"
  },
  "proeth:activatesConstraint": [
    "Section_III_4b_Prohibition_Constraint",
    "Consent_Requirement_Constraint",
    "Specialized_Knowledge_Adverse_Use_Prohibition"
  ],
  "proeth:causesStateChange": "The regulatory landscape governing engineer conflicts of interest is materially changed; what may have been ethically ambiguous under the 1976 Code becomes explicitly prohibited under the 1981 Code; all engineers are on notice of the new standard",
  "proeth:createsObligation": [
    "All_Engineers_Must_Comply_With_Section_III_4b",
    "Seek_Consent_Before_Adverse_Engagement_Using_Former_Client_Knowledge"
  ],
  "proeth:description": "The 1981 revision of the NSPE Code of Ethics introduces Section III.4.b, which explicitly prohibits engineers from using specialized knowledge gained from a former client to represent adverse interests without that client\u0027s consent. This exogenous regulatory event changes the applicable ethical standard governing Engineer A\u0027s situation.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "1981; prior to the events of this case but after the analogous Case 76-3",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "1981 Code Revision Enacted"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_Dam_Failure_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How does the severity of an underlying disaster affect the ethical obligations of experts retained to investigate it?",
    "What special responsibilities arise when an engineer gains access to sensitive government information during a crisis investigation?",
    "Should the nature of the originating event (a public safety failure) heighten or change the conflict-of-interest analysis?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Alarm and urgency for government officials responsible for public infrastructure; potential loss, injury, or economic harm for affected communities; professional opportunity mixed with gravity of responsibility for Engineer A",
  "proeth-scenario:ethicalImplications": "Reveals that public infrastructure failures create asymmetric information environments where forensic experts hold privileged knowledge; raises questions about whether crisis-context expertise carries heavier confidentiality obligations than routine engagements",
  "proeth-scenario:learningMoment": "Exogenous disasters create complex webs of professional relationships and obligations; engineers retained in crisis contexts acquire privileged access to sensitive information that carries lasting ethical responsibilities regardless of how the professional relationship ends.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "affected_communities": "Direct harm from dam failure consequences",
    "contractor": "Possible financial losses from project disruption, grounds for additional compensation claims",
    "engineer_a": "Professional opportunity to serve as forensic expert; access to sensitive government information begins",
    "public": "Safety risk from failure, loss of infrastructure, potential injury or property damage",
    "us_government": "Legal liability exposure, reputational damage, mandatory investigation costs, potential compensation obligations"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Investigation_Mandate",
    "Government_Accountability_Constraint"
  ],
  "proeth:causesStateChange": "Dam is destroyed or compromised; government liability exposure begins; need for forensic engineering expertise activated; contractor claims become possible",
  "proeth:createsObligation": [
    "Investigate_Failure_Causes",
    "Retain_Qualified_Expert",
    "Determine_Liability"
  ],
  "proeth:description": "A dam failure occurs, creating the precipitating condition that requires forensic investigation and government response. This exogenous event establishes the entire context for Engineer A\u0027s subsequent engagements.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to initial engagement; the originating incident",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Dam Failure Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_Government_Retainer_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what precise moment do professional ethical obligations begin\u2014offer, acceptance, first work performed, or first payment?",
    "Does the government\u0027s status as a public institution change the nature or weight of the confidentiality obligations owed to it?",
    "What should Engineer A have considered about future conflict risks before accepting this government engagement?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Professional confidence and sense of duty for Engineer A; relief for government officials that qualified expertise is secured; neutral at this stage for contractor who is unaware of the engagement",
  "proeth-scenario:ethicalImplications": "Illustrates that the formation of a professional relationship is itself an ethically significant event; raises questions about prospective conflict screening obligations and the duty to anticipate future loyalty conflicts before they arise",
  "proeth-scenario:learningMoment": "Professional relationships are not merely contractual\u2014they automatically trigger ethical obligations the moment they are formed. Students should understand that accepting a retention is not a neutral business transaction but an ethical commitment with lasting consequences.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Unaffected at this stage but will later be materially impacted by this relationship\u0027s existence",
    "engineer_a": "Assumes full professional obligations to government client; begins accumulating privileged knowledge that will later create ethical constraints",
    "engineering_profession": "Professional norms activated; Code of Ethics becomes operative framework",
    "us_government": "Gains expert forensic assistance; implicitly trusts Engineer A with sensitive case information"
  },
  "proeth:activatesConstraint": [
    "Client_Loyalty_Constraint",
    "Confidentiality_Obligation_Constraint",
    "Competent_Service_Constraint",
    "Conflict_of_Interest_Avoidance_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/170#Action_Accepts_Government_Dam_Retention",
  "proeth:causesStateChange": "Engineer A transitions from independent consultant to retained government expert; privileged professional relationship established; information shared within this relationship acquires protected status",
  "proeth:createsObligation": [
    "Maintain_Client_Confidentiality",
    "Serve_Government_Competently",
    "Avoid_Conflicting_Engagements",
    "Disclose_Potential_Conflicts"
  ],
  "proeth:description": "A formal professional relationship between Engineer A and the U.S. government comes into existence upon acceptance of the initial retention, creating legally and ethically binding duties of loyalty, confidentiality, and competent service.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "At the moment of initial engagement acceptance",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Government Retainer Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_Specialized_Knowledge_Acquired",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer A have an obligation to actively recognize and catalogue what knowledge is \u0027specialized\u0027 and therefore protected, or is this a retrospective determination?",
    "How does the nature of forensic investigation\u2014which inherently involves accessing an adversary\u0027s vulnerabilities\u2014heighten post-engagement confidentiality obligations?",
    "Should the Code of Ethics require engineers to proactively warn former clients when they are approached by adverse parties, even before accepting a conflicting engagement?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Professional engagement and intellectual investment for Engineer A; trust extended by government officials; no immediate emotional salience\u2014the ethical weight of this event only becomes apparent retrospectively when adverse retention is considered",
  "proeth-scenario:ethicalImplications": "Reveals that professional knowledge is not neutral\u2014its acquisition within a confidential relationship transforms it into protected information with ongoing ethical valence; raises the deeper question of whether engineers can ever fully \u0027unknow\u0027 privileged information and what obligations flow from that impossibility",
  "proeth-scenario:learningMoment": "The acquisition of specialized knowledge during a professional engagement is not merely a technical event\u2014it is an ethically significant occurrence that creates lasting obligations. Students should understand that confidential knowledge does not become freely usable simply because the engagement ends or payment is received.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Unknowingly benefits later from Engineer A\u0027s accumulated knowledge if adverse retention proceeds",
    "engineer_a": "Becomes holder of privileged information that will permanently constrain future engagement options; does not yet recognize the future ethical burden being accumulated",
    "engineering_profession": "The integrity of the forensic expert role depends on this knowledge remaining protected",
    "us_government": "Vulnerability created: sensitive legal and technical information now resides with a third party whose future loyalties are not guaranteed"
  },
  "proeth:activatesConstraint": [
    "Specialized_Knowledge_Protection_Constraint",
    "Confidentiality_Obligation_Constraint",
    "Section_III_4b_Prohibition_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/170#Action_Accepts_Government_Dam_Retention",
  "proeth:causesStateChange": "Engineer A\u0027s knowledge state permanently altered; information asymmetry created between Engineer A and future adverse parties; the specialized knowledge becomes a latent ethical constraint on all future engagements",
  "proeth:createsObligation": [
    "Protect_Acquired_Knowledge_Indefinitely",
    "Refrain_From_Adverse_Use_of_Knowledge",
    "Disclose_Knowledge_Conflict_If_Approached_By_Adverse_Party"
  ],
  "proeth:description": "Through the course of performing forensic analysis of the dam failure, Engineer A accumulates specialized, privileged knowledge about the failure\u0027s causes, the government\u0027s legal vulnerabilities, technical findings, and strategic information that the government shared in confidence.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "During the period of government engagement; ongoing throughout work performance",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Specialized Knowledge Acquired"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_Government_Engagement_Concluded",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Many engineers assume their obligations end when the contract ends and payment is received. What is wrong with this assumption, and why does the Code of Ethics reject it?",
    "Should the Code require engineers to affirmatively notify former clients when they are approached by adverse parties, rather than simply prohibiting acceptance without consent?",
    "How long should post-engagement confidentiality obligations last\u2014is there a point at which specialized knowledge becomes sufficiently stale or public that the prohibition should lapse?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Sense of professional completion and financial satisfaction for Engineer A; relief or closure for government officials; the termination feels routine but contains latent ethical significance that Engineer A may not fully appreciate",
  "proeth-scenario:ethicalImplications": "Exposes a common misconception that professional obligations are purely transactional and end with payment; reveals the Code\u0027s recognition that trust relationships create lasting duties; highlights the gap between what engineers may believe (obligations ended) and what ethics requires (obligations transformed)",
  "proeth-scenario:learningMoment": "Termination of a professional engagement does not terminate all ethical obligations\u2014it transforms them. Students must understand that \u0027former client\u0027 is an ethically significant status, not simply a historical description. The moment of termination is a critical juncture where new constraints activate.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "The window for approaching Engineer A as an adverse expert now technically opens, creating the conditions for the ethical violation",
    "engineer_a": "Gains freedom to pursue new work but carries invisible ethical constraints; may incorrectly believe all obligations to the government have ended with payment",
    "engineering_profession": "The adequacy of professional norms to protect former clients in adversarial legal contexts is now being tested",
    "us_government": "Loses active expert relationship but retains reasonable expectation that privileged information will not be weaponized against them"
  },
  "proeth:activatesConstraint": [
    "Post_Engagement_Confidentiality_Constraint",
    "Former_Client_Protection_Constraint",
    "Section_III_4b_Prohibition_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/170#Action_Completes_and_Terminates_Government_Retainer",
  "proeth:causesStateChange": "Engineer A transitions from \u0027current client\u0027 to \u0027former client\u0027 status for U.S. government; active loyalty obligations terminate but confidentiality and adverse-use prohibitions activate in their place; Engineer A is now technically free to accept new work but constrained in what that work may involve",
  "proeth:createsObligation": [
    "Maintain_Post_Engagement_Confidentiality",
    "Seek_Former_Client_Consent_Before_Adverse_Engagement",
    "Disclose_Prior_Relationship_If_Approached_Adversely"
  ],
  "proeth:description": "The professional relationship between Engineer A and the U.S. government formally terminates upon completion of the forensic work and full payment, but the ethical obligations arising from that relationship\u2014particularly regarding confidentiality and adverse use of specialized knowledge\u2014persist beyond termination.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After completion of forensic work and receipt of full payment; before contractor retention",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Government Engagement Concluded"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_Adverse_Retainer_Relationship_Formed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Engineer A may have genuinely believed that completing and being paid for the government work freed him to take any subsequent engagement. How should professional education address this gap between common assumption and ethical reality?",
    "The contractor presumably approached Engineer A precisely because of his prior government work. Does the contractor bear any ethical responsibility for knowingly soliciting a conflicted expert?",
    "If Engineer A recognized the conflict after accepting but before performing any adverse work, what would be the most ethically appropriate course of action, and would withdrawal alone be sufficient?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Potential professional confidence for Engineer A (unaware of or dismissive of ethical issue); concern or alarm if the conflict is recognized; betrayal if experienced from the government\u0027s perspective upon discovery; ethical discomfort for observers who recognize the violation",
  "proeth-scenario:ethicalImplications": "Reveals the tension between market freedom (engineers may contract with whom they choose) and professional loyalty (some relationships create lasting constraints on future contracting); exposes how the adversarial legal system can create perverse incentives to exploit former professional relationships; raises questions about whether consent-based exceptions are adequate protection or whether some conflicts should be non-waivable",
  "proeth-scenario:learningMoment": "This event demonstrates that an ethical violation is not merely a paperwork failure\u2014it has real consequences for real stakeholders. The moment of adverse retention crystallizes the conflict and shows students that the Code\u0027s prohibitions exist to protect identifiable parties from concrete harms.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Engagement with Engineer A is ethically tainted; legal proceedings may be affected if conflict is disclosed or challenged; potential for adverse rulings",
    "engineer_a": "Professional reputation at serious risk; potential disciplinary action by engineering board; engagement may need to be unwound; legal exposure possible",
    "engineering_profession": "Integrity of the expert witness role and forensic engineering practice called into question; public trust in engineers as neutral professionals undermined",
    "us_government": "Former trusted expert is now working against government interests using knowledge gained in confidence; legal strategy potentially compromised; trust in engineering profession damaged"
  },
  "proeth:activatesConstraint": [
    "Section_III_4b_Violation_Constraint",
    "Conflict_of_Interest_Active_Constraint",
    "Former_Client_Harm_Prevention_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/170#Action_Accepts_Contractor_Adverse_Retention",
  "proeth:causesStateChange": "Engineer A is now simultaneously a former government confidant and an active adverse expert against the government; an ethical violation under the 1981 Code is instantiated; the professional relationship with the contractor is ethically compromised from its inception",
  "proeth:createsObligation": [
    "Withdraw_From_Contractor_Engagement",
    "Notify_Relevant_Parties_of_Conflict",
    "Seek_Retroactive_Consent_or_Withdraw",
    "Self_Report_to_Professional_Body_if_Required"
  ],
  "proeth:description": "Upon Engineer A\u0027s acceptance of the contractor\u0027s retention, a new professional relationship is instantiated that places Engineer A in direct adversarial opposition to the U.S. government\u2014Engineer A\u0027s former client\u2014in the same matter for which specialized knowledge was acquired.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "At the moment Engineer A accepts the contractor\u0027s retention; after government engagement concluded",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Adverse Retainer Relationship Formed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#Event_Code_Violation_Instantiated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "The 1981 Code revision explicitly added Section III.4.b to address this type of situation. What does this legislative history tell us about the relationship between ethical cases and code development?",
    "Should the burden be on Engineer A to seek consent, or should the Code require former clients to affirmatively object within a specified period after being notified of a potential conflict?",
    "If Engineer A\u0027s specialized knowledge would actually help the contractor pursue a legitimate and meritorious claim, does the public interest in accurate adjudication create any tension with the conflict-of-interest prohibition?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Gravity and professional anxiety if Engineer A recognizes the violation; vindication for those who identified the conflict; institutional concern for the engineering profession\u0027s self-regulatory credibility; potential anger from government stakeholders upon learning of the adverse engagement",
  "proeth-scenario:ethicalImplications": "Reveals the dynamic relationship between case outcomes and code evolution; exposes the tension between individual professional freedom and systemic trust in professional institutions; raises the question of whether conflict-of-interest rules serve client protection, professional integrity, or both\u2014and whether those goals can ever conflict with each other or with justice",
  "proeth-scenario:learningMoment": "The Code of Ethics is not aspirational guidance\u2014it establishes enforceable professional standards with real consequences. The 1981 revision to add Section III.4.b was a deliberate policy choice to close a gap that Case 76-3 had identified under the prior code. Students should understand how professional codes evolve in response to identified ethical gaps.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Adverse engagement with Engineer A is ethically compromised; may need to retain different expert; legal proceedings potentially delayed or complicated",
    "engineer_a": "Subject to potential NSPE disciplinary proceedings; professional license at risk; financial consequences from required withdrawal; reputational damage in forensic engineering community",
    "engineering_profession": "NSPE ethical review process validated; Code\u0027s 1981 revision shown to have practical significance; precedent established for future conflict-of-interest cases",
    "us_government": "May seek to disqualify Engineer A from the adverse proceeding; legal strategy may need adjustment; potential grounds for challenging any work product Engineer A produced for the contractor"
  },
  "proeth:activatesConstraint": [
    "Professional_Disciplinary_Review_Constraint",
    "Remediation_Required_Constraint",
    "Disclosure_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/170#Action_Forgoes_Consent-Seeking_from_Former_Client",
  "proeth:causesStateChange": "Engineer A is in a state of ongoing Code violation; the ethical analysis by the NSPE Board of Ethical Review reaches a conclusion of impermissibility; the situation requires active remediation to restore ethical compliance",
  "proeth:createsObligation": [
    "Withdraw_From_Adverse_Engagement",
    "Disclose_Violation_If_Required",
    "Cease_Use_of_Former_Client_Knowledge_Adversely"
  ],
  "proeth:description": "The ethical violation of Section III.4.b of the 1981 NSPE Code of Ethics is fully instantiated as an outcome when Engineer A, having accepted the adverse contractor retention without government consent, is in an active state of representing interests adverse to a former client using specialized knowledge gained from that client.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Concurrent with and following the adverse retainer relationship formation; ongoing state",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Code Violation Instantiated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#CausalChain_951794f1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A dam failure occurs, creating the precipitating condition that requires forensic investigation and [engagement of Engineer A by the U.S. government]",
  "proeth:causalSequence": [
    {
      "proeth:description": "Structural dam failure creates an urgent need for forensic engineering investigation",
      "proeth:element": "Dam Failure Occurs (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A voluntarily agrees to serve the U.S. government as forensic investigator",
      "proeth:element": "Accepts Government Dam Retention (Action 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Formal professional and fiduciary relationship between Engineer A and the U.S. government comes into legal and ethical existence",
      "proeth:element": "Government Retainer Established (Event 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A accumulates privileged, client-specific knowledge about the dam failure through government-funded investigation",
      "proeth:element": "Specialized Knowledge Acquired (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Ongoing professional obligations to the government client are established, persisting beyond termination of the retainer",
      "proeth:element": "Duty of Loyalty and Confidentiality Attached",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Dam Failure Occurs (Event 1)",
  "proeth:counterfactual": "Without the dam failure, no forensic investigation would have been commissioned and no retainer relationship with Engineer A would have been established",
  "proeth:effect": "Government Retainer Established (Event 2)",
  "proeth:necessaryFactors": [
    "Dam failure as precipitating incident requiring investigation",
    "Government need for qualified forensic engineering expertise",
    "Engineer A\u0027s availability and relevant competence"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (Action 1: Accepts Government Dam Retention)",
  "proeth:sufficientFactors": [
    "Dam failure + government investigative mandate + Engineer A\u0027s qualifications together were sufficient to establish the retainer relationship"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#CausalChain_370ae3df",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Through the course of performing forensic analysis of the dam failure, Engineer A accumulates specialized [knowledge] \u2014 knowledge that is directly attributable to the government engagement",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A voluntarily enters the retainer, gaining authorized access to the dam failure investigation",
      "proeth:element": "Accepts Government Dam Retention (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Formal relationship grants Engineer A privileged investigative access and resources",
      "proeth:element": "Government Retainer Established (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A conducts detailed technical analysis of dam failure causes using government-provided access",
      "proeth:element": "Forensic Investigation Performed",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A accumulates unique, client-derived technical knowledge about the dam failure",
      "proeth:element": "Specialized Knowledge Acquired (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The specialized knowledge later becomes the very asset that makes Engineer A attractive to the contractor filing a claim against the government",
      "proeth:element": "Knowledge Becomes Instrumentally Valuable to Adverse Party",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accepts Government Dam Retention (Action 1)",
  "proeth:counterfactual": "Without accepting the government retention, Engineer A would not have had access to the privileged forensic data and would not have acquired the specialized knowledge that later created the conflict of interest",
  "proeth:effect": "Specialized Knowledge Acquired (Event 3)",
  "proeth:necessaryFactors": [
    "Existence of the government retainer granting Engineer A investigative access",
    "Engineer A\u0027s active performance of forensic analysis under that retainer",
    "Government-funded access to site data, records, and investigative resources"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Government retainer + active forensic investigation + privileged access to failure data together were sufficient to produce specialized, client-derived knowledge"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#CausalChain_0dc87bee",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A concludes the government investigation, accepts full payment, and allows the retainer relationship to terminate \u2014 formally ending the active engagement while leaving residual obligations intact",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A finalizes investigation deliverables and accepts full payment from the government",
      "proeth:element": "Completes and Terminates Government Retainer (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Active retainer relationship formally ends, but residual fiduciary obligations persist",
      "proeth:element": "Government Engagement Concluded (Event 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Termination of active retainer creates the practical opportunity for Engineer A to accept new clients",
      "proeth:element": "Engineer A Becomes Available for New Engagements",
      "proeth:step": 3
    },
    {
      "proeth:description": "The contractor, aware of Engineer A\u0027s specialized knowledge, seeks to retain him against the government",
      "proeth:element": "Contractor Identifies Engineer A as Valuable Adverse Expert",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A accepts the contractor\u0027s retention, leveraging government-derived knowledge against his former client",
      "proeth:element": "Accepts Contractor Adverse Retention (Action 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Completes and Terminates Government Retainer (Action 2)",
  "proeth:counterfactual": "Had Engineer A not completed the investigation or had the government extended the retainer, the formal termination would not have occurred and the subsequent adverse retention would have been an even more obvious conflict",
  "proeth:effect": "Government Engagement Concluded (Event 4)",
  "proeth:necessaryFactors": [
    "Completion of the forensic investigation deliverables",
    "Engineer A\u0027s acceptance of full payment (signaling mutual discharge of active duties)",
    "Absence of any contractual extension or renewal of the retainer"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Completion of work + acceptance of payment + no renewal together were sufficient to formally terminate the active retainer relationship"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#CausalChain_0050037b",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon Engineer A\u0027s acceptance of the contractor\u0027s retention, a new professional relationship is instantiated that is directly adverse to Engineer A\u0027s former client, the U.S. government",
  "proeth:causalSequence": [
    {
      "proeth:description": "Legal adversity between the contractor and Engineer A\u0027s former client is established",
      "proeth:element": "Contractor Files Claim Against U.S. Government",
      "proeth:step": 1
    },
    {
      "proeth:description": "Contractor seeks to leverage Engineer A\u0027s government-derived specialized knowledge",
      "proeth:element": "Contractor Solicits Engineer A",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A omits the affirmative step of seeking the government\u0027s informed consent before proceeding",
      "proeth:element": "Forgoes Consent-Seeking from Former Client (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A voluntarily accepts the retention, creating direct adversity to his former client",
      "proeth:element": "Accepts Contractor Adverse Retention (Action 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "New professional relationship adverse to the former government client is fully instantiated",
      "proeth:element": "Adverse Retainer Relationship Formed (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accepts Contractor Adverse Retention (Action 3)",
  "proeth:counterfactual": "Had Engineer A declined the contractor\u0027s retention, no adverse relationship would have formed and no Code violation would have been instantiated",
  "proeth:effect": "Adverse Retainer Relationship Formed (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s volitional acceptance of the contractor\u0027s offer of retention",
    "Existence of an active legal claim by the contractor against the U.S. government (Engineer A\u0027s former client)",
    "Engineer A\u0027s possession of specialized knowledge derived from the prior government engagement",
    "Absence of informed consent from the former government client"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Voluntary acceptance + adversity to former client + use of client-derived knowledge + no consent together were sufficient to instantiate both the adverse relationship and the ethical violation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#CausalChain_efe81a96",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The ethical violation of Section III.4.b of the 1981 NSPE Code of Ethics is fully instantiated as an operative breach \u2014 Engineer A proceeds to accept the contractor engagement without taking the affirmative step of seeking consent from his former client",
  "proeth:causalSequence": [
    {
      "proeth:description": "Section III.4.b explicitly prohibits accepting adverse engagements against former clients without consent, establishing the normative standard",
      "proeth:element": "1981 Code Revision Enacted (Event 7)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A\u0027s acceptance of the contractor retention creates direct adversity to the former government client",
      "proeth:element": "Adverse Retainer Relationship Formed (Event 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A omits the affirmative consent-seeking step required to cure the conflict under the Code",
      "proeth:element": "Forgoes Consent-Seeking from Former Client (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Former client relationship + adversity + specialized knowledge + no consent = complete violation",
      "proeth:element": "All Elements of Section III.4.b Violation Satisfied",
      "proeth:step": 4
    },
    {
      "proeth:description": "The ethical breach is fully constituted as an operative violation of professional engineering ethics",
      "proeth:element": "Code Violation Instantiated (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Forgoes Consent-Seeking from Former Client (Action 4)",
  "proeth:counterfactual": "Had Engineer A either declined the adverse retention OR sought and obtained the government\u0027s informed consent, the Code violation would not have been instantiated even under the 1981 Code",
  "proeth:effect": "Code Violation Instantiated (Event 6)",
  "proeth:necessaryFactors": [
    "Prior government client relationship creating ongoing duties",
    "Acceptance of adverse contractor retention (Action 3)",
    "Failure to seek or obtain informed consent from the former government client (Action 4)",
    "Existence of Section III.4.b of the 1981 NSPE Code as the applicable normative standard (Event 7)"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Adverse retention + former client relationship + no consent + applicable Code provision together were sufficient to constitute a complete ethical violation under Section III.4.b"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/170#",
    "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/170#CausalChain_9697c0f8",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The 1981 revision of the NSPE Code of Ethics introduces Section III.4.b, which explicitly prohibits [adverse engagements against former clients without consent] \u2014 making Engineer A\u0027s conduct a codified ethical violation rather than merely a matter of professional judgment",
  "proeth:causalSequence": [
    {
      "proeth:description": "NSPE enacts Section III.4.b, creating an explicit prohibition on adverse engagements against former clients without consent",
      "proeth:element": "1981 Code Revision Enacted (Event 7)",
      "proeth:step": 1
    },
    {
      "proeth:description": "The Code provision becomes the governing ethical standard against which Engineer A\u0027s subsequent decisions are measured",
      "proeth:element": "Normative Standard Applicable to Engineer A\u0027s Conduct",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A\u0027s volitional decisions bring his conduct squarely within the scope of the Section III.4.b prohibition",
      "proeth:element": "Accepts Contractor Adverse Retention (Action 3) + Forgoes Consent-Seeking (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Former client + adversity + no consent + applicable Code provision = complete ethical violation",
      "proeth:element": "All Violation Elements Satisfied",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s conduct is formally constituted as a violation of Section III.4.b of the 1981 NSPE Code of Ethics",
      "proeth:element": "Code Violation Instantiated (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "1981 Code Revision Enacted (Event 7)",
  "proeth:counterfactual": "Without the 1981 Code revision enacting Section III.4.b, Engineer A\u0027s conduct might have been criticized as professionally questionable but would not have constituted a codified violation of an explicit ethical rule; the Code revision is a necessary background condition for the formal violation",
  "proeth:effect": "Code Violation Instantiated (Event 6)",
  "proeth:necessaryFactors": [
    "Enactment of Section III.4.b as the applicable normative standard",
    "Engineer A\u0027s conduct falling within the scope of the prohibition",
    "Engineer A\u0027s status as a professional engineer subject to the Code"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); NSPE (institutional, for establishing the standard)",
  "proeth:sufficientFactors": [
    "The Code provision alone was not sufficient to produce a violation \u2014 it required Engineer A\u0027s non-compliant conduct; conversely, Engineer A\u0027s conduct alone might have been ethically questionable but not a codified violation without the Code provision"
  ],
  "proeth:withinAgentControl": true
}