Step 4: Case Synthesis

Build a coherent case model from extracted entities

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Balancing Client Directives and Public Welfare: Stormwater Management Dilemma
Step 4 of 5
Four-Phase Synthesis Pipeline
1
Entity Foundation
Passes 1-3
2
Analytical Extraction
2A-2E
3
Decision Synthesis
E1-E3 + LLM
4
Narrative
Timeline + Scenario
Phase 1 Entity Foundation
218 entities
Pass 1: Contextual Framework
  • 17 Roles
  • 20 States
  • 18 Resources
Pass 2: Normative Requirements
  • 28 Principles
  • 32 Obligations
  • 36 Constraints
  • 34 Capabilities
Pass 3: Temporal Dynamics
  • 33 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 public health, safety and welfare, with particular emphasis on protecting safe drinking water sources.
BER Case 20-4 supporting
linked
Engineers have a primary responsibility to public health, safety and welfare, with particular emphasis on protecting safe drinking water sources.
BER Case 76-4 supporting
linked
An engineer's duty to public welfare is paramount over client interests; when an engineer's findings show harm to public water quality, the engineer is obligated to report those findings to the relevant public authority.
BER Case 67-10 supporting
linked
It is basic to the entire concept of a profession that its members will devote their interests to the public welfare, as made clear in the NSPE Code of Ethics.
BER Case 07-6 supporting
linked
Engineers are obligated to be objective and truthful in professional reports and must include all relevant and pertinent information, including environmental threats, in written reports submitted to public authorities.
BER Case 89-7 supporting
linked
Engineers must disclose safety violations even when such information is confided by the client.
BER Case 99-8 supporting
linked
Engineers must disclose facts related to incomplete drawings and specifications that could affect public safety or project success.
BER Case 04-8 supporting
linked
Engineers must disclose violations of federal and state laws and regulations that are discovered in the course of their work.
BER Case 18-9 supporting
linked
Engineers must disclose public safety risks related to future surge level rise when such risks are identified in the course of their work.
BER Case 21-2 supporting
linked
Engineers must disclose facts related to the effects of sea level rise and changes in precipitation intensities and recurrence intervals affected by ongoing climate change.
BER Case 84-5 analogizing
linked
An engineer who identifies a safety concern, notifies the client, but then continues work when the client refuses to address it for cost reasons has abandoned their ethical duty to the public and placed client economic concerns above the paramount obligation to public health and safety, in violation of the Code.
2C: Questions & Conclusions 20 21
Board text parsed LLM analytical Q&C LLM Q-C linking Case text + 2A provisions
Questions (20)
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 At what point does an engineer's preliminary, unquantified concern about public safety become sufficiently concrete to trigger a mandatory disclosure ...
Question_102 Does Engineer L's silence about the potential drinking water risk during the suspension period constitute a material omission under the Code, even if ...
Question_103 When Client X refuses to implement protective measures and states it will address compliance issues 'later, if needed,' does Engineer L have an indepe...
Question_104 If Engineer L withdraws from the project after Client X refuses protective measures, is Engineer L ethically obligated to ensure that any successor en...
Question_201 Does the principle of Client Loyalty as a faithful agent conflict with the principle of Proactive Risk Disclosure when Engineer L chooses not to menti...
Question_202 Does the principle of Fact-Based Disclosure Obligation conflict with the principle of Professional Competence in Risk Assessment when Engineer L's con...
Question_203 Does the principle of Non-Acquiescence to Unsafe Client Directives conflict with the principle of Client Loyalty when Client X insists on proceeding w...
Question_204 Does the principle of Environmental Stewardship applied to drinking water watershed protection conflict with the principle of Client Loyalty when fulf...
Question_301 From a deontological perspective, did Engineer L fulfill a categorical duty of candor toward Client X when Engineer L omitted mention of preliminary s...
Question_302 From a consequentialist perspective, did the Board's conclusion that omitting unquantified risk during the suspension was not unethical adequately wei...
Question_303 From a virtue ethics perspective, did Engineer L demonstrate the professional integrity and moral courage expected of a licensed engineer by notifying...
Question_304 From a deontological perspective, once Client X refused to invest in protective measures after Engineer L had quantified and communicated the stormwat...
Question_305 From a consequentialist perspective, would Engineer L continuing to work on the project after Client X's refusal of safeguards-while simultaneously ad...
Question_306 From a virtue ethics perspective, does Engineer L's willingness to continue working on the project after Client X refuses protective measures-even fra...
Question_401 If Engineer L had disclosed the preliminary, unquantified stormwater runoff concerns to Client X at the moment of work suspension, would Client X have...
Question_402 If Engineer L had refused to resume work on the project unless Client X first committed in writing to fund the protective measures identified during t...
Question_403 If Client X had agreed to implement the protective measures identified by Engineer L but only partially-addressing some but not all of the quantified ...
Question_404 If Engineer L had escalated the confirmed stormwater runoff risk directly to local environmental regulatory authorities after Client X refused protect...
Conclusions (21)
Conclusion_1 It was not unethical for Engineer L to cease work when requested by Client X, without voicing concern about unquantified increased risk.
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 conclusion that Engineer L's silence during the suspension was not unethical rests implicitly on the distinction between a quantified, fac...
Conclusion_102 The Board's conclusion that Engineer L's silence during the suspension was not unethical does not resolve the separate question of whether that silenc...
Conclusion_103 The Board's marking of Question 2 as 'unknown' - whether it would be ethical for Engineer L to continue working after Client X refuses protective meas...
Conclusion_104 Even if the Board were to conclude that Engineer L's withdrawal from the project is ethically required upon Client X's refusal of protective measures,...
Conclusion_105 The Board's analysis does not address the obligations that arise for Engineer L with respect to any successor engineer who might assume responsibility...
Conclusion_201 In response to Q101: An engineer's preliminary, unquantified concern about public safety crosses the threshold for mandatory disclosure to the client ...
Conclusion_202 In response to Q102: Engineer L's silence about the potential drinking water risk during the suspension period constitutes a material omission under C...
Conclusion_203 In response to Q103: Once Client X refused to implement protective measures after Engineer L had quantified and communicated the confirmed stormwater ...
Conclusion_204 In response to Q104: If Engineer L withdraws from the project after Client X refuses protective measures, Engineer L bears an ethical obligation to en...
Conclusion_205 In response to Q201 and Q203: The tension between Client Loyalty and Proactive Risk Disclosure is not a symmetrical conflict between equally weighted ...
Conclusion_206 In response to Q202: The Code does not limit disclosure obligations to findings that meet a threshold of full analytical rigor or quantification. Code...
Conclusion_207 In response to Q301 and Q303 (deontological and virtue ethics perspectives): From a deontological standpoint, Engineer L's omission of preliminary sto...
Conclusion_208 In response to Q302 and Q305 (consequentialist perspectives): The Board's conclusion that omitting unquantified risk during the suspension was not une...
Conclusion_209 In response to Q401 and Q402 (counterfactual questions): Had Engineer L disclosed the preliminary, unquantified stormwater runoff concerns to Client X...
Conclusion_210 In response to Q403: If Client X had agreed to implement protective measures only partially - addressing some but not all of the quantified runoff ris...
Conclusion_211 In response to Q404 and Q304 (deontological perspective on regulatory escalation): From a deontological standpoint, once Client X refused to invest in...
Conclusion_301 The tension between Client Loyalty and Proactive Risk Disclosure was resolved differently across the two phases of Engineer L's engagement, revealing ...
Conclusion_302 The principle of Non-Acquiescence to Unsafe Client Directives and the principle of Client Loyalty are not merely in tension in this case - they are st...
Conclusion_303 The principle of Environmental Stewardship applied to drinking water watershed protection and the principle of Client Loyalty interact in this case to...
2D: Transformation Classification
stalemate 82%
LLM classification Phase 1 entities + 2C Q&C

Engineer L is trapped between two irreconcilable obligation sets: the fiduciary and contractual duty to Client X (which counsels continued engagement, confidentiality, and deference to client budget decisions) and the paramount public welfare duty (which demands withdrawal, disclosure, and potentially regulatory escalation to protect the community's primary drinking water source). The Board acknowledges both obligation sets as valid — affirming that silence during suspension was not unethical while simultaneously suggesting continued work after client refusal would be impermissible — but stops short of resolving the deeper conflict over whether withdrawal alone suffices or whether regulatory notification is also required. This leaves Engineer L, Client X, and the affected community all locked within an unresolved configuration of rules where no stakeholder can act without violating at least one applicable obligation.

Reasoning

The Board's resolution does not achieve a clean handoff of responsibility nor a temporal cycling of duties; instead, it leaves multiple valid but incompatible obligations simultaneously active and unresolved. Engineer L remains bound by both Client Loyalty (Canon I.4) and the paramount Public Welfare obligation (Canon I.1), and the Board's explicit conclusions — particularly the 'unknown' designation on Q2 and the unresolved frontier on regulatory escalation — confirm that competing duties cannot both be fulfilled without one overriding the other, a determination the Board declines to make definitively. The ethical tension between confidentiality, client loyalty, proactive risk disclosure, and regulatory escalation persists across all stakeholder relationships after the Board's analysis, with no single obligation clearly discharged or transferred.

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 (6)
CausalLink_Withhold Preliminary Risk Conc Withholding preliminary risk concerns may superficially serve client loyalty during the pre-analysis phase, but it violates Engineer L's timely risk d...
CausalLink_Omit Risk During Suspension Omitting risk information during the project suspension period directly violates Engineer L's non-deception omission constraint and timely disclosure ...
CausalLink_Resume Work Without Disclosure Resuming work without disclosing identified runoff risks constitutes a serious violation of Engineer L's post-resumption disclosure obligation and pub...
CausalLink_Conduct Additional Risk Studie Conducting additional risk studies fulfills Engineer L's professional competence and fact-grounded opinion obligations by transforming preliminary con...
CausalLink_Formally Notify Client of Risk Formally notifying the client of confirmed stormwater runoff risk is the ethically required action that fulfills Engineer L's core disclosure, public ...
CausalLink_Continue Work Despite Refusal Continuing work after Client X refuses to implement protective safeguards for a confirmed stormwater runoff risk to the community's drinking water wat...
Question Emergence (20)
QuestionEmergence_1 This question arose because Engineer L's silence at suspension sits precisely at the contested boundary between the Fact-Grounded Opinion Constraint (...
QuestionEmergence_2 This question emerged because Client X's refusal transformed the ethical situation from a disclosure problem into a continuation problem: Engineer L n...
QuestionEmergence_3 This question arose because the NSPE Code and BER precedents do not explicitly define the evidentiary threshold at which a preliminary engineering con...
QuestionEmergence_4 This question emerged because the suspension event created a temporal gap in which Engineer L held a risk concern but had no active project obligation...
QuestionEmergence_5 This question arose because it sits at the most contested intersection in engineering ethics: the point where client loyalty, confidentiality, and pub...
QuestionEmergence_6 This question emerged because Engineer L's withdrawal does not extinguish the confirmed public safety risk, and the act of handing off a project witho...
QuestionEmergence_7 This question arose because the work suspension created a temporal gap in which Engineer L possessed a risk concern but had no active project context ...
QuestionEmergence_8 This question emerged because the Code's disclosure obligations were drafted with reference to factual findings, not to the intermediate epistemic sta...
QuestionEmergence_9 This question arose because BER precedents such as BER Case 84-5 establish that engineers must not acquiesce to client overrides of safety requirement...
QuestionEmergence_10 This question emerged because the NSPE Code of Ethics establishes public welfare as paramount and recognizes environmental stewardship as a profession...
QuestionEmergence_11 This question arose because Engineer L's omission during suspension sits at the contested boundary between the deontological duty of complete candor a...
QuestionEmergence_12 This question arose because the consequentialist framework demands that ethical adequacy be judged by outcomes actually produced, and the coincidence ...
QuestionEmergence_13 This question arose because virtue ethics evaluates character holistically across time, and the two-phase behavioral pattern-silence then disclosure-c...
QuestionEmergence_14 This question arose because Client X's refusal after confirmed risk disclosure creates a data state in which the faithful-agent relationship is exhaus...
QuestionEmergence_15 This question arose because the consequentialist framework requires comparing the expected-outcome distributions of two available action paths-continu...
QuestionEmergence_16 This question emerged because the same factual pattern-confirmed risk, client refusal, continued work-appeared in both Engineer L's situation and BER ...
QuestionEmergence_17 This question arose because the historic rainfall event created a counterfactual pressure point: had Client X known of even preliminary concerns at su...
QuestionEmergence_18 This question emerged because the sequential structure of Engineer L's actual conduct-resuming work and then notifying-created an apparent gap between...
QuestionEmergence_19 This question arose because the binary framing of 'full safeguards or withdrawal' obscures the practical reality that clients often implement partial ...
QuestionEmergence_20 This question emerged because the NSPE Code and BER precedents (including BER Cases 76-4 and 07-6) establish a hierarchy in which public welfare is pa...
Resolution Patterns (21)
ResolutionPattern_1 The board concluded that Engineer L's silence was not unethical because the risk concern was too preliminary and unquantified to constitute a professi...
ResolutionPattern_2 The board concluded that continued work would be unethical because the combination of confirmed risk, identified regulatory requirements, and explicit...
ResolutionPattern_3 The board refined Conclusion 1 by articulating that the permissibility of Engineer L's silence was narrowly contingent on the concern not yet having c...
ResolutionPattern_4 The board concluded that approval of suspension-era silence does not extend to approving a pattern of selective post-resumption disclosure, because II...
ResolutionPattern_5 The board resolved the 'unknown' designation on Question 2 in the direction of ethical impermissibility, reasoning that the weight of provisions I.1, ...
ResolutionPattern_6 The board concluded that Engineer L's ethical obligations upon Client X's refusal extended beyond withdrawal to mandatory notification of environmenta...
ResolutionPattern_7 The board identified a gap in the prior analysis and concluded that Engineer L bears a supplementary post-withdrawal obligation - distinct from regula...
ResolutionPattern_8 The board concluded that Engineer L's preliminary, unquantified concern crossed the mandatory disclosure threshold at the moment of suspension because...
ResolutionPattern_9 The board concluded that Engineer L's silence about the potential drinking water risk during the suspension period constituted a material omission und...
ResolutionPattern_10 The board concluded that Engineer L incurred a mandatory - not merely permissive - obligation to notify local environmental or public health regulator...
ResolutionPattern_11 The board concluded that Engineer L bears a post-withdrawal notification obligation to any successor engineer because the ethical force of withdrawal ...
ResolutionPattern_12 The board concluded that the Client Loyalty versus Proactive Risk Disclosure tension is not a symmetrical conflict but a hierarchical one in which I.1...
ResolutionPattern_13 The board concluded that the Fact-Based Disclosure Obligation applied to Engineer L's preliminary qualitative concern because II.3.b and III.1.b conte...
ResolutionPattern_14 The board concluded that Engineer L's omission during suspension represented an incomplete fulfillment of the categorical duty of candor under deontol...
ResolutionPattern_15 The board concluded that the consequentialist dimension weighs against the Board's permissive conclusion on omission during suspension because the his...
ResolutionPattern_16 The board concluded that earlier disclosure of preliminary concerns - framed as a qualified professional judgment rather than a confirmed finding - wo...
ResolutionPattern_17 The board resolved Q403 through a graduated, compliance-anchored framework: if partial safeguards bring the project into conformity with applicable en...
ResolutionPattern_18 The board concluded from a deontological standpoint that once the three triggering conditions were met - confirmed quantified risk, explicit client re...
ResolutionPattern_19 The board resolved the Client Loyalty versus Proactive Risk Disclosure tension through a phase-sensitive framework that treats the disclosure obligati...
ResolutionPattern_20 The board concluded that once Client X refused safeguards for a confirmed, quantified public health risk, the principles of Non-Acquiescence and Clien...
ResolutionPattern_21 The board concluded that Engineer L's obligations under Canon I.1 and applicable local environmental standards - interpreted through the lens of activ...
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

© Licensed under the GNU GPL v3 | Report Issue