Step 4: Case Synthesis

Build a coherent case model from extracted entities

Back to Case

Balancing Client Directives and Public Welfare: Stormwater Management Dilemma

Step 4 of 5

Four-Phase Synthesis Pipeline

Entity Foundation

Passes 1-3

Analytical Extraction

2A-2E

Decision Synthesis

E1-E3 + LLM

Narrative

Timeline + Scenario

Phase 1 Entity Foundation

115 entities

Pass 1: Contextual Framework

8 Roles
17 States
13 Resources

Pass 2: Normative Requirements

10 Principles
10 Obligations
3 Constraints
16 Capabilities

Pass 3: Temporal Dynamics

38 Temporal Dynamics

Phase 2 Analytical Extraction

2A: Code Provisions 7

LLM detect algorithmic linking Case text + Phase 1 entities

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

I.4. Act for each employer or client as faithful agents or trustees.

II.1.a. If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other auth...

II.3.a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information...

II.3.b. Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter.

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

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

2B: Precedent Cases 11

LLM extraction Case text

BER Case 22-5 supporting

linked

Engineers have a primary responsibility to protect public health, safety and welfare, with particular emphasis on safe drinking water.

BER Case 20-4 supporting

linked

Engineers have a primary responsibility to protect public health, safety and welfare, with particular emphasis on safe drinking water.

BER Case 76-4 supporting

linked

An engineer's duty to protect public safety, health, and welfare is paramount and can require disclosure to authorities even against a client's wishes, once facts establishing risk are known.

BER Case 67-10 supporting

linked

It is basic to the entire concept of a profession that its members devote their interests to the public welfare, as required by the Code's ethics sections.

BER Case 07-6 distinguishing

linked

Engineers must include all relevant and pertinent facts, including known risks, in reports submitted to public authorities under Code section II.3.a; disclosure is required once information rises to the level of established fact.

BER Case 89-7 distinguishing

linked

Known safety violations confided by a client constitute facts that may require disclosure under the Code.

BER Case 99-8 distinguishing

linked

Incomplete drawings and specifications constitute facts that may require disclosure under the Code.

BER Case 04-8 distinguishing

linked

Violations of federal and state laws and regulations constitute facts that may require disclosure under the Code.

BER Case 18-9 distinguishing

linked

A known public safety risk from future surge level rise constitutes a fact that may require disclosure under the Code.

BER Case 21-2 distinguishing

linked

Known effects of sea level rise and changing precipitation patterns due to climate change constitute facts that may require disclosure under the Code.

BER Case 84-5 supporting

linked

Code section III.1.b requires engineers to inform clients when they believe a project will not be successful, including from a safety standpoint; continuing to work despite a client's refusal to fund necessary safety measures violates the engineer's paramount obligation to public welfare under section II.1.a.

2C: Questions & Conclusions 17 17

Board text parsed LLM analytical Q&C LLM Q-C linking Case text + 2A provisions

Questions (17)

Question_1 Was it ethical for Engineer L to cease work when requested by Client X, without voicing concern about increased risk?

Question_2 Would it be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified by ...

Question_101 Did Engineer L have an ethical duty to at least flag the existence of an unquantified but plausible increased risk to Client X at the time of suspensi...

Question_102 If Client X proceeds with construction without adopting the protective measures Engineer L identified, does Engineer L have any further ethical obliga...

Question_103 Should the original scope of work and preliminary design have anticipated evolving climate-driven stormwater risk (as reflected in BER Case 21-2) rath...

Question_104 Does Engineer L's acceptance of the contract with a stated duty to prevent watershed impact create a heightened, ongoing monitoring obligation that pe...

Question_201 How should Loyalty to Client X be balanced against Public Welfare in Watershed Protection when Client X's financial constraints directly conflict with...

Question_202 Does Transparency in Risk Disclosure conflict with Loyalty to Client X in the period before suspension, when Engineer L withheld mention of a still-un...

Question_203 How does Fact-Based Opinion by Engineer L constrain Transparency of Risk to Client, given that engineers are expected to voice only founded, evidence-...

Question_204 How should Public Welfare in Stormwater Design be weighed against Loyalty to Client X once the risk of runoff into the drinking water source has been ...

Question_301 From a deontological perspective, did Engineer L fulfill the duty of faithful agency to Client X by ceasing work without raising the unquantified risk...

Question_302 From a consequentialist perspective, did the outcome of Engineer L's disclosure of the quantified runoff risk justify the potential harm to Client X's...

Question_303 Did Engineer L act with professional integrity in refusing to continue the project once Client X declined to invest in the identified protective measu...

Question_401 If Engineer L had already quantified the increased runoff risk before Client X requested the work suspension, would the Board still have concluded tha...

Question_402 If the historic heavy rainfall event had not occurred, and stormwater accumulation had not increased, would Engineer L's risk concerns have ever been ...

Question_403 If local environmental standards had not explicitly required protective measures to safeguard public water sources, would the Board still have conclud...

Question_404 If Client X's financial setback had not occurred and work had never been suspended, would Engineer L's later notification of quantified risk still hav...

Conclusions (17)

Conclusion_1 It was not unethical for Engineer L to cease work when requested by Client X, without voicing concern about unquantified increased risk. Later, Engine...

Conclusion_2 It would not be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified...

Conclusion_101 The Board's finding that Engineer L acted ethically in staying silent during suspension rests on a critical distinction between a speculative, unquant...

Conclusion_102 Had Engineer L already quantified the increased runoff risk before Client X requested suspension, the ethical calculus would likely have shifted: the ...

Conclusion_103 The Board's second conclusion establishes that Engineer L cannot ethically continue work absent adequate safeguards, but it does not resolve whether E...

Conclusion_104 The Board's reasoning treats the increased runoff risk as an emergent discovery tied to a historic rainfall event, but BER Case 21-2's treatment of cl...

Conclusion_201 Regarding Q101, the Board's own distinction between a 'concern' and a 'fact' (as reflected in cases like BER Case 89-7, BER Case 99-8, and BER Case 04...

Conclusion_202 Regarding Q103, BER Case 21-2's treatment of climate-driven changes in precipitation intensity and recurrence intervals suggests that a forward-lookin...

Conclusion_203 Regarding Q104, the combination of Engineer L's explicit contractual duty to prevent watershed impact and the Code's paramount public welfare obligati...

Conclusion_204 Regarding Q301, from a deontological perspective Engineer L's duty of faithful agency to Client X (I.4) was not violated by ceasing work without voici...

Conclusion_205 Regarding Q302, from a consequentialist standpoint, Engineer L's decision to disclose the quantified runoff risk to Client X, despite the likelihood o...

Conclusion_206 Regarding Q303, Engineer L's refusal to continue the project without the identified protective measures reflects professional integrity consistent wit...

Conclusion_207 Regarding Q401, had Engineer L already quantified the increased runoff risk before Client X requested suspension, the Board would likely have reached ...

Conclusion_208 Regarding Q403, even absent explicit local environmental standards requiring protective measures, the Board's second conclusion would likely remain un...

Conclusion_301 During the suspension period, the apparent tension between Transparency in Risk Disclosure and Loyalty to Client X was resolved not by subordinating o...

Conclusion_302 Once the runoff risk moved from an unquantified concern to a confirmed, qualitatively-estimated finding, the same two principles—Public Welfare in Sto...

Conclusion_303 The case illustrates that Fact-Based Opinion functions as a temporal hinge between two otherwise competing regimes of obligation: a client-protective ...

2D: Transformation Classification

stalemate 78%

LLM classification Phase 1 entities + 2C Q&C

Engineer L's duty to disclose runoff risk was dormant during the suspension because the risk was unquantified 'speculative concern' rather than a Code-defined 'fact'; the historic rainfall event and subsequent risk study created a temporal gap after which the same underlying risk crystallized into a disclosable, paramount-safety-triggering fact, retroactively reframing what was ethically required in the earlier period (as explored in Q14/C4/C13) without actually changing what occurred at the time.

Reasoning

The case is structured around a temporal gap between an initial period (preliminary design/suspension), when Engineer L's concern was merely speculative and unquantified, and a later period (post-rainfall resumption), when additional studies transformed that concern into a qualitatively confirmed risk. The Board's entire ethical analysis (C3, C4, C7, C13, C15-C17) hinges on this evidentiary/temporal threshold — obligations that did not exist (or were not triggered) during suspension 'emerge or become clear only after time has passed,' consistent with the phase_lag pattern's core mechanism.

2E: Rich Analysis (Causal Links, Question Emergence, Resolution Patterns)

LLM batched analysis label-to-URI resolution Phase 1 entities + 2C Q&C + 2A provisions

Causal-Normative Links (8)

CausalLink_Work Suspension Request Although the Work Suspension Request itself carries no direct fulfills or violates tags, it is the causal trigger for the Nondisclosure at Suspension,...

CausalLink_Risk Notification Risk Notification fulfills the Faithful Agent Obligation and the Opinions Founded on Facts Obligation because it is the direct downstream act of the R...

CausalLink_Risk Study Conduct Risk Study Conduct fulfills the Opinions Founded on Facts Obligation because it transforms the observed Stormwater Accumulation Increase into a factua...

CausalLink_Safeguard Refusal Safeguard Refusal carries no fulfills or violates tags for the client, but it is the pivotal causal link that forces Engineer L into the Refusal to Ac...

CausalLink_Refusal to Acquiesce Refusal to Acquiesce fulfills the Public Safety Paramountcy Obligation and Project Success Advisement Obligation because, in response to the client's ...

CausalLink_Contract Acceptance By accepting the contract Engineer L fulfilled the Faithful Agent Obligation to Client X, but this same acceptance set in motion the causal chain towa...

CausalLink_Nondisclosure at Suspension Nondisclosure at Suspension fulfilled the Faithful Agent Obligation and the Opinions Founded on Facts Obligation because at that point the risk had no...

CausalLink_Work Resumption Work Resumption fulfilled the Faithful Agent Obligation by honoring the client's renewed instructions after Client Financial Recovery, but this resump...

Question Emergence (17)

QuestionEmergence_1 The question arises because the suspension request coincided with an unresolved, undisclosed safety concern, creating ambiguity over whether loyalty t...

QuestionEmergence_2 The question arises because a confirmed public risk and a client's financial refusal to mitigate it collide, forcing a choice between the paramount du...

QuestionEmergence_3 The question arises because Engineer L possessed early, unquantified awareness of a risk to a drinking water source but chose not to disclose it durin...

QuestionEmergence_4 The question emerged because Client X's refusal to adopt protective measures converts a private professional disagreement into a public safety issue, ...

QuestionEmergence_5 The question arose because the gap between when the original design was completed and when the increased risk was later confirmed as fact creates ambi...

QuestionEmergence_6 The question arises because Client X's financial setback paused paid work after Engineer L had already accepted a contract with an explicit watershed ...

QuestionEmergence_7 The question emerged because Client X's financial setback forced a suspension of protective stormwater work just as evidence of drinking water contami...

QuestionEmergence_8 The question arises because Engineer L's silence during suspension sits at the boundary between an unconfirmed technical concern and a known threat to...

QuestionEmergence_9 The question arises because Engineer L's professional obligation to only voice founded concerns collides with the public welfare imperative to disclos...

QuestionEmergence_10 The question arises because moving from a confirmed technical fact (quantified runoff risk) to an ethical conclusion requires choosing between two leg...

QuestionEmergence_11 The question arises because Engineer L's silent work suspension sits at the exact fault line between two NSPE-recognized duties, agency loyalty to the...

QuestionEmergence_12 The question arises because evaluating disclosure purely by its outcomes forces a comparison between averted public harm and inflicted client harm, an...

QuestionEmergence_13 The question arises because Engineer L's decision to stop work sits at the intersection of two legitimate but conflicting professional obligations, an...

QuestionEmergence_14 The question arises because the Board's ethical judgment hinged on the timing and evidentiary status of the runoff risk, and altering that timing test...

QuestionEmergence_15 This question arises because the Board's second conclusion depends on treating the risk as an established fact rather than a mere professional concern...

QuestionEmergence_16 The question arose because the Board's actual decision was grounded partly in a concrete environmental regulation, leaving ambiguous whether the ethic...

QuestionEmergence_17 The question arises because the financial suspension created a natural break point that could be read either as an excuse for delayed disclosure or as...

Resolution Patterns (17)

ResolutionPattern_1 Given that Engineer L's runoff concern was still preliminary and unquantified when Client X requested suspension, the Board concluded that silence at ...

ResolutionPattern_2 Because the runoff risk had by this point been quantified and Client X still refused the necessary protective investment, the Board concluded that con...

ResolutionPattern_3 Reasoning from the distinction between a hunch and a verified fact, the Board explained that Engineer L's silence was permissible only because the run...

ResolutionPattern_4 Reasoning counterfactually, the Board indicated that had Engineer L already quantified the runoff risk before Client X asked to suspend work, the same...

ResolutionPattern_5 Because withdrawal alone leaves the confirmed risk to the drinking water source unaddressed if Client X proceeds unsafeguarded, the Board suggested, d...

ResolutionPattern_6 Given that BER Case 21-2 recognizes climate-driven precipitation change as a foreseeable design factor, the Board's framing of the runoff risk as a pu...

ResolutionPattern_7 Because the risk was still unquantified when Client X requested suspension, the Board's own concern-versus-fact distinction from prior cases supports ...

ResolutionPattern_8 Given that BER Case 21-2 treats evolving precipitation risk as foreseeable for a stormwater design specialist, and Engineer L's contract explicitly ta...

ResolutionPattern_9 Because Engineer L's contract explicitly assigned a watershed protection duty and the suspension only paused paid work rather than ending the relation...

ResolutionPattern_10 Since the runoff risk remained speculative when Engineer L ceased work, the Board concludes that faithful agency under I.4 was not breached because th...

ResolutionPattern_11 Given that the risk had been quantified and threatened an entire community's drinking water, the board concluded that Engineer L's disclosure produced...

ResolutionPattern_12 Because Client X refused to invest in identified protective measures despite a confirmed risk, the board found that Engineer L's refusal to continue r...

ResolutionPattern_13 Had Engineer L already quantified the risk before Client X requested suspension, the board would have treated that quantified risk as a material fact ...

ResolutionPattern_14 Even in the absence of explicit local standards, because the risk to the community's drinking water remained real, the board concluded that Engineer L...

ResolutionPattern_15 Because Engineer L's concern was still unquantified during the suspension period, the board concluded that the apparent tension between transparency a...

ResolutionPattern_16 Given that the historic rainfall event and subsequent study turned an unquantified concern into a confirmed risk to the community's drinking water sou...

ResolutionPattern_17 Because Engineer L had no evidentiary basis for the runoff concern when Client X requested suspension, the Board found silence permissible under Fact-...

Phase 3 Decision Point Synthesis

Decision Point Synthesis (E1-E3 + Q&C Alignment + LLM)

E1-E3 algorithmic Q&C scoring LLM refinement Phase 1 entities + 2C Q&C + 2E rich analysis

E1
Obligation Coverage
-

E2
Action Mapping
-

E3
Composition
-

Q&C
Alignment
-

LLM
Refinement
-

Phase 4 Narrative Construction

Narrative Elements (Event Calculus + Scenario Seeds)

algorithmic base LLM enhancement Phase 1 entities + Phase 3 decision points

4.1
Characters
-

4.2
Timeline
-

4.3
Conflicts
-

4.4
Decisions
-

Review Entities & Commit View Synthesis

Step 4: Case Synthesis

Four-Phase Synthesis Pipeline

Phase 1 Entity Foundation

Pass 1: Contextual Framework

Pass 2: Normative Requirements

Pass 3: Temporal Dynamics

Phase 2 Analytical Extraction

2A: Code Provisions 7

2B: Precedent Cases 11

2C: Questions & Conclusions 17 17

2D: Transformation Classification

2E: Rich Analysis (Causal Links, Question Emergence, Resolution Patterns)

Phase 3 Decision Point Synthesis

Decision Point Synthesis (E1-E3 + Q&C Alignment + LLM)

Decision Points

Phase 4 Narrative Construction

Narrative Elements (Event Calculus + Scenario Seeds)