Step 4: Full View

The Board's recommendation that Engineer A pursue persistent discussions with Client A before withdrawing does not require Engineer A to engage in indefinite or open-ended negotiation. The proportional escalation obligation is bounded by the point at which continued engagement becomes functional acquiescence to a design standard that Engineer A has already determined endangers life and property. Once Client A has explicitly and unambiguously refused the 100-year storm surge elevation standard on cost grounds, and once Engineer A has made a good-faith written effort to explain the public safety consequences of that refusal, the escalation obligation is satisfied. Continued discussion beyond that point risks creating the appearance that the safety standard is negotiable, which would itself undermine Engineer A's professional integrity and the clarity of the public safety message. The Board's two-step framework - persuade, then withdraw - should therefore be understood as a sequential and time-bounded process, not a license for indefinite deferral of withdrawal.

The Board's conclusion that Engineer A should withdraw if Client A refuses to accept the 100-year storm surge standard does not exhaust Engineer A's ethical obligations. Withdrawal removes Engineer A from complicity in an unsafe design but does not eliminate the foreseeable risk to future residents and the general public, who remain exposed to storm surge danger regardless of which engineer ultimately executes the project. In a jurisdiction with no building code, there is no regulatory mechanism that will independently capture or correct the identified deficiency after Engineer A's departure. Accordingly, Engineer A's post-withdrawal obligations extend to notifying appropriate local government officials or public authorities of the identified storm surge risk and the absence of any regulatory standard adequate to address it. This obligation is grounded in the public welfare paramount principle and is reinforced by the building code advocacy engineer principle, which encourages engineers to engage with public authorities to establish protective standards. Engineer A's duty to the public does not terminate at the boundary of the client relationship, and the residual risk to future residents constitutes a continuing professional responsibility that survives withdrawal from the project.

In response to Q101: Engineer A bears an affirmative obligation to notify local government officials or other relevant public authorities about the identified storm surge risk even after withdrawing from the project. The absence of a building code in the jurisdiction does not eliminate the foreseeable danger to future residents; it amplifies it. Code provision II.1.a makes clear that when an engineer's judgment is overruled under circumstances that endanger life or property, the engineer shall notify the proper authority. Withdrawal alone satisfies the negative duty not to participate in an unsafe design, but it does not discharge the positive duty to protect public welfare. Because no regulatory floor exists in this jurisdiction, Engineer A's notification to local government officials is the only remaining mechanism by which the identified risk can be surfaced to a body capable of acting on it. Silence after withdrawal, in a no-code jurisdiction where the developer may simply retain a less scrupulous engineer, leaves the public safety risk entirely unaddressed and is ethically insufficient.

Beyond the Board's recommendation that Engineer A continue to pursue discussions with Client A, Engineer A bears an affirmative obligation to document in writing the 100-year storm surge recommendation, the technical basis for that recommendation including the newly released algorithm and historic weather data, and Client A's explicit refusal on cost grounds. This written record serves two distinct functions: first, it fulfills Engineer A's faithful agent duty by formally notifying Client A that the project as currently scoped carries foreseeable risk to future residents and the general public; and second, it creates a contemporaneous professional record that may be essential if Engineer A is later called upon to demonstrate that the safety-critical recommendation was made and rejected. The absence of a local building code in the jurisdiction makes this documentation obligation more urgent, not less, because there is no regulatory paper trail that would otherwise capture the identified deficiency. Engineer A should provide this written notification to Client A before withdrawing from the project, and should retain copies as part of the professional record.

In response to Q102: Engineer A is obligated to document in writing the 100-year storm surge recommendation and Client A's explicit refusal. This obligation flows from multiple converging sources. First, code provision II.1.a requires that when an engineer's judgment is overruled under circumstances endangering life or property, the engineer shall notify the proper authority - a notification that is only credible and actionable if supported by a written record. Second, code provision III.1.b requires Engineer A to advise the client when a project will not be successful, and written documentation of that advice protects the integrity of that communication. Third, the Written Documentation Requirement for Safety Notification principle establishes that oral advocacy alone is insufficient when safety-critical recommendations are rejected. The documentation must be retained by Engineer A as a professional record, provided to Client A as formal notice of the safety concern and its rejection, and made available to any public authority to whom Engineer A subsequently discloses the risk. It should not be treated merely as a liability shield for Engineer A's professional standing; its primary ethical function is to create a durable, verifiable record of the safety risk that can inform regulatory or legal action.

The absence of a local building code in the project jurisdiction does not merely create a regulatory gap - it affirmatively expands Engineer A's independent professional duty to self-impose a technically defensible safety standard. Where a building code exists, an engineer's minimum obligation is compliance with that code, even if the engineer believes a higher standard is warranted. Where no code exists, the engineer's professional judgment is the only operative safety standard, and that judgment must be exercised with full application of available technical knowledge, including newly released algorithms and historic weather data. Client A's cost objection cannot function as a substitute for the absent regulatory floor. The Board's framework implicitly recognizes this dynamic by treating Engineer A's 100-year storm surge recommendation not as a discretionary preference but as a professional obligation grounded in public safety. This obligation persists regardless of cost constraints and is not diminished by the fact that a lower standard might have been acceptable in a jurisdiction with a more permissive building code.

In response to Q103: The absence of a local building code materially expands Engineer A's independent professional duty to self-impose a safety standard. Where a regulatory floor exists, an engineer can at minimum point to codified requirements as a baseline, even if personally recommending a higher standard. In a no-code jurisdiction, the engineer's professional judgment is the only operative safety standard in the design process. This places the full weight of public safety determination on Engineer A's expertise, making the self-imposed standard not merely aspirational but ethically mandatory. Client A's cost objections do not diminish this duty; the Public Welfare Paramount principle and the constraint that public safety is not subordinate to client cost preference together establish that economic considerations cannot override a safety-critical technical determination. Furthermore, this duty persists regardless of cost objections because the harm at stake - storm surge danger to future residents and the general public - is foreseeable, serious, and irreversible in the event of a major storm event. The no-code context therefore heightens rather than relaxes Engineer A's obligation to hold the 100-year storm surge standard as a non-negotiable professional floor.

The tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle was resolved in this case through a clear lexical ordering: Engineer A's duty to serve Client A's interests is bounded by, and ultimately subordinate to, the obligation to hold public safety paramount. The Board's conclusions confirm that Engineer A must first attempt persuasion - satisfying the faithful agent duty by fully informing Client A of the risk and its consequences - but when Client A's cost-driven refusal persists, the public welfare obligation overrides client loyalty and compels withdrawal. This resolution teaches that client service is not an independent ethical value in engineering; it is a conditional obligation that operates only within the space permitted by public safety. The moment client direction would require Engineer A to acquiesce to a design standard that exposes future residents to foreseeable storm surge danger, the faithful agent role collapses into the public welfare role, and the latter governs. Notably, the absence of a local building code does not relax this hierarchy - it intensifies it, because Engineer A's independent professional judgment becomes the only operative safety standard in the jurisdiction.

The Board's conclusion that Engineer A should withdraw if Client A refuses to accept the 100-year storm surge standard does not exhaust Engineer A's ethical obligations. Withdrawal removes Engineer A from complicity in an unsafe design but does not eliminate the foreseeable risk to future residents and the general public, who remain exposed to storm surge danger regardless of which engineer ultimately executes the project. In a jurisdiction with no building code, there is no regulatory mechanism that will independently capture or correct the identified deficiency after Engineer A's departure. Accordingly, Engineer A's post-withdrawal obligations extend to notifying appropriate local government officials or public authorities of the identified storm surge risk and the absence of any regulatory standard adequate to address it. This obligation is grounded in the public welfare paramount principle and is reinforced by the building code advocacy engineer principle, which encourages engineers to engage with public authorities to establish protective standards. Engineer A's duty to the public does not terminate at the boundary of the client relationship, and the residual risk to future residents constitutes a continuing professional responsibility that survives withdrawal from the project.

From a consequentialist perspective, the Board's recommendation that Engineer A withdraw if Client A refuses the 100-year storm surge standard requires supplementary analysis to avoid a potentially counterproductive outcome. If Engineer A withdraws and a replacement engineer with fewer safety commitments accepts the engagement and designs to a lower storm surge elevation, the net effect on future residents may be worse than if Engineer A had remained engaged and continued to advocate for the higher standard from within the project. This replacement engineer risk does not, however, override the deontological obligation to withdraw - Engineer A cannot ethically lend professional credentials to a design that Engineer A has determined endangers life and property. But it does reinforce the importance of the post-withdrawal obligations identified above: Engineer A's notification to public authorities and advocacy for a protective building code are not merely optional extensions of professional responsibility but are the consequentialist mechanism by which withdrawal produces better rather than worse outcomes for the public. Withdrawal without post-withdrawal public disclosure may protect Engineer A's professional integrity while leaving the underlying public safety risk entirely unaddressed.

In response to Q104: Engineer A does bear residual ethical responsibility for harm to future residents if Engineer A withdraws from the project but takes no further action to alert public authorities or advocate for protective building codes. Withdrawal is a necessary but not sufficient ethical response once Client A refuses the safety-critical recommendation. The Board's conclusion that Engineer A should withdraw if Client A refuses is correct as far as it goes, but it does not exhaust Engineer A's obligations. Code provision II.1.a explicitly contemplates post-overruling notification to proper authorities, and the Building Code Advocacy Engineer Principle and Post-Client-Refusal Escalation Assessment Obligation together establish that Engineer A's professional duty extends beyond the client relationship into the broader public sphere. In a no-code jurisdiction, where no regulatory body will independently discover the risk, Engineer A's silence after withdrawal is functionally equivalent to acquiescence in the unsafe outcome. The residual responsibility is not unlimited - Engineer A cannot compel the developer or the jurisdiction to act - but it does require Engineer A to take affirmative steps to surface the risk to those with authority to address it.

In response to Q201: The Faithful Agent Notification Obligation and the Public Welfare Paramount principle do not fundamentally conflict in this case - they operate in sequence rather than in opposition, but Public Welfare Paramount takes lexical priority when they diverge. Engineer A's duty as a faithful agent requires notifying Client A of the storm surge risk and the likelihood that a lower design standard will expose the project and its future residents to foreseeable danger. This notification duty is fully compatible with public welfare protection so long as Client A accepts the recommendation. The conflict arises only when Client A refuses: at that point, continuing to serve the client's cost preference would require Engineer A to subordinate public safety to client interest, which the NSPE Code does not permit. Code provision II.1. establishes that public safety is paramount, and the Client Loyalty Obligation of Engineer A is explicitly bounded by public safety. The faithful agent role therefore terminates at the boundary of ethical permissibility - Engineer A cannot be a faithful agent to a client directive that endangers the public.

The tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle was resolved in this case through a clear lexical ordering: Engineer A's duty to serve Client A's interests is bounded by, and ultimately subordinate to, the obligation to hold public safety paramount. The Board's conclusions confirm that Engineer A must first attempt persuasion - satisfying the faithful agent duty by fully informing Client A of the risk and its consequences - but when Client A's cost-driven refusal persists, the public welfare obligation overrides client loyalty and compels withdrawal. This resolution teaches that client service is not an independent ethical value in engineering; it is a conditional obligation that operates only within the space permitted by public safety. The moment client direction would require Engineer A to acquiesce to a design standard that exposes future residents to foreseeable storm surge danger, the faithful agent role collapses into the public welfare role, and the latter governs. Notably, the absence of a local building code does not relax this hierarchy - it intensifies it, because Engineer A's independent professional judgment becomes the only operative safety standard in the jurisdiction.

Beyond the Board's recommendation that Engineer A continue to pursue discussions with Client A, Engineer A bears an affirmative obligation to document in writing the 100-year storm surge recommendation, the technical basis for that recommendation including the newly released algorithm and historic weather data, and Client A's explicit refusal on cost grounds. This written record serves two distinct functions: first, it fulfills Engineer A's faithful agent duty by formally notifying Client A that the project as currently scoped carries foreseeable risk to future residents and the general public; and second, it creates a contemporaneous professional record that may be essential if Engineer A is later called upon to demonstrate that the safety-critical recommendation was made and rejected. The absence of a local building code in the jurisdiction makes this documentation obligation more urgent, not less, because there is no regulatory paper trail that would otherwise capture the identified deficiency. Engineer A should provide this written notification to Client A before withdrawing from the project, and should retain copies as part of the professional record.

The Board's conclusions do not address the epistemic dimension of Engineer A's recommendation, specifically the tension between the professional obligation to render a definitive and defensible safety standard and the inherent uncertainty in climate projections derived from newly released algorithms and recently identified historic weather data. Engineer A's reliance on newly released tools is itself an expression of the professional competence obligation - engineers must apply the best available technical knowledge, not merely established consensus methods. However, professional integrity also requires that Engineer A qualify the recommendation appropriately: the 100-year storm surge standard should be presented as the technically defensible minimum given current best-available data, with explicit acknowledgment that evolving climate baselines may require future reassessment. This qualification does not weaken the recommendation or provide Client A with grounds to reject it on grounds of uncertainty; rather, it demonstrates the epistemic honesty that distinguishes a professionally credible safety recommendation from an overconfident assertion. The qualification also reinforces the case for building to the higher standard, since uncertainty in climate projections generally argues for greater rather than lesser conservatism in safety-critical infrastructure design.

In response to Q202: The Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle are in genuine tension, but that tension does not license indefinite hedging. Engineer A is correct to acknowledge that climate projections carry inherent uncertainty and that the baseline for storm surge risk may shift over time. However, professional competence requires that Engineer A render a definitive and defensible recommendation based on the best available data at the time of the assessment - in this case, the newly released algorithm and historic weather data. Epistemic humility does not mean refusing to commit to a standard; it means selecting the most protective standard that the current evidence supports and disclosing the uncertainty range transparently. The 100-year storm surge elevation standard represents Engineer A's best professional judgment given available tools, and that judgment must be stated clearly enough to be actionable. Qualifying the recommendation to the point of ambiguity would undermine its protective function and would itself constitute a failure of professional competence. Engineer A should state the recommendation definitively while noting that the standard may need to be revisited as climate data evolves.

The interaction between the Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle reveals an important synthesis: epistemic uncertainty about future climate baselines does not diminish Engineer A's obligation to render a definitive and defensible safety recommendation - it actually strengthens the case for adopting the more protective standard. When the technical baseline is inherently uncertain and evolving, a competent professional does not hedge toward the lower bound of risk; rather, professional competence in a no-code jurisdiction requires Engineer A to apply the best available tools - here, the newly released algorithm and historic weather data - and recommend the standard that accounts for the upper plausible range of foreseeable harm. The availability of superior technical tools creates a heightened professional duty, because Engineer A can no longer claim ignorance of the more protective standard. At the same time, the moving-target nature of climate data requires Engineer A to qualify the recommendation transparently - not to weaken it, but to explain its basis and acknowledge that future data may require design revision. This synthesis teaches that professional competence and epistemic humility are not in conflict: a competent engineer discloses uncertainty while still committing to the most defensible protective standard available at the time of the assessment. The Building Code Advocacy Engineer Principle further extends this synthesis: because the climate baseline will continue to evolve, Engineer A's obligation to advocate for a local building code incorporating the 100-year standard is not merely a post-withdrawal courtesy but a forward-looking professional responsibility to ensure that the jurisdiction's regulatory framework keeps pace with improving climate science.

The Board's recommendation that Engineer A pursue persistent discussions with Client A before withdrawing does not require Engineer A to engage in indefinite or open-ended negotiation. The proportional escalation obligation is bounded by the point at which continued engagement becomes functional acquiescence to a design standard that Engineer A has already determined endangers life and property. Once Client A has explicitly and unambiguously refused the 100-year storm surge elevation standard on cost grounds, and once Engineer A has made a good-faith written effort to explain the public safety consequences of that refusal, the escalation obligation is satisfied. Continued discussion beyond that point risks creating the appearance that the safety standard is negotiable, which would itself undermine Engineer A's professional integrity and the clarity of the public safety message. The Board's two-step framework - persuade, then withdraw - should therefore be understood as a sequential and time-bounded process, not a license for indefinite deferral of withdrawal.

In response to Q203: The Proportional Escalation Obligation and the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle are in tension, but the resolution depends on the nature and clarity of Client A's refusal. Proportional escalation - attempting to persuade, documenting the disagreement, and escalating through available channels before withdrawing - is the appropriate framework when a client's position is ambiguous, negotiable, or based on incomplete information. However, when Client A has made an explicit, cost-driven refusal of a safety-critical standard, continued engagement that delays withdrawal risks becoming a form of tacit acquiescence. The Board's recommendation that Engineer A continue to pursue discussions is appropriate only if those discussions are genuinely aimed at changing Client A's position, not at finding a compromise that falls below the safety threshold. If Client A's refusal is unequivocal and no further persuasion is plausible, the Non-Acquiescence principle demands that Engineer A not continue to participate in a design process that will produce an unsafe outcome. The escalation obligation does not require Engineer A to exhaust every conceivable avenue before withdrawing; it requires that withdrawal be preceded by a good-faith effort to resolve the disagreement through professional persuasion.

The tension between the Proportional Escalation Obligation - which calls for graduated steps before withdrawal - and the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle was resolved in this case by treating them as sequentially compatible rather than genuinely conflicting. The Board's recommendation that Engineer A continue to pursue discussions before withdrawing reflects the proportional escalation logic: withdrawal is the terminal step in a graduated response, not the first. However, this sequential compatibility has a critical limit. Once Client A has explicitly and finally refused the 100-year storm surge standard on cost grounds, continued discussion that merely delays withdrawal without any realistic prospect of changing the client's position would itself become ethically problematic - it would allow Engineer A to remain nominally engaged with a project whose safety standard Engineer A has already determined to be inadequate. The non-acquiescence principle therefore functions as a ceiling on how long proportional escalation may continue: Engineer A may pursue persuasion, but may not use the escalation framework as a pretext for indefinite engagement with a project that endangers the public. This case teaches that proportional escalation is a procedural obligation, not a substantive one - it governs the sequence of Engineer A's response but does not alter the ultimate outcome once client refusal is confirmed.

In response to Q204: The Building Code Advocacy Engineer Principle and the Regulatory Gap Awareness and Proactive Risk Disclosure principle are not fundamentally in conflict regarding timing, but they operate on different tracks. Proactive risk disclosure to public authorities is triggered by the identification of a foreseeable public safety risk that cannot be adequately addressed through the client relationship - a trigger that may be reached before withdrawal if Client A's refusal is clear and the risk is serious. Building code advocacy, by contrast, is a longer-horizon obligation that involves engaging local government to establish systemic protective standards and is appropriately pursued both during and after the client engagement. The disclosure duty is narrower and more urgent: it requires Engineer A to surface the specific identified risk to authorities capable of acting on it. The advocacy duty is broader and more structural: it requires Engineer A to work toward closing the regulatory gap that allowed the risk to go unaddressed in the first place. These duties are complementary rather than conflicting, and both are activated by the combination of a no-code jurisdiction, a foreseeable public safety risk, and a client's refusal to adopt the recommended protective standard.

In response to Q301: From a deontological perspective, Engineer A's duty to hold public safety paramount does create a near-absolute obligation to withdraw once Client A explicitly refuses the 100-year storm surge elevation standard, but the deontological analysis does not end there. Withdrawal is obligatory because continuing to participate in the design of a structure that Engineer A knows to be unsafe would make Engineer A complicit in a foreseeable harm to future residents - a violation of the categorical duty not to use persons merely as means. However, the deontological framework also imposes a positive duty of beneficence toward those future residents, which withdrawal alone does not satisfy. The duty to withdraw is therefore necessary but not sufficient: it must be accompanied by the affirmative duty to notify proper authorities, as specified in code provision II.1.a. The fact that withdrawal may not actually prevent harm - because another engineer may replace Engineer A - does not diminish the deontological obligation to withdraw; acting from duty is not contingent on producing the desired outcome. But it does reinforce the importance of the notification duty as the mechanism through which Engineer A's moral agency extends beyond the client relationship.

From a consequentialist perspective, the Board's recommendation that Engineer A withdraw if Client A refuses the 100-year storm surge standard requires supplementary analysis to avoid a potentially counterproductive outcome. If Engineer A withdraws and a replacement engineer with fewer safety commitments accepts the engagement and designs to a lower storm surge elevation, the net effect on future residents may be worse than if Engineer A had remained engaged and continued to advocate for the higher standard from within the project. This replacement engineer risk does not, however, override the deontological obligation to withdraw - Engineer A cannot ethically lend professional credentials to a design that Engineer A has determined endangers life and property. But it does reinforce the importance of the post-withdrawal obligations identified above: Engineer A's notification to public authorities and advocacy for a protective building code are not merely optional extensions of professional responsibility but are the consequentialist mechanism by which withdrawal produces better rather than worse outcomes for the public. Withdrawal without post-withdrawal public disclosure may protect Engineer A's professional integrity while leaving the underlying public safety risk entirely unaddressed.

In response to Q302: From a consequentialist perspective, the question of whether withdrawal produces better outcomes than remaining engaged is genuinely difficult, but the analysis ultimately supports withdrawal as the ethically superior choice under the specific conditions of this case. The argument for remaining engaged - that Engineer A might influence the design from within - is plausible only if Client A's refusal is soft and subject to ongoing persuasion. If Client A's refusal is firm, remaining engaged produces no safety benefit and instead lends Engineer A's professional credibility to an unsafe design. The replacement engineer scenario - where a less scrupulous engineer simply adopts the lower standard - is a real consequentialist concern, but it does not justify Engineer A's continued participation in an unsafe project. The better consequentialist response to the replacement risk is not to remain on the project but to pursue the post-withdrawal notification and advocacy obligations that can alert public authorities to the risk regardless of who ultimately designs the structure. Withdrawal combined with proactive disclosure to local government officials produces better expected outcomes than continued engagement without client agreement on the safety standard.

The Board's conclusions do not address the epistemic dimension of Engineer A's recommendation, specifically the tension between the professional obligation to render a definitive and defensible safety standard and the inherent uncertainty in climate projections derived from newly released algorithms and recently identified historic weather data. Engineer A's reliance on newly released tools is itself an expression of the professional competence obligation - engineers must apply the best available technical knowledge, not merely established consensus methods. However, professional integrity also requires that Engineer A qualify the recommendation appropriately: the 100-year storm surge standard should be presented as the technically defensible minimum given current best-available data, with explicit acknowledgment that evolving climate baselines may require future reassessment. This qualification does not weaken the recommendation or provide Client A with grounds to reject it on grounds of uncertainty; rather, it demonstrates the epistemic honesty that distinguishes a professionally credible safety recommendation from an overconfident assertion. The qualification also reinforces the case for building to the higher standard, since uncertainty in climate projections generally argues for greater rather than lesser conservatism in safety-critical infrastructure design.

In response to Q303: From a virtue ethics perspective, Engineer A demonstrates genuine professional integrity by applying the newly released algorithm and historic weather data to recommend the 100-year storm surge standard, but epistemic humility requires that the recommendation be accompanied by a transparent disclosure of the uncertainty inherent in climate projections - not as a qualification that weakens the recommendation, but as a demonstration of intellectual honesty that strengthens it. A virtuous engineer does not suppress uncertainty to make a recommendation appear more authoritative than the evidence warrants; nor does the virtuous engineer use uncertainty as a reason to avoid making a definitive professional judgment. The virtue of practical wisdom - phronesis - requires Engineer A to calibrate the recommendation to the best available evidence, state it clearly and confidently, and acknowledge the evolving nature of the climate baseline in a way that informs rather than undermines the client's decision-making. Recommending the 100-year standard on the basis of the best current tools, while noting that the standard may need to be revisited as data improves, reflects the kind of honest, competent, and courageous professional conduct that virtue ethics demands.

The interaction between the Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle reveals an important synthesis: epistemic uncertainty about future climate baselines does not diminish Engineer A's obligation to render a definitive and defensible safety recommendation - it actually strengthens the case for adopting the more protective standard. When the technical baseline is inherently uncertain and evolving, a competent professional does not hedge toward the lower bound of risk; rather, professional competence in a no-code jurisdiction requires Engineer A to apply the best available tools - here, the newly released algorithm and historic weather data - and recommend the standard that accounts for the upper plausible range of foreseeable harm. The availability of superior technical tools creates a heightened professional duty, because Engineer A can no longer claim ignorance of the more protective standard. At the same time, the moving-target nature of climate data requires Engineer A to qualify the recommendation transparently - not to weaken it, but to explain its basis and acknowledge that future data may require design revision. This synthesis teaches that professional competence and epistemic humility are not in conflict: a competent engineer discloses uncertainty while still committing to the most defensible protective standard available at the time of the assessment. The Building Code Advocacy Engineer Principle further extends this synthesis: because the climate baseline will continue to evolve, Engineer A's obligation to advocate for a local building code incorporating the 100-year standard is not merely a post-withdrawal courtesy but a forward-looking professional responsibility to ensure that the jurisdiction's regulatory framework keeps pace with improving climate science.

In response to Q304: From a deontological perspective, Engineer A's duty as a faithful agent to Client A and the duty to hold public safety paramount do conflict when Client A's cost-driven refusal creates foreseeable risk to future residents, and public safety takes unambiguous lexical priority. The faithful agent duty - including the obligation under code provision III.1.b to notify the client when a project will not be successful - is a genuine professional obligation, but it is explicitly bounded by the public safety paramount principle established in code provision II.1. The NSPE Code does not treat these duties as equally weighted and subject to balancing; it establishes a clear hierarchy in which public safety is paramount. This means that when the two duties conflict, Engineer A cannot satisfy the faithful agent obligation by continuing to serve Client A's cost preference at the expense of public safety. The faithful agent duty is fully discharged when Engineer A provides Client A with a clear, written notification of the safety risk and the consequences of refusing the recommended standard - after which the public safety duty takes over and requires Engineer A to withdraw and notify appropriate authorities.

The tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle was resolved in this case through a clear lexical ordering: Engineer A's duty to serve Client A's interests is bounded by, and ultimately subordinate to, the obligation to hold public safety paramount. The Board's conclusions confirm that Engineer A must first attempt persuasion - satisfying the faithful agent duty by fully informing Client A of the risk and its consequences - but when Client A's cost-driven refusal persists, the public welfare obligation overrides client loyalty and compels withdrawal. This resolution teaches that client service is not an independent ethical value in engineering; it is a conditional obligation that operates only within the space permitted by public safety. The moment client direction would require Engineer A to acquiesce to a design standard that exposes future residents to foreseeable storm surge danger, the faithful agent role collapses into the public welfare role, and the latter governs. Notably, the absence of a local building code does not relax this hierarchy - it intensifies it, because Engineer A's independent professional judgment becomes the only operative safety standard in the jurisdiction.

The absence of a local building code in the project jurisdiction does not merely create a regulatory gap - it affirmatively expands Engineer A's independent professional duty to self-impose a technically defensible safety standard. Where a building code exists, an engineer's minimum obligation is compliance with that code, even if the engineer believes a higher standard is warranted. Where no code exists, the engineer's professional judgment is the only operative safety standard, and that judgment must be exercised with full application of available technical knowledge, including newly released algorithms and historic weather data. Client A's cost objection cannot function as a substitute for the absent regulatory floor. The Board's framework implicitly recognizes this dynamic by treating Engineer A's 100-year storm surge recommendation not as a discretionary preference but as a professional obligation grounded in public safety. This obligation persists regardless of cost constraints and is not diminished by the fact that a lower standard might have been acceptable in a jurisdiction with a more permissive building code.

In response to Q401: If the jurisdiction had an existing building code mandating a lower storm surge elevation standard, Engineer A would still be ethically obligated to recommend the 100-year projection if professional judgment - supported by the best available data - indicated that the code-mandated standard was technically insufficient to protect public safety. Code provision II.1.b requires engineers to approve only those engineering documents in conformity with applicable standards, but it does not limit Engineer A's professional duty to recommend a higher standard when the applicable code is inadequate. Legal compliance provides a legal safe harbor but not an ethical one: an engineer who knows that a code-compliant design will expose future residents to foreseeable danger cannot discharge the public safety obligation merely by pointing to the code. However, the ethical calculus for withdrawal would change in a coded jurisdiction: Engineer A could not refuse to certify a code-compliant design on safety grounds alone without a stronger evidentiary basis that the code itself was deficient, and the appropriate response might shift toward formal advocacy for code revision rather than project withdrawal. The no-code jurisdiction in the present case removes this complication and places the full weight of the safety determination on Engineer A's professional judgment.

In response to Q402: Proactive contact with local government officials before presenting findings to Client A would likely have produced better outcomes for future residents than treating advocacy as a post-withdrawal obligation. If Engineer A had engaged local government at the outset - alerting officials to the identified storm surge risk and the absence of a protective building code - the jurisdiction might have initiated a code development process that would have established a regulatory floor independent of Client A's cost preferences. This would have changed the negotiating dynamic: Client A would have faced not only Engineer A's professional recommendation but also the prospect of an emerging regulatory requirement. However, this sequencing raises its own ethical complexity: Engineer A's primary engagement is with Client A, and disclosing project-specific findings to public authorities before informing the client could be seen as a breach of the faithful agent obligation. The more defensible approach is for Engineer A to raise the regulatory gap issue with local government in general terms - advocating for a building code that addresses storm surge risk in the jurisdiction - without disclosing Client A's project-specific information before the client relationship has broken down. Post-withdrawal, the disclosure obligation becomes more direct and project-specific.

In response to Q403: Written documentation of the safety recommendation and Client A's refusal, provided at the outset of the disagreement rather than only during ongoing discussions, would likely have served a dual function: it would have created a formal record that could influence Client A's decision-making by making the professional stakes of the refusal explicit, and it would have protected Engineer A's professional standing. However, the evidence suggests that Client A's refusal is cost-driven and firm, which means the written record's primary practical effect would be protective of Engineer A rather than persuasive to Client A. This does not diminish the obligation to document: the Written Documentation Requirement for Safety Notification principle establishes that documentation is required regardless of its persuasive effect, because its function extends beyond the client relationship to the broader public safety record. The written record is the instrument through which Engineer A's professional judgment becomes available to public authorities, future investigators, and regulatory bodies. Its value is not exhausted by its effect on Client A's decision, and the underlying public safety risk remains unresolved regardless of whether Client A is persuaded - which is precisely why the post-withdrawal notification obligation to public authorities is independently required.

In response to Q404: The availability of the newly released algorithm and historic weather data does create a heightened professional duty that did not previously exist to the same degree, and the ethical obligation to recommend the 100-year storm surge standard is correspondingly stronger than it would have been under previously established climate models alone. Professional competence requires engineers to apply the best available tools and data to their assessments; when superior technical tools become available, the standard of care rises accordingly. If Engineer A had relied only on older climate models that did not support the 100-year projection, the obligation to recommend that specific standard would have been weaker - though the obligation to recommend the most protective standard supported by available evidence would have remained. The newly released algorithm does not create the ethical obligation from scratch; it provides the technical basis for a more specific and more demanding recommendation. This also means that Engineer A's obligation to stay current with technical literature and newly released tools is itself an ethical obligation, not merely a professional development aspiration: failing to apply available superior tools when assessing a safety-critical design would itself constitute a failure of professional competence under the circumstances of this case.

The interaction between the Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle reveals an important synthesis: epistemic uncertainty about future climate baselines does not diminish Engineer A's obligation to render a definitive and defensible safety recommendation - it actually strengthens the case for adopting the more protective standard. When the technical baseline is inherently uncertain and evolving, a competent professional does not hedge toward the lower bound of risk; rather, professional competence in a no-code jurisdiction requires Engineer A to apply the best available tools - here, the newly released algorithm and historic weather data - and recommend the standard that accounts for the upper plausible range of foreseeable harm. The availability of superior technical tools creates a heightened professional duty, because Engineer A can no longer claim ignorance of the more protective standard. At the same time, the moving-target nature of climate data requires Engineer A to qualify the recommendation transparently - not to weaken it, but to explain its basis and acknowledge that future data may require design revision. This synthesis teaches that professional competence and epistemic humility are not in conflict: a competent engineer discloses uncertainty while still committing to the most defensible protective standard available at the time of the assessment. The Building Code Advocacy Engineer Principle further extends this synthesis: because the climate baseline will continue to evolve, Engineer A's obligation to advocate for a local building code incorporating the 100-year standard is not merely a post-withdrawal courtesy but a forward-looking professional responsibility to ensure that the jurisdiction's regulatory framework keeps pace with improving climate science.