{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Action_Accept_Initial_ABC_Retention",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the retention due to uncertainty about future conflicts in a specialized industry where the same parties may recur",
    "Accept the retention but formally document the limited scope of the engagement and notify ABC Manufacturing in writing that future adverse engagements are not precluded",
    "Accept the retention conditionally, requesting a conflicts waiver from ABC Manufacturing acknowledging she may work against them in unrelated matters in the future"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to apply her technical expertise in a legitimate professional capacity, earn compensation for specialized consulting work, and fulfill her role as an expert witness in a domain where she had relevant knowledge. There is no indication of improper motive \u2014 this was a routine professional engagement.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would have avoided any future conflict-of-interest appearance but would have cost Engineer A legitimate work and potentially stunted her reputation in patent litigation consulting \u2014 an overly cautious approach that the eventual Board ruling suggests was unnecessary.",
    "Formal documentation of limited scope would have created a clear record that the relationship was transactional and bounded, potentially making the later cross-examination attack much weaker and providing Engineer A with a strong paper defense.",
    "A prospective conflicts waiver would have been unusually forward-thinking for the time but would have most cleanly resolved the later controversy, effectively obtaining ABC Manufacturing\u0027s advance consent to future adverse work \u2014 though such waivers are more common in legal than engineering practice."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that the origin of a conflict-of-interest concern often lies in an entirely unremarkable first engagement. Students learn that routine professional decisions can have downstream ethical implications and that documenting the scope and nature of early engagements is critical for managing future conflicts.",
  "proeth-scenario:ethicalTension": "Professional autonomy to accept consulting work vs. the need to evaluate whether accepting any engagement with a party creates future constraints on independence; short-term financial and professional opportunity vs. long-term implications of establishing a client relationship.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s long-term professional independence and reputation; the precedent set for future engagements with the same party; the integrity of the patent litigation process; potential future awkwardness if the client relationship becomes relevant in subsequent matters.",
  "proeth:description": "Engineer A chose to accept retention by ABC Manufacturing to review documents and form an expert opinion in a patent litigation matter within her area of expertise. She performed the requested services and received payment.",
  "proeth:foreseenUnintendedEffects": [
    "Establishment of a prior professional relationship with ABC Manufacturing that could complicate future engagements",
    "Potential future perception of loyalty or partiality toward ABC Manufacturing"
  ],
  "proeth:fulfillsObligation": [
    "Competence: accepted work within her area of expertise (NSPE Code II.2)",
    "Faithful agent and trustee: performed services diligently for client ABC Manufacturing (NSPE Code II.4)",
    "Public safety and professional service: provided honest expert opinion in litigation context"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence",
    "Faithful agency to client",
    "Professional independence and objectivity in forensic engineering"
  ],
  "proeth:hasAgent": "Engineer A (Expert/Forensic Engineer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide competent expert review services in patent litigation within her area of expertise and fulfill the professional engagement",
  "proeth:requiresCapability": [
    "Expert knowledge in the relevant technical domain of patent litigation",
    "Document review and analysis",
    "Formation and articulation of expert opinion",
    "Understanding of forensic engineering standards and obligations"
  ],
  "proeth:temporalMarker": "Earliest event in timeline; exact date unspecified",
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Initial ABC Retention"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Action_Engineering_Profession_Shifts_Conflict_Standard",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Retain the strict avoidance standard but create a formal waiver process allowing engineers to seek advance approval for potentially conflicting engagements from a professional body",
    "Adopt a tiered conflict standard distinguishing between conflicts involving the same matter (prohibited) and conflicts involving the same party in unrelated matters (disclosure required but not prohibited)",
    "Defer to external legal standards for conflicts of interest rather than maintaining an independent professional standard, aligning engineering ethics with attorney conflict rules"
  ],
  "proeth-scenario:characterMotivation": "The engineering profession collectively recognized that the older standard \u2014 requiring engineers to avoid all conflicts of interest \u2014 was both practically unworkable in a specialized consulting marketplace and philosophically misaligned with the reality that conflicts are structural features of professional practice rather than aberrations. The profession sought a standard that preserved public trust while enabling engineers to sustain viable practices, shifting the ethical burden from avoidance to transparency.",
  "proeth-scenario:consequencesIfAlternative": [
    "A waiver process would have preserved the idealism of the avoidance standard while creating a practical safety valve, but would have created administrative burden and potentially inconsistent outcomes depending on which body reviewed waiver requests.",
    "A tiered standard would have provided clearer guidance for cases exactly like Engineer A\u0027s, explicitly distinguishing same-matter conflicts (which implicate confidentiality and loyalty) from same-party conflicts in unrelated matters (which implicate only appearance), and would have made the Board\u0027s eventual ruling more predictable.",
    "Deferring to legal standards would have created consistency between engineering and legal expert witness practice but would have surrendered the profession\u0027s independent ethical voice and potentially imported legal standards that were themselves contested or jurisdiction-specific."
  ],
  "proeth-scenario:decisionSignificance": "This action teaches students that ethics codes are not static moral truths but evolving professional consensus documents that reflect the profession\u0027s collective experience and practical wisdom. It also illustrates the difference between avoidance-based and disclosure-based ethical frameworks, and why the shift from one to the other represents a meaningful philosophical evolution rather than a mere relaxation of standards.",
  "proeth-scenario:ethicalTension": "The idealism of a zero-conflict standard that maximizes the appearance of impartiality vs. the pragmatic reality that strict avoidance would disproportionately burden specialists in narrow fields, effectively creating monopolies of access; the profession\u0027s duty to public trust vs. its duty to enable members to practice; collective standard-setting authority vs. individual engineer autonomy.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "The credibility and enforceability of professional ethics standards; the ability of engineering consultants to sustain practices in specialized fields; public trust in the impartiality of engineering expertise; the profession\u0027s self-regulatory authority and its relationship to external legal and judicial standards for expert witness conduct.",
  "proeth:description": "The engineering profession collectively decided to revise ethics codes to replace the requirement to avoid all conflicts of interest with a requirement to disclose known or potential conflicts of interest, acknowledging that conflicts are a practical inevitability in engineering practice.",
  "proeth:foreseenUnintendedEffects": [
    "Reduced clarity about what constitutes a prohibited conflict, requiring more individual judgment",
    "Potential for engineers to rationalize acceptance of engagements that create genuine conflicts under a disclosure framework",
    "Shift in professional image from one of strict conflict avoidance to one of managed conflict disclosure"
  ],
  "proeth:fulfillsObligation": [
    "Practical workability of professional ethics standards",
    "Preservation of engineer professional autonomy and independence",
    "Protection of clients through transparency and disclosure rather than rigid exclusion"
  ],
  "proeth:guidedByPrinciple": [
    "Professional autonomy and independence",
    "Transparency and disclosure as the mechanism for managing conflicts",
    "Pragmatic recognition of the realities of engineering practice",
    "Protection of public and client interests through informed consent rather than blanket prohibition"
  ],
  "proeth:hasAgent": "Engineering Profession Collectively (Professional Bodies and Code-Setting Authorities, including NSPE)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Strict conflict avoidance (image protection) vs. disclosure-based conflict management (autonomy and practicality)",
    "proeth:resolutionReasoning": "The profession concluded that conflicts of interest are a near-inevitable feature of engineering practice and that requiring absolute avoidance was both impractical and overly restrictive of professional autonomy; disclosure was adopted as a more appropriate and workable mechanism for protecting all parties"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Create a more practical and workable ethical standard that preserves engineer autonomy and independence while still protecting clients and the public through transparency and disclosure",
  "proeth:requiresCapability": [
    "Collective professional deliberation and ethics standard-setting",
    "Analysis of practical realities of engineering practice across diverse contexts",
    "Balancing of competing ethical principles at the profession-wide level",
    "Code drafting and promulgation authority"
  ],
  "proeth:temporalMarker": "Historical; occurred at an unspecified point prior to the events in the case",
  "proeth:violatesObligation": [
    "Prior commitment to absolute avoidance of all conflicts of interest",
    "Strict protection of professional image by eliminating any appearance of impropriety"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineering Profession Shifts Conflict Standard"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Action_Board_Rules_No_Prohibited_Conflict",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Find a technical violation based on the appearance of impropriety even if no specific code provision was clearly breached, prioritizing the profession\u0027s reputational interest over strict textual interpretation",
    "Find no violation but issue advisory guidance recommending that engineers in similar sequential engagement situations adopt best-practice disclosure protocols to preempt future cross-examination attacks",
    "Decline to rule on the merits, instead referring the matter to a broader ethics committee for development of more specific guidance on sequential and opposing engagements with the same party"
  ],
  "proeth-scenario:characterMotivation": "The NSPE Board sought to apply the current ethics code accurately to the facts presented, protect a member engineer from an unfounded ethics accusation, clarify the profession\u0027s standards for the benefit of all practitioners, and affirm that the shift to a disclosure-based conflict standard had substantive meaning \u2014 that it was not merely rhetorical but actually changed outcomes in cases like Engineer A\u0027s.",
  "proeth-scenario:consequencesIfAlternative": [
    "Finding a violation on appearance grounds alone would have been intellectually inconsistent with the profession\u0027s deliberate shift away from the avoidance standard, effectively reinstating the old standard through adjudication rather than code revision, and would have chilled legitimate consulting practice.",
    "A no-violation ruling with advisory guidance would have been the most constructive outcome for the profession, combining vindication of Engineer A with practical guidance for future practitioners \u2014 modeling the transparency-based approach the code now requires and helping engineers avoid the cross-examination vulnerability Engineer A experienced.",
    "Deferring to a broader committee would have delayed resolution and left Engineer A in professional limbo, but might have produced more comprehensive guidance addressing the full range of sequential engagement scenarios beyond the specific facts of this case."
  ],
  "proeth-scenario:decisionSignificance": "The resolution teaches students several critical lessons: (1) the appearance of impropriety is not equivalent to actual ethical violation; (2) ethics adjudication requires careful application of the specific standard in force, not general moral intuition; (3) professional ethics bodies serve a legitimizing function that can protect engineers from bad-faith attacks; and (4) the evolution of ethics codes has real consequences for how cases are decided.",
  "proeth-scenario:ethicalTension": "The Board\u0027s duty to enforce ethics standards rigorously vs. its duty to interpret them fairly and not overextend their reach; the interest in protecting Engineer A\u0027s professional reputation vs. the interest in maintaining robust conflict-of-interest norms that protect public trust; the appearance of impropriety (which opposing counsel exploited) vs. the actual ethical standard (which the Board found was not violated).",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Engineer A\u0027s professional standing and reputation; the precedential value of the ruling for all engineering consultants who work in specialized fields with recurring parties; the credibility of the NSPE ethics review process; the practical meaning of the profession\u0027s shift to a disclosure-based conflict standard.",
  "proeth:description": "The NSPE Board of Ethical Review deliberated on the facts and decided that Engineer A\u0027s sequential and opposing engagements with ABC Manufacturing did not constitute a prohibited conflict of interest under the NSPE Code of Ethics, affirming her professional autonomy to accept unrelated engagements regardless of prior adversarial history.",
  "proeth:foreseenUnintendedEffects": [
    "Potential concern that the ruling could be used to justify acceptance of engagements that create more genuine conflicts",
    "Risk that the ruling could be misread as endorsing a \u0027hired gun\u0027 approach to forensic engineering",
    "Clarification that may not fully resolve the appearance of impropriety concern acknowledged in the discussion"
  ],
  "proeth:fulfillsObligation": [
    "Providing authoritative ethical guidance to the engineering profession",
    "Protecting engineer professional autonomy and independence from unwarranted restrictions",
    "Correctly applying the modern NSPE Code standard (disclosure rather than absolute avoidance)",
    "Distinguishing engineering professional obligations from legal advocacy obligations"
  ],
  "proeth:guidedByPrinciple": [
    "Professional autonomy and independence of engineers",
    "Disclosure-based conflict of interest standard (modern NSPE Code)",
    "Engineers as objective experts, not advocates",
    "Faithful agency limited to active client relationships, not perpetual loyalty",
    "Individual engineer judgment and discretion in accepting engagements"
  ],
  "proeth:hasAgent": "NSPE Board of Ethical Review (Professional Ethics Adjudicatory Body)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional image protection vs. engineer autonomy and correct application of disclosure-based ethics standard",
    "proeth:resolutionReasoning": "The Board concluded that no actual prohibited conflict existed under the modern NSPE Code because the matters were entirely unrelated, engineers are not advocates, and perpetual absolute loyalty to former clients is neither required nor practical; the appearance concern was acknowledged but deemed insufficient to constitute an ethical violation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide authoritative ethical guidance clarifying that engineers do not owe perpetual absolute loyalty to former clients and that accepting unrelated engagements adverse to former clients does not violate the NSPE Code of Ethics",
  "proeth:requiresCapability": [
    "Authoritative interpretation of the NSPE Code of Ethics",
    "Analysis of conflict of interest principles in forensic engineering contexts",
    "Distinguishing engineering professional obligations from legal professional obligations",
    "Application of prior BER precedents to new fact patterns"
  ],
  "proeth:temporalMarker": "After the events described in the case; adjudicative decision",
  "proeth:withinCompetence": true,
  "rdfs:label": "Board Rules No Prohibited Conflict"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Action_Accept_Re-Retention_by_ABC",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the re-retention specifically because the prior adverse engagement creates an appearance problem that could compromise Engineer A\u0027s effectiveness as a witness and harm ABC Manufacturing\u0027s case",
    "Accept the re-retention but insist on a written acknowledgment from ABC Manufacturing that they are aware of the prior adverse engagement and affirmatively waive any conflict objection",
    "Accept the re-retention and proactively prepare a written disclosure for the court record documenting the full sequence of engagements, preempting the cross-examination attack with transparent self-disclosure"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to resume a professional relationship with a client who apparently trusted her expertise sufficiently to re-engage her despite her prior adverse work, demonstrating that ABC Manufacturing itself did not view the product liability engagement as a betrayal warranting permanent exclusion. Engineer A likely saw this as validation of her position that the engagements were genuinely independent and that her professional integrity was intact.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would have been professionally cautious and would have avoided the cross-examination attack entirely, but would have denied both Engineer A and ABC Manufacturing the benefit of a legitimate professional relationship \u2014 and the Board\u0027s eventual ruling suggests this caution was not ethically required.",
    "A written waiver from ABC Manufacturing would have created a strong record that the client with the most direct interest in objecting had affirmatively consented, substantially weakening opposing counsel\u0027s cross-examination narrative and demonstrating sophisticated conflict management.",
    "Proactive court disclosure would have transformed the cross-examination attack from a surprise impeachment into a non-issue already in the record, modeling the transparency-based approach to conflicts that the profession was moving toward and demonstrating that openness about engagement history is itself an ethical virtue."
  ],
  "proeth-scenario:decisionSignificance": "Students learn that the sequence of engagements \u2014 not just any individual engagement \u2014 is what creates the appearance of impropriety that opposing counsel can exploit at trial. This action demonstrates how an accumulation of individually defensible decisions can collectively create a narrative vulnerability, and why engineers in consulting roles must think longitudinally about how their engagement history will appear to skeptical third parties.",
  "proeth-scenario:ethicalTension": "The symmetrical nature of this re-retention creates a mirror-image tension to Action 2: just as working against a former client raised loyalty questions, returning to a client after working against them raises questions about whether Engineer A\u0027s prior adverse testimony was genuinely independent or strategically modulated. There is also tension between accepting legitimate work and the appearance of \u0027switching sides\u0027 that opposing counsel would later exploit.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s credibility as an expert witness in the current proceeding; ABC Manufacturing\u0027s litigation strategy if their own expert is impeached on cross-examination; the integrity of the judicial process if expert witness credibility is undermined by conflict appearances; Engineer A\u0027s broader reputation in the expert witness community where credibility is a primary professional asset.",
  "proeth:description": "Several years after working against ABC Manufacturing in the product liability case, Engineer A chose to accept re-retention by ABC Manufacturing for a new, unrelated patent litigation matter. This decision re-established a professional relationship with a party she had previously worked against.",
  "proeth:foreseenUnintendedEffects": [
    "Creating a three-engagement record of alternating loyalty (for ABC, against ABC, for ABC) that could be characterized as opportunistic or improper",
    "Exposure to cross-examination challenges implying impropriety based on the pattern of engagements",
    "Potential perception that Engineer A\u0027s opinions were for sale to whoever retained her"
  ],
  "proeth:fulfillsObligation": [
    "Professional autonomy and independence: exercised independent judgment to accept a legitimate engagement",
    "Competence: accepted work within her area of expertise",
    "Faithful agent and trustee: performed services for ABC Manufacturing in the new engagement (NSPE Code II.4)",
    "Disclosure obligation: presumed to have assessed and disclosed any potential conflicts"
  ],
  "proeth:guidedByPrinciple": [
    "Professional independence and autonomy",
    "Objectivity and non-advocacy in forensic engineering",
    "Disclosure of conflicts rather than absolute avoidance",
    "Individual engineer judgment and discretion in accepting engagements"
  ],
  "proeth:hasAgent": "Engineer A (Expert/Forensic Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Avoiding appearance of impropriety vs. professional autonomy and independence",
    "proeth:resolutionReasoning": "Engineer A determined that the new patent matter was entirely unrelated to prior engagements and that professional autonomy permitted acceptance; the Board affirmed no ethical violation occurred, though noted some reasonable persons might perceive a conflict"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide competent expert services to ABC Manufacturing in the new patent litigation matter, fulfilling the professional engagement",
  "proeth:requiresCapability": [
    "Expert technical knowledge in the relevant patent litigation domain",
    "Forensic engineering analysis and expert opinion formation",
    "Conflict of interest assessment across multiple prior engagements",
    "Credibility maintenance under cross-examination scrutiny",
    "Ability to maintain objectivity despite complex prior relationship history with client"
  ],
  "proeth:temporalMarker": "Several years after the plaintiff-side product liability engagement",
  "proeth:violatesObligation": [
    "Potential tension with residual professional relationship with Attorney X or the plaintiff from the prior adverse engagement, though no explicit violation identified by the Board"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Re-Retention by ABC"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Action_Accept_Adverse_Plaintiff_Retention",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the retention out of loyalty to ABC Manufacturing as a former client, treating the prior relationship as creating an ongoing duty of non-adversarial conduct",
    "Accept the retention but proactively disclose to Attorney X the existence and nature of the prior ABC engagement, and separately notify ABC Manufacturing of the potential adverse engagement and offer them the opportunity to object",
    "Accept the retention after conducting a formal self-assessment to confirm no confidential ABC information from the patent matter is relevant to the product liability case, and document that assessment in writing"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to continue practicing her expertise in product liability consulting, serve a new client with a legitimate legal need, and exercise her professional autonomy to work across different parties in her field. She likely assessed \u2014 correctly per the eventual ruling \u2014 that the product liability matter was substantively unrelated to the earlier patent work and that no confidential ABC information from the first engagement was implicated.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would have protected Engineer A from any appearance of impropriety but would have established a chilling precedent that a single engagement with a large manufacturer could permanently foreclose adverse work \u2014 an outcome the Board ultimately rejected as inconsistent with engineering professional norms.",
    "Proactive dual disclosure would have been the most ethically transparent path, potentially securing informed consent from both parties and insulating Engineer A from the later cross-examination attack. It would also have modeled the disclosure-based conflict standard the profession was moving toward.",
    "A documented self-assessment would have demonstrated good faith and professional rigor, providing a contemporaneous record that Engineer A actively considered the conflict question and concluded no protected information was at risk \u2014 strengthening her defense years later."
  ],
  "proeth-scenario:decisionSignificance": "This is the ethical crux of the case and the most teachable moment. Students must grapple with whether \u0027former client\u0027 status creates a permanent or semi-permanent loyalty obligation, and whether working adversely against a former client \u2014 in an unrelated matter, without using confidential information \u2014 constitutes a prohibited conflict of interest or simply the normal functioning of a consulting marketplace.",
  "proeth-scenario:ethicalTension": "Professional autonomy and the right to earn a living vs. loyalty and perceived fidelity to a former client; the engineer\u0027s duty to serve the public and the legal system with honest expert testimony vs. the appearance of inconsistency or opportunism when working against a former client; financial incentive vs. reputational risk.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional reputation with ABC Manufacturing and in the broader industry; the integrity of her expert testimony if confidential information from the first engagement were to bleed into the second; the plaintiff\u0027s right to qualified expert assistance; ABC Manufacturing\u0027s reasonable expectation that a former consultant would not be weaponized against them; the broader question of whether engineers can sustain independent consulting practices if former-client relationships permanently restrict future work.",
  "proeth:description": "Several years after working for ABC Manufacturing, Engineer A chose to accept retention by Attorney X, who represented a plaintiff in a product liability case against ABC Manufacturing \u2014 a matter unrelated to the earlier patent litigation. This decision placed Engineer A in a position adverse to her former client.",
  "proeth:foreseenUnintendedEffects": [
    "Taking a position adverse to the interests of a former client (ABC Manufacturing)",
    "Creating a record of having worked both for and against ABC Manufacturing, which could later be used to imply impropriety",
    "Potential perception of disloyalty or conflict of interest by ABC Manufacturing or future observers"
  ],
  "proeth:fulfillsObligation": [
    "Professional autonomy and independence: exercised independent judgment to accept a legitimate engagement",
    "Competence: accepted work within her area of professional expertise",
    "Disclosure obligation: presumed to have assessed and managed any potential conflict of interest through disclosure (modern NSPE standard)"
  ],
  "proeth:guidedByPrinciple": [
    "Professional independence and autonomy",
    "Objectivity in forensic engineering (engineers are not advocates)",
    "Disclosure of known or potential conflicts rather than absolute avoidance",
    "Faithful agency limited to active engagements, not perpetual loyalty to former clients"
  ],
  "proeth:hasAgent": "Engineer A (Expert/Forensic Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Duty of loyalty to former client vs. professional autonomy and independence",
    "proeth:resolutionReasoning": "Engineer A determined that because the product liability matter was entirely unrelated to the prior patent litigation work, no actual conflict of interest existed and professional autonomy permitted acceptance of the engagement; the Board affirmed this reasoning"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide competent expert services in the product liability matter on behalf of the plaintiff, fulfilling the new professional engagement",
  "proeth:requiresCapability": [
    "Expert technical knowledge applicable to the product liability matter",
    "Forensic engineering analysis and opinion formation",
    "Conflict of interest assessment and disclosure judgment",
    "Ability to maintain objectivity when working within the legal adversarial system"
  ],
  "proeth:temporalMarker": "Several years after the initial ABC Manufacturing engagement",
  "proeth:violatesObligation": [
    "Potential tension with duty of loyalty to former client ABC Manufacturing, though Board concluded this did not rise to a prohibited conflict given the unrelated subject matter"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Adverse Plaintiff Retention"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Event_Prior_Relationship_Exists_at_Adverse_Retention",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What criteria should Engineer A use to determine whether the product liability matter is genuinely \u0027unrelated\u0027 to the prior patent litigation work?",
    "Does the passage of \u0027several years\u0027 reduce or eliminate the ethical concerns arising from the prior relationship?",
    "Should Engineer A have proactively disclosed the prior ABC relationship to Attorney X before accepting the engagement, and what would proper disclosure look like?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A may feel confident the matters are unrelated and proceed without alarm; Attorney X may be unaware of the prior relationship; ABC Manufacturing, if aware, would likely feel a sense of betrayal or concern about confidential information exposure",
  "proeth-scenario:ethicalImplications": "Exposes the tension between an expert\u0027s economic interest in accepting available work and the duty of loyalty and confidentiality to former clients; raises questions about whether temporal distance can substitute for substantive unrelatedness in conflict analysis",
  "proeth-scenario:learningMoment": "The mere existence of a prior relationship with an adverse party is not automatically disqualifying, but it activates specific obligations of disclosure and assessment. Students should understand that \u0027unrelated matter\u0027 is a critical ethical distinction that must be evaluated carefully, not assumed.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "abc_manufacturing": "Potentially exposed to an expert who holds confidential information from prior engagement; trust violated if confidential information is used adversely",
    "attorney_x": "Needs to know about prior relationship to assess whether retained expert is ethically available",
    "engineer_a": "Professional credibility contingent on whether the \u0027unrelated matter\u0027 characterization is accurate and defensible; risk of later cross-examination implications",
    "engineering_profession": "Integrity of expert witness practice depends on clear conflict-of-interest standards",
    "plaintiff": "Benefits from Engineer A\u0027s expertise but has interest in ensuring expert is not compromised"
  },
  "proeth:activatesConstraint": [
    "Conflict_Of_Interest_Disclosure_Constraint",
    "Prior_Confidential_Information_Protection_Constraint",
    "Loyalty_Obligation_Assessment_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/179#Action_Accept_Adverse_Plaintiff_Retention",
  "proeth:causesStateChange": "Engineer A now occupies an adversarial position relative to a former client; the \u0027unrelated matter\u0027 characterization becomes ethically load-bearing; the conflict of interest question is activated and must be resolved",
  "proeth:createsObligation": [
    "Assess_Whether_Prior_Confidential_Info_Is_Relevant",
    "Disclose_Prior_ABC_Relationship_To_Attorney_X",
    "Obtain_Informed_Consent_Or_Decline_If_Conflict_Exists",
    "Ensure_New_Work_Is_Genuinely_Unrelated_To_Prior_Work"
  ],
  "proeth:description": "At the moment Engineer A accepted retention by Attorney X against ABC Manufacturing, a prior professional relationship with ABC Manufacturing already existed as an established fact, creating a potential conflict of interest condition.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Beginning of second engagement (Engagement 2) \u2014 several years after Engagement 1",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Prior Relationship Exists at Adverse Retention"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Event_Impropriety_Implied_by_Counsel",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is there a meaningful ethical difference between actually committing an impropriety and merely creating the appearance of one? Should engineers be held to an \u0027appearance standard\u0027?",
    "How should Engineer A respond under oath to the implication of impropriety \u2014 what can she say to defend her conduct without violating confidentiality obligations to prior clients?",
    "Does opposing counsel\u0027s tactic of implying impropriety without proving it raise its own ethical concerns under legal professional responsibility rules?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences stress, embarrassment, and indignation at the implication of impropriety; ABC Manufacturing\u0027s counsel may feel defensive; the judge and jury form impressions of Engineer A\u0027s credibility; opposing counsel feels tactically advantaged",
  "proeth-scenario:ethicalImplications": "Reveals the tension between the legal system\u0027s adversarial use of professional history and the engineering profession\u0027s substantive ethics standards; exposes how the \u0027appearance of impropriety\u0027 standard can conflict with the \u0027actual conflict\u0027 standard; raises questions about whether expert witnesses owe duties to the court that supersede loyalty to retaining counsel",
  "proeth-scenario:learningMoment": "Even ethically permissible conduct can be weaponized in adversarial proceedings. Engineers serving as expert witnesses must anticipate that their full engagement history will be scrutinized and must be prepared to articulate the ethical basis for each engagement decision. Appearance of impropriety can cause real harm even absent actual impropriety.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "abc_manufacturing": "Their retained expert\u0027s credibility is undermined, potentially weakening their litigation position",
    "attorney_x_and_plaintiff": "Opposing party may benefit from the implication of impropriety regardless of its ultimate validity",
    "court_and_jury": "Must assess whether Engineer A\u0027s testimony is tainted by the implied impropriety",
    "engineer_a": "Credibility as expert witness damaged in the moment; professional reputation at stake; may face ethics inquiry; future retention opportunities potentially affected",
    "engineering_profession": "Public perception of expert witness integrity is implicated; demonstrates need for clear conflict-of-interest standards"
  },
  "proeth:activatesConstraint": [
    "Professional_Reputation_Defense_Constraint",
    "Truthful_Testimony_Constraint",
    "Ethics_Code_Compliance_Verification_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/179#Action_Accept_Re-Retention_by_ABC",
  "proeth:causesStateChange": "Engineer A\u0027s professional conduct is now a matter of public record in litigation; her credibility as an expert witness is directly challenged; the ethical propriety of her prior engagement decisions is thrust into scrutiny",
  "proeth:createsObligation": [
    "Engineer_A_Must_Respond_Truthfully_To_Cross_Examination",
    "Retaining_Counsel_Must_Rehabilitate_Witness_If_Possible",
    "Ethics_Board_Review_May_Be_Warranted",
    "Document_Basis_For_Prior_Engagement_Decisions"
  ],
  "proeth:description": "During cross-examination in the third engagement, opposing counsel publicly implied that Engineer A had acted improperly by having previously worked both for and against ABC Manufacturing, casting doubt on her professional integrity before the court.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "During cross-examination in Engagement 3 (third engagement with ABC Manufacturing)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Impropriety Implied by Counsel"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Event_Ethics_Code_Evolution_Recognized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should engineers be held to the strictest historical version of a standard, the version in effect at the time of their conduct, or the current version? What are the fairness implications of each approach?",
    "Does the evolution of ethics codes toward more permissive conflict standards reflect genuine ethical progress, or does it represent the profession accommodating commercial pressures at the expense of client protection?",
    "How should an engineer stay current with evolving professional ethics standards, and what responsibility do professional bodies have to communicate changes clearly?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Provides relief and vindication for Engineer A; may frustrate opposing counsel whose implied impropriety argument loses its normative foundation; creates a sense of historical perspective for ethics adjudicators",
  "proeth-scenario:ethicalImplications": "Reveals that professional ethics is a living system subject to revision, not a fixed set of eternal rules; raises questions about the legitimacy of retroactive application of evolved standards; exposes the tension between client protection (favoring strict loyalty rules) and expert availability and market efficiency (favoring matter-specific analysis)",
  "proeth-scenario:learningMoment": "Ethics codes are not static \u2014 they evolve as the profession matures and as practice contexts change. Students must understand that the applicable standard is the one in effect at the time of the conduct, and that historical evolution of standards can be determinative in ethics adjudication. The shift from absolute loyalty to matter-specific conflict analysis reflects a more sophisticated understanding of expert practice.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "abc_manufacturing": "Benefits from the evolved standard insofar as their retained expert is vindicated",
    "engineer_a": "Conduct is evaluated under a more permissive standard that recognizes matter-specific analysis; likelihood of ethical violation finding decreases",
    "engineering_profession": "Evolution of standards signals maturation of the profession\u0027s understanding of expert practice; creates precedent for future similar cases",
    "ethics_adjudicatory_bodies": "Must apply historically appropriate standards, adding complexity to retrospective review",
    "future_expert_witnesses": "Gain clarity about the operative conflict-of-interest standard; can structure engagements accordingly"
  },
  "proeth:activatesConstraint": [
    "Applicable_Code_Version_Determination_Constraint",
    "Retroactive_Standard_Application_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/179#Action_Engineering_Profession_Shifts_Conflict_Standard",
  "proeth:causesStateChange": "The evaluative framework for assessing Engineer A\u0027s conduct shifts from an absolute loyalty model to a matter-specific conflict model; conduct that might have been impermissible under older standards may be permissible under evolved standards",
  "proeth:createsObligation": [
    "Ethics_Board_Must_Apply_Code_Version_In_Effect_At_Time_Of_Conduct",
    "Adjudicators_Must_Recognize_Historical_Context_Of_Standards"
  ],
  "proeth:description": "The historical shift in engineering ethics codes \u2014 from stricter loyalty-based conflict standards to more nuanced, matter-specific conflict analysis \u2014 is recognized as an established fact contextualizing Engineer A\u0027s conduct across her three engagements.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Spanning the period of all three engagements; formally recognized in the Discussion section of the ethics opinion",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Ethics Code Evolution Recognized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Event_No_Violation_Finding_Issued",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "The Board found no violation, but does that mean Engineer A\u0027s conduct was beyond ethical criticism? Is there a difference between \u0027not a violation\u0027 and \u0027best practice\u0027?",
    "What would have changed the outcome of the Board\u0027s analysis \u2014 i.e., under what circumstances would working both for and against the same company constitute an ethical violation?",
    "Should the formal ethics opinion be admissible or relevant in the underlying litigation where opposing counsel raised the impropriety implication? Why or why not?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Relief and vindication for Engineer A; satisfaction for ABC Manufacturing whose confidence in their expert is restored; possible frustration for opposing counsel whose cross-examination tactic is formally rebutted; reassurance for the engineering profession that the ethics system functions",
  "proeth-scenario:ethicalImplications": "Demonstrates that ethics adjudication requires contextual, fact-specific analysis rather than categorical rules; validates the profession\u0027s evolution toward nuanced conflict standards while preserving the core prohibition on using confidential information adversely; raises questions about the relationship between legal adversarial tactics and professional ethics standards",
  "proeth-scenario:learningMoment": "Formal ethics adjudication serves an important function beyond individual cases \u2014 it generates precedent and guidance for the profession. Students should understand that the outcome here turned on two critical factual and legal determinations: (1) the matters were genuinely unrelated, and (2) the evolved standard permits matter-specific conflict analysis. Change either factor and the outcome could differ.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "abc_manufacturing": "Retained expert validated; litigation position strengthened to the extent expert credibility was at issue",
    "engineer_a": "Professional reputation restored; expert witness career can continue without the cloud of implied impropriety; gains a formal ethics opinion supporting her conduct",
    "engineering_profession": "Receives authoritative guidance on conflict-of-interest standards for expert witnesses; precedent clarifies permissible practice",
    "future_expert_witnesses": "Gain a roadmap for navigating sequential engagements on both sides of disputes; understand the \u0027unrelated matter\u0027 standard is determinative",
    "legal_system": "Expert witness pool benefits from clarity; courts can rely on engineers who have served multiple parties in unrelated matters without presuming impropriety"
  },
  "proeth:activatesConstraint": [
    "Precedent_Setting_Constraint",
    "Professional_Guidance_Dissemination_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/179#Action_Board_Rules_No_Prohibited_Conflict",
  "proeth:causesStateChange": "Engineer A is formally cleared of ethical wrongdoing; the implied impropriety from cross-examination is officially rebutted; a precedent is established for similar future cases; the matter-specific conflict analysis is validated as the operative standard",
  "proeth:createsObligation": [
    "Publish_Ethics_Opinion_For_Professional_Guidance",
    "Engineer_A_May_Continue_Expert_Practice_Without_Restriction",
    "Profession_Must_Communicate_Applicable_Conflict_Standards_Clearly"
  ],
  "proeth:description": "The NSPE Board of Ethical Review formally concluded that Engineer A committed no ethical violation, establishing an authoritative ruling that her sequential engagements for and against ABC Manufacturing were permissible under applicable professional standards.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Conclusion of NSPE ethics review process (post all three engagements)",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "No Violation Finding Issued"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#Event_Initial_Payment_Received",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What confidentiality obligations persist after an expert engagement concludes, and how long do they last?",
    "Should Engineer A have anticipated that working for ABC Manufacturing might complicate future engagements? Is such foresight required?",
    "How does the creation of a prior professional relationship affect an expert\u0027s marketability versus their ethical constraints?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral and professional for Engineer A \u2014 routine conclusion of an engagement; no anticipation of future complications; ABC Manufacturing satisfied with services rendered",
  "proeth-scenario:ethicalImplications": "Reveals the tension between an expert\u0027s right to build a diverse practice and the lasting confidentiality and loyalty obligations created by prior engagements; raises questions about when a professional relationship truly ends",
  "proeth-scenario:learningMoment": "Even routine, completed engagements create lasting professional obligations \u2014 particularly confidentiality \u2014 that constrain future conduct and must be disclosed. Students should recognize that professional relationships do not simply \u0027end\u0027 upon payment.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "abc_manufacturing": "Receives completed patent litigation review; develops trust in Engineer A\u0027s expertise",
    "engineer_a": "Establishes professional credibility with ABC Manufacturing; begins accumulating confidential knowledge of ABC\u0027s litigation posture",
    "engineering_profession": "No immediate consequence; routine expert engagement",
    "future_adverse_parties": "Unaware that Engineer A now holds confidential information potentially relevant to future disputes"
  },
  "proeth:activatesConstraint": [
    "Prior_Relationship_Disclosure_Constraint",
    "Confidentiality_Obligation_To_ABC"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/179#Action_Accept_Initial_ABC_Retention",
  "proeth:causesStateChange": "Engineer A transitions from active engagement to post-engagement status with ABC; a professional history record is established; confidentiality obligations persist indefinitely",
  "proeth:createsObligation": [
    "Maintain_Confidentiality_Of_ABC_Information",
    "Disclose_Prior_Relationship_In_Future_Engagements"
  ],
  "proeth:description": "Engineer A received payment from ABC Manufacturing upon completion of the first patent litigation review engagement, formalizing the prior professional relationship and creating a record of service.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "End of first engagement (Engagement 1)",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Initial Payment Received"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#CausalChain_cc67a031",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "At the moment Engineer A accepted retention by Attorney X against ABC Manufacturing, a prior professional relationship existed \u2014 one that was created by Engineer A\u0027s original decision to accept retention by ABC Manufacturing.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A voluntarily accepts engagement with ABC Manufacturing for patent litigation document review",
      "proeth:element": "Accept Initial ABC Retention",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A completes work and receives payment, formalizing and concluding the professional relationship",
      "proeth:element": "Initial Payment Received",
      "proeth:step": 2
    },
    {
      "proeth:description": "The completed professional relationship persists as a historical fact at the moment Engineer A is approached for adverse retention",
      "proeth:element": "Prior Relationship Exists at Adverse Retention",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A accepts retention against ABC Manufacturing, activating the latent conflict created in Step 1",
      "proeth:element": "Accept Adverse Plaintiff Retention",
      "proeth:step": 4
    },
    {
      "proeth:description": "Opposing counsel exploits the prior relationship during cross-examination to imply bias or impropriety",
      "proeth:element": "Impropriety Implied by Counsel",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Initial ABC Retention",
  "proeth:counterfactual": "Had Engineer A declined the initial ABC retention, no prior professional relationship would have existed at the time of the adverse retention, and the conflict-of-interest question would not have arisen",
  "proeth:effect": "Prior Relationship Exists at Adverse Retention",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s volitional acceptance of the initial ABC engagement",
    "Completion of paid professional services creating a professional relationship",
    "Temporal persistence of that relationship into future engagements"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Acceptance of retention + completion of work + receipt of payment = established prior professional relationship"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#CausalChain_39103c75",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "During cross-examination in the third engagement, opposing counsel publicly implied that Engineer A had acted improperly \u2014 a line of attack made possible only because Engineer A had chosen to accept retention adverse to a former client.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A carries an established professional history with ABC Manufacturing into the new engagement",
      "proeth:element": "Prior Relationship Exists at Adverse Retention",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A accepts retention by Attorney X to work against ABC Manufacturing, creating the switching-sides factual predicate",
      "proeth:element": "Accept Adverse Plaintiff Retention",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A later accepts re-retention by ABC, completing a pattern of sequential adverse engagements visible to all parties",
      "proeth:element": "Accept Re-Retention by ABC",
      "proeth:step": 3
    },
    {
      "proeth:description": "Opposing counsel uses the full sequential pattern during cross-examination to publicly imply Engineer A\u0027s testimony is compromised by mercenary switching of sides",
      "proeth:element": "Impropriety Implied by Counsel",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Accept Adverse Plaintiff Retention",
  "proeth:counterfactual": "Had Engineer A declined the adverse retention, opposing counsel would have had no factual basis to imply switching-sides impropriety during cross-examination",
  "proeth:effect": "Impropriety Implied by Counsel",
  "proeth:necessaryFactors": [
    "Existence of a prior professional relationship with ABC Manufacturing",
    "Engineer A\u0027s decision to accept an adverse role against ABC Manufacturing",
    "Opposing counsel\u0027s awareness of the sequential relationship history",
    "A litigation context enabling cross-examination"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); Opposing Counsel (proximate actor)",
  "proeth:sufficientFactors": [
    "Prior relationship + adverse acceptance + litigation forum = sufficient basis for opposing counsel to raise impropriety publicly"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#CausalChain_2987e2bb",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The completed three-engagement sequential pattern \u2014 working for ABC, then against ABC, then for ABC again \u2014 provided opposing counsel the factual predicate to imply during cross-examination that Engineer A\u0027s loyalty and objectivity were for sale.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A establishes initial professional relationship with ABC Manufacturing",
      "proeth:element": "Accept Initial ABC Retention",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A works against ABC, creating first directional switch",
      "proeth:element": "Accept Adverse Plaintiff Retention",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A returns to work for ABC, completing a full adverse cycle and establishing a mercenary-switching appearance",
      "proeth:element": "Accept Re-Retention by ABC",
      "proeth:step": 3
    },
    {
      "proeth:description": "The completed pattern is weaponized during cross-examination to undermine Engineer A\u0027s credibility and imply ethical misconduct",
      "proeth:element": "Impropriety Implied by Counsel",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Accept Re-Retention by ABC",
  "proeth:counterfactual": "Had Engineer A declined re-retention by ABC, the switching pattern would have been incomplete and the cross-examination attack on credibility would have been substantially weaker or unavailable",
  "proeth:effect": "Impropriety Implied by Counsel",
  "proeth:necessaryFactors": [
    "Completion of all three sequential engagements creating a visible pattern",
    "Engineer A\u0027s volitional acceptance of re-retention by ABC after adverse work",
    "A litigation forum in which the pattern could be exposed"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Three-phase switching pattern + litigation context = sufficient for credible public impropriety allegation by opposing counsel"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#CausalChain_0518aab7",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The historical shift in engineering ethics codes \u2014 from stricter loyalty-based conflict standards to disclosure-based standards \u2014 provided the normative framework within which the NSPE Board evaluated Engineer A\u0027s conduct and formally concluded that no ethical violation had been committed.",
  "proeth:causalSequence": [
    {
      "proeth:description": "The profession collectively revises ethics codes to replace strict conflict prohibitions with disclosure-based requirements",
      "proeth:element": "Engineering Profession Shifts Conflict Standard",
      "proeth:step": 1
    },
    {
      "proeth:description": "The historical shift becomes a recognized normative fact that frames how subsequent conduct is evaluated",
      "proeth:element": "Ethics Code Evolution Recognized",
      "proeth:step": 2
    },
    {
      "proeth:description": "NSPE Board deliberates applying the revised standard and finds Engineer A\u0027s conduct permissible under disclosure-based rules",
      "proeth:element": "Board Rules No Prohibited Conflict",
      "proeth:step": 3
    },
    {
      "proeth:description": "The Board formally issues a finding of no ethical violation, providing institutional legitimation of Engineer A\u0027s sequential engagements",
      "proeth:element": "No Violation Finding Issued",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Engineering Profession Shifts Conflict Standard",
  "proeth:counterfactual": "Had the profession retained the stricter loyalty-based conflict standard, Engineer A\u0027s sequential adverse engagements would likely have constituted a clear violation, and the Board\u0027s finding would have been different",
  "proeth:effect": "No Violation Finding Issued",
  "proeth:necessaryFactors": [
    "The profession\u0027s collective decision to revise ethics codes replacing prohibition with disclosure requirements",
    "The revised standard being in effect at the time of the NSPE Board\u0027s deliberation",
    "Engineer A\u0027s conduct being evaluated against the current rather than historical standard"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineering Profession Collectively (NSPE and member organizations); NSPE Board of Ethical Review (applying the standard)",
  "proeth:sufficientFactors": [
    "Revised disclosure-based ethics standard + Engineer A\u0027s conduct not violating disclosure requirements = sufficient basis for no-violation finding"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/179#",
    "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/179#CausalChain_66265379",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The NSPE Board of Ethical Review deliberated on the facts and decided that Engineer A\u0027s sequential adverse engagements did not constitute a prohibited conflict of interest under the applicable ethics code, directly producing the formal no-violation conclusion.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Cross-examination attack on Engineer A\u0027s credibility creates the reputational harm that motivates or contextualizes the ethics review",
      "proeth:element": "Impropriety Implied by Counsel",
      "proeth:step": 1
    },
    {
      "proeth:description": "The Board situates Engineer A\u0027s conduct within the historical shift from strict to disclosure-based conflict standards",
      "proeth:element": "Ethics Code Evolution Recognized",
      "proeth:step": 2
    },
    {
      "proeth:description": "After deliberation, the Board determines the conduct does not violate the applicable disclosure-based ethics standard",
      "proeth:element": "Board Rules No Prohibited Conflict",
      "proeth:step": 3
    },
    {
      "proeth:description": "The formal finding is issued, providing institutional resolution of the ethical question raised by the sequential engagements",
      "proeth:element": "No Violation Finding Issued",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Board Rules No Prohibited Conflict",
  "proeth:counterfactual": "Had the Board ruled that a prohibited conflict existed \u2014 either by applying a stricter standard or finding disclosure requirements were not met \u2014 no no-violation finding would have been issued, and Engineer A\u0027s professional standing would have been formally damaged",
  "proeth:effect": "No Violation Finding Issued",
  "proeth:necessaryFactors": [
    "NSPE Board\u0027s jurisdiction and authority to issue ethical findings",
    "The Board\u0027s deliberative decision to apply the disclosure-based standard rather than a stricter one",
    "The factual record of Engineer A\u0027s engagements being presented to the Board",
    "The revised ethics code providing a permissive framework for the conduct at issue"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "NSPE Board of Ethical Review",
  "proeth:sufficientFactors": [
    "Board authority + revised permissive standard + Engineer A\u0027s conduct not violating disclosure requirements = sufficient for formal no-violation finding"
  ],
  "proeth:withinAgentControl": true
}