Step 4: Full View

Entities, provisions, decisions, and narrative

Conflicting Engineering Opinions
Step 4 of 5

323

Entities

0

Provisions

0

Precedents

17

Questions

20

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
Provision (e.g., I.1.) Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis Entity (hidden by default)
Edges:
informs answered by applies to
NSPE Code Provisions Referenced

No code provisions extracted yet.

Cross-Case Connections
View Extraction
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 55% Facts Similarity 36% Discussion Similarity 56% Provision Overlap 67% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: I.3, II.3.b, III.1.a, III.3.a, III.6, III.7 Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 53% Discussion Similarity 58% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: I.3, II.3.b, III.3.a Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 44% Discussion Similarity 55% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 40%
Shared provisions: I.3, III.6, III.7 Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 43% Discussion Similarity 28% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: III.7, III.7.a Same outcome True View Synthesis
Component Similarity 49% Facts Similarity 35% Discussion Similarity 36% Provision Overlap 16% Outcome Alignment 100% Tag Overlap 25%
Shared provisions: I.3, II.3.b, III.3.a Same outcome True View Synthesis
Component Similarity 51% Facts Similarity 33% Discussion Similarity 24% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: III.7.a Same outcome True View Synthesis
Component Similarity 42% Facts Similarity 41% Discussion Similarity 49% Provision Overlap 21% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.3, II.3.b, III.3.a Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 49% Discussion Similarity 27% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 20%
Shared provisions: III.1.a Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 38% Discussion Similarity 28% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: III.1.a Same outcome True View Synthesis
Component Similarity 44% Facts Similarity 42% Discussion Similarity 34% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 30%
Shared provisions: I.3, III.3.a Same outcome True View Synthesis
Questions & Conclusions
View Extraction
Each question is shown with its corresponding conclusion(s). Board questions are expanded by default.
Decisions & Arguments
View Extraction
Causal-Normative Links 4
Fulfills
  • Dual-Retained Legislative Witness Mutual Peer Criticism Permissibility Obligation
  • Dual-Retained Legislative Witness Mutual Criticism Permissibility Recognition
  • State Power Commission PE Peer Criticism Professional Deportment
  • Private Power Company PE Peer Criticism Professional Deportment
  • State_Power_Commission_PE_, _Canon_24_Due-Restraint_Peer_Criticism
  • Private_Power_Company_PE_, _Canon_24_Due-Restraint_Peer_Criticism
  • State_Power_Commission_PE_, _Canon_24_Forum_Non-Interference_with_Legislative_Duty
  • Private_Power_Company_PE_, _Canon_24_Forum_Non-Interference_with_Legislative_Duty
  • State Power Commission PE Adverse Technical Finding Non-Malicious Non-Violation
  • Private Power Company PE Adverse Technical Finding Non-Malicious Non-Violation
  • State Power Commission PE Honest Technical Disagreement Non-Violation
  • Private Power Company PE Honest Technical Disagreement Non-Violation
Violates
  • State Power Commission PE Peer Criticism Professional Deportment
  • Private Power Company PE Peer Criticism Professional Deportment
  • State_Power_Commission_PE_, _Canon_24_Due-Restraint_Peer_Criticism
  • Private_Power_Company_PE_, _Canon_24_Due-Restraint_Peer_Criticism
  • Canon 24 Due-Restraint Peer Criticism Personality-Avoidance Obligation
  • State Power Commission PE Adverse Technical Finding Non-Malicious Non-Violation
  • Private Power Company PE Adverse Technical Finding Non-Malicious Non-Violation
Fulfills
  • Dam Design Legislative Debate Post-Decision Non-Ethical-Indictment
  • BER_, _Large_Complex_Project_Multiple_Sound_Approaches_Non-Indictment_Recognition
  • BER_, _Public_Policy_Override_Non-Ethical-Indictment_of_Efficiency-Advocate_Engineer
  • Public Policy Override of Engineering Efficiency Non-Ethical-Indictment Obligation
  • Large Complex Project Multiple Sound Approaches Recognition Obligation
  • Dual-Retained Legislative Witness Mutual Criticism Permissibility Recognition
  • State Power Commission PE Honest Technical Disagreement Non-Violation
  • Private Power Company PE Honest Technical Disagreement Non-Violation
  • State Power Commission PE Good Faith Sincerity Sufficiency
  • Private Power Company PE Good Faith Sincerity Sufficiency
Violates
  • Dam Design Legislative Debate Post-Decision Non-Ethical-Indictment
  • State Power Commission PE Honest Technical Disagreement Non-Violation
  • Private Power Company PE Honest Technical Disagreement Non-Violation
  • BER_, _Large_Complex_Project_Multiple_Sound_Approaches_Non-Indictment_Recognition
  • BER_, _Public_Policy_Override_Non-Ethical-Indictment_of_Efficiency-Advocate_Engineer
Fulfills
  • Private Power Company PE Legislative Testimony Objectivity
  • Private Power Company PE Fact-Grounded High-Dam Opinion
  • Private Power Company PE Data Submission Completeness
  • Private Power Company PE Good Faith Sincerity Sufficiency
  • Private Power Company PE Competing Public Goods Balanced Advisory
  • Private Power Company PE Honest Public Policy Disagreement Non-Prohibition
  • Private Power Company PE Honest Technical Disagreement Non-Violation
  • Private Power Company PE Adverse Technical Finding Non-Malicious Non-Violation
  • Legislative Hearing Engineering Advocate Role Honest Conviction Prerequisite Obligation
  • Engineering Opinion Estimate-Based Indeterminacy Honest Acknowledgment Obligation
  • Private_Power_Company_PE_Legislative_Witness_, _Estimate-Based_Indeterminacy_Acknowledgment
  • Private_Power_Company_PE_, _Honest_Conviction_Advocacy_Prerequisite
  • Private_Power_Company_PE_, _Competing_Public_Goods_Balanced_Legislative_Testimony
  • Large Complex Project Multiple Sound Approaches Recognition Obligation
  • Competing Public Goods Water Supply Flood Control Power Production Balanced Testimony Obligation
  • Retained Legislative Witness Engineer Data-Submission Completeness Obligation
Violates None
Fulfills
  • State Power Commission PE Legislative Testimony Objectivity
  • State Power Commission PE Fact-Grounded Low-Dams Opinion
  • State Power Commission PE Data Submission Completeness
  • State Power Commission PE Good Faith Sincerity Sufficiency
  • State Power Commission PE Competing Public Goods Balanced Advisory
  • State Power Commission PE Honest Public Policy Disagreement Non-Prohibition
  • State Power Commission PE Honest Technical Disagreement Non-Violation
  • State Power Commission PE Adverse Technical Finding Non-Malicious Non-Violation
  • Legislative Hearing Engineering Advocate Role Honest Conviction Prerequisite Obligation
  • Engineering Opinion Estimate-Based Indeterminacy Honest Acknowledgment Obligation
  • State_Power_Commission_PE_Legislative_Witness_, _Estimate-Based_Indeterminacy_Acknowledgment
  • State_Power_Commission_PE_, _Honest_Conviction_Advocacy_Prerequisite
  • State_Power_Commission_PE_, _Competing_Public_Goods_Balanced_Legislative_Testimony
  • Large Complex Project Multiple Sound Approaches Recognition Obligation
  • Competing Public Goods Water Supply Flood Control Power Production Balanced Testimony Obligation
  • Retained Legislative Witness Engineer Data-Submission Completeness Obligation
Violates None
Decision Points 5

Should the retained engineer affirmatively disclose client affiliation and the associated interest to the legislative committee before offering engineering testimony, or proceed without disclosure and allow the testimony to be evaluated solely on its technical merits?

Options:
Affirmatively Disclose Retained Status to Committee Before presenting technical findings, explicitly inform the legislative committee of the retaining party's identity, the nature of the financial or institutional relationship, and any interest the client holds in the legislative outcome, so that committee members can properly calibrate the weight of the testimony.
Testify Without Disclosing Client Affiliation Present engineering data and conclusions without volunteering the retained relationship, relying on the committee to independently investigate affiliations and treating the technical quality of the submission as sufficient to establish credibility.
Disclose Affiliation and Explicitly Distinguish Advocacy from Independent Judgment Disclose the retained relationship and additionally clarify on the record which elements of the testimony reflect the engineer's independent professional judgment versus positions advanced at the client's direction, preserving the honest-conviction prerequisite while fully informing the legislature.

Should the testifying engineer present cost and demand projections as definitive engineering conclusions, or explicitly acknowledge to the legislative committee that the opinion rests on estimates of indeterminate factors subject to significant variance?

Options:
Present Estimates as Definitive Engineering Conclusions Deliver cost projections, demand forecasts, and efficiency comparisons as firm engineering findings without qualifying their estimate-based character, maximizing the persuasive force of the testimony in support of the client's preferred solution.
Acknowledge Estimate-Based Indeterminacy Transparently Explicitly inform the legislative committee that the engineering opinion rests on estimates of indeterminate factors, including construction cost by each method, population growth trajectories, and future equipment efficiency, and present the range of uncertainty so that the legislature can properly calibrate the evidentiary weight of the testimony.
Acknowledge Uncertainty and Identify Conditions Under Which Opposing Approach Becomes Preferable Disclose the estimate-based character of the analysis and additionally identify the specific threshold conditions: e.g., higher-than-projected population growth, lower construction cost differentials, under which the opposing engineer's solution would become the more efficient choice, fulfilling the competing-public-goods balanced advisory obligation.

When criticizing the opposing engineer's analysis before the legislative committee, should the engineer confine criticism to technical substance and data, or extend it to characterizations of the opposing engineer's professional competence or motivations?

Options:
Confine Criticism to Technical Data and Alternative Engineering Conclusions Limit all criticism of the opposing engineer's work to specific engineering findings, data interpretations, cost methodology, and technical conclusions, offering the committee an alternative analysis rather than characterizing the opposing engineer's competence, motives, or professional integrity, fully satisfying Canon 24's due-restraint requirement.
Extend Criticism to Opposing Engineer's Professional Competence or Motivations Go beyond technical disagreement to suggest that the opposing engineer's conclusions reflect incompetence, bias toward the retaining client, or professional failure, framing the disagreement as a question of the opposing engineer's fitness rather than a legitimate difference in engineering judgment.
Criticize Technical Conclusions While Explicitly Acknowledging Legitimate Disagreement Criticize the opposing engineer's specific technical methodology and conclusions on engineering grounds while affirmatively acknowledging to the committee that the opposing approach is a technically defensible alternative grounded in sound engineering principles, satisfying both Canon 24 restraint and the multiple-sound-approaches recognition obligation.

After the legislature adopts the opposing engineering approach, does the engineer whose position was rejected have a continuing ethical obligation to flag unresolved safety or technical concerns about the adopted solution, or does the legislative decision extinguish that obligation?

Options:
Treat Legislative Decision as Conclusive and Withdraw Technical Objections Accept the legislature's policy determination as a legitimate exercise of public authority that may properly reflect non-engineering considerations, recognize that the adopted approach is technically sound even if not the engineer's preferred solution, and refrain from continuing to advocate for the rejected approach in ways that could undermine implementation of the adopted plan.
Flag Residual Safety or Technical Concerns Through Appropriate Channels Where the engineer holds specific, data-grounded concerns about safety or technical adequacy of the adopted approach, distinct from mere preference for the alternative, discharge a continuing public-welfare obligation by communicating those concerns through appropriate professional or regulatory channels, not as continued advocacy for the rejected solution but as fulfillment of the paramount duty to public safety.
Publicly Continue Advocacy for Rejected Approach Post-Decision Continue publicly advocating for the rejected engineering solution after the legislative decision, treating the policy determination as reversible and using professional standing to campaign against implementation of the adopted approach, regardless of whether specific safety concerns justify continued intervention.

Should an ethics adjudicating body treat the alignment of an engineer's technical conclusion with the retaining client's financial interest, or the legislature's rejection of the engineer's preferred approach, as evidence of an ethical violation requiring sanction?

Options:
Evaluate Ethical Conduct on Good Faith and Data-Grounding Alone Assess each engineer's conduct exclusively on whether the testimony was grounded in honest professional conviction, supported by complete engineering data, and conducted with professional deportment, treating client-interest alignment and legislative outcome as irrelevant to the ethical evaluation, consistent with the good-faith sincerity sufficiency standard.
Treat Client-Interest Alignment as Presumptive Evidence of Ethical Violation Treat the fact that each engineer's technical conclusion aligned with the retaining client's preferred outcome as presumptive evidence that the testimony was advocacy rather than objective engineering judgment, shifting the burden to the engineer to affirmatively disprove client influence on the technical conclusions.
Treat Legislative Rejection of Engineering Position as Evidence of Technical Incompetence or Bad Faith Treat the legislature's adoption of the opposing approach as retrospective evidence that the rejected engineer's analysis was technically unsound or in bad faith, using the policy outcome as a proxy for the quality of the engineering judgment underlying the rejected testimony.
9 sequenced 4 actions 6 events
Action (volitional) Event (occurrence) Associated decision points
1 Testify for Single High Dam During legislative hearings, after years of public debate
2 Publicly Criticize Opposing Analysis During legislative hearings, in the course of and following each other's testimony
3 Evaluate Engineers' Ethical Conduct After the legislative hearings, in the case discussion phase
4 Legislative Debate Initiated Beginning of multi-year period (exact date unspecified)
5 Legislative Hearings Convened After multi-year debate period; specific date unspecified
6 Competing Analyses Made Public During legislative hearings
7 Professional Reputations Publicly Contested During and after legislative hearings, following mutual criticism
8 Ethics Review Triggered Retrospectively, after legislative hearings concluded (Discussion section of case)
9 Public Trust In Expertise Strained During and following legislative hearings
Causal Flow
  • Testify for Low Dams Testify for Single High Dam
  • Testify for Single High Dam Publicly Criticize Opposing Analysis
  • Publicly Criticize Opposing Analysis Evaluate_Engineers'_Ethical_Conduct
  • Evaluate_Engineers'_Ethical_Conduct Legislative Debate Initiated
Opening Context
View Extraction

You are a licensed Professional Engineer retained by the State Power Commission to testify before a state legislative committee examining proposals for water supply, flood control, and electric power production. Your engineering studies, conducted with professional colleagues, support a series of low dams as the most efficient solution to the state's needs. A competing engineer, retained by a private power company, has submitted testimony and voluminous data arguing that a single high dam would produce the same results at lower cost. The legislature has not yet acted on either proposal, and the committee is actively weighing both technical positions. The testimony you provide, and the manner in which you engage with the opposing engineer's analysis, will raise questions about professional obligation, the limits of advocacy, and the standards that apply to engineers offering technical opinions in a public forum.

From the perspective of State Power Commission PE Legislative Witness
Characters (8)
authority

A government agency responsible for public power infrastructure planning that sponsors legislative testimony to secure approval for its preferred low-dam engineering strategy.

Motivations:
  • To secure legislative support and funding for its chosen infrastructure approach, preserving institutional authority and fulfilling its public utility mission.
  • To protect and advance the commercial and strategic interests of the private power company, while navigating the tension between client loyalty and the ethical obligation to provide honest, fact-grounded engineering opinion.
  • To advance the State Power Commission's preferred engineering solution while fulfilling a public-interest mandate, though potentially under institutional pressure to defend the agency's position rather than render purely objective analysis.
stakeholder

A privately held energy enterprise that retains engineering expertise to challenge a competing public agency proposal and promote an alternative dam solution before state lawmakers.

Motivations:
  • To influence legislative outcomes in favor of a solution that aligns with its financial interests, operational efficiency goals, and competitive positioning against the public agency.
authority

Public agency whose engineering position (low dams) is represented before the state legislature; retains or employs the testifying PE.

stakeholder

Private industry entity whose engineering position (one high dam) is represented before the state legislature; retains the testifying PE.

authority

A governmental deliberative body tasked with evaluating conflicting technical recommendations on water supply, flood control, and power generation to inform sound public policy decisions.

Motivations:
  • To gather credible, objective engineering evidence sufficient to make informed legislative decisions that serve the public good, while managing the challenge of adjudicating between competing expert claims.
stakeholder

An engineer who presents a point of view on highway routing — either through a populated residential district (efficiency/cost) or through a lightly populated area (public policy) — before a public body, commission, or tribunal, bearing Canon 5 obligations to ground opinion in adequate knowledge and honest conviction.

stakeholder

An engineer working on a large, complicated public infrastructure project such as a water-power complex, where multiple technically sound approaches exist and the final adopted approach reflects both engineering diagnoses and public policy determinations, including estimates of indeterminate factors.

stakeholder

An engineer who publicly criticizes the work of another engineer before a public body, commission, court, or in engineering society gatherings or the engineering press, subject to Canon 24's due restraint obligation — required to avoid personalities and abuse, ground criticism in engineering conclusions, and offer alternative analyses.

Ethical Tensions (3)

Each retained engineer is obligated to provide objective technical testimony to the legislature, yet their very retention by an interested party (State Power Commission or Private Power Company) structurally compromises the appearance — and potentially the substance — of that objectivity. The constraint requiring disclosure of client affiliation acknowledges this tension but does not resolve it: even a fully disclosed affiliation creates pressure to advocate for the retaining client's preferred outcome (low-dams vs. high-dam), pulling against the duty to present impartial engineering judgment. The engineer must simultaneously serve as an honest technical witness to a public body and as a retained expert whose livelihood depends on the client relationship.

Obligation Vs Constraint
Affects: State Agency Legislative Hearing Witness Engineer Private Company Legislative Hearing Witness Engineer State Power Commission PE Legislative Witness Private Power Company PE Legislative Witness State Legislature Committee
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct diffuse

The obligation to submit complete data to the legislature is in tension with the practical and strategic reality that each engineer is retained by a client with a specific policy preference. Submitting truly complete data may require the engineer to include findings, studies, or analyses that undermine their retaining client's position — for example, the State Power Commission PE may possess data favorable to the high-dam option, or the Private Power Company PE may hold data supporting the low-dams alternative. The constraint demanding factual grounding and completeness forces the engineer to potentially act against their client's immediate interests, creating a dilemma between professional integrity and client loyalty. Selective omission of voluminous data is a plausible temptation that this tension makes ethically live.

Obligation Vs Constraint
Affects: State Power Commission PE Legislative Witness Private Power Company PE Legislative Witness State Agency Legislative Hearing Witness Engineer Private Company Legislative Hearing Witness Engineer State Legislature Committee Public Body Engineering Opinion Witness Engineer
Moral Intensity (Jones 1991):
Magnitude: high Probability: medium immediate direct diffuse

Engineers on opposing sides of the legislative debate are permitted — and in the interest of full legislative disclosure arguably obligated — to criticize each other's technical conclusions. However, this mutual criticism must remain within the bounds of professional deportment. The tension arises because adversarial legislative contexts incentivize aggressive discrediting of opposing expert testimony, and the line between legitimate technical critique and professionally improper disparagement of a peer's competence or integrity is difficult to maintain under advocacy pressure. An engineer who pulls punches to preserve collegial relations may fail the legislature; one who attacks too forcefully may violate professional conduct norms and damage the broader credibility of engineering expertise.

Obligation Vs Constraint
Affects: Competing Technical Advocacy Peer Engineer State Power Commission PE Legislative Witness Private Power Company PE Legislative Witness State Agency Legislative Hearing Witness Engineer Private Company Legislative Hearing Witness Engineer
Moral Intensity (Jones 1991):
Magnitude: medium Probability: high immediate direct concentrated
Opening States (10)
Mutual Inter-Engineer Technical Criticism at Legislative Hearing Multi-Year Public Infrastructure Policy Controversy Legislative Testimony Competing Principal Representation State State Power Commission Engineer Legislative Testimony Private Power Company Engineer Legislative Testimony Competing Low Dam vs. High Dam Design Approaches Engineering Judgment vs. Public Policy Override State Indeterminate Factor Engineering Estimate Reliance State Engineer Advocate Role Before Public Body State Multi-Approach Water-Power Complex Engineering Problem
Key Takeaways
  • Structural conflicts of interest in retained expert testimony cannot be fully neutralized by disclosure alone, as affiliation pressure persistently distorts the incentive to present impartial engineering judgment.
  • The completeness obligation is the most operationally demanding ethical constraint in adversarial legislative contexts, because it may require an engineer to actively undermine their own client's preferred outcome with their own findings.
  • The stalemate transformation reveals that retrospective harm does not retroactively redefine the ethical standard for testimony — an engineer's conduct must be evaluated against what was knowable and disclosed at the time, not against subsequent outcomes.