{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Determine_100-Year_Surge_Standard",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Present the 100-year standard as a recommendation rather than a requirement, framing it as one option among several to soften anticipated client resistance",
    "Determine a lower standard (e.g., 50-year surge) by selectively weighting older data, rationalizing that the new algorithm is too novel to be definitive",
    "Make the 100-year determination but simultaneously prepare cost-mitigation alternatives to present alongside the finding, anticipating client pushback proactively"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by the core professional obligation to hold public safety above client interests. Having applied rigorous, state-of-the-art methods, Engineer A translates technical findings into a clear safety standard, accepting the professional responsibility to make a definitive judgment rather than hedging to avoid conflict.",
  "proeth-scenario:consequencesIfAlternative": [
    "Framing the standard as optional rather than required misrepresents the engineer\u0027s professional judgment and gives the client false latitude to choose an unsafe option \u2014 an ethical failure that could constitute fraud or negligence.",
    "Selectively weighting data to reach a more convenient conclusion is a fundamental breach of engineering ethics and scientific integrity, regardless of rationalization about methodological uncertainty.",
    "Proactively preparing cost-mitigation alternatives is a constructive approach that upholds the safety standard while demonstrating client-service orientation \u2014 potentially the most professionally sophisticated response, though it does not change the ethical floor."
  ],
  "proeth-scenario:decisionSignificance": "The act of making and standing behind a safety-critical professional determination \u2014 even when the finding is commercially inconvenient \u2014 is the central ethical act of engineering practice. This moment illustrates that professional judgment is not negotiable in response to economic pressure.",
  "proeth-scenario:ethicalTension": "Objective technical judgment vs. awareness of client financial consequences \u2014 Engineer A knows this determination will be costly and unwelcome, creating subtle pressure to soften or qualify the finding. The tension between scientific honesty and client service is at its sharpest at the moment of formal determination.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If the determination is accurate and ignored, future residents face life-threatening flood risk. If Engineer A softens the finding under anticipated pressure, the engineer has compromised professional integrity and potentially contributed to foreseeable harm. The determination also sets the terms for all subsequent conflict.",
  "proeth:description": "Based on technical analysis using newly released data and algorithm, Engineer A makes a professional judgment determination that the residential development must be built to a 100-year projected storm surge elevation standard due to unacceptable public safety risks at lower projections.",
  "proeth:foreseenUnintendedEffects": [
    "Recommendation will significantly increase construction costs, likely creating conflict with client",
    "Standard may exceed what client anticipated or budgeted for",
    "Determination made in absence of any local building code to provide external validation or mandate"
  ],
  "proeth:fulfillsObligation": [
    "NSPE paramount obligation to hold public health and safety above all other considerations",
    "Obligation to exercise independent professional judgment based on technical competence",
    "Obligation to be objective and truthful in professional assessments",
    "NSPE Code Section III.2.d. obligations regarding environmental protection"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as the paramount engineering obligation",
    "Technical objectivity and professional independence",
    "Good faith application of engineering judgment",
    "Precautionary principle in the face of substantial public safety risk"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public safety obligation requiring highest defensible standard vs. client cost and commercial viability interests",
    "proeth:resolutionReasoning": "Engineer A resolves in favor of public safety, consistent with NSPE Code hierarchy placing public safety above client interests, and consistent with BER discussion concluding that risk to life and property should prevail over cost considerations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Establish a technically justified and publicly safe design standard that protects future residents and the general public from foreseeable storm surge risks associated with climate change and sea level rise",
  "proeth:requiresCapability": [
    "Expert-level coastal engineering and hydrodynamic modeling judgment",
    "Ability to translate technical risk data into appropriate design standards",
    "Independent professional judgment in the absence of regulatory guidance",
    "Understanding of storm surge probability and climate projection methodologies"
  ],
  "proeth:temporalMarker": "At conclusion of technical assessment phase, prior to presenting findings to client",
  "proeth:withinCompetence": true,
  "rdfs:label": "Determine 100-Year Surge Standard"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Continue_Advocating_Higher_Safety_Standard",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept Client A\u0027s refusal after the first objection and proceed with the project at the lower standard the client prefers",
    "Immediately withdraw from the project upon Client A\u0027s first refusal, without further advocacy",
    "Propose a compromise standard (e.g., 75-year surge elevation) to find middle ground between the engineer\u0027s determination and the client\u0027s cost constraints"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by genuine concern for future residents and the general public who will bear the consequences of an inadequately designed development, combined with professional ethical obligations that do not permit simple deference to client preference on safety matters. Continued advocacy reflects the belief that the client may be persuadable if the full scope of risk \u2014 including liability exposure \u2014 is made vivid.",
  "proeth-scenario:consequencesIfAlternative": [
    "Accepting the client\u0027s refusal and proceeding at a lower standard constitutes a direct violation of engineering ethics \u2014 Engineer A would be knowingly facilitating a development that poses unacceptable public safety risks, potentially exposing residents to life-threatening harm.",
    "Immediate withdrawal without advocacy may be premature \u2014 it forgoes the possibility of persuasion and does not fulfill the obligation to make every reasonable effort to protect public safety before disengaging.",
    "Proposing a compromise standard is ethically problematic if Engineer A\u0027s professional judgment is that the 100-year standard is the minimum required for public safety \u2014 a compromise below that threshold is not a legitimate middle ground but a capitulation to economic pressure on a safety-critical determination."
  ],
  "proeth-scenario:decisionSignificance": "Engineers are not merely technical service providers who defer to client decisions on all matters \u2014 they have an independent obligation to advocate for public safety even against client resistance. However, advocacy has limits, and this action illustrates the prescribed escalation path before withdrawal becomes necessary.",
  "proeth-scenario:ethicalTension": "Persistent advocacy for public safety vs. respect for client autonomy and the limits of the engineer-client relationship \u2014 there is a point at which continued advocacy becomes coercive or paternalistic, and Engineer A must navigate between insufficient advocacy (abandoning the safety standard too easily) and overreach (exceeding the proper professional role).",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "If advocacy succeeds, the development is built safely and the public is protected. If advocacy fails, Engineer A must decide whether to withdraw \u2014 with consequences for both the project and the engineer\u0027s livelihood. The intensity of this moment defines the ethical core of the scenario.",
  "proeth:description": "After Client A refuses to agree to the 100-year storm surge standard, Engineer A is prescribed to continue pursuing discussions with Client A to persuade the developer of the danger posed to future residents and the general public, and the potential for significant property and environmental damage.",
  "proeth:foreseenUnintendedEffects": [
    "Continued advocacy may strain the client relationship further",
    "Client may remain intransigent, making withdrawal ultimately necessary",
    "Persistent advocacy creates a documented record of Engineer A\u0027s good faith efforts to protect public safety"
  ],
  "proeth:fulfillsObligation": [
    "NSPE obligation to hold public health and safety paramount",
    "Duty to advise client of actions necessary to protect public safety before escalating to withdrawal",
    "Obligation to act in good faith to resolve professional disagreements through communication before severing engagement",
    "Responsibility to protect future residents and general public from foreseeable harm"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as paramount engineering obligation",
    "Good faith engagement and professional counsel",
    "Proportional escalation of response to client non-compliance",
    "Protection of third parties (future residents, general public) who are not party to the client relationship"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Persistent public safety advocacy vs. client autonomy and risk of irreparably damaging the professional relationship",
    "proeth:resolutionReasoning": "BER discussion concludes that risk to life and property should prevail over cost considerations; continued advocacy is the prescribed first response to refusal before escalating to withdrawal"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Convince Client A to voluntarily adopt the 100-year storm surge standard, thereby protecting public safety without requiring Engineer A to withdraw from the project",
  "proeth:requiresCapability": [
    "Persuasive professional communication of technical risk to non-engineering client",
    "Ability to articulate long-term liability, safety, and ethical implications to developer",
    "Negotiation skills to seek compromise without compromising safety standards"
  ],
  "proeth:temporalMarker": "Immediately following Client A\u0027s refusal, during prescribed post-refusal negotiation phase",
  "proeth:withinCompetence": true,
  "rdfs:label": "Continue Advocating Higher Safety Standard"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Withdraw_from_Project",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Remain on the project while continuing to document objections in writing, reasoning that an engaged engineer with safety concerns provides more protection than a disengaged one",
    "Withdraw but notify Client A\u0027s lender or insurer of the safety determination, reasoning that financial stakeholders may exert pressure the engineer cannot",
    "Withdraw and simultaneously report the situation to the relevant professional engineering licensing board or ethics committee"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by the recognition that continuing to provide professional services to a project that poses unacceptable public safety risks \u2014 after sustained advocacy has failed \u2014 makes the engineer complicit in potential harm. Withdrawal is the mechanism by which Engineer A refuses to lend professional credibility and services to an outcome the engineer has determined is unsafe.",
  "proeth-scenario:consequencesIfAlternative": [
    "Remaining on the project while objecting creates a false appearance of professional endorsement \u2014 Engineer A\u0027s name and seal on the project implies approval of the final design, which would be a misrepresentation if the design does not meet the engineer\u0027s own safety standard.",
    "Notifying lenders or insurers is a creative escalation that may be effective but raises questions about confidentiality obligations and whether such disclosure is authorized \u2014 it may also not be within the scope of prescribed ethical actions.",
    "Reporting to a licensing board may be appropriate if Engineer A believes a successor engineer will be asked to certify an unsafe design, but may be premature at the withdrawal stage before any such certification occurs."
  ],
  "proeth-scenario:decisionSignificance": "Withdrawal is a legitimate and sometimes obligatory ethical response, but it is not cost-free or consequence-free. This action illustrates the limits of the engineer\u0027s ability to control outcomes after disengagement, and raises the important question of whether withdrawal alone fulfills the public safety obligation or whether further action (Action 7) is also required.",
  "proeth-scenario:ethicalTension": "Professional integrity and public safety obligation vs. contractual duty to the client, financial self-interest, and concern that withdrawal may result in a less scrupulous replacement engineer \u2014 creating the troubling possibility that withdrawal makes the public less safe rather than more safe.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional integrity and license are protected by withdrawal. However, the development may proceed with another engineer at a lower standard, leaving future residents at risk. Engineer A may also face contractual liability for withdrawal. The public safety risk does not disappear \u2014 it is merely no longer Engineer A\u0027s direct professional responsibility.",
  "proeth:description": "If Client A continues to refuse the 100-year storm surge elevation standard after sustained advocacy, Engineer A is prescribed to withdraw from the project rather than continue providing services that would facilitate a development Engineer A believes poses unacceptable public safety risks.",
  "proeth:foreseenUnintendedEffects": [
    "Withdrawal does not prevent Client A from proceeding with the project using another engineer",
    "Loss of professional fee and client relationship",
    "Withdrawal may leave Engineer A without ongoing influence over project safety decisions",
    "Creates a clear professional record that Engineer A refused to endorse an unsafe standard"
  ],
  "proeth:fulfillsObligation": [
    "NSPE paramount obligation to hold public health and safety above client and employer interests",
    "Obligation to refuse to approve or participate in plans that endanger public safety",
    "Duty to avoid professional complicity in knowingly unsafe engineering decisions",
    "Obligation to maintain professional integrity when client refuses to adopt necessary safety standards"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as the paramount and non-negotiable engineering obligation",
    "Professional integrity and refusal to endorse unsafe practices",
    "Proportional and escalating response to client non-compliance with safety requirements",
    "Engineer\u0027s independent professional responsibility that cannot be overridden by client instruction"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Contractual obligation to complete professional services vs. ethical obligation to withdraw when client refuses necessary safety standards",
    "proeth:resolutionReasoning": "NSPE Code and BER discussion unambiguously resolve this conflict in favor of withdrawal; the obligation to protect public safety is paramount and cannot be subordinated to contractual or financial considerations when client refuses to adopt necessary safety standards"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Avoid professional complicity in a development that Engineer A believes poses unacceptable risks to public health, safety, and the environment, and preserve professional integrity by refusing to provide engineering services that enable an unsafe project",
  "proeth:requiresCapability": [
    "Professional judgment to determine that continued engagement is ethically untenable",
    "Ability to manage professional disengagement in accordance with contractual and ethical obligations",
    "Courage to withdraw from a fee-generating engagement on ethical grounds"
  ],
  "proeth:temporalMarker": "Contingent on failed negotiations; prescribed action following continued client refusal after advocacy",
  "proeth:violatesObligation": [
    "Contractual obligation to complete services for Client A (superseded by overriding public safety obligation)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Withdraw from Project"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Contact_Government_Officials_for_Code_Advocacy",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Take no further action after withdrawal, reasoning that the professional obligation ends with disengagement from the project",
    "Publish findings in a technical journal or present at a professional conference to raise awareness of the regional risk without directly lobbying officials",
    "Collaborate with a professional engineering society (e.g., ASCE, NSPE) to develop and advocate for model coastal building codes for the region, leveraging institutional credibility rather than acting as an individual"
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognizes that the client conflict is a symptom of a systemic regulatory failure \u2014 the absence of regional building codes \u2014 and that addressing only the immediate project leaves the underlying public safety vulnerability intact for future developments. Contacting government officials reflects an understanding that engineers have a civic obligation that extends beyond individual projects to the broader built environment and public welfare.",
  "proeth-scenario:consequencesIfAlternative": [
    "Taking no further action after withdrawal may satisfy the minimum ethical requirement but foregoes the opportunity to prevent future harm \u2014 the systemic regulatory vacuum remains, and the next developer in the region faces the same unconstrained risk calculus.",
    "Publishing technical findings advances scientific knowledge and public awareness without the political complexity of direct lobbying, but may have slower and less targeted impact on local regulatory change than direct engagement with officials.",
    "Collaborating with a professional society amplifies Engineer A\u0027s advocacy with institutional authority and reduces the risk of being dismissed as a single disgruntled engineer \u2014 but requires more time and coordination, and the regulatory change may come too late to affect the immediate project."
  ],
  "proeth-scenario:decisionSignificance": "This action illustrates the highest expression of engineering ethics: moving beyond individual project compliance to address systemic conditions that create recurring public safety risks. It also raises important questions about the scope of engineering professional responsibility and the relationship between technical expertise and public policy.",
  "proeth-scenario:ethicalTension": "Proactive civic engagement for systemic public safety vs. concerns about overstepping the engineering role into policy advocacy, potential breach of client confidentiality in how the situation is described to officials, and the practical question of whether a single engineer\u0027s advocacy can produce meaningful regulatory change.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "If successful, code advocacy could protect not only this development\u0027s future residents but all future residents of the region from inadequate coastal construction standards. If unsuccessful or mishandled \u2014 particularly if client confidentiality is breached \u2014 Engineer A could face legal liability and professional discipline while failing to achieve the systemic change sought.",
  "proeth:description": "Engineer A is prescribed to consider contacting local government officials to advocate for the implementation of appropriate and updated region-wide building codes for the geographical area where the residential development project is located, addressing the systemic regulatory vacuum that enabled the client-engineer conflict.",
  "proeth:foreseenUnintendedEffects": [
    "Government officials may not act or may act slowly, leaving the regulatory gap unaddressed in the near term",
    "Advocacy may be perceived by Client A as adversarial or retaliatory",
    "Successful advocacy could retroactively impose code requirements on Client A\u0027s project or similar projects in the region",
    "Sets a precedent for engineers engaging in proactive policy advocacy beyond the immediate client engagement"
  ],
  "proeth:fulfillsObligation": [
    "NSPE obligation to hold public health and safety paramount, extended to systemic and policy dimensions",
    "NSPE Code Section III.2.d. obligations regarding environmental protection at a regional scale",
    "Obligation to protect third parties (future residents of the broader region) who are not party to the immediate client engagement",
    "Professional responsibility to contribute engineering expertise to public policy for the benefit of society",
    "Obligation analogous to BER Case 04-8 precedent of bringing matters to appropriate authorities when client fails to take necessary action"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as paramount obligation extending beyond individual project scope",
    "Engineers\u0027 role in contributing technical expertise to public policy and regulation",
    "Proactive societal responsibility to address systemic risks, not merely project-level risks",
    "Environmental protection as an engineering obligation (NSPE Code Section III.2.d.)"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Individual project-level client obligations and professional discretion vs. broader societal obligation to advocate for systemic regulatory change that protects the public beyond the immediate engagement",
    "proeth:resolutionReasoning": "BER discussion prescribes this as an action Engineer A \u0027should consider,\u0027 recognizing it as a professional responsibility that flows from the same public safety obligation underlying the project-level decisions, while acknowledging it is discretionary rather than mandatory; the broader societal obligation to address the systemic regulatory vacuum supports taking this action"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Advocate for systemic policy change by prompting local government to adopt appropriate regional building codes for coastal storm surge risk, thereby protecting not only the immediate development\u0027s future residents but all residents in the broader geographic area from foreseeable climate and sea level rise risks",
  "proeth:requiresCapability": [
    "Ability to translate technical coastal risk findings into accessible policy recommendations for government officials",
    "Knowledge of regional building code frameworks and processes for their adoption",
    "Professional credibility to serve as a credible technical advocate in a policy context",
    "Understanding of the geographic scope of the coastal risk beyond the immediate project site"
  ],
  "proeth:temporalMarker": "Following or concurrent with withdrawal from the project; prescribed as a broader societal obligation beyond the immediate client engagement",
  "proeth:withinCompetence": true,
  "rdfs:label": "Contact Government Officials for Code Advocacy"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Accept_Coastal_Risk_Engagement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the engagement due to the absence of local building codes, citing inability to define a defensible regulatory baseline",
    "Accept the engagement but negotiate upfront contractual language requiring the client to implement findings regardless of cost",
    "Accept the engagement conditionally, first consulting with local government officials about the regulatory vacuum before proceeding"
  ],
  "proeth-scenario:characterMotivation": "Engineer A seeks to apply specialized expertise in hydrodynamic modeling and coastal risk assessment, likely motivated by professional interest, financial compensation, and a genuine desire to contribute technical competence to a complex coastal development challenge in a regulatory vacuum.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining leaves the developer free to hire a less scrupulous engineer who may apply lower standards, potentially producing a worse public safety outcome \u2014 but Engineer A avoids complicity in any resulting harm.",
    "Negotiating safety-compliance language upfront could prevent the later client conflict entirely, though the client might refuse such terms and the engagement would not proceed.",
    "Consulting local officials first could prompt early code development, providing Engineer A a regulatory anchor \u2014 but delays the project and may frustrate the client before work even begins."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that the act of accepting an engagement is itself an ethical choice: engineers carry their professional obligations into every project regardless of local regulatory context, and the absence of building codes does not reduce the duty to protect public safety.",
  "proeth-scenario:ethicalTension": "Autonomy to accept professional engagements vs. foreseeable obligation \u2014 by accepting, Engineer A implicitly commits to honest, safety-first findings even if those findings conflict with the client\u0027s financial interests. Accepting work in an unregulated environment also raises the question of whether the engineer\u0027s standards will substitute for absent regulatory floors.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Future residents and the general public could be exposed to life-threatening coastal flood risk if the engagement proceeds without rigorous safety standards. Engineer A\u0027s professional reputation and license are also at stake from the outset.",
  "proeth:description": "Engineer A voluntarily accepts retention by Client A to perform hydrodynamic modeling and coastal risk assessment for a residential development in a coastal area with no existing building codes.",
  "proeth:foreseenUnintendedEffects": [
    "Potential exposure to client-engineer conflicts if findings are unfavorable to developer\u0027s cost objectives",
    "Assumption of professional responsibility in a regulatory vacuum where no building codes exist to provide external enforcement support"
  ],
  "proeth:fulfillsObligation": [
    "NSPE obligation to provide competent professional services within area of expertise",
    "Obligation to serve client interests by undertaking legitimate professional work",
    "Obligation to contribute engineering expertise to projects with public safety implications"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence and engagement",
    "Faithful agency to client",
    "Public health and safety as paramount concern"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client service obligation vs. anticipated public safety responsibility in absence of external regulatory enforcement",
    "proeth:resolutionReasoning": "Engineer A accepts engagement, implicitly committing to apply professional judgment and safety standards even in the absence of mandating regulations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide professional engineering services to the developer client, fulfilling a contractual obligation and applying technical expertise to coastal risk assessment",
  "proeth:requiresCapability": [
    "Hydrodynamic modeling expertise",
    "Coastal risk assessment methodology",
    "Climate change and sea level rise analysis",
    "Professional judgment in applying safety standards without regulatory guidance"
  ],
  "proeth:temporalMarker": "Project outset, prior to any technical work",
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Coastal Risk Engagement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Apply_Newly_Released_Algorithm_and_Data",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Use only previously established conventional methods, avoiding the newly released algorithm due to its novelty and potential uncertainty",
    "Apply both the new algorithm and conventional methods, presenting results as a range with explicit uncertainty quantification",
    "Use the new algorithm but engage peer review from other coastal engineers before finalizing findings to validate the methodology"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by professional duty to use the best available science and methods, consistent with the engineering obligation to hold public safety paramount. Applying newly released data and a recently developed algorithm reflects a commitment to state-of-the-art practice rather than convenient reliance on outdated baselines that might produce a more palatable \u2014 but less accurate \u2014 result.",
  "proeth-scenario:consequencesIfAlternative": [
    "Using only conventional methods might produce a lower surge elevation standard, reducing client conflict but potentially leaving residents underprotected \u2014 and exposing Engineer A to liability if the newer data later proves the conventional approach inadequate.",
    "Presenting a range gives the client transparency about uncertainty but may be exploited to justify selecting the lower bound for cost reasons, shifting the ethical burden without resolving it.",
    "Peer review strengthens the defensibility of findings and reduces the risk that the novel algorithm contains errors, but adds time and cost and may delay the client\u0027s project timeline."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that engineers have an affirmative obligation to apply current best practices and newly available data, and that deliberately choosing inferior methods to soften findings would itself constitute an ethical violation. Method selection is not ethically neutral.",
  "proeth-scenario:ethicalTension": "Methodological rigor and professional integrity vs. client expectation management \u2014 using cutting-edge methods may yield more stringent findings that increase project costs and create client conflict. A less conscientious engineer might justify using older methods to avoid controversy, raising the question of whether method selection can itself be a form of bias.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Accuracy of the risk assessment directly determines whether future residents are adequately protected. Underestimating surge risk through outdated methods could result in loss of life, property destruction, and environmental damage. Overestimating could impose unnecessary costs \u2014 but the asymmetry of harm favors rigor.",
  "proeth:description": "Engineer A deliberately employs a recently developed algorithm incorporating newly identified historic weather data and newly released information to conduct the coastal risk assessment, rather than relying solely on conventional or previously established methods.",
  "proeth:foreseenUnintendedEffects": [
    "Findings may diverge from conventional standards and be harder for client to accept",
    "Use of cutting-edge methodology may invite challenge to legitimacy or acceptance of conclusions",
    "Higher safety recommendations resulting from updated data may significantly increase project costs"
  ],
  "proeth:fulfillsObligation": [
    "NSPE obligation to perform services only in areas of competence using current technical knowledge",
    "Obligation to be objective and truthful in professional assessments",
    "Obligation to include all relevant and pertinent information in professional reports (per BER Case 07-6 precedent)",
    "Duty to apply best available science to protect public health and safety"
  ],
  "proeth:guidedByPrinciple": [
    "Technical objectivity and accuracy",
    "Use of best available scientific methods",
    "Public safety as paramount engineering obligation",
    "Professional integrity in methodology selection"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Methodological rigor and use of cutting-edge data vs. conventional standards more readily accepted by client and regulators",
    "proeth:resolutionReasoning": "Engineer A resolves in favor of technical rigor, applying the most current and accurate methodology available, consistent with the obligation to hold public safety paramount over client cost considerations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Produce the most technically accurate and current coastal risk assessment possible, reflecting best available science to protect future residents and the general public",
  "proeth:requiresCapability": [
    "Advanced hydrodynamic modeling",
    "Proficiency with newly developed algorithmic tools",
    "Ability to interpret and integrate newly released climate and weather datasets",
    "Professional judgment to evaluate and apply emerging technical methodologies"
  ],
  "proeth:temporalMarker": "During the technical assessment phase, after engagement and before presenting findings to client",
  "proeth:withinCompetence": true,
  "rdfs:label": "Apply Newly Released Algorithm and Data"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Action_Present_Findings_to_Client",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Deliver findings in writing only, without a meeting, to create a clear paper trail but avoid direct confrontation",
    "Present findings in a meeting without written documentation, relying on verbal communication",
    "Present findings but omit or minimize the public safety rationale, focusing only on technical specifications to reduce emotional friction"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by transparency and the duty to inform the client fully, including the public safety rationale, so that Client A cannot later claim ignorance of the risk basis. Clear communication also fulfills the professional obligation to serve the client\u0027s genuine long-term interests \u2014 which include avoiding liability \u2014 even when those interests conflict with the client\u0027s immediate financial preferences.",
  "proeth-scenario:consequencesIfAlternative": [
    "Written-only delivery ensures documentation but may reduce the client\u0027s understanding and eliminate the opportunity for Engineer A to gauge the client\u0027s reaction and respond to questions in real time \u2014 a missed opportunity for persuasion.",
    "Verbal-only communication without documentation creates significant professional risk: if the client later denies being informed of the safety rationale, Engineer A has no evidence of the disclosure.",
    "Omitting the public safety rationale is an ethical failure \u2014 it deprives the client of the full basis for the determination and undermines Engineer A\u0027s ability to later justify withdrawal on public safety grounds, having never clearly articulated those grounds."
  ],
  "proeth-scenario:decisionSignificance": "Effective communication of safety-critical findings is itself an ethical obligation, not merely a procedural step. How an engineer presents unwelcome findings \u2014 with clarity, completeness, and documented rationale \u2014 shapes whether the client can make an informed decision and whether the engineer is protected professionally.",
  "proeth-scenario:ethicalTension": "Complete and honest disclosure vs. anticipation of client refusal \u2014 Engineer A must communicate findings fully knowing this will trigger conflict, and must resist any temptation to soften language, bury the safety rationale, or present the finding ambiguously to avoid confrontation.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If findings are communicated unclearly or incompletely, the client may make decisions based on misunderstanding, and Engineer A loses the moral and legal standing to later withdraw or escalate. Clear documentation of the communication also protects Engineer A in any future liability proceeding.",
  "proeth:description": "Engineer A communicates the technical determination that the project must be built to the 100-year projected storm surge elevation standard to Client A, including the public safety rationale underlying that recommendation.",
  "proeth:foreseenUnintendedEffects": [
    "Client may refuse to accept the higher-cost recommendation, creating conflict",
    "Transparent disclosure of safety concerns creates a record of professional advice given",
    "Client refusal following disclosure will trigger further ethical obligations for Engineer A"
  ],
  "proeth:fulfillsObligation": [
    "NSPE obligation to be objective and truthful in professional reports and communications",
    "Obligation to include all relevant and pertinent information in professional assessments (per BER Case 07-6)",
    "Duty of faithful agency including honest communication of professional findings to client",
    "Obligation to advise client of actions necessary to protect public safety"
  ],
  "proeth:guidedByPrinciple": [
    "Truthfulness and objectivity in professional communications",
    "Faithful agency and honest client counsel",
    "Transparency regarding material safety findings",
    "Public safety as paramount obligation"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer in Private Practice)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Complete honest disclosure of safety-driven findings vs. preservation of client relationship and project continuity",
    "proeth:resolutionReasoning": "Honest and complete disclosure is non-negotiable under NSPE ethical obligations; Engineer A must present findings fully regardless of anticipated client reaction"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill professional duty to inform client of material findings and safety requirements, enabling client to make an informed decision about the project design standard",
  "proeth:requiresCapability": [
    "Clear technical communication to non-engineering client",
    "Ability to explain risk assessment methodology and its implications",
    "Professional confidence to deliver unfavorable findings to client"
  ],
  "proeth:temporalMarker": "After completing technical assessment, upon delivery of findings to Client A",
  "proeth:withinCompetence": true,
  "rdfs:label": "Present Findings to Client"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Event_New_Algorithm_Released",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When a new methodology is released mid-project, at what point does an engineer become obligated to apply it rather than rely on previously accepted methods?",
    "How should engineers communicate to clients that evolving science may change project requirements and costs?",
    "Does the existence of better tools create an immediate ethical obligation, or is there a reasonable transition period for professional adoption?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral to mildly energizing for Engineer A as a professional tool; potentially alarming in retrospect when results reveal higher risk than previously understood; developers and clients may feel unsettled as the scientific landscape shifts under their assumptions",
  "proeth-scenario:ethicalImplications": "Reveals tension between professional obligation to use best available science and client expectations set under older standards; raises questions about who bears the cost when scientific advancement raises safety thresholds mid-project; underscores that engineering competence is not static",
  "proeth-scenario:learningMoment": "Illustrates that engineering standards of care are dynamic and evolve with scientific knowledge; engineers have an obligation to apply the best available tools and data, even when doing so complicates client relationships or increases project costs.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "broader_profession": "Standard of care elevated; all coastal engineers now expected to incorporate new methodology",
    "client_a": "Faces potential cost increases if new methodology reveals higher risk thresholds; prior planning assumptions may be invalidated",
    "engineer_a": "Obligated to use new methodology; results may be more conservative and harder to sell to client; professional credibility tied to applying best available science",
    "future_residents": "Benefit from more accurate risk assessment; safety potentially improved if findings are heeded"
  },
  "proeth:activatesConstraint": [
    "Competence_Currency_Constraint",
    "Best_Available_Science_Constraint"
  ],
  "proeth:causesStateChange": "State of professional knowledge shifts; older modeling approaches become potentially inadequate; Engineer A is obligated to incorporate new methodology into assessment",
  "proeth:createsObligation": [
    "Obligation_to_Apply_Best_Available_Methods",
    "Obligation_to_Stay_Current_with_Relevant_Tools"
  ],
  "proeth:description": "A newly developed hydrodynamic modeling algorithm incorporating newly identified historic weather data becomes publicly available, providing more accurate coastal risk assessment capabilities than previously possible.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to or concurrent with Engineer A\u0027s engagement; precedes application of the algorithm",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "New Algorithm Released"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Event_No_Building_Codes_Exist",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When no building code exists, how should an engineer determine what standard of safety is \u0027enough\u0027? Who bears that burden?",
    "Does the absence of regulation reduce an engineer\u0027s ethical obligations, increase them, or leave them unchanged?",
    "What responsibility do engineers have to advocate for regulatory frameworks when they identify dangerous gaps?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Potentially alarming for Engineer A upon recognizing the absence of a regulatory safety net; developer may view the lack of codes as an opportunity to minimize costs; future residents are unknowingly vulnerable; observers in the profession may recognize this as a systemic risk",
  "proeth-scenario:ethicalImplications": "Exposes the danger of treating regulatory compliance as the ceiling rather than the floor of professional responsibility; raises questions about the engineer\u0027s role as a public safety guardian independent of legal mandates; highlights systemic governance failures that place disproportionate ethical burdens on individual professionals",
  "proeth-scenario:learningMoment": "Demonstrates that engineers cannot rely on regulatory compliance as a substitute for professional ethical judgment; when codes are absent, the engineer\u0027s duty to public safety becomes even more critical and non-delegable. This is a foundational principle in engineering ethics.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "broader_public": "Demonstrates systemic gap in coastal safety governance",
    "client_a": "Freed from mandatory compliance costs but exposed to liability if engineer\u0027s recommendations are ignored and harm results",
    "engineer_a": "Bears sole professional responsibility for setting safety standards; no code to hide behind if something goes wrong; heightened exposure to liability and ethical scrutiny",
    "future_residents": "Entirely dependent on engineer\u0027s professional integrity for their safety; no governmental protection",
    "local_government": "Implicitly negligent in failing to regulate; may face pressure to enact codes as a result of this case"
  },
  "proeth:activatesConstraint": [
    "Engineer_as_Last_Line_of_Defense_Constraint",
    "Public_Safety_Paramount_Constraint",
    "Independent_Professional_Judgment_Constraint"
  ],
  "proeth:causesStateChange": "Engineer A cannot defer to code compliance as a safety floor; professional judgment becomes the sole safeguard for public safety; Engineer A bears heightened ethical responsibility",
  "proeth:createsObligation": [
    "Obligation_to_Self_Impose_Appropriate_Safety_Standards",
    "Obligation_to_Advocate_for_Regulatory_Baseline",
    "Obligation_to_Protect_Future_Residents_Without_Regulatory_Backstop"
  ],
  "proeth:description": "The residential development site is located in a jurisdiction with no existing building codes governing storm surge or coastal construction standards, creating a regulatory vacuum that places full burden of safety determination on the engineer.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Pre-existing condition at the time Engineer A is retained",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "No Building Codes Exist"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Event_100-Year_Surge_Standard_Identified",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Once Engineer A\u0027s analysis produces the 100-year standard finding, is there any legitimate basis for revising that standard downward to accommodate client costs?",
    "How should engineers communicate technically derived safety thresholds to clients who lack technical expertise?",
    "At what point does a technical finding become an ethical commitment that cannot be negotiated away?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A may feel professional conviction but also anxiety about client reaction; Client A will likely feel financial alarm and resistance; future residents (unaware) would feel relief if they knew; observers recognize this as the pivotal technical moment of the case",
  "proeth-scenario:ethicalImplications": "Demonstrates the inseparability of technical judgment and ethical obligation; reveals how scientific rigor and professional integrity are mutually reinforcing; raises the question of whether safety standards should ever be subject to cost-benefit negotiation when public lives are at stake",
  "proeth-scenario:learningMoment": "Illustrates that technical findings can create ethical obligations that supersede client preferences; the moment of scientific determination is also an ethical turning point. Engineers must follow where the data leads, even when inconvenient.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "broader_profession": "This outcome demonstrates the real-world impact of applying updated scientific tools",
    "client_a": "Faces significantly higher construction costs; project economics may be threatened; feels engineer is being overly conservative",
    "engineer_a": "Now professionally and ethically bound to advocate for this standard; cannot in good conscience approve a lower specification; faces potential conflict with client",
    "future_residents": "Their safety depends on whether this finding is acted upon; they are the silent, unrepresented stakeholders most affected",
    "local_government": "Implicitly affected \u2014 this finding suggests existing (absent) codes are dangerously inadequate"
  },
  "proeth:activatesConstraint": [
    "Public_Safety_Paramount_Constraint",
    "Duty_to_Disclose_Safety_Findings_Constraint",
    "Honest_Communication_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/87#Action_Apply_Newly_Released_Algorithm_and_Data",
  "proeth:causesStateChange": "A specific, technically grounded safety threshold is established; Engineer A\u0027s professional judgment is now committed to this standard; the project\u0027s cost and feasibility calculus is fundamentally altered",
  "proeth:createsObligation": [
    "Obligation_to_Report_Findings_to_Client",
    "Obligation_to_Advocate_for_100_Year_Standard",
    "Obligation_to_Refuse_Designs_Below_This_Threshold"
  ],
  "proeth:description": "As a direct result of applying the new algorithm and historic weather data, Engineer A\u0027s analysis yields the finding that the development must be built to a 100-year projected storm surge elevation to meet public safety requirements \u2014 a standard higher than what the developer anticipated.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following application of the new algorithm; prior to presenting findings to Client A",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "100-Year Surge Standard Identified"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Event_Client_Refuses_Higher_Standard",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does a client\u0027s refusal to accept a safety recommendation change the engineer\u0027s ethical obligations, and if so, how?",
    "What options does Engineer A have at this point, and what are the ethical implications of each?",
    "Is it ever acceptable for an engineer to proceed with a project after a client rejects a safety-critical recommendation? Under what conditions, if any?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely feels frustrated, professionally threatened, and morally conflicted; Client A may feel justified in business terms but also defensive; future residents remain unaware of the decision being made on their behalf; observers in the profession recognize this as a classic ethics flashpoint",
  "proeth-scenario:ethicalImplications": "Epitomizes the fundamental tension in engineering ethics between loyalty to the client and duty to the public; reveals how market incentives can systematically underweight safety when costs are immediate and harms are probabilistic and diffuse; raises questions about the adequacy of voluntary professional ethics in the absence of regulatory backstops",
  "proeth-scenario:learningMoment": "This is the central ethical crisis of the case: the moment when client interest and public safety directly collide. Students should recognize that client refusal does not extinguish the engineer\u0027s safety obligations \u2014 it intensifies them.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "broader_public": "Demonstrates how private cost-benefit calculations can externalize safety risks onto vulnerable third parties",
    "client_a": "Saves construction costs in the short term but assumes significant legal, moral, and financial liability if harm results; may face reputational damage",
    "engineer_a": "Must now decide whether to continue advocating, withdraw, or escalate to authorities; professional integrity and license are implicated; potential loss of client and income",
    "future_residents": "Face elevated risk of harm from storm surge if the lower standard is built to; are entirely unrepresented in this negotiation",
    "local_government": "Absence of codes means no enforcement mechanism exists; this refusal would go unchallenged without engineer\u0027s further action"
  },
  "proeth:activatesConstraint": [
    "Public_Safety_Paramount_Constraint",
    "Conflict_with_Client_Constraint",
    "Engineer_Advocacy_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/87#Action_Present_Findings_to_Client",
  "proeth:causesStateChange": "Professional relationship enters adversarial tension; Engineer A can no longer proceed as if client and public interests are aligned; withdrawal and external advocacy become live ethical options",
  "proeth:createsObligation": [
    "Obligation_to_Continue_Advocating_for_Safety_Standard",
    "Obligation_to_Consider_Withdrawal_if_Advocacy_Fails",
    "Obligation_to_Consider_Government_Notification"
  ],
  "proeth:description": "After receiving Engineer A\u0027s findings and recommendation for the 100-year storm surge elevation standard, Client A refuses to incorporate it into the project due to the increased construction costs it would impose.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following Engineer A\u0027s presentation of findings to Client A",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Client Refuses Higher Standard"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Event_Public_Safety_Risk_Persists",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what point does a known, unmitigated public safety risk obligate an engineer to take action beyond the client relationship?",
    "How should engineers weigh the certainty of professional consequences (loss of client, income) against the probability of public harm?",
    "If Engineer A withdraws without notifying anyone, has the engineer fulfilled their ethical obligations? Why or why not?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A faces profound moral distress \u2014 the knowledge that people may be harmed if action is not taken; Client A may be insulated from this emotional weight by financial framing; future residents are entirely unaware of the risk they face; professional observers recognize this as the moment that defines Engineer A\u0027s ethical character",
  "proeth-scenario:ethicalImplications": "Reveals the deepest tension in professional engineering ethics: the engineer is simultaneously an agent of the client and a guardian of the public; demonstrates that public safety obligations are not merely aspirational but carry concrete duties of action; raises questions about collective responsibility when individual professional action is insufficient to address systemic risk",
  "proeth-scenario:learningMoment": "The persistence of public safety risk after client refusal is the ethical core of the case. Students must understand that the engineer\u0027s duty to the public does not dissolve when the client says no \u2014 it becomes more urgent. This event illustrates why engineering ethics codes place public safety above client loyalty.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "broader_profession": "This case becomes a precedent for how engineers should respond when clients reject safety-critical recommendations",
    "client_a": "May face catastrophic legal and financial liability if a storm surge event causes harm; short-term cost savings could result in enormous long-term losses",
    "engineer_a": "Faces the full weight of professional ethical obligation; inaction is itself an ethical choice with consequences; professional license and moral integrity are at stake",
    "future_residents": "Face potential loss of life, property, and community if a major storm event occurs and the development is inadequately protected",
    "local_government": "Bears indirect responsibility for the regulatory vacuum; may face political and legal consequences if harm results"
  },
  "proeth:activatesConstraint": [
    "Public_Safety_Paramount_Constraint",
    "Engineer_as_Last_Line_of_Defense_Constraint",
    "Duty_to_Protect_Third_Parties_Constraint"
  ],
  "proeth:causesStateChange": "The situation transforms from a professional disagreement into an active public safety risk; Engineer A\u0027s obligations shift from advisory to protective; third-party harm becomes a foreseeable consequence of inaction",
  "proeth:createsObligation": [
    "Obligation_to_Escalate_Advocacy",
    "Obligation_to_Withdraw_if_Advocacy_Fails",
    "Obligation_to_Notify_Authorities_if_Necessary",
    "Obligation_to_Not_Seal_Non_Compliant_Plans"
  ],
  "proeth:description": "As a consequence of Client A\u0027s refusal to adopt the 100-year surge standard, future residents of the development remain exposed to elevated storm surge risk that Engineer A\u0027s analysis has identified as a genuine public safety hazard.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Ongoing state following Client A\u0027s refusal; persists until resolved by advocacy, withdrawal, or regulatory action",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Public Safety Risk Persists"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#Event_Prior_BER_Cases_Contextualized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the existence of prior BER cases change the ethical analysis? Does it make Engineer A\u0027s obligations clearer or more constrained?",
    "Should professional ethics precedent be binding, persuasive, or merely informative for practicing engineers?",
    "What does the pattern across multiple BER cases tell us about the profession\u0027s collective values regarding public safety versus client loyalty?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Provides intellectual reassurance to Engineer A that their instincts align with established professional ethics; may feel validating or clarifying; for students, this moment provides a sense of grounding \u2014 the answer is not arbitrary but grounded in professional history",
  "proeth-scenario:ethicalImplications": "Illustrates that professional ethics has an institutional dimension beyond individual conscience; reveals how professional bodies shape ethical norms over time through case-by-case decisions; raises questions about the accessibility and awareness of ethics precedent among practicing engineers",
  "proeth-scenario:learningMoment": "Professional ethics is not invented anew in each situation; engineers can and should draw on established precedent and institutional guidance. The BER\u0027s prior decisions provide a framework for navigating novel situations by analogy.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_a": "Implicitly, the precedent suggests that client refusal has not historically been accepted as a justification for engineer inaction",
    "engineer_a": "Actions are now contextualized within a professional tradition; deviation from the prescribed course would be inconsistent with established ethics precedent",
    "profession": "Demonstrates the cumulative, precedent-building nature of professional ethics; shows that individual cases contribute to a living body of ethical guidance",
    "students": "Learn that engineering ethics is not purely situational but has institutional memory and developing jurisprudence"
  },
  "proeth:activatesConstraint": [
    "Professional_Precedent_Consistency_Constraint",
    "Established_Ethical_Standard_Constraint"
  ],
  "proeth:causesStateChange": "Engineer A\u0027s situation is framed within established professional ethics jurisprudence; the appropriate course of action is no longer novel or uncertain \u2014 it is grounded in precedent",
  "proeth:createsObligation": [
    "Obligation_to_Act_Consistently_with_Established_Professional_Ethics_Precedent"
  ],
  "proeth:description": "The Discussion section of the case references prior Board of Ethical Review decisions (Cases 04-8 and 07-6) involving environmental and public safety obligations, establishing that Engineer A\u0027s situation fits within a recognized pattern of professional ethical precedent.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Discussion/analysis phase; contextualizes the case retrospectively",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Prior BER Cases Contextualized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#CausalChain_b0cab828",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A voluntarily accepts retention by Client A to perform hydrodynamic modeling and coastal risk analysis, initiating the professional chain that leads to the technical determination",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A voluntarily enters professional relationship with Client A for hydrodynamic modeling",
      "proeth:element": "Accept Coastal Risk Engagement (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Newly developed algorithm incorporating historic weather data becomes available during or prior to engagement",
      "proeth:element": "New Algorithm Released (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A deliberately employs the new algorithm, elevating analytical accuracy beyond prior standards",
      "proeth:element": "Apply Newly Released Algorithm and Data (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Absence of regulatory baseline places full technical and ethical weight on Engineer A\u0027s professional determination",
      "proeth:element": "No Building Codes Exist (Event 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Analysis yields the 100-year storm surge elevation as the technically appropriate safety standard",
      "proeth:element": "100-Year Surge Standard Identified (Event 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Coastal Risk Engagement (Action 1)",
  "proeth:counterfactual": "Had Engineer A declined the engagement, no 100-year surge standard would have been identified for this project; the standard existed in nature but would have remained undiscovered in this context",
  "proeth:effect": "100-Year Surge Standard Identified (Event 3)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s voluntary acceptance of the engagement",
    "Engineer A\u0027s professional competence in hydrodynamic modeling",
    "Existence of the newly released algorithm and historic weather data",
    "Absence of existing building codes creating the need for independent technical determination"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Acceptance of engagement + application of new algorithm + professional analytical judgment = technical standard determination",
    "Without the engagement, no analysis would have been performed regardless of algorithm availability"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#CausalChain_fe084b1d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct result of applying the new algorithm and historic weather data, Engineer A\u0027s analysis yields the 100-year storm surge elevation as the technically appropriate safety standard",
  "proeth:causalSequence": [
    {
      "proeth:description": "External release of improved hydrodynamic modeling algorithm with historic weather data",
      "proeth:element": "New Algorithm Released (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A makes deliberate professional choice to employ the most current analytical tools",
      "proeth:element": "Apply Newly Released Algorithm and Data (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A exercises professional judgment to translate analytical output into a safety standard",
      "proeth:element": "Determine 100-Year Surge Standard (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The 100-year storm surge elevation is established as the technically appropriate standard for the project",
      "proeth:element": "100-Year Surge Standard Identified (Event 3)",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Apply Newly Released Algorithm and Data (Action 2)",
  "proeth:counterfactual": "Had Engineer A applied only previously available algorithms and data, the 100-year surge standard would likely not have been identified; a lower or less accurate standard may have been determined",
  "proeth:effect": "100-Year Surge Standard Identified (Event 3)",
  "proeth:necessaryFactors": [
    "Availability of the newly released algorithm (Event 1)",
    "Engineer A\u0027s deliberate decision to employ the new algorithm rather than legacy tools",
    "Incorporation of newly identified historic weather data",
    "Engineer A\u0027s professional competence to interpret results"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "New algorithm + historic weather data + professional application = identification of 100-year surge standard",
    "Legacy algorithms alone would have been insufficient to identify the updated standard"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#CausalChain_ab0f8c2c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After receiving Engineer A\u0027s findings and recommendation for the 100-year storm surge elevation standard, Client A refuses to adopt the higher safety standard",
  "proeth:causalSequence": [
    {
      "proeth:description": "Technical analysis establishes the safety standard that will be communicated to client",
      "proeth:element": "100-Year Surge Standard Identified (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A formally communicates the 100-year surge standard and its implications to Client A",
      "proeth:element": "Present Findings to Client (Action 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Absence of regulatory mandate leaves Client A legally free to reject the recommendation",
      "proeth:element": "No Building Codes Exist (Event 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Client A makes autonomous decision to reject the 100-year storm surge elevation standard",
      "proeth:element": "Client Refuses Higher Standard (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Future residents face elevated risk as a consequence of the refused safety standard",
      "proeth:element": "Public Safety Risk Persists (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Present Findings to Client (Action 4)",
  "proeth:counterfactual": "Had Engineer A not presented findings, no refusal would have occurred; had building codes mandated the standard, refusal would have been legally impossible",
  "proeth:effect": "Client Refuses Higher Standard (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s communication of the 100-year surge standard to Client A",
    "Client A\u0027s awareness that the standard would impose additional cost or design constraints",
    "Absence of regulatory compulsion (no building codes) allowing Client A to legally refuse",
    "Client A\u0027s independent volitional decision to prioritize other interests over the recommended standard"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Client A (primary); Engineer A (indirect, for initiating the decision point)",
  "proeth:sufficientFactors": [
    "Presentation of findings + Client A\u0027s cost-benefit calculus + absence of regulatory mandate = client refusal",
    "The refusal required both the presentation (triggering the decision point) and Client A\u0027s autonomous choice"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#CausalChain_ff310b8e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a consequence of Client A\u0027s refusal to adopt the 100-year surge standard, future residents of the development face persistent and unmitigated public safety risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client A rejects the 100-year surge elevation standard despite full knowledge of safety implications",
      "proeth:element": "Client Refuses Higher Standard (Event 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A is prescribed to continue advocacy, representing a potential intervention point",
      "proeth:element": "Continue Advocating Higher Safety Standard (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "If advocacy fails, Engineer A\u0027s withdrawal is prescribed as an ethical obligation, removing professional endorsement",
      "proeth:element": "Withdraw from Project (Action 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A is prescribed to consider systemic intervention through government channels to address the regulatory gap",
      "proeth:element": "Contact Government Officials for Code Advocacy (Action 7)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Without successful intervention at any prior step, future residents face unmitigated coastal storm surge risk",
      "proeth:element": "Public Safety Risk Persists (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Client Refuses Higher Standard (Event 4)",
  "proeth:counterfactual": "Had Client A accepted the 100-year standard, the public safety risk would have been substantially mitigated; had building codes existed, the risk would have been independently addressed regardless of client preference",
  "proeth:effect": "Public Safety Risk Persists (Event 5)",
  "proeth:necessaryFactors": [
    "Client A\u0027s refusal to adopt the 100-year surge standard",
    "Continuation of the development project at a lower safety elevation",
    "Absence of building codes that would have independently mandated the standard",
    "Future occupancy of the development by residents unaware of the elevated risk"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Client A (primary); Engineer A (indirect, for potential failure to withdraw or escalate)",
  "proeth:sufficientFactors": [
    "Refusal + continued development at lower standard + no regulatory backstop + future occupancy = persistent public safety risk",
    "Any one of the necessary factors being absent could have broken the causal chain"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/87#",
    "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/87#CausalChain_4391a00c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After Client A refuses to agree to the 100-year storm surge standard, Engineer A is prescribed to continue advocacy; if Client A continues to refuse after sustained advocacy, withdrawal and government contact are the prescribed ethical responses",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client A\u0027s refusal triggers Engineer A\u0027s ethical obligation to advocate beyond initial presentation",
      "proeth:element": "Client Refuses Higher Standard (Event 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A fulfills prescribed ethical duty to persistently advocate for the 100-year standard",
      "proeth:element": "Continue Advocating Higher Safety Standard (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Ongoing risk to future residents provides the ethical justification for escalated responses",
      "proeth:element": "Public Safety Risk Persists (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "If advocacy fails, Engineer A withdraws to avoid professional complicity in the safety risk",
      "proeth:element": "Withdraw from Project (Action 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A pursues systemic remedy by advocating for building codes to close the regulatory gap",
      "proeth:element": "Contact Government Officials for Code Advocacy (Action 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Continue Advocating Higher Safety Standard (Action 5)",
  "proeth:counterfactual": "Had Client A accepted the 100-year standard during advocacy, neither withdrawal nor government contact would have been ethically required; had building codes existed, the ethical burden on Engineer A would have been substantially reduced",
  "proeth:effect": "Withdraw from Project (Action 6) / Contact Government Officials for Code Advocacy (Action 7)",
  "proeth:necessaryFactors": [
    "Client A\u0027s sustained refusal following Engineer A\u0027s advocacy efforts",
    "Engineer A\u0027s professional ethical obligations under engineering codes of conduct",
    "Engineer A\u0027s knowledge that public safety risk persists without the higher standard",
    "The absence of any regulatory mechanism to independently enforce the standard"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (for fulfilling prescribed ethical obligations); Client A (for creating the conditions requiring escalation)",
  "proeth:sufficientFactors": [
    "Sustained client refusal + professional ethical obligations + public safety risk + no regulatory backstop = prescribed withdrawal and government contact",
    "If Client A had accepted the standard at any advocacy stage, withdrawal and government contact would not have been triggered"
  ],
  "proeth:withinAgentControl": true
}