Step 4: Review

Hold paramount the safety, health, and welfare of the public.

Issue public statements only in an objective and truthful manner.

Avoid deceptive acts.

Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise.

Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required.

Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.

Engineers shall advise their clients or employers when they believe a project will not be successful.

Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.

Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers. Engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action.

The Board cited this case to show a prior ruling where the Canons and Rules did not apply to an engineering firm providing sub-professional services, then distinguished it by noting the Code has since been revised and that Firm DBA has licensed PEs in supervisory and ownership roles.

The Board cited this case to support the principle that the NSPE Code applies universally to all members regardless of circumstance, analogizing that just as geography does not exempt members from the Code, the type of services provided should not either.

The Board cited this case to establish that engineers have a duty to hold paramount the safety, health, and welfare of the public, and that failing to act when aware of a problem violates that duty, analogizing Engineer M's obligations to those of Engineer A.

The Board cited this case to support the principle that when an engineer becomes aware of potential ethical or licensure violations by another firm, the engineer has an obligation to communicate with that firm and, if unsatisfied, may need to report the matter to the state engineering licensure board.

The Board cited this case to support the principle that a registered professional engineer is obligated to include all relevant and pertinent information in a report, and that omitting such information prevents stakeholders from making informed decisions and fails to protect public safety, health, and welfare.

The actions of Firm DBA are not ethical under the Code as the services provided were under the supervision and ownership of licensed professional engineers.

Beyond the Board's finding that Firm DBA's actions are unethical because its services were conducted under the supervision and ownership of licensed professional engineers, the ethical violation is compounded by the structural design of Firm DBA's public engagement process itself. The assignment of public outreach to a communications and public relations department does not insulate the licensed professional engineers in supervisory and ownership roles from ethical accountability. Because those licensed PEs retained responsible charge over all departments - including the communications department - they bore an affirmative duty to ensure that the public engagement process met the standards of objectivity, truthfulness, and completeness required by the Code. The rationalization that the sessions were consistent with prior City projects does not satisfy that duty; prior practice cannot establish an ethical baseline when that practice systematically excluded a historically underserved community. The licensed PEs' failure to independently evaluate whether the engagement design met professional standards - rather than deferring to City direction and institutional precedent - constitutes a failure of the professional judgment the Code requires.

The Board's conclusion that Firm DBA's actions are unethical does not fully address the independent ethical culpability of the City as a directing party. The City's explicit instruction to Firm DBA to conduct public engagement sessions in a manner that foreseeably excluded Community P residents - citing economic, political, and social considerations - does not constitute a legitimate client directive that engineers are obligated to follow. Client authority under the Code extends only to lawful and professionally appropriate direction; it does not extend to directing engineers to deceive the public or to suppress community input in a way that misrepresents the basis for a major infrastructure decision. The City's direction, if accurately characterized by Firm DBA, transforms the City from a client exercising legitimate authority into a party directing a deceptive act. This implicates Engineer M's obligations as lead engineer: Engineer M cannot treat the City's instruction as a complete defense for Firm DBA's conduct, nor can Engineer M continue to serve the City's interest in advancing the project on the basis of a fraudulent public engagement record without independently violating the obligation to hold paramount the safety, health, and welfare of the public - including the residents of Community P.

The Board's finding that Firm DBA's actions are unethical has direct downstream consequences for Engineer M's own ethical standing that the Board's explicit conclusions do not fully resolve. Engineer M's obligation to hold paramount the safety, health, and welfare of the public - and to avoid association with deceptive enterprises - requires a graduated but time-sensitive escalation response. Having raised concerns to Firm DBA and received a dismissal grounded in client direction rather than professional justification, Engineer M's next obligation is to escalate formally to the City, advising the City that the public engagement report does not accurately represent the conditions under which sessions were held and that the project, if advanced on the basis of that report, will not succeed in satisfying the professional and public welfare standards the engagement process was designed to serve. If the City declines to correct the record, Engineer M's obligation to report known Code violations to appropriate authorities - including the state engineering licensure board - is triggered. Continued association with the project after exhausting these escalation pathways without correction would risk Engineer M's own ethical compliance, because the project would then be proceeding on a fraudulent evidentiary basis with Engineer M's implicit professional endorsement as lead engineer. Disassociation, while not the first required step, becomes an ethical obligation if escalation fails and the fraudulent record is allowed to stand uncorrected.

In response to Q101: The City's explicit instruction to Firm DBA to conduct public engagement sessions in an inequitable manner does implicate the City in an ethical violation, but that implication does not transfer or dilute Engineer M's independent obligations. Engineer M, as lead engineer retained directly by the City, holds a paramount duty to the public welfare that is not subordinate to client authority. When a client directive foreseeably channels harm toward a historically underserved community by suppressing that community's meaningful participation in a decision that will materially affect their homes, businesses, and neighborhood, compliance with that directive is not a legitimate exercise of serving client interests - it is a facilitation of public harm. The Code's instruction to serve the legitimate interests of clients does not extend to instructions that are themselves illegitimate by virtue of their foreseeable inequitable impact. Engineer M therefore had an obligation not merely to raise concerns with Firm DBA but to refuse to allow the project to proceed on the basis of a fraudulent engagement record, and to advise the City directly that the engagement process as directed could not produce a report Engineer M could professionally endorse.

In response to Q102: Engineer M's continued association with the project after Firm DBA dismissed concerns and submitted the misleading report crosses a meaningful ethical threshold. The Code's prohibition on associating in business ventures with persons engaged in fraudulent or dishonest practice is not satisfied by a prior verbal objection that was overruled. Once Firm DBA submitted a report that Engineer M recognized as materially misrepresentative - omitting session locations, times, and the absence of written comment mechanisms, while affirmatively claiming Community P support - Engineer M's continued role as lead engineer lent professional credibility to a project record that Engineer M knew to be fraudulent. Continued association at that point constitutes a form of implicit endorsement. However, disassociation alone would not fully satisfy Engineer M's obligations, because withdrawal without disclosure would leave Community P without any professional advocate capable of challenging the fraudulent record in the public process. The ethical path therefore required Engineer M to escalate formally to the City before considering disassociation, and to document that escalation in writing so that the basis for any subsequent withdrawal was itself part of the professional record. Disassociation without prior escalation to the City would have been ethically insufficient; escalation followed by disassociation if the City failed to act would have been ethically defensible.

In response to Q103: The routing of a major public infrastructure project through Community P based on a fraudulent public engagement record constitutes a public safety and welfare harm that independently triggers Engineer M's paramount obligation under the Code, irrespective of client or subconsultant relationships. The harm here is not speculative or remote. Community P is a historically underserved, underrepresented, and overburdened neighborhood whose residents raised concrete concerns about displacement and business disruption during the limited participation that did occur. A report that affirmatively misrepresents the level of community support for routing the project through that neighborhood - by suppressing the conditions that prevented meaningful participation - directly corrupts the evidentiary basis on which a consequential public decision will be made. This is precisely the category of harm the Code's paramount public welfare obligation is designed to address. The fact that the harm flows through a procedural mechanism - a fraudulent engagement report - rather than through a structural defect in the physical infrastructure does not diminish its severity. Engineer M's obligation to hold paramount the safety, health, and welfare of the public therefore required action beyond an informal objection to Firm DBA, and that obligation existed independently of any contractual or subconsultant relationship.

In response to Q104: Firm DBA's communications and public relations department is operating in a domain that, when embedded within an engineering project affecting community welfare and public infrastructure routing decisions, carries engineering ethical obligations regardless of the professional licensing status of the individuals directly executing the work. The public engagement process here is not a peripheral marketing function - it is a data-collection mechanism whose outputs directly inform a consequential engineering and planning decision. When a communications department designs and executes a process intended to produce a record of community input that will be used to justify routing a major highway through a specific neighborhood, the integrity of that process is an engineering ethics matter. The presence of licensed professional engineers in supervisory and ownership roles within Firm DBA does not merely satisfy the ethical obligations that attach to this work - it makes those licensed engineers directly responsible for the ethical quality of the output. A PE supervisor who approves or permits the submission of a materially misrepresentative public engagement report cannot disclaim responsibility by pointing to the communications department as the executing unit. The Code's obligations attach to the licensed engineer's exercise of responsible charge, and responsible charge over a department that produces a fraudulent report means responsible charge over the fraud.

In response to Q201: The tension between Engineer M's obligation to hold paramount the public welfare and the duty to serve the client faithfully is resolved by the Code's explicit hierarchy: public welfare is paramount, and client service is legitimate only insofar as it does not require the engineer to act against that paramount obligation. When the City itself has directed the conduct that produced the fraudulent engagement record, the client relationship does not provide cover - it compounds the problem. Engineer M cannot satisfy the public welfare obligation by deferring to the City's economic, political, and social justifications, because those justifications do not appear in the Code as recognized exceptions to the duty of honesty and non-deception. The appropriate resolution of this tension required Engineer M to advise the City formally, in writing, that the engagement process as conducted could not support a legitimate finding of community support, and that proceeding on the basis of Firm DBA's report would expose the project to a materially false public record. This is precisely the kind of adverse notification the Code contemplates under the obligation to advise clients when a project will not be successful as planned.

In response to Q202: The obligation to report known Code violations to appropriate authorities and the principle of resolving disputes at the lowest possible level first are not genuinely in conflict when properly sequenced. The Code does not require engineers to exhaust every possible internal remedy before reporting a violation - it requires that engineers report violations to appropriate authorities, and the appropriate authority depends on the nature and severity of the violation and the responsiveness of lower-level actors. In this case, Engineer M should have first raised concerns formally and in writing with Firm DBA, then escalated to the City upon Firm DBA's non-compliance, and then assessed whether the City's response was adequate. If the City - itself implicated in directing the inequitable engagement - failed to correct the record or take remedial action, the appropriate next step would be reporting to the state licensure board, because at that point both the subconsultant and the client have demonstrated that internal resolution is unavailable. The sequencing obligation does not require Engineer M to remain silent indefinitely while a fraudulent report shapes a consequential public decision. The threshold for escalation to the licensure board is reached when internal escalation has been genuinely attempted and has failed, not when it has merely been initiated.

In response to Q203: The obligation to avoid injuring the professional reputation of another engineer does not prohibit Engineer M from formally challenging Firm DBA's public engagement report. The Code's protection of professional reputation is conditioned on the absence of malice and falsity - it prohibits malicious or false attacks, not truthful and professionally grounded challenges to a materially misrepresentative report. When Engineer M formally contests Firm DBA's report by accurately describing the session locations, times, absence of written comment mechanisms, and the resulting participation gap, Engineer M is issuing truthful statements grounded in documented fact. That is precisely what the Code requires under the obligation to be objective and truthful in professional reports and statements. The reputational harm that flows to Firm DBA from an accurate account of its conduct is a consequence of Firm DBA's own actions, not of Engineer M's malice. Engineer M must navigate this tension by ensuring that any formal challenge is scrupulously factual, documented, and directed to appropriate parties - not offered as a public denunciation but as a professional correction of a materially false record.

In response to Q301: From a deontological perspective, Engineer M did not fully discharge the categorical duty to hold paramount the safety, health, and welfare of the public by raising concerns only to Firm DBA. The categorical nature of the public welfare obligation means that its fulfillment cannot be satisfied by a good-faith attempt that stops short of the action necessary to actually protect the public. Raising concerns informally to Firm DBA, receiving a dismissal, and then allowing the misleading report to enter the public record without further escalation fails the deontological standard because the duty is not merely to object - it is to act in a manner that gives the public welfare obligation its full practical effect. A deontological framework does not permit Engineer M to satisfy the duty by performing the minimum procedural step and then deferring to the outcome. The duty required Engineer M to escalate to the City, to document concerns formally, and to refuse to allow the project to proceed on the basis of a report Engineer M knew to be materially false. Anything less treats the public welfare obligation as a preference to be weighed rather than a categorical imperative to be honored.

In response to Q302: From a deontological perspective, the City's explicit instruction to Firm DBA to conduct inequitable public engagement sessions does not relieve Firm DBA's licensed professional engineers of their independent duty not to deceive. The Code imposes obligations on licensed engineers as individuals, and those obligations are not delegable to clients. A client instruction to act unethically is not a defense under the Code - it is itself a violation of the client's obligations, but it does not transform an engineer's compliance with that instruction into ethical conduct. Firm DBA's licensed PE supervisors and owners retained full, unconditional responsibility for the accuracy and completeness of the public engagement report that was submitted under their professional authority. The rationalization that the City directed the process, or that the process was consistent with prior City projects, does not satisfy the deontological standard because the duty not to deceive is categorical and cannot be discharged by pointing to the source of the instruction to deceive. Firm DBA's licensed engineers were obligated to refuse to submit a report they knew to be materially misrepresentative, regardless of client direction.

In response to Q303: From a consequentialist perspective, the harm imposed on Community P by routing a major highway upgrade through a historically underserved, underrepresented, and overburdened neighborhood based on fraudulent public engagement data almost certainly outweighs the economic, political, and social benefits the City cited as justification. The consequentialist calculus here must account not only for the direct harms - resident displacement, business disruption, and the concentration of infrastructure burden in an already overburdened community - but also for the systemic harms produced by normalizing fraudulent engagement practices. If the fraudulent report is accepted as a legitimate basis for the routing decision, the precedent established is that public engagement processes for infrastructure projects affecting underserved communities can be designed to suppress participation and then misrepresented as evidence of community support. The long-term aggregate harm of that precedent - to democratic legitimacy, to environmental justice, and to the integrity of public infrastructure planning - is substantial and extends far beyond the immediate project. The City's cited justifications, which are economic, political, and social in nature, do not appear to have been weighed against these systemic harms, and a consequentialist analysis that accounts for them would not support the conclusion that the fraudulent engagement process produced a net benefit.

In response to Q304: From a virtue ethics perspective, Firm DBA's licensed professional engineers failed to demonstrate the professional integrity and moral courage expected of engineers when they rationalized the inequitable engagement sessions as consistent with prior City projects. Virtue ethics evaluates conduct not merely by whether it conforms to rules but by whether it reflects the character of a person of practical wisdom and professional integrity. A virtuous engineer, confronted with a client instruction to conduct public engagement in a manner that foreseeably excludes a historically underserved community, would not seek comfort in the precedent of prior projects - they would independently evaluate whether the practice meets the standard of honest and objective professional conduct. The appeal to prior practice is a form of moral outsourcing: it substitutes institutional habit for independent ethical judgment. Firm DBA's licensed engineers demonstrated neither the practical wisdom to recognize the ethical significance of what they were doing nor the moral courage to resist client pressure when that pressure pointed toward professional misconduct. The virtue ethics standard requires more than rule compliance - it requires the kind of character that does not need a rule to tell it that suppressing community participation and then misrepresenting the results is wrong.

In response to Q305: From a virtue ethics perspective, Engineer M's decision to express concern to Firm DBA but continue associating with the project after Firm DBA dismissed those concerns and submitted a misleading report reflects an incomplete exercise of professional courage and integrity. A person of genuine professional virtue does not satisfy the demands of integrity by registering an objection and then acquiescing to the outcome. Continued association with a project whose public record Engineer M knew to be fraudulent - without formal escalation to the City, without written documentation of objections, and without a clear statement that the project could not proceed ethically on its current basis - represents a compromise of the character expected of a trustworthy steward of the public welfare. The virtue ethics standard does not require Engineer M to be heroic or to sacrifice the professional relationship gratuitously, but it does require that Engineer M's conduct be consistent with the character of someone who genuinely holds the public welfare paramount rather than someone who treats that obligation as a preference to be expressed and then set aside when it becomes inconvenient. Engineer M's continued association, without escalation, falls short of that standard.

In response to Q306: From a consequentialist perspective, Engineer M's reporting of Firm DBA's violations to the state licensure board - after exhausting escalation to the City - would produce better long-term outcomes for public welfare and professional integrity than limiting escalation to the City alone. The consequentialist case for licensure board reporting rests on three distinct grounds. First, the City is itself implicated in directing the inequitable engagement process, which means it is not a neutral corrective authority and may have institutional incentives to allow the fraudulent report to stand. Second, licensure board reporting creates a formal record of the violation that is independent of the project's political and economic dynamics, providing a basis for deterrence that a private City-level resolution does not. Third, the normalization of fraudulent public engagement practices for infrastructure projects affecting underserved communities produces systemic harms - to democratic legitimacy, to environmental justice, and to the integrity of the engineering profession - that are best addressed through the formal accountability mechanisms the licensure system provides. The risk of disrupting the project timeline is a real cost, but it is outweighed by the benefit of preventing a consequential public decision from being made on a fraudulent evidentiary basis and by the deterrent value of formal accountability for the licensed engineers who produced and approved the misleading report.

In response to Q401: If Engineer M had formally documented concerns about the inequitable session locations and lack of written comment mechanisms in writing to Firm DBA before the sessions were held, Firm DBA would have had clear, documented notice that the proposed process was professionally unacceptable to the lead engineer. Whether that notice would have caused Firm DBA to correct the process is uncertain, given that Firm DBA subsequently dismissed Engineer M's concerns even after the sessions were held and cited City direction as justification. However, pre-session written documentation would have produced two significant consequences regardless of Firm DBA's response. First, it would have created a contemporaneous record establishing that Engineer M identified the ethical deficiencies before they produced a fraudulent report, which would have strengthened Engineer M's professional position in any subsequent escalation to the City or licensure board. Second, it would have given the City an earlier opportunity to intervene before the misleading report entered the public record. The failure to document concerns in writing before the sessions were held was itself a procedural shortcoming that reduced Engineer M's practical ability to challenge the report effectively after the fact.

In response to Q402: If Engineer M had refused to continue as lead engineer upon learning that Firm DBA submitted the misleading public engagement report without correction, that act of professional disassociation would have been ethically necessary but not ethically sufficient. Disassociation without disclosure would have removed Engineer M's implicit endorsement of the fraudulent record but would have left Community P without any professional advocate capable of challenging that record in the public process. The ethical obligation to hold paramount the safety, health, and welfare of the public does not terminate upon disassociation - it requires that the engineer take whatever steps are available to prevent the public harm, including advising the City of the basis for disassociation and the specific deficiencies in the public engagement record. A silent withdrawal that allows the fraudulent report to stand unchallenged in the public record does not satisfy the paramount public welfare obligation, even if it satisfies the non-association obligation. Engineer M's ethical obligations therefore required both disassociation and disclosure - a formal, documented statement to the City explaining why the report could not be professionally endorsed and what corrective action was required before the project could proceed on a legitimate basis.

In response to Q403: The City's explicit instruction to Firm DBA to conduct the public engagement sessions in an inequitable manner is a significant factor in the ethical culpability analysis, but it does not fundamentally alter Firm DBA's ethical responsibility - it adds a layer of culpability to the City without removing any from Firm DBA. Without the City's direction, it is plausible that Firm DBA's licensed professional engineers might have designed a more accessible and representative outreach process, given that the inequitable design appears to have been responsive to specific City instructions rather than Firm DBA's independent professional judgment. However, the ethical analysis does not turn on what Firm DBA would have done absent the City's direction - it turns on what Firm DBA was obligated to do regardless of that direction. The Code's obligations are unconditional with respect to deception and misrepresentation. Even if the City had not directed the inequitable process, Firm DBA's licensed engineers would have been obligated to design an accessible process and to produce an accurate report. The City's direction explains the genesis of the violation but does not excuse it. What the City's direction does establish is that the City itself violated its obligation not to direct conduct that produces a fraudulent public record, making the City a co-responsible party in the ethical violation rather than a neutral client whose instructions Firm DBA was entitled to follow.

In response to Q404: Even if virtual meetings and written comment mechanisms had been provided alongside the in-person sessions held in Community Q, the participation gap between Community P and Community Q would not have been fully remedied, because the session locations themselves were so fundamentally exclusionary that supplemental access measures would have addressed only part of the structural inequity. The in-person sessions were held during work hours at venues far from Community P and not easily accessible via public transit - conditions that systematically disadvantaged Community P residents regardless of whether virtual alternatives were also available. Virtual participation requires reliable internet access, digital literacy, and time - resources that are often disproportionately scarce in historically underserved communities. Written comment mechanisms, while valuable, do not substitute for the deliberative quality of in-person engagement, particularly for communities with lower rates of formal written communication with government institutions. A genuinely representative engagement process for Community P would have required sessions held within or immediately adjacent to Community P, at times accessible to working residents, with multiple participation modalities including in-person, virtual, and written options. The supplemental measures alone, without correcting the fundamental location and timing exclusions, would have produced a more accessible process but not a legitimately representative one.

The tension between client loyalty and public welfare paramountcy was not resolved in this case - it was suppressed. The City's explicit direction to Firm DBA to conduct inequitable engagement sessions created a situation in which the client's stated interests were structurally opposed to the welfare of Community P. The Code resolves this tension categorically: the obligation to hold paramount the safety, health, and welfare of the public is not a principle that yields to client preference, economic rationale, or political convenience. When the City cited economic, political, and social considerations to justify the inequitable process, it did not create a legitimate competing interest that Engineer M or Firm DBA were entitled to weigh against public welfare - it identified the precise kind of institutional pressure that the Code's paramountcy language is designed to override. This case teaches that client authority is a bounded concept under the Code: engineers may serve client interests faithfully only within the space that public welfare constraints permit, and when a client directive itself produces the ethical violation, the directive loses its claim to professional deference entirely.

The obligation to avoid deceptive acts and to issue only truthful, objective professional statements came into direct tension with the principle of avoiding injury to the professional reputation of another engineer when Engineer M faced the decision of whether to formally challenge Firm DBA's public engagement report. The Code resolves this tension by making non-deception and truthfulness structural prerequisites of professional conduct, not merely aspirational values to be balanced against collegial courtesy. The prohibition on injuring another engineer's reputation applies to malicious or false attacks - it does not shield a materially misrepresentative report from factual correction. When Firm DBA submitted a report omitting the session locations, times, and the absence of written comment mechanisms, and affirmatively claimed Community P's support, the report crossed from professional opinion into deceptive misrepresentation. Engineer M's obligation to issue truthful public statements and to avoid association with deceptive acts therefore required formal challenge of the report, and that challenge - grounded in documented fact rather than professional animus - would not constitute the kind of reputational injury the Code prohibits. This case teaches that the collegial protection principle operates only in the space of honest disagreement, not as a shield for documented misrepresentation.

The principle requiring engineers to resolve disputes at the lowest possible level first and the principle requiring reporting of known Code violations to appropriate authorities are not inherently in conflict, but they impose a sequenced rather than simultaneous set of obligations - and that sequence has a time limit defined by harm. In this case, Engineer M appropriately initiated escalation at the lowest level by raising concerns directly with Firm DBA. When Firm DBA dismissed those concerns and submitted the misleading report, the lowest-level resolution pathway was exhausted, and the obligation to escalate to the City became active. If the City - already implicated as the directing party - failed to correct the record, the obligation to report to the state licensure board would become operative not as an optional escalation but as a mandatory one, because the harm to Community P from a project proceeding on a fraudulent public engagement record constitutes precisely the kind of public welfare threat that reporting obligations exist to address. This case teaches that graduated escalation is not a mechanism for indefinitely deferring accountability - it is a structured pathway with defined trigger points, and each failed level of resolution accelerates rather than delays the obligation to escalate further.

Should Engineer M challenge the validity of Firm DBA’s report?

Should Engineer M raise any concerns with the City, as the client, and, if so, how?

Are Firm DBA’s actions ethical?

Does the City's explicit instruction to Firm DBA to conduct public engagement sessions in an inequitable manner implicate the City itself in an ethical violation, and does Engineer M have an obligation to refuse City directives that foreseeably harm a historically underserved community?

At what point does Engineer M's continued association with the project - after raising concerns that were dismissed by both Firm DBA and potentially the City - constitute complicity in the fraudulent public engagement record, and should Engineer M consider disassociation before exhausting all escalation pathways?

Does the routing of a major public infrastructure project through Community P - a historically underserved, underrepresented, and overburdened neighborhood - based on a fraudulent public engagement report constitute a public safety and welfare harm that triggers Engineer M's paramount obligation to the public independent of client or subconsultant relationships?

Is the Firm DBA communications and public relations department operating within an appropriate scope of engineering practice when it designs and executes public engagement processes for infrastructure projects affecting community welfare, and does the licensed PE supervisory structure within Firm DBA fully satisfy the ethical obligations that attach to that work?

How should Engineer M balance the obligation to hold paramount the safety, health, and welfare of the public - including Community P - against the duty to serve the client faithfully when the City itself has directed the conduct that produced the fraudulent engagement record?

Does the principle requiring engineers to report known Code violations to appropriate authorities conflict with the principle of resolving disputes at the lowest possible level first, and how should Engineer M sequence these obligations when both Firm DBA and the City may be implicated in the same ethical violation?

Does the obligation to avoid injuring the professional reputation of another engineer conflict with the obligation to issue truthful public statements and challenge a materially misrepresentative report, and how should Engineer M navigate this tension when formally contesting Firm DBA's public engagement report?

When the City cites economic, political, and social considerations to justify directing inequitable public engagement, how should Engineer M weigh the principle of serving the legitimate interests of clients against the principle of protecting the welfare of a historically underserved community whose input was systematically suppressed?

From a deontological perspective, did Engineer M fulfill their categorical duty to hold paramount the safety, health, and welfare of the public by raising concerns only to Firm DBA rather than immediately escalating to the City when the misleading report was submitted?

From a deontological perspective, does the City's explicit instruction to Firm DBA to conduct inequitable public engagement sessions relieve Firm DBA's licensed professional engineers of their independent duty not to deceive, or does the Code impose an unconditional obligation that cannot be delegated away by client direction?

From a consequentialist perspective, does the harm imposed on Community P - a historically underserved, underrepresented, and overburdened neighborhood - by routing a major highway upgrade based on fraudulent public engagement data outweigh any economic, political, or social benefits the City cited as justification for directing the inequitable engagement process?

From a virtue ethics perspective, did Firm DBA's licensed professional engineers demonstrate the professional integrity and moral courage expected of engineers when they rationalized the inequitable engagement sessions as consistent with prior City projects rather than independently evaluating whether those practices met the standard of honest and objective professional conduct?

From a virtue ethics perspective, did Engineer M demonstrate sufficient professional courage and integrity by expressing concern to Firm DBA but continuing to associate with the project after Firm DBA dismissed those concerns and submitted a misleading report, or did continued association compromise Engineer M's character as a trustworthy steward of the public welfare?

From a consequentialist perspective, would Engineer M's reporting of Firm DBA's violations to the state licensure board produce better long-term outcomes for public welfare and professional integrity - including deterrence of future inequitable engagement practices - than limiting escalation to the City alone, even if such reporting risks disrupting the infrastructure project timeline?

If Engineer M had formally documented their concerns about the inequitable session locations and lack of written comment mechanisms in writing to Firm DBA before the sessions were held - rather than raising concerns informally after the fact - would Firm DBA have had sufficient notice to correct the process, and would the misleading report have been prevented from entering the public record?

If Engineer M had refused to continue as lead engineer on the project upon learning that Firm DBA submitted the misleading public engagement report without correction, would that act of professional disassociation have been sufficient to satisfy Engineer M's ethical obligations, or would it have left Community P without any advocate capable of challenging the fraudulent record?

If the City had not explicitly instructed Firm DBA to conduct the public engagement sessions in an inequitable manner, would Firm DBA's licensed professional engineers have independently designed an accessible and representative outreach process for Community P, and does the City's direction fundamentally alter the ethical culpability analysis for Firm DBA?

If virtual meetings and written comment mechanisms had been provided alongside the in-person sessions held in Community Q, would the participation gap between Community P and Community Q have been sufficiently narrowed to produce a legitimately representative public engagement record, or were the session locations themselves so fundamentally exclusionary that no supplemental access measures could have remedied the structural inequity?

The City's engagement of Firm DBA initiates the procurement relationship that subsequently enables client-directed procedural manipulation, placing the City in potential violation of its obligation not to direct or enable fraudulent reporting, and is constrained by environmental justice and ethical compliance standards that govern how public outreach consultants must be selected and supervised.

Firm DBA's scheduling of sessions at inaccessible times and locations directly violates the equitable public engagement constraint and the completeness/accuracy obligation by structurally excluding Community P residents from meaningful participation, thereby undermining the environmental justice protections that constrain how public outreach must be conducted for historically underserved communities.

Excluding written and virtual participation modes compounds the inaccessible scheduling by eliminating all alternative pathways for Community P to provide input, violating the completeness and accuracy obligation and the non-deception constraint because the resulting record will misrepresent the actual scope and inclusivity of community engagement.

Engineer M raising concerns fulfills the subcontractor ethical compliance oversight obligation and initiates the required graduated escalation sequence, constrained by the lowest-level resolution priority principle that requires Engineer M to first attempt internal resolution with Firm DBA before escalating to the City or licensure board.

Firm DBA's dismissal of Engineer M's concerns violates the completeness and accuracy obligation by refusing to correct the deficient engagement process, triggers Engineer M's obligation to escalate to the City and potentially the licensure board, and is constrained by the code of ethics universal applicability constraint which applies to Firm DBA's PE supervisors regardless of the City's direction as a defense.

Firm DBA's production of a misleading outreach report directly violates its completeness and accuracy obligations and every constraint requiring factual, non-deceptive reporting, while fulfilling no legitimate obligation and placing Community P's welfare at risk by entering a fraudulent document into the public record.

Engineer M's formal confrontation of Firm DBA fulfills the subcontractor ethical compliance oversight obligation and is the required first step in the graduated escalation sequence, constrained by the lowest-level resolution priority principle that demands direct engagement before escalating to the City or licensure board.

Engineer M's escalation to the City fulfills the graduated escalation obligation triggered by Firm DBA's non-compliance and serves the paramount public safety obligation for Community P, but is constrained by the procedural requirement that direct subcontractor confrontation must have been exhausted first and by the complication that the City itself directed the inequitable engagement process.

This question emerged because Firm DBA's dismissal of Engineer M's concerns left a fraudulent report in the official project record, directly triggering Engineer M's subcontractor oversight and public welfare obligations. The tension between those obligations and Engineer M's limited direct authority over a subconsultant's deliverable created genuine uncertainty about whether formal challenge was required, permitted, or procedurally appropriate.

This question emerged because Firm DBA's non-compliance exhausted the lowest-level resolution pathway, making City escalation the next required step under graduated escalation obligations, but the possibility that the City directed the problematic conduct introduced uncertainty about whether the City could serve as a neutral corrective authority. The question of 'how' reflects the additional tension between Engineer M's duty to be forthright and the procedural norms governing client communication.

This question emerged because Firm DBA's conduct involved both licensed PE supervisors and a communications department, making the scope of applicable ethical obligations genuinely contested. The combination of inaccessible sessions, exclusion of participation alternatives, a misleading report, and active dismissal of concerns created a factual record that clearly implicates ethical standards, but the dual identity of Firm DBA as both an engineering firm and a public relations firm introduced structural ambiguity about which standards govern which actors.

This question emerged because the City's direct role in directing the inequitable engagement process transformed the standard client-escalation pathway into a structural paradox: the entity Engineer M is obligated to notify and defer to is the same entity that originated the ethical violation. The intersection of environmental justice obligations, client authority norms, and the historically underserved status of Community P created a novel question about whether client directives that foreseeably harm vulnerable communities fall outside the scope of permissible professional compliance.

This question emerged because the sequential dismissal of Engineer M's concerns by both Firm DBA and potentially the City created a situation where continued project association increasingly implicates Engineer M in the fraudulent public engagement record, but the graduated escalation framework has not yet been fully exhausted. The tension between the non-association obligation's immediacy and the procedural requirement to exhaust escalation pathways before disassociation - combined with the paradox that disassociation may harm the very community Engineer M seeks to protect - produced a genuinely novel and unresolved ethical question.

This question arose because the data - a fraudulent engagement report produced under City direction that routes infrastructure through an overburdened community - simultaneously satisfies the trigger conditions for both the paramount public welfare obligation and the client-service obligation, and the question of whether public welfare paramountcy operates independently of client relationships is unresolved when the client is itself the source of the ethical violation. The historically underserved status of Community P and the environmental justice dimension intensify the warrant conflict by raising the threshold of what counts as a public safety and welfare harm sufficient to override normal professional deference to client authority.

This question arose because the organizational structure of Firm DBA - a communications department operating within a PE-supervised firm - creates genuine ambiguity about whether the ethical obligations of engineering licensure travel with the PE supervisory relationship or are bounded by the technical engineering scope of work, and the fraudulent report makes the stakes of that ambiguity concrete. The question is structurally generated by the data showing that non-engineer communications professionals produced a materially misrepresentative report affecting public infrastructure decisions, while licensed PEs nominally supervised the enterprise, leaving unresolved whether that supervision was ethically sufficient or merely organizational.

This question arose because the City's role as both the client and the directing party of the fraudulent engagement collapses the normal two-step structure in which an engineer escalates subconsultant violations to the client for correction, forcing Engineer M into a direct conflict between the obligation to serve the client faithfully and the obligation to protect Community P's welfare that cannot be resolved through the standard escalation pathway. The historically underserved and overburdened status of Community P sharpens the conflict by invoking environmental justice obligations that elevate the welfare harm above ordinary project disputes.

This question arose because the NSPE Code contains two procedural obligations - report known violations to appropriate authorities, and resolve disputes at the lowest possible level first - that are both triggered by the same data set and point toward different sequencing conclusions, and the involvement of both the subconsultant and the client in the same violation eliminates the normal hierarchical structure that would make the sequencing question answerable. The question is structurally generated by the exhaustion of internal escalation pathways and the ambiguity about whether that exhaustion satisfies or merely begins the conditions for external reporting.

This question arose because the same act - formally contesting Firm DBA's report - is simultaneously required by one set of Code obligations and potentially constrained by another, and the question of how to navigate that tension is not resolved by the Code's text alone because both obligations are framed as affirmative duties rather than as exceptions to each other. The fraudulent nature of the report and its consequences for Community P make the tension practically urgent, because Engineer M cannot remain silent without violating the truthfulness obligation but cannot speak without risking a reputation-injury claim from Firm DBA.

This question emerged because the City's invocation of economic, political, and social justifications created a plausible but contested warrant for client deference, directly colliding with the unconditional public welfare paramountcy obligation triggered by Community P's systematic exclusion. The question could not be resolved by either warrant alone because the data - a historically underserved community's input being suppressed by client direction - simultaneously activated both the client-service and public-protection obligations without a clear hierarchical rule to adjudicate between them.

This question emerged because the deontological framing exposed a structural gap between the procedurally correct graduated escalation pathway and the categorical imperative to protect public welfare without delay once a fraudulent document entered the official record. The data - Firm DBA's dismissal followed by report submission - created a moment where the two warrants diverged in their prescribed responses, making it impossible to satisfy both simultaneously and forcing the question of which obligation was truly paramount.

This question emerged because the City's explicit instruction created a facially plausible defense for Firm DBA's engineers - that they were executing a client mandate rather than exercising independent professional judgment - which directly contested the warrant that the Code imposes non-delegable duties on licensed professionals. The collision between the principal-agent relationship data and the unconditional professional obligation warrant produced irreducible uncertainty about whether client direction can ever function as a valid rebuttal to a categorical ethical constraint.

This question emerged because the consequentialist framework's standard aggregation logic was destabilized by the intersection of two data facts: the harm fell on a historically underserved and overburdened community, and it was produced through a fraudulent process rather than a legitimate trade-off analysis. These two facts activated competing warrants about whether consequentialist calculus can proceed normally when the input data is corrupted and when the harmed party holds protected status under environmental justice policy, making the question of harm-benefit comparison genuinely unresolvable within a single consequentialist framework.

This question emerged because the virtue ethics framework exposed the gap between the external appearance of professional compliance - following City precedent - and the internal moral quality of the engineers' reasoning process, which the data revealed to be rationalization rather than independent evaluation. The fact that Engineer M had formally raised concerns before the report was produced transformed the precedent-reliance defense from a plausible warrant into a contested rebuttal, because the engineers could no longer claim ignorance of the ethical problem, making the question of whether their conduct reflected genuine professional integrity or motivated reasoning genuinely contested.

This question emerged because Engineer M's conduct occupies an ambiguous middle ground between the virtue ethics ideals of courage and integrity: the act of raising concerns is consistent with professional character, but the failure to escalate or disassociate after dismissal and fraudulent report submission challenges whether that character was sustained. The question is structurally necessary because virtue ethics evaluates the whole arc of conduct, not isolated acts, forcing scrutiny of whether Engineer M's continued association corrupted the integrity that the initial objection expressed.

This question emerged because consequentialist analysis requires comparing outcome streams across multiple escalation pathways, and the data shows that City-level escalation was insufficient to correct the fraudulent record, making the incremental benefit of licensure board reporting genuinely uncertain relative to its costs. The question is structurally necessary because the competing warrants authorize different escalation endpoints, and consequentialism cannot resolve the conflict without empirical projections about deterrence, timeline, and community welfare that the available facts do not supply.

This counterfactual question emerged because the sequence of Engineer M's informal post-hoc concern-raising versus a hypothetical formal pre-session intervention creates a causal gap in the ethical analysis: the question tests whether the procedural failure was preventable through Engineer M's earlier action or was structurally determined by City direction and Firm DBA's independent choices. The question is structurally necessary because the subcontractor oversight warrant and the Firm DBA primary responsibility warrant reach different conclusions about causal attribution, and the counterfactual framing is the only mechanism for isolating Engineer M's contribution to the outcome.

This counterfactual question emerged because the non-association obligation and the public welfare paramountcy obligation point in directly opposite directions when the fraudulent report has already entered the record: disassociation satisfies personal ethical integrity but may deprive Community P of its only internal advocate, while continued association preserves advocacy capacity but risks complicity in the fraudulent enterprise. The question is structurally necessary because the two warrants cannot be simultaneously satisfied, and the ethical analysis must determine which obligation takes precedence given the specific vulnerability of Community P and the absence of equivalent substitute advocates.

This counterfactual question emerged because the City's explicit direction to Firm DBA introduces a causal and moral complexity that the standard subconsultant compliance analysis does not resolve: if the inequitable design originated with the client rather than the subconsultant, the warrant structure governing Firm DBA's obligations must be tested against the rebuttal condition that client authority supersedes professional independence. The question is structurally necessary because the ethical culpability analysis for Firm DBA's licensed PE supervisors depends entirely on whether their independent professional obligations survived the City's direction, and the competing warrants reach opposite conclusions about that survival.

This question arose because Firm DBA's decision to schedule sessions exclusively in Community Q - without virtual, written, or geographically proximate alternatives - produced a participation record that systematically excluded Community P, the primary affected community, while the submitted report represented that record as legitimate community input. The question crystallizes the unresolved normative dispute between a procedural sufficiency view (supplemental mechanisms cure location defects) and a structural equity view (location exclusion is a foundational violation that supplemental access cannot remedy), a dispute that was never adjudicated because Firm DBA dismissed Engineer M's concerns and the City directed continuation of the flawed process.

The board concluded that Firm DBA's actions were unethical because the services were rendered under the supervision and ownership of licensed professional engineers, meaning the Code applied directly to the firm's conduct and the misleading public engagement report could not be insulated from ethical scrutiny by organizational structure or departmental assignment.

The board concluded that Firm DBA's ethical violation was compounded - not mitigated - by routing public engagement through a communications department, because the licensed PEs' retention of responsible charge meant they bore an affirmative duty to independently evaluate the engagement design against professional standards, and their failure to do so in favor of deference to City direction and precedent constituted a failure of the professional judgment the Code requires.

The board concluded that the City's explicit direction to conduct inequitable engagement sessions implicated the City itself in an ethical violation and independently obligated Engineer M - as lead engineer - to refuse to advance the project on the basis of a fraudulent engagement record, because compliance with an illegitimate client directive that foreseeably harms a historically underserved community is not a permissible exercise of serving client interests under the Code.

The board concluded that Engineer M's ethical standing was directly implicated by Firm DBA's unethical conduct and that Engineer M's obligations required a graduated, time-sensitive escalation - from formal advisement to the City, to reporting to the state licensure board if uncorrected, to disassociation as a last resort - because continued association with a project proceeding on a fraudulent evidentiary basis with Engineer M's implicit endorsement would independently violate Engineer M's paramount duty to the public welfare.

The board concluded that Engineer M could not balance the obligation to serve the City against the obligation to protect Community P's welfare because the City's directive was not a legitimate client instruction - it was a direction to facilitate public harm - and therefore Engineer M's paramount duty to the public required not merely raising concerns with Firm DBA but refusing to allow the project to advance on the fraudulent record and directly advising the City that the engagement process could not produce a report Engineer M could professionally endorse.

The board concluded that Engineer M's continued association crossed an ethical threshold once the misleading report was submitted and recognized as such, because passive association after that point constituted implicit endorsement under II.1.d; however, the board further concluded that immediate disassociation without first formally escalating to the City would itself be ethically deficient, because it would abandon Community P without any professional advocate, making sequenced escalation-then-disassociation the only fully defensible path.

The board concluded that routing a major public infrastructure project through Community P on the basis of a fraudulent engagement record constitutes a public safety and welfare harm that independently triggers Engineer M's paramount obligation under I.1, because the harm is concrete and direct - the fraudulent record corrupts the decision-making process for a community already bearing disproportionate infrastructure burdens - and the Code's paramount obligation does not recognize the procedural versus structural distinction as a basis for diminishing that harm.

The board concluded that Firm DBA's communications and public relations department was operating within the domain of engineering ethics because its outputs directly determined the evidentiary basis for a consequential infrastructure routing decision, and that the licensed PE supervisors within Firm DBA were therefore directly and fully responsible for the ethical quality of those outputs under the doctrine of responsible charge - meaning the PE supervisory structure did not merely satisfy ethical obligations but affirmatively imposed them.

The board concluded that the tension between Engineer M's paramount public welfare obligation and the duty to serve the City faithfully was resolved by the Code's own hierarchy, which makes client service subordinate to public welfare; because the City was itself the directing party behind the fraudulent record, deference to the client relationship would have compounded rather than resolved the ethical violation, and the correct expression of faithful client service was formal written notification under III.1.b that the engagement process could not support a legitimate community support finding.

The board concluded that the reporting obligation under II.1.f and the lowest-level-first resolution principle operate in sequence rather than in conflict: Engineer M was required to escalate formally in writing to Firm DBA, then to the City, and only upon the City's failure to correct the record or take remedial action would reporting to the state licensure board become the appropriate next step - because at that point both the subconsultant and the client would have demonstrated that internal resolution was genuinely unavailable, satisfying the precondition for external reporting.

The board concluded that Engineer M's formal challenge to Firm DBA's report does not violate the obligation to protect professional reputation because that obligation is expressly conditioned on malice and falsity, neither of which attaches to a scrupulously factual, documented correction; the reputational harm Firm DBA suffers is a consequence of its own conduct, not of Engineer M's wrongdoing, provided Engineer M directs the challenge to appropriate parties rather than offering it as a public denunciation.

The board concluded that Engineer M did not fully discharge the categorical duty to hold paramount public welfare because stopping at an informal objection to Firm DBA - and then allowing the misleading report to stand unchallenged - treats the duty as a preference to be weighed rather than an imperative to be honored; under a deontological standard, the duty required Engineer M to escalate to the City, document concerns formally, and refuse to allow the project to proceed on a false record.

The board concluded that the City's explicit instruction does not relieve Firm DBA's licensed engineers of their independent duty not to deceive because Code obligations are personal and non-delegable; Firm DBA's licensed PE supervisors retained full responsibility for the accuracy of the report submitted under their professional authority, and the rationalization that the City directed the process - or that it was consistent with prior projects - does not satisfy the categorical standard because the duty not to deceive cannot be outsourced to a client.

The board concluded that the harm to Community P almost certainly outweighs the City's cited justifications because the consequentialist analysis must account not only for direct harms - displacement, business disruption, and concentrated infrastructure burden - but also for the systemic harm of establishing a precedent that fraudulent engagement processes can be used to suppress participation in underserved communities and then misrepresented as evidence of community support, a precedent whose long-term aggregate harm to democratic legitimacy and environmental justice is substantial.

The board concluded that Firm DBA's licensed engineers failed the virtue ethics standard because they demonstrated neither the practical wisdom to recognize the ethical significance of designing sessions that foreseeably excluded Community P nor the moral courage to resist client pressure - instead outsourcing their ethical judgment to institutional habit by rationalizing the sessions as consistent with prior City projects, a rationalization that a person of genuine professional integrity would not have needed a rule to reject.

The board concluded that Engineer M's continued association after Firm DBA dismissed concerns and submitted a fraudulent report fell short of the virtue ethics standard because genuine professional integrity requires escalation beyond a registered objection - expressing concern and then acquiescing is not the conduct of someone who truly holds public welfare paramount, but of someone who treats that obligation as optional when it becomes professionally inconvenient.

The board concluded that licensure board reporting produces better long-term outcomes than City-level escalation alone because the City is not a neutral corrective authority, formal reporting creates an independent deterrence record, and the systemic harms of normalizing fraudulent engagement for infrastructure projects affecting underserved communities are best addressed through the accountability mechanisms the licensure system provides - making the timeline disruption risk a real but clearly outweighed cost.

The board concluded that pre-session written documentation would have produced two significant consequences regardless of Firm DBA's response - a contemporaneous record establishing Engineer M's prior identification of ethical deficiencies, and an earlier opportunity for City intervention - and that Engineer M's failure to document concerns in writing before the sessions was itself a procedural shortcoming that materially reduced the ability to challenge the fraudulent report effectively after it was submitted.

The board concluded that disassociation alone would have been ethically necessary but insufficient because it would have removed Engineer M's implicit endorsement while leaving Community P without a professional advocate and the fraudulent report unchallenged in the public record - the paramount public welfare obligation required Engineer M to both disassociate and formally disclose to the City the specific deficiencies in the report and the corrective action required before the project could proceed on a legitimate basis.

The board concluded that the City's explicit instruction is a significant factor that makes the City a co-responsible party in the ethical violation, but it does not alter Firm DBA's ethical culpability because the Code imposes unconditional obligations not to deceive or misrepresent - Firm DBA's licensed engineers were independently obligated to design an accessible process and produce an accurate report regardless of City direction, and the City's instruction explains but does not excuse the violation.

The board concluded that virtual meetings and written comment mechanisms, while valuable, would have addressed only part of the structural inequity because the fundamental barriers of inaccessible location and work-hour timing would have persisted; a legitimately representative process required sessions held within or adjacent to Community P at accessible times, with multiple modalities, not supplemental accommodations grafted onto an exclusionary foundation.

The board concluded that the tension between client loyalty and public welfare was not legitimately resolved in this case but suppressed, because the Code categorically subordinates client authority to public welfare obligations, and when the City's explicit direction produced the ethical violation, that direction forfeited its claim to professional deference entirely - Engineer M and Firm DBA were obligated to refuse, not comply.

The board concluded that Engineer M was obligated to formally challenge Firm DBA's report because the report constituted deceptive misrepresentation rather than mere professional disagreement, and the Code's prohibition on injuring another engineer's reputation does not protect materially false or omissive reports from factual correction - a challenge grounded in documented fact satisfies the truthfulness obligation without violating the collegial protection principle.

The board concluded that graduated escalation is not a mechanism for indefinitely deferring accountability but a structured pathway with defined trigger points: Engineer M's obligation moved from Firm DBA to the City once Firm DBA dismissed concerns and submitted the misleading report, and would move to the state licensure board if the City - already implicated as the directing party - failed to correct the fraudulent public engagement record, because the harm to Community P from a project proceeding on that record constitutes precisely the public welfare threat that mandatory reporting obligations exist to address.

Should Engineer M formally confront Firm DBA about the materially false and incomplete public engagement report, state all applicable ethical objections in writing, and require correction before the report is used to advance the project?

After Firm DBA refuses to correct the misleading public engagement report, should Engineer M escalate formally to the City, advise the City in writing that the report is materially false and that the project cannot proceed ethically on its current basis, and present the ethical obligations of all parties before considering external regulatory reporting?

After exhausting escalation to both Firm DBA and the City without obtaining correction of the fraudulent public engagement report, should Engineer M refuse to continue as lead engineer and formally document the basis for disassociation - including the specific deficiencies in the report and the corrective action required - rather than remaining associated with a project proceeding on a fraudulent evidentiary record?

Did Firm DBA's licensed professional engineers in supervisory and ownership roles violate the NSPE Code of Ethics by approving and permitting the submission of a materially false and incomplete public engagement report, and does the routing of execution through a communications department insulate those licensed PEs from ethical accountability?

If the City declines to correct the fraudulent public engagement record after Engineer M's formal escalation, should Engineer M report Firm DBA's ethical violations to the state engineering licensure board to prevent similar situations from occurring in the future, even if such reporting risks disrupting the infrastructure project timeline?

Does the City's explicit instruction to conduct inequitable public engagement sessions constitute a client directive that Engineer M is obligated to refuse, and does Engineer M's paramount duty to hold public safety, health, and welfare paramount require refusing to allow the project to proceed on the basis of a fraudulent engagement record regardless of the City's economic, political, and social justifications?