{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Action_Withhold_Preliminary_Risk_Concerns",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose concerns informally to Client X with a caveat that they are preliminary and unquantified",
    "Document the concern in internal project files and set a formal threshold for when disclosure would be triggered",
    "Pause preliminary design work until the concern could be adequately assessed before proceeding further"
  ],
  "proeth-scenario:characterMotivation": "Engineer L had not yet quantified the risk and may have rationalized that unverified, preliminary concerns did not rise to the level requiring formal disclosure. There may also have been reluctance to alarm the client or jeopardize the contract based on speculative concerns.",
  "proeth-scenario:consequencesIfAlternative": [
    "Client X would have been on notice early, enabling collaborative risk planning; Engineer L would have fulfilled disclosure obligations and established transparency as a project norm, though the client might have reacted negatively to early uncertainty.",
    "Internal documentation would create a professional record of due diligence and a structured decision framework, but would not satisfy the ethical obligation to inform the client or the public of a potential health risk.",
    "Pausing design would delay the project and potentially frustrate Client X, but would allow Engineer L to develop a more informed risk picture before proceeding, reducing the likelihood of compounding omissions later."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the critical question of when an engineer\u0027s obligation to disclose risk is triggered \u2014 does it require quantified certainty, or does a reasonable professional concern suffice? Teaches that the threshold for disclosure involving public health risks is intentionally low.",
  "proeth-scenario:ethicalTension": "Duty to protect public health and safety (NSPE Canon 1) vs. professional caution about communicating unverified findings vs. contractual loyalty to Client X and desire to preserve the working relationship.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Community drinking water safety; Engineer L\u0027s professional integrity; establishment of a pattern of non-disclosure that compounds over time; potential future liability if harm occurs.",
  "proeth:description": "During the preliminary design phase, Engineer L identified emerging concerns about increased stormwater risk over time but chose not to disclose these concerns to Client X before the project was suspended. No formal or informal communication of potential risk was made at this stage.",
  "proeth:foreseenUnintendedEffects": [
    "Client X proceeds without awareness of potential risk trajectory",
    "Window for early protective design decisions closes",
    "Community drinking water source remains unprotected from an emerging but uncharacterized threat"
  ],
  "proeth:fulfillsObligation": [
    "Arguably avoided premature alarmism inconsistent with factual basis (epistemic caution)"
  ],
  "proeth:guidedByPrinciple": [
    "Epistemic threshold for disclosure: facts vs. concerns",
    "Precautionary principle in public health engineering",
    "Transparency as a foundation of professional trust"
  ],
  "proeth:hasAgent": "Engineer L (Licensed Engineer / Designer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Premature disclosure of unverified risk vs. timely warning to protect public health",
    "proeth:resolutionReasoning": "Engineer L implicitly prioritized epistemic rigor over precautionary disclosure, treating the lack of quantified data as justification for silence; however, the Discussion section suggests that even qualitative professional concern near a public water source may trigger a duty of early informal notice"
  },
  "proeth:hasMentalState": "deliberate omission \u2014 consciously chose not to disclose unquantified concerns",
  "proeth:intendedOutcome": "Avoid alarming client with unverified concerns; wait until risk could be substantiated before raising it",
  "proeth:requiresCapability": [
    "Stormwater hydrology assessment",
    "Risk identification and professional judgment",
    "Client communication protocols"
  ],
  "proeth:temporalMarker": "Preliminary design phase, prior to project suspension",
  "proeth:violatesObligation": [
    "NSPE Code I.4 \u2014 duty to act as faithful agent includes informing client of material concerns affecting project scope",
    "NSPE Code II.3.a \u2014 engineers shall be objective and truthful in professional reports and disclosures",
    "Emerging obligation under Canon I.1 to protect public health, safety, and welfare when a foreseeable risk is developing",
    "BER precedent obligation to disclose known or reasonably anticipated risks affecting third parties (community water supply)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Withhold Preliminary Risk Concerns"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Action_Omit_Risk_During_Suspension",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Include a written note in suspension correspondence flagging the preliminary risk concern and recommending it be addressed upon resumption",
    "Use the suspension as an opportunity to conduct further risk assessment independently, so that a more substantiated concern could be communicated upon resumption",
    "Formally withdraw from the project during suspension, citing unresolved safety concerns as the basis"
  ],
  "proeth-scenario:characterMotivation": "With the project being suspended for financial reasons, Engineer L may have viewed suspension communications as administrative rather than technical in nature, and reasoned that raising risk concerns about a paused project was premature or unnecessary. There may also have been an implicit hope that the project would not resume.",
  "proeth-scenario:consequencesIfAlternative": [
    "Client X would have had documented notice of the risk prior to resumption, preserving their autonomy to make informed decisions; Engineer L would have created a clear paper trail of ethical compliance, though it might have prompted difficult conversations.",
    "Proactive use of the suspension period for study would have positioned Engineer L to provide a more credible and actionable risk disclosure upon resumption, reducing the gap between concern and formal notification.",
    "Withdrawal would have been a strong protective action for public safety but potentially disproportionate at this stage given the unquantified nature of the risk; it would have ended the contractual relationship and possibly triggered disputes."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical obligations do not pause when a project pauses. Teaches students that suspension or transition moments are often the most important windows for disclosure, as they represent natural checkpoints before further commitment is made.",
  "proeth-scenario:ethicalTension": "Duty of honest and complete communication with the client vs. practical judgment about relevance during a suspension period vs. concern that raising unquantified risks could permanently derail a project and harm the professional relationship.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Client X\u0027s ability to make an informed decision about whether and how to resume the project; Engineer L\u0027s ongoing credibility and trustworthiness; the community\u0027s right to have risks factored into project decisions from the outset.",
  "proeth:description": "When Client X communicated the project suspension due to financial setbacks, Engineer L chose not to mention the potential drinking water risk that had been identified during the preliminary design phase. Suspension communications proceeded without any reference to the emerging concern.",
  "proeth:foreseenUnintendedEffects": [
    "Client X remains uninformed of risk during a period when protective decisions could still be made",
    "Time passes without any protective measures being considered or planned",
    "If risk materializes during suspension, Engineer L\u0027s prior silence becomes ethically and legally significant"
  ],
  "proeth:fulfillsObligation": [
    "Honored client\u0027s request for suspension without introducing complicating disputes",
    "Avoided burdening client with unsubstantiated technical claims during a financial hardship period"
  ],
  "proeth:guidedByPrinciple": [
    "Continuity of professional duty through project interruptions",
    "Transparency and full disclosure as baseline professional obligations",
    "Public safety obligations do not pause when projects are suspended"
  ],
  "proeth:hasAgent": "Engineer L (Licensed Engineer / Designer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Respecting client\u0027s good-faith suspension vs. disclosing emerging public safety risk",
    "proeth:resolutionReasoning": "Engineer L chose to defer disclosure, treating the client\u0027s financial situation and the unquantified nature of the risk as jointly sufficient reasons for silence; this decision is identified in the Discussion as ethically problematic because the public safety dimension of the risk did not diminish during the suspension period"
  },
  "proeth:hasMentalState": "deliberate \u2014 Engineer L made a conscious choice about what to include in suspension communications",
  "proeth:intendedOutcome": "Respect client\u0027s good-faith suspension request without complicating it with unverified technical concerns; preserve client relationship during a financially sensitive moment",
  "proeth:requiresCapability": [
    "Professional judgment on disclosure thresholds",
    "Client communication and relationship management",
    "Risk characterization under uncertainty"
  ],
  "proeth:temporalMarker": "Work suspension period, during communications with Client X about financial setback",
  "proeth:violatesObligation": [
    "NSPE Code II.3.a \u2014 engineers shall be objective and truthful in professional communications",
    "NSPE Code III.1.b \u2014 engineers shall not misrepresent or withhold facts that are relevant to professional judgments affecting public safety",
    "Canon I.1 \u2014 duty to hold public health paramount extends through project interruptions",
    "NSPE Code I.4 \u2014 faithful agent duty includes ensuring client has material information needed to make informed decisions about the project"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Omit Risk During Suspension"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Action_Resume_Work_Without_Disclosure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Condition acceptance of resumption on a preliminary risk review meeting with Client X before restarting design work",
    "Send a written disclosure of the previously identified concern as a prerequisite to signing any resumption agreement",
    "Decline to resume the project until additional risk studies could be completed and shared with the client"
  ],
  "proeth-scenario:characterMotivation": "Engineer L may have been motivated by financial need, professional investment in the project, or optimism that the risk concern would prove manageable upon further study. Accepting resumption without disclosure may also reflect a normalization of the earlier omissions \u2014 having not disclosed before, disclosure now felt awkward or inconsistent.",
  "proeth-scenario:consequencesIfAlternative": [
    "A required risk review meeting would have created a structured forum for disclosure, normalized safety as a project priority, and given Client X agency in deciding how to proceed with full information.",
    "Written disclosure prior to resumption would have fulfilled the engineer\u0027s ethical obligations, created a clear legal and professional record, and reset the transparency baseline for the project.",
    "Declining to resume pending study completion would have delayed the project but ensured that recommitment was based on a fully informed understanding of risks, preventing the situation where work proceeds ahead of adequate safety assessment."
  ],
  "proeth-scenario:decisionSignificance": "Highlights the concept of compounding omissions \u2014 each failure to disclose makes the next disclosure harder and raises the stakes of eventual revelation. Teaches that resumption of work is a clear decision point requiring a clean slate of disclosure before new commitments are made.",
  "proeth-scenario:ethicalTension": "Obligation to disclose known concerns before recommitting to work vs. contractual and financial incentives to resume vs. the psychological difficulty of raising a concern that had already been passed over twice, creating a compounding ethical debt.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer L\u0027s professional credibility if the risk later materializes; Client X\u0027s informed consent to resume the project; the community\u0027s drinking water safety; the integrity of the engineer-client relationship going forward.",
  "proeth:description": "When Client X\u0027s finances improved and Engineer L was asked to resume the project, Engineer L accepted the resumption without raising the prior risk concerns that had been identified during the preliminary design phase. Work recommenced without any prior disclosure of the emerging stormwater risk.",
  "proeth:foreseenUnintendedEffects": [
    "Client X continues to lack awareness of risk identified months earlier",
    "The resumption implicitly signals to Client X that no outstanding concerns exist",
    "Engineer L\u0027s credibility and ethical standing are further compromised if risk later materializes and prior silence is scrutinized"
  ],
  "proeth:fulfillsObligation": [
    "Honored contractual obligation to resume work when client was ready",
    "Maintained the professional engagement needed to conduct further risk studies"
  ],
  "proeth:guidedByPrinciple": [
    "Full and timely disclosure as a precondition for ethical resumption of professional services",
    "Continuity of professional duty \u2014 obligations carry forward across project interruptions",
    "Informed consent principle \u2014 client must have material information to make valid decisions about project resumption"
  ],
  "proeth:hasAgent": "Engineer L (Licensed Engineer / Designer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Contractual obligation to resume vs. ethical obligation to disclose prior concerns before resuming",
    "proeth:resolutionReasoning": "Engineer L chose resumption without disclosure, possibly reasoning that forthcoming studies would either confirm or dispel the concern before it needed to be raised; the Discussion identifies this as an ethically insufficient rationale given the public safety stakes"
  },
  "proeth:hasMentalState": "deliberate \u2014 Engineer L chose to resume without initiating a disclosure conversation",
  "proeth:intendedOutcome": "Restore the professional engagement and move forward with the project; potentially intended to address risk concerns through the forthcoming design work itself",
  "proeth:requiresCapability": [
    "Project management and client communication",
    "Stormwater system design",
    "Professional judgment on disclosure timing"
  ],
  "proeth:temporalMarker": "Project resumption, several months after suspension",
  "proeth:violatesObligation": [
    "NSPE Code II.3.a \u2014 engineers shall be truthful and not withhold relevant professional information",
    "NSPE Code III.3.a \u2014 engineers shall not misrepresent their professional qualifications or the status of a project",
    "Canon I.1 \u2014 resuming work on a project with a known unaddressed risk concern without disclosure violates the paramount duty to public safety",
    "NSPE Code I.4 \u2014 faithful agent duty requires client to be informed of material facts before work resumes",
    "NSPE Code II.3.b \u2014 engineers shall promptly inform clients of factors that may affect project outcomes"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Resume Work Without Disclosure"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Action_Formally_Notify_Client_of_Risk",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Notify Client X informally first to allow a collaborative response before issuing formal written notification",
    "Simultaneously notify Client X and relevant regulatory authorities given the public health implications",
    "Notify Client X and propose a range of protective measure options at different cost levels to reduce the barrier to compliance"
  ],
  "proeth-scenario:characterMotivation": "Having now developed qualitative evidence of a real risk, Engineer L was motivated by professional duty, NSPE Code obligations, and the moral weight of the community\u0027s dependence on the drinking water source. Formal notification also served to correct the record after prior omissions and to establish a defensible professional position.",
  "proeth-scenario:consequencesIfAlternative": [
    "Informal notification first might have preserved the relationship and opened dialogue, but risks the concern being minimized or ignored without a formal record; in cases involving public health, formal documentation is generally required.",
    "Simultaneous regulatory notification would have maximized protection of the public interest and removed the decision about safeguards from Client X\u0027s sole discretion, but would likely have ended the professional relationship and may have been disproportionate before Client X had an opportunity to respond.",
    "Offering tiered protective measure options would have demonstrated professional problem-solving and reduced the financial barrier to compliance, potentially avoiding the impasse that followed; this approach is consistent with best practices in client communication around risk mitigation."
  ],
  "proeth-scenario:decisionSignificance": "Represents the ethical recovery point in the narrative \u2014 the moment where Engineer L fulfills a core professional obligation. Teaches that formal notification of risk to public health is non-negotiable under the NSPE Code and that doing the right thing late is still better than not doing it, though it does not erase prior omissions.",
  "proeth-scenario:ethicalTension": "Duty to notify vs. awareness that formal notification may damage or end the client relationship vs. concern that the notification comes late relative to when concerns first arose, which may itself raise questions about prior conduct. There is also tension between recommending safeguards and respecting the client\u0027s financial constraints.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Community drinking water safety; Engineer L\u0027s professional standing and license; Client X\u0027s ability to make an informed decision about the project; potential legal liability for all parties if harm occurs after notification is ignored.",
  "proeth:description": "After completing additional studies, Engineer L formally notified Client X of the identified stormwater runoff risk to the watershed and recommended that additional protective measures be implemented before proceeding with the project. This notification fulfilled multiple NSPE Code obligations regarding disclosure of risks to public health.",
  "proeth:foreseenUnintendedEffects": [
    "Client X may refuse protective measures due to budget constraints",
    "Formal notification creates a documented record that may have legal implications",
    "Notification may strain the client relationship or jeopardize Engineer L\u0027s engagement",
    "If Client X refuses safeguards, Engineer L will face a critical ethical decision about whether to continue work"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code I.4 \u2014 acted as faithful agent by ensuring client has material information affecting project decisions",
    "NSPE Code II.3.a \u2014 provided objective and truthful professional assessment to client",
    "NSPE Code II.3.b \u2014 promptly informed client of factors that may affect project outcomes",
    "NSPE Code III.1.b \u2014 took affirmative action to inform client of risk to public welfare",
    "NSPE Code III.3.a \u2014 fulfilled duty to report conditions endangering public safety",
    "Canon I.1 \u2014 acted to protect public health, safety, and welfare by ensuring risk was disclosed"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency and full disclosure as foundational professional obligations",
    "Proactive protection of public health over deference to client preferences",
    "Professional courage \u2014 disclosing unwelcome findings regardless of anticipated client reaction",
    "Documented communication as professional best practice"
  ],
  "proeth:hasAgent": "Engineer L (Licensed Engineer / Designer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client relationship preservation vs. mandatory public safety disclosure",
    "proeth:resolutionReasoning": "Engineer L correctly prioritized mandatory disclosure over client relationship preservation; the Discussion affirms this as the ethically required action under Codes I.4, II.3.a, II.3.b, III.1.b, and III.3.a, and consistent with BER precedent from 1967 through 2022"
  },
  "proeth:hasMentalState": "deliberate and obligatory \u2014 Engineer L recognized the confirmed risk triggered a mandatory disclosure and recommendation duty",
  "proeth:intendedOutcome": "Ensure Client X has full knowledge of the identified risk and the professional recommendation for protective measures; fulfill Code obligations and create a documented record of disclosure; enable Client X to make an informed decision about how to proceed",
  "proeth:requiresCapability": [
    "Professional risk communication",
    "Technical report preparation",
    "Protective measure design and recommendation",
    "Knowledge of applicable NSPE Code obligations"
  ],
  "proeth:temporalMarker": "Post-study notification phase, following completion of additional risk studies",
  "proeth:withinCompetence": true,
  "rdfs:label": "Formally Notify Client of Risk"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Action_Conduct_Additional_Risk_Studies",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Commission a third-party independent risk assessment to supplement or validate internal findings",
    "Conduct studies but delay formal notification until a fully quantitative risk estimate could be produced",
    "Share preliminary study findings with Client X in real time as they developed, rather than waiting for a completed assessment"
  ],
  "proeth-scenario:characterMotivation": "The historic rainfall event provided concrete, observable evidence that elevated Engineer L\u0027s concern from speculative to credible. Engineer L was motivated by professional responsibility to assess the situation rigorously and by the recognition that the risk could no longer be deferred without additional investigation.",
  "proeth-scenario:consequencesIfAlternative": [
    "A third-party assessment would have added credibility and objectivity to the findings, potentially making it harder for Client X to dismiss the risk, though it would have introduced additional cost and time.",
    "Delaying notification pending full quantification would have repeated the earlier pattern of withholding concerns and could have allowed design work to proceed further in an unsafe direction; qualitative risk estimates are sufficient to trigger disclosure obligations.",
    "Real-time sharing of developing findings would have kept Client X informed and engaged throughout the assessment process, fostering collaborative problem-solving rather than presenting a completed finding that the client might receive as a confrontation."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the role of external events in forcing ethical reckonings that internal discipline should have prompted earlier. Teaches that while conducting additional studies is the right action, it should not have required a triggering event \u2014 the obligation existed from the preliminary design phase.",
  "proeth-scenario:ethicalTension": "Tension between acting promptly on a newly urgent situation vs. the discomfort of having previously withheld concerns \u2014 conducting studies now implicitly acknowledges that earlier omissions may have been ethically problematic. There is also tension between thoroughness and the pressure to resume productive design work.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Accuracy and completeness of the risk assessment; the community\u0027s drinking water; Engineer L\u0027s ability to make a credible and defensible formal notification; the quality of the evidence base for any recommended protective measures.",
  "proeth:description": "Following project resumption and coinciding with a historic heavy rainfall event that elevated on-site stormwater accumulation, Engineer L conducted additional studies to assess the risk of stormwater runoff into the watershed. These studies produced a qualitative estimate that a real risk of runoff into the community\u0027s drinking water source existed.",
  "proeth:foreseenUnintendedEffects": [
    "Studies may confirm a risk that obligates Engineer L to notify Client X and potentially recommend costly protective measures",
    "Confirmed risk may create conflict with Client X over budget and project scope",
    "Studies elevate Engineer L\u0027s professional and ethical responsibility by converting concern into documented finding"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code I.1 \u2014 proactive investigation of foreseeable public health risk near drinking water source",
    "NSPE Code II.3.a \u2014 gathering objective factual basis before making professional representations",
    "NSPE Code III.1.b \u2014 taking affirmative steps to characterize risks to public welfare",
    "Professional competence obligation \u2014 applying technical expertise to assess risk within area of practice"
  ],
  "proeth:guidedByPrinciple": [
    "Due diligence as a professional standard before proceeding with design work",
    "Precautionary principle \u2014 heightened scrutiny warranted near public water sources",
    "Factual grounding as prerequisite for professional disclosure and recommendation"
  ],
  "proeth:hasAgent": "Engineer L (Licensed Engineer / Designer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Project momentum and client expectations vs. thorough risk characterization before proceeding",
    "proeth:resolutionReasoning": "Engineer L correctly resolved in favor of risk assessment, recognizing that the rainfall event and proximity to drinking water elevated the professional obligation to investigate; this decision is consistent with Canon I.1 and BER precedent cited in the Discussion"
  },
  "proeth:hasMentalState": "deliberate and professionally responsible \u2014 Engineer L proactively investigated the risk rather than proceeding without assessment",
  "proeth:intendedOutcome": "Characterize the stormwater risk sufficiently to meet the disclosure threshold and inform design decisions; fulfill professional duty to investigate foreseeable risks before proceeding with design",
  "proeth:requiresCapability": [
    "Stormwater hydrology and watershed analysis",
    "Qualitative risk assessment methodology",
    "Environmental engineering judgment near sensitive receptors"
  ],
  "proeth:temporalMarker": "Post-resumption study phase, concurrent with historic rainfall event",
  "proeth:withinCompetence": true,
  "rdfs:label": "Conduct Additional Risk Studies"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Action_Continue_Work_Despite_Refusal",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Withdraw from the project entirely, citing the inability to proceed ethically without the required safeguards, and document the withdrawal and its basis in writing",
    "Notify the relevant regulatory authority or public health agency of the identified risk before making a final decision about continued participation",
    "Propose a project redesign that incorporates protective measures within Client X\u0027s existing budget constraints as a condition of continued work"
  ],
  "proeth-scenario:characterMotivation": "Engineer L faces competing pressures: financial dependence on the contract, professional investment in the project, possible sympathy for Client X\u0027s genuine budget constraints, and uncertainty about what obligations exist after formal notification has been given. The motivation to continue may also reflect hope that the risk will not materialize or that a compromise will emerge.",
  "proeth-scenario:consequencesIfAlternative": [
    "Withdrawal is the ethically required action according to the Discussion\u0027s conclusion and decades of BER precedent; it protects the public, preserves Engineer L\u0027s professional integrity, and creates a clear record of ethical compliance, though it forfeits the contract and may result in financial and legal consequences.",
    "Regulatory notification would invoke external oversight to protect the public interest independent of the client\u0027s decision, fulfilling the engineer\u0027s obligation to society even if the client refuses to act; this may be required in addition to, not instead of, withdrawal.",
    "A redesign proposal within budget constraints demonstrates professional creativity and good faith, and could resolve the impasse; however, if no feasible protective design exists within the budget, this alternative merely delays the same ethical decision point without resolving it."
  ],
  "proeth-scenario:decisionSignificance": "The culminating teaching moment of the scenario. Illustrates that the engineer\u0027s obligation to the public supersedes obligations to the client when the two conflict, and that continuing work under unsafe conditions \u2014 even under client direction \u2014 constitutes an ethical violation. Demonstrates the limits of client authority over engineering judgment.",
  "proeth-scenario:ethicalTension": "Paramount obligation to protect public health and safety (NSPE Canon 1) vs. contractual obligation to Client X vs. financial self-interest vs. respect for the client\u0027s autonomy and business judgment. This is the core ethical dilemma of the entire case.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Community drinking water safety at maximum risk; Engineer L\u0027s professional license and reputation; potential civil and criminal liability if harm occurs; the integrity of the engineering profession\u0027s social contract with the public.",
  "proeth:description": "Following Client X\u0027s refusal to implement protective measures, Engineer L faces the decision of whether to continue work on the project without the safeguards identified as necessary to protect the community\u0027s drinking water source. The Discussion concludes that continuing work under these conditions would be unethical, making this a critical volitional decision point.",
  "proeth:foreseenUnintendedEffects": [
    "Continuation without safeguards exposes the community\u0027s drinking water source to confirmed runoff risk",
    "Continuation creates professional liability exposure for Engineer L",
    "Continuation may constitute a violation of Canon I.1 and multiple Code provisions",
    "Withdrawal may harm Engineer L\u0027s professional livelihood but fulfills ethical obligations",
    "Withdrawal without further action may leave the public unprotected if no other engineer or authority intervenes"
  ],
  "proeth:fulfillsObligation": [
    "If Engineer L withdraws: Canon I.1 \u2014 protection of public health over client and financial interests",
    "If Engineer L withdraws: NSPE Code III.3.a \u2014 refusal to participate in a project that endangers public safety",
    "If Engineer L withdraws: BER Case 84-5 principle \u2014 safety success cannot be sacrificed for economic success"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of Canon I.1 over all other professional obligations",
    "BER Case 84-5: both economic and safety dimensions of project success must be achieved",
    "Professional withdrawal as an ethical obligation when continuation would violate public safety duties",
    "Engineer\u0027s independent professional judgment cannot be subordinated to client financial preferences when public safety is at stake"
  ],
  "proeth:hasAgent": "Engineer L (Licensed Engineer / Designer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Contractual obligation and professional livelihood vs. paramount duty to protect public health",
    "proeth:resolutionReasoning": "The Discussion concludes that continuation without safeguards is ethically impermissible under Canon I.1 and BER precedent spanning 1967\u20132022; Engineer L must withdraw from the project if Client X will not implement the identified protective measures, as the paramount duty to public health overrides all competing professional and financial obligations"
  },
  "proeth:hasMentalState": "deliberate \u2014 continuation would require an affirmative choice to proceed despite known, confirmed, and unmitigated risk",
  "proeth:intendedOutcome": "If Engineer L chooses to continue: maintain the professional engagement, preserve the client relationship, and complete the contracted work; if Engineer L withdraws: fulfill ethical obligations at the cost of the professional engagement",
  "proeth:requiresCapability": [
    "Ethical decision-making under professional pressure",
    "Knowledge of NSPE Code withdrawal obligations",
    "Professional courage to prioritize public safety over client and financial interests",
    "Understanding of BER precedent on engineer withdrawal obligations"
  ],
  "proeth:temporalMarker": "Unresolved endpoint, following Client X\u0027s refusal of protective measures",
  "proeth:violatesObligation": [
    "If Engineer L continues: Canon I.1 \u2014 paramount duty to hold public health, safety, and welfare above all other obligations",
    "If Engineer L continues: NSPE Code II.3.b \u2014 obligation not to proceed when factors affecting public safety are unresolved",
    "If Engineer L continues: NSPE Code III.1.b \u2014 obligation not to complete work that poses confirmed risk to public welfare",
    "If Engineer L continues: NSPE Code III.3.a \u2014 obligation to report and refuse to participate in decisions endangering public safety",
    "If Engineer L continues: BER precedent from 1967\u20132022 establishing that engineers cannot ethically complete projects that compromise public safety when client refuses to implement identified safeguards"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Continue Work Despite Refusal"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Event_Preliminary_Risk_Concerns_Emerge",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what threshold of certainty does an engineer\u0027s concern become a professional obligation to disclose \u2014 must it be quantifiable, or is qualitative judgment sufficient?",
    "How does the proximity of this stormwater system to a community drinking water source change the ethical calculus compared to a more isolated site?",
    "If Engineer L had disclosed these preliminary concerns immediately, how might the subsequent events have unfolded differently?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer L experiences cognitive dissonance \u2014 professional instinct signals danger while the absence of hard data creates uncertainty and hesitation; a quiet internal alarm begins; Client X is unaware and therefore unaffected at this stage; the community near the drinking water source is unknowingly at risk",
  "proeth-scenario:ethicalImplications": "Reveals the tension between epistemic humility (not wanting to alarm without proof) and the precautionary principle (acting on incomplete but credible risk signals); challenges the assumption that disclosure requires certainty; highlights that public safety obligations may outweigh professional comfort with ambiguity",
  "proeth-scenario:learningMoment": "Students should understand that professional ethical obligations \u2014 particularly disclosure duties \u2014 are triggered by the existence of a cognizable concern, not merely by the ability to quantify that concern precisely. The emergence of unquantified risk is itself an ethically significant event.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_X": "Remains uninformed of a risk that could materially affect project scope and cost; opportunity for early, low-cost intervention is silently closing",
    "community": "Drinking water source enters a period of unacknowledged vulnerability; no protective action is yet possible because no disclosure has occurred",
    "engineer_L": "Enters a state of professional tension between incomplete knowledge and emerging duty to disclose; seeds of the ethical dilemma are planted",
    "profession": "The moment tests whether engineering ethics norms around disclosure apply before quantification \u2014 a foundational question for the case"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Disclosure_Constraint",
    "Competent_Practice_Constraint",
    "Duty_To_Inform_Client_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/8#Action_Withhold_Preliminary_Risk_Concerns",
  "proeth:causesStateChange": "Engineer L transitions from routine design mode to heightened professional vigilance; a latent ethical obligation to disclose is activated even before quantification is possible; the project\u0027s risk profile is internally elevated",
  "proeth:createsObligation": [
    "Monitor_And_Quantify_Risk",
    "Disclose_Concerns_To_Client_When_Sufficiently_Formed",
    "Document_Risk_Observations",
    "Continue_Investigation_To_Characterize_Risk"
  ],
  "proeth:description": "During preliminary design, Engineer L develops internal concerns about increasing stormwater risk over time, though the risk cannot yet be quantified. This marks the first moment a potential hazard to the community\u0027s drinking water source enters the professional awareness of the engineer of record.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During preliminary design phase, before project suspension",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Preliminary Risk Concerns Emerge"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Event_Project_Suspension_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the suspension of a project suspend an engineer\u0027s duty to disclose safety concerns, or does that duty persist regardless of project status?",
    "What information should an engineer provide to a client during suspension communications, beyond purely administrative matters?",
    "How does Client X\u0027s financial stress affect the ethical analysis \u2014 should Engineer L have been more or less forthcoming given the client\u0027s vulnerability?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Client X likely experiences financial stress and project frustration; Engineer L may feel relief at the pause but also faces a decision point about whether to disclose concerns during suspension communications; the community near the drinking water source remains unaware",
  "proeth-scenario:ethicalImplications": "Tests whether professional duties are project-phase-dependent or continuous; reveals how administrative events (suspension) can create ethical inflection points; highlights the risk that engineers may rationalize silence during pauses as \u0027waiting for the right time\u0027 \u2014 a form of indefinite deferral",
  "proeth-scenario:learningMoment": "Students should recognize that project suspension does not suspend ethical obligations \u2014 a communication checkpoint created by suspension is itself an opportunity and obligation to disclose known concerns, particularly those affecting public safety.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_X": "Loses access to risk information that could inform decisions made during the financial restructuring period, including whether to ultimately resume the project",
    "community": "Continues to be unaware of potential risk; the suspension delays any protective action further",
    "engineer_L": "Faces a concrete communication opportunity \u2014 suspension communications are a natural moment to surface concerns; failure to use this window compounds the initial withholding",
    "project": "Timeline disrupted; risk monitoring paused; the site conditions that generated Engineer L\u0027s concerns continue to exist and potentially evolve during the hiatus"
  },
  "proeth:activatesConstraint": [
    "Suspension_Communication_Duty_Constraint",
    "Duty_To_Inform_Client_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/8#Action_Omit_Risk_During_Suspension",
  "proeth:causesStateChange": "Project enters suspended state; active engineering work ceases; a communication window opens between Engineer L and Client X during which disclosure of risk concerns would be both possible and professionally required; Engineer L\u0027s silence during this window becomes ethically significant",
  "proeth:createsObligation": [
    "Disclose_Known_Concerns_During_Suspension_Communications",
    "Document_Project_Status_Including_Risk_Observations",
    "Ensure_Client_Has_Information_Needed_For_Informed_Resumption_Decision"
  ],
  "proeth:description": "Client X suspends the stormwater management project due to financial setbacks, halting all active design work. This exogenous financial event interrupts the project timeline and creates a communication juncture during which Engineer L\u0027s undisclosed risk concerns remain unshared.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After preliminary design phase, before risk disclosure occurs",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Project Suspension Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Event_Historic_Rainfall_Event_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How does the occurrence of the historic rainfall event change Engineer L\u0027s ethical obligations compared to the pre-suspension period when risk was only theoretical?",
    "Should Engineer L have anticipated that a rainfall event could occur during the project hiatus or upon resumption, and does that foreseeability affect the ethical analysis?",
    "At what point does an exogenous event like extreme weather transform a professional concern into an emergency requiring immediate escalation beyond the client?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer L likely experiences alarm and a sense of vindication of earlier concerns, mixed with urgency and possibly guilt about prior silence; Client X may feel the project is suddenly more complicated and costly than anticipated; the community near the drinking water source faces an unrecognized but real threat to their water supply",
  "proeth-scenario:ethicalImplications": "Demonstrates how natural events can serve as ethical forcing functions \u2014 removing ambiguity about whether action is required; reveals the compounding risk of deferred disclosure (earlier silence now has higher stakes consequences); raises questions about engineer\u0027s duty to anticipate foreseeable natural events in risk-sensitive design contexts; highlights tension between client-engineer relationship and broader public safety obligations",
  "proeth-scenario:learningMoment": "Students should understand that exogenous events \u2014 particularly natural events \u2014 can dramatically and suddenly change the ethical urgency of a situation. An engineer\u0027s prior inaction that was arguably defensible in a low-urgency context may become indefensible when a triggering event raises the stakes. The timing of the rainfall event relative to resumption is a critical narrative and ethical inflection point.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client_X": "Faces a project that has become materially more complex and potentially more expensive precisely when they have just recommitted financially",
    "community": "Drinking water source faces acute, elevated risk; community members are unaware and have no opportunity to protect themselves",
    "engineer_L": "Prior concerns are now empirically supported; professional obligation to act becomes unambiguous and urgent; the cost of earlier silence becomes apparent",
    "regulatory_authorities": "May have jurisdiction over watershed protection; their potential role in the situation is activated by this event",
    "watershed_ecosystem": "Faces potential contamination from uncontrolled stormwater runoff"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Immediate_Risk_Assessment_Constraint",
    "Duty_To_Inform_Client_Constraint",
    "Watershed_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/8#Action_Resume_Work_Without_Disclosure",
  "proeth:causesStateChange": "Site risk profile escalates from theoretical/preliminary to observable and acute; stormwater accumulation provides empirical evidence supporting Engineer L\u0027s earlier concerns; the ethical urgency of disclosure and protective action increases substantially; the case moves from slow-burn to escalation",
  "proeth:createsObligation": [
    "Conduct_Immediate_Additional_Risk_Studies",
    "Assess_Runoff_Threat_To_Watershed",
    "Expedite_Disclosure_To_Client",
    "Consider_Notification_To_Relevant_Authorities"
  ],
  "proeth:description": "A historic heavy rainfall event coincides with Client X\u0027s resumption of the project, causing elevated on-site stormwater accumulation. This exogenous natural event materially increases the observable and measurable risk to the nearby drinking water source.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Months after suspension; coinciding with project resumption",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Historic Rainfall Event Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Event_Runoff_Risk_Qualitatively_Confirmed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the confirmation of risk qualitatively rather than quantitatively affect the strength of Engineer L\u0027s obligation to disclose and act \u2014 why or why not?",
    "Now that risk is confirmed, what is the minimum acceptable response from Engineer L, and what happens if Client X refuses that minimum?",
    "How does the fact that a community\u0027s drinking water source is at risk \u2014 as opposed to, say, a private property \u2014 affect the ethical analysis and Engineer L\u0027s obligations to parties beyond the client?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer L faces a moment of professional reckoning \u2014 the concern they held silently is now confirmed, and the weight of prior silence becomes palpable; there may be anxiety about how Client X will respond; the community faces a real, confirmed threat they do not know about; Client X is about to receive unwelcome news at a financially difficult moment",
  "proeth-scenario:ethicalImplications": "Crystallizes the core tension of the case: engineer\u0027s duty to client versus engineer\u0027s paramount duty to public safety; establishes that confirmed risk to public health cannot be subordinated to client financial interests; raises the question of whether Engineer L\u0027s prior silence has itself caused harm by delaying protective action; tests the limits of client confidentiality when public safety is at stake",
  "proeth-scenario:learningMoment": "Students should understand that qualitative risk confirmation \u2014 even without full quantification \u2014 is professionally and ethically sufficient to trigger mandatory disclosure and protective action obligations. The standard is not certainty but professional judgment. This event also illustrates that deferred disclosure compounds ethical liability.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client_X": "About to learn that the project they have just recommitted to carries a confirmed public safety risk requiring additional investment they may not have budgeted for",
    "community": "Faces confirmed risk to drinking water source; their safety is now contingent on decisions made by parties they have no knowledge of or influence over",
    "engineer_L": "Professional obligation is now unambiguous; prior silence is retroactively more problematic; must now act decisively or face serious ethical and potentially legal consequences",
    "engineering_profession": "This moment tests whether BER precedent and NSPE Code obligations are operationalized in practice",
    "regulatory_authorities": "Have a legitimate interest in this confirmed risk; their potential involvement becomes more likely"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Mandatory_Disclosure_Constraint",
    "Watershed_Protection_Constraint",
    "Duty_To_Notify_Relevant_Authorities_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/8#Action_Conduct_Additional_Risk_Studies",
  "proeth:causesStateChange": "Risk status changes from \u0027preliminary concern\u0027 to \u0027confirmed qualitative hazard\u0027; Engineer L\u0027s discretion about whether to disclose is eliminated \u2014 disclosure is now mandatory; the ethical framework shifts from \u0027should I disclose?\u0027 to \u0027I must disclose and must ensure protective action follows\u0027",
  "proeth:createsObligation": [
    "Formally_Notify_Client_Of_Confirmed_Risk",
    "Recommend_Specific_Protective_Measures",
    "Document_Risk_Finding_Formally",
    "Prepare_To_Notify_Authorities_If_Client_Refuses_Action",
    "Condition_Continued_Work_On_Implementation_Of_Safeguards"
  ],
  "proeth:description": "Following the historic rainfall event and additional studies conducted by Engineer L, the risk of stormwater runoff into the drinking water watershed is qualitatively estimated as real. This outcome transforms the risk from a preliminary, unquantified concern into a professionally confirmed hazard.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After historic rainfall event; after additional risk studies conducted",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Runoff Risk Qualitatively Confirmed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#Event_Client_Refuses_Protective_Measures",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When a client refuses to implement safeguards for a confirmed public safety risk, what specific options does Engineer L have, and what are the ethical and professional consequences of each?",
    "Does Engineer L\u0027s prior silence \u2014 withholding concerns during preliminary design and suspension \u2014 affect their moral authority or legal standing to now refuse to continue work?",
    "At what point does Engineer L\u0027s obligation shift from informing the client to informing regulatory authorities, and what factors determine that threshold?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer L faces profound professional distress \u2014 the ethical path forward (refusing to continue, potentially notifying authorities) conflicts with contractual obligations, financial interests, and the client relationship; Client X likely feels pressured, frustrated, and possibly resentful; the community near the drinking water source faces the highest risk they have faced throughout the narrative, still without knowledge of the situation",
  "proeth-scenario:ethicalImplications": "Represents the sharpest possible conflict between contractual duty to client and paramount duty to public safety; tests whether financial constraints can ever justify proceeding with a project known to pose confirmed risk to a community\u0027s drinking water; raises questions about the adequacy of the engineer-client disclosure model when client refusal leaves the public unprotected; highlights that engineering ethics are not merely advisory \u2014 they impose binding constraints that override client instructions at the highest risk levels",
  "proeth-scenario:learningMoment": "Students should understand that a client\u0027s refusal to implement safeguards for a confirmed public safety risk does not give the engineer discretion to continue \u2014 it activates the highest tier of professional obligations, including potential authority notification and mandatory withdrawal. The engineer\u0027s paramount duty to public safety is not negotiable by client instruction or financial pressure.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client_X": "Faces a project that may be halted or significantly altered; financial constraints that seemed to justify refusing safeguards may produce far greater costs if contamination occurs",
    "community": "At greatest risk in the narrative; their drinking water source is threatened by a confirmed hazard, a client who refuses to mitigate it, and an engineer who has not yet escalated to authorities",
    "engineer_L": "Must choose between continuing work (ethically impermissible per BER precedent) and refusing/withdrawing (professionally correct but personally and financially costly); professional license and reputation are at stake regardless of choice",
    "engineering_profession": "The resolution of this impasse will either vindicate or undermine decades of BER precedent on public safety obligations",
    "regulatory_authorities": "Have the most legitimate and urgent interest in this outcome; their absence from the situation to this point is itself a product of Engineer L\u0027s prior silence"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Duty_To_Refuse_Unsafe_Work_Constraint",
    "Duty_To_Notify_Authorities_Constraint",
    "Cannot_Continue_Without_Safeguards_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/8#Action_Formally_Notify_Client_of_Risk",
  "proeth:causesStateChange": "The engineer-client relationship reaches a fundamental ethical breaking point; Engineer L can no longer treat this as a negotiable professional matter \u2014 the refusal to implement safeguards for a confirmed public safety risk activates the highest tier of engineering ethics obligations; continued work without safeguards becomes ethically impermissible",
  "proeth:createsObligation": [
    "Refuse_To_Continue_Work_Without_Safeguards",
    "Notify_Relevant_Regulatory_Authorities",
    "Document_Client_Refusal_Formally",
    "Withdraw_From_Project_If_Safeguards_Not_Implemented",
    "Protect_Public_Interest_Over_Client_Interest"
  ],
  "proeth:description": "Following Engineer L\u0027s formal notification of confirmed risk, Client X refuses to invest in additional protective measures, citing budget constraints, and insists on proceeding with the project as planned. This outcome creates an unresolved ethical impasse and activates Engineer L\u0027s most serious professional obligations.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer L formally notifies Client X of confirmed risk",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Client Refuses Protective Measures"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#CausalChain_828828e7",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer L identified emerging concerns about increased stormwater risk during preliminary design but withheld them, allowing the risk to develop unaddressed until confirmed by additional studies following a historic rainfall event",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer L internally identifies emerging stormwater risk concerns during preliminary design phase",
      "proeth:element": "Preliminary Risk Concerns Emerge (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer L chooses not to communicate these concerns to Client X, leaving the risk unaddressed",
      "proeth:element": "Withhold Preliminary Risk Concerns (Action 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Client X suspends the project for financial reasons; risk concerns remain undisclosed during this window",
      "proeth:element": "Project Suspension Occurs (Event 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "A historic rainfall event coincides with project resumption, materially elevating on-site stormwater risk",
      "proeth:element": "Historic Rainfall Event Occurs (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Additional studies confirm the stormwater runoff risk that Engineer L had initially suspected but withheld",
      "proeth:element": "Runoff Risk Qualitatively Confirmed (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Withhold Preliminary Risk Concerns (Action 1)",
  "proeth:counterfactual": "Had Engineer L disclosed preliminary concerns, Client X could have authorized early risk studies or mitigation, potentially preventing or reducing the severity of the confirmed risk",
  "proeth:effect": "Runoff Risk Qualitatively Confirmed (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer L\u0027s early identification of stormwater risk concerns",
    "Decision to withhold concerns from Client X during preliminary phase",
    "Absence of early protective or investigative measures",
    "Continued project progression without risk mitigation"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer L",
  "proeth:sufficientFactors": [
    "Combination of withheld preliminary concerns + project continuation + historic rainfall event = confirmed and elevated runoff risk"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#CausalChain_d453cdfa",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "When Client X communicated the project suspension, Engineer L chose not to disclose risk concerns, which directly enabled the subsequent resumption of work without any protective measures or informed client consent regarding the identified hazard",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer L holds undisclosed internal concerns about stormwater risk",
      "proeth:element": "Preliminary Risk Concerns Emerge (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client X suspends the project, creating a natural communication opportunity for Engineer L",
      "proeth:element": "Project Suspension Occurs (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer L fails to disclose risk concerns during suspension communication, perpetuating client ignorance",
      "proeth:element": "Omit Risk During Suspension (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Client X\u0027s finances improve and Engineer L accepts resumption without disclosing the known risk",
      "proeth:element": "Resume Work Without Disclosure (Action 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Delayed disclosure and lack of early client engagement contribute to Client X\u0027s resistance to protective investment",
      "proeth:element": "Client Refuses Protective Measures (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Omit Risk During Suspension (Action 2)",
  "proeth:counterfactual": "Had Engineer L disclosed risk concerns during the suspension period, Client X would have resumed work with knowledge of the hazard, potentially conditioning resumption on risk mitigation",
  "proeth:effect": "Resume Work Without Disclosure (Action 3)",
  "proeth:necessaryFactors": [
    "Engineer L\u0027s awareness of stormwater risk concerns prior to suspension",
    "Decision to omit risk disclosure during the suspension communication",
    "Client X\u0027s lack of knowledge about the risk at the time of resumption decision"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer L",
  "proeth:sufficientFactors": [
    "Omission during suspension + Client X\u0027s uninformed financial recovery decision = resumption of work without risk disclosure"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#CausalChain_8376a567",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A historic heavy rainfall event coincides with Client X\u0027s resumption of the project, causing elevated on-site conditions that, combined with Engineer L\u0027s additional studies, led to qualitative confirmation of the stormwater runoff risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Project resumes without prior risk disclosure, leaving site vulnerability unaddressed",
      "proeth:element": "Resume Work Without Disclosure (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "A historic rainfall event elevates on-site stormwater conditions, making risk observable",
      "proeth:element": "Historic Rainfall Event Occurs (Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer L initiates additional risk studies in response to the rainfall event and elevated site conditions",
      "proeth:element": "Conduct Additional Risk Studies (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Studies confirm the stormwater runoff risk that had been internally identified but withheld since preliminary design",
      "proeth:element": "Runoff Risk Qualitatively Confirmed (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer L formally notifies Client X of the confirmed risk, triggering the client\u0027s refusal to act",
      "proeth:element": "Formally Notify Client of Risk (Action 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Historic Rainfall Event Occurs (Event 3)",
  "proeth:counterfactual": "Without the historic rainfall event, on-site risk indicators may not have been sufficiently elevated to prompt additional studies or to confirm the risk at this stage; however, the underlying risk existed independently",
  "proeth:effect": "Runoff Risk Qualitatively Confirmed (Event 4)",
  "proeth:necessaryFactors": [
    "Occurrence of a historic heavy rainfall event at the critical project resumption juncture",
    "Engineer L\u0027s decision to conduct additional risk studies in response",
    "Pre-existing but unaddressed stormwater vulnerability on-site"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer L (shared with natural event)",
  "proeth:sufficientFactors": [
    "Historic rainfall event + additional risk studies + pre-existing site vulnerability = qualitative confirmation of elevated runoff risk"
  ],
  "proeth:withinAgentControl": false
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#CausalChain_3c2ae86d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After completing additional studies, Engineer L formally notified Client X of the identified stormwater risk, following which Client X refused to invest in additional protective measures",
  "proeth:causalSequence": [
    {
      "proeth:description": "Additional studies confirm the stormwater runoff risk following the historic rainfall event",
      "proeth:element": "Runoff Risk Qualitatively Confirmed (Event 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer L formally notifies Client X of the confirmed risk and recommends protective measures",
      "proeth:element": "Formally Notify Client of Risk (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Client X refuses to invest in protective measures, citing financial or other priorities",
      "proeth:element": "Client Refuses Protective Measures (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer L faces the decision of whether to continue work knowing protective measures have been refused",
      "proeth:element": "Continue Work Despite Refusal (Action 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Continuation of work without protective measures exposes third parties and the public to unmitigated stormwater runoff risk",
      "proeth:element": "Potential Public Safety Risk Materializes",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Formally Notify Client of Risk (Action 5)",
  "proeth:counterfactual": "Without formal notification, Client X would not have had the opportunity to refuse; however, the refusal is Client X\u0027s autonomous decision and would likely have occurred regardless of timing given financial priorities",
  "proeth:effect": "Client Refuses Protective Measures (Event 5)",
  "proeth:necessaryFactors": [
    "Formal notification of confirmed risk by Engineer L",
    "Client X\u0027s awareness of the financial cost of protective measures",
    "Prior pattern of Client X prioritizing financial constraints over risk mitigation",
    "Absence of regulatory compulsion to implement protective measures"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Client X (primary); Engineer L (contributing)",
  "proeth:sufficientFactors": [
    "Formal risk notification + Client X\u0027s financial disposition + lack of mandatory regulatory requirement = client refusal to implement protective measures"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/8#",
    "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/8#CausalChain_54c14a13",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following Client X\u0027s refusal to implement protective measures, Engineer L faces the decision of whether to continue the project, with continuation directly enabling an unmitigated stormwater risk to persist and potentially harm third parties or the public",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client X formally refuses to invest in protective measures after being notified of confirmed risk",
      "proeth:element": "Client Refuses Protective Measures (Event 5)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer L decides to continue project work despite knowing protective measures are absent",
      "proeth:element": "Continue Work Despite Refusal (Action 6)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Stormwater runoff risk remains unaddressed as project progresses without protective infrastructure",
      "proeth:element": "Unmitigated Risk Persists",
      "proeth:step": 3
    },
    {
      "proeth:description": "Downstream communities or adjacent properties face unmitigated stormwater runoff risk from the completed or ongoing project",
      "proeth:element": "Public and Third-Party Exposure",
      "proeth:step": 4
    },
    {
      "proeth:description": "Flooding, property damage, or safety incidents occur as a result of unmitigated stormwater mismanagement",
      "proeth:element": "Potential Public Safety Harm",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Continue Work Despite Refusal (Action 6)",
  "proeth:counterfactual": "Had Engineer L withdrawn from the project or reported the risk to regulatory authorities upon Client X\u0027s refusal, the unmitigated risk would have been flagged and potentially addressed through external compulsion, reducing the likelihood of harm",
  "proeth:effect": "Potential Public Safety Risk Materializes",
  "proeth:necessaryFactors": [
    "Engineer L\u0027s decision to continue work after Client X\u0027s refusal",
    "Confirmed and unmitigated stormwater runoff risk on-site",
    "Absence of protective measures due to client refusal",
    "Engineer L\u0027s professional capacity to withdraw services or escalate to authorities"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer L (primary at this stage); Client X (contributing)",
  "proeth:sufficientFactors": [
    "Continuation of work + unmitigated confirmed risk + no regulatory intervention = enabling conditions for public safety harm"
  ],
  "proeth:withinAgentControl": true
}