{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Engineer_A_Retains_Independent_Observer",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Participate directly in the test pile program as a co-supervisor rather than as an observer, asserting equal procedural authority",
    "Request that all test pile driving protocols be agreed in writing before work begins, with both parties bound to the specified methodology",
    "Decline to participate in the test program and instead challenge the municipality\u0027s right to conduct unilateral testing without Engineer A\u0027s formal consent"
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognized that the municipality\u0027s retention of Engineer B created an adversarial dynamic and sought to protect professional interests by ensuring an independent, qualified observer could document the test conditions, identify procedural deviations, and provide a counter-record to Engineer B\u0027s findings.",
  "proeth-scenario:consequencesIfAlternative": [
    "Co-supervision would have given Engineer A direct authority to halt procedural deviations as they occurred, potentially preventing the compromised test conditions entirely.",
    "Pre-agreed written protocols would have created a binding standard against which Engineer B\u0027s deviations could be formally measured, strengthening any subsequent challenge.",
    "Declining participation would have preserved Engineer A\u0027s objection to the process but forfeited the opportunity to document deviations and generate a counter-record."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the importance of independent observation and contemporaneous documentation in disputed technical proceedings. Engineer A\u0027s decision to retain an independent observer ultimately generated the evidentiary record that exposed Engineer B\u0027s procedural deviations and selective omissions \u2014 demonstrating that defensive professional diligence can serve both self-protection and broader truth-finding.",
  "proeth-scenario:ethicalTension": "Defensive self-protection through parallel observation is professionally prudent but risks further polarizing the fact-finding process; the presence of competing observers may create pressure for each to advocate for their retaining party rather than objectively document conditions.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s ability to contest adverse findings, the completeness and accuracy of the technical record, the fairness of the fact-finding process, and the evidentiary foundation for any subsequent professional or legal challenge to Engineer B\u0027s report.",
  "proeth:description": "Engineer A independently retained a geotechnical consultant to observe the test pile driving program supervised by Engineer B, establishing a parallel fact-gathering effort to protect Engineer A\u0027s technical interests. This was a deliberate defensive professional response to the municipality\u0027s adversarial positioning.",
  "proeth:foreseenUnintendedEffects": [
    "Signals distrust of Engineer B\u0027s objectivity",
    "Creates a competing technical record that could complicate dispute resolution"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to protect the integrity of the original design through independent verification",
    "Professional obligation to gather complete and accurate technical information",
    "Obligation to advocate for technically correct conclusions"
  ],
  "proeth:guidedByPrinciple": [
    "Due diligence in technical fact-gathering",
    "Self-protection of professional reputation",
    "Verification of adversarially-generated technical findings"
  ],
  "proeth:hasAgent": "Engineer A (Retained Design Engineer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Ensure independent documentation of test conditions and results to counter potential bias in Engineer B\u0027s findings and preserve Engineer A\u0027s ability to challenge adverse conclusions",
  "proeth:requiresCapability": [
    "Judgment to identify need for independent technical observation",
    "Ability to select and brief a qualified geotechnical consultant"
  ],
  "proeth:temporalMarker": "Prior to test pile driving, in response to municipality retaining Engineer B",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Retains Independent Observer"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_90-Pile_Foundation_Design",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Commission independent geotechnical verification before finalizing pile count and design parameters",
    "Specify more conservative driving resistance requirements with explicit re-test protocols built into the construction documents",
    "Decline to rely on the 30-day strength-gain assumption and require confirmation testing as a contractual construction milestone"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to fulfill a municipal contract by applying sound engineering judgment, integrating third-party geotechnical data to produce a cost-effective and structurally adequate foundation design. The reliance on the geotechnical firm\u0027s 30-day strength-gain prediction reflected standard professional practice of delegating subsurface analysis to specialists.",
  "proeth-scenario:consequencesIfAlternative": [
    "Independent verification would have increased upfront project cost and schedule but could have either confirmed the geotechnical firm\u0027s conclusions or identified discrepancies early, potentially preventing the entire downstream dispute.",
    "More conservative specifications would have provided clearer pass/fail criteria during construction, reducing ambiguity about pile adequacy and giving the contractor less grounds for an extra claim.",
    "Requiring confirmation testing as a contractual milestone would have formalized the strength-gain verification process, ensuring it was conducted under agreed protocols rather than becoming an adversarial post-dispute exercise."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the professional responsibility engineers bear when integrating third-party technical data into their own designs. Engineers cannot fully transfer accountability to sub-consultants \u2014 they must critically evaluate external inputs and understand the limitations of data they incorporate. This action also establishes the technical baseline against which all subsequent disputes are measured.",
  "proeth-scenario:ethicalTension": "Reliance on third-party specialist data versus independent verification of geotechnical assumptions; efficiency and client cost management versus exhaustive redundant testing; trust in professional delegation versus personal accountability for integrated design outcomes.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public safety of dock users, structural integrity of a 90-pile foundation, Engineer A\u0027s professional reputation, municipal infrastructure investment, and the downstream legal and financial exposure that flows from any design adequacy dispute.",
  "proeth:description": "Engineer A chose to design the dock foundation using 90 piles, relying on the geotechnical firm\u0027s report predicting sufficient strength gain within 30 days of driving. This was a deliberate technical judgment integrating third-party geotechnical data into a structural design solution.",
  "proeth:foreseenUnintendedEffects": [
    "Dependency on geotechnical firm\u0027s 30-day strength-gain prediction being accurate",
    "Risk that field driving conditions might not match geotechnical assumptions"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to use relevant technical data in design decisions",
    "Obligation to serve the public safety through competent structural design",
    "Obligation to rely on qualified specialists (geotechnical firm) for subsurface data"
  ],
  "proeth:guidedByPrinciple": [
    "Competence: apply specialized knowledge appropriately",
    "Public safety: design to adequate safety factors",
    "Reliance on qualified specialist reports"
  ],
  "proeth:hasAgent": "Engineer A (Retained Design Engineer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Produce a structurally sound, code-compliant dock foundation meeting the municipality\u0027s project requirements",
  "proeth:requiresCapability": [
    "Structural/foundation engineering judgment",
    "Interpretation of geotechnical reports",
    "Pile design methodology"
  ],
  "proeth:temporalMarker": "Initial design phase, prior to construction",
  "proeth:withinCompetence": true,
  "rdfs:label": "90-Pile Foundation Design"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Mediation_Settlement_Agreement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Refuse to settle and proceed to full litigation to obtain a definitive judicial finding on design adequacy",
    "Settle individually rather than jointly, negotiating separate contributions that reflect each party\u0027s distinct liability exposure",
    "Agree to settle financially but issue a public or professional statement preserving Engineer A\u0027s position that the design met applicable standards"
  ],
  "proeth-scenario:characterMotivation": "Engineer A and the municipality sought to limit financial exposure, avoid the uncertainty and cost of prolonged litigation, and resolve the contractor\u0027s claims in a controlled environment. Mediation offered a predictable outcome and preserved ongoing working relationships compared to adversarial court proceedings.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full litigation would have forced a complete technical adjudication, potentially vindicating Engineer A\u0027s design but at significant cost, time, and reputational risk during proceedings.",
    "Separate settlements would have created a clearer record of each party\u0027s liability assessment but might have complicated mediation and increased total legal costs.",
    "A settlement paired with a public technical statement would have protected Engineer A\u0027s professional record but could have antagonized the municipality and complicated the ongoing working relationship."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that legal resolution and ethical resolution are not the same thing. A settlement ends a dispute financially but does not establish technical truth. Students should understand that engineers may face pressure to settle even when they believe their work was sound, and that such decisions have reputational and precedential implications beyond the immediate financial outcome.",
  "proeth-scenario:ethicalTension": "Settling without full factual adjudication may obscure whether the design was actually deficient, potentially creating a false public record of fault; financial pragmatism conflicts with professional interest in vindicating one\u0027s technical judgment; shared settlement cost raises questions about relative responsibility allocation.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional reputation and implicit acknowledgment of potential design fault, the municipality\u0027s public accountability for infrastructure decisions, the $300,000 financial burden, and the precedent set for how future design disputes are handled.",
  "proeth:description": "Engineer A and the municipality jointly decided to settle the contractor\u0027s lawsuit for $300,000 rather than proceed to full litigation, sharing the settlement cost between them. This was a deliberate legal-strategic decision to resolve the dispute through mediation.",
  "proeth:foreseenUnintendedEffects": [
    "Settlement could be interpreted as implicit acknowledgment of fault",
    "Cost-sharing arrangement creates adversarial dynamic between Engineer A and municipality regarding attribution of responsibility",
    "Precedent for further technical scrutiny of Engineer A\u0027s original design"
  ],
  "proeth:fulfillsObligation": [
    "Legitimate exercise of legal rights to settle disputes",
    "Practical obligation to manage client and professional financial exposure"
  ],
  "proeth:guidedByPrinciple": [
    "Risk management and professional prudence",
    "Cooperative resolution of disputes"
  ],
  "proeth:hasAgent": "Engineer A (Retained Design Engineer) and Municipality (Client/Co-Defendant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Full technical vindication vs. practical dispute resolution",
    "proeth:resolutionReasoning": "Both parties chose financial and procedural certainty of settlement over the risk and expense of continued litigation, even though technical questions remained contested"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Resolve contractor\u0027s legal claim efficiently, avoid prolonged and costly litigation, and apportion financial liability between the two defendants",
  "proeth:requiresCapability": [
    "Legal strategy judgment (in consultation with counsel)",
    "Risk assessment of litigation outcomes",
    "Negotiation and mediation participation"
  ],
  "proeth:temporalMarker": "Post-construction, during mediation proceedings",
  "proeth:withinCompetence": true,
  "rdfs:label": "Mediation Settlement Agreement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Municipality_Retains_Engineer_B",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Retain a neutral third-party engineer jointly agreed upon by both the municipality and Engineer A to conduct unbiased test pile supervision",
    "Request that a professional engineering society or regulatory body appoint an independent technical reviewer",
    "Conduct the test pile program under a jointly agreed protocol with both parties\u0027 representatives present and with pre-specified acceptance criteria"
  ],
  "proeth-scenario:characterMotivation": "The municipality sought an independent engineering authority to validate its position that pile deficiencies were attributable to Engineer A\u0027s design rather than to construction execution or contractor conduct. Retaining Engineer B was a strategic move to generate expert technical support for cost-attribution arguments in an ongoing financial dispute.",
  "proeth-scenario:consequencesIfAlternative": [
    "A jointly retained neutral engineer would have produced findings with far greater credibility and legal weight, potentially resolving the dispute more efficiently and reducing the likelihood of the ethical violations that followed.",
    "A society- or regulator-appointed reviewer would have insulated both parties from accusations of bias and produced findings less vulnerable to challenge.",
    "A jointly agreed protocol with pre-specified criteria would have constrained the procedural deviations that occurred during test driving and produced data both parties were contractually bound to accept."
  ],
  "proeth-scenario:decisionSignificance": "Highlights the structural conflict of interest that arises when an engineer is retained specifically to support one party\u0027s litigation position. The framing of Engineer B\u0027s engagement as \u0027supervision of test pile driving\u0027 obscures its fundamentally adversarial purpose, creating conditions where confirmation bias is institutionally incentivized rather than guarded against.",
  "proeth-scenario:ethicalTension": "The legitimate need for independent technical review conflicts with the risk of creating a biased fact-finding process when the retained expert\u0027s role is implicitly adversarial; the municipality\u0027s financial interest in attributing fault to Engineer A conflicts with the public interest in an objective assessment of infrastructure safety.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The objectivity and integrity of the technical fact-finding process, Engineer A\u0027s professional reputation, the municipality\u0027s credibility as a public institution, and the safety conclusions drawn about 90 piles supporting public infrastructure.",
  "proeth:description": "The municipality made a deliberate decision to retain Engineer B to supervise test pile driving as a mechanism to challenge Engineer A\u0027s design conclusions and support the municipality\u0027s position in the ongoing cost-attribution dispute. This decision introduced an adversarially-positioned engineer into a technical fact-finding process.",
  "proeth:foreseenUnintendedEffects": [
    "Risk that Engineer B\u0027s adversarial positioning could compromise objectivity of technical findings",
    "Escalation of technical dispute between Engineer A and municipality"
  ],
  "proeth:fulfillsObligation": [
    "Legitimate right to retain independent technical expert",
    "Obligation to investigate technical claims before accepting financial liability"
  ],
  "proeth:guidedByPrinciple": [
    "Client self-interest and cost protection",
    "Use of technical expertise to resolve factual disputes"
  ],
  "proeth:hasAgent": "Municipality (Client/Co-Defendant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Adversarial cost recovery vs. objective technical investigation",
    "proeth:resolutionReasoning": "Municipality chose to frame the technical investigation as an adversarial exercise rather than a neutral one, embedding a conflict of interest into the fact-finding process from the outset"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Generate technical evidence challenging Engineer A\u0027s design to support the municipality\u0027s position that Engineer A bore greater responsibility for the settlement cost",
  "proeth:requiresCapability": [
    "Client judgment in selecting technical experts",
    "Understanding of litigation support roles for engineers"
  ],
  "proeth:temporalMarker": "During or immediately following mediation, prior to test pile driving",
  "proeth:violatesObligation": [
    "Implicit obligation of good faith in shared fact-finding when results affect a co-party"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Municipality Retains Engineer B"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Vibratory_Hammer_Substitution_Decision",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Halt the test program and reschedule until the correct impact hammer was available, ensuring methodological equivalence with original construction",
    "Document the equipment substitution transparently in the test report and explicitly qualify all conclusions as limited by the non-equivalent testing conditions",
    "Consult with Engineer A\u0027s observer and both parties\u0027 representatives before proceeding with a substitute hammer, obtaining mutual agreement or documented objection"
  ],
  "proeth-scenario:characterMotivation": "Engineer B\u0027s team may have chosen the vibratory hammer due to equipment availability, cost considerations, scheduling convenience, or \u2014 more troublingly \u2014 because it produced driving conditions that would generate data favorable to the municipality\u0027s position. Whether motivated by negligence or strategic intent, the substitution served to undermine the test\u0027s comparative validity.",
  "proeth-scenario:consequencesIfAlternative": [
    "Rescheduling would have delayed the process and increased costs but produced methodologically valid comparative data capable of supporting defensible conclusions.",
    "Transparent documentation would not have corrected the methodological flaw but would have preserved Engineer B\u0027s honesty and allowed readers to appropriately discount the findings.",
    "Mutual consultation would have either produced agreement on an acceptable substitute methodology or generated a formal record of Engineer A\u0027s objection, protecting both parties and the integrity of the process."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates how procedural deviations in engineering testing \u2014 even those that appear to be minor field decisions \u2014 can fundamentally compromise the validity of technical conclusions. Students should recognize that engineering testing methodology is not merely a technical matter but an ethical one: deviations that systematically bias results in favor of a retaining party\u0027s position constitute a form of professional misconduct.",
  "proeth-scenario:ethicalTension": "Practical field expediency conflicts with methodological rigor; the obligation to conduct a valid comparative test conflicts with the implicit pressure to produce results supporting the retaining party; the duty to the profession and public conflicts with the financial relationship with the municipality.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The validity of the entire test pile program, the accuracy of pile adequacy conclusions affecting public infrastructure safety, Engineer B\u0027s professional integrity, and the fairness of the cost-attribution dispute between Engineer A and the municipality.",
  "proeth:description": "During test pile driving, Engineer B\u0027s team used a vibratory hammer instead of the original driving hammer, deviating from the conditions of the original pile installation and compromising the validity of the comparative test. This was a deliberate procedural choice that undermined the test\u0027s ability to replicate original driving conditions.",
  "proeth:foreseenUnintendedEffects": [
    "Results would not be directly comparable to original pile driving conditions",
    "Test validity could be challenged by Engineer A\u0027s independent observer",
    "Substitution could skew blow count and penetration depth results"
  ],
  "proeth:guidedByPrinciple": [
    "Technical rigor and test validity",
    "Objectivity in engineering investigation",
    "Accuracy in fact-gathering"
  ],
  "proeth:hasAgent": "Engineer B (Municipality-Retained Engineer) and/or test contractor under Engineer B\u0027s supervision",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Test validity vs. practical testing constraints",
    "proeth:resolutionReasoning": "Expedience and possibly adversarial interest in generating unfavorable results for Engineer A\u0027s design were prioritized over methodological validity"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Complete test pile driving using available equipment; possibly expedite the testing process",
  "proeth:requiresCapability": [
    "Knowledge of pile driving test protocols",
    "Understanding of how equipment variation affects blow count and penetration results",
    "Supervisory authority to require correct equipment"
  ],
  "proeth:temporalMarker": "During test pile driving program",
  "proeth:violatesObligation": [
    "Obligation to design and supervise tests that validly replicate original conditions",
    "Obligation to ensure test methodology supports accurate and unbiased conclusions",
    "Obligation to public safety through technically sound evaluation methods"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Vibratory Hammer Substitution Decision"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Pre-Count_Hammer_Drop_Decision",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Record all hammer drops including pre-count drops in the test log, ensuring a complete account of all energy input to each pile",
    "Establish and document a standardized pre-count procedure agreed upon by all parties before testing begins, so any warm-up drops are part of the formal protocol",
    "Eliminate pre-count drops entirely and begin official blow counts from the first hammer impact, maintaining strict equivalence with original driving records"
  ],
  "proeth-scenario:characterMotivation": "The pre-count hammer drops may have been rationalized as a field warm-up procedure or equipment calibration step, but the effect was to introduce unrecorded energy input into the pile before official blow counts began. Whether intentional or negligent, this practice distorted the resistance data by pre-fatiguing soil conditions without documentation, making piles appear to require more recorded blows than they actually did under equivalent conditions.",
  "proeth-scenario:consequencesIfAlternative": [
    "Complete recording would have preserved data integrity and allowed post-hoc analysis to account for pre-count energy input, producing more defensible conclusions.",
    "A pre-agreed standardized procedure would have transformed the pre-count drops from an ad hoc deviation into a documented, mutually accepted protocol element.",
    "Eliminating pre-count drops would have maximized methodological equivalence with original construction and produced the most directly comparable resistance data."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that engineering misconduct in testing contexts is often embedded in seemingly minor procedural decisions rather than in dramatic falsification. Students should understand that the cumulative effect of multiple small deviations \u2014 each potentially rationalizable individually \u2014 can constitute a pattern of systematic bias that rises to an ethical violation.",
  "proeth-scenario:ethicalTension": "Field operational convenience or equipment practice conflicts with the obligation to maintain a complete and accurate test record; the implicit pressure to generate data supporting the municipality\u0027s position conflicts with the duty to conduct testing that is genuinely comparable to original construction conditions.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The accuracy of blow count data used to assess pile resistance, the integrity of the comparative analysis between test and original piles, Engineer B\u0027s professional credibility, and the validity of conclusions affecting the safety assessment of 90 piles.",
  "proeth:description": "During test pile driving, Engineer B\u0027s team dropped the hammer multiple times before commencing official blow count records, introducing unrecorded energy input that distorted the comparative validity of the test data. This procedural deviation was a deliberate operational choice made during the supervised test.",
  "proeth:foreseenUnintendedEffects": [
    "Official blow counts would not reflect total energy applied to piles",
    "Penetration resistance data would be skewed relative to original driving records",
    "Test results would be less favorable to Engineer A\u0027s design validation"
  ],
  "proeth:guidedByPrinciple": [
    "Technical honesty and procedural rigor",
    "Objectivity in engineering testing",
    "Completeness of data recording"
  ],
  "proeth:hasAgent": "Engineer B (Municipality-Retained Engineer) and/or test contractor under Engineer B\u0027s supervision",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Operational convenience vs. data completeness and test integrity",
    "proeth:resolutionReasoning": "Procedural shortcut was taken at the expense of test integrity, whether through negligence or deliberate bias"
  },
  "proeth:hasMentalState": "deliberate or negligently permissive",
  "proeth:intendedOutcome": "Possibly to seat the hammer or warm up equipment before official recording; however, the effect was to exclude initial driving energy from the official record",
  "proeth:requiresCapability": [
    "Knowledge of standard pile driving test protocols",
    "Supervisory oversight of field testing procedures",
    "Understanding of how pre-count drops affect data validity"
  ],
  "proeth:temporalMarker": "During test pile driving program",
  "proeth:violatesObligation": [
    "Obligation to conduct tests with procedural integrity",
    "Obligation to produce accurate and complete technical records",
    "Obligation to avoid actions that systematically bias test outcomes"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Pre-Count Hammer Drop Decision"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Inconsistent_Pile_Depth_Decision",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Establish explicit depth targets for each test pile before driving begins, matched to the as-built records of the corresponding original piles",
    "Halt driving when depth discrepancies are identified and adjust the test protocol to correct the deviation before proceeding",
    "Document depth discrepancies transparently and explicitly exclude non-equivalent piles from comparative analysis, limiting conclusions to valid data subsets"
  ],
  "proeth-scenario:characterMotivation": "Engineer B\u0027s team failed to drive test piles to the same depth as the original piles, either through inadequate supervision, equipment limitations, or a failure to establish clear depth targets before testing began. The effect was to make direct comparison of penetration resistance data between test and original piles methodologically invalid, since resistance varies with depth and soil stratigraphy.",
  "proeth-scenario:consequencesIfAlternative": [
    "Pre-established depth targets would have ensured methodological equivalence and produced data directly comparable to original construction records.",
    "Halting and correcting discrepancies during testing would have increased time and cost but preserved the validity of the test program.",
    "Transparent documentation and exclusion of non-equivalent data would have reduced the dataset but maintained the integrity of conclusions drawn from the remaining valid comparisons."
  ],
  "proeth-scenario:decisionSignificance": "Reinforces the principle that engineering testing protocols must be designed and executed with explicit equivalence criteria. The failure to match a fundamental parameter \u2014 pile depth \u2014 renders the entire comparative analysis scientifically invalid. Students should understand that an engineering report built on invalid comparative data is itself invalid, regardless of how technically sophisticated its analysis appears.",
  "proeth-scenario:ethicalTension": "The obligation to conduct a methodologically valid comparative test conflicts with field expediency and the pressure to complete testing within schedule and budget constraints; if the depth deviation was deliberate, it represents a direct conflict between the duty to produce honest findings and the financial interest in supporting the retaining party.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The scientific validity of the test program\u0027s comparative conclusions, the credibility of Engineer B\u0027s report, the fairness of the pile adequacy assessment, and ultimately the safety determination for infrastructure serving the public.",
  "proeth:description": "During test pile driving, Engineer B\u0027s team did not drive test piles to the same depth as the original piles, creating a non-equivalent comparison basis that invalidated direct comparison of penetration resistance data between the test and original construction. This was a deliberate or negligently supervised procedural deviation.",
  "proeth:foreseenUnintendedEffects": [
    "Penetration resistance data would not be comparable to original pile driving records",
    "Conclusions about safety factor adequacy based on this data would be methodologically unsound",
    "Engineer A\u0027s independent observer would document the discrepancy"
  ],
  "proeth:guidedByPrinciple": [
    "Scientific rigor and methodological validity",
    "Objectivity and completeness in engineering investigation",
    "Accuracy in technical fact-finding"
  ],
  "proeth:hasAgent": "Engineer B (Municipality-Retained Engineer) and/or test contractor under Engineer B\u0027s supervision",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Test replication validity vs. practical testing constraints or adversarial interest",
    "proeth:resolutionReasoning": "Methodological equivalence was sacrificed, whether through negligence, practical constraint, or deliberate adversarial bias"
  },
  "proeth:hasMentalState": "deliberate or negligently permissive",
  "proeth:intendedOutcome": "Complete test pile driving within practical constraints; possibly to generate penetration data at depths favorable to the municipality\u0027s argument",
  "proeth:requiresCapability": [
    "Pile driving test design and supervision",
    "Knowledge of requirements for valid comparative pile testing",
    "Field supervision authority to enforce correct procedures"
  ],
  "proeth:temporalMarker": "During test pile driving program",
  "proeth:violatesObligation": [
    "Obligation to design tests that validly replicate conditions being evaluated",
    "Obligation to ensure conclusions are supported by methodologically sound data",
    "Obligation to avoid systematic bias in technical investigations"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Inconsistent Pile Depth Decision"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Decision_to_Exclude_Stakeholder_Consultation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct structured interviews with Engineer A\u0027s on-site representatives, contractors, and workers as a standard component of the fact-gathering process, documenting their accounts in the report",
    "Request access to all contemporaneous pile driving records, field logs, and inspection reports from the original construction before forming any conclusions",
    "Disclose in the report that stakeholder consultation was not conducted and explicitly qualify conclusions as limited by the absence of first-hand observational data"
  ],
  "proeth-scenario:characterMotivation": "Engineer B may have avoided consulting Engineer A\u0027s representatives, contractors, and workers to maintain the appearance of independence from Engineer A\u0027s position, to avoid information that would complicate the municipality-favorable narrative, or due to an overly narrow interpretation of the scope of work that excluded stakeholder consultation. The effect, regardless of motivation, was to produce a report systematically deprived of first-hand observational knowledge.",
  "proeth-scenario:consequencesIfAlternative": [
    "Structured stakeholder interviews would have surfaced the critical facts about piles driven to refusal and equipment failures, potentially leading to different and more accurate conclusions.",
    "Review of contemporaneous records would have provided the pile driving data Engineer B later claimed to find suspicious, allowing a more complete and defensible analysis.",
    "Transparent disclosure of the consultation gap would not have corrected the information deficit but would have preserved Engineer B\u0027s honesty and alerted readers to the report\u0027s limitations."
  ],
  "proeth-scenario:decisionSignificance": "Highlights that engineering reports issued in disputed contexts carry the same epistemic obligations as any other professional engineering work \u2014 completeness of information-gathering is not optional. The deliberate or negligent exclusion of available first-hand knowledge sources is itself an ethical failure independent of what those sources might have said.",
  "proeth-scenario:ethicalTension": "The duty to gather all reasonably available information relevant to an engineering conclusion conflicts with the adversarial dynamic that discouraged engagement with sources associated with Engineer A; the obligation to produce a complete and accurate report conflicts with the implicit pressure to avoid information that might undermine the municipality\u0027s position.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The completeness and accuracy of Engineer B\u0027s factual foundation, the fairness of the pile adequacy assessment, the professional reputations of all parties, and the reliability of a safety conclusion affecting public infrastructure.",
  "proeth:description": "Engineer B deliberately chose not to consult Engineer A\u0027s on-site representatives, contractors, or construction workers before or during preparation of the pile adequacy report, despite their direct knowledge of original pile driving conditions. This omission deprived the report of critical first-hand observational data.",
  "proeth:foreseenUnintendedEffects": [
    "Report would lack the contextual knowledge held by those who observed original pile driving",
    "Critical facts about equipment failures and driving-to-refusal would be absent from Engineer B\u0027s analysis",
    "Report conclusions would be vulnerable to challenge as incomplete"
  ],
  "proeth:guidedByPrinciple": [
    "Completeness and objectivity in professional reporting",
    "Due diligence in fact-gathering",
    "Intellectual honesty in engineering analysis"
  ],
  "proeth:hasAgent": "Engineer B (Municipality-Retained Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client advocacy and scope compliance vs. professional thoroughness and objectivity",
    "proeth:resolutionReasoning": "Engineer B prioritized client advocacy and expedience over professional thoroughness, using scope limitations as a post-hoc rationalization for a decision that served the client\u0027s adversarial interest"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Produce a report based solely on Engineer B\u0027s own test data and analysis, possibly to avoid information that would complicate or contradict the municipality\u0027s preferred conclusions",
  "proeth:requiresCapability": [
    "Ability to conduct comprehensive stakeholder interviews",
    "Knowledge of what information sources are required for valid pile adequacy assessment",
    "Professional judgment to expand scope when available information is incomplete"
  ],
  "proeth:temporalMarker": "During report preparation, following test pile driving",
  "proeth:violatesObligation": [
    "Obligation to gather all reasonably available relevant information before issuing professional conclusions",
    "Obligation to issue complete and objective engineering reports",
    "Obligation to act in a manner that protects public safety by ensuring structural adequacy conclusions are based on full information",
    "Obligation of due diligence in engineering investigation"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Decision to Exclude Stakeholder Consultation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Selective_Omission_in_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Include all three omitted facts in the report with full technical analysis, allowing the conclusions to reflect the complete evidentiary picture even if less favorable to the municipality",
    "Decline to issue a report concluding pile failure given the contradictory evidence, instead recommending additional testing under agreed protocols to resolve the technical uncertainty",
    "Issue the report with its conclusions but include a complete disclosure of all data considered and excluded, with explicit justification for any exclusions, allowing readers to assess the reasoning independently"
  ],
  "proeth-scenario:characterMotivation": "Engineer B issued a report omitting three critical facts \u2014 dynamic test equipment failure, all 19 piles driven to refusal, and wave equation calculations showing adequate strength \u2014 either to produce a conclusion favorable to the retaining municipality, to avoid complicating a report whose conclusions had already been determined, or due to a rationalized but unjustifiable judgment that these facts were outside the relevant scope. The omissions transformed a potentially balanced technical assessment into a selective advocacy document.",
  "proeth-scenario:consequencesIfAlternative": [
    "A complete report including all three omitted facts would likely have reached different conclusions about pile adequacy, potentially vindicating Engineer A\u0027s design and resolving the dispute on accurate technical grounds.",
    "Declining to conclude pile failure would have preserved Engineer B\u0027s professional integrity and forced a more rigorous resolution process, though it would likely have dissatisfied the retaining municipality.",
    "Full disclosure of data and reasoning would have preserved Engineer B\u0027s honesty even if the conclusions remained the same, allowing the report to be challenged on its reasoning rather than on concealment of material facts."
  ],
  "proeth-scenario:decisionSignificance": "This is the central ethical violation of the case and the primary teaching moment. It demonstrates that engineering ethics violations in reporting contexts are often not outright fabrication but selective presentation \u2014 the strategic omission of facts that would complicate or contradict a desired conclusion. Students should understand that an engineer\u0027s duty of completeness and honesty applies with full force even when retained in an adversarial context, and that a technically accurate but selectively incomplete report is an ethically dishonest report.",
  "proeth-scenario:ethicalTension": "The financial and professional relationship with the retaining municipality conflicts with the obligation to report all material facts regardless of their effect on the client\u0027s position; the pressure to produce a definitive, actionable conclusion conflicts with the duty to represent uncertainty and contradictory evidence honestly; professional loyalty to a client conflicts with the overriding duty to the public and the profession.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer B\u0027s professional license and reputation, the integrity of the engineering profession\u0027s role in dispute resolution, the accuracy of a safety determination for public infrastructure, Engineer A\u0027s professional reputation and financial exposure, and the municipality\u0027s long-term liability for acting on a flawed report.",
  "proeth:description": "Engineer B issued a formal engineering report concluding that 19 of 90 piles failed the required safety factor, deliberately omitting three critical facts: that dynamic test equipment had failed during testing, that all 19 piles had been driven to refusal, and that wave equation calculations would demonstrate adequate pile strength. This selective presentation of facts constituted the central ethics violation analyzed in the case.",
  "proeth:foreseenUnintendedEffects": [
    "Report would misrepresent the technical reality of pile adequacy",
    "Report could be used to unjustly damage Engineer A\u0027s professional reputation",
    "If relied upon, report could lead to unnecessary and costly remediation of structurally adequate piles",
    "Report would be vulnerable to exposure as incomplete when compared to Engineer A\u0027s independent observer\u0027s records"
  ],
  "proeth:guidedByPrinciple": [
    "Objectivity and completeness in professional reporting",
    "Intellectual honesty",
    "Protection of public safety",
    "Integrity of the engineering profession"
  ],
  "proeth:hasAgent": "Engineer B (Municipality-Retained Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client advocacy vs. engineering objectivity and completeness",
    "proeth:resolutionReasoning": "Engineer B resolved the conflict in favor of client advocacy, treating the engineering report as an instrument of litigation strategy rather than an objective professional document \u2014 a resolution that violates core engineering ethics obligations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Produce a report supporting the municipality\u0027s position that Engineer A\u0027s pile design was inadequate, thereby shifting cost-attribution responsibility toward Engineer A",
  "proeth:requiresCapability": [
    "Pile foundation adequacy analysis",
    "Wave equation analysis methodology",
    "Dynamic pile testing interpretation",
    "Objective and complete technical report writing",
    "Ethical judgment in adversarial expert contexts"
  ],
  "proeth:temporalMarker": "Following test pile driving and 30-day set period, during report preparation and issuance",
  "proeth:violatesObligation": [
    "Obligation to issue complete, objective, and accurate engineering reports",
    "Obligation to include all material facts relevant to the conclusions drawn",
    "Obligation to avoid misleading clients, courts, or other engineers through selective presentation",
    "Obligation to protect public safety by ensuring structural conclusions are technically sound",
    "Obligation to uphold the integrity of the engineering profession",
    "NSPE Code of Ethics: Engineers shall be objective and truthful in professional reports",
    "NSPE Code of Ethics: Engineers shall act in a manner that upholds public safety, health, and welfare"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Selective Omission in Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Action_Contradictory_Post-Report_Explanations",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Acknowledge honestly when first confronted that the pile driving records were reviewed but judged less reliable than other data sources, providing a single consistent and documented rationale",
    "Acknowledge that the report was incomplete, withdraw or formally supplement it to include the omitted facts and their technical implications",
    "Decline to respond to Engineer A\u0027s challenge and instead refer all questions about the report to the retaining municipality\u0027s legal counsel, preserving consistency while avoiding further self-contradiction"
  ],
  "proeth-scenario:characterMotivation": "When confronted by Engineer A about the exclusion of pile driving records, Engineer B first claimed they were outside the scope of work \u2014 a scope-based rationalization. When this explanation was challenged or found inadequate, Engineer B shifted to claiming the records appeared suspicious \u2014 a credibility-based rationalization. The sequential inconsistency reveals that neither explanation was the actual reason, suggesting the records were excluded because they contradicted the desired conclusion.",
  "proeth-scenario:consequencesIfAlternative": [
    "A single honest and consistent explanation, even if debatable, would have preserved Engineer B\u0027s professional credibility and allowed the disagreement to be resolved on technical rather than ethical grounds.",
    "Withdrawing or supplementing the report would have been professionally costly in the short term but would have demonstrated integrity and potentially prevented formal ethics proceedings.",
    "Referring questions to legal counsel would have avoided the self-contradicting explanations but would have signaled awareness of the report\u0027s vulnerability and potentially accelerated formal challenge proceedings."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that post-hoc rationalization \u2014 offering justifications for a decision that were not the actual reasons for it \u2014 is itself an ethical violation compounding the original misconduct. Students should understand that professional accountability requires honest explanation of actual reasoning, and that contradictory explanations are not merely a credibility problem but evidence that the original decision lacked a legitimate professional basis.",
  "proeth-scenario:ethicalTension": "The obligation to provide honest, consistent explanations for professional judgments conflicts with the desire to defend a report whose conclusions were reached through selective analysis; the duty of candor in professional communications conflicts with the self-protective impulse to justify prior conduct; accountability to a peer engineer conflicts with loyalty to the retaining client\u0027s interests.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Engineer B\u0027s professional credibility and license, the evidentiary weight of the pile adequacy report in any subsequent proceedings, the integrity of the engineering profession\u0027s self-regulatory mechanisms, and Engineer A\u0027s ability to mount an effective professional or legal challenge to the report\u0027s conclusions.",
  "proeth:description": "When questioned by Engineer A after the report was issued, Engineer B provided two contradictory justifications for ignoring pile driving records \u2014 first claiming they were outside the scope of work, then claiming the records appeared suspicious. This sequential issuance of inconsistent explanations revealed that neither was an honest account of Engineer B\u0027s actual reasoning.",
  "proeth:foreseenUnintendedEffects": [
    "Contradictory explanations would themselves become evidence of bad faith and compromised professional judgment",
    "Inconsistency would undermine Engineer B\u0027s credibility as an expert",
    "Exposure of the contradiction would strengthen the case that Engineer B\u0027s omissions were deliberate rather than inadvertent"
  ],
  "proeth:guidedByPrinciple": [
    "Intellectual honesty",
    "Consistency and transparency in professional conduct",
    "Accountability for professional decisions and their rationale"
  ],
  "proeth:hasAgent": "Engineer B (Municipality-Retained Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional honesty vs. self-protective defense of compromised report",
    "proeth:resolutionReasoning": "Engineer B chose self-protection over honesty, issuing contradictory explanations that ultimately served as additional evidence of the original ethical violation rather than successfully defending it"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Defend the report\u0027s conclusions and methodology against Engineer A\u0027s challenge without acknowledging the true basis for the omissions",
  "proeth:requiresCapability": [
    "Honest and consistent professional communication",
    "Ability to acknowledge methodological limitations",
    "Ethical judgment in responding to professional challenges"
  ],
  "proeth:temporalMarker": "After report issuance, in response to Engineer A\u0027s post-report inquiry",
  "proeth:violatesObligation": [
    "Obligation to be truthful and transparent when explaining professional decisions",
    "Obligation to provide consistent and honest accounts of methodology",
    "Obligation to acknowledge limitations or errors in professional work when challenged",
    "Obligation to uphold the integrity of professional communications"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Contradictory Post-Report Explanations"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_Geotechnical_Report_Strength-Gain_Anticipation",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How should geotechnical predictions about pile set-up be communicated to contractors and inspectors during construction?",
    "What is the engineer\u0027s obligation when a geotechnical report predicts behavior that differs from initial field observations?",
    "How does reliance on a third-party geotechnical report affect an engineer\u0027s professional responsibility for pile performance?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A gains confidence and a technical anchor for defense; municipality and its experts face a complicating factor in their position; geotechnical firm\u0027s credibility becomes relevant",
  "proeth-scenario:ethicalImplications": "Highlights the ethical importance of preserving and presenting complete technical context; raises questions about how engineers should communicate time-dependent soil behavior to all project stakeholders to prevent misunderstandings",
  "proeth-scenario:learningMoment": "Illustrates the critical importance of geotechnical reports as living project documents that can serve as both design basis and legal defense; shows how soil behavior (pile set-up) is a legitimate engineering consideration that must be communicated and verified.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Has documented technical basis for defending design decisions; burden shifts to demonstrating actual strength gain",
    "geotechnical_firm": "Report becomes central to dispute; firm\u0027s professional credibility implicated",
    "municipality": "Must account for geotechnical predictions in evaluating pile adequacy claims",
    "public": "If strength gain is real, dock may be structurally adequate despite initial resistance deficiencies"
  },
  "proeth:activatesConstraint": [
    "Technical_Documentation_Preservation",
    "Reliance_On_Geotechnical_Recommendations"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_90-Pile_Foundation_Design",
  "proeth:causesStateChange": "Technical basis established for 30-day set period testing; Engineer A\u0027s defense strategy anchored to geotechnical report findings",
  "proeth:createsObligation": [
    "Verify_Strength_Gain_Through_Testing",
    "Present_Geotechnical_Evidence_In_Defense"
  ],
  "proeth:description": "The original geotechnical firm\u0027s report had documented an expectation that piles would gain sufficient strength within 30 days of initial driving, providing a technical basis for Engineer A\u0027s defense.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Pre-construction (report issued before construction); surfaced during mediation",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Geotechnical Report Strength-Gain Anticipation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_Dynamic_Test_Equipment_Failure",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When testing equipment fails during a critical investigation, what are an engineer\u0027s immediate professional obligations?",
    "How does knowingly omitting equipment failure from a technical report differ ethically from simply making an error in analysis?",
    "What systems should be in place to ensure test data integrity is preserved and documented even when equipment fails?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A\u0027s observer is alarmed by implications for data reliability; Engineer B faces a decision point about how to handle compromised data; municipality is anxious about test validity; contractor and other stakeholders uncertain about outcome",
  "proeth-scenario:ethicalImplications": "This event is the technical foundation of the ethics violation: Engineer B\u0027s subsequent omission of this fact from the report transforms a technical setback into a deliberate misrepresentation; raises questions about the engineer\u0027s duty of candor and objectivity in adversarial contexts",
  "proeth-scenario:learningMoment": "Demonstrates that equipment failures during testing are material facts that must be disclosed in any subsequent report; shows how omission of known data limitations constitutes a fundamental breach of engineering integrity.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Test results that could vindicate design are now compromised; independent observer\u0027s documentation becomes critical",
    "engineer_b": "Professional obligation triggered to disclose failure; subsequent omission of this fact from report becomes the central ethics violation",
    "municipality": "Invested in test process now yielding questionable data; must decide how to proceed",
    "public": "Dock safety assessment rests on potentially incomplete data"
  },
  "proeth:activatesConstraint": [
    "Data_Integrity_Constraint",
    "Test_Validity_Constraint",
    "Disclosure_Obligation_In_Reporting"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_Municipality_Retains_Engineer_B",
  "proeth:causesStateChange": "Test data integrity compromised; Engineer B now has affirmative obligation to disclose equipment failure in any report relying on or interpreting test results",
  "proeth:createsObligation": [
    "Document_Equipment_Failure_In_Report",
    "Assess_Impact_On_Data_Validity",
    "Consider_Retest_Or_Alternative_Analysis",
    "Disclose_Limitation_To_All_Stakeholders"
  ],
  "proeth:description": "During the test pile driving exercise, dynamic testing equipment malfunctioned and failed, compromising the reliability and completeness of the pile strength data collected.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "During test pile driving, prior to 30-day set period",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Dynamic Test Equipment Failure"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_Piles_Driven_to_Refusal",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Why is the distinction between \u0027insufficient depth\u0027 and \u0027driven to refusal\u0027 so important in evaluating pile adequacy?",
    "If an engineer knows that piles were driven to refusal but omits this from a report, is that a factual error or an ethical violation? What is the difference?",
    "How should an engineer balance advocacy for their client with the obligation to present complete technical facts?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A\u0027s team feels vindicated by this fact; Engineer B\u0027s omission of this fact later creates moral discomfort for observers aware of it; municipality stakeholders face conflicting technical narratives",
  "proeth-scenario:ethicalImplications": "Directly implicates Engineer B\u0027s duty of objectivity and completeness; reveals how selective presentation of technically accurate facts (insufficient depth) while omitting exculpatory context (driven to refusal) constitutes professional misrepresentation",
  "proeth-scenario:learningMoment": "Illustrates the critical distinction between penetration depth and actual load capacity; shows that \u0027driven to refusal\u0027 is a technically significant condition that must be reported because it fundamentally changes the interpretation of depth-based adequacy conclusions.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Has strong technical defense that piles achieved maximum possible penetration; omission by Engineer B directly harms Engineer A\u0027s professional standing",
    "engineer_b": "Omitting refusal condition from report constitutes a knowing misrepresentation that transforms depth-based criticism into a misleading capacity conclusion",
    "municipality": "Receives a report that omits a fact favorable to Engineer A, potentially biasing decision-making",
    "public": "Dock safety assessment distorted by incomplete technical picture"
  },
  "proeth:activatesConstraint": [
    "Disclosure_Obligation_In_Technical_Report",
    "Complete_Factual_Reporting_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_90-Pile_Foundation_Design",
  "proeth:causesStateChange": "Technical record shows piles achieved maximum possible penetration; this fact materially affects interpretation of depth-based capacity conclusions and must be disclosed in any professional assessment",
  "proeth:createsObligation": [
    "Report_Refusal_Condition_As_Mitigating_Factor",
    "Consider_Wave_Equation_Analysis_For_Refusal_Piles",
    "Distinguish_Depth_Deficiency_From_Capacity_Deficiency"
  ],
  "proeth:description": "All 19 piles later identified by Engineer B as failing were in fact driven to refusal \u2014 the point at which no further penetration is possible \u2014 a material fact indicating maximum achievable embedment.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During original construction and/or test pile driving phase",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Piles Driven to Refusal"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_Mediation_Settlement_Reached",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does settling a lawsuit imply admission of fault, and how should engineers manage this perception?",
    "What obligations does an engineer have to investigate and resolve technical questions even after a legal settlement?",
    "How can the existence of expert testimony during mediation create downstream consequences for professional reputation?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A feels partial vindication but lingering professional concern; municipality officials feel financial and political relief; the unresolved technical questions create ongoing anxiety for Engineer A; contractor achieves financial resolution",
  "proeth-scenario:ethicalImplications": "Reveals the gap between legal resolution and ethical accountability; raises questions about whether financial settlements adequately address public safety concerns; highlights tension between litigation strategy and professional transparency",
  "proeth-scenario:learningMoment": "Demonstrates that legal settlement does not resolve underlying technical or ethical questions; shows how financial resolution can leave professional reputations and public safety concerns unaddressed, necessitating further investigation.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Financial remedy obtained; dispute resolved",
    "engineer_a": "Financial loss from settlement share; professional reputation still under cloud due to unresolved pile performance questions",
    "municipality": "Financial cost shared; political pressure partially relieved; technical dispute continues",
    "public": "Taxpayer funds used for settlement; underlying infrastructure questions unresolved"
  },
  "proeth:activatesConstraint": [
    "Financial_Liability_Constraint",
    "Continued_Technical_Dispute_Resolution"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_Mediation_Settlement_Agreement",
  "proeth:causesStateChange": "Legal dispute formally closed; financial liability allocated; technical questions about pile performance remain unresolved and drive subsequent investigation",
  "proeth:createsObligation": [
    "Payment_Of_Settlement_Share",
    "Continued_Investigation_Of_Pile_Performance",
    "Retention_Of_Technical_Experts"
  ],
  "proeth:description": "The contractor lawsuit was resolved through mediation, resulting in a $300,000 settlement shared between Engineer A and the municipality, ending formal litigation.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During mediation proceedings, prior to pile testing phase",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Mediation Settlement Reached"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_Expert_Testimony_on_Pile_Failures",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What records should Engineer A have maintained to effectively counter this testimony?",
    "How does the role of an expert witness differ from that of an independent technical investigator, and what ethical obligations apply to each?",
    "When expert testimony focuses only on initial driving resistance without considering strength gain over time, is that technically misleading even if factually accurate?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences alarm and urgency to defend design decisions; municipality feels vindicated in questioning pile performance; contractor feels technical claims validated; engineering community observers note reputational stakes",
  "proeth-scenario:ethicalImplications": "Raises questions about the completeness and context of expert testimony; illustrates how technically accurate but incomplete information can create misleading impressions; foreshadows the deeper ethics issues with Engineer B\u0027s later report",
  "proeth-scenario:learningMoment": "Shows how expert testimony can fundamentally shift the technical and legal landscape of a dispute; illustrates the importance of engineers maintaining comprehensive records that can withstand adversarial scrutiny.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Extra claim appears more credible with expert support",
    "engineer_a": "Design competence publicly questioned; must mount technical defense; professional reputation at acute risk",
    "municipality": "Gains technical leverage in settlement negotiations; infrastructure credibility partially restored",
    "public": "Concerns raised about safety of completed dock structure"
  },
  "proeth:activatesConstraint": [
    "Technical_Rebuttal_Obligation",
    "Public_Safety_Verification_Constraint",
    "Professional_Integrity_Defense"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_Mediation_Settlement_Agreement",
  "proeth:causesStateChange": "Pile performance formally contested in legal record; technical burden of proof shifts to Engineer A to demonstrate adequacy of design and construction",
  "proeth:createsObligation": [
    "Engineer_A_Must_Rebut_Technically",
    "Initiate_Pile_Performance_Investigation",
    "Engage_Geotechnical_Expert_Support"
  ],
  "proeth:description": "During mediation, a municipality-retained expert testified that many piles failed to meet driving resistance requirements at initial driving, formally placing pile performance in dispute.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "During mediation proceedings",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Expert Testimony on Pile Failures"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_Contractor_Lawsuit_Filed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What documentation practices could Engineer A have employed to better protect against such claims?",
    "How does the threat of litigation change the professional obligations of an engineer?",
    "At what point does a construction dispute become an ethics issue versus a purely legal one?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences professional anxiety and reputational concern; municipality faces political and financial pressure; contractor is aggrieved and adversarial; observers in the engineering community note the reputational stakes",
  "proeth-scenario:ethicalImplications": "Reveals tension between an engineer\u0027s duty to a client and accountability to broader project stakeholders; raises questions about whether design specifications were communicated clearly enough to prevent contractor confusion and dispute",
  "proeth-scenario:learningMoment": "Illustrates how construction disputes can escalate into legal proceedings with broad professional consequences; emphasizes the importance of thorough documentation and clear specification of requirements during design and construction phases.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "contractor": "Seeks financial remedy for alleged extra work, enters adversarial posture",
    "engineer_a": "Professional reputation at risk, legal costs incurred, design decisions subjected to public scrutiny",
    "municipality": "Public funds at risk, political accountability triggered, infrastructure credibility questioned",
    "public": "Dock safety and municipal spending become matters of concern"
  },
  "proeth:activatesConstraint": [
    "Legal_Defense_Obligation",
    "Professional_Record_Preservation",
    "Duty_To_Cooperate_With_Proceedings"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_90-Pile_Foundation_Design",
  "proeth:causesStateChange": "Engineer A and municipality shift from project-completion mode to legal-defense mode; formal dispute resolution process initiated",
  "proeth:createsObligation": [
    "Retain_Legal_Counsel",
    "Preserve_Project_Documentation",
    "Respond_To_Claims_Formally"
  ],
  "proeth:description": "A contractor filed an extra claim and initiated legal action against both Engineer A and the municipality following dock construction, triggering formal legal proceedings.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Post-construction, prior to mediation",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Contractor Lawsuit Filed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#Event_30-Day_Strength_Gain_Confirmed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When test results confirm strength gain but a report still concludes inadequacy based on depth, what additional analysis is required before issuing the report?",
    "How should an engineer handle a situation where new data contradicts the conclusion they were retained to support?",
    "What does it mean for an engineer to be \u0027objective\u0027 when retained by one party in an adversarial dispute?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A and independent observer feel vindicated; Engineer B faces pressure to reconcile confirmed strength gain with adverse report conclusions; municipality stakeholders receive conflicting signals about pile adequacy",
  "proeth-scenario:ethicalImplications": "Highlights the tension between client advocacy and professional objectivity; confirmed strength gain that is subsequently omitted from Engineer B\u0027s report elevates the omission from oversight to deliberate misrepresentation",
  "proeth-scenario:learningMoment": "Demonstrates that pile capacity is a time-dependent phenomenon and that engineering assessments must account for soil set-up; shows how confirmed test results that contradict a report\u0027s conclusions create an obligation to reconcile or disclose the discrepancy.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Technical defense substantially strengthened; confirmed strength gain supports original design approach",
    "engineer_b": "Must now explain how 19 piles \u0027fail\u0027 despite confirmed overall strength gain; report\u0027s omission of this context becomes harder to justify",
    "municipality": "Receives technically ambiguous picture: strength gain confirmed at test level but Engineer B\u0027s report still condemns 19 piles",
    "public": "Dock may be structurally adequate, but public cannot assess this without complete technical picture"
  },
  "proeth:activatesConstraint": [
    "Complete_Factual_Reporting_Constraint",
    "Obligation_To_Report_Favorable_Technical_Findings"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/71#Action_Municipality_Retains_Engineer_B",
  "proeth:causesStateChange": "Technical evidence now supports Engineer A\u0027s position that piles achieve adequate capacity over time; Engineer B\u0027s subsequent report ignoring this context becomes more clearly problematic",
  "proeth:createsObligation": [
    "Report_Strength_Gain_Confirmation",
    "Integrate_Set_Period_Results_Into_Capacity_Analysis",
    "Reconsider_Adequacy_Conclusions_In_Light_Of_Confirmed_Strength"
  ],
  "proeth:description": "After the 30-day set period following test pile driving, retesting confirmed that the piles had gained sufficient strength, validating the geotechnical report\u0027s predictions and Engineer A\u0027s defense.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "30 days after test pile driving",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "30-Day Strength Gain Confirmed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#CausalChain_69084696",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B deliberately chose not to consult Engineer A\u0027s on-site representatives, contractors, or other stakeholders, and when subsequently questioned by Engineer A after the report was issued, provided two contradictory justifications \u2014 an outcome consistent with the absence of a contemporaneous, consultatively validated record of methodological decisions",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B deliberately excludes Engineer A\u0027s representatives and contractors from the test pile driving process, creating an information asymmetry and eliminating contemporaneous checks on methodological decisions",
      "proeth:element": "Decision to Exclude Stakeholder Consultation",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B issues a report that omits the methodological deviations, leaving no documented rationale for the hammer substitution, pre-count drops, or depth inconsistencies",
      "proeth:element": "Selective Omission in Report",
      "proeth:step": 2
    },
    {
      "proeth:description": "Retesting after the 30-day set period confirms piles had gained sufficient strength, directly contradicting Engineer B\u0027s failure conclusions and prompting Engineer A to question the report\u0027s basis",
      "proeth:element": "30-Day Strength Gain Confirmed",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A challenges Engineer B on the methodological basis for the failure findings, exposing the absence of a documented, consultatively validated rationale",
      "proeth:element": "Engineer A\u0027s Post-Report Questioning",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B provides two contradictory justifications when questioned, revealing that no coherent, pre-established methodological rationale existed \u2014 a direct consequence of the exclusion of consultation and contemporaneous documentation",
      "proeth:element": "Contradictory Post-Report Explanations",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Decision to Exclude Stakeholder Consultation",
  "proeth:counterfactual": "Had Engineer B consulted stakeholders and documented agreed-upon methodological decisions contemporaneously, a consistent and verifiable explanation would have existed, making contradictory post-report justifications unnecessary and unlikely",
  "proeth:effect": "Contradictory Post-Report Explanations",
  "proeth:necessaryFactors": [
    "Absence of contemporaneous consultation record that would have locked Engineer B into a single documented rationale",
    "Engineer A\u0027s post-report questioning that exposed the lack of methodological justification",
    "Engineer B\u0027s need to retroactively justify decisions made without stakeholder input"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Exclusion of consultation + undocumented methodological deviations + post-report scrutiny = sufficient to produce contradictory explanations that reveal the absence of a defensible, pre-established rationale"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#CausalChain_61012b56",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A contractor filed an extra claim and initiated legal action against both Engineer A and the municipality, which directly precipitated the mediation process and the joint decision to settle for $300,000 rather than proceed to trial",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A designs the dock foundation using 90 piles based on the geotechnical firm\u0027s recommendations, establishing the technical baseline that later becomes the subject of dispute",
      "proeth:element": "90-Pile Foundation Design",
      "proeth:step": 1
    },
    {
      "proeth:description": "Contractor files an extra claim and initiates legal action against Engineer A and the municipality, alleging issues with the pile foundation that generated additional costs",
      "proeth:element": "Contractor Lawsuit Filed",
      "proeth:step": 2
    },
    {
      "proeth:description": "During mediation, a municipality-retained expert testifies that many piles failed to meet driving requirements, creating adverse evidentiary pressure on both defendants",
      "proeth:element": "Expert Testimony on Pile Failures",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A and the municipality jointly decide to settle for $300,000 rather than proceed to trial, sharing the financial liability",
      "proeth:element": "Mediation Settlement Agreement",
      "proeth:step": 4
    },
    {
      "proeth:description": "The $300,000 settlement is formally concluded, resolving the contractor\u0027s claims but leaving open questions about the validity of the pile failure findings that informed the settlement",
      "proeth:element": "Mediation Settlement Reached",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Contractor Lawsuit Filed",
  "proeth:counterfactual": "Without the contractor\u0027s lawsuit, no mediation process would have been initiated and no settlement obligation would have arisen; the $300,000 shared liability would not have materialized",
  "proeth:effect": "Mediation Settlement Agreement",
  "proeth:necessaryFactors": [
    "Contractor\u0027s initiation of legal action creating formal litigation exposure for Engineer A and the municipality",
    "Expert testimony during mediation that many piles failed to meet driving requirements, increasing settlement pressure",
    "Joint decision by Engineer A and municipality to share settlement costs rather than contest liability individually"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A and Municipality (shared)",
  "proeth:sufficientFactors": [
    "Active litigation + adverse expert testimony + shared litigation exposure + cost-benefit calculation favoring settlement = sufficient to produce the mediation settlement agreement"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#CausalChain_a8cdaba5",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "All 19 piles later identified by Engineer B as failing were in fact driven to refusal \u2014 the engineering standard indicating maximum load-bearing capacity \u2014 which directly contradicted Engineer B\u0027s failure conclusions and, when raised by Engineer A, forced Engineer B to provide two contradictory post-report justifications",
  "proeth:causalSequence": [
    {
      "proeth:description": "The original geotechnical firm\u0027s report documents an expectation that piles would gain sufficient strength over a 30-day set period, establishing a known and documented protocol for evaluating pile adequacy",
      "proeth:element": "Geotechnical Report Strength-Gain Anticipation",
      "proeth:step": 1
    },
    {
      "proeth:description": "All 19 piles later identified as failing are in fact driven to refusal, the standard engineering indicator of maximum load-bearing capacity \u2014 a fact that is inconsistent with failure conclusions under standard methodology",
      "proeth:element": "Piles Driven to Refusal",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B issues a report concluding these 19 piles failed, without addressing the refusal data or the anticipated strength-gain protocol, creating a factually and methodologically incomplete record",
      "proeth:element": "Selective Omission in Report",
      "proeth:step": 3
    },
    {
      "proeth:description": "Retesting after the 30-day set period confirms the piles gained sufficient strength, providing objective post-report evidence that directly contradicts Engineer B\u0027s failure conclusions",
      "proeth:element": "30-Day Strength Gain Confirmed",
      "proeth:step": 4
    },
    {
      "proeth:description": "When Engineer A confronts Engineer B with the refusal data and strength gain confirmation, Engineer B provides two contradictory justifications, revealing the absence of a coherent, defensible methodological basis for the failure conclusions",
      "proeth:element": "Contradictory Post-Report Explanations",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Piles Driven to Refusal",
  "proeth:counterfactual": "Had the 19 piles not been driven to refusal, or had the 30-day retest not confirmed strength gain, Engineer B\u0027s failure conclusions would have faced less direct factual contradiction and the contradictory explanations might not have been elicited",
  "proeth:effect": "Contradictory Post-Report Explanations",
  "proeth:necessaryFactors": [
    "Physical fact that all 19 identified piles were driven to refusal, establishing a factual basis inconsistent with failure conclusions",
    "30-Day Strength Gain Confirmation providing additional objective evidence contradicting the report",
    "Engineer A\u0027s post-report questioning that brought the refusal data and strength gain data into direct confrontation with Engineer B\u0027s conclusions"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Piles driven to refusal + confirmed 30-day strength gain + Engineer A\u0027s direct questioning = sufficient to expose the internal inconsistency of Engineer B\u0027s report and produce contradictory explanations"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#CausalChain_0cc8dead",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B\u0027s team used a vibratory hammer instead of the original driving method, generating non-standard test conditions that formed the basis for Engineer B\u0027s report concluding 19 of 90 piles failed required safety thresholds",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B\u0027s team substitutes a vibratory hammer for the originally specified driving method, departing from the conditions under which the original 90-pile foundation design was validated",
      "proeth:element": "Vibratory Hammer Substitution Decision",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B\u0027s team drops the hammer multiple times before commencing official counts, further distorting the comparability of test results against original design benchmarks",
      "proeth:element": "Pre-Count Hammer Drop Decision",
      "proeth:step": 2
    },
    {
      "proeth:description": "Test piles are not driven to the same depth as the original design piles, compounding methodological inconsistency and undermining the validity of comparative safety assessments",
      "proeth:element": "Inconsistent Pile Depth Decision",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B does not consult Engineer A\u0027s on-site representatives, contractors, or other stakeholders, preventing identification or correction of methodological deviations before the report is finalized",
      "proeth:element": "Decision to Exclude Stakeholder Consultation",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B issues a formal report concluding 19 of 90 piles failed, without disclosing the hammer substitution, pre-count drops, depth inconsistencies, or dynamic equipment failure \u2014 omissions that render the failure conclusions misleading",
      "proeth:element": "Selective Omission in Report",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Vibratory Hammer Substitution Decision",
  "proeth:counterfactual": "Had the original driving method been used and results been consistent with design specifications, the data underpinning the failure conclusions would not have existed; the report\u0027s findings would likely have been materially different or absent",
  "proeth:effect": "Selective Omission in Report",
  "proeth:necessaryFactors": [
    "Substitution of non-standard vibratory hammer during test pile driving",
    "Absence of consultation with Engineer A\u0027s representatives or original design team",
    "Engineer B\u0027s authority to issue formal engineering report based on flawed test data"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Non-standard hammer substitution + exclusion of stakeholder consultation + Engineer B\u0027s unilateral reporting authority = sufficient to produce a formally issued report based on methodologically compromised data"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/71#",
    "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/71#CausalChain_06591add",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The municipality made a deliberate decision to retain Engineer B to supervise test pile driving as a separate agent from Engineer A, creating a structural condition in which Engineer B operated with unilateral reporting authority in an adversarial litigation context, ultimately producing a report that omitted critical methodological deviations",
  "proeth:causalSequence": [
    {
      "proeth:description": "Municipality retains Engineer B as its own agent to supervise test pile driving, creating a structural conflict of interest in a litigation context where Engineer B\u0027s findings will directly affect the municipality\u0027s legal position",
      "proeth:element": "Municipality Retains Engineer B",
      "proeth:step": 1
    },
    {
      "proeth:description": "Operating as the municipality\u0027s agent without joint oversight obligations, Engineer B excludes Engineer A\u0027s representatives from the testing process",
      "proeth:element": "Decision to Exclude Stakeholder Consultation",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B\u0027s team makes multiple methodological deviations \u2014 hammer substitution, pre-count drops, inconsistent pile depths \u2014 without contemporaneous documentation or consultation",
      "proeth:element": "Vibratory Hammer Substitution Decision and Related Deviations",
      "proeth:step": 3
    },
    {
      "proeth:description": "Equipment malfunction during testing further compromises data integrity, but is not disclosed in the report",
      "proeth:element": "Dynamic Test Equipment Failure",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B issues a formal report concluding 19 piles failed, omitting all methodological deviations and equipment failures \u2014 a report that serves the municipality\u0027s litigation interest",
      "proeth:element": "Selective Omission in Report",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Municipality Retains Engineer B",
  "proeth:counterfactual": "Had the municipality retained a jointly agreed neutral third-party engineer with transparent reporting obligations to all parties, the structural incentive for selective omission would have been substantially reduced",
  "proeth:effect": "Selective Omission in Report",
  "proeth:necessaryFactors": [
    "Municipality\u0027s decision to retain a separate engineer with independent reporting authority rather than using a jointly agreed neutral party",
    "Absence of a shared oversight or peer-review mechanism between Engineer A and Engineer B",
    "Litigation context that gave the municipality a material interest in Engineer B\u0027s findings"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Municipality",
  "proeth:sufficientFactors": [
    "Retention of municipality-aligned engineer + unilateral reporting authority + adversarial litigation context + absence of joint oversight = sufficient structural condition for a selectively omissive report to be issued without correction"
  ],
  "proeth:withinAgentControl": true
}