{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Accept_Forensic_Engagement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the engagement due to a conflict of interest or insufficient expertise in the specific product domain",
    "Accept the engagement but establish explicit written terms with Attorney X clarifying that the report will reflect objective findings regardless of outcome",
    "Accept the engagement but negotiate scope limitations that Engineer A knows in advance may compromise the completeness of the analysis"
  ],
  "proeth-scenario:characterMotivation": "Engineer A accepts the engagement as a legitimate professional opportunity, motivated by expertise in mechanical failure analysis, professional duty to support the legal system with competent technical testimony, and standard business incentives of forensic consulting work. There is no indication of improper motive at this stage.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would eliminate Engineer A\u0027s subsequent ethical exposure but would deprive the legal process of potentially qualified expertise; another engineer \u2014 possibly less scrupulous \u2014 might be retained instead",
    "Establishing explicit written terms upfront would create a documented ethical baseline, making it easier for Engineer A to later insist on disclosing the data error without Attorney X claiming surprise or breach of the client relationship",
    "Accepting with known scope limitations would be an early ethical failure, pre-loading the engagement with incompleteness and potentially violating the engineer\u0027s duty to issue truthful and complete reports \u2014 foreshadowing the same misconduct seen in Engineer B\u0027s case"
  ],
  "proeth-scenario:decisionSignificance": "Establishes that accepting a forensic engagement is not ethically neutral \u2014 it creates binding professional obligations to honesty, completeness, and integrity that persist throughout the engagement and cannot be waived by the retaining attorney. Students should understand that the moment of acceptance is the moment those obligations attach.",
  "proeth-scenario:ethicalTension": "The duty to provide objective, independent expert analysis exists in tension with the adversarial legal context in which the engineer is retained by one party\u0027s attorney \u2014 raising latent questions about whether advocacy pressures might later compromise objectivity. The engineer must balance serving the client relationship with serving the truth.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The foundation of the entire ethical situation is laid here. If Engineer A performs the work without internalizing the independence obligations of a forensic expert, every subsequent decision is compromised. Public safety, injured parties\u0027 access to accurate technical information, and the integrity of the legal process are all at risk from the outset.",
  "proeth:description": "Engineer A accepts retention by Attorney X to perform forensic engineering investigation and prepare a written report on a mechanical product failure case involving serious injuries. This commitment establishes Engineer A\u0027s professional obligations to perform the work with honesty and integrity.",
  "proeth:foreseenUnintendedEffects": [
    "Assumption of ethical obligations to be truthful regardless of outcome for client",
    "Potential conflict between client advocacy and objective engineering conclusions"
  ],
  "proeth:fulfillsObligation": [
    "Willingness to serve in a professional capacity requiring specialized competence",
    "Acceptance of duty to provide honest and objective forensic engineering services"
  ],
  "proeth:guidedByPrinciple": [
    "Professional integrity",
    "Honesty and truthfulness in professional reports",
    "Competent performance of professional services"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Forensic Expert)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide professional forensic engineering services to Attorney X in support of litigation on behalf of an injured client",
  "proeth:requiresCapability": [
    "Forensic engineering investigation skills",
    "Mechanical failure analysis expertise",
    "Technical report writing",
    "Familiarity with litigation support context"
  ],
  "proeth:temporalMarker": "At the outset, before investigation begins",
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Forensic Engagement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Conduct_Forensic_Investigation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Implement a more rigorous data verification protocol before finalizing analytical conclusions, including cross-checking data sources",
    "Flag data uncertainties or data quality limitations explicitly in the report rather than presenting conclusions without qualification",
    "Request additional time from Attorney X to conduct a more thorough data review before submitting findings"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated to fulfill the professional commitment made upon accepting the engagement \u2014 to conduct a thorough, competent investigation. The reliance on data that later proves inaccurate appears to reflect an inadvertent methodological failure rather than deliberate misconduct, distinguishing this case sharply from Engineer B\u0027s deliberate omissions.",
  "proeth-scenario:consequencesIfAlternative": [
    "More rigorous verification might have caught the data inaccuracy before the report was submitted, avoiding the entire subsequent ethical dilemma \u2014 this is the most consequential preventive alternative",
    "Flagging data uncertainties would have given the report appropriate epistemic humility and potentially softened the impact of later discovering the error, since conclusions would already be qualified rather than stated with false certainty",
    "Requesting more time might have introduced delay into the litigation timeline but could have prevented the submission of a report with flawed conclusions \u2014 a proportionate professional response to genuine uncertainty"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that ethical failures in forensic engineering can arise from inadvertent error as well as deliberate misconduct \u2014 and that the engineer\u0027s response upon discovering the error, not the error itself, is the true ethical test. Students should also learn that rigorous data verification protocols are themselves an ethical obligation, not merely a quality-control preference.",
  "proeth-scenario:ethicalTension": "The duty of technical competence and due diligence in data verification competes with practical constraints of time, access, and the inherent difficulty of forensic investigation. There is also tension between the engineer\u0027s role as a neutral truth-seeker and the subtle pressure of working within an adversarial legal framework where the retaining attorney has a desired outcome.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The accuracy of the forensic conclusions will directly influence settlement negotiations and potentially the outcome of litigation affecting injured parties, the defendant, and the integrity of the legal process. An investigation built on inaccurate data produces conclusions that misrepresent physical reality, regardless of the engineer\u0027s intent.",
  "proeth:description": "Engineer A performs the forensic engineering investigation into the mechanical product failure, basing the analytical work on data that is later discovered to be inaccurate. This is a volitional professional act involving methodological choices about what data to rely upon.",
  "proeth:foreseenUnintendedEffects": [
    "Risk that data sources could be unreliable or incomplete, potentially leading to flawed conclusions"
  ],
  "proeth:fulfillsObligation": [
    "Performed investigation as retained to do",
    "Applied professional engineering judgment to available data"
  ],
  "proeth:guidedByPrinciple": [
    "Objective and thorough investigation",
    "Reliance on accurate and sufficient data",
    "Professional competence and due care"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Forensic Expert)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Thoroughness of data verification vs. timeliness of investigation deliverable",
    "proeth:resolutionReasoning": "Engineer A proceeded with available data in good faith; the ethical weight of this decision becomes significant only upon subsequent discovery of inaccuracy"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Determine the cause of the mechanical product failure through rigorous investigation and produce defensible engineering conclusions",
  "proeth:requiresCapability": [
    "Mechanical failure analysis",
    "Data evaluation and interpretation",
    "Forensic engineering methodology",
    "Root cause analysis"
  ],
  "proeth:temporalMarker": "After retention, before report submission",
  "proeth:violatesObligation": [
    "Retrospectively, reliance on inaccurate data without sufficient verification may implicate duty of due diligence, though no bad faith is indicated at this stage"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Conduct Forensic Investigation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Submit_Report_to_Attorney",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct a final internal peer review of the report and underlying data before submission to catch potential errors",
    "Submit the report with explicit statements about the confidence level and limitations of the data upon which conclusions are based",
    "Deliver the report orally first to Attorney X, walking through the data and methodology, before formal written submission \u2014 allowing for collaborative identification of potential weaknesses"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated to fulfill the contracted deliverable \u2014 producing and submitting the written report \u2014 and to provide Attorney X with the technical foundation needed to proceed with litigation or settlement. At the moment of submission, Engineer A presumably believes the report is accurate and complete, making this a good-faith professional act.",
  "proeth-scenario:consequencesIfAlternative": [
    "A pre-submission peer review is the most straightforward preventive measure and represents best practice in forensic engineering; it might have identified the data inaccuracy before the report entered the legal process",
    "Explicit confidence and limitation statements would not have prevented the error but would have signaled to Attorney X that the conclusions were contingent on data quality, making the subsequent disclosure of the error less disruptive to the legal strategy",
    "An oral preliminary delivery might have prompted Attorney X to ask probing questions about the data that could have surfaced the inaccuracy earlier, though it also risks the attorney attempting to shape the report\u0027s conclusions \u2014 a separate ethical hazard"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that the act of formally submitting a professional report is a significant threshold event that increases the stakes of any subsequent error discovery. Students should understand that submission creates reliance and that the engineer\u0027s duty of honesty does not terminate at submission \u2014 it extends to correcting errors discovered afterward, especially when the report is still actively influencing legal proceedings.",
  "proeth-scenario:ethicalTension": "Submitting the report formally introduces it into the legal process, creating reliance by the attorney and potentially shaping the trajectory of settlement negotiations. This transition from private analysis to legal instrument heightens the ethical weight of any subsequent discovery of error \u2014 the report is no longer just Engineer A\u0027s working document but a professional representation made to the legal system.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Once submitted, the report becomes the technical basis for Attorney X\u0027s negotiating position. If the report contains conclusions based on inaccurate data, settlement negotiations may proceed on a false technical premise \u2014 potentially resulting in an unjust settlement that either over- or under-compensates the injured parties and misrepresents the defendant\u0027s actual liability.",
  "proeth:description": "Engineer A prepares and submits the written forensic report, including conclusions about the cause of the accident, to Attorney X for use in litigation. This is a definitive professional act that places the report into the legal process.",
  "proeth:foreseenUnintendedEffects": [
    "Report will be relied upon by Attorney X in settlement negotiations",
    "If conclusions are later found to be flawed, the report could mislead the legal process"
  ],
  "proeth:fulfillsObligation": [
    "Delivered professional report as contracted",
    "Provided written conclusions as required by the engagement"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and truthfulness in professional reports",
    "Completeness and accuracy of engineering findings",
    "Integrity in litigation support services"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Forensic Expert)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Deliver professional findings to Attorney X to support the litigation and potential settlement negotiations on behalf of the injured client",
  "proeth:requiresCapability": [
    "Technical report writing",
    "Clear communication of engineering conclusions",
    "Understanding of litigation report standards"
  ],
  "proeth:temporalMarker": "After investigation, before settlement negotiations conclude",
  "proeth:withinCompetence": true,
  "rdfs:label": "Submit Report to Attorney"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Disclose_Data_Inaccuracy_to_Attorney",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Remain silent and allow settlement negotiations to conclude, rationalizing that the error may not have changed the ultimate outcome or that it is now too late to act",
    "Disclose the error to Attorney X but agree to Attorney X\u0027s request to withhold the correction from opposing counsel until after settlement is finalized",
    "Withdraw from the engagement entirely without disclosing the specific nature of the error, leaving Attorney X to draw their own conclusions"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated \u2014 and, per the Board\u0027s ruling, obligated \u2014 by the foundational engineering ethics principle that engineers shall be objective and truthful in professional reports and shall not misrepresent facts. The discovery of the data error creates an immediate professional duty that supersedes the engineer\u0027s interest in avoiding embarrassment, professional inconvenience, or disruption to the attorney-client relationship.",
  "proeth-scenario:consequencesIfAlternative": [
    "Remaining silent would constitute a serious ethical violation equivalent to the Board\u0027s condemnation of Engineer B \u2014 Engineer A would be knowingly allowing a legal process to proceed on a false technical foundation, exposing themselves to professional discipline, potential civil liability, and lasting reputational harm",
    "Disclosing to Attorney X but agreeing to suppress the correction from opposing counsel would be a partial ethical failure \u2014 Engineer A would have fulfilled a narrow duty to the client while violating the broader duty to the integrity of the legal process; this arrangement would likely itself constitute an ethical violation",
    "Withdrawing without disclosure would be an ethically evasive action that protects Engineer A from direct complicity but fails the affirmative duty to correct the record \u2014 the Board\u0027s ruling implies that passive withdrawal is insufficient when the engineer holds material corrective information that is actively needed by the ongoing legal process"
  ],
  "proeth-scenario:decisionSignificance": "This is the central teaching moment of the entire case. The Board\u0027s ruling establishes that the duty to correct material errors in a forensic report is immediate, affirmative, and non-waivable \u2014 it cannot be deferred until after settlement, and the engineer cannot remain silent simply because disclosure is inconvenient or professionally uncomfortable. Students must understand that professional ethics obligations run to the truth and the public, not solely to the retaining client.",
  "proeth-scenario:ethicalTension": "The most acute ethical tension in the entire case: the duty of honesty and accuracy to the public and the legal system directly conflicts with loyalty to the retaining client (Attorney X), fear of professional embarrassment or liability for having submitted an inaccurate report, and concern that disclosure will disrupt or collapse ongoing settlement negotiations. There is also tension between the engineer\u0027s role as a retained expert and the engineer\u0027s independent professional obligations that exist regardless of client preferences.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Maximum stakes across every dimension: the integrity of the legal process, the just resolution of a case involving serious injuries, Engineer A\u0027s professional license and reputation, Attorney X\u0027s ability to negotiate from an accurate factual basis, the defendant\u0027s right not to be held liable based on false technical conclusions, and the broader public trust in forensic engineering as a discipline. Silence here is not neutral \u2014 it is active participation in a potentially unjust outcome.",
  "proeth:description": "Upon discovering that the data underlying the report was inaccurate and that corrected data would yield different conclusions, Engineer A faces the decision \u2014 identified by the Board as an affirmative obligation \u2014 to immediately notify Attorney X of the error while settlement negotiations are still ongoing. This is the central ethical action point of the case.",
  "proeth:foreseenUnintendedEffects": [
    "May undermine or collapse Attorney X\u0027s negotiating position in ongoing settlement",
    "May harm the interests of Attorney X\u0027s injured client in the short term",
    "Could expose Engineer A to professional or legal consequences for the initial inaccuracy",
    "Corrected conclusions may favor the defendant, disadvantaging the party Engineer A was retained to support"
  ],
  "proeth:fulfillsObligation": [
    "Affirmative duty of honesty and truthfulness in professional reports and findings",
    "Obligation to correct materially false or misleading information Engineer A has placed into the legal process",
    "Duty to protect the integrity of the legal process",
    "NSPE Code obligation to be truthful and not misrepresent engineering findings"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and integrity as foundational engineering ethics obligations",
    "Truthfulness in professional reports",
    "Objectivity independent of client interest",
    "Affirmative duty to correct known errors",
    "Protection of the integrity of the legal and engineering professions"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer / Forensic Expert)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional obligation to honesty and disclosure vs. duty to client and risk of disrupting ongoing settlement negotiations",
    "proeth:resolutionReasoning": "The Board concludes that Engineer A has an affirmative and immediate obligation to disclose; the integrity of the engineering profession and the legal process cannot be subordinated to client litigation strategy; the precedent of BER Case 95-5 establishes that selective use or suppression of data to favor a client is an egregious ethical violation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Correct the record by informing Attorney X that the report conclusions were based on inaccurate data and would differ under accurate data, ensuring the legal process is not misled",
  "proeth:requiresCapability": [
    "Professional judgment to recognize materiality of data inaccuracy",
    "Courage to disclose findings adverse to client interest",
    "Clear communication of technical error and its implications to a non-engineer attorney",
    "Ability to reassess and revise engineering conclusions based on corrected data"
  ],
  "proeth:temporalMarker": "After report submission, before settlement negotiations conclude \u2014 the critical ethical decision point",
  "proeth:violatesObligation": [
    "If disclosure is withheld: obligation of honesty and integrity in professional reports",
    "If disclosure is withheld: obligation not to allow false or misleading engineering conclusions to stand in legal proceedings",
    "If disclosure is withheld: duty to public safety and welfare over client interest"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Disclose Data Inaccuracy to Attorney"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Exclude_Pile_Driving_Records_from_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Include all pile driving records in the report and address the contradicting data explicitly, explaining why Engineer B nonetheless reached the conclusions stated",
    "Disclose the contradicting data to the retaining attorney and allow the attorney to decide how to proceed, rather than making the suppression decision unilaterally",
    "Withdraw from the engagement upon recognizing that the available data did not support the conclusions the retaining party sought"
  ],
  "proeth-scenario:characterMotivation": "Engineer B appears motivated by a desire to produce a report that supports a predetermined conclusion favorable to the retaining party, whether driven by client pressure, financial incentive to maintain the client relationship, or a cognitive bias toward confirming an initial hypothesis. The deliberate exclusion of contradicting data \u2014 pile driving records showing refusal and wave equation calculations showing adequate strength \u2014 suggests conscious awareness that the omitted information would undermine the report\u0027s conclusions.",
  "proeth-scenario:consequencesIfAlternative": [
    "Including all data and addressing contradictions would have produced a complete, defensible report \u2014 even if the ultimate conclusions remained the same, the engineer\u0027s credibility and ethical standing would be preserved; the retaining attorney would have had to build their legal strategy on an honest technical foundation",
    "Disclosing the contradicting data to the attorney and deferring the decision would partially transfer ethical responsibility but would not fully discharge Engineer B\u0027s independent professional duty \u2014 the engineer cannot delegate the obligation of completeness to the client",
    "Withdrawing upon recognizing the data conflict would have been the most ethically protective course for Engineer B personally and would have prevented the production of a misleading report, though it would not have corrected the situation for the parties already affected by the litigation"
  ],
  "proeth-scenario:decisionSignificance": "Provides the negative precedent against which Engineer A\u0027s situation is measured. Students should understand that selective data presentation in forensic engineering is not a gray area \u2014 it is a fundamental violation of the engineer\u0027s duty of objectivity, equivalent to falsification of a professional report. The case illustrates how omission can be as ethically culpable as affirmative misrepresentation.",
  "proeth-scenario:ethicalTension": "The tension between serving the retaining client\u0027s litigation interests and the engineer\u0027s independent duty to present complete, objective findings. Engineer B\u0027s conduct represents the complete collapse of this tension in favor of client advocacy at the expense of professional integrity \u2014 the antithesis of the forensic engineer\u0027s proper role.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The omitted pile driving records and wave equation calculations were material to the central question of the litigation \u2014 whether the 19 disputed piles were structurally adequate. By excluding this data, Engineer B potentially exposed the defendant to liability based on an incomplete and misleading technical analysis, while simultaneously undermining the reliability of forensic engineering testimony in construction litigation generally.",
  "proeth:description": "Engineer B deliberately omitted from the concluding report the fact that the 19 disputed piles had been driven to essential refusal and that wave equation calculations would indicate their strength exceeded load requirements by several multiples \u2014 data that materially contradicted the report\u0027s conclusions. This selective exclusion was a volitional professional decision to present incomplete findings.",
  "proeth:foreseenUnintendedEffects": [
    "Report would present a misleading picture of pile adequacy by omitting data showing piles met strength requirements by a significant margin",
    "Opposing party and the legal process would be deprived of materially relevant engineering information"
  ],
  "proeth:guidedByPrinciple": [
    "Completeness and objectivity in engineering reporting",
    "Honesty and integrity as non-negotiable professional standards",
    "Independence of engineering judgment from client advocacy"
  ],
  "proeth:hasAgent": "Engineer B (Professional Engineer / Expert retained by municipality)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client defense advocacy vs. complete and objective engineering reporting",
    "proeth:resolutionReasoning": "Engineer B resolved the conflict by prioritizing client defense, which the Board explicitly condemned as an assumption of responsibility to defend the client through selective use of data \u2014 an egregious denial of professional duties"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Produce a report supporting the client municipality\u0027s litigation position by concluding that 19 piles did not meet safety factor requirements, without including contradictory pile driving record data",
  "proeth:requiresCapability": [
    "Pile foundation analysis",
    "Wave equation calculation methodology",
    "Forensic geotechnical engineering",
    "Objective interpretation of pile driving records"
  ],
  "proeth:temporalMarker": "During report preparation in BER Case 95-5 parallel, before report issuance",
  "proeth:violatesObligation": [
    "Obligation to be truthful and complete in professional engineering reports",
    "Obligation not to selectively use data to favor a client",
    "Duty to include all materially relevant data in forensic engineering findings",
    "Obligation to avoid deceptive or misleading professional reports",
    "Duty to the integrity of the legal process as an engineering expert"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Exclude Pile Driving Records from Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Omit_Dynamic_Test_Equipment_Failure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose the equipment failure prominently in the report\u0027s methodology section and qualify all conclusions accordingly, noting the reduced reliability of results obtained during the failure period",
    "Retest the affected piles using functioning equipment before finalizing the report, ensuring that conclusions rest on reliable data",
    "Disclose the equipment failure to the retaining attorney and recommend that the affected test results be excluded from the report\u0027s evidentiary basis"
  ],
  "proeth-scenario:characterMotivation": "Engineer B chose not to disclose the equipment failure likely to prevent the retaining party from losing confidence in the test results and to avoid having the report\u0027s conclusions challenged on reliability grounds. This motivation prioritizes the appearance of methodological soundness over the reality of it \u2014 a form of professional deception that serves the client\u0027s litigation position at the expense of factual accuracy.",
  "proeth-scenario:consequencesIfAlternative": [
    "Disclosing and qualifying the conclusions would have produced a more limited but honest report \u2014 the retaining attorney would have had to work with qualified findings, but Engineer B\u0027s professional integrity would have been preserved and the report would have been defensible under cross-examination",
    "Retesting would have been the most thorough and professionally sound response, ensuring the conclusions rested on reliable data \u2014 though it would have required additional time and expense and might have produced results unfavorable to the retaining party",
    "Disclosing to the attorney and recommending exclusion of affected results would have been honest but incomplete \u2014 it would have protected Engineer B from direct complicity in the omission while still leaving the strategic decision to the attorney; the better course would be to insist on disclosure in the report itself"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that the duty of completeness in forensic engineering reports extends specifically to methodological limitations and equipment failures \u2014 not just to the substantive data collected. Students should learn that a forensic report must disclose anything that would affect a reasonable reader\u0027s assessment of the reliability of the conclusions, including failures in the testing apparatus itself.",
  "proeth-scenario:ethicalTension": "The duty to report material facts affecting the reliability of test results \u2014 a core obligation of scientific and engineering integrity \u2014 conflicts with the practical consequence that disclosure would undermine the report\u0027s usefulness to the retaining party. Engineer B resolved this tension in the ethically impermissible direction, treating the report as an advocacy document rather than an objective technical analysis.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The equipment failure was not a peripheral detail \u2014 it went to the foundational reliability of the dynamic pile testing upon which the report\u0027s conclusions rested. Omitting this fact meant that attorneys, opposing experts, and potentially a court or jury would evaluate the report\u0027s conclusions without knowing that the testing methodology itself had been compromised. This is a direct threat to the integrity of the fact-finding process.",
  "proeth:description": "Engineer B chose not to disclose in the report that the dynamic test equipment had failed during the pile testing, a material fact that undermined the reliability of the test results upon which the report\u0027s conclusions were based. This omission was a deliberate professional decision affecting the completeness and accuracy of the report.",
  "proeth:foreseenUnintendedEffects": [
    "Legal proceedings and opposing parties would rely on test results without knowing the equipment had failed",
    "The reliability and validity of the entire testing program would be misrepresented"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency regarding limitations of engineering analysis and testing",
    "Honesty in reporting testing conditions and results",
    "Objectivity and completeness as core forensic engineering standards"
  ],
  "proeth:hasAgent": "Engineer B (Professional Engineer / Expert retained by municipality)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client litigation interest in valid-appearing test results vs. professional obligation to disclose known testing failures",
    "proeth:resolutionReasoning": "Engineer B chose to omit the equipment failure, prioritizing the appearance of reliable test results over the obligation of complete disclosure; this was condemned by the Board as part of an egregious ethical violation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Present test results as valid and reliable in support of the conclusion that 19 piles were deficient, without disclosing the equipment failure that compromised the testing",
  "proeth:requiresCapability": [
    "Dynamic pile testing methodology",
    "Recognition and documentation of equipment failures during testing",
    "Geotechnical engineering judgment regarding test validity"
  ],
  "proeth:temporalMarker": "During report preparation in BER Case 95-5 parallel, before report issuance",
  "proeth:violatesObligation": [
    "Obligation to disclose material limitations and failures in testing methodology",
    "Duty of completeness and accuracy in professional engineering reports",
    "Obligation not to present test results without disclosing known factors that compromise their reliability",
    "Duty to the integrity of the legal process"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Omit Dynamic Test Equipment Failure"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Action_Decline_to_Consult_Available_Witnesses",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct structured interviews with all available on-site witnesses as a standard component of the forensic investigation protocol, documenting their accounts regardless of whether they support or contradict the emerging analytical conclusions",
    "Consult the witnesses but selectively report only those accounts that support the report\u0027s conclusions \u2014 a partial improvement over complete avoidance but still ethically deficient",
    "Acknowledge in the report that witness interviews were not conducted and explain the reason, allowing readers to assess the completeness of the investigation for themselves"
  ],
  "proeth-scenario:characterMotivation": "Engineer B\u0027s decision not to consult available witnesses \u2014 on-site representatives, contractors, and workers \u2014 likely reflects a motivation to avoid information that might contradict the report\u0027s predetermined conclusions. Witnesses with direct knowledge of why the 19 piles met driving refusal before reaching predicted depth could have provided explanations that undermined Engineer B\u0027s theory of inadequacy. Avoiding them preserved the analytical narrative Engineer B was constructing.",
  "proeth-scenario:consequencesIfAlternative": [
    "Conducting thorough witness interviews would have been the professionally correct course and might have produced a more accurate understanding of the pile behavior \u2014 even if the resulting report was less favorable to the retaining party, it would have reflected a genuine forensic investigation rather than a litigation support exercise",
    "Selectively reporting witness accounts would represent an improvement in investigative thoroughness but would replicate the same ethical failure as the data omissions \u2014 partial disclosure designed to support a predetermined conclusion is not meaningfully different from complete omission",
    "Acknowledging the omission of witness interviews in the report would at least have been transparent about the investigation\u0027s limitations, allowing opposing counsel and the court to assess the completeness of the analysis \u2014 this is ethically superior to silent omission but still falls short of the duty of thoroughness that requires actually conducting the interviews"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that the forensic engineer\u0027s duty of thoroughness is not satisfied by collecting only favorable evidence. The deliberate avoidance of available witnesses who could provide material information is itself an ethical violation \u2014 it is a form of willful ignorance that corrupts the investigative process. Students should understand that a competent forensic investigation requires actively seeking contradicting information, not just confirming evidence.",
  "proeth-scenario:ethicalTension": "The duty of thoroughness and due diligence in forensic investigation \u2014 which requires seeking out all reasonably available sources of relevant information \u2014 conflicts with the strategic interest in not discovering facts that complicate or contradict the desired conclusion. This tension exposes a fundamental incompatibility between the forensic engineer\u0027s role as objective investigator and any role as partisan advocate.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "The witnesses Engineer B declined to consult may have held the key to understanding why the piles behaved as they did \u2014 information that was directly relevant to the central question of the litigation. By forgoing this testimony, Engineer B produced conclusions that were not only incomplete but potentially based on a false theory of causation. The parties to the litigation, and ultimately the legal process itself, were deprived of potentially dispositive factual information.",
  "proeth:description": "Engineer B made a deliberate decision not to consult Engineer A\u0027s on-site representatives, contractors, workers, or other available witnesses who could have verified or refuted theories about why the 19 piles met driving refusal before reaching predicted depth. This decision to forgo available corroborating or contradicting testimony was a volitional professional choice.",
  "proeth:foreseenUnintendedEffects": [
    "Report conclusions would be based on incomplete information, excluding perspectives that could have materially altered findings",
    "Engineer B\u0027s theories about pile behavior would remain untested against available firsthand knowledge"
  ],
  "proeth:guidedByPrinciple": [
    "Thoroughness and due diligence in forensic investigation",
    "Objectivity requiring active consideration of contradictory evidence",
    "Professional responsibility to seek complete information before rendering conclusions"
  ],
  "proeth:hasAgent": "Engineer B (Professional Engineer / Expert retained by municipality)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Scope-of-work and client-defined task boundaries vs. professional obligation to conduct a thorough and complete forensic investigation",
    "proeth:resolutionReasoning": "Engineer B resolved the conflict by deferring to scope limitations and apparent disbelief in the driving records, avoiding testimony that could contradict the intended conclusions; the Board\u0027s condemnation indicates this resolution was ethically impermissible"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Complete the report without engaging with witnesses whose testimony might contradict or complicate the conclusions Engineer B intended to reach in support of the municipality",
  "proeth:requiresCapability": [
    "Forensic investigation methodology including witness consultation",
    "Ability to evaluate conflicting accounts of construction conditions",
    "Professional judgment about what information is material to engineering conclusions"
  ],
  "proeth:temporalMarker": "During investigation and report preparation in BER Case 95-5 parallel, before report issuance",
  "proeth:violatesObligation": [
    "Duty of due diligence in forensic engineering investigation",
    "Obligation to seek out and consider all materially relevant information before drawing conclusions",
    "Duty to test theories against available evidence and witnesses",
    "Obligation to perform a complete and thorough forensic investigation"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Decline to Consult Available Witnesses"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Event_Report_Successfully_Submitted",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does an engineer\u0027s ethical responsibility for a report end at submission, or does it persist? Why?",
    "What professional norms govern what an engineer must verify before submitting a forensic report?",
    "How does the legal context of forensic work change the ethical weight of submitting a report?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A feels professional satisfaction and closure; Attorney X feels equipped to proceed; both parties are unaware of impending complication \u2014 a false sense of security pervades this moment",
  "proeth-scenario:ethicalImplications": "Reveals the tension between treating report submission as a transactional deliverable versus understanding it as an ongoing professional commitment; establishes that accuracy obligations do not terminate upon delivery",
  "proeth-scenario:learningMoment": "Submission of a professional report is not merely an administrative act \u2014 it is a professional commitment to accuracy that carries ongoing ethical obligations. The moment of submission activates a duty to monitor and correct.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "Gains a foundational document for settlement strategy; begins relying on conclusions in good faith",
    "defendant": "Faces an expert report that will shape negotiation dynamics",
    "engineer_a": "Professional reputation formally attached to report conclusions; accountability window opens",
    "public_legal_system": "A document enters the legal process that, unknown to all, contains inaccurate underlying data"
  },
  "proeth:activatesConstraint": [
    "Accuracy_Of_Public_Statements_Constraint",
    "Professional_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/107#Action_Submit_Report_to_Attorney",
  "proeth:causesStateChange": "Report is now in Attorney X\u0027s possession; conclusions are active in the legal proceeding; Engineer A\u0027s professional credibility is formally attached to the document",
  "proeth:createsObligation": [
    "Monitor_Report_Accuracy_Obligation",
    "Correct_Errors_If_Discovered_Obligation",
    "Support_Attorney_With_Accurate_Information_Obligation"
  ],
  "proeth:description": "Engineer A\u0027s written forensic report with conclusions is received by Attorney X, formally entering the legal record and initiating its use in settlement negotiations.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After forensic investigation is complete; before settlement negotiations begin",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Report Successfully Submitted"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Event_Settlement_Negotiations_Commenced",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should engineers be notified when their reports enter active legal use? Does it matter ethically?",
    "How does the fact that negotiations are ongoing change the urgency of correcting a discovered error?",
    "Who bears responsibility if a settlement is reached based on inaccurate expert conclusions?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Attorney X feels strategic momentum; Engineer A is likely unaware negotiations have begun; defendant\u0027s side feels pressure; the audience senses growing stakes as inaccurate data now underlies an active legal process",
  "proeth-scenario:ethicalImplications": "Highlights how professional work product escapes the professional\u0027s direct control once submitted, yet the ethical responsibility does not escape with it; raises questions about the engineer\u0027s duty to the legal system versus duty to the retaining attorney",
  "proeth-scenario:learningMoment": "Expert reports do not sit inert after submission \u2014 they actively shape legal proceedings. Engineers must understand that their work product enters a dynamic environment where errors compound over time.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "Committed to a negotiation strategy built on potentially flawed conclusions; vulnerable to embarrassment or malpractice if error surfaces later",
    "defendant": "May be pressured toward settlement based on inaccurate expert conclusions \u2014 either overpaying or being wrongly exculpated",
    "engineer_a": "Report is now doing active work in the world; professional and legal exposure increases with each negotiation step taken on its basis",
    "legal_system": "Integrity of settlement process is at risk if inaccurate data underlies negotiating positions"
  },
  "proeth:activatesConstraint": [
    "Do_Not_Mislead_Legal_Proceedings_Constraint",
    "Accuracy_Of_Expert_Evidence_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/107#Action_Submit_Report_to_Attorney",
  "proeth:causesStateChange": "Report conclusions are now actively influencing a live legal negotiation; any inaccuracy in the report is no longer merely a professional error but a potential corruption of the legal process; time pressure on error correction intensifies",
  "proeth:createsObligation": [
    "Ensure_Report_Remains_Accurate_While_In_Active_Use_Obligation"
  ],
  "proeth:description": "Attorney X enters formal settlement negotiations with the defendant\u0027s attorney, using Engineer A\u0027s submitted report as a foundational document, creating a live legal proceeding dependent on the report\u0027s accuracy.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After report submission; before settlement is concluded",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Settlement Negotiations Commenced"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Event_Data_Inaccuracy_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What factors might tempt Engineer A to remain silent, and how should the profession\u0027s ethical codes address those temptations?",
    "Does it matter whether the data inaccuracy was Engineer A\u0027s fault or an exogenous error? Why or why not?",
    "How does the ongoing nature of the settlement negotiations change the ethical calculus compared to a scenario where settlement had already concluded?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences alarm, professional dread, and moral distress \u2014 caught between the discomfort of admitting error and the clear ethical imperative to disclose; Attorney X is unaware and continues negotiating in false confidence; the audience feels the weight of the engineer\u0027s dilemma",
  "proeth-scenario:ethicalImplications": "Reveals the core tension between self-interest (protecting professional reputation, avoiding awkwardness with client) and professional duty (truthfulness, protection of the legal process, and ultimately public welfare); demonstrates that ethical obligations are most demanding precisely when compliance is most costly; raises questions about the nature of professional courage",
  "proeth-scenario:learningMoment": "This is the central ethical turning point of the case. The discovery of error after submission \u2014 with negotiations ongoing \u2014 is precisely the scenario where professional codes demand courage over comfort. The NSPE Code\u0027s requirement of truthfulness is not aspirational; it is operationally mandatory in moments like this.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "Is currently negotiating based on false premises; faces potential malpractice exposure if not informed; needs this information to protect client",
    "attorney_xs_client": "May be harmed by a settlement outcome shaped by inaccurate expert conclusions",
    "defendant": "May be wrongly advantaged or disadvantaged depending on direction of error",
    "engineer_a": "Faces immediate reputational risk, potential disciplinary exposure, and profound professional discomfort; must choose between self-protection and ethical duty",
    "engineering_profession": "Public trust in forensic engineering is implicated by how Engineer A responds",
    "legal_system": "Integrity of the proceeding is actively at risk"
  },
  "proeth:activatesConstraint": [
    "Truthfulness_In_Professional_Statements_Constraint",
    "Do_Not_Mislead_Legal_Proceedings_Constraint",
    "Affirmative_Duty_To_Correct_Public_Statements_Constraint",
    "Public_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/107#Action_Conduct_Forensic_Investigation__underlying_data_co",
  "proeth:causesStateChange": "Engineer A transitions from a state of professional completion to a state of active ethical obligation; the submitted report is retroactively rendered unreliable; all legal proceedings relying on it are compromised; an affirmative duty to act immediately is triggered",
  "proeth:createsObligation": [
    "Immediate_Disclosure_To_Attorney_X_Obligation",
    "Prepare_Corrected_Report_Obligation",
    "Do_Not_Allow_Inaccurate_Report_To_Continue_Influencing_Negotiations_Obligation",
    "Document_Discovery_Of_Error_Obligation"
  ],
  "proeth:description": "Engineer A discovers that the underlying data used in the submitted forensic report was inaccurate and that corrected data would yield materially different conclusions, creating an immediate ethical crisis.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After report submission; after settlement negotiations have begun; before settlement is concluded",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Data Inaccuracy Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Event_Conclusions_Rendered_Invalid",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what threshold of changed conclusions should an engineer feel obligated to correct a report \u2014 minor nuance, or only material changes?",
    "How does the concept of \u0027professional opinion\u0027 interact with the discovery that the factual basis of that opinion was wrong?",
    "Should the engineering profession have formal protocols for post-submission report corrections, similar to legal errata filings?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A faces the professional equivalent of a ground-shifting moment \u2014 prior work is invalidated; this is experienced as both a professional failure and a moral test; the emotional weight of \u0027undoing\u0027 submitted professional work is significant",
  "proeth-scenario:ethicalImplications": "Exposes the difference between honest error (not unethical in itself) and allowing a known error to persist uncorrected (clearly unethical); demonstrates that professional integrity requires ongoing vigilance, not just diligence at the moment of submission",
  "proeth-scenario:learningMoment": "Professional reports are not permanent once submitted \u2014 they carry an implicit warranty of continued accuracy that the engineer must honor. When that warranty is breached by discovered error, the professional obligation to correct is immediate and non-negotiable.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "The strategic foundation of ongoing negotiations is undermined, though Attorney X does not yet know it",
    "engineer_a": "Prior professional output is invalidated; must confront the possibility of reputational damage and the necessity of professional humility",
    "engineering_profession": "The case becomes a test of whether the profession\u0027s self-correction mechanisms function as designed",
    "legal_proceeding": "The evidentiary basis of the proceeding is compromised"
  },
  "proeth:activatesConstraint": [
    "Engineer_Must_Not_Misrepresent_Facts_Constraint",
    "Affirmative_Duty_To_Correct_Constraint",
    "Prohibition_On_Allowing_False_Statements_To_Stand_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/107#Action_Conduct_Forensic_Investigation__data_collection_ph",
  "proeth:causesStateChange": "The original report transitions from \u0027submitted professional opinion\u0027 to \u0027known-inaccurate document\u0027; Engineer A now holds knowledge that transforms continued silence into active misrepresentation; the report\u0027s legal utility is suspended pending correction",
  "proeth:createsObligation": [
    "Withdraw_Or_Correct_Original_Conclusions_Obligation",
    "Notify_All_Parties_Relying_On_Report_Obligation",
    "Issue_Corrected_Analysis_Obligation"
  ],
  "proeth:description": "As a direct consequence of the data inaccuracy discovery, Engineer A\u0027s original report conclusions are rendered professionally untenable \u2014 they no longer represent Engineer A\u0027s honest expert opinion and cannot ethically be allowed to stand uncorrected.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Simultaneous with Data Inaccuracy Discovered event; before disclosure to Attorney X",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Conclusions Rendered Invalid"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Event_Legal_Process_Integrity_Compromised",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does an engineer acting as a forensic expert have duties to the legal system that can override duties to the retaining attorney? How should these be prioritized?",
    "If Engineer A remains silent and settlement is reached, who has been harmed and who bears moral responsibility?",
    "How does the concept of \u0027complicity by silence\u0027 apply to professional ethics, and where is the line between passivity and active wrongdoing?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A bears the psychological burden of knowing the legal process is compromised while Attorney X and opposing counsel proceed in ignorance; this creates acute moral distress \u2014 the engineer is effectively a silent participant in a proceeding built on false foundations",
  "proeth-scenario:ethicalImplications": "Reveals the multi-stakeholder nature of forensic engineering ethics \u2014 the engineer\u0027s duties extend beyond the client relationship to the broader legal system and public interest; demonstrates how inaction can itself become an ethical violation; raises questions about the limits of attorney-client privilege and confidentiality when they shield material errors",
  "proeth-scenario:learningMoment": "Engineers serving as expert witnesses or forensic consultants have duties not only to their retaining attorney but to the integrity of the legal process itself. Silence in the face of known error is not neutrality \u2014 it is participation in deception.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "attorney_x": "Unknowingly advancing a flawed case; professional duty to client is undermined by reliance on inaccurate expert opinion",
    "both_parties_clients": "Risk financial and legal outcomes shaped by inaccurate technical conclusions",
    "defendant_and_counsel": "May reach a settlement that does not reflect the actual facts of the case",
    "engineer_a": "Each moment of continued silence increases ethical and potential legal exposure",
    "legal_system": "Settlement, if reached, may be challenged or may produce unjust outcomes"
  },
  "proeth:activatesConstraint": [
    "Do_Not_Participate_In_Deception_Of_Legal_Process_Constraint",
    "Public_Interest_Protection_Constraint",
    "Engineer_Duty_To_Legal_System_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/107#Action_Submit_Report_to_Attorney",
  "proeth:causesStateChange": "The legal proceeding enters a compromised state; every negotiation step taken without correction deepens the compromise; Engineer A\u0027s silence, if prolonged, transitions from omission to complicity",
  "proeth:createsObligation": [
    "Act_Before_Settlement_Concludes_Obligation",
    "Protect_Integrity_Of_Legal_Proceeding_Obligation"
  ],
  "proeth:description": "With inaccurate expert conclusions actively influencing ongoing settlement negotiations, the integrity of the legal proceeding is objectively compromised \u2014 parties are negotiating based on false premises without their knowledge.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "From the moment data inaccuracy is discovered while negotiations are ongoing; persists until disclosure is made",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Legal Process Integrity Compromised"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#Event_Precedent_Case_Ethical_Violation_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How is Engineer A\u0027s situation similar to and different from Engineer B\u0027s? Does the similarity justify applying the same ethical standard?",
    "Why does the Board characterize selective data use as \u0027egregious\u0027 rather than merely \u0027problematic\u0027? What values are at stake?",
    "Should the existence of a precedent case change how Engineer A feels morally obligated to act, or should the ethical obligation exist independently of precedent?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "For students and practitioners, the precedent case creates a sense of professional accountability \u2014 the Board has spoken clearly; for Engineer A (by analogy), the precedent heightens the stakes of the current decision; the \u0027egregious\u0027 characterization carries moral weight",
  "proeth-scenario:ethicalImplications": "Demonstrates the role of professional precedent in establishing and reinforcing ethical norms; reveals that selective or incomplete expert reporting is not merely a technical failure but a fundamental betrayal of the forensic engineer\u0027s role; shows how individual cases of misconduct shape the ethical landscape for the entire profession",
  "proeth-scenario:learningMoment": "Precedent cases serve as ethical guardrails. The Board\u0027s condemnation of Engineer B\u0027s selective reporting is directly analogous to what Engineer A faces \u2014 allowing known inaccurate conclusions to persist in a legal proceeding is the functional equivalent of selective and misleading reporting.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a_by_analogy": "The precedent makes clear that allowing inaccurate conclusions to stand would be condemned similarly",
    "engineer_b": "Professional reputation permanently damaged; formal condemnation on record",
    "engineering_profession": "Standards for forensic reporting are clarified and strengthened",
    "future_forensic_engineers": "Clear warning about the ethical requirements of expert reporting",
    "legal_system": "Reassurance that engineering profession polices its own standards of accuracy and completeness"
  },
  "proeth:activatesConstraint": [
    "Completeness_Of_Expert_Reports_Constraint",
    "No_Selective_Use_Of_Data_Constraint",
    "Duty_To_Consult_Available_Evidence_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/107#Action_Exclude_Pile_Driving_Records_from_Report__Omit_Dyn",
  "proeth:causesStateChange": "A formal ethical standard is established through Board precedent: forensic engineers must provide complete, accurate, and unconflicted reports; selective or incomplete reporting constitutes egregious ethical violation; this precedent is now available to govern Engineer A\u0027s situation",
  "proeth:createsObligation": [
    "Future_Engineers_Must_Provide_Complete_Accurate_Reports_Obligation",
    "Disclose_All_Material_Information_In_Expert_Reports_Obligation"
  ],
  "proeth:description": "In the parallel BER Case 95-5, Engineer B\u0027s selective data use, omission of critical information (including dynamic test equipment failure), and failure to consult available witnesses was formally condemned by the Board as an egregious ethical violation, establishing precedent applicable to Engineer A\u0027s situation.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior case; introduced in Discussion section as precedent; temporally antecedent to current case",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Precedent Case Ethical Violation Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#CausalChain_492fa57c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A accepts retention by Attorney X to perform forensic engineering investigation and prepare [a report], culminating in the written forensic report with conclusions being received by Attorney X",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A voluntarily agrees to serve as forensic expert for Attorney X, establishing professional and ethical obligations",
      "proeth:element": "Accept Forensic Engagement (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A performs the technical investigation into the mechanical product failure, gathering and relying upon underlying data",
      "proeth:element": "Conduct Forensic Investigation (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A prepares and delivers the written forensic report including causal conclusions to Attorney X",
      "proeth:element": "Submit Report to Attorney (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The report formally enters the legal record, becoming the evidentiary basis for Attorney X\u0027s legal strategy",
      "proeth:element": "Report Successfully Submitted (Event 1)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Attorney X initiates formal settlement negotiations relying on Engineer A\u0027s submitted conclusions as expert support",
      "proeth:element": "Settlement Negotiations Commenced (Event 2)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Forensic Engagement (Action 1)",
  "proeth:counterfactual": "Without Engineer A accepting the engagement, no forensic report would have been submitted to Attorney X; the legal process would have lacked expert engineering conclusions",
  "proeth:effect": "Report Successfully Submitted (Event 1)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s voluntary acceptance of the forensic engagement",
    "Completion of the forensic investigation (Action 2)",
    "Preparation and submission of the written report (Action 3)"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Acceptance of engagement + completion of investigation + submission of report together constitute a sufficient set to produce the submitted report event"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#CausalChain_0a102105",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct consequence of the data inaccuracy discovery, Engineer A\u0027s original report conclusions are rendered invalid, meaning the evidentiary foundation of the submitted report collapses",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A bases investigation and conclusions on data that is subsequently discovered to be inaccurate",
      "proeth:element": "Conduct Forensic Investigation (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Report containing conclusions derived from inaccurate data enters the legal record",
      "proeth:element": "Report Successfully Submitted (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A discovers post-submission that the underlying data was inaccurate and that corrected data yields materially different conclusions",
      "proeth:element": "Data Inaccuracy Discovered (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Original expert conclusions are no longer supportable; the report\u0027s evidentiary value is fundamentally undermined",
      "proeth:element": "Conclusions Rendered Invalid (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Settlement negotiations continue to rely on invalidated conclusions, corrupting the integrity of the legal process",
      "proeth:element": "Legal Process Integrity Compromised (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Data Inaccuracy Discovered (Event 3)",
  "proeth:counterfactual": "If the underlying data had been accurate, or if the inaccuracy had no material effect on conclusions, the original report would have remained valid and no disclosure obligation would have arisen",
  "proeth:effect": "Conclusions Rendered Invalid (Event 4)",
  "proeth:necessaryFactors": [
    "Existence of inaccurate underlying data used in the original report",
    "Discovery of that inaccuracy by Engineer A post-submission",
    "Materiality of the inaccuracy \u2014 corrected data yields different conclusions"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); data source provider (contributing)",
  "proeth:sufficientFactors": [
    "Inaccurate data + material effect on conclusions + post-submission discovery together are sufficient to render original conclusions invalid and create an ethical disclosure obligation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#CausalChain_763d437f",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B deliberately omitted from the concluding report the fact that the 19 disputed piles had been driven \u2014 this selective omission, combined with other omissions, constitutes the core factual basis for the ethical violation finding in BER Case 95-5",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B deliberately omits the fact that 19 disputed piles had been driven, removing material facts from the report",
      "proeth:element": "Exclude Pile Driving Records from Report (Action 5)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B further omits disclosure that dynamic test equipment failed during testing, compounding the selective presentation of facts",
      "proeth:element": "Omit Dynamic Test Equipment Failure (Action 6)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B refuses to consult on-site representatives and contractors who could have provided corrective factual information",
      "proeth:element": "Decline to Consult Available Witnesses (Action 7)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The cumulative effect of omissions produces a report that misrepresents the factual basis for engineering conclusions",
      "proeth:element": "Report Presents Selectively Incomplete Factual Record",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER Case 95-5 finds Engineer B\u0027s pattern of selective data use, omission, and refusal to investigate constitutes a violation of engineering ethics standards",
      "proeth:element": "Precedent Case Ethical Violation Established (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Exclude Pile Driving Records from Report (Action 5)",
  "proeth:counterfactual": "Had Engineer B included the pile driving records, the report would have reflected the complete factual record; the ethical violation finding would likely not have been established on this basis",
  "proeth:effect": "Precedent Case Ethical Violation Established (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s deliberate decision to omit the pile driving records",
    "Materiality of the omitted records to the report\u0027s conclusions",
    "The omission\u0027s capacity to mislead the client or legal process about the true state of facts"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Deliberate omission of pile driving records + omission of dynamic test equipment failure (Action 6) + refusal to consult available witnesses (Action 7) together constitute a sufficient pattern of selective data use to establish an ethical violation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#CausalChain_7bb57908",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B chose not to disclose in the report that the dynamic test equipment had failed during the [testing] and made a deliberate decision not to consult Engineer A\u0027s on-site representatives, contractors \u2014 together these omissions reinforce the pattern of selective data use underlying the ethical violation in BER Case 95-5",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B knowingly excludes from the report the fact that testing equipment failed, concealing a material limitation on the reliability of test data",
      "proeth:element": "Omit Dynamic Test Equipment Failure (Action 6)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B deliberately avoids consulting on-site representatives and contractors who possess material factual knowledge relevant to the investigation",
      "proeth:element": "Decline to Consult Available Witnesses (Action 7)",
      "proeth:step": 2
    },
    {
      "proeth:description": "The combination of Actions 5, 6, and 7 creates a demonstrable pattern of deliberate selective data use and suppression of contrary evidence",
      "proeth:element": "Cumulative Pattern of Selective Omission Established",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B\u0027s conclusions rest on an artificially narrowed evidentiary base, misrepresenting the reliability and completeness of the forensic analysis",
      "proeth:element": "Report Conclusions Unsupported by Complete Investigation",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER Case 95-5 formally establishes that Engineer B\u0027s conduct violated engineering ethics, creating precedent applicable to similar forensic engineering contexts",
      "proeth:element": "Precedent Case Ethical Violation Established (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Omit Dynamic Test Equipment Failure (Action 6) + Decline to Consult Available Witnesses (Action 7)",
  "proeth:counterfactual": "Had Engineer B disclosed the equipment failure and consulted available witnesses, the report would have been grounded in a more complete evidentiary basis; the ethical violation finding would have been substantially weakened or negated",
  "proeth:effect": "Precedent Case Ethical Violation Established (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s knowledge of the equipment failure and its potential effect on test data reliability",
    "Availability of witnesses who could have provided material factual information",
    "Engineer B\u0027s deliberate choice to exclude both the equipment failure disclosure and witness consultation"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Omission of equipment failure + refusal to consult available witnesses, when combined with the pile driving record omission (Action 5), are together sufficient to establish a pattern of deliberate selective presentation constituting an ethical violation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/107#",
    "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/107#CausalChain_024043a1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon discovering that the data underlying the report was inaccurate and that corrected data would yield different conclusions, Engineer A discloses this to Attorney X \u2014 this action, if taken, is the critical intervention preventing ongoing corruption of the legal process",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A becomes aware that submitted conclusions are based on inaccurate data",
      "proeth:element": "Data Inaccuracy Discovered (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A recognizes that corrected data would yield materially different conclusions, invalidating the report",
      "proeth:element": "Conclusions Rendered Invalid (Event 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A fulfills ethical obligation by informing Attorney X of the inaccuracy and its effect on conclusions",
      "proeth:element": "Disclose Data Inaccuracy to Attorney (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Attorney X receives notice that the expert conclusions underpinning settlement negotiations are no longer valid",
      "proeth:element": "Attorney X Informed of Report Invalidity",
      "proeth:step": 4
    },
    {
      "proeth:description": "With corrected information, settlement negotiations can proceed on accurate expert conclusions, preserving legal process integrity",
      "proeth:element": "Legal Process Integrity Preserved (counterfactual outcome)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Disclose Data Inaccuracy to Attorney (Action 4)",
  "proeth:counterfactual": "Without disclosure, settlement negotiations would continue to be influenced by invalid expert conclusions, directly compromising legal process integrity; disclosure is the necessary countermeasure",
  "proeth:effect": "Legal Process Integrity Compromised (Event 5) \u2014 PREVENTION pathway",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s awareness of the inaccuracy and its material effect",
    "Engineer A\u0027s volitional decision to disclose rather than conceal",
    "Attorney X\u0027s ability to act on the disclosure to correct or withdraw reliance on the flawed report"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Timely disclosure + attorney\u0027s corrective action together are sufficient to prevent further compromise of legal process integrity"
  ],
  "proeth:withinAgentControl": true
}