PASS 3: Temporal Dynamics
Case 172: Objectivity of Engineer Retained as Expert
Timeline Overview
OWL-Time Temporal Structure 14 relations time: = w3.org/2006/time
Extracted Actions (5)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A agrees to be retained by Attorney Z as a forensic engineering consultant to provide an engineering and safety analysis report and courtroom testimony in support of the plaintiff in a personal injury case.
Temporal Marker: Initial engagement, before case review begins
Mental State: deliberate
Intended Outcome: Provide professional forensic engineering services, including analysis and expert testimony, in exchange for a fee
Fulfills Obligations:
- Legitimate acceptance of professional engagement within area of competence
- Willingness to apply objective engineering judgment to litigation support
Guided By Principles:
- Engineers may provide forensic consulting services as legitimate professional practice
- Objective engineering analysis in service of the legal process
- Professional competence in forensic engineering
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A seeks legitimate professional work as a forensic consultant, applying his engineering expertise in the legal arena for compensation. He likely views the retention as a standard professional engagement with no foreseeable ethical complications at the outset.
Ethical Tension: Serving a paying client's litigation interests vs. maintaining an independent, objective engineering judgment — the adversarial legal context pressures experts toward advocacy, while engineering ethics demand impartiality and honesty above client preference.
Learning Significance: Establishes that accepting forensic retention is not inherently unethical, but it creates confidentiality obligations and a knowledge relationship with the retaining attorney that will constrain all future conduct in the same matter. Students learn that every professional engagement has downstream ethical consequences.
Stakes: Engineer A's professional independence and future flexibility are immediately encumbered. The plaintiff's confidential litigation strategy, documents, and internal case assessments are now entrusted to Engineer A. A breach of that trust — even an inadvertent one — could harm the plaintiff, undermine the justice system, and damage Engineer A's reputation and licensure.
Decision Point: Yes - Story can branch here
- Decline the retention due to a pre-existing relationship with the defendant or defendant's counsel
- Accept with an explicit written agreement clarifying confidentiality obligations and conflict-of-interest protocols
- Accept but immediately disclose any prior knowledge of the incident or parties that could compromise independence
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Action_Accept_Plaintiff_Forensic_Retention",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the retention due to a pre-existing relationship with the defendant or defendant\u0027s counsel",
"Accept with an explicit written agreement clarifying confidentiality obligations and conflict-of-interest protocols",
"Accept but immediately disclose any prior knowledge of the incident or parties that could compromise independence"
],
"proeth-scenario:characterMotivation": "Engineer A seeks legitimate professional work as a forensic consultant, applying his engineering expertise in the legal arena for compensation. He likely views the retention as a standard professional engagement with no foreseeable ethical complications at the outset.",
"proeth-scenario:consequencesIfAlternative": [
"Declining removes Engineer A from the case entirely, avoiding all downstream conflicts but forgoing legitimate work; another qualified engineer would be retained instead.",
"An explicit written confidentiality and conflict agreement would not prevent the later conflict but would make Engineer A\u0027s obligations legally and ethically unambiguous, potentially causing him to self-screen more carefully when Attorney X later approaches him.",
"Proactive disclosure of prior knowledge would demonstrate good faith, build trust with Attorney Z, and establish a pattern of transparency that might have led Engineer A to self-disclose the conflict when Attorney X contacted him."
],
"proeth-scenario:decisionSignificance": "Establishes that accepting forensic retention is not inherently unethical, but it creates confidentiality obligations and a knowledge relationship with the retaining attorney that will constrain all future conduct in the same matter. Students learn that every professional engagement has downstream ethical consequences.",
"proeth-scenario:ethicalTension": "Serving a paying client\u0027s litigation interests vs. maintaining an independent, objective engineering judgment \u2014 the adversarial legal context pressures experts toward advocacy, while engineering ethics demand impartiality and honesty above client preference.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "Engineer A\u0027s professional independence and future flexibility are immediately encumbered. The plaintiff\u0027s confidential litigation strategy, documents, and internal case assessments are now entrusted to Engineer A. A breach of that trust \u2014 even an inadvertent one \u2014 could harm the plaintiff, undermine the justice system, and damage Engineer A\u0027s reputation and licensure.",
"proeth:description": "Engineer A agrees to be retained by Attorney Z as a forensic engineering consultant to provide an engineering and safety analysis report and courtroom testimony in support of the plaintiff in a personal injury case.",
"proeth:foreseenUnintendedEffects": [
"Access to confidential plaintiff documents and information that would create residual obligations",
"Potential future conflict if analysis results did not support the retaining party"
],
"proeth:fulfillsObligation": [
"Legitimate acceptance of professional engagement within area of competence",
"Willingness to apply objective engineering judgment to litigation support"
],
"proeth:guidedByPrinciple": [
"Engineers may provide forensic consulting services as legitimate professional practice",
"Objective engineering analysis in service of the legal process",
"Professional competence in forensic engineering"
],
"proeth:hasAgent": "Engineer A (Forensic Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client advocacy vs. engineering objectivity",
"proeth:resolutionReasoning": "At the point of acceptance this action was ethically sound; Engineer A accepted with the implicit understanding that his conclusions would be governed by objective analysis, not client preference"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Provide professional forensic engineering services, including analysis and expert testimony, in exchange for a fee",
"proeth:requiresCapability": [
"Forensic engineering analysis",
"Safety analysis",
"Expert witness testimony",
"Technical report writing"
],
"proeth:temporalMarker": "Initial engagement, before case review begins",
"proeth:withinCompetence": true,
"rdfs:label": "Accept Plaintiff Forensic Retention"
}
Description: Following his review and analysis, Engineer A determines he cannot produce an engineering and safety analysis report favorable to the plaintiff because his honest findings indicate the plaintiff, not the defendant, was at fault.
Temporal Marker: After completion of review and analysis, prior to termination
Mental State: deliberate
Intended Outcome: Uphold professional integrity by refusing to issue a report whose conclusions would misrepresent his honest engineering findings
Fulfills Obligations:
- Duty to issue objective and truthful engineering reports (NSPE Code II.3.a.)
- Duty to avoid acting as a 'hired gun' biased toward the paying client
- Duty to hold public safety paramount by accurately identifying the at-fault party
- Duty of honesty and integrity in professional practice
Guided By Principles:
- Forensic engineers must 'call them as they see them'
- Engineering objectivity supersedes client financial interest
- Public safety and truthful analysis are paramount professional obligations
- Engineers shall not misrepresent engineering facts or conditions
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A is committed to honest, objective engineering analysis. His professional integrity and adherence to the canon that engineers shall be objective and truthful compel him to report his findings accurately even when they are adverse to the client who retained him. He may also fear liability or reputational harm from producing a dishonest report.
Ethical Tension: Loyalty and gratitude to the retaining client (Attorney Z) vs. the overriding engineering obligation to provide truthful, objective findings regardless of who is paying. The financial relationship and implicit expectation of a favorable report create pressure to shade conclusions, while professional codes and personal integrity push toward honest reporting.
Learning Significance: This action is the ethical high point of Engineer A's conduct in the case and a critical teaching moment: forensic engineers owe their primary duty to truth and the court, not to the retaining party. Declining to produce a favorable report when the evidence does not support it is the correct and courageous professional choice. Students should recognize this as the standard all forensic engineers must meet.
Stakes: If Engineer A produces a dishonest favorable report, he risks perjury, professional discipline, loss of licensure, and public harm. By refusing, he preserves his integrity but triggers termination, which then sets the stage for the subsequent ethical failure when he accepts the opposing engagement.
Decision Point: Yes - Story can branch here
- Produce a deliberately ambiguous or hedged report that avoids directly contradicting the plaintiff's theory without explicitly endorsing it
- Communicate findings privately to Attorney Z and allow the attorney to decide whether to use the report, without formally withdrawing
- Decline to produce the report and proactively advise Attorney Z to seek a second engineering opinion before terminating the engagement
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Action_Decline_Favorable_Plaintiff_Report",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Produce a deliberately ambiguous or hedged report that avoids directly contradicting the plaintiff\u0027s theory without explicitly endorsing it",
"Communicate findings privately to Attorney Z and allow the attorney to decide whether to use the report, without formally withdrawing",
"Decline to produce the report and proactively advise Attorney Z to seek a second engineering opinion before terminating the engagement"
],
"proeth-scenario:characterMotivation": "Engineer A is committed to honest, objective engineering analysis. His professional integrity and adherence to the canon that engineers shall be objective and truthful compel him to report his findings accurately even when they are adverse to the client who retained him. He may also fear liability or reputational harm from producing a dishonest report.",
"proeth-scenario:consequencesIfAlternative": [
"An ambiguous report would be intellectually dishonest, potentially misleading the court, and would still constitute a violation of engineering ethics; it might also expose Engineer A to cross-examination that reveals the evasion.",
"Private communication without formal withdrawal creates ambiguity about Engineer A\u0027s role and obligations and could be seen as allowing the attorney to suppress unfavorable findings, raising its own ethical concerns.",
"Advising Attorney Z to seek a second opinion is professionally courteous and helpful, but does not change Engineer A\u0027s core obligation to report honestly; it would, however, demonstrate good faith and might strengthen the professional relationship even in adversity."
],
"proeth-scenario:decisionSignificance": "This action is the ethical high point of Engineer A\u0027s conduct in the case and a critical teaching moment: forensic engineers owe their primary duty to truth and the court, not to the retaining party. Declining to produce a favorable report when the evidence does not support it is the correct and courageous professional choice. Students should recognize this as the standard all forensic engineers must meet.",
"proeth-scenario:ethicalTension": "Loyalty and gratitude to the retaining client (Attorney Z) vs. the overriding engineering obligation to provide truthful, objective findings regardless of who is paying. The financial relationship and implicit expectation of a favorable report create pressure to shade conclusions, while professional codes and personal integrity push toward honest reporting.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If Engineer A produces a dishonest favorable report, he risks perjury, professional discipline, loss of licensure, and public harm. By refusing, he preserves his integrity but triggers termination, which then sets the stage for the subsequent ethical failure when he accepts the opposing engagement.",
"proeth:description": "Following his review and analysis, Engineer A determines he cannot produce an engineering and safety analysis report favorable to the plaintiff because his honest findings indicate the plaintiff, not the defendant, was at fault.",
"proeth:foreseenUnintendedEffects": [
"Termination of the engagement by Attorney Z",
"Loss of continued fee income from this matter",
"Potential reputational consequences with plaintiff\u0027s bar"
],
"proeth:fulfillsObligation": [
"Duty to issue objective and truthful engineering reports (NSPE Code II.3.a.)",
"Duty to avoid acting as a \u0027hired gun\u0027 biased toward the paying client",
"Duty to hold public safety paramount by accurately identifying the at-fault party",
"Duty of honesty and integrity in professional practice"
],
"proeth:guidedByPrinciple": [
"Forensic engineers must \u0027call them as they see them\u0027",
"Engineering objectivity supersedes client financial interest",
"Public safety and truthful analysis are paramount professional obligations",
"Engineers shall not misrepresent engineering facts or conditions"
],
"proeth:hasAgent": "Engineer A (Forensic Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client loyalty and financial continuity vs. professional integrity and truthfulness",
"proeth:resolutionReasoning": "Engineer A correctly resolved the conflict in favor of professional integrity; the Board explicitly commends this decision as wholly ethical and distinguishes it from the subsequent problematic action"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Uphold professional integrity by refusing to issue a report whose conclusions would misrepresent his honest engineering findings",
"proeth:requiresCapability": [
"Forensic engineering judgment",
"Objective safety analysis",
"Professional courage to deliver unfavorable findings to retaining client"
],
"proeth:temporalMarker": "After completion of review and analysis, prior to termination",
"proeth:withinCompetence": true,
"rdfs:label": "Decline Favorable Plaintiff Report"
}
Description: After his services with Attorney Z are terminated, Engineer A agrees to be retained by Attorney X (defendant's counsel) to provide a purportedly separate and independent engineering and safety analysis report for the defendant in the same personal injury case.
Temporal Marker: After termination by Attorney Z and payment of fee in full; after Attorney X learns of the circumstances of Engineer A's termination
Mental State: deliberate
Intended Outcome: Provide a new, independent forensic engineering analysis for the defendant's side of the same litigation in exchange for a fee
Guided By Principles:
- An engineer's duty of confidentiality and loyalty to a former client persists at minimum for the duration of the same legal proceeding
- Mere termination of a professional relationship does not extinguish residual ethical obligations
- Engineers must avoid situations where retained knowledge from one client could advantage an adverse party
- An engineer cannot provide truly independent analysis when he has already been immersed in confidential information from the opposing party
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A may rationalize that because his services were terminated and he was paid in full, his obligations to Attorney Z have ended. He may view the defendant's case as a genuinely new, separate engagement and may be motivated by financial compensation, professional interest in the technical problem, or a belief that his honest findings — which actually favor the defendant — mean he is simply following the truth to its logical conclusion. He may also feel that Attorney X's framing of the work as 'independent' provides ethical cover.
Ethical Tension: The desire to continue working and to follow his honest technical conclusions vs. the residual confidentiality and loyalty obligations that survive termination of the first engagement. The appearance of impartiality (his findings do favor the defendant) conflicts with the reality that he carries privileged knowledge of the plaintiff's litigation strategy, documents, and internal assessments that could — consciously or not — shape his new analysis.
Learning Significance: This is the central ethical failure of the scenario and the climax of the case. Students learn that termination of an engagement and full payment do not extinguish confidentiality obligations or resolve conflicts of interest. The key insight from BER cases 74-2, 76-3, 82-2, and 82-6 is that an engineer cannot switch sides in ongoing litigation because the conflict is irresolvable for the duration of the proceeding, regardless of the engineer's good intentions.
Stakes: The integrity of the legal proceeding is at risk; the plaintiff may be prejudiced by the use of her own confidential information against her. Engineer A faces potential professional discipline, loss of licensure, civil liability, and reputational destruction. The justice system's reliance on neutral expert witnesses is undermined. Attorney X may also face bar discipline for knowingly retaining a conflicted expert.
Decision Point: Yes - Story can branch here
- Decline Attorney X's retention immediately upon being contacted, citing confidentiality obligations and conflict of interest from the prior engagement
- Disclose the prior engagement to Attorney X and allow Attorney X to seek an ethics ruling or court guidance before proceeding
- Contact Attorney Z to seek informed consent and a formal conflict waiver before agreeing to work for Attorney X
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Action_Accept_Defendant_Attorney_Retention",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline Attorney X\u0027s retention immediately upon being contacted, citing confidentiality obligations and conflict of interest from the prior engagement",
"Disclose the prior engagement to Attorney X and allow Attorney X to seek an ethics ruling or court guidance before proceeding",
"Contact Attorney Z to seek informed consent and a formal conflict waiver before agreeing to work for Attorney X"
],
"proeth-scenario:characterMotivation": "Engineer A may rationalize that because his services were terminated and he was paid in full, his obligations to Attorney Z have ended. He may view the defendant\u0027s case as a genuinely new, separate engagement and may be motivated by financial compensation, professional interest in the technical problem, or a belief that his honest findings \u2014 which actually favor the defendant \u2014 mean he is simply following the truth to its logical conclusion. He may also feel that Attorney X\u0027s framing of the work as \u0027independent\u0027 provides ethical cover.",
"proeth-scenario:consequencesIfAlternative": [
"Declining is the clearly correct ethical choice; it preserves Engineer A\u0027s integrity, protects the plaintiff\u0027s confidential information, and maintains the appearance of fairness in the proceeding. Engineer A loses the new fee but avoids all downstream ethical and legal jeopardy.",
"Disclosing to Attorney X and seeking guidance demonstrates good faith and transparency; a court or ethics body would almost certainly confirm the conflict is irresolvable, leading to the same outcome as declining but with external validation.",
"Seeking consent from Attorney Z is ethically necessary but almost certainly futile \u2014 no reasonable plaintiff\u0027s attorney would consent to the opposing side retaining the engineer who reviewed all of the plaintiff\u0027s confidential materials. The attempt would, however, demonstrate Engineer A\u0027s awareness of his obligations."
],
"proeth-scenario:decisionSignificance": "This is the central ethical failure of the scenario and the climax of the case. Students learn that termination of an engagement and full payment do not extinguish confidentiality obligations or resolve conflicts of interest. The key insight from BER cases 74-2, 76-3, 82-2, and 82-6 is that an engineer cannot switch sides in ongoing litigation because the conflict is irresolvable for the duration of the proceeding, regardless of the engineer\u0027s good intentions.",
"proeth-scenario:ethicalTension": "The desire to continue working and to follow his honest technical conclusions vs. the residual confidentiality and loyalty obligations that survive termination of the first engagement. The appearance of impartiality (his findings do favor the defendant) conflicts with the reality that he carries privileged knowledge of the plaintiff\u0027s litigation strategy, documents, and internal assessments that could \u2014 consciously or not \u2014 shape his new analysis.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "The integrity of the legal proceeding is at risk; the plaintiff may be prejudiced by the use of her own confidential information against her. Engineer A faces potential professional discipline, loss of licensure, civil liability, and reputational destruction. The justice system\u0027s reliance on neutral expert witnesses is undermined. Attorney X may also face bar discipline for knowingly retaining a conflicted expert.",
"proeth:description": "After his services with Attorney Z are terminated, Engineer A agrees to be retained by Attorney X (defendant\u0027s counsel) to provide a purportedly separate and independent engineering and safety analysis report for the defendant in the same personal injury case.",
"proeth:foreseenUnintendedEffects": [
"Inevitable use of confidential information and knowledge acquired during the plaintiff engagement",
"Creation of an irresolvable conflict of interest adverse to former client",
"Perception that Engineer A was selected precisely because his prior analysis favored the defendant\u0027s position",
"Violation of residual duty of loyalty and confidentiality owed to Attorney Z and the plaintiff"
],
"proeth:guidedByPrinciple": [
"An engineer\u0027s duty of confidentiality and loyalty to a former client persists at minimum for the duration of the same legal proceeding",
"Mere termination of a professional relationship does not extinguish residual ethical obligations",
"Engineers must avoid situations where retained knowledge from one client could advantage an adverse party",
"An engineer cannot provide truly independent analysis when he has already been immersed in confidential information from the opposing party"
],
"proeth:hasAgent": "Engineer A (Forensic Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Right to accept new work and earn fees vs. residual confidentiality and loyalty obligations to former client",
"proeth:resolutionReasoning": "The Board finds Engineer A should have declined this retention. The residual duty of confidentiality and loyalty to the former client, the impossibility of providing truly independent analysis given prior immersion in plaintiff\u0027s confidential information, and the transparent reason for the retention (favorable prior findings) collectively make this engagement irresolvably conflicted and unethical"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Provide a new, independent forensic engineering analysis for the defendant\u0027s side of the same litigation in exchange for a fee",
"proeth:requiresCapability": [
"Forensic engineering analysis",
"Safety analysis",
"Conflict of interest recognition and management",
"Professional judgment to decline conflicted engagements"
],
"proeth:temporalMarker": "After termination by Attorney Z and payment of fee in full; after Attorney X learns of the circumstances of Engineer A\u0027s termination",
"proeth:violatesObligation": [
"Duty to protect confidential client information acquired during prior engagement (NSPE Code III.4.b.)",
"Duty to avoid conflicts of interest (NSPE Code II.4.b.)",
"Residual duty of loyalty and trust to former client Attorney Z and the plaintiff for the duration of the legal proceeding",
"Duty to disclose conflict of interest and obtain consent of former client before accepting adverse engagement",
"Duty to consult with former client Attorney Z before agreeing to work for opposing counsel"
],
"proeth:withinCompetence": true,
"rdfs:label": "Accept Defendant Attorney Retention"
}
Description: Engineer A fails to consult with or seek the informed consent of Attorney Z (former client) before agreeing to perform services for Attorney X on the opposing side of the same litigation.
Temporal Marker: At the point of accepting retention by Attorney X; before commencing work for the defendant
Mental State: negligent or deliberate omission
Intended Outcome: No affirmative intended outcome — this is a failure to act on a required obligation; Engineer A proceeds to accept the new engagement without taking the required disclosure and consent step
Guided By Principles:
- Engineers must proactively manage conflicts of interest, not merely avoid the most obvious violations
- Disclosure and consent are minimum requirements before an engineer switches sides in active litigation
- The former client's ability to protect confidential information depends on the engineer's proactive disclosure
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A likely omits disclosure because he believes — incorrectly — that the termination of his first engagement fully dissolved all obligations to Attorney Z. He may also wish to avoid an awkward or adversarial conversation, fear that disclosure would result in a formal objection blocking the new engagement, or simply fail to recognize that the duty to consult a former client before switching sides is a distinct and affirmative ethical obligation rather than a courtesy.
Ethical Tension: Self-interest and convenience in pursuing the new engagement vs. the professional obligation of transparency and the former client's right to protect confidential information she entrusted to Engineer A. The tension is between the engineer's desire to treat the matter as closed and the reality that the former client retains a legitimate ongoing interest in how her confidential information is used.
Learning Significance: Students learn that confidentiality and conflict-of-interest obligations to former clients are affirmative duties, not passive ones. The obligation to consult and seek informed consent before undertaking adverse representation is a procedural safeguard that protects both the former client and the integrity of the professional relationship. Omitting this step compounds the underlying conflict rather than merely reflecting it.
Stakes: Attorney Z and the plaintiff are denied the opportunity to seek a protective order, move to disqualify Engineer A, or take other legal steps to protect their confidential information. The plaintiff's litigation position may be materially harmed. Engineer A's omission transforms a potential conflict into a definitive ethical violation and may constitute a breach of contract or tortious conduct in addition to a professional code violation.
Decision Point: Yes - Story can branch here
- Contact Attorney Z directly, disclose Attorney X's approach, and ask whether Attorney Z consents to the new engagement
- Retain independent legal counsel to advise on the disclosure obligation before responding to Attorney X
- Notify both attorneys in writing of the prior engagement and the potential conflict, and decline to proceed until the conflict is resolved by agreement or court order
Narrative Role: falling_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Action_Omit_Disclosure_to_Former_Client",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Contact Attorney Z directly, disclose Attorney X\u0027s approach, and ask whether Attorney Z consents to the new engagement",
"Retain independent legal counsel to advise on the disclosure obligation before responding to Attorney X",
"Notify both attorneys in writing of the prior engagement and the potential conflict, and decline to proceed until the conflict is resolved by agreement or court order"
],
"proeth-scenario:characterMotivation": "Engineer A likely omits disclosure because he believes \u2014 incorrectly \u2014 that the termination of his first engagement fully dissolved all obligations to Attorney Z. He may also wish to avoid an awkward or adversarial conversation, fear that disclosure would result in a formal objection blocking the new engagement, or simply fail to recognize that the duty to consult a former client before switching sides is a distinct and affirmative ethical obligation rather than a courtesy.",
"proeth-scenario:consequencesIfAlternative": [
"Contacting Attorney Z is the ethically required step; Attorney Z would almost certainly withhold consent, but Engineer A would have fulfilled his disclosure obligation and could then decline Attorney X\u0027s retention with a clear conscience and a documented record.",
"Retaining independent legal counsel demonstrates prudence and good faith; counsel would almost certainly advise Engineer A that the conflict is irresolvable and that he must decline, producing the correct outcome through a structured process.",
"Written notification to both parties creates a transparent record, protects Engineer A from later accusations of bad faith, and allows the court to adjudicate the conflict question if the parties cannot agree \u2014 the most procedurally sound alternative."
],
"proeth-scenario:decisionSignificance": "Students learn that confidentiality and conflict-of-interest obligations to former clients are affirmative duties, not passive ones. The obligation to consult and seek informed consent before undertaking adverse representation is a procedural safeguard that protects both the former client and the integrity of the professional relationship. Omitting this step compounds the underlying conflict rather than merely reflecting it.",
"proeth-scenario:ethicalTension": "Self-interest and convenience in pursuing the new engagement vs. the professional obligation of transparency and the former client\u0027s right to protect confidential information she entrusted to Engineer A. The tension is between the engineer\u0027s desire to treat the matter as closed and the reality that the former client retains a legitimate ongoing interest in how her confidential information is used.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "falling_action",
"proeth-scenario:stakes": "Attorney Z and the plaintiff are denied the opportunity to seek a protective order, move to disqualify Engineer A, or take other legal steps to protect their confidential information. The plaintiff\u0027s litigation position may be materially harmed. Engineer A\u0027s omission transforms a potential conflict into a definitive ethical violation and may constitute a breach of contract or tortious conduct in addition to a professional code violation.",
"proeth:description": "Engineer A fails to consult with or seek the informed consent of Attorney Z (former client) before agreeing to perform services for Attorney X on the opposing side of the same litigation.",
"proeth:foreseenUnintendedEffects": [
"Former client is deprived of the opportunity to object or protect confidential information",
"Conflict of interest proceeds without the safeguard of informed consent",
"Engineer A\u0027s obligations under Code Section III.4.b. are violated"
],
"proeth:guidedByPrinciple": [
"Engineers must proactively manage conflicts of interest, not merely avoid the most obvious violations",
"Disclosure and consent are minimum requirements before an engineer switches sides in active litigation",
"The former client\u0027s ability to protect confidential information depends on the engineer\u0027s proactive disclosure"
],
"proeth:hasAgent": "Engineer A (Forensic Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Convenience and speed of accepting new engagement vs. procedural obligation to disclose and seek consent",
"proeth:resolutionReasoning": "There is no legitimate competing priority that justifies omitting disclosure; the Board finds this omission to be a straightforward ethical violation with no valid justification"
},
"proeth:hasMentalState": "negligent or deliberate omission",
"proeth:intendedOutcome": "No affirmative intended outcome \u2014 this is a failure to act on a required obligation; Engineer A proceeds to accept the new engagement without taking the required disclosure and consent step",
"proeth:requiresCapability": [
"Conflict of interest identification",
"Professional communication with former client",
"Ethical judgment regarding switching sides in active litigation"
],
"proeth:temporalMarker": "At the point of accepting retention by Attorney X; before commencing work for the defendant",
"proeth:violatesObligation": [
"Duty to fully disclose conflict of interest to former client before accepting adverse engagement (NSPE Code III.4.b.)",
"Duty to obtain informed consent of former client before representing adverse interests in the same matter",
"Duty of transparency and honesty with all parties affected by potential conflict"
],
"proeth:withinCompetence": true,
"rdfs:label": "Omit Disclosure to Former Client"
}
Description: Engineer A accepts the characterization of his new engagement as 'separate and independent' without recognizing or disclosing that his prior immersion in the plaintiff's confidential documents and information makes a truly independent analysis impossible and creates an irresolvable conflict of interest.
Temporal Marker: At the point of agreeing to terms with Attorney X; framing of the new engagement as independent
Mental State: negligent — failure to apply required professional judgment; possibly self-serving rationalization
Intended Outcome: Engineer A apparently intends to perform a genuinely new and independent analysis, or at minimum accepts the framing that the engagement is independent in order to justify accepting it
Guided By Principles:
- The label 'independent' does not make an analysis independent when the engineer has been immersed in one party's confidential information
- Engineers must recognize the limits of their ability to compartmentalize prior knowledge in conflict situations
- Professional integrity requires declining engagements where true independence cannot be achieved
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A accepts the 'separate and independent' framing because it provides a convenient rationalization that aligns with his financial interest in the new engagement and his genuine belief that his honest technical conclusions favor the defendant. He may conflate the objectivity of his technical findings with the independence of his analytical process, failing to appreciate that the latter is irremediably compromised by his prior exposure to the plaintiff's confidential materials regardless of how honest his intentions are.
Ethical Tension: The appeal of a logically coherent but superficially reasoned justification ('my findings are honest, therefore my analysis is independent') vs. the deeper ethical reality that independence is not only about the honesty of conclusions but about the integrity of the process and the absence of privileged prior knowledge. The tension is between subjective good faith and objective appearance of conflict, both of which matter in professional ethics.
Learning Significance: This action encapsulates the most sophisticated and teachable insight of the entire scenario: that an engineer's sincere belief in the objectivity of his conclusions does not cure a structural conflict of interest. Students learn to distinguish between subjective honesty and objective independence, and to recognize that the appearance of conflict — particularly in the context of litigation where public trust in expert witnesses is essential — is itself an ethical harm that must be avoided. The 'independent analysis' label cannot override the reality of retained confidential knowledge.
Stakes: If this rationalization goes unchallenged, it sets a dangerous precedent allowing engineers to switch sides in litigation whenever they believe their conclusions are honest, effectively eliminating the protection that conflict-of-interest rules provide to former clients. The broader stakes include erosion of public trust in forensic engineering, weakening of the adversarial legal system's reliance on untainted expert witnesses, and the normalization of a self-serving ethical standard that subordinates structural integrity to subjective intent.
Decision Point: Yes - Story can branch here
- Critically examine the 'independent' characterization by consulting the NSPE Code of Ethics and relevant BER opinions before accepting the engagement
- Seek a formal advisory opinion from the state engineering licensing board or a professional ethics committee before proceeding
- Acknowledge the structural impossibility of independence given prior exposure to confidential plaintiff materials and decline the engagement on that basis alone, separate from any other conflict analysis
Narrative Role: resolution
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Action_Fail_to_Recognize_Irresolvable_Conflict",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Critically examine the \u0027independent\u0027 characterization by consulting the NSPE Code of Ethics and relevant BER opinions before accepting the engagement",
"Seek a formal advisory opinion from the state engineering licensing board or a professional ethics committee before proceeding",
"Acknowledge the structural impossibility of independence given prior exposure to confidential plaintiff materials and decline the engagement on that basis alone, separate from any other conflict analysis"
],
"proeth-scenario:characterMotivation": "Engineer A accepts the \u0027separate and independent\u0027 framing because it provides a convenient rationalization that aligns with his financial interest in the new engagement and his genuine belief that his honest technical conclusions favor the defendant. He may conflate the objectivity of his technical findings with the independence of his analytical process, failing to appreciate that the latter is irremediably compromised by his prior exposure to the plaintiff\u0027s confidential materials regardless of how honest his intentions are.",
"proeth-scenario:consequencesIfAlternative": [
"Consulting the NSPE Code and BER precedents (74-2, 76-3, 82-2, 82-6) would have revealed directly on-point authority establishing that switching sides in ongoing litigation is unethical regardless of the engineer\u0027s subjective honesty; Engineer A would have had clear guidance to decline.",
"A formal advisory opinion would produce the same substantive conclusion through an authoritative external channel, providing Engineer A with documented ethical cover for declining and potentially educating Attorney X about the impropriety of the solicitation.",
"Recognizing and articulating the impossibility of true independence \u2014 even without reference to formal authority \u2014 reflects the kind of practical ethical reasoning that experienced professionals develop; it would lead Engineer A to the correct outcome through first-principles analysis rather than rule-lookup, demonstrating mature professional judgment."
],
"proeth-scenario:decisionSignificance": "This action encapsulates the most sophisticated and teachable insight of the entire scenario: that an engineer\u0027s sincere belief in the objectivity of his conclusions does not cure a structural conflict of interest. Students learn to distinguish between subjective honesty and objective independence, and to recognize that the appearance of conflict \u2014 particularly in the context of litigation where public trust in expert witnesses is essential \u2014 is itself an ethical harm that must be avoided. The \u0027independent analysis\u0027 label cannot override the reality of retained confidential knowledge.",
"proeth-scenario:ethicalTension": "The appeal of a logically coherent but superficially reasoned justification (\u0027my findings are honest, therefore my analysis is independent\u0027) vs. the deeper ethical reality that independence is not only about the honesty of conclusions but about the integrity of the process and the absence of privileged prior knowledge. The tension is between subjective good faith and objective appearance of conflict, both of which matter in professional ethics.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "resolution",
"proeth-scenario:stakes": "If this rationalization goes unchallenged, it sets a dangerous precedent allowing engineers to switch sides in litigation whenever they believe their conclusions are honest, effectively eliminating the protection that conflict-of-interest rules provide to former clients. The broader stakes include erosion of public trust in forensic engineering, weakening of the adversarial legal system\u0027s reliance on untainted expert witnesses, and the normalization of a self-serving ethical standard that subordinates structural integrity to subjective intent.",
"proeth:description": "Engineer A accepts the characterization of his new engagement as \u0027separate and independent\u0027 without recognizing or disclosing that his prior immersion in the plaintiff\u0027s confidential documents and information makes a truly independent analysis impossible and creates an irresolvable conflict of interest.",
"proeth:foreseenUnintendedEffects": [
"Confidential plaintiff information inevitably informs the purportedly independent analysis",
"The integrity of the engineering report and the litigation process is compromised",
"Former client\u0027s confidential information is effectively weaponized against them"
],
"proeth:guidedByPrinciple": [
"The label \u0027independent\u0027 does not make an analysis independent when the engineer has been immersed in one party\u0027s confidential information",
"Engineers must recognize the limits of their ability to compartmentalize prior knowledge in conflict situations",
"Professional integrity requires declining engagements where true independence cannot be achieved"
],
"proeth:hasAgent": "Engineer A (Forensic Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Self-interest in accepting new work vs. honest recognition that independence is unachievable",
"proeth:resolutionReasoning": "The Board finds no valid justification for Engineer A\u0027s failure to recognize the irresolvable conflict; the sequence of events made the conflict obvious, and professional ethical judgment required declining the engagement"
},
"proeth:hasMentalState": "negligent \u2014 failure to apply required professional judgment; possibly self-serving rationalization",
"proeth:intendedOutcome": "Engineer A apparently intends to perform a genuinely new and independent analysis, or at minimum accepts the framing that the engagement is independent in order to justify accepting it",
"proeth:requiresCapability": [
"Conflict of interest analysis",
"Self-awareness regarding the limits of cognitive compartmentalization",
"Professional judgment to decline engagements where independence cannot be achieved",
"Recognition of how prior confidential access taints subsequent adverse engagements"
],
"proeth:temporalMarker": "At the point of agreeing to terms with Attorney X; framing of the new engagement as independent",
"proeth:violatesObligation": [
"Duty to avoid conflicts of interest (NSPE Code II.4.b.)",
"Duty to protect confidential client information (NSPE Code III.4.b.)",
"Duty to provide objective engineering analysis free from the taint of improperly retained confidential information",
"Duty to decline engagements where an irresolvable conflict exists"
],
"proeth:withinCompetence": true,
"rdfs:label": "Fail to Recognize Irresolvable Conflict"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changesDescription: A formal forensic consulting relationship is created between Attorney Z and Engineer A upon hiring, establishing confidentiality obligations and a duty of loyalty to the plaintiff's legal team. This relationship is legally and ethically binding from the moment of retention.
Temporal Marker: At outset, when Attorney Z hires Engineer A
Activates Constraints:
- Confidentiality_Obligation_Constraint
- Loyalty_To_Client_Constraint
- Conflict_Of_Interest_Avoidance_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A likely feels professional confidence and routine engagement; Attorney Z feels optimism about technical support; plaintiff has hope that expert analysis will support their case; no tension yet as obligations feel manageable
- engineer_a: Becomes bound by confidentiality and conflict-of-interest obligations that will persist beyond the engagement's termination
- attorney_z_plaintiff_team: Gains forensic expertise but also shares privileged case strategy and evidence with Engineer A
- plaintiff: Trusts that retained expert will maintain confidentiality and loyalty throughout proceedings
- defendant_and_attorney_x: Unaware that this retention creates future constraints on Engineer A's availability
Learning Moment: The moment of retention is not merely administrative — it automatically creates lasting ethical obligations including confidentiality that survive termination. Students should understand that professional relationships carry invisible but binding ethical consequences from their inception.
Ethical Implications: Reveals that professional obligations are not merely contractual but arise automatically from the nature of the relationship; highlights tension between treating engineering as a commercial service versus a profession with inherent duties; establishes the ethical foundation that makes subsequent events problematic
- What ethical obligations are automatically triggered the moment an engineer accepts a forensic consulting engagement, and do those obligations differ from a standard engineering contract?
- Should Engineer A have asked Attorney Z about the nature of the case and potential conflicts before accepting the retention?
- How long do confidentiality obligations persist after a consulting engagement ends, and what factors determine their duration?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Event_Plaintiff_Engagement_Established",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"What ethical obligations are automatically triggered the moment an engineer accepts a forensic consulting engagement, and do those obligations differ from a standard engineering contract?",
"Should Engineer A have asked Attorney Z about the nature of the case and potential conflicts before accepting the retention?",
"How long do confidentiality obligations persist after a consulting engagement ends, and what factors determine their duration?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer A likely feels professional confidence and routine engagement; Attorney Z feels optimism about technical support; plaintiff has hope that expert analysis will support their case; no tension yet as obligations feel manageable",
"proeth-scenario:ethicalImplications": "Reveals that professional obligations are not merely contractual but arise automatically from the nature of the relationship; highlights tension between treating engineering as a commercial service versus a profession with inherent duties; establishes the ethical foundation that makes subsequent events problematic",
"proeth-scenario:learningMoment": "The moment of retention is not merely administrative \u2014 it automatically creates lasting ethical obligations including confidentiality that survive termination. Students should understand that professional relationships carry invisible but binding ethical consequences from their inception.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"attorney_z_plaintiff_team": "Gains forensic expertise but also shares privileged case strategy and evidence with Engineer A",
"defendant_and_attorney_x": "Unaware that this retention creates future constraints on Engineer A\u0027s availability",
"engineer_a": "Becomes bound by confidentiality and conflict-of-interest obligations that will persist beyond the engagement\u0027s termination",
"plaintiff": "Trusts that retained expert will maintain confidentiality and loyalty throughout proceedings"
},
"proeth:activatesConstraint": [
"Confidentiality_Obligation_Constraint",
"Loyalty_To_Client_Constraint",
"Conflict_Of_Interest_Avoidance_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/172#Action_Accept_Plaintiff_Forensic_Retention",
"proeth:causesStateChange": "Engineer A transitions from independent professional to retained forensic consultant with fiduciary-like obligations to plaintiff\u0027s legal team; confidentiality clock begins",
"proeth:createsObligation": [
"Maintain_Confidentiality_Of_Case_Information",
"Provide_Honest_Independent_Analysis",
"Avoid_Adverse_Representation_In_Same_Matter",
"Disclose_Conflicts_If_They_Arise"
],
"proeth:description": "A formal forensic consulting relationship is created between Attorney Z and Engineer A upon hiring, establishing confidentiality obligations and a duty of loyalty to the plaintiff\u0027s legal team. This relationship is legally and ethically binding from the moment of retention.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "At outset, when Attorney Z hires Engineer A",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Plaintiff Engagement Established"
}
Description: Engineer A's independent technical review of the evidence produces a conclusion that fault lies with the plaintiff rather than the defendant, an outcome that is determined by the objective facts of the case rather than by Engineer A's preferences or choices. This finding is an evidentiary outcome, not a decision.
Temporal Marker: After reviewing evidence, during the forensic engagement
Activates Constraints:
- Honesty_And_Objectivity_Constraint
- Public_Truthfulness_Constraint
- Duty_Not_To_Deceive_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel professional integrity affirmed but also discomfort at delivering unwelcome news; Attorney Z likely feels frustration and concern about losing technical support; plaintiff may feel betrayed or anxious about case prospects; the finding creates interpersonal tension
- engineer_a: Findings become confidential case information; Engineer A now holds sensitive knowledge about plaintiff's weaknesses that could be exploited if shared
- attorney_z_plaintiff_team: Loses anticipated expert support; must reassess litigation strategy; becomes concerned about what Engineer A now knows
- plaintiff: Case prospects weaken; confidential vulnerabilities are now known to a third party
- defendant_and_attorney_x: Unaware that adverse findings exist and that an expert with inside knowledge of plaintiff's case has been released
Learning Moment: An adverse technical finding is an objective outcome, not a choice — but how the engineer handles that finding is entirely an ethical matter. Students should recognize that honest findings that damage a client's case are the hallmark of engineering integrity, and that such findings create heightened confidentiality sensitivity.
Ethical Implications: Illustrates the core tension between client loyalty and professional objectivity; demonstrates that engineering integrity sometimes requires delivering unwelcome truths; reveals that honest adverse findings paradoxically create greater confidentiality obligations because the information is more sensitive and potentially exploitable
- If Engineer A's findings are adverse to the plaintiff, what ethical obligations does Engineer A have in communicating those findings, and to whom?
- Does the fact that Engineer A reached an honest, objective conclusion protect him from any subsequent ethical criticism, or do new obligations arise from the finding itself?
- How does an adverse finding change the sensitivity of the information Engineer A holds about the plaintiff's case?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Event_Analysis_Points_To_Plaintiff_Fault",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"If Engineer A\u0027s findings are adverse to the plaintiff, what ethical obligations does Engineer A have in communicating those findings, and to whom?",
"Does the fact that Engineer A reached an honest, objective conclusion protect him from any subsequent ethical criticism, or do new obligations arise from the finding itself?",
"How does an adverse finding change the sensitivity of the information Engineer A holds about the plaintiff\u0027s case?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may feel professional integrity affirmed but also discomfort at delivering unwelcome news; Attorney Z likely feels frustration and concern about losing technical support; plaintiff may feel betrayed or anxious about case prospects; the finding creates interpersonal tension",
"proeth-scenario:ethicalImplications": "Illustrates the core tension between client loyalty and professional objectivity; demonstrates that engineering integrity sometimes requires delivering unwelcome truths; reveals that honest adverse findings paradoxically create greater confidentiality obligations because the information is more sensitive and potentially exploitable",
"proeth-scenario:learningMoment": "An adverse technical finding is an objective outcome, not a choice \u2014 but how the engineer handles that finding is entirely an ethical matter. Students should recognize that honest findings that damage a client\u0027s case are the hallmark of engineering integrity, and that such findings create heightened confidentiality sensitivity.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"attorney_z_plaintiff_team": "Loses anticipated expert support; must reassess litigation strategy; becomes concerned about what Engineer A now knows",
"defendant_and_attorney_x": "Unaware that adverse findings exist and that an expert with inside knowledge of plaintiff\u0027s case has been released",
"engineer_a": "Findings become confidential case information; Engineer A now holds sensitive knowledge about plaintiff\u0027s weaknesses that could be exploited if shared",
"plaintiff": "Case prospects weaken; confidential vulnerabilities are now known to a third party"
},
"proeth:activatesConstraint": [
"Honesty_And_Objectivity_Constraint",
"Public_Truthfulness_Constraint",
"Duty_Not_To_Deceive_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/172#Action_Decline_Favorable_Plaintiff_Report",
"proeth:causesStateChange": "Engineer A\u0027s role shifts from potential plaintiff-supporting expert to a consultant whose findings are adverse to the retaining party; the engagement becomes untenable for Attorney Z\u0027s purposes while Engineer A\u0027s knowledge of case strategy and evidence becomes sensitive",
"proeth:createsObligation": [
"Communicate_Findings_Honestly_To_Retaining_Attorney",
"Decline_To_Produce_Report_Unsupported_By_Evidence",
"Preserve_Confidentiality_Of_Findings_And_Case_Strategy"
],
"proeth:description": "Engineer A\u0027s independent technical review of the evidence produces a conclusion that fault lies with the plaintiff rather than the defendant, an outcome that is determined by the objective facts of the case rather than by Engineer A\u0027s preferences or choices. This finding is an evidentiary outcome, not a decision.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After reviewing evidence, during the forensic engagement",
"proeth:urgencyLevel": "high",
"rdfs:label": "Analysis Points To Plaintiff Fault"
}
Description: Attorney Z ends Engineer A's forensic consulting engagement after receiving the adverse findings, and Engineer A is paid in full for work completed. This termination is an outcome of the irreconcilable mismatch between Engineer A's honest findings and Attorney Z's litigation needs.
Temporal Marker: After Engineer A communicates inability to support plaintiff's case
Activates Constraints:
- Post_Engagement_Confidentiality_Constraint
- Residual_Conflict_Of_Interest_Constraint
- Duration_Of_Proceeding_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel relief at honest conclusion but uncertainty about professional standing; Attorney Z feels frustration and strategic concern; plaintiff feels exposed knowing an expert now holds knowledge of their case weaknesses; the termination feels abrupt but professionally clean on the surface
- engineer_a: Freed from active obligations but bound by residual confidentiality; holds sensitive case knowledge that makes him a liability if retained by opposing party
- attorney_z_plaintiff_team: Loses forensic support; must find alternative expert; concerned about Engineer A's future conduct and potential disclosure of case strategy
- plaintiff: Vulnerable — an outside expert now knows the technical weaknesses of their case and is no longer bound by active loyalty
- defendant_and_attorney_x: The termination, once discovered, signals that Engineer A has inside knowledge of plaintiff's case — making him an attractive but ethically impermissible target for retention
Learning Moment: Termination of a consulting engagement does not terminate all ethical obligations. Students must understand that confidentiality and conflict-of-interest constraints survive the end of the formal relationship, particularly when the same legal matter remains ongoing. Payment in full does not constitute ethical release.
Ethical Implications: Exposes the myth that professional obligations end when a contract ends; reveals the tension between an engineer's right to seek new clients and the profession's interest in maintaining trustworthy confidential relationships; demonstrates that the adversarial legal system creates structural pressures that can corrupt engineering ethics if engineers are not vigilant
- Does full payment upon termination release Engineer A from any ongoing ethical obligations, or do those obligations persist regardless of compensation?
- What should Engineer A do if, after termination, he is approached by another party in the same legal proceeding?
- How does the termination of an engagement change the ethical landscape compared to the engagement's active phase?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Event_Engineer_A_Services_Terminated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Does full payment upon termination release Engineer A from any ongoing ethical obligations, or do those obligations persist regardless of compensation?",
"What should Engineer A do if, after termination, he is approached by another party in the same legal proceeding?",
"How does the termination of an engagement change the ethical landscape compared to the engagement\u0027s active phase?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may feel relief at honest conclusion but uncertainty about professional standing; Attorney Z feels frustration and strategic concern; plaintiff feels exposed knowing an expert now holds knowledge of their case weaknesses; the termination feels abrupt but professionally clean on the surface",
"proeth-scenario:ethicalImplications": "Exposes the myth that professional obligations end when a contract ends; reveals the tension between an engineer\u0027s right to seek new clients and the profession\u0027s interest in maintaining trustworthy confidential relationships; demonstrates that the adversarial legal system creates structural pressures that can corrupt engineering ethics if engineers are not vigilant",
"proeth-scenario:learningMoment": "Termination of a consulting engagement does not terminate all ethical obligations. Students must understand that confidentiality and conflict-of-interest constraints survive the end of the formal relationship, particularly when the same legal matter remains ongoing. Payment in full does not constitute ethical release.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"attorney_z_plaintiff_team": "Loses forensic support; must find alternative expert; concerned about Engineer A\u0027s future conduct and potential disclosure of case strategy",
"defendant_and_attorney_x": "The termination, once discovered, signals that Engineer A has inside knowledge of plaintiff\u0027s case \u2014 making him an attractive but ethically impermissible target for retention",
"engineer_a": "Freed from active obligations but bound by residual confidentiality; holds sensitive case knowledge that makes him a liability if retained by opposing party",
"plaintiff": "Vulnerable \u2014 an outside expert now knows the technical weaknesses of their case and is no longer bound by active loyalty"
},
"proeth:activatesConstraint": [
"Post_Engagement_Confidentiality_Constraint",
"Residual_Conflict_Of_Interest_Constraint",
"Duration_Of_Proceeding_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/172#Action_Decline_Favorable_Plaintiff_Report",
"proeth:causesStateChange": "The active engagement ends but confidentiality obligations survive; Engineer A is now a free agent in the labor market but is ethically constrained from working for the opposing party in the same legal proceeding; the termination paradoxically makes Engineer A more attractive to Attorney X while simultaneously making that attraction ethically impermissible",
"proeth:createsObligation": [
"Maintain_Confidentiality_Of_All_Case_Information_Indefinitely_During_Proceedings",
"Decline_Retention_By_Adverse_Party_In_Same_Matter",
"Disclose_Prior_Engagement_If_Approached_By_Opposing_Party"
],
"proeth:description": "Attorney Z ends Engineer A\u0027s forensic consulting engagement after receiving the adverse findings, and Engineer A is paid in full for work completed. This termination is an outcome of the irreconcilable mismatch between Engineer A\u0027s honest findings and Attorney Z\u0027s litigation needs.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After Engineer A communicates inability to support plaintiff\u0027s case",
"proeth:urgencyLevel": "high",
"rdfs:label": "Engineer A Services Terminated"
}
Description: Attorney X (defendant's counsel) learns of the circumstances surrounding Engineer A's termination by Attorney Z, including the fact that Engineer A's findings were adverse to the plaintiff and that services were ended as a result. This information disclosure is an exogenous event that creates the conditions for the subsequent ethically problematic retention.
Temporal Marker: Subsequently, after Engineer A's termination, before Attorney X's retention
Activates Constraints:
- Appearance_Of_Conflict_Constraint
- Prohibition_On_Exploitation_Of_Confidential_Information_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Attorney X likely feels opportunistic excitement — a potentially favorable expert has become available; Engineer A may be unaware that this information has circulated; plaintiff and Attorney Z may feel anxiety or betrayal if they suspect Engineer A's situation is being exploited; the event has a voyeuristic quality — someone is watching and acting on private professional circumstances
- engineer_a: Becomes a target for retention by the opposing party without necessarily knowing it; his professional reputation and prior work are being assessed by an adversarial party
- attorney_z_plaintiff_team: Their confidential case strategy may be indirectly compromised if Engineer A's knowledge of adverse findings becomes available to the defense
- plaintiff: Faces the prospect that an expert who knows their case weaknesses may be weaponized against them
- attorney_x_defendant: Gains what appears to be a strategic opportunity but is actually pursuing an ethically impermissible path
Learning Moment: The circulation of information about an engineer's termination circumstances is itself an ethically significant event. Students should understand that the manner in which professional transitions become known can create exploitation risks and that engineers must be alert to situations where their prior knowledge makes them attractive for impermissible reasons.
Ethical Implications: Reveals how information asymmetries in adversarial legal proceedings create structural pressures that can corrupt professional relationships; demonstrates that the appearance of a conflict is itself an ethical problem independent of actual disclosure of confidential information; highlights the vulnerability of confidential professional relationships to exploitation by sophisticated legal actors
- Who, if anyone, bears responsibility for the fact that Attorney X learned about the circumstances of Engineer A's termination — and does it matter how that information was transmitted?
- Does the fact that Attorney X learned this information through the legal community rather than from Engineer A directly change the ethical analysis?
- At what point does Engineer A acquire an obligation to act proactively to prevent being retained by Attorney X, even before being approached?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Event_Termination_Circumstances_Become_Known",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Who, if anyone, bears responsibility for the fact that Attorney X learned about the circumstances of Engineer A\u0027s termination \u2014 and does it matter how that information was transmitted?",
"Does the fact that Attorney X learned this information through the legal community rather than from Engineer A directly change the ethical analysis?",
"At what point does Engineer A acquire an obligation to act proactively to prevent being retained by Attorney X, even before being approached?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Attorney X likely feels opportunistic excitement \u2014 a potentially favorable expert has become available; Engineer A may be unaware that this information has circulated; plaintiff and Attorney Z may feel anxiety or betrayal if they suspect Engineer A\u0027s situation is being exploited; the event has a voyeuristic quality \u2014 someone is watching and acting on private professional circumstances",
"proeth-scenario:ethicalImplications": "Reveals how information asymmetries in adversarial legal proceedings create structural pressures that can corrupt professional relationships; demonstrates that the appearance of a conflict is itself an ethical problem independent of actual disclosure of confidential information; highlights the vulnerability of confidential professional relationships to exploitation by sophisticated legal actors",
"proeth-scenario:learningMoment": "The circulation of information about an engineer\u0027s termination circumstances is itself an ethically significant event. Students should understand that the manner in which professional transitions become known can create exploitation risks and that engineers must be alert to situations where their prior knowledge makes them attractive for impermissible reasons.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"attorney_x_defendant": "Gains what appears to be a strategic opportunity but is actually pursuing an ethically impermissible path",
"attorney_z_plaintiff_team": "Their confidential case strategy may be indirectly compromised if Engineer A\u0027s knowledge of adverse findings becomes available to the defense",
"engineer_a": "Becomes a target for retention by the opposing party without necessarily knowing it; his professional reputation and prior work are being assessed by an adversarial party",
"plaintiff": "Faces the prospect that an expert who knows their case weaknesses may be weaponized against them"
},
"proeth:activatesConstraint": [
"Appearance_Of_Conflict_Constraint",
"Prohibition_On_Exploitation_Of_Confidential_Information_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/172#Action_Decline_Favorable_Plaintiff_Report",
"proeth:causesStateChange": "Attorney X now possesses information that makes Engineer A appear attractive as a defendant expert \u2014 precisely because of knowledge that makes Engineer A ethically unavailable; the stage is set for the core ethical violation; the information asymmetry between what Attorney X knows and what ethical obligations require creates dangerous conditions",
"proeth:createsObligation": [
"Engineer_A_Must_Decline_If_Approached_By_Attorney_X",
"Engineer_A_Must_Disclose_Prior_Engagement_To_Any_Prospective_Retaining_Party_In_Same_Matter"
],
"proeth:description": "Attorney X (defendant\u0027s counsel) learns of the circumstances surrounding Engineer A\u0027s termination by Attorney Z, including the fact that Engineer A\u0027s findings were adverse to the plaintiff and that services were ended as a result. This information disclosure is an exogenous event that creates the conditions for the subsequent ethically problematic retention.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Subsequently, after Engineer A\u0027s termination, before Attorney X\u0027s retention",
"proeth:urgencyLevel": "high",
"rdfs:label": "Termination Circumstances Become Known"
}
Description: Upon Engineer A agreeing to work for Attorney X, a direct and irresolvable conflict of interest is created: Engineer A now holds confidential knowledge from the plaintiff's engagement and is simultaneously working to produce analysis favorable to the defendant in the same legal proceeding. This conflict is an automatic ethical outcome of the retention, not a separate decision.
Temporal Marker: At the moment Engineer A agrees to work for Attorney X
Activates Constraints:
- Irresolvable_Conflict_Of_Interest_Constraint
- Prohibition_On_Adverse_Representation_Constraint
- Confidentiality_Breach_Risk_Constraint
- Appearance_Of_Impropriety_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may not fully appreciate the gravity of the conflict, feeling that honest findings justify switching sides; Attorney X may feel satisfied at securing a knowledgeable expert; Attorney Z and plaintiff may feel violated and betrayed when they learn of the new retention; the legal system itself is placed under ethical stress
- engineer_a: Professional reputation severely damaged; potential disciplinary action by engineering ethics board; findings for defendant rendered ethically suspect and potentially inadmissible; career consequences possible
- attorney_z_plaintiff_team: Case strategy and technical vulnerabilities potentially exposed to opposing counsel through Engineer A's retained knowledge; legal remedies may be sought
- plaintiff: Faces the prospect of being harmed by their own former expert's knowledge being used against them
- attorney_x_defendant: Report produced under conflicted conditions may be challenged; Attorney X may face professional criticism for knowingly exploiting the conflict
- engineering_profession: Public trust in forensic engineering expertise undermined; appearance that engineers can be 'bought' by whichever party pays
Learning Moment: A conflict of interest is not merely a procedural inconvenience — it is an automatic ethical violation that taints all subsequent work and cannot be resolved simply by claiming honest intentions. Students must understand that the appearance of conflict is itself a violation, independent of whether confidential information is actually disclosed.
Ethical Implications: Reveals the deep tension between individual professional judgment and systemic trust in the engineering profession; demonstrates that conflict of interest rules protect not just individual clients but the integrity of adversarial proceedings and public confidence in expert testimony; shows how the adversarial legal system creates structural incentives that can corrupt professional ethics if engineers lack robust conflict-awareness; highlights that confidentiality is a relational obligation, not merely an information-security obligation
- Can Engineer A's honest, objective findings in the first engagement serve as a justification for accepting the defendant's retention, or does the conflict of interest exist regardless of the quality of the prior analysis?
- What specific steps should Engineer A have taken when approached by Attorney X, and at what point in the conversation should those steps have been triggered?
- How does the concept of 'appearance of conflict' differ from 'actual conflict,' and why does engineering ethics treat both as violations?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Event_Conflict_Of_Interest_Crystallized",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Can Engineer A\u0027s honest, objective findings in the first engagement serve as a justification for accepting the defendant\u0027s retention, or does the conflict of interest exist regardless of the quality of the prior analysis?",
"What specific steps should Engineer A have taken when approached by Attorney X, and at what point in the conversation should those steps have been triggered?",
"How does the concept of \u0027appearance of conflict\u0027 differ from \u0027actual conflict,\u0027 and why does engineering ethics treat both as violations?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may not fully appreciate the gravity of the conflict, feeling that honest findings justify switching sides; Attorney X may feel satisfied at securing a knowledgeable expert; Attorney Z and plaintiff may feel violated and betrayed when they learn of the new retention; the legal system itself is placed under ethical stress",
"proeth-scenario:ethicalImplications": "Reveals the deep tension between individual professional judgment and systemic trust in the engineering profession; demonstrates that conflict of interest rules protect not just individual clients but the integrity of adversarial proceedings and public confidence in expert testimony; shows how the adversarial legal system creates structural incentives that can corrupt professional ethics if engineers lack robust conflict-awareness; highlights that confidentiality is a relational obligation, not merely an information-security obligation",
"proeth-scenario:learningMoment": "A conflict of interest is not merely a procedural inconvenience \u2014 it is an automatic ethical violation that taints all subsequent work and cannot be resolved simply by claiming honest intentions. Students must understand that the appearance of conflict is itself a violation, independent of whether confidential information is actually disclosed.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"attorney_x_defendant": "Report produced under conflicted conditions may be challenged; Attorney X may face professional criticism for knowingly exploiting the conflict",
"attorney_z_plaintiff_team": "Case strategy and technical vulnerabilities potentially exposed to opposing counsel through Engineer A\u0027s retained knowledge; legal remedies may be sought",
"engineer_a": "Professional reputation severely damaged; potential disciplinary action by engineering ethics board; findings for defendant rendered ethically suspect and potentially inadmissible; career consequences possible",
"engineering_profession": "Public trust in forensic engineering expertise undermined; appearance that engineers can be \u0027bought\u0027 by whichever party pays",
"plaintiff": "Faces the prospect of being harmed by their own former expert\u0027s knowledge being used against them"
},
"proeth:activatesConstraint": [
"Irresolvable_Conflict_Of_Interest_Constraint",
"Prohibition_On_Adverse_Representation_Constraint",
"Confidentiality_Breach_Risk_Constraint",
"Appearance_Of_Impropriety_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/172#Action_Accept_Defendant_Attorney_Retention",
"proeth:causesStateChange": "Engineer A is now in an ethically untenable dual-knowledge position; the conflict is not merely potential but actual and irresolvable for the duration of the legal proceeding; any work product Engineer A produces for Attorney X is tainted by the conflict; the professional integrity of the entire forensic process is compromised",
"proeth:createsObligation": [
"Immediate_Withdrawal_From_Defendant_Engagement",
"Notification_To_Attorney_X_Of_Prior_Conflicting_Engagement",
"Refusal_To_Produce_Report_Until_Conflict_Resolved",
"Potential_Disclosure_To_Professional_Ethics_Board"
],
"proeth:description": "Upon Engineer A agreeing to work for Attorney X, a direct and irresolvable conflict of interest is created: Engineer A now holds confidential knowledge from the plaintiff\u0027s engagement and is simultaneously working to produce analysis favorable to the defendant in the same legal proceeding. This conflict is an automatic ethical outcome of the retention, not a separate decision.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "At the moment Engineer A agrees to work for Attorney X",
"proeth:urgencyLevel": "critical",
"rdfs:label": "Conflict Of Interest Crystallized"
}
Description: Following termination of the plaintiff engagement, Engineer A continues to hold in memory all technical findings, case strategy information, evidence assessments, and analytical conclusions acquired during the forensic review. This retention of knowledge is an automatic and unavoidable outcome of having performed the engagement, not a volitional act.
Temporal Marker: Continuously, from termination of plaintiff engagement through defendant retention
Activates Constraints:
- Residual_Knowledge_Conflict_Constraint
- Post_Engagement_Confidentiality_Constraint
- Prohibition_On_Using_Retained_Knowledge_Against_Former_Client_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may not consciously register this as a burden — the knowledge simply exists; Attorney Z and plaintiff may feel a diffuse anxiety about what Engineer A 'knows'; the event has an invisible quality that makes it easy to overlook but ethically significant
- engineer_a: Constrained from accepting certain future engagements without being fully aware of why; the constraint is ethical, not contractual, making it easier to rationalize away
- attorney_z_plaintiff_team: Vulnerable to having case strategy and technical weaknesses accessible to an engineer who may work for the opposition
- plaintiff: Protected only by Engineer A's voluntary compliance with ethical obligations that have no external enforcement mechanism at the moment of violation
- engineering_profession: Depends on individual engineers internalizing residual knowledge obligations without external prompting
Learning Moment: Professional knowledge acquired during a confidential engagement does not disappear when the engagement ends. Students must understand that residual knowledge creates ongoing ethical obligations and that the inability to 'unknow' information is precisely why conflict-of-interest rules prohibit switching sides in the same matter.
Ethical Implications: Highlights the epistemological challenge at the heart of conflict-of-interest ethics: knowledge is not a discrete object that can be returned or destroyed, making confidentiality obligations inherently relational and ongoing; reveals why the engineering profession's conflict rules must be prophylactic rather than remedial — by the time a violation is detectable, the harm has already occurred
- If Engineer A genuinely believes he can set aside his prior knowledge and produce an independent analysis for the defendant, does that belief change the ethical analysis?
- How should engineering ethics rules account for the practical reality that knowledge cannot be selectively erased — is the prohibition on adverse retention the only workable solution?
- What systemic mechanisms could help engineers recognize and act on residual knowledge conflicts before they accept problematic engagements?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#Event_Confidential_Knowledge_Retained_Post-Termination",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"If Engineer A genuinely believes he can set aside his prior knowledge and produce an independent analysis for the defendant, does that belief change the ethical analysis?",
"How should engineering ethics rules account for the practical reality that knowledge cannot be selectively erased \u2014 is the prohibition on adverse retention the only workable solution?",
"What systemic mechanisms could help engineers recognize and act on residual knowledge conflicts before they accept problematic engagements?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer A may not consciously register this as a burden \u2014 the knowledge simply exists; Attorney Z and plaintiff may feel a diffuse anxiety about what Engineer A \u0027knows\u0027; the event has an invisible quality that makes it easy to overlook but ethically significant",
"proeth-scenario:ethicalImplications": "Highlights the epistemological challenge at the heart of conflict-of-interest ethics: knowledge is not a discrete object that can be returned or destroyed, making confidentiality obligations inherently relational and ongoing; reveals why the engineering profession\u0027s conflict rules must be prophylactic rather than remedial \u2014 by the time a violation is detectable, the harm has already occurred",
"proeth-scenario:learningMoment": "Professional knowledge acquired during a confidential engagement does not disappear when the engagement ends. Students must understand that residual knowledge creates ongoing ethical obligations and that the inability to \u0027unknow\u0027 information is precisely why conflict-of-interest rules prohibit switching sides in the same matter.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"attorney_z_plaintiff_team": "Vulnerable to having case strategy and technical weaknesses accessible to an engineer who may work for the opposition",
"engineer_a": "Constrained from accepting certain future engagements without being fully aware of why; the constraint is ethical, not contractual, making it easier to rationalize away",
"engineering_profession": "Depends on individual engineers internalizing residual knowledge obligations without external prompting",
"plaintiff": "Protected only by Engineer A\u0027s voluntary compliance with ethical obligations that have no external enforcement mechanism at the moment of violation"
},
"proeth:activatesConstraint": [
"Residual_Knowledge_Conflict_Constraint",
"Post_Engagement_Confidentiality_Constraint",
"Prohibition_On_Using_Retained_Knowledge_Against_Former_Client_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/172#Action_Accept_Plaintiff_Forensic_Retention",
"proeth:causesStateChange": "Engineer A carries an invisible but ethically significant burden of confidential knowledge that constrains future professional choices; this knowledge cannot be compartmentalized or selectively forgotten; it creates a permanent conflict risk for the duration of the legal proceeding",
"proeth:createsObligation": [
"Refrain_From_Using_Retained_Knowledge_To_Benefit_Adverse_Party",
"Disclose_Existence_Of_Prior_Knowledge_When_Approached_By_Opposing_Party",
"Treat_All_Retained_Case_Information_As_Permanently_Confidential"
],
"proeth:description": "Following termination of the plaintiff engagement, Engineer A continues to hold in memory all technical findings, case strategy information, evidence assessments, and analytical conclusions acquired during the forensic review. This retention of knowledge is an automatic and unavoidable outcome of having performed the engagement, not a volitional act.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "Continuously, from termination of plaintiff engagement through defendant retention",
"proeth:urgencyLevel": "high",
"rdfs:label": "Confidential Knowledge Retained Post-Termination"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: A formal forensic consulting relationship is created between Attorney Z and Engineer A upon hiring
Necessary Factors (NESS):
- Engineer A's volitional decision to accept the retention
- Attorney Z's offer of engagement
- Formation of a formal consulting relationship with attendant duties
Sufficient Factors:
- Engineer A's acceptance + Attorney Z's retention offer = binding professional relationship with confidentiality and loyalty obligations
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Accept Plaintiff Forensic Retention (Action 1)
Engineer A voluntarily agrees to serve as forensic consultant for Attorney Z (plaintiff's counsel) -
Plaintiff Engagement Established (Event 1)
Formal professional relationship is created, triggering duties of confidentiality, loyalty, and competence -
Confidential Knowledge Retained Post-Termination (Event 6)
Engineer A acquires and retains privileged technical and strategic knowledge belonging to Attorney Z's client -
Accept Defendant Attorney Retention (Action 3)
Engineer A agrees to work for the opposing party, bringing retained confidential knowledge into the adverse engagement -
Conflict Of Interest Crystallized (Event 5)
A direct and irresolvable conflict of interest is created, compromising the integrity of both the plaintiff and defendant proceedings
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#CausalChain_a99fb275",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "A formal forensic consulting relationship is created between Attorney Z and Engineer A upon hiring",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A voluntarily agrees to serve as forensic consultant for Attorney Z (plaintiff\u0027s counsel)",
"proeth:element": "Accept Plaintiff Forensic Retention (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Formal professional relationship is created, triggering duties of confidentiality, loyalty, and competence",
"proeth:element": "Plaintiff Engagement Established (Event 1)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A acquires and retains privileged technical and strategic knowledge belonging to Attorney Z\u0027s client",
"proeth:element": "Confidential Knowledge Retained Post-Termination (Event 6)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A agrees to work for the opposing party, bringing retained confidential knowledge into the adverse engagement",
"proeth:element": "Accept Defendant Attorney Retention (Action 3)",
"proeth:step": 4
},
{
"proeth:description": "A direct and irresolvable conflict of interest is created, compromising the integrity of both the plaintiff and defendant proceedings",
"proeth:element": "Conflict Of Interest Crystallized (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Accept Plaintiff Forensic Retention (Action 1)",
"proeth:counterfactual": "Without Engineer A\u0027s acceptance, no formal engagement would exist, no confidential information would be shared, and no subsequent conflict could arise from this relationship",
"proeth:effect": "Plaintiff Engagement Established (Event 1)",
"proeth:necessaryFactors": [
"Engineer A\u0027s volitional decision to accept the retention",
"Attorney Z\u0027s offer of engagement",
"Formation of a formal consulting relationship with attendant duties"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Engineer A\u0027s acceptance + Attorney Z\u0027s retention offer = binding professional relationship with confidentiality and loyalty obligations"
],
"proeth:withinAgentControl": true
}
Causal Language: Attorney Z ends Engineer A's forensic consulting engagement after receiving the adverse findings
Necessary Factors (NESS):
- Engineer A's independent technical conclusion that fault lay with the plaintiff
- Attorney Z's receipt of findings adverse to the plaintiff's legal position
- Attorney Z's decision that Engineer A's testimony would be unhelpful or harmful to the case
Sufficient Factors:
- Adverse technical findings + Attorney Z's strategic litigation interest = termination of engagement as the predictable consequence
Responsibility Attribution:
Agent: Engineer A (for the finding); Attorney Z (for the termination decision)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Plaintiff Engagement Established (Event 1)
Engineer A is formally retained and begins independent technical review -
Analysis Points To Plaintiff Fault (Event 2)
Engineer A's objective review produces conclusions adverse to the plaintiff's legal position -
Decline Favorable Plaintiff Report (Action 2)
Engineer A, bound by professional honesty, declines to produce a report favorable to the plaintiff -
Engineer A Services Terminated (Event 3)
Attorney Z terminates the engagement upon receiving adverse findings, setting the stage for the subsequent conflict -
Termination Circumstances Become Known (Event 4)
Attorney X learns of the termination circumstances, creating the opportunity to recruit Engineer A to the opposing side
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#CausalChain_57b5418b",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Attorney Z ends Engineer A\u0027s forensic consulting engagement after receiving the adverse findings",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A is formally retained and begins independent technical review",
"proeth:element": "Plaintiff Engagement Established (Event 1)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A\u0027s objective review produces conclusions adverse to the plaintiff\u0027s legal position",
"proeth:element": "Analysis Points To Plaintiff Fault (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A, bound by professional honesty, declines to produce a report favorable to the plaintiff",
"proeth:element": "Decline Favorable Plaintiff Report (Action 2)",
"proeth:step": 3
},
{
"proeth:description": "Attorney Z terminates the engagement upon receiving adverse findings, setting the stage for the subsequent conflict",
"proeth:element": "Engineer A Services Terminated (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "Attorney X learns of the termination circumstances, creating the opportunity to recruit Engineer A to the opposing side",
"proeth:element": "Termination Circumstances Become Known (Event 4)",
"proeth:step": 5
}
],
"proeth:cause": "Decline Favorable Plaintiff Report (Action 2)",
"proeth:counterfactual": "Had Engineer A produced findings favorable to the plaintiff, termination would not have occurred and the subsequent conflict of interest chain would not have been initiated",
"proeth:effect": "Engineer A Services Terminated (Event 3)",
"proeth:necessaryFactors": [
"Engineer A\u0027s independent technical conclusion that fault lay with the plaintiff",
"Attorney Z\u0027s receipt of findings adverse to the plaintiff\u0027s legal position",
"Attorney Z\u0027s decision that Engineer A\u0027s testimony would be unhelpful or harmful to the case"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (for the finding); Attorney Z (for the termination decision)",
"proeth:sufficientFactors": [
"Adverse technical findings + Attorney Z\u0027s strategic litigation interest = termination of engagement as the predictable consequence"
],
"proeth:withinAgentControl": true
}
Causal Language: Attorney X (defendant's counsel) learns of the circumstances surrounding Engineer A's termination by Attorney Z
Necessary Factors (NESS):
- Attorney X's knowledge that Engineer A had been terminated after producing adverse findings for the plaintiff
- Attorney X's inference that Engineer A possessed confidential technical knowledge about the plaintiff's case
- Engineer A's willingness to accept the new retention despite the prior relationship
Sufficient Factors:
- Attorney X's knowledge of termination + Engineer A's availability + Engineer A's failure to recognize the conflict = sufficient conditions for the adverse retention to occur
Responsibility Attribution:
Agent: Engineer A (primary); Attorney X (contributing)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Engineer A Services Terminated (Event 3)
Termination creates Engineer A's availability and makes the circumstances of his prior engagement known -
Termination Circumstances Become Known (Event 4)
Attorney X learns that Engineer A holds adverse technical findings and confidential knowledge about the plaintiff's case -
Accept Defendant Attorney Retention (Action 3)
Engineer A agrees to work for Attorney X without conducting a conflict check or notifying Attorney Z -
Omit Disclosure to Former Client (Action 4)
Engineer A fails to seek informed consent from Attorney Z, compounding the ethical breach -
Conflict Of Interest Crystallized (Event 5)
The irresolvable conflict of interest is fully realized, threatening the integrity of the litigation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#CausalChain_c60c2500",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Attorney X (defendant\u0027s counsel) learns of the circumstances surrounding Engineer A\u0027s termination by Attorney Z",
"proeth:causalSequence": [
{
"proeth:description": "Termination creates Engineer A\u0027s availability and makes the circumstances of his prior engagement known",
"proeth:element": "Engineer A Services Terminated (Event 3)",
"proeth:step": 1
},
{
"proeth:description": "Attorney X learns that Engineer A holds adverse technical findings and confidential knowledge about the plaintiff\u0027s case",
"proeth:element": "Termination Circumstances Become Known (Event 4)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A agrees to work for Attorney X without conducting a conflict check or notifying Attorney Z",
"proeth:element": "Accept Defendant Attorney Retention (Action 3)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A fails to seek informed consent from Attorney Z, compounding the ethical breach",
"proeth:element": "Omit Disclosure to Former Client (Action 4)",
"proeth:step": 4
},
{
"proeth:description": "The irresolvable conflict of interest is fully realized, threatening the integrity of the litigation",
"proeth:element": "Conflict Of Interest Crystallized (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Termination Circumstances Become Known (Event 4)",
"proeth:counterfactual": "Had the termination circumstances remained unknown to Attorney X, or had Engineer A declined the approach, the adverse retention would not have occurred",
"proeth:effect": "Accept Defendant Attorney Retention (Action 3)",
"proeth:necessaryFactors": [
"Attorney X\u0027s knowledge that Engineer A had been terminated after producing adverse findings for the plaintiff",
"Attorney X\u0027s inference that Engineer A possessed confidential technical knowledge about the plaintiff\u0027s case",
"Engineer A\u0027s willingness to accept the new retention despite the prior relationship"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (primary); Attorney X (contributing)",
"proeth:sufficientFactors": [
"Attorney X\u0027s knowledge of termination + Engineer A\u0027s availability + Engineer A\u0027s failure to recognize the conflict = sufficient conditions for the adverse retention to occur"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A fails to consult with or seek the informed consent of Attorney Z (former client) before accepting the adverse engagement, crystallizing a direct and irresolvable conflict of interest
Necessary Factors (NESS):
- Engineer A's prior confidential relationship with Attorney Z
- Engineer A's possession of confidential technical and strategic knowledge
- Engineer A's failure to disclose the new engagement to the former client
- Engineer A's acceptance of the adverse retention without informed consent
Sufficient Factors:
- Prior confidential relationship + adverse new retention + absence of disclosure or consent = irresolvable conflict of interest as a matter of professional ethics
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Plaintiff Engagement Established (Event 1)
Confidential relationship and duties are created between Engineer A and Attorney Z -
Confidential Knowledge Retained Post-Termination (Event 6)
Engineer A continues to hold all confidential technical and strategic knowledge after termination -
Accept Defendant Attorney Retention (Action 3)
Engineer A accepts the adverse engagement without conflict analysis -
Omit Disclosure to Former Client (Action 4)
Engineer A fails to notify or seek consent from Attorney Z, eliminating any possibility of waiver or remediation -
Conflict Of Interest Crystallized (Event 5)
The direct and irresolvable conflict of interest is fully established, with Engineer A holding confidential plaintiff knowledge while serving the defendant
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#CausalChain_1bbe5522",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A fails to consult with or seek the informed consent of Attorney Z (former client) before accepting the adverse engagement, crystallizing a direct and irresolvable conflict of interest",
"proeth:causalSequence": [
{
"proeth:description": "Confidential relationship and duties are created between Engineer A and Attorney Z",
"proeth:element": "Plaintiff Engagement Established (Event 1)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A continues to hold all confidential technical and strategic knowledge after termination",
"proeth:element": "Confidential Knowledge Retained Post-Termination (Event 6)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A accepts the adverse engagement without conflict analysis",
"proeth:element": "Accept Defendant Attorney Retention (Action 3)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A fails to notify or seek consent from Attorney Z, eliminating any possibility of waiver or remediation",
"proeth:element": "Omit Disclosure to Former Client (Action 4)",
"proeth:step": 4
},
{
"proeth:description": "The direct and irresolvable conflict of interest is fully established, with Engineer A holding confidential plaintiff knowledge while serving the defendant",
"proeth:element": "Conflict Of Interest Crystallized (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Omit Disclosure to Former Client (Action 4)",
"proeth:counterfactual": "Had Engineer A disclosed the approach to Attorney Z and sought informed consent, the conflict might have been waived or Engineer A would have been clearly prohibited from proceeding, preventing the crystallization of the conflict",
"proeth:effect": "Conflict Of Interest Crystallized (Event 5)",
"proeth:necessaryFactors": [
"Engineer A\u0027s prior confidential relationship with Attorney Z",
"Engineer A\u0027s possession of confidential technical and strategic knowledge",
"Engineer A\u0027s failure to disclose the new engagement to the former client",
"Engineer A\u0027s acceptance of the adverse retention without informed consent"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Prior confidential relationship + adverse new retention + absence of disclosure or consent = irresolvable conflict of interest as a matter of professional ethics"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A accepts the characterization of his new engagement as 'separate and independent' without critically evaluating whether the retained confidential knowledge from the prior engagement creates an irresolvable conflict
Necessary Factors (NESS):
- Engineer A's uncritical acceptance of Attorney X's self-serving characterization of the engagement
- Engineer A's failure to apply independent professional judgment to the conflict question
- The objective existence of retained confidential knowledge that cannot be 'unknowed'
- The adversarial relationship between the new client and the former client in the same matter
Sufficient Factors:
- Retained confidential knowledge + same matter + adverse parties + Engineer A's failure to independently assess the conflict = sufficient to crystallize an irresolvable conflict regardless of how the engagement is characterized
Responsibility Attribution:
Agent: Engineer A (primary); Attorney X (contributing through mischaracterization)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Engineer A Services Terminated (Event 3)
Termination creates a false impression that professional obligations to Attorney Z have ended -
Termination Circumstances Become Known (Event 4)
Attorney X approaches Engineer A with a characterization designed to minimize the appearance of conflict -
Fail to Recognize Irresolvable Conflict (Action 5)
Engineer A accepts the 'separate and independent' characterization without independent professional analysis -
Confidential Knowledge Retained Post-Termination (Event 6)
The objective reality that Engineer A holds irremovable confidential knowledge makes the conflict irresolvable regardless of characterization -
Conflict Of Interest Crystallized (Event 5)
The conflict is fully crystallized; Engineer A is now serving the defendant while holding confidential knowledge of the plaintiff's case strategy and technical vulnerabilities
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/172#",
"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/172#CausalChain_9e211ce3",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A accepts the characterization of his new engagement as \u0027separate and independent\u0027 without critically evaluating whether the retained confidential knowledge from the prior engagement creates an irresolvable conflict",
"proeth:causalSequence": [
{
"proeth:description": "Termination creates a false impression that professional obligations to Attorney Z have ended",
"proeth:element": "Engineer A Services Terminated (Event 3)",
"proeth:step": 1
},
{
"proeth:description": "Attorney X approaches Engineer A with a characterization designed to minimize the appearance of conflict",
"proeth:element": "Termination Circumstances Become Known (Event 4)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A accepts the \u0027separate and independent\u0027 characterization without independent professional analysis",
"proeth:element": "Fail to Recognize Irresolvable Conflict (Action 5)",
"proeth:step": 3
},
{
"proeth:description": "The objective reality that Engineer A holds irremovable confidential knowledge makes the conflict irresolvable regardless of characterization",
"proeth:element": "Confidential Knowledge Retained Post-Termination (Event 6)",
"proeth:step": 4
},
{
"proeth:description": "The conflict is fully crystallized; Engineer A is now serving the defendant while holding confidential knowledge of the plaintiff\u0027s case strategy and technical vulnerabilities",
"proeth:element": "Conflict Of Interest Crystallized (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Fail to Recognize Irresolvable Conflict (Action 5)",
"proeth:counterfactual": "Had Engineer A independently and critically evaluated the conflict rather than accepting Attorney X\u0027s characterization, he would have recognized the irresolvable nature of the conflict and declined the engagement, preventing its crystallization",
"proeth:effect": "Conflict Of Interest Crystallized (Event 5)",
"proeth:necessaryFactors": [
"Engineer A\u0027s uncritical acceptance of Attorney X\u0027s self-serving characterization of the engagement",
"Engineer A\u0027s failure to apply independent professional judgment to the conflict question",
"The objective existence of retained confidential knowledge that cannot be \u0027unknowed\u0027",
"The adversarial relationship between the new client and the former client in the same matter"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A (primary); Attorney X (contributing through mischaracterization)",
"proeth:sufficientFactors": [
"Retained confidential knowledge + same matter + adverse parties + Engineer A\u0027s failure to independently assess the conflict = sufficient to crystallize an irresolvable conflict regardless of how the engagement is characterized"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (14)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer A's fee paid in full |
before
Entity1 is before Entity2 |
Attorney X retains Engineer A |
time:before
http://www.w3.org/2006/time#before |
Engineer A's services are terminated and his fee is paid in full. Thereafter, Attorney X, representi... [more] |
| Engineer A hired by Attorney Z |
before
Entity1 is before Entity2 |
Engineer A's review and analysis |
time:before
http://www.w3.org/2006/time#before |
Engineer A is a forensic engineer. He is hired as a consultant by Attorney Z to provide an engineeri... [more] |
| Engineer A's review and analysis |
before
Entity1 is before Entity2 |
Engineer A's services terminated by Attorney Z |
time:before
http://www.w3.org/2006/time#before |
Following Engineer A's review and analysis, Engineer A determines that he cannot provide an engineer... [more] |
| Engineer A's services terminated |
meets
Entity1 ends exactly when Entity2 begins |
Engineer A's fee paid in full |
time:intervalMeets
http://www.w3.org/2006/time#intervalMeets |
Engineer A's services are terminated and his fee is paid in full |
| BER Case 82-2 |
equals
Entity1 and Entity2 have the same start and end times |
BER Case 82-6 |
time:intervalEquals
http://www.w3.org/2006/time#intervalEquals |
During the same term, in BER Case 82-6, this Board ruled |
| Attorney X learns of Engineer A's termination circumstances |
before
Entity1 is before Entity2 |
Attorney X seeks to retain Engineer A |
time:before
http://www.w3.org/2006/time#before |
Attorney X, representing the defendant in the case, learns of the circumstances relating to Engineer... [more] |
| Attorney X seeks to retain Engineer A |
before
Entity1 is before Entity2 |
Engineer A agrees to provide report for Attorney X |
time:before
http://www.w3.org/2006/time#before |
seeks to retain Engineer A to provide an independent and separate engineering and safety analysis re... [more] |
| Engineer A's engagement with Attorney Z |
before
Entity1 is before Entity2 |
Engineer A's engagement with Attorney X |
time:before
http://www.w3.org/2006/time#before |
He is hired as a consultant by Attorney Z... Engineer A's services are terminated... Thereafter, Att... [more] |
| BER Case 74-2 |
before
Entity1 is before Entity2 |
BER Case 76-3 |
time:before
http://www.w3.org/2006/time#before |
In BER Case 76-3, this Board distinguished that case from earlier BER Case 74-2 |
| BER Case 76-3 |
before
Entity1 is before Entity2 |
BER Case 82-2 |
time:before
http://www.w3.org/2006/time#before |
More recently in BER Case 82-2... In BER Case 76-3, this Board distinguished that case from earlier ... [more] |
| Engineer A's access to plaintiff's information |
during
Entity1 occurs entirely within the duration of Entity2 |
Engineer A's first analysis engagement |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
Engineer A throughout his first analysis had access to information, documents, etc., that were made ... [more] |
| Engineer A's duty of trust and loyalty to Attorney Z |
overlaps
Entity1 starts before Entity2 and ends during Entity2 |
Engineer A's engagement with Attorney X |
time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps |
while Engineer A may not currently have a professional relationship with a former client, he still h... [more] |
| Engineer A's termination by Attorney Z |
before
Entity1 is before Entity2 |
Engineer A's ethical transgressions |
time:before
http://www.w3.org/2006/time#before |
Had Engineer A ceased his involvement in the case following the termination of his relationship with... [more] |
| Engineer A's subsequent involvement with Attorney X |
after
Entity1 is after Entity2 |
Engineer A's termination by Attorney Z |
time:after
http://www.w3.org/2006/time#after |
His transgressions were a result of his subsequent involvement with Attorney X |
About Allen Relations & OWL-Time
Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.
Each relation includes both a ProEthica custom property and a
time:* OWL-Time property for maximum compatibility.