{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Accept_Limited_Scope_Engagement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Negotiate a broader initial scope that explicitly includes climate-risk and cumulative hydraulic impact screening before signing the contract.",
    "Decline the engagement on the grounds that the proposed scope is insufficient for a project in a tidal saltmarsh environment subject to sea level rise.",
    "Accept the engagement but document in writing at the outset that the scope may need to be expanded if hydraulic evaluation reveals foreseeable third-party impacts."
  ],
  "proeth-scenario:characterMotivation": "Engineer A seeks to secure professional work and serve a client within the boundaries of a standard consulting engagement, accepting the scope as defined by the client\u0027s immediate project goals and applicable regulatory minimums without yet having reason to anticipate the climate-risk complexity that will emerge during technical evaluation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Negotiating a broader scope upfront could have prevented the later conflict entirely by building flood-impact evaluation into the budget and timeline, though Client B might have rejected the engagement or selected a less cautious engineer.",
    "Declining the engagement would have protected Engineer A from the ethical dilemma but would not have protected the upstream homeowners, who would remain at risk under a different engineer potentially less attuned to climate impacts.",
    "Documenting scope limitations in writing at the outset would have created a contractual record supporting later scope-expansion requests and potentially strengthened Engineer A\u0027s position when proposing the specialized flood analysis."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how the framing of an engagement scope at the outset can constrain later ethical action, and prompts students to consider whether engineers have a duty to negotiate broader risk-evaluation provisions before accepting work in climate-sensitive contexts.",
  "proeth-scenario:ethicalTension": "Deference to client-defined scope and standard industry practice versus the engineer\u0027s independent professional obligation to anticipate and surface risks that fall outside a narrowly defined engagement but may affect public welfare.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "If the scope is too narrow from the start, the engineer may lack contractual authority or budget to investigate foreseeable harms; downstream homes and their occupants are placed at latent risk before any technical work begins.",
  "proeth:description": "Engineer A accepts the consulting engagement from Client B with a scope limited to design and local permitting per existing 25-year storm regulations, without initially negotiating broader climate-risk evaluation into the scope.",
  "proeth:foreseenUnintendedEffects": [
    "Scope may prove insufficient to address public safety risks that emerge during design",
    "Accepting scope bounded by outdated regulations may constrain later ability to raise climate concerns"
  ],
  "proeth:fulfillsObligation": [
    "Responding to client\u0027s legitimate business need",
    "Agreeing to perform work within professional competence"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of public health, safety, and welfare",
    "Professional competence and due diligence",
    "Truthfulness and objectivity in professional undertakings"
  ],
  "proeth:hasAgent": "Engineer A (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client-defined scope compliance vs. proactive public safety obligation",
    "proeth:resolutionReasoning": "Engineer A proceeded with the limited scope, which is a common professional practice when regulatory requirements define the baseline, but this created a latent ethical tension that surfaced once design-phase analysis revealed potential upstream flood impacts"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure consulting engagement and deliver compliant road and tidal crossing design within established regulatory framework",
  "proeth:requiresCapability": [
    "Civil/structural engineering design",
    "Hydraulic and hydrologic engineering",
    "Local permitting and regulatory navigation",
    "Tidal crossing and bridge design"
  ],
  "proeth:temporalMarker": "Pre-project scoping phase",
  "proeth:violatesObligation": [
    "Proactive duty to scope engagements broadly enough to protect public health, safety, and welfare",
    "Obligation to flag at intake that existing regulatory standards may be insufficient given climate change context"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Limited Scope Engagement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Form_Climate_Risk_Judgment",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Document the concern internally but take no further action, reasoning that the judgment is preliminary and outside the contracted scope.",
    "Consult informally with a peer or the specialized subconsultant to pressure-test the hydraulic concern before raising it with the client.",
    "Disclose the concern directly to regulatory agencies without first engaging the client, on the grounds that the public interest is paramount."
  ],
  "proeth-scenario:characterMotivation": "Engineer A applies recently acquired professional knowledge from a transportation agency conference to fulfill the core duty of competent technical practice, exercising independent judgment to identify a foreseeable harm to third parties that the client has not asked about and that existing regulations do not require the engineer to evaluate.",
  "proeth-scenario:consequencesIfAlternative": [
    "Internal documentation without disclosure would protect Engineer A from immediate conflict but would likely constitute a violation of the ethical duty to disclose information relevant to public safety, and would provide little practical protection if harms later materialized.",
    "Peer consultation before client engagement is a professionally prudent intermediate step that could strengthen the technical basis for the concern and make the subsequent client conversation more credible, though it adds time and cost.",
    "Bypassing the client to go directly to regulators would likely violate professional norms of client relationship management and could expose Engineer A to contract liability, even though the underlying ethical impulse to protect the public is sound."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical obligations can arise from technical findings generated in the ordinary course of professional work, and that an engineer\u0027s duty to the public is triggered by knowledge, not merely by regulatory mandate or client instruction.",
  "proeth-scenario:ethicalTension": "Loyalty to the client\u0027s defined project goals and cost expectations versus the engineer\u0027s paramount obligation under codes of ethics to hold public health, safety, and welfare above private interests, even when no regulation compels the inquiry.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The judgment, if correct, means approximately twenty households face accelerated uninhabitability; if suppressed or ignored, Engineer A becomes complicit in a foreseeable harm. If the judgment is acted upon, it will cost the client time and money and may jeopardize the engagement.",
  "proeth:description": "Engineer A exercises independent professional judgment, drawing on hydraulic evaluation procedures presented at a recent transportation agency conference, to conclude that the proposed project may cause upstream homes to become uninhabitable a decade or more earlier than would otherwise be the case.",
  "proeth:foreseenUnintendedEffects": [
    "Finding creates obligation to act beyond minimum regulatory requirements",
    "Conclusion may conflict with client\u0027s interest in proceeding efficiently and cost-effectively",
    "Raises the prospect of difficult public hearing scrutiny"
  ],
  "proeth:fulfillsObligation": [
    "Duty to apply current and relevant technical knowledge beyond minimum code requirements",
    "Obligation to proactively identify risks to public health, safety, and welfare",
    "Professional competence in recognizing when specialized evaluation may be needed"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of public health, safety, and welfare",
    "Professional competence and continuing education",
    "Objectivity and truthfulness in technical assessment",
    "Obligation to consider reasonably likely and significant future impacts"
  ],
  "proeth:hasAgent": "Engineer A (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Regulatory compliance sufficiency vs. professional obligation to address known gaps in outdated standards",
    "proeth:resolutionReasoning": "Engineer A correctly exercised professional judgment to flag the risk, consistent with the ethical principle that public safety obligations are not bounded by what regulations require"
  },
  "proeth:hasMentalState": "deliberate and reflective",
  "proeth:intendedOutcome": "Accurately characterize the hydraulic and climate risk implications of the tidal crossing upgrade to inform project decision-making",
  "proeth:requiresCapability": [
    "Hydrology and hydraulic engineering",
    "Coastal and tidal dynamics understanding",
    "Climate change impact assessment at a generalist level",
    "Ability to recognize when specialized subconsultant expertise is needed"
  ],
  "proeth:temporalMarker": "During design phase, following review of transportation agency conference materials",
  "proeth:withinCompetence": true,
  "rdfs:label": "Form Climate Risk Judgment"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Propose_Specialized_Flood_Analysis",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Propose a lower-cost, less rigorous screening-level assessment as a compromise between full analysis and no analysis.",
    "Recommend that the client consult legal counsel about liability exposure before deciding whether to commission the analysis.",
    "Propose that the analysis be scoped and budgeted but deferred pending initial regulatory agency feedback, allowing regulators to signal whether they will require it."
  ],
  "proeth-scenario:characterMotivation": "Having identified a foreseeable harm through independent technical judgment, Engineer A fulfills the professional obligation to recommend a course of action that would quantify and document the risk, proposing a concrete and technically credible remedy rather than simply flagging a vague concern.",
  "proeth-scenario:consequencesIfAlternative": [
    "A screening-level assessment might satisfy Engineer A\u0027s immediate disclosure obligation at lower cost but could prove inadequate if it fails to capture the full magnitude of impacts, potentially creating a false sense of security for both the client and regulators.",
    "Recommending legal consultation reframes the issue as a liability risk rather than solely an ethical one, which may be more persuasive to a cost-focused client, though it risks reducing a public-safety obligation to a business calculation.",
    "Deferring the analysis pending regulatory feedback is pragmatically reasonable but shifts the burden of requiring protective evaluation onto regulators, who may lack the technical capacity or information to ask the right questions."
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that identifying an ethical problem is insufficient; the engineer must also propose a constructive, actionable path forward, and that the cost or inconvenience of a protective measure does not diminish the obligation to recommend it.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to recommend technically sound and thorough analysis conflicts with the client\u0027s interest in cost control and schedule efficiency, and with the implicit pressure not to expand project scope in ways that could trigger regulatory scrutiny or delay.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If the analysis is conducted, the project may be delayed, redesigned, or cancelled, and Client B may lose confidence in Engineer A. If it is not conducted, approximately twenty households may face accelerated flood risk without their knowledge or any opportunity to seek legal or protective recourse.",
  "proeth:description": "Engineer A proactively proposes commissioning a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to quantify the extent to which sea level rise and the increased hydraulic capacity of the tidal crossing will result in flood damage to approximately twenty upstream homes during future high tides and storm surges.",
  "proeth:foreseenUnintendedEffects": [
    "Significant additional cost to Client B",
    "Potential project delay",
    "Analysis results could jeopardize project approval or require costly design modifications",
    "Client B may resist or refuse the proposal"
  ],
  "proeth:fulfillsObligation": [
    "Duty to hold paramount public health, safety, and welfare of upstream homeowners",
    "Obligation to be objective and truthful and include all relevant and pertinent information in professional reports",
    "Duty to disclose potential public safety risks to regulatory agencies and the public",
    "Obligation to recommend specialized expertise when a problem exceeds generalist analysis"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of public health, safety, and welfare",
    "Objectivity and completeness in professional reporting",
    "Duty to advise client of actions necessary to protect public safety",
    "Transparency with regulatory authorities"
  ],
  "proeth:hasAgent": "Engineer A (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client cost minimization vs. public safety due diligence",
    "proeth:resolutionReasoning": "Engineer A correctly identified that the potential harm to upstream homeowners is sufficiently likely and significant to warrant detailed evaluation, consistent with the ethical obligation to go beyond minimum regulatory requirements when public safety is at stake"
  },
  "proeth:hasMentalState": "deliberate and proactive",
  "proeth:intendedOutcome": "Obtain rigorous technical data to accurately characterize flood risk to upstream homeowners, support informed regulatory review, and prepare for anticipated scrutiny at public hearings",
  "proeth:requiresCapability": [
    "Judgment to recognize limits of generalist hydraulic analysis",
    "Ability to scope and procure specialized subconsultant services",
    "Understanding of coastal and tidal flood modeling requirements",
    "Communication of technical risk to non-technical client"
  ],
  "proeth:temporalMarker": "During design phase, after forming climate risk judgment and in anticipation of public hearings",
  "proeth:withinCompetence": true,
  "rdfs:label": "Propose Specialized Flood Analysis"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Client_Directs_Analysis_Deferral",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engineer A complies silently with the client directive, proceeding without the analysis and without further disclosure.",
    "Engineer A complies with the directive but inserts a written qualification in project documents noting that a flood impact analysis was recommended but not authorized by the client.",
    "Engineer A immediately withdraws from the project upon receiving the directive, without attempting further engagement."
  ],
  "proeth-scenario:characterMotivation": "Client B seeks to control project costs, maintain schedule, and avoid regulatory complications, operating within a rational business logic that treats regulatory compliance as the ceiling of obligation rather than a floor, and that discounts probabilistic future harms to third parties relative to certain present costs.",
  "proeth-scenario:consequencesIfAlternative": [
    "Silent compliance would likely constitute a violation of the engineer\u0027s ethical duty to disclose information relevant to public safety and could expose Engineer A to professional disciplinary action and civil liability if harms materialize.",
    "Written qualification in project documents is a partial protective measure that creates a record but may be insufficient if the qualification is buried in technical appendices and never reaches regulators, the public, or the affected homeowners.",
    "Immediate withdrawal without further engagement would protect Engineer A\u0027s ethical standing but would forgo the opportunity to persuade the client, potentially leaving the project to proceed under a less conscientious engineer with no flood concern on record."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the classic principal-agent tension in engineering ethics: the client pays and directs, but the engineer\u0027s license and ethical code impose duties that cannot be waived by client instruction, making this directive a pivotal test of professional integrity.",
  "proeth-scenario:ethicalTension": "The client\u0027s legitimate authority to direct the scope and cost of an engagement conflicts with the engineer\u0027s non-delegable ethical duty to protect public welfare, creating a direct clash between contractual hierarchy and professional independence.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A now faces a binary choice between compliance, which risks public harm and ethical violation, and resistance, which risks the client relationship, contract termination, and potential professional isolation. The upstream homeowners remain unaware of the risk being debated on their behalf.",
  "proeth:description": "Client B directs Engineer A to proceed with the project without conducting the costly specialized flood analysis unless and until regulatory authorities specifically request it, prioritizing cost control and regulatory minimums over proactive risk quantification.",
  "proeth:foreseenUnintendedEffects": [
    "Potential flood risk to twenty upstream homeowners remains unquantified and undisclosed",
    "Creates ethical conflict for Engineer A",
    "May expose Client B to future liability if flood damage occurs",
    "Relevant information may be withheld from regulatory agencies and the public"
  ],
  "proeth:fulfillsObligation": [
    "Exercising client authority over project scope and budget within contractual relationship"
  ],
  "proeth:guidedByPrinciple": [
    "Client\u0027s legitimate authority over business decisions",
    "Developer\u0027s responsibility to avoid harm to affected communities"
  ],
  "proeth:hasAgent": "Client B (Developer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Developer financial interest vs. third-party public safety",
    "proeth:resolutionReasoning": "Client B resolved in favor of cost minimization and regulatory minimums, deferring analysis unless compelled by regulators, which creates an ethical obligation for Engineer A to resist this directive"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Avoid the cost and potential project complications of the specialized analysis; proceed to permitting on the basis of existing regulatory requirements only",
  "proeth:requiresCapability": [
    "Project management and budget authority",
    "Understanding of regulatory requirements"
  ],
  "proeth:temporalMarker": "Client directive moment, during design phase after Engineer A\u0027s proposal",
  "proeth:violatesObligation": [
    "Duty not to direct licensed professionals to withhold material public safety information",
    "Responsibility to avoid harm to third parties (upstream homeowners) through project decisions"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Client Directs Analysis Deferral"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Engage_Client_on_Risk_Disclosure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engage the client in writing only, submitting a formal memorandum documenting the concern and the recommendation, without seeking a face-to-face or interactive dialogue.",
    "Involve a senior partner or principal from Engineer A\u0027s firm in the client engagement conversation to add organizational weight to the recommendation.",
    "Engage the client\u0027s legal counsel directly, bypassing Client B, to ensure the liability dimensions of the decision are understood at the appropriate level."
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognizes that the client\u0027s directive, while reflecting a legitimate business preference, cannot override the paramount ethical obligation to protect public welfare, and seeks to fulfill both the duty of candid professional counsel to the client and the duty of public protection by making the strongest possible case for the analysis before escalating.",
  "proeth-scenario:consequencesIfAlternative": [
    "Written-only engagement creates a documentary record but sacrifices the persuasive dynamics of dialogue and may allow the client to dismiss the concern without substantive consideration, reducing the chance of a positive outcome.",
    "Involving a senior firm representative could strengthen the recommendation\u0027s credibility and signal organizational seriousness, but may also escalate the conflict prematurely and damage the client relationship before all interpersonal options are exhausted.",
    "Engaging the client\u0027s legal counsel directly is unconventional and could be perceived as adversarial or a breach of professional relationship norms, though it might be appropriate if Engineer A has reason to believe Client B is not sharing the concern with decision-makers who bear legal exposure."
  ],
  "proeth-scenario:decisionSignificance": "Models the ethical obligation of substantive engagement before escalation or withdrawal, teaching students that engineers must make a genuine and documented effort to persuade clients through professional reasoning, including framing ethical obligations in terms of legal risk and reputational consequences that are meaningful to a business client.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty of loyalty and candor to the client, which includes providing honest advice even when unwelcome, is in tension with the risk of damaging the professional relationship, losing the engagement, and being replaced by an engineer who will not raise the concern at all.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "This conversation is the last realistic opportunity to resolve the conflict within the client relationship. If it succeeds, the public is protected and the engagement continues. If it fails, Engineer A must choose between continued participation under ethically compromised conditions and withdrawal with its professional and financial consequences.",
  "proeth:description": "Engineer A should engage Client B in substantive discussions about the necessity of the detailed flood evaluation, the obligation to disclose potential impacts to regulatory agencies and the public, and the potential legal and reputational risk to Client B of proceeding without the analysis.",
  "proeth:foreseenUnintendedEffects": [
    "Client B may remain unconvinced and maintain the directive",
    "Engagement may strain or damage the professional relationship",
    "Failure to persuade will require escalation to disclosure or withdrawal"
  ],
  "proeth:fulfillsObligation": [
    "Duty to advise client of actions necessary to protect public health, safety, and welfare",
    "Obligation to be objective and truthful with client about risks and professional obligations",
    "Duty to attempt to resolve ethical conflicts through client engagement before escalating"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of public health, safety, and welfare",
    "Objectivity and truthfulness in professional communications",
    "Duty to inform client of consequences of decisions affecting public safety",
    "Obligation to act as a faithful agent while not compromising public safety"
  ],
  "proeth:hasAgent": "Engineer A (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client relationship preservation vs. public safety advocacy",
    "proeth:resolutionReasoning": "The discussion concludes that Engineer A must engage Client B as a first step, consistent with BER Case 18-9 precedent that engineers should continue attempting to convince owners of public safety risks before withdrawing"
  },
  "proeth:hasMentalState": "deliberate and obligatory",
  "proeth:intendedOutcome": "Persuade Client B to authorize the specialized analysis or agree to disclose the potential flood risk in regulatory submissions; protect public safety while preserving the professional relationship if possible",
  "proeth:requiresCapability": [
    "Professional communication and negotiation",
    "Ability to articulate technical risk in terms of client business risk",
    "Knowledge of NSPE ethical obligations and BER precedents",
    "Understanding of regulatory disclosure requirements"
  ],
  "proeth:temporalMarker": "Ethical crossroads, immediately following Client B\u0027s directive to defer analysis",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engage Client on Risk Disclosure"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Propose_Regulatory_Disclosure_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Propose that the concern be disclosed informally to the lead regulatory contact rather than through a formal public report, preserving some client control over the process.",
    "Propose that Engineer A personally notify the affected upstream homeowners directly, outside the regulatory process, as an alternative to or supplement to regulatory disclosure.",
    "Accept the client\u0027s position and proceed without any formal disclosure, reasoning that the regulatory process itself will surface the concern through standard review."
  ],
  "proeth-scenario:characterMotivation": "Having attempted direct client engagement, Engineer A seeks a compromise path that fulfills the ethical obligation to disclose potential impacts to regulatory agencies and the public without requiring the client to fund the full specialized analysis, proposing a formal engineering report as a mechanism for transparency that places the decision about further investigation in the hands of regulators and the public.",
  "proeth-scenario:consequencesIfAlternative": [
    "Informal regulatory disclosure without a formal report reduces transparency and public access to the concern, and may allow the issue to be resolved in private conversations that do not create an accessible record, undermining the protective purpose of disclosure.",
    "Direct notification of affected homeowners is ethically compelling as it reaches the people most directly at risk, but may exceed the scope of Engineer A\u0027s professional role, create legal complications, and could be perceived as an attempt to mobilize opposition to the client\u0027s project.",
    "Relying on standard regulatory review to surface the concern is unlikely to succeed because regulators typically lack the specific hydraulic modeling insight that Engineer A has developed, and this approach would effectively transfer the ethical burden to a process not equipped to bear it."
  ],
  "proeth-scenario:decisionSignificance": "Introduces students to the concept of regulatory disclosure as an ethical tool, and raises questions about what level of disclosure is sufficient to satisfy the duty to protect the public when full analysis is refused, including whether disclosing an unquantified concern is more or less protective than remaining silent.",
  "proeth-scenario:ethicalTension": "The obligation to proactively disclose known risks to public welfare conflicts with the client\u0027s interest in controlling the information environment around the permitting process, and with the engineer\u0027s uncertainty about whether a formal report without full quantification is sufficient to discharge the duty of disclosure.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If the client accepts this proposal, the concern enters the public record and regulators and the public can respond, though without quantification the concern may not receive adequate weight. If the client refuses even this minimal disclosure, Engineer A has exhausted all compromise options and must withdraw.",
  "proeth:description": "If Client B remains unconvinced after initial engagement, Engineer A should propose providing the potential flood concern in a formal engineering report submitted to regulatory agencies and made available to the public for consideration during the permitting process.",
  "proeth:foreseenUnintendedEffects": [
    "Regulatory agencies may require the full analysis as a result",
    "Project may face heightened scrutiny or denial at public hearings",
    "Client B may view this as a breach of loyal agency",
    "Disclosure without full analysis may be incomplete but is better than no disclosure"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to be objective and truthful in professional reports and include all relevant and pertinent information",
    "Duty to disclose potential public safety risks to regulatory authorities",
    "Obligation to protect public health, safety, and welfare through transparent disclosure",
    "Duty to serve the public interest in regulatory proceedings"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of public health, safety, and welfare",
    "Objectivity and completeness in professional reporting",
    "Transparency with regulatory authorities and the public",
    "Precedent from BER Case 07.6 on disclosure of relevant information in regulatory submissions"
  ],
  "proeth:hasAgent": "Engineer A (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client confidentiality and agency vs. regulatory transparency and public safety",
    "proeth:resolutionReasoning": "The discussion determines that disclosure of the concern to regulatory agencies is ethically required even without the full analysis, as regulatory agencies and the public have a right to this information and can themselves require further analysis"
  },
  "proeth:hasMentalState": "deliberate and ethically compelled",
  "proeth:intendedOutcome": "Ensure that regulatory agencies and the public have access to material information about potential flood risks to upstream homeowners, fulfilling disclosure obligations even if Client B does not authorize the full specialized analysis",
  "proeth:requiresCapability": [
    "Technical report writing",
    "Regulatory submission preparation",
    "Ability to characterize risk qualitatively when quantitative analysis is not yet available",
    "Knowledge of regulatory disclosure standards"
  ],
  "proeth:temporalMarker": "Potential future action, if Client B remains unconvinced after initial engagement",
  "proeth:violatesObligation": [
    "Potentially the duty of faithful agency to Client B if client explicitly objects to disclosure"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Propose Regulatory Disclosure Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Action_Withdraw_from_Project",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Remain on the project but file a confidential complaint with the state engineering licensing board or a relevant regulatory agency, attempting to trigger external intervention without formally withdrawing.",
    "Remain on the project and continue to document objections in writing, creating a record that might later be used to demonstrate that Engineer A acted in good faith, while hoping that the regulatory process will independently require the analysis.",
    "Withdraw from the project and, consistent with applicable professional and legal obligations, proactively notify the relevant regulatory agency of the reason for withdrawal so that the concern is not lost when Engineer A exits the project."
  ],
  "proeth-scenario:characterMotivation": "Having exhausted all available options for protecting the public within the client relationship, Engineer A concludes that continued participation in the project would make the engineer complicit in a foreseeable harm to approximately twenty households, and that the paramount ethical obligation to hold public welfare above client and personal interests requires withdrawal regardless of the professional and financial consequences.",
  "proeth-scenario:consequencesIfAlternative": [
    "Filing a confidential complaint while remaining on the project is legally and ethically complex, may not be permissible under applicable rules, and places Engineer A in the contradictory position of simultaneously serving and reporting on the client, likely undermining both the complaint and the professional relationship.",
    "Remaining on the project with documented objections provides a paper trail but does not actually protect the public, as the harm proceeds regardless of Engineer A\u0027s internal reservations, and may not constitute a sufficient defense if professional discipline or civil liability follows.",
    "Withdrawing and notifying the regulatory agency of the reason is arguably the most complete discharge of Engineer A\u0027s ethical duty, as it both removes the engineer from complicity and ensures the concern survives the departure, though it carries the highest risk of legal and reputational conflict with Client B."
  ],
  "proeth-scenario:decisionSignificance": "Presents withdrawal as not merely a last resort but as the ethically required action when all other avenues are exhausted, teaching students that professional integrity sometimes demands accepting significant personal cost, and that the engineering license carries obligations that supersede contractual relationships.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to protect public health, safety, and welfare in the most direct way available conflicts with duties of loyalty to the client, obligations to subconsultants and other project stakeholders who depend on the engagement, and the engineer\u0027s own professional and financial interests in retaining the work.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Engineer A risks loss of the contract, potential reputational damage with Client B and associated networks, and possible legal exposure for breach of contract. However, remaining on the project risks professional disciplinary action, civil liability if harms materialize, and violation of the foundational ethical obligation that justifies the existence of professional licensure.",
  "proeth:description": "If Client B refuses both further substantive engagement on the flood risk and agreement to disclose the potential concern in regulatory submissions, Engineer A should withdraw from the project rather than proceed in a manner that violates the paramount ethical obligation to protect public health, safety, and welfare.",
  "proeth:foreseenUnintendedEffects": [
    "Loss of consulting revenue and potential reputational harm with Client B",
    "Project may proceed with a different engineer who does not raise these concerns",
    "Withdrawal does not itself protect upstream homeowners if another engineer proceeds without disclosure",
    "Engineer A may have a residual obligation to notify regulatory authorities even after withdrawal"
  ],
  "proeth:fulfillsObligation": [
    "Paramount duty to hold public health, safety, and welfare above client and employer interests",
    "Obligation not to be complicit in withholding material public safety information from regulatory agencies",
    "Duty to refuse to participate in projects that violate ethical obligations"
  ],
  "proeth:guidedByPrinciple": [
    "Primacy of public health, safety, and welfare as the paramount obligation",
    "Integrity and refusal to participate in ethically compromised projects",
    "Precedent from BER Case 18-9 that withdrawal is appropriate when owner refuses necessary public safety measures"
  ],
  "proeth:hasAgent": "Engineer A (Consulting Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional and financial interest in completing engagement vs. ethical obligation to refuse complicity in public safety risk",
    "proeth:resolutionReasoning": "The discussion determines that withdrawal is the only ethically permissible course when Client B refuses both engagement and disclosure, as proceeding would make Engineer A complicit in a violation of the paramount obligation to public health, safety, and welfare"
  },
  "proeth:hasMentalState": "deliberate and ethically compelled",
  "proeth:intendedOutcome": "Avoid professional complicity in a project that poses unquantified and undisclosed flood risks to twenty upstream homeowners; uphold the paramount ethical obligation to public health, safety, and welfare even at the cost of the client relationship and project revenue",
  "proeth:requiresCapability": [
    "Professional judgment on ethical limits of client compliance",
    "Knowledge of contractual withdrawal procedures",
    "Understanding of residual obligations upon withdrawal",
    "Documentation of the basis for withdrawal decision"
  ],
  "proeth:temporalMarker": "Final decision point, if Client B refuses both prior courses of action",
  "proeth:violatesObligation": [
    "Contractual obligation to complete the engagement (mitigated by ethical justification for withdrawal)",
    "Duty of faithful agency to Client B (superseded by public safety obligation)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Withdraw from Project"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Event_Analysis_Deferral_Imposed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When a client directs an engineer to skip analysis that the engineer believes is necessary to protect third parties, what options does the engineer have and what are the consequences of each?",
    "Does the fact that regulators have not required the analysis reduce Engineer A\u0027s ethical obligation to pursue it?",
    "How should engineers document situations where clients override their professional recommendations, and why does documentation matter?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences frustration, moral conflict, and professional anxiety; the directive puts Engineer A in direct tension between loyalty to the client and duty to the public; Client B may feel relief at avoiding cost but is unaware of the ethical exposure being created; upstream homeowners remain oblivious to both the risk and the decision being made about their futures",
  "proeth-scenario:ethicalImplications": "Illustrates the structural vulnerability of engineering ethics when client financial interests conflict with public safety; reveals how cost-benefit reasoning by clients can externalize risks onto uninvolved third parties; raises questions about the adequacy of regulatory systems that place ethical burden entirely on the engineer rather than mandating analysis",
  "proeth-scenario:learningMoment": "Client directives do not override professional ethical obligations; when a client instructs an engineer to suppress or defer analysis of known hazards, the engineer faces a defining professional moment that cannot be resolved through passive compliance.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client_b": "Short-term cost savings achieved, but legal, regulatory, and reputational exposure increases; decision may constitute negligence if harm materializes",
    "engineer_a": "Placed in an ethically untenable position; continued participation without action risks complicity in harm; professional license and reputation at risk",
    "engineering_profession": "Professional norms are under pressure; the outcome of this situation will either reinforce or undermine public trust in engineers as public protectors",
    "regulatory_agencies": "Deprived of information that may be material to their permitting decisions",
    "upstream_homeowners": "Their risk remains unquantified and undisclosed; they lose the opportunity for informed decision-making about their properties"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Prohibition_On_Concealing_Known_Hazards",
    "Duty_To_Engage_Client_On_Ethics"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/88#Action_Client_Directs_Analysis_Deferral",
  "proeth:causesStateChange": "Project proceeds without the flood impact analysis; known risk to upstream homeowners remains unquantified and undisclosed; Engineer A\u0027s continued participation now carries moral weight; the ethical threshold for withdrawal begins to approach",
  "proeth:createsObligation": [
    "Engage_Client_On_Risk_Disclosure",
    "Assess_Whether_Continued_Participation_Is_Ethical",
    "Consider_Regulatory_Disclosure_Independently",
    "Document_Client_Directive_And_Engineer_Response"
  ],
  "proeth:description": "Following Client B\u0027s directive to skip the specialized flood analysis unless regulators require it, the detailed assessment of flood impacts on upstream homes is formally deferred, leaving the risk undocumented and unmitigated within the project scope.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following Engineer A\u0027s proposal for specialized flood analysis and Client B\u0027s direction",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Analysis Deferral Imposed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Event_Hydraulic_Evaluation_Completed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what point does an engineer\u0027s professional obligation to act on findings begin \u2014 when findings are suspected, or only when formally confirmed?",
    "Does completing a hydraulic evaluation create a duty to fully investigate all implications, even those outside the original project scope?",
    "How should engineers handle situations where their technical findings may complicate or derail a client\u0027s project plans?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences professional satisfaction at completing the technical work, but this is immediately complicated by the troubling implications of the findings; a shift from routine professional confidence to moral unease begins here",
  "proeth-scenario:ethicalImplications": "Reveals the tension between technical work as a neutral service and technical work as a morally loaded activity; demonstrates that knowledge itself creates responsibility; raises questions about the scope of duty of care in engineering practice",
  "proeth-scenario:learningMoment": "Technical engineering work is never purely neutral \u2014 completing an analysis creates knowledge that carries ethical weight and activates professional obligations, regardless of what the client wants to hear.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_b": "Unaware of impending difficult conversation; project timeline may be at risk",
    "engineer_a": "Now bears knowledge of potential harm; professional and ethical obligations are activated",
    "public": "Indirectly affected as the knowledge now exists that could protect or fail them",
    "regulatory_agencies": "Not yet aware; their oversight role will soon become relevant",
    "upstream_homeowners": "Unaware their properties may be affected; their vulnerability is now technically documented"
  },
  "proeth:activatesConstraint": [
    "Competent_Engineering_Practice",
    "Technical_Accuracy_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/88#Action_Accept_Limited_Scope_Engagement",
  "proeth:causesStateChange": "Technical knowledge state changes from unknown to known; Engineer A now possesses data sufficient to identify potential upstream flood risk; obligation to act on findings is triggered",
  "proeth:createsObligation": [
    "Report_Findings_To_Client",
    "Assess_Downstream_Effects",
    "Document_Technical_Conclusions"
  ],
  "proeth:description": "Engineer A completes a hydraulic evaluation of the proposed culvert-to-bridge replacement project, producing technical findings about water flow and capacity changes in the tidal saltmarsh system.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Early project phase, following engagement and initial design work",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Hydraulic Evaluation Completed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Event_Flood_Risk_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When an engineer discovers that a project will harm third parties who are not party to the contract, what obligations arise and to whom are they owed?",
    "How should an engineer weigh a harm that is probabilistic and decades away against immediate client and project interests?",
    "Is there a meaningful ethical difference between a project that directly causes harm and one that accelerates an existing environmental harm?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences significant moral distress upon recognizing the human consequences of the findings; the discovery transforms a technical project into a potential harm to real families; Client B is not yet aware and faces no emotional impact at this moment; upstream homeowners remain entirely unaware of the risk to their homes and lives",
  "proeth-scenario:ethicalImplications": "Exposes the fundamental tension in engineering between serving the client and protecting the public; raises questions about intergenerational equity and climate justice; highlights the engineer\u0027s unique position as the only actor in the system who possesses both the technical knowledge and the professional standing to act on this risk",
  "proeth-scenario:learningMoment": "This event illustrates that engineering decisions have distributional consequences \u2014 benefits accrue to some (the developer, facility users) while harms fall on others (upstream homeowners) who have no voice in the decision. Engineers serve as a critical check on this imbalance.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client_b": "Project viability and cost projections may be threatened; faces potential regulatory scrutiny",
    "engineer_a": "Faces acute ethical dilemma; professional obligations now conflict with client\u0027s likely preferences; bears the burden of knowledge",
    "public_interest": "The broader community interest in honest infrastructure assessment is at stake",
    "regulatory_agencies": "Have a legitimate interest in this information that has not yet been triggered",
    "upstream_homeowners": "Approximately twenty households face potential acceleration of property loss and displacement; their homes may become uninhabitable years earlier than expected; they have no knowledge of this risk"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Duty_To_Disclose_Known_Hazards",
    "Protect_Third_Party_Interests"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/88#Action_Form_Climate_Risk_Judgment",
  "proeth:causesStateChange": "Project status changes from routine infrastructure upgrade to potentially harmful development; twenty upstream households are now identified as at-risk third parties; Engineer A\u0027s ethical obligations expand beyond client service to encompass public protection",
  "proeth:createsObligation": [
    "Inform_Client_Of_Risk_Findings",
    "Propose_Further_Analysis",
    "Consider_Regulatory_Disclosure",
    "Document_Risk_Assessment",
    "Protect_Uninvolved_Third_Parties"
  ],
  "proeth:description": "The hydraulic evaluation reveals that replacing the culvert with a bridge will increase hydraulic capacity in ways that, combined with sea level rise, may render approximately twenty upstream homes uninhabitable a decade or more earlier than would otherwise occur.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon completion of hydraulic evaluation, early-to-mid project phase",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Flood Risk Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Event_Third_Party_Risk_Unmitigated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is there a morally meaningful difference between causing harm through action and allowing harm to continue through inaction when you have the knowledge and power to intervene?",
    "How does the concept of informed consent apply to homeowners who are making major life decisions without access to risk information that an engineer possesses?",
    "At what point does an engineer\u0027s failure to disclose a known risk become professional misconduct rather than merely a judgment call?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "This event is largely invisible to those it affects most \u2014 upstream homeowners feel nothing yet because they do not know; Engineer A bears the psychological weight of knowing harm may be occurring through inaction; the asymmetry of knowledge creates a profound moral burden",
  "proeth-scenario:ethicalImplications": "Reveals the ethics of omission and information asymmetry; demonstrates how professional knowledge creates power imbalances with ethical consequences; raises questions about who bears the cost of risk disclosure and who bears the cost of risk concealment",
  "proeth-scenario:learningMoment": "Harm is not only caused by direct action \u2014 sustained inaction in the face of known risk is itself a form of ethical failure. Engineers must understand that \u0027doing nothing\u0027 is a choice with consequences.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_b": "Legal and regulatory liability accumulates; future harm to homeowners may be traceable to this decision point",
    "engineer_a": "Bears ongoing moral responsibility for a harm that continues to develop; professional culpability increases with inaction",
    "future_courts_or_investigators": "This moment may become a critical point of accountability if harm materializes",
    "regulatory_agencies": "Unable to fulfill their protective function because they lack the information to trigger review",
    "upstream_homeowners": "Make life decisions (renovations, sales, mortgages, retirement planning) without material information that an engineer possesses; their autonomy is compromised by information asymmetry"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Duty_To_Protect_Uninvolved_Third_Parties",
    "Prohibition_Against_Deceptive_Omission"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/88#Action_Client_Directs_Analysis_Deferral",
  "proeth:causesStateChange": "A class of uninvolved third parties (upstream homeowners) are exposed to an unmitigated, undisclosed, and unquantified risk as a direct consequence of project decisions; the moral and legal exposure of all parties increases with each day the situation continues unaddressed",
  "proeth:createsObligation": [
    "Escalate_Disclosure_Efforts",
    "Evaluate_Project_Withdrawal",
    "Notify_Regulatory_Agencies_Independently_If_Necessary"
  ],
  "proeth:description": "As a consequence of the deferred analysis and the absence of disclosure, approximately twenty upstream homeowners remain unaware of the accelerated flood risk to their properties, with no mitigation measures, warnings, or regulatory review in place.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Ongoing state following analysis deferral, persisting until disclosure or project termination",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Third Party Risk Unmitigated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Event_Engineer_Ethical_Obligation_Crystallized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How should an engineer respond when professional ethics obligations directly conflict with a client\u0027s explicit instructions and the engineer\u0027s own financial interests?",
    "Is the three-step sequence (engage, disclose, withdraw) the right framework, or are there situations where an engineer should move directly to disclosure or withdrawal?",
    "What does it mean for an engineering obligation to be \u0027mandatory\u0027 \u2014 who enforces it, and what are the consequences of non-compliance?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "This event may bring Engineer A a kind of moral clarity \u2014 the ambiguity of \u0027what should I do?\u0027 resolves into \u0027what I must do\u0027; this clarity may be accompanied by anxiety about professional and financial consequences; it may also produce a sense of professional integrity and purpose",
  "proeth-scenario:ethicalImplications": "Demonstrates that professional licensure is not merely a credential but a social contract with enforceable obligations; reveals the relationship between professional codes and specific situational duties; raises questions about the adequacy of professional self-regulation when client pressure conflicts with public protection",
  "proeth-scenario:learningMoment": "Professional ethics are not merely aspirational guidelines \u2014 they create specific, binding obligations that can override client instructions and financial self-interest. Understanding when and how obligations crystallize is a core professional competency.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client_b": "Will face a direct professional confrontation that may disrupt the project and the relationship",
    "engineer_a": "Faces a defined path with significant personal and professional risk; must choose between ethical compliance and client accommodation",
    "engineering_profession": "The case becomes a potential precedent for how engineers handle climate-related third-party risks",
    "upstream_homeowners": "Their protection now depends entirely on Engineer A\u0027s willingness to act on crystallized obligations"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Mandatory_Client_Engagement_Constraint",
    "Regulatory_Disclosure_Obligation",
    "Withdrawal_If_Refused_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/88#Action_Client_Directs_Analysis_Deferral",
  "proeth:causesStateChange": "Engineer A\u0027s permissible options narrow; passive compliance is no longer ethically available; the three-step obligation sequence (engage, disclose, withdraw) becomes the operative professional standard",
  "proeth:createsObligation": [
    "Engage_Client_On_Risk_Disclosure",
    "Propose_Regulatory_Disclosure_Report",
    "Withdraw_From_Project_If_Client_Refuses"
  ],
  "proeth:description": "Following the BER precedent analysis, it becomes clear that Engineer A\u0027s professional obligations have crystallized into three specific required actions: engaging Client B about detailed evaluation, disclosing potential impacts to regulators and the public, and withdrawing if Client B refuses either course.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Discussion/analysis phase, following identification of the ethical conflict",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer Ethical Obligation Crystallized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#Event_Project_Continuation_Risk_Realized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does an engineer\u0027s duty to protect the public end when they withdraw from a project, or do obligations persist beyond the professional relationship?",
    "What obligations does Engineer A have toward a successor engineer who may inherit the project without knowledge of the flood risk?",
    "Is regulatory disclosure before withdrawal a necessary condition for withdrawal to be ethically sufficient, or merely a best practice?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "This event reveals that withdrawal, while ethically required, is not emotionally or ethically satisfying if it merely transfers the problem; Engineer A may feel the inadequacy of withdrawal as a complete solution; it introduces a deeper layer of moral complexity",
  "proeth-scenario:ethicalImplications": "Reveals the limits of withdrawal as an ethical remedy; demonstrates that professional obligations can survive the end of a contractual relationship; raises questions about the adequacy of individual engineer action as a mechanism for public protection in systemic risk situations",
  "proeth-scenario:learningMoment": "Withdrawal from a project does not fully discharge an engineer\u0027s ethical obligations when a known public risk remains unaddressed. The duty to protect the public may require affirmative disclosure even after the professional relationship ends.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "client_b": "May attempt to continue project with a less informed engineer, increasing legal and ethical exposure",
    "engineer_a": "Withdrawal may be professionally necessary but insufficient to fully discharge ethical obligations; must also ensure disclosure occurs",
    "regulatory_agencies": "Continue to be deprived of material information needed for proper oversight",
    "successor_engineer": "Inherits a project with undisclosed known risks; their professional standing is at risk through no fault of their own",
    "upstream_homeowners": "Remain unprotected if withdrawal is not accompanied by disclosure"
  },
  "proeth:activatesConstraint": [
    "Duty_To_Inform_Successor_Engineer",
    "Prohibition_Against_Abandonment_Without_Notice"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/88#Action_Withdraw_from_Project",
  "proeth:causesStateChange": "Withdrawal alone does not resolve the ethical problem if risk findings are not disclosed; the obligation to protect the public extends beyond the moment of withdrawal and requires affirmative disclosure before or concurrent with withdrawal",
  "proeth:createsObligation": [
    "Disclose_Risk_Findings_To_Regulators_Before_Withdrawal",
    "Ensure_Successor_Engineer_Awareness",
    "Document_Reasons_For_Withdrawal"
  ],
  "proeth:description": "If Engineer A withdraws from the project, the risk arises that another engineer without knowledge of the flood risk findings may continue the project without the same ethical awareness, potentially resulting in the harm proceeding unaddressed.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Hypothetical outcome following potential withdrawal decision",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Project Continuation Risk Realized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#CausalChain_39d4e1dd",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A accepts the consulting engagement from Client B with a scope limited to design and local [evaluation], which enabled the hydraulic evaluation that revealed the flood risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A formally accepts consulting engagement with scope bounded to design and local hydraulic evaluation",
      "proeth:element": "Accept Limited Scope Engagement (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A executes hydraulic evaluation of the culvert-to-bridge replacement project per scope",
      "proeth:element": "Hydraulic Evaluation Completed (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A exercises independent professional judgment drawing on hydraulic evaluation procedures",
      "proeth:element": "Form Climate Risk Judgment (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Hydraulic evaluation reveals that replacing the culvert with a bridge will increase hydraulic capacity and create upstream flood risk",
      "proeth:element": "Flood Risk Discovered (Event 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Discovery of flood risk triggers Engineer A\u0027s professional and ethical obligations to act on the finding",
      "proeth:element": "Engineer Ethical Obligation Crystallized (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Limited Scope Engagement (Action 1)",
  "proeth:counterfactual": "Without Engineer A accepting the engagement, the hydraulic evaluation would not have been performed and the flood risk would not have been formally discovered at this stage",
  "proeth:effect": "Flood Risk Discovered (Event 2)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s acceptance of the engagement",
    "Scope inclusion of hydraulic evaluation work",
    "Completion of the hydraulic evaluation procedures"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Acceptance of engagement + defined scope including hydraulic work + professional execution of evaluation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#CausalChain_f6af829a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The hydraulic evaluation reveals that replacing the culvert with a bridge will increase hydraulic capacity, directly prompting Engineer A to proactively propose commissioning a complex and costly hydrologic and hydraulic analysis",
  "proeth:causalSequence": [
    {
      "proeth:description": "Hydraulic evaluation reveals material upstream flood risk from proposed bridge replacement",
      "proeth:element": "Flood Risk Discovered (Event 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A applies independent professional judgment to assess significance of discovered risk",
      "proeth:element": "Form Climate Risk Judgment (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Professional obligations to public safety and third parties become operative upon risk discovery",
      "proeth:element": "Engineer Ethical Obligation Crystallized (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A proactively proposes commissioning detailed hydrologic and hydraulic analysis to quantify and address the risk",
      "proeth:element": "Propose Specialized Flood Analysis (Action 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Client B responds to the proposal by directing Engineer A to proceed without the costly specialized analysis",
      "proeth:element": "Client Directs Analysis Deferral (Action 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Flood Risk Discovered (Event 2)",
  "proeth:counterfactual": "Without the flood risk discovery, there would have been no basis or professional impetus for Engineer A to propose the specialized flood analysis",
  "proeth:effect": "Propose Specialized Flood Analysis (Action 3)",
  "proeth:necessaryFactors": [
    "Discovery of upstream flood risk through hydraulic evaluation",
    "Engineer A\u0027s professional obligation to address identified risks",
    "Existence of a recognized specialized analytical method capable of quantifying the risk"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Identified flood risk + professional duty of care + availability of specialized analysis methodology"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#CausalChain_0fa05a55",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following Client B\u0027s directive to proceed with the project without conducting the costly specialized flood analysis, the Analysis Deferral Imposed event directly materializes as a consequence of that volitional client decision",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A formally proposes costly specialized flood analysis to Client B",
      "proeth:element": "Propose Specialized Flood Analysis (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client B exercises project authority to direct Engineer A to proceed without the analysis",
      "proeth:element": "Client Directs Analysis Deferral (Action 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Specialized flood analysis is not conducted; risk remains unquantified and undisclosed",
      "proeth:element": "Analysis Deferral Imposed (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Approximately twenty upstream properties remain exposed to uncharacterized flood risk",
      "proeth:element": "Third Party Risk Unmitigated (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s obligation to engage client, propose disclosure, or withdraw becomes fully operative",
      "proeth:element": "Engineer Ethical Obligation Crystallized (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Client Directs Analysis Deferral (Action 4)",
  "proeth:counterfactual": "If Client B had approved the specialized flood analysis, or if Engineer A had withdrawn or escalated to regulators, the deferral would not have been imposed and third-party risk would have been characterized",
  "proeth:effect": "Analysis Deferral Imposed (Event 3)",
  "proeth:necessaryFactors": [
    "Client B\u0027s authority over project scope and budget decisions",
    "Client B\u0027s decision to prioritize cost over risk characterization",
    "Engineer A\u0027s continuation on the project following the directive"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Client B (primary); Engineer A (shared for continuation)",
  "proeth:sufficientFactors": [
    "Client directive to defer + Engineer A\u0027s non-withdrawal + absence of regulatory mandate forcing the analysis"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#CausalChain_597612f5",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a consequence of the deferred analysis and the absence of disclosure, approximately twenty upstream properties remain exposed to uncharacterized and unmitigated flood risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client B directs project to proceed without specialized flood analysis",
      "proeth:element": "Client Directs Analysis Deferral (Action 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Flood risk remains unquantified; no disclosure made to regulators or affected parties",
      "proeth:element": "Analysis Deferral Imposed (Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A fails to substantively engage Client B on necessity of disclosure, missing key intervention point",
      "proeth:element": "Engage Client on Risk Disclosure (Action 5) \u2014 NOT TAKEN",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A does not propose regulatory disclosure report, leaving third parties uninformed",
      "proeth:element": "Propose Regulatory Disclosure Report (Action 6) \u2014 NOT TAKEN",
      "proeth:step": 4
    },
    {
      "proeth:description": "Twenty upstream properties remain exposed to uncharacterized flood risk without knowledge or recourse",
      "proeth:element": "Third Party Risk Unmitigated (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Analysis Deferral Imposed (Event 3)",
  "proeth:counterfactual": "If the specialized analysis had been conducted, or if disclosure had been made to regulators or property owners, the risk to third parties would have been identified, quantified, and potentially mitigated through design modification or informed consent",
  "proeth:effect": "Third Party Risk Unmitigated (Event 4)",
  "proeth:necessaryFactors": [
    "Non-performance of the specialized flood analysis",
    "Absence of disclosure to regulators or affected third parties",
    "Continuation of the bridge replacement project",
    "Existence of approximately twenty upstream properties in the flood impact zone"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Client B (primary for deferral decision); Engineer A (shared for failure to escalate disclosure obligations)",
  "proeth:sufficientFactors": [
    "Deferred analysis + no disclosure + project continuation + presence of third-party properties in risk zone"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#CausalChain_f31db46f",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "If Client B refuses both further substantive engagement on the flood risk and agreement to disclose, Engineer A\u0027s ethical obligations under BER precedent require withdrawal from the project to avoid complicity in ongoing third-party harm",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A attempts substantive engagement with Client B on flood risk disclosure necessity",
      "proeth:element": "Engage Client on Risk Disclosure (Action 5)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A proposes providing disclosure report to regulators after Client B remains unconvinced",
      "proeth:element": "Propose Regulatory Disclosure Report (Action 6)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Client B refuses substantive engagement and declines to authorize disclosure report",
      "proeth:element": "Client B Refuses Both Options",
      "proeth:step": 3
    },
    {
      "proeth:description": "All intermediate remediation options exhausted; Engineer A\u0027s obligation to withdraw becomes operative",
      "proeth:element": "Engineer Ethical Obligation Crystallized (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A withdraws from the project, triggering Project Continuation Risk (Event 6) but fulfilling ethical duty",
      "proeth:element": "Withdraw from Project (Action 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Client Directs Analysis Deferral (Action 4) + Third Party Risk Unmitigated (Event 4)",
  "proeth:counterfactual": "If Client B had agreed to either substantive engagement or disclosure at any prior stage, withdrawal would not be required; if Engineer A withdraws without exhausting Actions 5 and 6 first, the withdrawal may itself be premature and ethically incomplete",
  "proeth:effect": "Withdraw from Project (Action 7)",
  "proeth:necessaryFactors": [
    "Client B\u0027s refusal to engage substantively on flood risk disclosure",
    "Client B\u0027s refusal to agree to regulatory or third-party disclosure",
    "Engineer A\u0027s crystallized ethical obligation to protect public safety",
    "Exhaustion of intermediate remediation options (Actions 5 and 6)"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (obligation to withdraw); Client B (responsibility for creating conditions requiring withdrawal)",
  "proeth:sufficientFactors": [
    "Client refusal of disclosure + exhaustion of engagement options + Engineer A\u0027s operative professional ethics obligations"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/88#",
    "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/88#CausalChain_8ac2c3c0",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "If Engineer A withdraws from the project, the risk arises that another engineer without knowledge of the flood risk will continue the project, potentially perpetuating or worsening the unmitigated third-party harm",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A withdraws after exhausting engagement and disclosure options with Client B",
      "proeth:element": "Withdraw from Project (Action 7)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client B proceeds with project by engaging a new engineer unaware of prior flood risk findings",
      "proeth:element": "Client B Engages Successor Engineer",
      "proeth:step": 2
    },
    {
      "proeth:description": "Successor engineer lacks access to Engineer A\u0027s hydraulic evaluation findings and flood risk discovery",
      "proeth:element": "Flood Risk Knowledge Gap",
      "proeth:step": 3
    },
    {
      "proeth:description": "Project proceeds without flood risk characterization, perpetuating unmitigated third-party exposure",
      "proeth:element": "Project Continuation Risk Realized (Event 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Twenty upstream properties remain at risk; harm potential continues or increases under uninformed successor",
      "proeth:element": "Third Party Risk Unmitigated (Event 4) \u2014 Perpetuated",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Withdraw from Project (Action 7)",
  "proeth:counterfactual": "If Engineer A had disclosed the flood risk findings to regulators before withdrawing, or if Client B had abandoned the project, the continuation risk would be substantially reduced or eliminated",
  "proeth:effect": "Project Continuation Risk Realized (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s withdrawal from the project",
    "Client B\u0027s intent to continue the project with a successor engineer",
    "Absence of any disclosure mechanism ensuring the successor engineer is informed of the flood risk",
    "Successor engineer\u0027s lack of independent knowledge of the identified risk"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Client B (primary, for continuing project without disclosure); Engineer A (partial, for not securing disclosure before withdrawal)",
  "proeth:sufficientFactors": [
    "Withdrawal + project continuation intent + no risk disclosure to successor = continuation risk realized"
  ],
  "proeth:withinAgentControl": true
}