Step 4: Review

Review extracted entities and commit to OntServe

Duty to Report Misconduct
Step 4 of 5
Commit to OntServe
Login to commit entities to OntServe. (300 entities already committed)
Phase 2D: Stalemate Competing obligations remain in tension without clear resolution
Phase 2A: Code Provisions
6 6 committed
code provision reference 6
II.5. individual committed

Engineers shall avoid deceptive acts.

codeProvision II.5.
provisionText Engineers shall avoid deceptive acts.
appliesTo 32 items
II.5.a. individual committed

Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates' qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments.

codeProvision II.5.a.
provisionText Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates' qualifications. They shall not misrepresent or exaggerate their responsibility in or for the ...
relevantExcerpts 1 items
appliesTo 53 items
III.7. individual committed

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.

codeProvision III.7.
provisionText 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 ...
appliesTo 52 items
III.8.a. individual committed

Engineers shall conform with state registration laws in the practice of engineering.

codeProvision III.8.a.
provisionText Engineers shall conform with state registration laws in the practice of engineering.
appliesTo 41 items
III.9. individual committed

Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.

codeProvision III.9.
provisionText Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.
relevantExcerpts 1 items
appliesTo 22 items
III.9.a. individual committed

Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments.

codeProvision III.9.a.
provisionText Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments.
appliesTo 16 items
Phase 2B: Precedent Cases
2 2 committed
precedent case reference 2
BER Case 76-4 individual committed

The Board cited this case to establish the precedent that engineers have an obligation to report their findings to applicable regulatory authorities, supporting the discussion of Engineer A's reporting obligations.

caseCitation BER Case 76-4
caseNumber 76-4
citationContext The Board cited this case to establish the precedent that engineers have an obligation to report their findings to applicable regulatory authorities, supporting the discussion of Engineer A's reportin...
citationType supporting
principleEstablished Engineers have an obligation to report observations or findings of potential violations or harm to the applicable regulatory authority, even when a client has terminated the contract and requested sil...
relevantExcerpts 2 items
internalCaseId 72
resolved True
BER Case 02-11 individual committed

The Board cited this case to reinforce that engineers have a clear obligation to report misconduct to engineering licensing boards, and to address the manner in which such reports may be made.

caseCitation BER Case 02-11
caseNumber 02-11
citationContext The Board cited this case to reinforce that engineers have a clear obligation to report misconduct to engineering licensing boards, and to address the manner in which such reports may be made.
citationType supporting
principleEstablished Engineers have a clear obligation to report information on misconduct to the engineering licensing board; while a signed complaint is preferable, an anonymous complaint is better than no complaint at ...
relevantExcerpts 2 items
internalCaseId 116
resolved True
Phase 2C: Questions & Conclusions
41 41 committed
ethical conclusion 20
Conclusion_1 individual committed

The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.

conclusionNumber 1
conclusionText The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.
conclusionType board_explicit
answersQuestions 1 items
extractionReasoning Parsed from imported case text (no LLM)
Conclusion_101 individual committed

The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution notice existed somewhere in the proposal, the overall presentation did not constitute falsification or misrepresentation. However, this reasoning leaves unresolved a meaningful gap between technical compliance and the spirit of honesty required by Section II.5.a. A single prefatory notice in a lengthy qualifications document does not guarantee that evaluators - who routinely focus on individual project descriptions when scoring proposals - will connect that notice to each project listed. The Board's analysis would have been strengthened by acknowledging that the adequacy of a disclosure is a function not only of its presence but of its placement, prominence, and the realistic reading behavior of the intended audience. Government procurement evaluators using scoring rubrics are likely to assess individual project entries in isolation, meaning that a prefatory notice, however well-intentioned, may functionally fail to inform the evaluation of each project. The Board's silence on this point leaves a normative gap: the NSPE Code's honesty standard, as applied here, appears to treat disclosure as a binary condition rather than a graduated obligation calibrated to the risk of actual misunderstanding.

conclusionNumber 101
conclusionText The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution not...
conclusionType analytical_extension
mentionedEntities {"principles": ["Honesty in Professional Representations Invoked By XYZ Engineers Qualification Proposals", "Transparency Principle Invoked By XYZ Engineers Prefatory Notice", "Qualification...
citedProvisions 2 items
answersQuestions 4 items
Conclusion_102 individual committed

The Board's finding that XYZ Engineers' practices were not unethical under the NSPE Code does not fully address the institutional dimension of the firm's responsibility. Engineer B is an individual licensee, but XYZ Engineers as a firm made the deliberate organizational decision to structure its qualifications proposals in the manner described. Section III.9 and Section III.9.a impose credit-attribution obligations that apply to the professional conduct of engineers, and when a firm systematically deploys a proposal format that concentrates attribution disclosure in a single prefatory location while allowing project-level descriptions to stand without attribution, the firm bears independent institutional responsibility for that structural choice. The Board's analysis focused primarily on Engineer B's individual conduct without separately evaluating whether XYZ Engineers, as the entity submitting the proposals and controlling their format, bore a distinct and potentially higher obligation to ensure that attribution was unambiguous at every level of the document. This omission is significant because it leaves open the question of whether firms can insulate themselves from ethical scrutiny by delegating attribution decisions to individual engineers while retaining control over proposal architecture.

conclusionNumber 102
conclusionText The Board's finding that XYZ Engineers' practices were not unethical under the NSPE Code does not fully address the institutional dimension of the firm's responsibility. Engineer B is an individual li...
conclusionType analytical_extension
mentionedEntities {"obligations": ["Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States", "Project-Level Attribution Obligation XYZ Engineers Engineer B State Z...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_103 individual committed

The Board's conclusion that Engineer B's practices were not unethical under the NSPE Code, when read alongside the finding that State Z's rules were violated, exposes a structural tension in the relationship between the NSPE Code and jurisdiction-specific licensing rules. The NSPE Code's honesty standard under Section II.5.a prohibits misrepresentation of qualifications but does not specify the granularity of attribution required in multi-employer proposal contexts. State Z's rules, by contrast, impose a precise project-level attribution requirement. The fact that conduct deemed compliant under the NSPE Code can simultaneously violate a state licensing rule suggests that the NSPE Code functions as a floor - not a ceiling - for professional honesty obligations, and that engineers practicing across multiple jurisdictions cannot rely solely on NSPE Code compliance to satisfy their full ethical and legal obligations. This divergence also raises a calibration concern: if the NSPE Code's honesty standard is consistently less demanding than jurisdiction-specific rules in states with detailed attribution requirements, the Code may systematically underprotect clients and competing firms in those jurisdictions. Engineers and firms operating in multi-state markets should therefore treat the most stringent applicable jurisdiction's rules as the operative standard for proposal preparation, rather than defaulting to the NSPE Code's more general formulation.

conclusionNumber 103
conclusionText The Board's conclusion that Engineer B's practices were not unethical under the NSPE Code, when read alongside the finding that State Z's rules were violated, exposes a structural tension in the relat...
conclusionType analytical_extension
mentionedEntities {"constraints": ["Jurisdiction-Specific Attribution Rule Compliance Constraint Engineer B XYZ Engineers State Z", "Jurisdiction-Specific Reporting Threshold Constraint Engineer A State Q vs State...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_104 individual committed

While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension introduced by Engineer A's status as a direct commercial competitor of XYZ Engineers. Both states' licensing rules impose a mandatory reporting obligation on licensees who have knowledge or reason to believe a violation has occurred, and the NSPE Code similarly supports reporting of unethical or illegal practice. However, the mandatory character of this obligation does not eliminate the ethical significance of the reporter's motivation. From a virtue ethics perspective, the legitimacy of Engineer A's reporting action depends in part on whether it was motivated by genuine concern for client protection and professional integrity rather than competitive self-interest. The Board's analysis would have been more complete had it acknowledged this tension and clarified that the mandatory reporting obligation remains valid and must be fulfilled regardless of the reporter's competitive position - but that Engineer A should be transparent about the competitive relationship when filing the report, and should confine the report strictly to documented rule violations rather than using the reporting mechanism to cast broader reputational doubt on XYZ Engineers. This framing preserves the integrity of the licensing enforcement system while acknowledging that competitive motivation, though it does not void the reporting duty, is an ethically relevant factor that the reporting engineer should consciously examine.

conclusionNumber 104
conclusionText While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension...
conclusionType analytical_extension
mentionedEntities {"constraints": ["Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State...
citedProvisions 2 items
answersQuestions 4 items
Conclusion_105 individual committed

The Board's analysis of Engineer A's reporting obligation appropriately distinguished between State Q and State Z based on the differing specificity of each state's licensing rules, concluding that a violation was established in State Z but not in State Q. This jurisdiction-differentiated outcome carries an important practical implication that the Board did not make explicit: Engineer A's obligation to report to the State Z board is mandatory under both states' rules once Engineer A has knowledge or reason to believe a violation occurred, and that threshold was met by Engineer A's own review of the State Z rules. The Board's reasoning therefore implicitly confirms that Engineer A's decision to report to the State Z board was not merely permissible but obligatory - and that declining to report after identifying a clear rule violation would itself have constituted a breach of Engineer A's professional obligations. Conversely, the absence of a comparable violation under State Q's more permissive standard means that reporting to the State Q board would have been unsupported by the factual record and potentially inconsistent with Section III.7's prohibition on conduct that injures the professional reputation of another engineer without factual basis. This asymmetry - mandatory reporting in State Z, inappropriate reporting in State Q - illustrates that the reporting obligation is not a blanket duty triggered by competitive suspicion but a jurisdiction-specific, evidence-calibrated professional responsibility.

conclusionNumber 105
conclusionText The Board's analysis of Engineer A's reporting obligation appropriately distinguished between State Q and State Z based on the differing specificity of each state's licensing rules, concluding that a ...
conclusionType analytical_extension
mentionedEntities {"constraints": ["Jurisdictional Constraint Engineer A Dual-State Reporting Obligation Assessment", "Jurisdiction-Specific Reporting Threshold Constraint Engineer A State Q vs State Z"],...
citedProvisions 3 items
answersQuestions 2 items
Conclusion_201 individual committed

Engineer A's status as a direct competitor of XYZ Engineers does create a potential conflict of interest that warrants careful self-examination before initiating any reporting action. However, that competitive relationship does not nullify the legitimacy of the reporting obligation itself. The NSPE Code and the licensing rules of both states impose a mandatory reporting duty on any licensee who has knowledge or reason to believe a violation has occurred - the rules do not carve out an exception for competitors, nor do they require the reporting engineer to be a disinterested party. The competitive motivation is ethically relevant to the question of motivational integrity (see Q306), but it does not transform a genuine violation into a non-violation, nor does it relieve Engineer A of the duty to report. What the conflict of interest does require is that Engineer A act with scrupulous accuracy - neither overstating the violation nor selectively reporting only in jurisdictions where it benefits ABC Consultants competitively. The fact that Engineer A declined to report to the State Q board, where no clear rule violation was found, and reported only to the State Z board, where a specific rule was clearly breached, is consistent with good-faith application of the reporting obligation rather than weaponization of the licensing system. The conflict of interest concern is real but does not override the mandatory reporting duty when the underlying violation is genuine.

conclusionNumber 201
conclusionText Engineer A's status as a direct competitor of XYZ Engineers does create a potential conflict of interest that warrants careful self-examination before initiating any reporting action. However, that co...
conclusionType question_response
mentionedEntities {"constraints": ["Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State...
citedProvisions 1 items
answersQuestions 2 items
Conclusion_202 individual committed

The Board's analysis focused primarily on Engineer B's individual conduct and did not separately evaluate XYZ Engineers' institutional culpability. This omission is analytically significant. XYZ Engineers, as the firm that prepared, reviewed, and submitted the qualifications proposals, bears independent institutional responsibility for the attribution practices embedded in those documents. A firm that knowingly structures proposal documents in a way that places attribution notices only in prefatory sections - while allowing lengthy individual project descriptions to function without any attribution reminder - has made an organizational decision about disclosure architecture. That decision cannot be attributed solely to Engineer B. Under NSPE Code Section II.5.a, the prohibition against permitting misrepresentation of qualifications applies to the firm as well as the individual engineer. The Board's conclusion that XYZ Engineers' practices were not unethical under the NSPE Code is defensible for State Q purposes, but the analysis would have been more complete had it separately assessed whether XYZ Engineers, as an institution, exercised adequate supervisory oversight to ensure that the prefatory attribution notice was sufficient to prevent a misleading overall impression - particularly given that the State Z rules imposed a stricter standard that the firm's proposal structure failed to meet.

conclusionNumber 202
conclusionText The Board's analysis focused primarily on Engineer B's individual conduct and did not separately evaluate XYZ Engineers' institutional culpability. This omission is analytically significant. XYZ Engin...
conclusionType question_response
mentionedEntities {"obligations": ["Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States", "XYZ Engineers Qualification Proposal Misrepresentation State Z"],...
citedProvisions 4 items
answersQuestions 1 items
Conclusion_203 individual committed

The prefatory attribution notice placed only at the beginning of Engineer B's individual qualification section - but not repeated within each project description - occupies an ethically ambiguous middle ground. It technically avoids outright falsification under the NSPE Code and satisfies the less specific State Q rules, but it does not fully satisfy the spirit of honesty and transparency that the Code's Section II.5.a demands. Sophisticated government procurement evaluators reading a lengthy qualifications proposal are most likely to focus their substantive evaluation on the detailed project descriptions themselves, not on a prefatory notice that may be several pages removed from the specific project narratives. A disclosure architecture that places the attribution caveat where it is least likely to be operationally noticed by evaluators - while allowing project descriptions to read as if they represent Engineer B's independent work product - creates a structural risk of misleading impressions even without any single false statement. The Board's conclusion that this practice was not unethical under the NSPE Code is defensible as a minimum compliance determination, but it should not be read as an endorsement of the practice as aspirationally ethical. The more transparent and professionally sound approach would have been to include attribution information adjacent to each project description, as State Z's rules explicitly require and as the intellectual integrity principle underlying Section III.9.a would support.

conclusionNumber 203
conclusionText The prefatory attribution notice placed only at the beginning of Engineer B's individual qualification section — but not repeated within each project description — occupies an ethically ambiguous midd...
conclusionType question_response
mentionedEntities {"principles": ["Transparency Principle Invoked By XYZ Engineers Prefatory Notice", "Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects", "Honesty in Professional...
citedProvisions 4 items
answersQuestions 1 items
Conclusion_204 individual committed

From a deontological perspective, Engineer B's prefatory-only attribution disclosure does not fully satisfy a categorical duty of honesty in professional representations. A Kantian analysis would ask whether the disclosure practice could be universalized - that is, whether a world in which all engineers disclosed prior-employer project credits only in prefatory sections, while allowing detailed project narratives to stand without attribution, would be consistent with a rational system of professional trust. It would not. The categorical duty of honesty requires that representations be structured so that the audience receives accurate information at the point of decision, not merely at a point in the document where the information is technically present but practically obscured. Engineer B's disclosure satisfies a weak non-falsification duty but falls short of the stronger duty of affirmative transparency that deontological ethics demands of licensed professionals whose representations directly affect client procurement decisions. The Board's finding of no NSPE Code violation reflects a minimum compliance threshold, not a deontological endorsement of the practice.

conclusionNumber 204
conclusionText From a deontological perspective, Engineer B's prefatory-only attribution disclosure does not fully satisfy a categorical duty of honesty in professional representations. A Kantian analysis would ask ...
conclusionType question_response
mentionedEntities {"obligations": ["Engineer B Maximum Clarity Attribution State Q Proposal", "Engineer B Project-Level Attribution State Z Proposal"], "principles": ["Honesty in Professional Representations...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_205 individual committed

From a consequentialist perspective, the partial attribution disclosure practice adopted by XYZ Engineers produces a net harm to the competitive fairness of the procurement process and to the integrity of the profession, even if it does not rise to the level of an NSPE Code violation under the State Q standard. The competitive advantage gained by XYZ Engineers through a proposal structure that allows Engineer B's prior-employer projects to function as apparent independent credentials - without per-project attribution reminders - is an advantage that competing firms who provide more granular attribution do not enjoy. Firms that fully comply with the spirit of attribution requirements bear a disclosure cost (potential client skepticism about the depth of in-house experience) that XYZ Engineers partially avoids through its disclosure architecture. Over time, if this practice were normalized, it would create a race-to-minimum-disclosure dynamic that degrades the informational quality of qualification proposals across the profession. The consequentialist calculus therefore supports the stricter State Z approach as producing better aggregate outcomes for clients, competing firms, and the profession - and suggests that the NSPE Code's current standard may be insufficiently calibrated to prevent this form of structural misleading.

conclusionNumber 205
conclusionText From a consequentialist perspective, the partial attribution disclosure practice adopted by XYZ Engineers produces a net harm to the competitive fairness of the procurement process and to the integrit...
conclusionType question_response
mentionedEntities {"principles": ["Fairness in Professional Competition Invoked By Engineer A ABC Consultants", "Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q",...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_206 individual committed

From a virtue ethics perspective, Engineer B did not fully demonstrate the professional integrity and intellectual honesty expected of a licensed engineer. A virtuous engineer - one who has internalized the character traits of honesty, transparency, and respect for clients as rational decision-makers - would not structure a qualifications proposal in a way that is technically transparent at the document level but practically obscure at the project-description level where evaluators focus their attention. The virtue ethics standard asks not merely whether Engineer B avoided lying, but whether Engineer B acted as a person of good professional character would act. A person of good professional character, aware that clients reading lengthy proposal narratives may not carry forward a prefatory attribution notice into their evaluation of each project, would take affirmative steps to ensure that the attribution was visible at the point of evaluation. Engineer B's approach reflects a compliance-minimizing orientation rather than a virtue-maximizing one, and while it may satisfy the minimum threshold for avoiding an NSPE Code violation, it falls short of the aspirational standard of professional integrity that the Code is designed to cultivate.

conclusionNumber 206
conclusionText From a virtue ethics perspective, Engineer B did not fully demonstrate the professional integrity and intellectual honesty expected of a licensed engineer. A virtuous engineer — one who has internaliz...
conclusionType question_response
mentionedEntities {"principles": ["Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects", "Honesty in Professional Representations Applied to Engineer B Attribution", "Transparency...
citedProvisions 4 items
answersQuestions 1 items
Conclusion_207 individual committed

From a virtue ethics perspective, the licensing regime's mandatory competitor-reporting obligation presents a genuine tension between professional solidarity and public protection, but that tension does not undermine the obligation's legitimacy. The virtue of professional solidarity - which would counsel engineers to resolve ambiguous situations in favor of colleagues rather than reporting them to regulatory authorities - is a real professional virtue, but it is subordinate to the more fundamental virtues of honesty and public protection when a genuine violation is at stake. Engineer A's decision to report to the State Z board, where a specific and clear rule violation existed, reflects appropriate motivational integrity only if Engineer A's primary concern was the integrity of the qualification proposal process and the protection of clients from misleading representations - not the elimination of a competitor. The case facts suggest that Engineer A conducted a careful, jurisdiction-specific analysis and declined to report where no clear violation existed (State Q), which is consistent with good-faith application of the reporting obligation. However, the virtue ethics framework would require Engineer A to honestly examine whether the decision to report was driven by genuine concern for professional standards or by competitive self-interest - and to refrain from reporting if the honest answer is the latter. The licensing system is not designed to be an instrument of competitive strategy, and a virtuous engineer would use it only when the public protection rationale is genuine and primary.

conclusionNumber 207
conclusionText From a virtue ethics perspective, the licensing regime's mandatory competitor-reporting obligation presents a genuine tension between professional solidarity and public protection, but that tension do...
conclusionType question_response
mentionedEntities {"constraints": ["Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State...
citedProvisions 1 items
answersQuestions 1 items
Conclusion_208 individual committed

The counterfactual in which XYZ Engineers had included attribution notices adjacent to each project description throughout the proposal body would almost certainly have led the Board to the same conclusion of no NSPE Code violation - and indeed would have represented a more clearly compliant practice. The Board's conclusion that the prefatory notice was sufficient to avoid a violation under the NSPE Code and State Q rules rested on the finding that the notice was present and identifiable, not that it was optimally placed. Had the attribution appeared at the project-description level, the case for compliance would have been even stronger, and the ambiguity that gave rise to Engineer A's concern would have been eliminated. This counterfactual therefore confirms that the Board's conclusion was a minimum-threshold determination: the prefatory notice was just sufficient to avoid a violation, but project-level attribution would have been the clearly preferable practice. The counterfactual also reveals that the NSPE Code's honesty standard under Section II.5.a does not affirmatively require project-level attribution - it only prohibits misrepresentation - which is the gap that State Z's more specific rules were designed to close.

conclusionNumber 208
conclusionText The counterfactual in which XYZ Engineers had included attribution notices adjacent to each project description throughout the proposal body would almost certainly have led the Board to the same concl...
conclusionType question_response
mentionedEntities {"principles": ["Transparency Principle Invoked By XYZ Engineers Prefatory Notice", "Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q", "Proportionality...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_209 individual committed

The counterfactual in which State Q's licensing rules were as specific as State Z's - requiring attribution information to appear next to each individual project listing - would have reversed the Board's conclusion on Question 2 with respect to State Q. Under that scenario, XYZ Engineers' prefatory-only attribution structure would have constituted a clear violation of State Q rules, and Engineer A would have had an obligation to report to the State Q board as well. This counterfactual is analytically important because it demonstrates that the Board's conclusion on the reporting obligation is entirely dependent on the jurisdiction-specific content of the applicable licensing rules, not on the NSPE Code of Ethics alone. The NSPE Code's general prohibition on misrepresentation of qualifications was insufficient to establish a clear violation in State Q; it was only the specific, granular language of State Z's rules that created the unambiguous violation triggering the mandatory reporting obligation. This reveals a structural gap: engineers practicing in jurisdictions with less specific rules receive less protection from the kind of partial-disclosure practices at issue here, and the NSPE Code does not fill that gap.

conclusionNumber 209
conclusionText The counterfactual in which State Q's licensing rules were as specific as State Z's — requiring attribution information to appear next to each individual project listing — would have reversed the Boar...
conclusionType question_response
mentionedEntities {"principles": ["Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review", "Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q",...
citedProvisions 1 items
answersQuestions 1 items
Conclusion_210 individual committed

The counterfactual in which Engineer A had relied solely on the NSPE Code of Ethics - without reviewing the jurisdiction-specific licensing rules of State Q and State Z - reveals a critical gap in the Code's ability to capture jurisdiction-specific professional misconduct. Under the NSPE Code alone, the analysis of XYZ Engineers' proposal practice would have been inconclusive: the prefatory attribution notice arguably avoids outright falsification under Section II.5.a, and the Code does not specify the granularity of attribution required. Engineer A would likely have concluded that the practice was ethically questionable but not clearly prohibited - and would not have identified the specific State Z rule violation that triggered the mandatory reporting obligation. This scenario confirms that the NSPE Code functions as a floor of general ethical principles, not as a comprehensive substitute for jurisdiction-specific licensing rules. Engineers practicing across multiple jurisdictions have an affirmative obligation to identify and apply the specific rules of each jurisdiction - an obligation that the Code itself acknowledges through Section III.8.a's requirement to conform with state registration laws. The case therefore stands as a practical illustration of why multi-jurisdictional practice requires jurisdiction-specific rule review, and why reliance on the NSPE Code alone is insufficient for compliance purposes.

conclusionNumber 210
conclusionText The counterfactual in which Engineer A had relied solely on the NSPE Code of Ethics — without reviewing the jurisdiction-specific licensing rules of State Q and State Z — reveals a critical gap in the...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Multi-Jurisdiction Licensing Rule Identification", "Engineer A Multi-Jurisdiction Ethics Review State Q State Z Capability"], "principles": ["Jurisdiction-Specific...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_211 individual committed

The divergence between State Q's general misrepresentation prohibition and State Z's granular project-level attribution requirement reveals that the NSPE Code's honesty standard under Section II.5.a is insufficiently calibrated to address the specific risks of cross-employer project credit attribution in multi-jurisdictional practice. The Code prohibits falsification and misrepresentation but does not specify the structural requirements for attribution disclosures - leaving engineers and firms free to adopt disclosure architectures that are technically non-false but practically obscure. State Z's legislature and licensing board identified this gap and addressed it through specific rules requiring attribution information to appear adjacent to each project listing. The NSPE Code has not made a parallel adjustment. This divergence suggests that the Code's honesty standard, while adequate for clear cases of falsification, is not adequate to govern the more subtle forms of misleading representation that arise from disclosure architecture choices. The Board's conclusion that XYZ Engineers' practice was not unethical under the NSPE Code, while correct as a matter of minimum compliance, should prompt the NSPE to consider whether the Code's attribution provisions need to be updated to reflect the more specific standards that state licensing bodies have found necessary to protect the integrity of the qualification proposal process.

conclusionNumber 211
conclusionText The divergence between State Q's general misrepresentation prohibition and State Z's granular project-level attribution requirement reveals that the NSPE Code's honesty standard under Section II.5.a i...
conclusionType question_response
mentionedEntities {"principles": ["Honesty in Professional Representations Applied to Engineer B Attribution", "Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review",...
citedProvisions 4 items
answersQuestions 2 items
Conclusion_301 individual committed

The Board resolved the tension between the Transparency Principle and Qualification Proposal Attribution Integrity by treating document-level disclosure as sufficient to satisfy the NSPE Code's honesty standard, even when that disclosure was not repeated at the project-description level where evaluators are most likely to focus. This resolution effectively privileges formal transparency - the existence of a prefatory notice - over functional transparency - the practical likelihood that a reader will connect that notice to each individual project description in a lengthy proposal body. The case thereby teaches that the NSPE Code's minimum compliance threshold for honesty in professional representations is calibrated to the document as a whole rather than to the reader's likely cognitive path through it. While this outcome avoids finding a violation under the Code, it leaves an unresolved gap between the aspirational standard of intellectual integrity in authorship, which would demand granular attribution, and the minimum standard the Board was willing to enforce. Practitioners and firms should treat this gap as a reason to adopt project-level attribution as a best practice rather than as a ceiling set by the Board's finding.

conclusionNumber 301
conclusionText The Board resolved the tension between the Transparency Principle and Qualification Proposal Attribution Integrity by treating document-level disclosure as sufficient to satisfy the NSPE Code's honest...
conclusionType principle_synthesis
mentionedEntities {"principles": ["Transparency Principle Invoked By XYZ Engineers Prefatory Notice", "Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q", "Honesty in...
citedProvisions 4 items
answersQuestions 2 items
Conclusion_302 individual committed

The case reveals a structural tension between the Mandatory Competitor Misconduct Reporting Obligation and the Fairness in Professional Competition principle that the Board did not fully resolve. By affirming Engineer A's obligation to report to the State Z board without separately examining whether Engineer A's competitive motivation compromised the integrity of that reporting decision, the Board implicitly treated the reporting duty as categorical - that is, the obligation to report a genuine licensing violation is not diminished or tainted by the reporter's competitive interest in the outcome. This resolution is consistent with a deontological reading of the reporting obligation: if a violation exists, it must be reported regardless of the reporter's motivation. However, the Board's silence on the conflict-of-interest dimension leaves open the consequentialist concern that mandatory reporting rules, when exercised by direct competitors, can function as instruments of competitive harm even when the underlying violation is real. The case teaches that the NSPE Code and state licensing rules prioritize public protection and regulatory integrity over the risk of competitive misuse, but that this prioritization is most defensible when the reported violation is clear and material - as it was under State Z's specific attribution rules - rather than marginal or ambiguous.

conclusionNumber 302
conclusionText The case reveals a structural tension between the Mandatory Competitor Misconduct Reporting Obligation and the Fairness in Professional Competition principle that the Board did not fully resolve. By a...
conclusionType principle_synthesis
mentionedEntities {"constraints": ["Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting", "Conflict of Interest Avoidance Constraint Engineer A Competitor...
citedProvisions 1 items
answersQuestions 3 items
Conclusion_303 individual committed

The most significant principle interaction in this case is the divergence between the Jurisdiction-Specific Ethics Compliance Obligation and the Honesty in Professional Representations principle as operationalized across two regulatory environments. The Board's analysis demonstrates that a single course of conduct - Engineer B's prefatory-only attribution practice - can simultaneously satisfy the NSPE Code's honesty standard and State Q's misrepresentation prohibition while violating State Z's more granular project-level attribution rule. This divergence reveals that the NSPE Code functions as a floor, not a ceiling, for professional honesty, and that jurisdiction-specific rules can impose materially higher standards without creating a logical contradiction with the Code. The practical teaching for multi-jurisdictional practitioners is that compliance with the NSPE Code does not guarantee compliance with all applicable state rules, and that the Jurisdiction-Specific Ethics Compliance Obligation requires independent rule-by-rule analysis in each state of practice. Firms operating across state lines must therefore treat the most demanding applicable jurisdiction's attribution standard as the operative benchmark for proposal preparation, not the most permissive one, if they wish to avoid selective non-compliance. This case also implicitly suggests that the NSPE Code's honesty provisions may benefit from revision to incorporate more explicit guidance on multi-jurisdictional attribution practices, closing the gap between the Code's general standard and the more specific requirements that some states have found necessary to protect clients and competitors alike.

conclusionNumber 303
conclusionText The most significant principle interaction in this case is the divergence between the Jurisdiction-Specific Ethics Compliance Obligation and the Honesty in Professional Representations principle as op...
conclusionType principle_synthesis
mentionedEntities {"principles": ["Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review", "Honesty in Professional Representations Invoked By XYZ Engineers Qualification...
citedProvisions 3 items
answersQuestions 2 items
ethical question 21
Question_1 individual committed

Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?

questionNumber 1
questionText Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
questionType board_explicit
extractionReasoning Parsed from imported case text (no LLM)
Question_2 individual committed

Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?

questionNumber 2
questionText Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
questionType board_explicit
extractionReasoning Parsed from imported case text (no LLM)
Question_101 individual committed

Does Engineer A's status as a direct competitor of XYZ Engineers create a conflict of interest that should have been disclosed or weighed before initiating any reporting action, and does that competitive motivation undermine the legitimacy or objectivity of the reporting obligation?

questionNumber 101
questionText Does Engineer A's status as a direct competitor of XYZ Engineers create a conflict of interest that should have been disclosed or weighed before initiating any reporting action, and does that competit...
questionType implicit
mentionedEntities {"constraints": ["Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State...
relatedProvisions 1 items
Question_102 individual committed

To what extent does XYZ Engineers bear institutional ethical responsibility for Engineer B's attribution practices in qualification proposals, and should the Board's analysis have separately evaluated the firm's culpability distinct from Engineer B's individual conduct?

questionNumber 102
questionText To what extent does XYZ Engineers bear institutional ethical responsibility for Engineer B's attribution practices in qualification proposals, and should the Board's analysis have separately evaluated...
questionType implicit
mentionedEntities {"constraints": ["Prior-Employer Attribution Completeness Constraint XYZ Engineers Engineer B State Q Proposals", "Prior-Employer Attribution Completeness Constraint XYZ Engineers Engineer B State...
relatedProvisions 3 items
Question_103 individual committed

Does the prefatory notice of prior-employer attribution placed only at the beginning of Engineer B's individual qualification section - but not repeated within each project description - satisfy the spirit of honesty and transparency required by the NSPE Code of Ethics, even if it technically avoids outright falsification?

questionNumber 103
questionText Does the prefatory notice of prior-employer attribution placed only at the beginning of Engineer B's individual qualification section — but not repeated within each project description — satisfy the s...
questionType implicit
mentionedEntities {"principles": ["Transparency Principle Invoked By XYZ Engineers Prefatory Notice", "Honesty in Professional Representations Applied to Engineer B Attribution", "Intellectual Integrity in...
relatedProvisions 3 items
Question_104 individual committed

What standard of client sophistication should be assumed when evaluating whether a proposal practice is misleading - are government procurement clients expected to read prefatory attribution notices carefully, and does that assumption affect the ethical analysis of Engineer B's disclosure approach?

questionNumber 104
questionText What standard of client sophistication should be assumed when evaluating whether a proposal practice is misleading — are government procurement clients expected to read prefatory attribution notices c...
questionType implicit
mentionedEntities {"principles": ["Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q", "Honesty in Professional Representations Invoked By XYZ Engineers Qualification...
relatedProvisions 1 items
Question_201 individual committed

Does the Transparency Principle invoked by XYZ Engineers' prefatory notice conflict with the Qualification Proposal Attribution Integrity principle, given that a single prefatory disclosure may create an appearance of transparency while still allowing individual project descriptions to function as misleading representations of Engineer B's independent authorship?

questionNumber 201
questionText Does the Transparency Principle invoked by XYZ Engineers' prefatory notice conflict with the Qualification Proposal Attribution Integrity principle, given that a single prefatory disclosure may create...
questionType principle_tension
mentionedEntities {"principles": ["Transparency Principle Invoked By XYZ Engineers Prefatory Notice", "Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q", "Qualification...
relatedProvisions 4 items
Question_202 individual committed

Does the Mandatory Competitor Misconduct Reporting Obligation conflict with the Fairness in Professional Competition principle when the engineer initiating the report stands to gain a competitive advantage from the investigation, and how should the ethics framework resolve the risk that a legitimate reporting duty becomes an instrument of competitive harm?

questionNumber 202
questionText Does the Mandatory Competitor Misconduct Reporting Obligation conflict with the Fairness in Professional Competition principle when the engineer initiating the report stands to gain a competitive adva...
questionType principle_tension
mentionedEntities {"constraints": ["Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State...
relatedProvisions 1 items
Question_203 individual committed

Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter state rule (State Z) is simultaneously deemed not unethical under the NSPE Code - and does this divergence suggest that the NSPE Code's honesty standard is inadequately calibrated to multi-jurisdictional practice?

questionNumber 203
questionText Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter st...
questionType principle_tension
mentionedEntities {"principles": ["Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review", "Honesty in Professional Representations Applied to Engineer B Attribution",...
relatedProvisions 3 items
Question_204 individual committed

Does the Intellectual Integrity in Authorship principle - which would favor granular, project-level attribution of Engineer B's prior-employer work - conflict with the Proportionality Analysis applied to the State Q proposal, where the Board found the partial disclosure sufficient to avoid an ethical violation, and does this tension reveal an unresolved gap between aspirational professional norms and minimum compliance thresholds?

questionNumber 204
questionText Does the Intellectual Integrity in Authorship principle — which would favor granular, project-level attribution of Engineer B's prior-employer work — conflict with the Proportionality Analysis applied...
questionType principle_tension
mentionedEntities {"principles": ["Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects", "Proportionality Analysis Applied to State Q Proposal", "Qualification Proposal Attribution...
relatedProvisions 3 items
Question_301 individual committed

From a deontological perspective, did Engineer B fulfill a categorical duty of honesty in professional representations by disclosing prior-employer attribution only in prefatory sections of qualifications proposals rather than at the project-description level, regardless of whether clients were actually misled?

questionNumber 301
questionText From a deontological perspective, did Engineer B fulfill a categorical duty of honesty in professional representations by disclosing prior-employer attribution only in prefatory sections of qualificat...
questionType theoretical
mentionedEntities {"obligations": ["Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States", "Project-Level Attribution Obligation XYZ Engineers Engineer B State Z...
relatedProvisions 4 items
Question_302 individual committed

From a consequentialist perspective, did the partial attribution disclosure practice adopted by XYZ Engineers produce net harm to clients, competing firms, and the profession - even if it technically avoided outright misrepresentation under State Q rules - when weighed against the competitive advantage gained?

questionNumber 302
questionText From a consequentialist perspective, did the partial attribution disclosure practice adopted by XYZ Engineers produce net harm to clients, competing firms, and the profession — even if it technically ...
questionType theoretical
mentionedEntities {"constraints": ["Non-Deception Constraint XYZ Engineers Engineer B Qualification Proposals"], "principles": ["Fairness in Professional Competition Invoked By Engineer A ABC Consultants",...
relatedProvisions 3 items
Question_303 individual committed

From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of a licensed engineer when structuring qualifications proposals in a way that was technically transparent at the document level but potentially obscure at the project-description level where clients are most likely to focus their evaluation?

questionNumber 303
questionText From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of a licensed engineer when structuring qualifications proposals in a way that...
questionType theoretical
mentionedEntities {"capabilities": ["Engineer B Qualification Proposal Attribution Accuracy Deficiency", "Engineer B Proposal Clarity Self-Assessment State Q"], "principles": ["Transparency Principle Invoked By XYZ...
relatedProvisions 3 items
Question_304 individual committed

From a deontological perspective, does Engineer A's status as a direct competitor of XYZ Engineers create a conflicting duty - between the obligation to report known or suspected licensing violations and the duty to avoid using the reporting mechanism as an instrument of competitive self-interest - and how should that tension be resolved when the underlying violation is genuine?

questionNumber 304
questionText From a deontological perspective, does Engineer A's status as a direct competitor of XYZ Engineers create a conflicting duty — between the obligation to report known or suspected licensing violations ...
questionType theoretical
mentionedEntities {"constraints": ["Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State...
relatedProvisions 2 items
Question_305 individual committed

From a consequentialist perspective, does the mandatory reporting obligation imposed on Engineer A by both states' licensing rules produce better aggregate outcomes for the profession and the public when enforced even in cases where the reporting engineer is a direct commercial competitor, or does it risk weaponizing the licensing system against legitimate competitive behavior?

questionNumber 305
questionText From a consequentialist perspective, does the mandatory reporting obligation imposed on Engineer A by both states' licensing rules produce better aggregate outcomes for the profession and the public w...
questionType theoretical
mentionedEntities {"obligations": ["Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Z", "Engineer A Jurisdiction-Specific Threshold Analysis State Z Reporting Required"],...
relatedProvisions 2 items
Question_306 individual committed

From a virtue ethics perspective, does a licensing regime that requires engineers to report competitors' violations cultivate or undermine the virtue of professional solidarity, and did Engineer A act with the appropriate motivational integrity - concern for public protection rather than competitive advantage - when deciding to report to the State Z board?

questionNumber 306
questionText From a virtue ethics perspective, does a licensing regime that requires engineers to report competitors' violations cultivate or undermine the virtue of professional solidarity, and did Engineer A act...
questionType theoretical
mentionedEntities {"actions": ["Engineer A Reports to State Z Board"], "principles": ["Professional Accountability Invoked By Engineer A Reporting Consideration", "Mandatory Competitor Misconduct Reporting Applied...
relatedProvisions 2 items
Question_401 individual committed

If XYZ Engineers had included the prior-employer attribution notice not only in the prefatory individual qualification section but also immediately adjacent to each project description throughout the proposal body, would the Board have reached the same conclusion that no NSPE Code violation occurred, or would that level of disclosure have been required to satisfy the honesty standard under Section II.5.a?

questionNumber 401
questionText If XYZ Engineers had included the prior-employer attribution notice not only in the prefatory individual qualification section but also immediately adjacent to each project description throughout the ...
questionType counterfactual
mentionedEntities {"obligations": ["Project-Level Attribution Obligation XYZ Engineers Engineer B State Z Proposals", "Engineer B Maximum Clarity Attribution State Q Proposal"], "resources": ["NSPE Code of Ethics -...
relatedProvisions 3 items
Question_402 individual committed

What if Engineer B's prior projects had involved proprietary design concepts owned by the previous employer - would the Board's analysis under NSPE Code Section III.9 have shifted, and would XYZ Engineers' proposal practice have been found unethical even under the more permissive State Q standard?

questionNumber 402
questionText What if Engineer B's prior projects had involved proprietary design concepts owned by the previous employer — would the Board's analysis under NSPE Code Section III.9 have shifted, and would XYZ Engin...
questionType counterfactual
mentionedEntities {"principles": ["Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects", "Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q"],...
relatedProvisions 2 items
Question_403 individual committed

If State Q's licensing rules had been as specific as State Z's - requiring attribution information to appear next to each individual project listing rather than only in a prefatory section - would Engineer A have had a clear obligation to report XYZ Engineers' conduct to the State Q board as well, and would the Board's conclusion on Question 2 have been reversed?

questionNumber 403
questionText If State Q's licensing rules had been as specific as State Z's — requiring attribution information to appear next to each individual project listing rather than only in a prefatory section — would Eng...
questionType counterfactual
mentionedEntities {"obligations": ["Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Q", "Engineer A Jurisdiction-Specific Threshold Analysis State Q No Reporting"], "resources":...
relatedProvisions 1 items
Question_404 individual committed

What if Engineer A had filed the report to the State Z board anonymously rather than under their own name - would the mandatory reporting obligation still be considered fulfilled, and would the competitive-interest neutrality concern be mitigated or exacerbated by anonymous filing?

questionNumber 404
questionText What if Engineer A had filed the report to the State Z board anonymously rather than under their own name — would the mandatory reporting obligation still be considered fulfilled, and would the compet...
questionType counterfactual
mentionedEntities {"constraints": ["Anonymous Reporting Adequacy Constraint Engineer A State Q and State Z Licensing Boards", "Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A...
relatedProvisions 2 items
Question_405 individual committed

If Engineer A had chosen not to review the specific licensing board rules of either state and had relied solely on the NSPE Code of Ethics to assess XYZ Engineers' conduct, would Engineer A have correctly identified the State Z violation, and does this scenario reveal a gap in the NSPE Code's ability to capture jurisdiction-specific professional misconduct?

questionNumber 405
questionText If Engineer A had chosen not to review the specific licensing board rules of either state and had relied solely on the NSPE Code of Ethics to assess XYZ Engineers' conduct, would Engineer A have corre...
questionType counterfactual
mentionedEntities {"actions": ["Engineer A Reviews Applicable Rules"], "capabilities": ["Engineer A Multi-Jurisdiction Licensing Rule Identification", "Engineer A Multi-Jurisdiction Ethics Review State Q State Z...
relatedProvisions 2 items
Phase 2E: Rich Analysis
48 48 committed
causal normative link 7

Engineer B's completion of projects under prior employment establishes the factual basis for all subsequent attribution obligations, as the work product legally and ethically belongs to the prior firm and clients, constraining how credit may later be claimed in XYZ Engineers' proposals.

URI case-19#CausalLink_1
action id case-19#Engineer_B_Completes_Prior_Projects
action label Engineer B Completes Prior Projects
fulfills obligations 2 items
guided by principles 3 items
constrained by 3 items
agent role http://proethica.org/ontology/case/19#Engineer_B_Multi-State_Project_Manager
reasoning Engineer B's completion of projects under prior employment establishes the factual basis for all subsequent attribution obligations, as the work product legally and ethically belongs to the prior firm...
confidence 0.82
CausalLink_XYZ Hires Engineer B individual committed

XYZ Engineers' decision to hire Engineer B is the precipitating event that creates the cross-employer attribution problem, triggering the firm's obligations to comply with State Q and State Z attribution rules whenever Engineer B's prior-employer projects are featured in qualification proposals.

URI case-19#CausalLink_2
action id case-19#XYZ_Hires_Engineer_B
action label XYZ Hires Engineer B
guided by principles 3 items
constrained by 3 items
agent role http://proethica.org/ontology/case/19#XYZ_Engineers_Competing_Firm
reasoning XYZ Engineers' decision to hire Engineer B is the precipitating event that creates the cross-employer attribution problem, triggering the firm's obligations to comply with State Q and State Z attribut...
confidence 0.78

XYZ Engineers' practice of featuring Engineer B's prior-employer projects with only partial attribution disclosure simultaneously violates multiple project-level attribution and misrepresentation obligations under both State Q and State Z rules, while the degree of violation differs by jurisdiction - creating the ambiguity that drives Engineer A's subsequent review.

URI case-19#CausalLink_3
action id case-19#Partial_Attribution_Disclosure_in_Proposals
action label Partial Attribution Disclosure in Proposals
violates obligations 12 items
guided by principles 5 items
constrained by 8 items
agent role http://proethica.org/ontology/case/19#Engineer_B_Prior-Firm_Project_Credit_Engineer
reasoning XYZ Engineers' practice of featuring Engineer B's prior-employer projects with only partial attribution disclosure simultaneously violates multiple project-level attribution and misrepresentation obli...
confidence 0.91

Engineer A's investigation of XYZ Engineers' marketing practice fulfills the multi-jurisdiction ethics review obligation and proportionate characterization obligation, while being constrained by the need to neutralize competitive self-interest and apply jurisdiction-specific thresholds before any reporting decision is made.

URI case-19#CausalLink_4
action id case-19#Engineer_A_Investigates_Marketing_Practice
action label Engineer A Investigates Marketing Practice
fulfills obligations 6 items
guided by principles 6 items
constrained by 6 items
agent role http://proethica.org/ontology/case/19#Engineer_A_Competing_Engineering_Firm_Employee
reasoning Engineer A's investigation of XYZ Engineers' marketing practice fulfills the multi-jurisdiction ethics review obligation and proportionate characterization obligation, while being constrained by the n...
confidence 0.89

Engineer A's review of State Q and State Z licensing rules is the analytical step that operationalizes the multi-jurisdiction ethics review obligation, enabling the discovery of the differential stringency between the two states' attribution requirements and thereby determining which jurisdiction triggers a mandatory reporting obligation.

URI case-19#CausalLink_5
action id case-19#Engineer_A_Reviews_Applicable_Rules
action label Engineer A Reviews Applicable Rules
fulfills obligations 5 items
guided by principles 7 items
constrained by 6 items
agent role http://proethica.org/ontology/case/19#Engineer_A_Multi-Jurisdiction_Ethics_Reviewer
reasoning Engineer A's review of State Q and State Z licensing rules is the analytical step that operationalizes the multi-jurisdiction ethics review obligation, enabling the discovery of the differential strin...
confidence 0.92

Engineer A fulfills the mandatory competitor misconduct reporting obligation specific to State Z by reporting XYZ Engineers' and Engineer B's non-compliant attribution practices to the State Z licensing board, guided by the principle that clear jurisdictional rule violations trigger a reporting duty, while constrained by the need to act without competitive self-interest and to ensure the complaint meets the anonymous reporting adequacy standard established by BER Case 02-11.

URI case-19#CausalLink_6
action id case-19#Engineer_A_Reports_to_State_Z_Board
action label Engineer A Reports to State Z Board
fulfills obligations 6 items
guided by principles 9 items
constrained by 7 items
agent role http://proethica.org/ontology/case/19#Engineer_A_Jurisdiction-Specific_Misconduct_Reporter
reasoning Engineer A fulfills the mandatory competitor misconduct reporting obligation specific to State Z by reporting XYZ Engineers' and Engineer B's non-compliant attribution practices to the State Z licensi...
confidence 0.92

Engineer A declines to report to the State Q board because the proportionality analysis reveals that State Q's rules do not impose the same specific attribution requirements as State Z, meaning the ambiguity in XYZ Engineers' State Q proposals does not clearly cross the threshold for a reportable violation, though this decision creates tension with the general competitor misconduct reporting obligation and must be free from competitive self-interest to remain ethically defensible.

URI case-19#CausalLink_7
action id case-19#Engineer_A_Declines_State_Q_Report
action label Engineer A Declines State Q Report
fulfills obligations 5 items
violates obligations 1 items
guided by principles 7 items
constrained by 6 items
agent role http://proethica.org/ontology/case/19#Engineer_A_Jurisdiction-Specific_Misconduct_Reporter
reasoning Engineer A declines to report to the State Q board because the proportionality analysis reveals that State Q's rules do not impose the same specific attribution requirements as State Z, meaning the am...
confidence 0.88
question emergence 21
QuestionEmergence_1 individual committed

This question arose because Engineer B's partial attribution practice sits at the boundary between permissible self-promotion and prohibited misrepresentation of qualifications, where the NSPE Code's honesty and credit-attribution obligations pull in different directions depending on how a proposal reader would interpret the disclosure structure. The ambiguity in what 'adequate' attribution means under the Code, absent explicit project-level labeling, made the ethical status of the technique genuinely contestable.

URI case-19#Q1
question uri case-19#Q1
question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
data events 3 items
data actions 3 items
involves roles 3 items
competing warrants 2 items
data warrant tension Engineer B's act of listing prior-employer projects under a prefatory-only attribution notice simultaneously triggers the warrant requiring full honesty in professional representations and the warrant...
competing claims One warrant concludes the prefatory notice is sufficient to satisfy honesty obligations, while the competing warrant concludes that project-level attribution is required to avoid misrepresentation of ...
rebuttal conditions Uncertainty arises because if a reasonable evaluator reading the proposal would not be misled into believing Engineer B personally led all listed projects independent of any firm, the misrepresentatio...
emergence narrative This question arose because Engineer B's partial attribution practice sits at the boundary between permissible self-promotion and prohibited misrepresentation of qualifications, where the NSPE Code's ...
confidence 0.88
QuestionEmergence_2 individual committed

This question arose because Engineer A's multi-jurisdiction review revealed that State Q and State Z impose different standards, meaning the same conduct that clearly triggers a reporting obligation in State Z may fall below the actionable threshold in State Q, making the reporting obligation contingent rather than absolute. The tension between the universal NSPE reporting norm and jurisdiction-specific rule stringency created genuine uncertainty about whether Engineer A's duty to report extended to the State Q Board.

URI case-19#Q2
question uri case-19#Q2
question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
data events 4 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A's discovery that State Q's rules may not clearly prohibit Engineer B's attribution practice triggers both the general NSPE warrant mandating reporting of unethical or illegal practice and t...
competing claims The general reporting warrant concludes Engineer A must report any apparent ethical violation to the State Q Board, while the jurisdiction-specific threshold warrant concludes that where State Q's rul...
rebuttal conditions The reporting obligation is rebutted if State Q's Rules of Professional Conduct do not independently prohibit the attribution practice at issue, because the NSPE Code's reporting obligation is conditi...
emergence narrative This question arose because Engineer A's multi-jurisdiction review revealed that State Q and State Z impose different standards, meaning the same conduct that clearly triggers a reporting obligation i...
confidence 0.87
QuestionEmergence_3 individual committed

This question arose because the structural fact of Engineer A's competitive relationship with XYZ Engineers introduces a motivational ambiguity that the Toulmin framework cannot resolve through the reporting-obligation warrant alone - the same action (filing a complaint) can be simultaneously ethically required and ethically suspect depending on the reporter's dominant motivation. The absence of any disclosure or recusal mechanism in the NSPE reporting framework for competitor-reporters left this tension unresolved and made the question unavoidable.

URI case-19#Q3
question uri case-19#Q3
question text Does Engineer A's status as a direct competitor of XYZ Engineers create a conflict of interest that should have been disclosed or weighed before initiating any reporting action, and does that competit...
data events 3 items
data actions 3 items
involves roles 5 items
competing warrants 2 items
data warrant tension The fact that Engineer A is a direct competitor of XYZ Engineers simultaneously activates the warrant obligating engineers to report unethical practice regardless of who commits it and the constraint ...
competing claims The reporting-obligation warrant concludes that Engineer A's competitive status is irrelevant to the validity of the report because the public interest in licensing board enforcement supersedes privat...
rebuttal conditions The conflict-of-interest rebuttal condition is strongest if Engineer A's report was selectively filed only where it would harm XYZ Engineers competitively rather than where the ethical violation was c...
emergence narrative This question arose because the structural fact of Engineer A's competitive relationship with XYZ Engineers introduces a motivational ambiguity that the Toulmin framework cannot resolve through the re...
confidence 0.85
QuestionEmergence_4 individual committed

This question arose because the BER analysis focused primarily on Engineer B's individual conduct without separately adjudicating XYZ Engineers' institutional role in producing and submitting the proposals, leaving a structural gap in the ethical accountability framework. The firm's active role in marketing - hiring Engineer B specifically for his prior project portfolio and publishing proposals under the firm's name - created a plausible basis for independent institutional culpability that the original analysis did not fully address.

URI case-19#Q4
question uri case-19#Q4
question text To what extent does XYZ Engineers bear institutional ethical responsibility for Engineer B's attribution practices in qualification proposals, and should the Board's analysis have separately evaluated...
data events 3 items
data actions 2 items
involves roles 5 items
competing warrants 2 items
data warrant tension XYZ Engineers' institutional act of publishing qualification proposals featuring Engineer B's prior-employer projects under a prefatory-only attribution notice triggers both the warrant holding the fi...
competing claims The institutional-responsibility warrant concludes that XYZ Engineers bears independent culpability for approving and distributing misleading qualification proposals regardless of Engineer B's individ...
rebuttal conditions XYZ Engineers' institutional responsibility is rebutted if the firm had no reasonable means of knowing that Engineer B's prior-employer projects were presented ambiguously, or if the firm relied in go...
emergence narrative This question arose because the BER analysis focused primarily on Engineer B's individual conduct without separately adjudicating XYZ Engineers' institutional role in producing and submitting the prop...
confidence 0.83
QuestionEmergence_5 individual committed

This question arose because the NSPE Code's honesty provisions do not specify the granularity of attribution required within a multi-project qualification section, leaving a gap between the letter of the non-falsification rule and the spirit of full transparency that the prefatory-notice format exploits. The structural ambiguity - whether disclosure must be continuous and proximate or merely present somewhere in the document - made it genuinely uncertain whether Engineer B's approach satisfied the Code's deeper normative purpose even if it avoided a technical violation.

URI case-19#Q5
question uri case-19#Q5
question text Does the prefatory notice of prior-employer attribution placed only at the beginning of Engineer B's individual qualification section — but not repeated within each project description — satisfy the s...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension The single prefatory notice placed at the opening of Engineer B's qualification section simultaneously activates the warrant that any disclosure avoiding outright falsification satisfies the honesty s...
competing claims The technical-compliance warrant concludes that a prefatory notice is sufficient because it places the reader on notice before any project descriptions are encountered, satisfying the non-falsificatio...
rebuttal conditions The spirit-of-transparency warrant is rebutted if the proposal's format and context make it objectively implausible that a sophisticated procurement evaluator would read any individual project descrip...
emergence narrative This question arose because the NSPE Code's honesty provisions do not specify the granularity of attribution required within a multi-project qualification section, leaving a gap between the letter of ...
confidence 0.86
QuestionEmergence_6 individual committed

This question emerged because the ethical analysis of Engineer B's disclosure approach depends entirely on an empirical assumption - client sophistication - that the NSPE Code and BER precedents do not explicitly resolve, leaving the warrant authorizing the move from 'prefatory notice exists' to 'no misrepresentation occurred' contestable on factual grounds. The attribution ambiguity created by XYZ Engineers' proposal format forced the question of whether the disclosure standard should be calibrated to the most careful or the most typical reader in a government procurement context.

URI case-19#Q6
question uri case-19#Q6
question text What standard of client sophistication should be assumed when evaluating whether a proposal practice is misleading — are government procurement clients expected to read prefatory attribution notices c...
data events 3 items
data actions 2 items
involves roles 4 items
competing warrants 2 items
data warrant tension The prefatory attribution notice in XYZ Engineers' proposals simultaneously triggers the Honesty in Professional Representations warrant — which demands that disclosures be sufficient to prevent a rea...
competing claims The Honesty warrant concludes that disclosure is only adequate if a government procurement client would reliably connect the prefatory notice to each individual project description, while the Proporti...
rebuttal conditions Uncertainty arises because if government procurement clients are shown to routinely overlook or misapply prefatory notices when evaluating individual project credentials — whether through institutiona...
emergence narrative This question emerged because the ethical analysis of Engineer B's disclosure approach depends entirely on an empirical assumption — client sophistication — that the NSPE Code and BER precedents do no...
confidence 0.82
QuestionEmergence_7 individual committed

This question arose because XYZ Engineers' prefatory notice strategy exploits a structural gap between the form of transparency and its functional effect: a disclosure that satisfies the letter of the Transparency Principle may simultaneously violate the spirit of Attribution Integrity if the proposal architecture allows individual project entries to operate as self-contained representations of Engineer B's independent authorship. The tension between these two principles is not resolved by the NSPE Code's general honesty provisions, which do not specify the granularity of attribution required in multi-project qualification proposals.

URI case-19#Q7
question uri case-19#Q7
question text Does the Transparency Principle invoked by XYZ Engineers' prefatory notice conflict with the Qualification Proposal Attribution Integrity principle, given that a single prefatory disclosure may create...
data events 2 items
data actions 2 items
involves roles 3 items
competing warrants 2 items
data warrant tension The single prefatory attribution notice triggers both the Transparency Principle — which treats any disclosure of prior-employer origin as sufficient to satisfy honesty norms — and the Qualification P...
competing claims The Transparency Principle concludes that XYZ Engineers acted ethically by including a prefatory notice that technically informs readers of the attribution context, while the Attribution Integrity pri...
rebuttal conditions The rebuttal condition that creates uncertainty is whether the proposal's physical or digital format — including pagination, section breaks, and reader navigation patterns — makes it reasonably forese...
emergence narrative This question arose because XYZ Engineers' prefatory notice strategy exploits a structural gap between the form of transparency and its functional effect: a disclosure that satisfies the letter of the...
confidence 0.85
QuestionEmergence_8 individual committed

This question emerged because the NSPE Code's reporting obligation was designed to protect the public from unethical practitioners, but its application by a direct competitor in a contested procurement context creates a structural conflict-of-interest that the Code does not explicitly address, leaving unresolved whether the legitimacy of a reporting duty can be compromised by the reporter's stake in the outcome. The State Z violation established by differential rule discovery forced the question of whether the ethics framework has adequate mechanisms to prevent a legitimate professional obligation from functioning as a competitive weapon.

URI case-19#Q8
question uri case-19#Q8
question text Does the Mandatory Competitor Misconduct Reporting Obligation conflict with the Fairness in Professional Competition principle when the engineer initiating the report stands to gain a competitive adva...
data events 3 items
data actions 3 items
involves roles 5 items
competing warrants 2 items
data warrant tension Engineer A's discovery of XYZ Engineers' State Z violation simultaneously activates the Mandatory Competitor Misconduct Reporting Obligation — which requires reporting engineers believed to be engaged...
competing claims The Mandatory Reporting warrant concludes that Engineer A must report to the State Z board because the public interest in licensing integrity is paramount and the reporter's competitive interest is le...
rebuttal conditions The rebuttal condition generating uncertainty is whether the ethics framework can distinguish between a report motivated primarily by genuine professional accountability concerns and one motivated pri...
emergence narrative This question emerged because the NSPE Code's reporting obligation was designed to protect the public from unethical practitioners, but its application by a direct competitor in a contested procuremen...
confidence 0.87
QuestionEmergence_9 individual committed

This question arose because the simultaneous application of State Q rules, State Z rules, and the NSPE Code to identical conduct produced three different normative outcomes, revealing that the NSPE Code's honesty standard does not function as a reliable ethical baseline across all U.S. jurisdictions and that multi-jurisdictional engineers face an unresolved structural problem when national professional norms and state licensing rules diverge. The differential state rules discovery forced the question of whether the NSPE Code's adequacy as an ethical standard should be evaluated against the most demanding or the most permissive jurisdictional rule applicable to the engineer's practice.

URI case-19#Q9
question uri case-19#Q9
question text Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter st...
data events 3 items
data actions 3 items
involves roles 5 items
competing warrants 2 items
data warrant tension The discovery that State Z's rules impose stricter attribution requirements than State Q — while the NSPE Code's honesty standard was found sufficient to avoid an ethical violation under State Q's fra...
competing claims The Jurisdiction-Specific Compliance warrant concludes that Engineer B's conduct is unethical in State Z regardless of NSPE Code compliance because state licensing authority supersedes national profes...
rebuttal conditions The rebuttal condition creating uncertainty is whether the NSPE Code's honesty standard is intended as a floor — below which no conduct is ethical — or as a complete specification of ethical conduct, ...
emergence narrative This question arose because the simultaneous application of State Q rules, State Z rules, and the NSPE Code to identical conduct produced three different normative outcomes, revealing that the NSPE Co...
confidence 0.88
QuestionEmergence_10 individual committed

This question emerged because the State Q Board's proportionality-based finding of no ethical violation exposed a structural tension within the NSPE Code between its aspirational commitment to intellectual integrity in professional representations and its operational minimum compliance thresholds, which are calibrated to avoid clear misrepresentation rather than to affirmatively require maximum clarity. The attribution ambiguity created by XYZ Engineers' proposal format forced the question of whether the ethics framework's tolerance of partial disclosure in State Q reflects a principled proportionality judgment or an unresolved gap that undermines the integrity of qualification-based procurement.

URI case-19#Q10
question uri case-19#Q10
question text Does the Intellectual Integrity in Authorship principle — which would favor granular, project-level attribution of Engineer B's prior-employer work — conflict with the Proportionality Analysis applied...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension The State Q Board's finding that partial disclosure was sufficient to avoid an ethical violation simultaneously triggers the Intellectual Integrity in Authorship warrant — which demands granular, proj...
competing claims The Intellectual Integrity in Authorship warrant concludes that each project entry in a qualifications proposal must independently and explicitly attribute prior-employer origin because authorship int...
rebuttal conditions The rebuttal condition generating uncertainty is whether the gap between aspirational authorship norms and minimum compliance thresholds is a feature of a well-calibrated ethics framework — which dist...
emergence narrative This question emerged because the State Q Board's proportionality-based finding of no ethical violation exposed a structural tension within the NSPE Code between its aspirational commitment to intelle...
confidence 0.86
QuestionEmergence_11 individual committed

This question arose because Engineer B's partial attribution practice sits precisely at the boundary between technical compliance and substantive honesty: the data of prefatory-only disclosure activates both a strict deontological warrant requiring project-level transparency and a weaker warrant treating document-level notice as sufficient, and neither warrant can be dismissed without resolving a contested empirical question about how clients actually read proposals. The question is therefore not merely about what Engineer B did, but about which level of the argument structure - the warrant itself or its application - is the appropriate site of ethical contestation.

URI case-19#Q11
question uri case-19#Q11
question text From a deontological perspective, did Engineer B fulfill a categorical duty of honesty in professional representations by disclosing prior-employer attribution only in prefatory sections of qualificat...
data events 3 items
data actions 3 items
involves roles 3 items
competing warrants 2 items
data warrant tension Engineer B's act of disclosing prior-employer attribution only in prefatory sections simultaneously triggers the categorical honesty warrant — which demands disclosure at every level where a reader mi...
competing claims The categorical honesty warrant concludes that disclosure must appear at the project-description level where clients actually evaluate qualifications, while the sufficiency-of-notice warrant concludes...
rebuttal conditions The categorical duty of honesty would not apply with full force if the prefatory disclosure were so prominent, unambiguous, and structurally integrated that no reasonable evaluator could read any proj...
emergence narrative This question arose because Engineer B's partial attribution practice sits precisely at the boundary between technical compliance and substantive honesty: the data of prefatory-only disclosure activat...
confidence 0.87
QuestionEmergence_12 individual committed

This question emerged because the consequentialist framework requires an empirical accounting of all affected parties - clients, competitors, and the profession - but the data of partial disclosure under rules of varying stringency makes that accounting indeterminate: the same practice that avoids State Q's misrepresentation threshold may still impose diffuse harms on competitors and professional trust that are real but difficult to quantify. The question therefore arose at the rebuttal layer, where the conditions under which technical compliance negates net harm are genuinely uncertain.

URI case-19#Q12
question uri case-19#Q12
question text From a consequentialist perspective, did the partial attribution disclosure practice adopted by XYZ Engineers produce net harm to clients, competing firms, and the profession — even if it technically ...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension The data that XYZ Engineers gained competitive advantage through partial attribution disclosure triggers both a harm-aggregation warrant demanding that all costs to clients, competitors, and the profe...
competing claims The harm-aggregation warrant concludes that competitive distortion and erosion of professional trust constitute net harm even absent outright misrepresentation, while the technical-compliance warrant ...
rebuttal conditions The harm-aggregation warrant would not yield a net-harm conclusion if the competitive advantage gained by XYZ Engineers were shown to be proportionate to Engineer B's genuine contribution to the prior...
emergence narrative This question emerged because the consequentialist framework requires an empirical accounting of all affected parties — clients, competitors, and the profession — but the data of partial disclosure un...
confidence 0.85
QuestionEmergence_13 individual committed

This question arose because virtue ethics evaluates character dispositions rather than rule compliance, and the data of a technically transparent but practically obscure disclosure structure creates genuine uncertainty about whether Engineer B's choices reflect the disposition of an intellectually honest professional or the disposition of one who uses technical compliance as cover for competitive advantage. The question is irreducible to rule-checking because it requires a judgment about the motivational structure behind the proposal design, which the available data underdetermines.

URI case-19#Q13
question uri case-19#Q13
question text From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of a licensed engineer when structuring qualifications proposals in a way that...
data events 2 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer B's structuring of proposals to be technically transparent at the document level but potentially obscure at the project-description level triggers both a virtue warrant demanding that profess...
competing claims The virtue warrant concludes that a person of genuine professional integrity would structure disclosure to match where clients actually focus attention, making project-level attribution the only hones...
rebuttal conditions The virtue ethics critique would not apply if it could be shown that the proposal structure was industry-standard, that clients were sophisticated enough to integrate prefatory disclosures into their ...
emergence narrative This question arose because virtue ethics evaluates character dispositions rather than rule compliance, and the data of a technically transparent but practically obscure disclosure structure creates g...
confidence 0.84
QuestionEmergence_14 individual committed

This question arose because the argument structure contains two warrants that are both valid in their own domain but point in opposite directions when applied to the same data: the reporting obligation warrant is grounded in public protection and professional accountability, while the conflict-of-interest warrant is grounded in the integrity of the regulatory process itself. The question is not resolvable by simply asserting one warrant's priority because the rebuttal conditions for each are empirically contested in Engineer A's specific situation.

URI case-19#Q14
question uri case-19#Q14
question text From a deontological perspective, does Engineer A's status as a direct competitor of XYZ Engineers create a conflicting duty — between the obligation to report known or suspected licensing violations ...
data events 3 items
data actions 4 items
involves roles 6 items
competing warrants 2 items
data warrant tension The data that Engineer A is simultaneously a direct commercial competitor of XYZ Engineers and a licensed engineer with knowledge of a genuine licensing violation triggers both a mandatory-reporting w...
competing claims The mandatory-reporting warrant concludes that the duty to report known violations is non-waivable and that Engineer A's competitive status is legally and ethically irrelevant to the obligation, while...
rebuttal conditions The conflict-of-interest rebuttal would not defeat the reporting obligation if the violation were sufficiently serious to implicate public safety or professional integrity at a level that transcends c...
emergence narrative This question arose because the argument structure contains two warrants that are both valid in their own domain but point in opposite directions when applied to the same data: the reporting obligatio...
confidence 0.89
QuestionEmergence_15 individual committed

This question arose because the consequentialist evaluation of mandatory reporting rules requires a second-order analysis of institutional effects that the rule's text does not resolve: the same rule that produces public benefit when applied to disinterested reporters may produce systemic harm when applied to direct competitors, and the data of Engineer A's dual status as both a legitimate reporter and a competitive beneficiary of the report makes it impossible to assess aggregate outcomes without knowing the broader distribution of competitor-initiated reports across the profession. The question therefore emerged at the rebuttal layer, where the conditions under which the rule's aggregate benefits hold are genuinely empirically uncertain.

URI case-19#Q15
question uri case-19#Q15
question text From a consequentialist perspective, does the mandatory reporting obligation imposed on Engineer A by both states' licensing rules produce better aggregate outcomes for the profession and the public w...
data events 4 items
data actions 4 items
involves roles 6 items
competing warrants 2 items
data warrant tension The data that mandatory reporting rules apply regardless of the reporter's competitive status triggers both a systemic-welfare warrant concluding that uniform enforcement produces better aggregate out...
competing claims The systemic-welfare warrant concludes that mandatory reporting by competitors produces net benefit because it increases detection of genuine violations and deters misconduct across the profession, wh...
rebuttal conditions The systemic-welfare warrant would not produce better aggregate outcomes if empirical evidence showed that competitor-initiated reports are disproportionately strategic rather than genuine, that licen...
emergence narrative This question arose because the consequentialist evaluation of mandatory reporting rules requires a second-order analysis of institutional effects that the rule's text does not resolve: the same rule ...
confidence 0.86
QuestionEmergence_16 individual committed

This question emerged because the licensing regime's mandatory reporting structure does not screen for reporter identity or motive, creating a structural gap between procedural compliance and virtue-ethical legitimacy. The question surfaces when the same data event (State Z violation established by a competitor) simultaneously satisfies the public-protection warrant and activates the professional-solidarity rebuttal, leaving the virtue status of the act genuinely contested.

URI case-19#Q16
question uri case-19#Q16
question text From a virtue ethics perspective, does a licensing regime that requires engineers to report competitors' violations cultivate or undermine the virtue of professional solidarity, and did Engineer A act...
data events 3 items
data actions 3 items
involves roles 5 items
competing warrants 2 items
data warrant tension The fact that Engineer A is a direct competitor of XYZ Engineers simultaneously triggers the mandatory reporting obligation (public protection warrant) and raises suspicion that the motivation may be ...
competing claims One warrant concludes that reporting is a virtuous fulfillment of professional accountability regardless of who reports, while the competing warrant concludes that a competitor's report is structurall...
rebuttal conditions Uncertainty arises because virtue ethics evaluates the internal motivational state of the agent, which is unverifiable from external conduct alone — if Engineer A's dominant motive was competitive adv...
emergence narrative This question emerged because the licensing regime's mandatory reporting structure does not screen for reporter identity or motive, creating a structural gap between procedural compliance and virtue-e...
confidence 0.82
QuestionEmergence_17 individual committed

This question arose because the Board's conclusion of no violation was premised on the existence of the prefatory notice, but the reasoning left unresolved whether that placement was sufficient or merely the minimum - the gap between 'not a violation' and 'best practice' created space for the question of whether a higher disclosure density would have been required to satisfy the honesty standard. The counterfactual framing exposes that the Board's holding was location-sensitive without specifying what location would have been dispositive.

URI case-19#Q17
question uri case-19#Q17
question text If XYZ Engineers had included the prior-employer attribution notice not only in the prefatory individual qualification section but also immediately adjacent to each project description throughout the ...
data events 2 items
data actions 3 items
involves roles 5 items
competing warrants 2 items
data warrant tension XYZ Engineers' placement of the attribution notice only in the prefatory section satisfies a minimal transparency warrant but leaves open whether the honesty standard under Section II.5.a demands proj...
competing claims The sufficiency-of-notice warrant concludes that a single prefatory disclosure adequately informs readers and no violation occurred, while the maximum-clarity warrant concludes that honesty requires a...
rebuttal conditions Uncertainty is created by the absence of a specified placement requirement in State Q's rules and in NSPE Code Section II.5.a itself — if the standard is reader-protective rather than form-specific, t...
emergence narrative This question arose because the Board's conclusion of no violation was premised on the existence of the prefatory notice, but the reasoning left unresolved whether that placement was sufficient or mer...
confidence 0.85
QuestionEmergence_18 individual committed

This question emerged because the Board's original analysis focused exclusively on attribution honesty and did not engage the proprietary-interest dimension of III.9, leaving open whether a factual variation (proprietary content in the prior projects) would activate a separate and more restrictive warrant that the permissive State Q standard cannot override. The question surfaces the analytical gap between 'who gets credit' and 'who owns the underlying work.'

URI case-19#Q18
question uri case-19#Q18
question text What if Engineer B's prior projects had involved proprietary design concepts owned by the previous employer — would the Board's analysis under NSPE Code Section III.9 have shifted, and would XYZ Engin...
data events 3 items
data actions 3 items
involves roles 5 items
competing warrants 2 items
data warrant tension If Engineer B's prior projects contained proprietary design concepts owned by the previous employer, the data of listing those projects in XYZ's proposals simultaneously triggers the standard attribut...
competing claims The attribution warrant concludes that disclosing prior-employer origin is sufficient to satisfy honesty obligations, while the proprietary-interest warrant under III.9 concludes that listing projects...
rebuttal conditions Uncertainty is created by the distinction between claiming personal experience credit (permissible) and exploiting proprietary design content (impermissible) — the rebuttal condition is that if the pr...
emergence narrative This question emerged because the Board's original analysis focused exclusively on attribution honesty and did not engage the proprietary-interest dimension of III.9, leaving open whether a factual va...
confidence 0.8
QuestionEmergence_19 individual committed

This question arose because the Board's differential treatment of State Q and State Z reporting obligations was entirely rule-text-dependent, exposing the ethical instability of a system where identical conduct is reportable in one jurisdiction and not another based solely on regulatory drafting specificity. The question forces examination of whether the reporting obligation is grounded in the conduct itself or in the local rule's articulation of that conduct.

URI case-19#Q19
question uri case-19#Q19
question text If State Q's licensing rules had been as specific as State Z's — requiring attribution information to appear next to each individual project listing rather than only in a prefatory section — would Eng...
data events 3 items
data actions 3 items
involves roles 6 items
competing warrants 2 items
data warrant tension The discovery that State Q's rules are less specific than State Z's triggers both the jurisdiction-specific threshold warrant (no violation under State Q's actual rules, so no reporting duty) and the ...
competing claims The jurisdiction-specific threshold warrant concludes that Engineer A correctly declined to report to State Q because XYZ's conduct did not violate State Q's actual rules, while the mandatory reportin...
rebuttal conditions Uncertainty is created by the counterfactual nature of the question — the rebuttal condition is that rule specificity is a legislative choice by the licensing board, and engineers are obligated to app...
emergence narrative This question arose because the Board's differential treatment of State Q and State Z reporting obligations was entirely rule-text-dependent, exposing the ethical instability of a system where identic...
confidence 0.87
QuestionEmergence_20 individual committed

This question emerged because the mandatory reporting obligation and the competitive-interest neutrality constraint are structurally in tension whenever a competitor is the reporting party, and anonymity introduces a third variable that does not cleanly resolve that tension in either direction. The question surfaces because the Board's analysis of Engineer A's reporting obligation did not address the identity dimension, leaving open whether the form of the report (named vs. anonymous) affects its ethical validity or its adequacy as fulfillment of the professional duty.

URI case-19#Q20
question uri case-19#Q20
question text What if Engineer A had filed the report to the State Z board anonymously rather than under their own name — would the mandatory reporting obligation still be considered fulfilled, and would the compet...
data events 3 items
data actions 2 items
involves roles 4 items
competing warrants 2 items
data warrant tension The fact that Engineer A is a competitor filing a report to State Z simultaneously triggers the mandatory reporting warrant (which does not specify identity requirements) and the competitive-interest ...
competing claims The mandatory reporting warrant concludes that the obligation is fulfilled by the act of reporting regardless of whether the reporter is identified, since the board receives the information needed to ...
rebuttal conditions Uncertainty is created by the dual-edged nature of anonymity in this context — the rebuttal condition for the 'anonymity mitigates' claim is that licensing boards may be unable to follow up with an an...
emergence narrative This question emerged because the mandatory reporting obligation and the competitive-interest neutrality constraint are structurally in tension whenever a competitor is the reporting party, and anonym...
confidence 0.83
QuestionEmergence_21 individual committed

This question emerged because Engineer A's actual review process required consulting both State Q and State Z licensing board rules to differentiate a non-violation from a violation - a differentiation the NSPE Code alone could not reliably produce - exposing a structural gap between the Code's general principles and the jurisdiction-specific precision needed to identify professional misconduct in multi-state practice. The question crystallizes the tension between the NSPE Code's role as a universal ethical floor and the reality that licensing boards impose jurisdiction-specific attribution standards that may exceed or differ from that floor in ways invisible to a practitioner relying solely on the national code.

URI case-19#Q21
question uri case-19#Q21
question text If Engineer A had chosen not to review the specific licensing board rules of either state and had relied solely on the NSPE Code of Ethics to assess XYZ Engineers' conduct, would Engineer A have corre...
data events 4 items
data actions 4 items
involves roles 5 items
competing warrants 3 items
data warrant tension The discovery that State Z imposes specific attribution requirements that the NSPE Code does not explicitly replicate means that the same factual conduct — XYZ Engineers' partial attribution disclosur...
competing claims The NSPE Code's honesty and misrepresentation provisions (Section II.5.a and Professional Obligation III.9) warrant a conclusion that XYZ Engineers' conduct is ethically questionable but may not const...
rebuttal conditions Uncertainty arises because if the NSPE Code's general honesty and credit-attribution principles are interpreted broadly enough to encompass jurisdiction-specific attribution granularity, then Engineer...
emergence narrative This question emerged because Engineer A's actual review process required consulting both State Q and State Z licensing board rules to differentiate a non-violation from a violation — a differentiatio...
confidence 0.87
resolution pattern 20
ResolutionPattern_1 individual committed

The board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code because the prefatory attribution notice prevented the proposals from constituting outright falsification or misrepresentation of qualifications, and that Engineer A's reporting obligation was triggered only with respect to the State Z board where a specific rule violation had occurred.

URI case-19#C1
conclusion uri case-19#C1
conclusion text The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board weighed the honesty obligation under II.5.a against the actual disclosure practice and found that the prefatory notice, while imperfect, was sufficient to avoid falsification under the NSPE ...
resolution narrative The board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code because the prefatory attribution notice prevented the proposals from constituting ou...
confidence 0.85
ResolutionPattern_2 individual committed

The Board reached its conclusion by reading the proposal at the document level and finding that the prefatory notice prevented falsification, but this analysis left a normative gap by failing to assess whether the notice's placement and prominence were adequate to inform the realistic reading behavior of government procurement evaluators, thereby treating honesty as a binary rather than graduated obligation.

URI case-19#C2
conclusion uri case-19#C2
conclusion text The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution not...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board implicitly resolved the tension between technical disclosure compliance and substantive honesty by treating the presence of a prefatory notice as categorically sufficient, without weighing t...
resolution narrative The Board reached its conclusion by reading the proposal at the document level and finding that the prefatory notice prevented falsification, but this analysis left a normative gap by failing to asses...
confidence 0.82
ResolutionPattern_3 individual committed

The Board concluded that Engineer B's conduct was not unethical without separately evaluating XYZ Engineers' institutional responsibility for the proposal format it controlled, thereby leaving open the question of whether firms can avoid ethical scrutiny by delegating attribution decisions to individual engineers while retaining architectural control over how disclosures are structured and positioned.

URI case-19#C3
conclusion uri case-19#C3
conclusion text The Board's finding that XYZ Engineers' practices were not unethical under the NSPE Code does not fully address the institutional dimension of the firm's responsibility. Engineer B is an individual li...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The Board weighed individual engineer culpability against firm-level responsibility but resolved the analysis entirely at the individual level, leaving unaddressed whether XYZ Engineers bore a distinc...
resolution narrative The Board concluded that Engineer B's conduct was not unethical without separately evaluating XYZ Engineers' institutional responsibility for the proposal format it controlled, thereby leaving open th...
confidence 0.8
ResolutionPattern_4 individual committed

The Board's finding that the same conduct was simultaneously compliant under the NSPE Code and violative of State Z's rules reveals that the NSPE Code's honesty standard functions as a minimum floor, and that engineers practicing across multiple jurisdictions cannot rely on NSPE Code compliance alone - they must identify and apply the most stringent jurisdiction-specific standard applicable to their proposal practices.

URI case-19#C4
conclusion uri case-19#C4
conclusion text The Board's conclusion that Engineer B's practices were not unethical under the NSPE Code, when read alongside the finding that State Z's rules were violated, exposes a structural tension in the relat...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The Board resolved the tension between NSPE Code compliance and jurisdiction-specific rule compliance by treating them as operating on separate tracks, but this approach exposed a structural gap in wh...
resolution narrative The Board's finding that the same conduct was simultaneously compliant under the NSPE Code and violative of State Z's rules reveals that the NSPE Code's honesty standard functions as a minimum floor, ...
confidence 0.83
ResolutionPattern_5 individual committed

The Board affirmed Engineer A's reporting obligation to the State Z board by treating the established rule violation as sufficient to trigger the duty, but did not address the virtue ethics dimension of whether Engineer A's competitive motivation - while not voiding the obligation - required disclosure of the competitive relationship and strict limitation of the report to documented facts rather than broader reputational claims against XYZ Engineers.

URI case-19#C5
conclusion uri case-19#C5
conclusion text While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension...
answers questions 6 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The Board implicitly resolved the tension between the mandatory reporting obligation and the competitive-interest concern by affirming the reporting duty without addressing the motivational dimension,...
resolution narrative The Board affirmed Engineer A's reporting obligation to the State Z board by treating the established rule violation as sufficient to trigger the duty, but did not address the virtue ethics dimension ...
confidence 0.78
ResolutionPattern_6 individual committed

The Board resolved Q2 by differentiating between the two states' licensing rule specificity: because State Z's rules explicitly required project-level attribution and XYZ Engineers' practice clearly failed that standard, Engineer A's reporting obligation to the State Z board was mandatory; because State Q's rules imposed no comparable requirement, reporting there would have lacked factual grounding and risked violating Section III.7's prohibition on injuring a competitor's reputation without basis.

URI case-19#C6
conclusion uri case-19#C6
conclusion text The Board's analysis of Engineer A's reporting obligation appropriately distinguished between State Q and State Z based on the differing specificity of each state's licensing rules, concluding that a ...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board balanced the mandatory reporting duty against the prohibition on unsupported reputational injury by conditioning the obligation to report on whether a jurisdiction-specific rule was clearly ...
resolution narrative The Board resolved Q2 by differentiating between the two states' licensing rule specificity: because State Z's rules explicitly required project-level attribution and XYZ Engineers' practice clearly f...
confidence 0.91
ResolutionPattern_7 individual committed

The Board concluded that Engineer A's competitive relationship with XYZ Engineers created a real but non-dispositive conflict of interest: because the underlying State Z violation was genuine and Engineer A's reporting was limited to that jurisdiction, the competitive motivation did not transform the report into an abuse of the licensing system, and the mandatory duty to report remained operative and was properly fulfilled.

URI case-19#C7
conclusion uri case-19#C7
conclusion text Engineer A's status as a direct competitor of XYZ Engineers does create a potential conflict of interest that warrants careful self-examination before initiating any reporting action. However, that co...
answers questions 5 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board weighed the mandatory reporting obligation against the fairness-in-competition concern by holding that the conflict of interest elevates the standard of care required of the reporting engine...
resolution narrative The Board concluded that Engineer A's competitive relationship with XYZ Engineers created a real but non-dispositive conflict of interest: because the underlying State Z violation was genuine and Engi...
confidence 0.89
ResolutionPattern_8 individual committed

The Board found XYZ Engineers' practices not unethical under the NSPE Code for State Q purposes, but the conclusion identifies this as an incomplete analysis because the firm's institutional decision to structure proposals with prefatory-only attribution - a decision that cannot be attributed solely to Engineer B - warranted separate scrutiny under Section II.5.a's prohibition on permitting misrepresentation, particularly given that the firm's standard structure failed the stricter State Z standard.

URI case-19#C8
conclusion uri case-19#C8
conclusion text The Board's analysis focused primarily on Engineer B's individual conduct and did not separately evaluate XYZ Engineers' institutional culpability. This omission is analytically significant. XYZ Engin...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board's implicit weighing treated individual and institutional culpability as coextensive, but the conclusion identifies this as an analytical gap: the firm's organizational decision about disclos...
resolution narrative The Board found XYZ Engineers' practices not unethical under the NSPE Code for State Q purposes, but the conclusion identifies this as an incomplete analysis because the firm's institutional decision ...
confidence 0.85
ResolutionPattern_9 individual committed

The Board concluded that Engineer B's prefatory-only attribution practice was not unethical under the NSPE Code as a minimum compliance matter because it avoided outright falsification and satisfied State Q's less specific rules, but the conclusion explicitly declines to endorse the practice as aspirationally ethical, finding that the disclosure architecture created a structural risk of misleading evaluators at the point of decision and that project-level attribution would have better satisfied the intellectual integrity principle underlying Section III.9.a.

URI case-19#C9
conclusion uri case-19#C9
conclusion text The prefatory attribution notice placed only at the beginning of Engineer B's individual qualification section — but not repeated within each project description — occupies an ethically ambiguous midd...
answers questions 5 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The Board weighed the technical non-falsification standard against the affirmative transparency demanded by Section II.5.a's spirit, concluding that the prefatory notice met the minimum compliance thr...
resolution narrative The Board concluded that Engineer B's prefatory-only attribution practice was not unethical under the NSPE Code as a minimum compliance matter because it avoided outright falsification and satisfied S...
confidence 0.88
ResolutionPattern_10 individual committed

Applying a deontological framework, the Board concluded that Engineer B's prefatory-only attribution disclosure fulfilled only a weak non-falsification duty and fell short of the categorical duty of honesty that requires representations to deliver accurate information at the point of decision; the universalizability test confirmed this shortfall because a profession-wide norm of prefatory-only attribution would structurally undermine the integrity of qualifications-based procurement, meaning the NSPE Code's no-violation finding reflects minimum compliance rather than deontological approval of the practice.

URI case-19#C10
conclusion uri case-19#C10
conclusion text From a deontological perspective, Engineer B's prefatory-only attribution disclosure does not fully satisfy a categorical duty of honesty in professional representations. A Kantian analysis would ask ...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The Board's deontological analysis weighed the weak duty of non-falsification — which Engineer B satisfied — against the stronger categorical duty of affirmative transparency — which Engineer B did no...
resolution narrative Applying a deontological framework, the Board concluded that Engineer B's prefatory-only attribution disclosure fulfilled only a weak non-falsification duty and fell short of the categorical duty of h...
confidence 0.86
ResolutionPattern_11 individual committed

The board concluded that XYZ Engineers' partial attribution practice, while not a Code violation under State Q rules, produced net consequentialist harm by creating an uneven competitive playing field and risking a profession-wide race to minimum disclosure; this led the board to endorse the stricter State Z approach as producing better aggregate outcomes and to flag the NSPE Code's current standard as insufficiently calibrated to prevent structural misleading.

URI case-19#C11
conclusion uri case-19#C11
conclusion text From a consequentialist perspective, the partial attribution disclosure practice adopted by XYZ Engineers produces a net harm to the competitive fairness of the procurement process and to the integrit...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board weighed the competitive advantage gained by XYZ Engineers through partial disclosure against the aggregate harm to competing firms, clients, and professional informational quality, concludin...
resolution narrative The board concluded that XYZ Engineers' partial attribution practice, while not a Code violation under State Q rules, produced net consequentialist harm by creating an uneven competitive playing field...
confidence 0.87
ResolutionPattern_12 individual committed

The board concluded that Engineer B fell short of the virtue ethics standard of professional integrity because a person of good professional character - aware of how evaluators actually read proposals - would have ensured attribution was visible at the project-description level, not merely in a prefatory notice; Engineer B's compliance-minimizing approach, while avoiding a Code violation, reflected an orientation inconsistent with the aspirational honesty and transparency the NSPE Code seeks to cultivate.

URI case-19#C12
conclusion uri case-19#C12
conclusion text From a virtue ethics perspective, Engineer B did not fully demonstrate the professional integrity and intellectual honesty expected of a licensed engineer. A virtuous engineer — one who has internaliz...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 4 items
weighing process The board weighed the technical sufficiency of the prefatory notice against the virtue ethics demand for affirmative transparency at the point of evaluation, concluding that satisfying the minimum com...
resolution narrative The board concluded that Engineer B fell short of the virtue ethics standard of professional integrity because a person of good professional character — aware of how evaluators actually read proposals...
confidence 0.9
ResolutionPattern_13 individual committed

The board concluded that Engineer A's reporting to the State Z board was consistent with appropriate motivational integrity because the jurisdiction-specific analysis and selective reporting (declining to report in State Q) indicated good-faith application of the obligation; however, the virtue ethics framework imposed an ongoing duty on Engineer A to honestly examine competitive motivations and refrain from reporting if self-interest, rather than public protection, was the primary driver.

URI case-19#C13
conclusion uri case-19#C13
conclusion text From a virtue ethics perspective, the licensing regime's mandatory competitor-reporting obligation presents a genuine tension between professional solidarity and public protection, but that tension do...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board weighed professional solidarity against the more fundamental virtues of honesty and public protection, concluding that solidarity is subordinate when a genuine violation exists, but that mot...
resolution narrative The board concluded that Engineer A's reporting to the State Z board was consistent with appropriate motivational integrity because the jurisdiction-specific analysis and selective reporting (declinin...
confidence 0.85
ResolutionPattern_14 individual committed

The board concluded through counterfactual analysis that project-level attribution would have produced an unambiguously compliant proposal and eliminated the ethical concern entirely, confirming that the prefatory-only notice was a minimum-threshold solution rather than best practice; this counterfactual also revealed that the NSPE Code's Section II.5.a honesty standard does not affirmatively require project-level attribution, identifying the structural gap that State Z's more granular rules were designed to address.

URI case-19#C14
conclusion uri case-19#C14
conclusion text The counterfactual in which XYZ Engineers had included attribution notices adjacent to each project description throughout the proposal body would almost certainly have led the Board to the same concl...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 4 items
weighing process The board weighed the sufficiency of the prefatory notice against the aspirational standard of project-level attribution, concluding that the former met the minimum threshold while the latter would ha...
resolution narrative The board concluded through counterfactual analysis that project-level attribution would have produced an unambiguously compliant proposal and eliminated the ethical concern entirely, confirming that ...
confidence 0.88
ResolutionPattern_15 individual committed

The board concluded through this counterfactual that the reporting obligation in State Q would have been reversed had State Q's rules matched State Z's specificity, demonstrating that the ethical and legal duty to report is a function of jurisdiction-specific rule content rather than the NSPE Code's general principles alone; this revealed a structural gap in which engineers practicing under less specific state rules receive materially less protection from partial-disclosure practices, and the NSPE Code does not fill that gap.

URI case-19#C15
conclusion uri case-19#C15
conclusion text The counterfactual in which State Q's licensing rules were as specific as State Z's — requiring attribution information to appear next to each individual project listing — would have reversed the Boar...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board weighed the NSPE Code's general honesty standard against jurisdiction-specific rule specificity, concluding that the Code alone cannot substitute for granular state rules in establishing the...
resolution narrative The board concluded through this counterfactual that the reporting obligation in State Q would have been reversed had State Q's rules matched State Z's specificity, demonstrating that the ethical and ...
confidence 0.91
ResolutionPattern_16 individual committed

The board resolved Q21 by confirming that Engineer A would not have correctly identified the State Z violation through Code review alone, because the prefatory attribution notice is ambiguous under Section II.5.a's general falsification prohibition; this gap validates Section III.8.a's implicit demand that engineers independently consult each jurisdiction's licensing rules rather than treating Code compliance as equivalent to full regulatory compliance.

URI case-19#C16
conclusion uri case-19#C16
conclusion text The counterfactual in which Engineer A had relied solely on the NSPE Code of Ethics — without reviewing the jurisdiction-specific licensing rules of State Q and State Z — reveals a critical gap in the...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board weighed the sufficiency of the NSPE Code's general honesty standard against the specificity required to detect jurisdiction-level violations, concluding that the Code's generality is structu...
resolution narrative The board resolved Q21 by confirming that Engineer A would not have correctly identified the State Z violation through Code review alone, because the prefatory attribution notice is ambiguous under Se...
confidence 0.91
ResolutionPattern_17 individual committed

The board concluded that the NSPE Code's honesty standard under Section II.5.a is insufficiently calibrated to address disclosure architecture choices in multi-jurisdictional proposal practice, and that the divergence between State Q and State Z rules does not create a logical contradiction with the Code but instead reveals a gap the NSPE should consider closing through revision of its attribution provisions.

URI case-19#C17
conclusion uri case-19#C17
conclusion text The divergence between State Q's general misrepresentation prohibition and State Z's granular project-level attribution requirement reveals that the NSPE Code's honesty standard under Section II.5.a i...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the divergence between the Code's honesty standard and State Z's more demanding rule by treating them as operating on different levels of specificity — the Code sets a general minim...
resolution narrative The board concluded that the NSPE Code's honesty standard under Section II.5.a is insufficiently calibrated to address disclosure architecture choices in multi-jurisdictional proposal practice, and th...
confidence 0.89
ResolutionPattern_18 individual committed

The board resolved Q7, Q10, and Q13 by finding that the prefatory notice satisfied the NSPE Code's honesty threshold because the Code calibrates compliance to the document as a whole rather than to the reader's likely cognitive path, but explicitly flagged that this outcome does not endorse prefatory-only attribution as best practice and that practitioners should adopt project-level attribution to close the gap between minimum compliance and intellectual integrity.

URI case-19#C18
conclusion uri case-19#C18
conclusion text The Board resolved the tension between the Transparency Principle and Qualification Proposal Attribution Integrity by treating document-level disclosure as sufficient to satisfy the NSPE Code's honest...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board balanced the Transparency Principle against Qualification Proposal Attribution Integrity by treating document-level disclosure as formally sufficient under the Code's minimum standard, while...
resolution narrative The board resolved Q7, Q10, and Q13 by finding that the prefatory notice satisfied the NSPE Code's honesty threshold because the Code calibrates compliance to the document as a whole rather than to th...
confidence 0.87
ResolutionPattern_19 individual committed

The board resolved Q8, Q14, Q15, and Q16 by affirming Engineer A's reporting obligation on deontological grounds - the existence of a real violation triggers the duty regardless of the reporter's motivation - while leaving open the consequentialist concern that mandatory reporting by direct competitors can function as competitive harm, noting that this prioritization is most defensible when the violation is clear rather than marginal.

URI case-19#C19
conclusion uri case-19#C19
conclusion text The case reveals a structural tension between the Mandatory Competitor Misconduct Reporting Obligation and the Fairness in Professional Competition principle that the Board did not fully resolve. By a...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board weighed the mandatory reporting duty against the conflict-of-interest concern by treating the reporting obligation as categorical when the underlying violation is genuine and material, impli...
resolution narrative The board resolved Q8, Q14, Q15, and Q16 by affirming Engineer A's reporting obligation on deontological grounds — the existence of a real violation triggers the duty regardless of the reporter's moti...
confidence 0.85
ResolutionPattern_20 individual committed

The board resolved Q1, Q2, Q3, Q9, Q11, and Q12 by finding that Engineer B's practice was not unethical under the NSPE Code or State Q rules but did violate State Z's specific attribution requirement, confirming Engineer A's reporting obligation to the State Z board while implicitly suggesting that the NSPE Code's honesty provisions require revision to incorporate more explicit multi-jurisdictional attribution guidance and close the gap between the Code's general standard and the more specific requirements some states have found necessary.

URI case-19#C20
conclusion uri case-19#C20
conclusion text The most significant principle interaction in this case is the divergence between the Jurisdiction-Specific Ethics Compliance Obligation and the Honesty in Professional Representations principle as op...
answers questions 6 items
determinative principles 3 items
determinative facts 3 items
cited provisions 5 items
weighing process The board resolved the divergence between the Code's general honesty standard and State Z's specific attribution rule by treating them as operating on different normative levels — the Code sets a gene...
resolution narrative The board resolved Q1, Q2, Q3, Q9, Q11, and Q12 by finding that Engineer B's practice was not unethical under the NSPE Code or State Q rules but did violate State Z's specific attribution requirement,...
confidence 0.88
Phase 3: Decision Points
17 17 committed
canonical decision point 17

Should Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by including prior-employer attribution only in a prefatory notice at the beginning of the qualification section, or by repeating attribution information adjacent to each individual project description throughout the proposal?

URI http://proethica.org/ontology/case-19#DP1
focus id DP1
focus number 1
description Engineer B and XYZ Engineers must decide how to present prior-employer project experience in qualification proposals submitted across State Q and State Z, choosing between a prefatory attribution noti...
decision question Should Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by placing prior-employer attribution only in a prefatory notice at the start of the qualification secti...
role uri http://proethica.org/ontology/case/19#Honesty_in_Professional_Representations_Obligation_XYZ_Engineers_Qualification_Proposals_Both_States
role label Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States
obligation uri http://proethica.org/ontology/intermediate#QualificationProposalMisrepresentationNon-CommissionObligation
obligation label Qualification Proposal Misrepresentation Non-Commission Obligation
constraint uri http://proethica.org/ontology/case/19#Maximum_Clarity_Attribution_Constraint_Engineer_B_XYZ_Engineers_State_Q
constraint label Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q
involved action uris 5 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["NSPE Code Section II.5.a", "NSPE Code Section III.9", "NSPE Code Section III.9.a"], "data_summary": "Engineer B joined XYZ Engineers after completing bridge and culvert...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 10 items
board resolution The Board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code of Ethics because the prefatory attribution notice prevented the proposals from const...
options 3 items
intensity score 0.75
qc alignment score 0.88
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers must decide how to present prior-employer project experience in qualification proposals submitted across State Q and State Z, choosing between a prefatory attribution noti...
llm refined question Should Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by including prior-employer attribution only in a prefatory notice at the beginning of the qualification...

Should Engineer A fulfill the mandatory competitor misconduct reporting obligation by reporting XYZ Engineers' attribution practices to the licensing board of State Z - where a specific rule violation is established - while declining to report to the State Q board where no clear rule violation is found, notwithstanding Engineer A's status as a direct commercial competitor?

URI http://proethica.org/ontology/case-19#DP2
focus id DP2
focus number 2
description Engineer A, a direct commercial competitor of XYZ Engineers, must decide whether to report XYZ Engineers' qualification proposal attribution practices to the licensing boards of State Q and State Z af...
decision question Should Engineer A report XYZ Engineers' attribution practices to both state licensing boards, to State Z's board only, or withhold the report entirely due to the competitor relationship?
role uri http://proethica.org/ontology/case/19#Mandatory_Competitor_Misconduct_Reporting_Obligation_Invoked_By_Engineer_A_Both_States
role label Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States
obligation uri http://proethica.org/ontology/intermediate#CompetitorQualificationProposalMisconductReportingObligation
obligation label Competitor Qualification Proposal Misconduct Reporting Obligation
constraint uri http://proethica.org/ontology/case/19#Competitor_Misconduct_Reporting_Competitive_Interest_Neutrality_Constraint_Engineer_A_State_Z_Reporting
constraint label Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting
involved action uris 7 items
provision uris 4 items
provision labels 4 items
toulmin {"backing_provisions": ["NSPE Code of Ethics Reporting Obligation", "State Q Licensing Board Rules", "State Z Licensing Board Rules", "NSPE Code Section III.7"], "data_summary": "Engineer A works...
aligned question uri case-19#Q2
aligned question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
addresses questions 8 items
board resolution The Board concluded that Engineer A had an obligation to report the State Z violation to the State Z licensing board because the specific rule violation was clearly established upon review of State Z'...
options 3 items
intensity score 0.72
qc alignment score 0.85
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer A, a direct commercial competitor of XYZ Engineers, must decide whether to report XYZ Engineers' qualification proposal attribution practices to the licensing boards of State Q and State Z af...
llm refined question Should Engineer A fulfill the mandatory competitor misconduct reporting obligation by reporting XYZ Engineers' attribution practices to the licensing board of State Z — where a specific rule violation...

Should Engineer B and XYZ Engineers fulfill their jurisdiction-specific licensing rule compliance obligation by identifying and applying the specific attribution requirements of each state - including State Z's more stringent project-level attribution rule - when preparing qualification proposals for submission in those jurisdictions, rather than applying a uniform format that satisfies only the less specific State Q standard?

URI http://proethica.org/ontology/case-19#DP3
focus id DP3
focus number 3
description Engineer B and XYZ Engineers, operating across multiple licensing jurisdictions, must decide whether to identify and apply the most stringent jurisdiction-specific attribution rules of each state when...
decision question Should Engineer B and XYZ Engineers tailor their qualification proposal format to meet each state's specific attribution requirements — including State Z's more stringent project-level rule — or apply...
role uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Licensing_Rule_Compliance_Obligation_XYZ_Engineers_Engineer_B_Both_States
role label Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
obligation uri http://proethica.org/ontology/intermediate#Jurisdiction-SpecificLicensingRuleComplianceinQualificationProposalsObligation
obligation label Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation
constraint uri http://proethica.org/ontology/case/19#Proportionate_Misrepresentation_Threshold_Assessment_Constraint_Engineer_A_State_Q_No_Reporting
constraint label Proportionate Misrepresentation Threshold Assessment Constraint Engineer A State Q No Reporting
involved action uris 5 items
provision uris 4 items
provision labels 4 items
toulmin {"backing_provisions": ["NSPE Code Section II.5.a", "NSPE Code Section III.8.a", "State Z Project-Level Attribution Rule", "State Q Misrepresentation Prohibition"], "data_summary": "XYZ Engineers...
aligned question uri case-19#Q9
aligned question text Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter st...
addresses questions 6 items
board resolution The Board concluded that XYZ Engineers' uniform proposal format violated State Z's specific project-level attribution rule while satisfying State Q's more general misrepresentation prohibition and the...
options 3 items
intensity score 0.68
qc alignment score 0.82
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers, operating across multiple licensing jurisdictions, must decide whether to identify and apply the most stringent jurisdiction-specific attribution rules of each state when...
llm refined question Should Engineer B and XYZ Engineers fulfill their jurisdiction-specific licensing rule compliance obligation by identifying and applying the specific attribution requirements of each state — including...

Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project description to satisfy the NSPE Code's honesty and transparency obligations?

URI http://proethica.org/ontology/case-19#DP4
focus id DP4
focus number 4
description Engineer B and XYZ Engineers: Attribution Disclosure Adequacy in Qualification Proposals
decision question Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project ...
role uri case-19#Engineer
role label Engineer B / XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Honesty_in_Professional_Representations_Obligation_XYZ_Engineers_Qualification_Proposals_Both_States
obligation label Honesty in Professional Representations Obligation — Qualification Proposals Both States
constraint uri http://proethica.org/ontology/intermediate#Prior-EmployerProjectCreditScopeLimitationObligation
constraint label Prior-Employer Project Credit Scope Limitation Obligation
involved action uris 5 items
provision uris 2 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.9", "III.9.a"], "data_summary": "Engineer B completed projects at a prior employer, then joined XYZ Engineers as it entered new state markets. XYZ...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 9 items
board resolution The Board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code because the prefatory attribution notice prevented the proposals from constituting ou...
options 2 items
intensity score 0.75
qc alignment score 0.88
source unified
source candidate ids 3 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers: Attribution Disclosure Adequacy in Qualification Proposals
llm refined question Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project ...

Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard - State Z's project-level requirement - as the operative benchmark for all qualification proposals, or is it ethically permissible to calibrate disclosure architecture to each state's minimum rule, accepting that the same proposal structure may comply in State Q while violating State Z?

URI http://proethica.org/ontology/case-19#DP5
focus id DP5
focus number 5
description Engineer B and XYZ Engineers: Jurisdiction-Specific Attribution Rule Compliance Across State Q and State Z
decision question Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard — State Z's project-level requirement — as the operative benchmark for all qualification pro...
role uri case-19#Engineer
role label Engineer B / XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Licensing_Rule_Compliance_Obligation_XYZ_Engineers_Engineer_B_Both_States
obligation label Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers, Engineer B, Both States
constraint uri http://proethica.org/ontology/case/19#Qualification_Proposal_Misrepresentation_Non-Commission_Obligation_XYZ_Engineers_State_Q
constraint label Qualification Proposal Misrepresentation Non-Commission Obligation — XYZ Engineers, State Q
involved action uris 5 items
provision uris 2 items
provision labels 2 items
toulmin {"backing_provisions": ["II.5.a", "III.8.a"], "data_summary": "State Q\u0027s licensing rules contain a general misrepresentation prohibition that does not specify where attribution information...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 6 items
board resolution The Board found that the same prefatory-only attribution practice was not unethical under the NSPE Code and State Q rules but did violate State Z's specific project-level attribution requirement. This...
options 2 items
intensity score 0.7
qc alignment score 0.82
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers: Jurisdiction-Specific Attribution Rule Compliance Across State Q and State Z
llm refined question Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard — State Z's project-level requirement — as the operative benchmark for all qualification pro...

Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content of each state's rules - reporting only where a clear rule violation is identifiable and declining to report where the applicable rules do not independently prohibit the practice?

URI http://proethica.org/ontology/case-19#DP6
focus id DP6
focus number 6
description Engineer A: Mandatory Competitor Misconduct Reporting Obligation Calibrated to Jurisdiction-Specific Rule Violations
decision question Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content ...
role uri case-19#Engineer
role label Engineer A
obligation uri http://proethica.org/ontology/case/19#Competitor_Qualification_Proposal_Misconduct_Reporting_Obligation_Engineer_A_State_Z
obligation label Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A, State Z
constraint uri http://proethica.org/ontology/case/19#Competitor_Misconduct_Reporting_Competitive_Interest_Neutrality_Constraint_Engineer_A_State_Z_Reporting
constraint label Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A, State Z Reporting
involved action uris 8 items
provision uris 2 items
provision labels 2 items
toulmin {"backing_provisions": ["III.7", "III.8.a"], "data_summary": "Engineer A, a direct commercial competitor of XYZ Engineers through ABC Consultants, became aware of XYZ Engineers\u0027 qualification...
aligned question uri case-19#Q2
aligned question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
addresses questions 9 items
board resolution The Board concluded that Engineer A's reporting obligation was mandatory in State Z — where a specific and clear rule violation was established — and that declining to report after identifying that vi...
options 3 items
intensity score 0.72
qc alignment score 0.83
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer A: Mandatory Competitor Misconduct Reporting Obligation Calibrated to Jurisdiction-Specific Rule Violations
llm refined question Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content ...

Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project description throughout the proposal body?

URI http://proethica.org/ontology/case-19#DP7
focus id DP7
focus number 7
description Engineer B and XYZ Engineers: Attribution Disclosure Placement in Qualification Proposals
decision question Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project descr...
role uri case-19#Engineer_B_Multi-State_Project_Manager
role label Engineer B Multi-State Project Manager
obligation uri http://proethica.org/ontology/intermediate#MaximumClarityAttributioninQualificationProposalsObligation
obligation label Maximum Clarity Attribution in Qualification Proposals Obligation
constraint uri http://proethica.org/ontology/case/19#Prior-Employer_Project_Credit_Scope_Limitation_Obligation_Engineer_B_XYZ_Engineers_State_Z
constraint label Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z
involved action uris 3 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.9", "III.9.a"], "data_summary": "Engineer B completed projects at a prior employer, then joined XYZ Engineers. XYZ Engineers submitted qualification...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 7 items
board resolution The Board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code because the prefatory attribution notice prevented the proposals from constituting ou...
options 2 items
intensity score 0.8
qc alignment score 0.85
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers: Attribution Disclosure Placement in Qualification Proposals
llm refined question Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project descr...

Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated?

URI http://proethica.org/ontology/case-19#DP8
focus id DP8
focus number 8
description Engineer A: Jurisdiction-Differentiated Reporting Obligation for Competitor Misconduct Across State Q and State Z
decision question Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated...
role uri http://proethica.org/ontology/case/19#Engineer_A
role label Engineer A (ABC Consultants)
obligation uri http://proethica.org/ontology/case/19#Mandatory_Competitor_Misconduct_Reporting_Obligation_Invoked_By_Engineer_A_Both_States
obligation label Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States
constraint uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Reporting_Threshold_Applied_by_Engineer_A_in_State_Q
constraint label Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
involved action uris 5 items
provision uris 4 items
provision labels 2 items
toulmin {"backing_provisions": ["III.7", "III.8.a"], "data_summary": "Engineer A, a principal at ABC Consultants and a direct commercial competitor of XYZ Engineers, discovered XYZ Engineers\u0027...
aligned question uri case-19#Q2
aligned question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
addresses questions 8 items
board resolution The Board concluded that Engineer A's reporting obligation was jurisdiction-differentiated: because State Z's rules explicitly required project-level attribution and XYZ Engineers' practice clearly fa...
options 3 items
intensity score 0.75
qc alignment score 0.82
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer A: Jurisdiction-Differentiated Reporting Obligation for Competitor Misconduct Across State Q and State Z
llm refined question Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated...

Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmark for all proposals, or calibrate disclosure architecture separately to each jurisdiction's minimum rule requirements?

URI http://proethica.org/ontology/case-19#DP9
focus id DP9
focus number 9
description XYZ Engineers: Institutional Responsibility for Proposal Attribution Architecture Across Multiple Jurisdictions
decision question Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmar...
role uri http://proethica.org/ontology/case/19#XYZ_Engineers
role label XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Honesty_in_Professional_Representations_Obligation_XYZ_Engineers_Qualification_Proposals_Both_States
obligation label Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States
constraint uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Licensing_Rule_Compliance_Obligation_XYZ_Engineers_Engineer_B_Both_States
constraint label Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
involved action uris 5 items
provision uris 4 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.9", "III.8.a"], "data_summary": "XYZ Engineers, upon entering new state markets, hired Engineer B and structured qualification proposals that listed Engineer...
aligned question uri case-19#Q4
aligned question text To what extent does XYZ Engineers bear institutional ethical responsibility for Engineer B's attribution practices in qualification proposals, and should the Board's analysis have separately evaluated...
addresses questions 5 items
board resolution The Board concluded that XYZ Engineers' practices were not unethical under the NSPE Code for State Q purposes, treating the prefatory notice as sufficient to avoid falsification under the Code's minim...
options 2 items
intensity score 0.7
qc alignment score 0.75
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description XYZ Engineers: Institutional Responsibility for Proposal Attribution Architecture Across Multiple Jurisdictions
llm refined question Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmar...

Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project description in order to satisfy the NSPE Code's honesty standard and applicable state licensing rules?

URI http://proethica.org/ontology/case-19#DP10
focus id DP10
focus number 10
description Engineer B and XYZ Engineers: Attribution Disclosure Granularity in Qualification Proposals Across State Q and State Z
decision question Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project d...
role uri http://proethica.org/ontology/case/19#Engineer
role label Engineer B / XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Honesty_in_Professional_Representations_Obligation_XYZ_Engineers_Qualification_Proposals_Both_States
obligation label Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States
constraint uri http://proethica.org/ontology/case/19#Prior-Employer_Project_Credit_Scope_Limitation_Obligation_Engineer_B_XYZ_Engineers_State_Z
constraint label Prior-Employer Project Credit Scope Limitation Obligation — Engineer B / XYZ Engineers State Z
involved action uris 5 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.9", "III.9.a"], "data_summary": "Engineer B completed projects at a prior employer, then joined XYZ Engineers as it entered new markets in State Q and State...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 11 items
board resolution The Board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code because the prefatory attribution notice prevented the proposals from constituting ou...
options 2 items
intensity score 0.75
qc alignment score 0.88
source unified
source candidate ids 3 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers: Attribution Disclosure Granularity in Qualification Proposals Across State Q and State Z
llm refined question Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project d...

Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither - and does Engineer A's status as a direct commercial competitor of XYZ Engineers create a conflict of interest that modifies or voids the mandatory reporting obligation?

URI http://proethica.org/ontology/case-19#DP11
focus id DP11
focus number 11
description Engineer A: Jurisdiction-Differentiated Reporting Obligation to State Licensing Boards Given Competitor Status and Differential State Rules
decision question Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither — and does Engineer A's status as a direct commercial compet...
role uri http://proethica.org/ontology/case/19#Engineer
role label Engineer A
obligation uri http://proethica.org/ontology/case/19#Mandatory_Competitor_Misconduct_Reporting_Obligation_Invoked_By_Engineer_A_Both_States
obligation label Mandatory Competitor Misconduct Reporting Obligation — Engineer A Both States
constraint uri http://proethica.org/ontology/case/19#Competitor_Misconduct_Reporting_Competitive_Interest_Neutrality_Constraint_Engineer_A_State_Z_Reporting
constraint label Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A State Z Reporting
involved action uris 8 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["III.7", "III.8.a", "II.5.a"], "data_summary": "Engineer A, principal of ABC Consultants and a direct commercial competitor of XYZ Engineers, became aware of XYZ...
aligned question uri case-19#Q2
aligned question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
addresses questions 9 items
board resolution The Board concluded that Engineer A's reporting obligation to the State Z board was mandatory and properly fulfilled because State Z's specific project-level attribution rule was clearly violated by X...
options 3 items
intensity score 0.72
qc alignment score 0.85
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer A: Jurisdiction-Differentiated Reporting Obligation to State Licensing Boards Given Competitor Status and Differential State Rules
llm refined question Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither — and does Engineer A's status as a direct commercial compet...

When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's project-level attribution standard to all proposals, or may they calibrate disclosure granularity to the minimum required by each individual state's rules?

URI http://proethica.org/ontology/case-19#DP12
focus id DP12
focus number 12
description Multi-Jurisdictional Compliance Standard: Whether Engineers and Firms Operating Across State Lines Must Apply the Most Stringent Applicable Jurisdiction's Attribution Rules as the Operative Benchmark ...
decision question When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable ju...
role uri http://proethica.org/ontology/case/19#Engineer
role label Engineer B / XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Licensing_Rule_Compliance_Obligation_XYZ_Engineers_Engineer_B_Both_States
obligation label Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers / Engineer B Both States
constraint uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Reporting_Threshold_Applied_by_Engineer_A_in_State_Q
constraint label Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
involved action uris 6 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.8.a", "III.9.a"], "data_summary": "Engineer A\u0027s review of the applicable rules in both states revealed that State Z\u0027s licensing rules explicitly...
aligned question uri case-19#Q9
aligned question text Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter st...
addresses questions 6 items
board resolution The Board's analysis demonstrated that a single course of conduct — prefatory-only attribution — can simultaneously satisfy the NSPE Code's honesty standard and State Q's misrepresentation prohibition...
options 2 items
intensity score 0.68
qc alignment score 0.82
source unified
source candidate ids 5 items
synthesis method algorithmic+llm
llm refined description Multi-Jurisdictional Compliance Standard: Whether Engineers and Firms Operating Across State Lines Must Apply the Most Stringent Applicable Jurisdiction's Attribution Rules as the Operative Benchmark ...
llm refined question When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable ju...

Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description throughout the proposal body?

URI http://proethica.org/ontology/case-19#DP13
focus id DP13
focus number 13
description Engineer B and XYZ Engineers: Attribution Disclosure Architecture in Qualification Proposals
decision question Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description thro...
role uri http://proethica.org/ontology/case/19#Engineer
role label Engineer B / XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Honesty_in_Professional_Representations_Obligation_XYZ_Engineers_Qualification_Proposals_Both_States
obligation label Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States
constraint uri http://proethica.org/ontology/case/19#Prior-Employer_Project_Credit_Scope_Limitation_Obligation_Engineer_B_XYZ_Engineers_State_Z
constraint label Prior-Employer Project Credit Scope Limitation Obligation — Engineer B XYZ Engineers State Z
involved action uris 3 items
provision uris 2 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.9", "III.9.a"], "data_summary": "Engineer B completed projects at a prior employer, then joined XYZ Engineers as it entered new markets. XYZ Engineers\u0027...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 10 items
board resolution The board concluded that Engineer B's and XYZ Engineers' prefatory-only attribution practice was not unethical under the NSPE Code of Ethics or State Q rules because the prefatory notice prevented the...
options 2 items
intensity score 0.75
qc alignment score 0.88
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers: Attribution Disclosure Architecture in Qualification Proposals
llm refined question Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description thro...

Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear rule violation is identifiable under State Q's standard?

URI http://proethica.org/ontology/case-19#DP14
focus id DP14
focus number 14
description Engineer A: Jurisdiction-Differentiated Reporting Obligation for Competitor Misconduct Across State Q and State Z
decision question Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear ...
role uri http://proethica.org/ontology/case/19#Engineer
role label Engineer A
obligation uri http://proethica.org/ontology/case/19#Competitor_Qualification_Proposal_Misconduct_Reporting_Obligation_Engineer_A_State_Q
obligation label Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Q
constraint uri http://proethica.org/ontology/case/19#Jurisdiction-Specific_Reporting_Threshold_Applied_by_Engineer_A_in_State_Q
constraint label Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
involved action uris 4 items
provision uris 2 items
provision labels 2 items
toulmin {"backing_provisions": ["III.7", "III.8.a"], "data_summary": "Engineer A, a direct commercial competitor of XYZ Engineers through ABC Consultants, became aware of XYZ Engineers\u0027...
aligned question uri case-19#Q2
aligned question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
addresses questions 8 items
board resolution The board concluded that Engineer A had no obligation to report to the State Q board because State Q's rules did not specifically require project-level attribution placement, meaning no clear rule vio...
options 2 items
intensity score 0.72
qc alignment score 0.82
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer A: Jurisdiction-Differentiated Reporting Obligation for Competitor Misconduct Across State Q and State Z
llm refined question Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear ...

Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to report, rather than relying solely on the NSPE Code of Ethics to assess the conduct?

URI http://proethica.org/ontology/case-19#DP15
focus id DP15
focus number 15
description Engineer A: Multi-Jurisdiction Ethics Review Obligation Before Acting on Competitor Misconduct
decision question Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to r...
role uri http://proethica.org/ontology/case/19#Engineer
role label Engineer A
obligation uri http://proethica.org/ontology/case/19#Multi-Jurisdiction_Ethics_Review_Obligation_Engineer_A_Both_States
obligation label Multi-Jurisdiction Ethics Review Obligation — Engineer A Both States
constraint uri http://proethica.org/ontology/case/19#Competitor_Qualification_Proposal_Misconduct_Reporting_Obligation_Engineer_A_State_Z
constraint label Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Z
involved action uris 4 items
provision uris 2 items
provision labels 2 items
toulmin {"backing_provisions": ["III.8.a", "II.5.a"], "data_summary": "Engineer A, practicing in both State Q and State Z, became aware of XYZ Engineers\u0027 qualification proposal attribution practice...
aligned question uri case-19#Q9
aligned question text Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter st...
addresses questions 3 items
board resolution The board concluded that Engineer A's independent review of the jurisdiction-specific licensing rules of both State Q and State Z was essential to correctly identifying the State Z violation and calib...
options 2 items
intensity score 0.68
qc alignment score 0.78
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer A: Multi-Jurisdiction Ethics Review Obligation Before Acting on Competitor Misconduct
llm refined question Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to r...

Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule violation is identifiable there but not under State Q's more permissive standard?

URI http://proethica.org/ontology/case-19#DP16
focus id DP16
focus number 16
description Engineer A discovers that XYZ Engineers' qualification proposals list Engineer B's prior-employer projects without per-project attribution, potentially violating State Z's specific licensing rules. En...
decision question Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule...
role uri http://proethica.org/ontology/case/19#Engineer_A
role label Engineer A
obligation uri http://proethica.org/ontology/case/19#Multi-Jurisdiction_Ethics_Review_Obligation_Engineer_A_Both_States
obligation label Multi-Jurisdiction Ethics Review and Mandatory Competitor Misconduct Reporting Obligation
constraint uri http://proethica.org/ontology/case/19#Competitor_Misconduct_Reporting_Competitive_Interest_Neutrality_Constraint_Engineer_A_State_Z_Reporting
constraint label Competitor Misconduct Reporting Competitive Interest Neutrality Constraint
involved action uris 4 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.7", "III.8.a"], "data_summary": "Engineer A, a direct commercial competitor of XYZ Engineers through ABC Consultants, discovers that XYZ Engineers\u0027...
aligned question uri case-19#Q2
aligned question text Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
addresses questions 9 items
board resolution The Board concluded that Engineer A was obligated to report to the State Z board because a specific and clear rule violation was identifiable on the facts after jurisdiction-specific rule review, maki...
options 3 items
intensity score 0.75
qc alignment score 0.88
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer A discovers that XYZ Engineers' qualification proposals list Engineer B's prior-employer projects without per-project attribution, potentially violating State Z's specific licensing rules. En...
llm refined question Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule...

Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a single prefatory section of Engineer B's qualifications, in order to satisfy both the NSPE Code's honesty standard and the more specific attribution requirements of State Z?

URI http://proethica.org/ontology/case-19#DP17
focus id DP17
focus number 17
description Engineer B and XYZ Engineers must decide how to structure attribution disclosures for Engineer B's prior-employer projects in qualification proposals submitted in State Q and State Z — specifically wh...
decision question Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a singl...
role uri http://proethica.org/ontology/case/19#Engineer_B
role label Engineer B / XYZ Engineers
obligation uri http://proethica.org/ontology/case/19#Honesty_in_Professional_Representations_Obligation_XYZ_Engineers_Qualification_Proposals_Both_States
obligation label Honesty in Professional Representations Obligation and Qualification Proposal Attribution Integrity
constraint uri http://proethica.org/ontology/case/19#Prior-Employer_Project_Credit_Scope_Limitation_Obligation_Engineer_B_XYZ_Engineers_State_Z
constraint label Prior-Employer Project Credit Scope Limitation Obligation
involved action uris 4 items
provision uris 2 items
provision labels 3 items
toulmin {"backing_provisions": ["II.5.a", "III.9", "III.9.a"], "data_summary": "Engineer B joins XYZ Engineers, which is entering the markets of State Q and State Z. XYZ Engineers prepares qualification...
aligned question uri case-19#Q1
aligned question text Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
addresses questions 12 items
board resolution The Board concluded that Engineer B's and XYZ Engineers' proposal practices were not unethical under the NSPE Code of Ethics because the prefatory attribution notice prevented the proposals from const...
options 2 items
intensity score 0.8
qc alignment score 0.85
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer B and XYZ Engineers must decide how to structure attribution disclosures for Engineer B's prior-employer projects in qualification proposals submitted in State Q and State Z — specifically wh...
llm refined question Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a singl...
Phase 4: Narrative Elements
84
Characters 12
XYZ Engineers Competing Firm stakeholder An ABC Consultants bridge and culvert engineer who has ident...
Engineer A Competing Engineering Firm Employee protagonist A careful ethical analyst applying both the NSPE Code and th...
Engineer A Multi-Jurisdiction Ethics Reviewer protagonist Reviews NSPE Code and state licensing board rules of both St...
Engineer B Multi-State Project Manager decision-maker A newly hired XYZ Engineers project manager who incorporated...
ABC Consultants Employer stakeholder An engineering consulting firm whose competitive standing in...
State Q Licensing Board Regulatory Authority authority State licensing board in State Q whose rules (patterned afte...
State Z Licensing Board Regulatory Authority authority State licensing board in State Z whose rules have a unique l...
Engineer A Jurisdiction-Specific Misconduct Reporter protagonist Engineer A identified that Engineer B and XYZ Engineers may ...
Engineer B Prior-Firm Project Credit Engineer stakeholder Engineer B, now employed at XYZ Engineers, included projects...
XYZ Engineers Preferred AE Firm stakeholder XYZ Engineers submitted qualification proposals in State Q a...
Engineer Doe Industry Manufacturing Process Client Reporter stakeholder Engineer Doe was retained to evaluate a manufacturing proces...
Industry Manufacturing Process Client Stakeholder stakeholder The industry client retained Engineer Doe to evaluate a manu...
Timeline Events 35 -- synthesized from Step 3 temporal dynamics
case_begins state Initial Situation synthesized

The case originates in a professional environment where engineering firms are only partially disclosing the original authors of prior work in their marketing proposals, raising questions about attribution ethics across multiple jurisdictions with differing regulatory standards.

Engineer B Completes Prior Projects action Action Step 3

Engineer B successfully completes a series of engineering projects, producing a body of professional work and documented experience that will later become central to a dispute over how that work is credited and represented to prospective clients.

XYZ Hires Engineer B action Action Step 3

Engineering firm XYZ brings Engineer B on board as a new hire, gaining access to Engineer B's professional background and prior project portfolio, which the firm subsequently incorporates into its client-facing marketing and proposal materials.

Partial Attribution Disclosure in Proposals action Action Step 3

XYZ begins submitting proposals to potential clients that reference Engineer B's prior projects without fully or accurately disclosing the context in which that work was performed, creating a misleading impression of the firm's collective experience and capabilities.

Engineer A Investigates Marketing Practice action Action Step 3

Engineer A, upon becoming aware of XYZ's proposal practices, undertakes a deliberate review of the firm's marketing materials to determine whether the attribution of prior work meets the ethical and professional standards required of licensed engineers.

Engineer A Reviews Applicable Rules action Action Step 3

Engineer A carefully examines the applicable codes of professional conduct, licensing board regulations, and NSPE ethical guidelines to establish a clear framework for evaluating whether XYZ's disclosure practices constitute a violation of professional standards.

Engineer A Reports to State Z Board action Action Step 3

Concluding that a reportable ethical violation has occurred, Engineer A formally files a complaint with the State Z licensing board, the jurisdiction where the questionable proposals were submitted, initiating an official review of XYZ's marketing conduct.

Engineer A Declines State Q Report action Action Step 3

Engineer A makes a deliberate and reasoned decision not to file a parallel complaint with the State Q licensing board, likely determining that State Q lacks sufficient jurisdictional authority or connection to the conduct in question to warrant a separate regulatory action.

Engineer B Gains Experience automatic Event Step 3

Engineer B Gains Experience

XYZ Market Entry Occurs automatic Event Step 3

XYZ Market Entry Occurs

Attribution Ambiguity Created automatic Event Step 3

Attribution Ambiguity Created

Competitor Awareness Triggered automatic Event Step 3

Competitor Awareness Triggered

Differential State Rules Discovered automatic Event Step 3

Differential State Rules Discovered

State Z Violation Established automatic Event Step 3

State Z Violation Established

BER Precedent Applied automatic Event Step 3

BER Precedent Applied

conflict_emerges_conflict_1 automatic Conflict Emerges synthesized

Tension between Qualification Proposal Misrepresentation Non-Commission Obligation and Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q

conflict_emerges_conflict_2 automatic Conflict Emerges synthesized

Tension between Competitor Qualification Proposal Misconduct Reporting Obligation and Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting

DP1 decision Decision: DP1 synthesized

Should Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by including prior-employer attribution only in a prefatory notice at the beginning of the qualification section, or by repeating attribution information adjacent to each individual project description throughout the proposal?

DP2 decision Decision: DP2 synthesized

Should Engineer A fulfill the mandatory competitor misconduct reporting obligation by reporting XYZ Engineers' attribution practices to the licensing board of State Z — where a specific rule violation is established — while declining to report to the State Q board where no clear rule violation is found, notwithstanding Engineer A's status as a direct commercial competitor?

DP3 decision Decision: DP3 synthesized

Should Engineer B and XYZ Engineers fulfill their jurisdiction-specific licensing rule compliance obligation by identifying and applying the specific attribution requirements of each state — including State Z's more stringent project-level attribution rule — when preparing qualification proposals for submission in those jurisdictions, rather than applying a uniform format that satisfies only the less specific State Q standard?

DP4 decision Decision: DP4 synthesized

Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project description to satisfy the NSPE Code's honesty and transparency obligations?

DP5 decision Decision: DP5 synthesized

Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard — State Z's project-level requirement — as the operative benchmark for all qualification proposals, or is it ethically permissible to calibrate disclosure architecture to each state's minimum rule, accepting that the same proposal structure may comply in State Q while violating State Z?

DP6 decision Decision: DP6 synthesized

Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content of each state's rules — reporting only where a clear rule violation is identifiable and declining to report where the applicable rules do not independently prohibit the practice?

DP7 decision Decision: DP7 synthesized

Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project description throughout the proposal body?

DP8 decision Decision: DP8 synthesized

Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated?

DP9 decision Decision: DP9 synthesized

Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmark for all proposals, or calibrate disclosure architecture separately to each jurisdiction's minimum rule requirements?

DP10 decision Decision: DP10 synthesized

Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project description in order to satisfy the NSPE Code's honesty standard and applicable state licensing rules?

DP11 decision Decision: DP11 synthesized

Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither — and does Engineer A's status as a direct commercial competitor of XYZ Engineers create a conflict of interest that modifies or voids the mandatory reporting obligation?

DP12 decision Decision: DP12 synthesized

When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's project-level attribution standard to all proposals, or may they calibrate disclosure granularity to the minimum required by each individual state's rules?

DP13 decision Decision: DP13 synthesized

Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description throughout the proposal body?

DP14 decision Decision: DP14 synthesized

Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear rule violation is identifiable under State Q's standard?

DP15 decision Decision: DP15 synthesized

Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to report, rather than relying solely on the NSPE Code of Ethics to assess the conduct?

DP16 decision Decision: DP16 synthesized

Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule violation is identifiable there but not under State Q's more permissive standard?

DP17 decision Decision: DP17 synthesized

Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a single prefatory section of Engineer B's qualifications, in order to satisfy both the NSPE Code's honesty standard and the more specific attribution requirements of State Z?

board_resolution outcome Resolution synthesized

The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.

Ethical Tensions 20
Tension between Qualification Proposal Misrepresentation Non-Commission Obligation and Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q obligation vs constraint
Qualification Proposal Misrepresentation Non-Commission Obligation Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q
Tension between Competitor Qualification Proposal Misconduct Reporting Obligation and Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting obligation vs constraint
Competitor Qualification Proposal Misconduct Reporting Obligation Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting
Tension between Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation and Proportionate Misrepresentation Threshold Assessment Constraint Engineer A State Q No Reporting obligation vs constraint
Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation Proportionate Misrepresentation Threshold Assessment Constraint Engineer A State Q No Reporting
Tension between Honesty in Professional Representations Obligation — Qualification Proposals Both States and Prior-Employer Project Credit Scope Limitation Obligation obligation vs constraint
Honesty in Professional Representations Obligation — Qualification Proposals Both States Prior-Employer Project Credit Scope Limitation Obligation
Tension between Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers, Engineer B, Both States and Qualification Proposal Misrepresentation Non-Commission Obligation — XYZ Engineers, State Q obligation vs constraint
Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers, Engineer B, Both States Qualification Proposal Misrepresentation Non-Commission Obligation — XYZ Engineers, State Q
Tension between Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A, State Z and Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A, State Z Reporting obligation vs constraint
Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A, State Z Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A, State Z Reporting
Tension between Maximum Clarity Attribution in Qualification Proposals Obligation and Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z obligation vs constraint
Maximum Clarity Attribution in Qualification Proposals Obligation Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z
Tension between Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States and Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q obligation vs constraint
Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
Tension between Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States and Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States obligation vs constraint
Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
Tension between Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States and Prior-Employer Project Credit Scope Limitation Obligation — Engineer B / XYZ Engineers State Z obligation vs constraint
Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States Prior-Employer Project Credit Scope Limitation Obligation — Engineer B / XYZ Engineers State Z
Tension between Mandatory Competitor Misconduct Reporting Obligation — Engineer A Both States and Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A State Z Reporting obligation vs constraint
Mandatory Competitor Misconduct Reporting Obligation — Engineer A Both States Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A State Z Reporting
Tension between Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers / Engineer B Both States and Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q obligation vs constraint
Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers / Engineer B Both States Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
Tension between Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States and Prior-Employer Project Credit Scope Limitation Obligation — Engineer B XYZ Engineers State Z obligation vs constraint
Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States Prior-Employer Project Credit Scope Limitation Obligation — Engineer B XYZ Engineers State Z
Tension between Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Q and Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q obligation vs constraint
Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Q Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
Tension between Multi-Jurisdiction Ethics Review Obligation — Engineer A Both States and Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Z obligation vs constraint
Multi-Jurisdiction Ethics Review Obligation — Engineer A Both States Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Z
Tension between Multi-Jurisdiction Ethics Review and Mandatory Competitor Misconduct Reporting Obligation and Competitor Misconduct Reporting Competitive Interest Neutrality Constraint obligation vs constraint
Multi-Jurisdiction Ethics Review and Mandatory Competitor Misconduct Reporting Obligation Competitor Misconduct Reporting Competitive Interest Neutrality Constraint
Tension between Honesty in Professional Representations Obligation and Qualification Proposal Attribution Integrity and Prior-Employer Project Credit Scope Limitation Obligation obligation vs constraint
Honesty in Professional Representations Obligation and Qualification Proposal Attribution Integrity Prior-Employer Project Credit Scope Limitation Obligation
Engineer A has a genuine professional duty to report XYZ Engineers' qualification proposal misconduct to licensing boards, yet doing so directly benefits Engineer A's firm (ABC Consultants) by potentially disqualifying a competitor. The reporting obligation is ethically mandatory under NSPE codes, but the competitive interest neutrality constraint demands that Engineer A's motivation and action not be tainted by self-interest. Fulfilling the reporting obligation fully and promptly may be indistinguishable — to regulators, the public, and Engineer A themselves — from a strategically motivated competitive attack, undermining the integrity of the reporting act itself. This creates a genuine dilemma: delay or abstain to appear neutral, or report promptly and risk the appearance of bad faith. obligation vs constraint
Competitor Qualification Proposal Misconduct Reporting Obligation Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision
Engineer B is obligated to limit the scope of credit claimed for projects completed at a prior employer — only claiming work personally and substantially performed. Simultaneously, the attribution completeness constraint requires that any project-level attribution in qualification proposals be complete and not misleading by omission. These pull in opposite directions: narrowing credit to comply with scope limitation may produce an incomplete or misleadingly sparse project record, while providing full attribution context risks implying broader organizational credit than Engineer B legitimately holds. In State Z proposals, where licensing rules may differ, this tension is especially acute because the threshold between permissible personal attribution and impermissible firm-level misrepresentation is jurisdictionally variable. obligation vs constraint
Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z Prior-Employer Attribution Completeness Constraint XYZ Engineers Engineer B State Z Proposals
Engineer A is obligated to conduct a thorough ethics review across both State Q and State Z jurisdictions, which implies a duty to act on findings in each jurisdiction independently. However, the jurisdictional constraint limits Engineer A's standing and authority to report misconduct to boards in states where Engineer A may not be licensed or where the misconduct does not directly implicate Engineer A's practice. This creates a dilemma where comprehensive multi-jurisdiction review generates knowledge of reportable violations that Engineer A may lack the jurisdictional standing to formally report, leaving Engineer A ethically informed but procedurally constrained — potentially complicit through inaction in one state while acting appropriately in another. obligation vs constraint
Multi-Jurisdiction Ethics Review Obligation Engineer A Both States Jurisdictional Constraint Engineer A Dual-State Reporting Obligation Assessment
Decision Moments 17
Should Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by including prior-employer attribution only in a prefatory notice at the beginning of the qualification section, or by repeating attribution information adjacent to each individual project description throughout the proposal? Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States
Competing obligations: Qualification Proposal Misrepresentation Non-Commission Obligation, Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q
  • Include prior-employer attribution only in a prefatory notice at the beginning of the individual qualification section without repeating it within each project description board choice
  • Include prior-employer attribution information adjacent to each individual project description throughout the proposal body in addition to any prefatory notice
Should Engineer A fulfill the mandatory competitor misconduct reporting obligation by reporting XYZ Engineers' attribution practices to the licensing board of State Z — where a specific rule violation is established — while declining to report to the State Q board where no clear rule violation is found, notwithstanding Engineer A's status as a direct commercial competitor? Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States
Competing obligations: Competitor Qualification Proposal Misconduct Reporting Obligation, Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting
  • Report XYZ Engineers' attribution practices to the State Z licensing board in writing while declining to report to the State Q board, based on jurisdiction-specific rule analysis board choice
  • Refrain from reporting to either state's licensing board on the grounds that Engineer A's status as a direct commercial competitor creates a conflict of interest that undermines the legitimacy of any reporting action
  • Report XYZ Engineers' attribution practices to the licensing boards of both State Q and State Z in writing, treating the NSPE Code's general misrepresentation prohibition as sufficient to establish a violation in both jurisdictions
Should Engineer B and XYZ Engineers fulfill their jurisdiction-specific licensing rule compliance obligation by identifying and applying the specific attribution requirements of each state — including State Z's more stringent project-level attribution rule — when preparing qualification proposals for submission in those jurisdictions, rather than applying a uniform format that satisfies only the less specific State Q standard? Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
Competing obligations: Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation, Proportionate Misrepresentation Threshold Assessment Constraint Engineer A State Q No Reporting
  • Apply a uniform proposal format calibrated to the less specific State Q standard, placing prior-employer attribution only in a prefatory notice without reviewing whether State Z imposes more granular requirements
  • Identify and apply the specific attribution rules of each jurisdiction before preparing qualification proposals, tailoring proposal format to meet the most stringent applicable state requirement including State Z's project-level attribution rule board choice
Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project description to satisfy the NSPE Code's honesty and transparency obligations? Engineer B / XYZ Engineers
Competing obligations: Honesty in Professional Representations Obligation — Qualification Proposals Both States, Prior-Employer Project Credit Scope Limitation Obligation
  • Include prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, without repeating attribution adjacent to each project description board choice
  • Include prior-employer attribution information immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice
Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard — State Z's project-level requirement — as the operative benchmark for all qualification proposals, or is it ethically permissible to calibrate disclosure architecture to each state's minimum rule, accepting that the same proposal structure may comply in State Q while violating State Z? Engineer B / XYZ Engineers
Competing obligations: Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers, Engineer B, Both States, Qualification Proposal Misrepresentation Non-Commission Obligation — XYZ Engineers, State Q
  • Calibrate proposal attribution architecture to each state's minimum licensing rule, using prefatory-only disclosure where state rules permit it and project-level attribution only where explicitly required board choice
  • Adopt the most stringent applicable jurisdiction's attribution standard — project-level attribution adjacent to each project description — as the universal benchmark for all qualification proposals regardless of which state they are submitted in
Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content of each state's rules — reporting only where a clear rule violation is identifiable and declining to report where the applicable rules do not independently prohibit the practice? Engineer A
Competing obligations: Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A, State Z, Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A, State Z Reporting
  • Report XYZ Engineers' attribution practice to the State Z licensing board only, after reviewing and confirming a specific rule violation under State Z's project-level attribution requirement, while declining to report to the State Q board where no clear rule violation is identifiable board choice
  • Report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z on the basis that the NSPE Code's general honesty standard is sufficient to establish a violation in both jurisdictions without separately reviewing each state's specific licensing rules
  • Decline to report XYZ Engineers' attribution practice to any licensing board, citing Engineer A's status as a direct commercial competitor and the risk that the reporting mechanism would function as an instrument of competitive harm rather than genuine public protection
Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project description throughout the proposal body? Engineer B Multi-State Project Manager
Competing obligations: Maximum Clarity Attribution in Qualification Proposals Obligation, Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z
  • Include prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, without repeating attribution adjacent to each project description board choice
  • Include prior-employer attribution information immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice
Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated? Engineer A (ABC Consultants)
Competing obligations: Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States, Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
  • Report XYZ Engineers' attribution practice to the State Z licensing board only, after reviewing and confirming a specific rule violation, while declining to report to State Q where no equivalent rule violation is established board choice
  • Report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z on the basis that the NSPE Code's general misrepresentation prohibition applies in both jurisdictions regardless of rule-specific granularity
  • Decline to report to either state licensing board on the grounds that Engineer A's status as a direct commercial competitor creates a conflict of interest that disqualifies the reporting action
Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmark for all proposals, or calibrate disclosure architecture separately to each jurisdiction's minimum rule requirements? XYZ Engineers
Competing obligations: Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States, Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
  • Adopt the most stringent applicable jurisdiction's attribution standard — project-level attribution adjacent to each individual project description — as the uniform benchmark for all qualification proposals submitted across all states of practice
  • Calibrate the proposal attribution architecture separately to each jurisdiction's minimum rule requirements, using a prefatory-only notice in states with general misrepresentation prohibitions and project-level attribution only in states with explicit granularity requirements board choice
Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project description in order to satisfy the NSPE Code's honesty standard and applicable state licensing rules? Engineer B / XYZ Engineers
Competing obligations: Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States, Prior-Employer Project Credit Scope Limitation Obligation — Engineer B / XYZ Engineers State Z
  • Include prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, without repeating attribution within each project description board choice
  • Include prior-employer attribution information immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice
Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither — and does Engineer A's status as a direct commercial competitor of XYZ Engineers create a conflict of interest that modifies or voids the mandatory reporting obligation? Engineer A
Competing obligations: Mandatory Competitor Misconduct Reporting Obligation — Engineer A Both States, Competitor Misconduct Reporting Competitive Interest Neutrality Constraint — Engineer A State Z Reporting
  • Report XYZ Engineers' attribution practice to the State Z licensing board only, after reviewing and confirming a specific rule violation under State Z's project-level attribution requirement, and decline to report to State Q where no clear rule violation is established board choice
  • Report XYZ Engineers' attribution practice to the licensing boards of both State Z and State Q, treating the NSPE Code's general honesty standard as sufficient to establish a reportable violation in both jurisdictions regardless of the differential specificity of each state's rules
  • Decline to report XYZ Engineers' attribution practice to either state licensing board, on the grounds that Engineer A's status as a direct commercial competitor creates a disqualifying conflict of interest that voids the reporting obligation
When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's project-level attribution standard to all proposals, or may they calibrate disclosure granularity to the minimum required by each individual state's rules? Engineer B / XYZ Engineers
Competing obligations: Jurisdiction-Specific Licensing Rule Compliance Obligation — XYZ Engineers / Engineer B Both States, Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
  • Calibrate attribution disclosure granularity to the minimum required by each individual state's licensing rules, using a prefatory-only notice in states with general misrepresentation prohibitions and project-level attribution only where explicitly required by state rules board choice
  • Apply the most stringent applicable jurisdiction's project-level attribution requirement as the uniform standard for all qualification proposals submitted across all states, regardless of whether each individual state's rules require that level of specificity
Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description throughout the proposal body? Engineer B / XYZ Engineers
Competing obligations: Honesty in Professional Representations Obligation — XYZ Engineers Qualification Proposals Both States, Prior-Employer Project Credit Scope Limitation Obligation — Engineer B XYZ Engineers State Z
  • Disclose prior-employer attribution only in a prefatory section of Engineer B's individual qualification section, without repeating attribution adjacent to each project description board choice
  • Include prior-employer attribution notice immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory section notice
Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear rule violation is identifiable under State Q's standard? Engineer A
Competing obligations: Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Q, Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
  • Decline to report XYZ Engineers' attribution practice to the State Q licensing board after determining that State Q's rules do not specifically prohibit the prefatory-only disclosure structure board choice
  • Report XYZ Engineers' attribution practice to the State Q licensing board on the basis that the NSPE Code's general misrepresentation prohibition is sufficient to establish a reportable violation regardless of State Q's rule specificity
Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to report, rather than relying solely on the NSPE Code of Ethics to assess the conduct? Engineer A
Competing obligations: Multi-Jurisdiction Ethics Review Obligation — Engineer A Both States, Competitor Qualification Proposal Misconduct Reporting Obligation — Engineer A State Z
  • Conduct an independent, jurisdiction-specific review of the licensing board rules of each state in which XYZ Engineers' practice occurred before determining whether and where to report board choice
  • Assess XYZ Engineers' attribution practice solely against the NSPE Code of Ethics without separately reviewing the jurisdiction-specific licensing rules of State Q and State Z
Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule violation is identifiable there but not under State Q's more permissive standard? Engineer A
Competing obligations: Multi-Jurisdiction Ethics Review and Mandatory Competitor Misconduct Reporting Obligation, Competitor Misconduct Reporting Competitive Interest Neutrality Constraint
  • Review the jurisdiction-specific licensing rules of both State Q and State Z, report the identified violation to the State Z licensing board, and decline to report to the State Q board where no specific rule violation is established board choice
  • Refrain from reviewing jurisdiction-specific rules and rely solely on the NSPE Code of Ethics to assess XYZ Engineers' conduct, taking no reporting action in either state
  • Report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z without differentiating between the specificity of each state's applicable rules
Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a single prefatory section of Engineer B's qualifications, in order to satisfy both the NSPE Code's honesty standard and the more specific attribution requirements of State Z? Engineer B / XYZ Engineers
Competing obligations: Honesty in Professional Representations Obligation and Qualification Proposal Attribution Integrity, Prior-Employer Project Credit Scope Limitation Obligation
  • Include prior-employer attribution information adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice, to satisfy both the NSPE Code's spirit of honesty and State Z's specific per-project attribution requirement
  • Disclose prior-employer attribution only in a single prefatory section of Engineer B's individual qualifications without repeating attribution adjacent to each project description in the proposal body board choice