Step 4: Full View

The Regulatory Domain Compliance Certification Competence Prerequisite Obligation requires domain-specific competence before certifying compliance, general PE licensure does not authorize certification across all regulatory domains. The Institutional Role Non-Expansion of Competence Scope Obligation establishes that the Division Chief title does not confer competence in arms storage regulations. The Training Fund Unavailability Non-Excuse Obligation confirms that resource constraints do not excuse the competence requirement. The Military Non-Engineering Authority Certification Direction Resistance Obligation requires Engineer A to resist the Army official's directive when it conflicts with professional ethical obligations. The Out-of-Competence Compliance Certification Deception Prohibition Obligation establishes that affixing a professional seal without domain knowledge constitutes an inherently misleading professional representation. Competing pressure: the Army official's legitimate institutional authority over Engineer A as a civilian employee, and the organizational expectation that the Division Chief role encompasses this certification function.

The Out-of-Competence Certification Escalation and Qualified Expert Identification Obligation requires Engineer A to affirmatively escalate the matter and assist in identifying qualified experts or training pathways rather than simply refusing without constructive follow-through. The paramount public welfare principle (holding safety, health, and welfare of the public paramount) imposes a positive duty beyond mere non-participation in unethical acts, leaving the safety gap unaddressed after refusal is itself a failure to hold public welfare paramount. The Training Fund Unavailability Non-Excuse Obligation, while confirming that resource constraints do not excuse Engineer A from refusal, simultaneously implies that Engineer A should formally communicate how the institutional training fund decision causally contributed to the competence gap, creating an institutional record that may prompt systemic correction. The BER 94-8 precedent's graduated escalation model provides the procedural template: direct engagement with the requesting official, escalation to supervisors, and referral to broader authority if unresolved.

The public welfare paramount principle imposes a positive duty beyond mere non-participation in unethical acts: Engineer A must take affirmative steps to ensure the safety gap does not persist. The post-refusal escalation obligation requires formal documentation, supervisor notification, and referral to a qualified expert. The institutional role non-expansion principle, applied prospectively, requires Engineer A to formally communicate that the Division Chief role as structured creates foreseeable out-of-competence certification demands. The BER encouragement of state board certification rule modification suggests an additional advocacy obligation. Competing against full post-refusal engagement is the argument that Engineer A's institutional authority as a civilian employee is limited, that formal documentation of refusal could expose Engineer A to retaliation, and that advocacy for systemic change exceeds individual ethical duty and is more properly characterized as supererogatory.

The pre-acceptance competence self-assessment obligation requires Engineer A to evaluate whether a role's foreseeable demands fall within the engineer's competence before accepting. The institutional role non-expansion principle establishes that the Division Chief title confers no new technical authority over Army physical security regulations. Proactive disclosure upon role acceptance would have allowed the institution to arrange for a qualified expert in advance, protecting public safety more effectively than a last-minute refusal. The BER 85-3 reasoning suggests that where out-of-competence certification demands are a core and foreseeable function of the role, the engineer should decline the appointment or negotiate explicit competence-bounded role terms. Competing against proactive disclosure is the argument that disclosure would be premature absent a concrete certification task, that organizational norms place disclosure responsibility on the requesting authority rather than the engineer, and that the Division Chief role may encompass many functions within Engineer A's competence with arms storage certification being a peripheral rather than core demand.

Competing obligations include: (1) the pre-acceptance competence self-assessment obligation, the NSPE Code implicitly requires engineers to assess whether a role's foreseeable demands fall within their competence before accepting, not merely to refuse specific tasks after the fact; (2) the BER 85-3 precedent, where out-of-competence certification demands are foreseeable and central to a role, accepting the role without negotiating competence-bounded terms or declining it constitutes a failure of the pre-acceptance ethical obligation; (3) the negotiated boundary approach, accepting the role on the condition that arms storage certification is excluded is ethically preferable to unrestricted acceptance, but is sound only if the excluded function can be reliably reassigned to a qualified engineer and the remaining role is workable; and (4) the institutional role non-expansion principle, the Division Chief title confers no new technical authority, so accepting the title without addressing the competence gap merely defers rather than resolves the ethical problem.