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
Excess Stormwater Runoff
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
180 entities
Pass 1: Contextual Framework
  • 17 Roles
  • 19 States
  • 18 Resources
Pass 2: Normative Requirements
  • 12 Principles
  • 18 Obligations
  • 26 Constraints
  • 39 Capabilities
Pass 3: Temporal Dynamics
  • 31 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.
I.6. Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.
II.4.a. Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of the...
III.1.a. Engineers shall acknowledge their errors and shall not distort or alter the facts.
III.2.d. Engineers are encouraged to adhere to the principles of sustainable development1in order to protect the environment for future generations.Footnote 1"...
III.8. Engineers shall accept personal responsibility for their professional activities, provided, however, that engineers may seek indemnification for servi...
2B: Precedent Cases 4
LLM extraction Case text
BER Case 14-8 distinguishing
linked
An engineer who transitions from a private firm to a public agency retains ongoing duties to their former employer and client, and cannot participate in matters involving that former employer without obtaining prior consent, particularly when the transition occurs in the midst of a relevant project.
BER Case 16-7 analogizing
linked
Once an engineer discovers that data or analysis upon which a report or design was based is inaccurate, there is an affirmative obligation to advise their client about the inaccurate data and revised conclusions.
BER Case 95-5 supporting
linked
Engineers have an affirmative obligation to disclose inaccurate data and revised conclusions when errors are discovered in their professional work.
BER Case 93-8 supporting
linked
A basic tenet of ethical conduct requires engineers to accept responsibility for the professional services they render, as members of a learned profession possessing skill, knowledge, and expertise expected to be used for the betterment of mankind.
2C: Questions & Conclusions 18 21
Board text parsed LLM analytical Q&C LLM Q-C linking Case text + 2A provisions
Questions (18)
Question_1 Was it ethical for City Engineer J to review and approve plans prepared by Firm BWJ, given that City Engineer J formerly worked for Firm BWJ?
Question_2 What are Principal Engineer R's ethical responsibilities under the facts?
Question_101 Did City Engineer J have an affirmative obligation to proactively disclose his prior employment relationship with Firm BWJ to City C decision-makers b...
Question_102 To what extent does the flooding harm to neighboring property owners create an independent ethical obligation for Principal Engineer R to proactively ...
Question_103 Given that third-party property owner construction - including paved areas and a large outbuilding - contributed to the flooding, does Principal Engin...
Question_104 Does the Board's conclusion that Engineer J's transition was 'not recent' rely on an unstated factual assumption about the elapsed time, and if so, wh...
Question_201 Does the principle of Objectivity in City Engineer J's plan review conflict with the principle of Loyalty to Former Employer, in that J's prior profes...
Question_202 How should Principal Engineer R balance the Error Acknowledgment Obligation - which calls for prompt and honest admission of mistakes - against the pr...
Question_203 Does the principle of Public Welfare Paramount conflict with the principle of Regulatory Compliance Verification in this case, in that strict adherenc...
Question_204 Does the principle of Conflict of Interest Recusal - which would counsel City Engineer J to step aside from reviewing Firm BWJ's plans - conflict with...
Question_301 From a deontological perspective, did City Engineer J fulfill his duty of impartiality by reviewing and approving plans submitted by his former employ...
Question_302 From a consequentialist perspective, did the downstream harm of flooding to neighboring properties - confirmed by Firm IBM's independent analysis - de...
Question_303 From a virtue ethics perspective, did Principal Engineer R demonstrate professional integrity and intellectual honesty by waiting to confirm Firm IBM'...
Question_304 From a deontological perspective, does Principal Engineer R bear an unconditional professional duty to acknowledge the stormwater design error and not...
Question_401 If City Engineer J had formally disclosed his prior employment at Firm BWJ to City C and recused himself from reviewing the subdivision plans - delega...
Question_402 If the temporal gap between City Engineer J's departure from Firm BWJ and his approval of the subdivision plans had been very recent - say, less than ...
Question_403 If Principal Engineer R had proactively commissioned an independent post-construction stormwater verification study immediately after subdivision comp...
Question_404 If the property owners who constructed extensive paved areas and a large outbuilding had not made those modifications - thereby eliminating the third-...
Conclusions (21)
Conclusion_1 Given the facts, the Board interprets that Engineer J's transition from the private sector to the public sector was not recent and there does not appe...
Conclusion_2 Although flood damage and independent consultant Firm IBM's analysis show larger flows, Principal Engineer R and Principal Engineers R's firm should c...
Conclusion_101 Beyond the Board's finding that City Engineer J's transition was 'not recent' and therefore did not create a conflict of interest, the Board's conclus...
Conclusion_102 The Board's conclusion that no conflict existed because the transition was 'not recent' does not address whether City Engineer J had an affirmative, p...
Conclusion_103 The Board's recommendation that Principal Engineer R re-review Firm IBM's analysis before acknowledging error reflects a reasonable professional stand...
Conclusion_104 The Board's recommendation that Principal Engineer R acknowledge errors if Firm BWJ's analysis confirms a mistake does not address the ethically signi...
Conclusion_105 Neither the Board's conclusions nor the explicit case record addresses whether Principal Engineer R had a proactive post-construction verification obl...
Conclusion_201 In response to Q101: City Engineer J had an affirmative obligation to proactively disclose his prior employment relationship with Firm BWJ to City C d...
Conclusion_202 In response to Q104: The Board's conclusion that Engineer J's transition was 'not recent' rests on an unstated factual assumption about the elapsed ti...
Conclusion_203 In response to Q102: The flooding harm to neighboring property owners creates an independent ethical obligation for Principal Engineer R that extends ...
Conclusion_204 In response to Q103: Principal Engineer R bears an affirmative ethical obligation to ensure that the multi-causal nature of the flooding harm is accur...
Conclusion_205 In response to Q201: A genuine tension exists between the principle of Objectivity in City Engineer J's plan review and the risk of unconscious loyalt...
Conclusion_206 In response to Q202: Principal Engineer R's obligation to independently verify Firm IBM's analysis before accepting its findings does not conflict wit...
Conclusion_207 In response to Q203: The case illustrates a fundamental limitation of regulatory compliance as a proxy for the public welfare obligation. City C's 25-...
Conclusion_208 In response to Q301 and Q302 (deontological and consequentialist perspectives on City Engineer J): From a deontological standpoint, City Engineer J fa...
Conclusion_209 In response to Q303 and Q304 (virtue ethics and deontological perspectives on Principal Engineer R): From a virtue ethics perspective, the virtue of c...
Conclusion_210 In response to Q402 and Q403 (counterfactual questions on temporal threshold and proactive verification): If the temporal gap between City Engineer J'...
Conclusion_211 In response to Q404: The counterfactual question of whether Firm BWJ's stormwater design alone - absent the third-party property owner modifications -...
Conclusion_301 The tension between Objectivity in plan review and Conflict of Interest Recusal - as applied to City Engineer J - was resolved by the Board through a ...
Conclusion_302 The tension between Error Acknowledgment Obligation and Professional Accountability - as applied to Principal Engineer R - was resolved by the Board t...
Conclusion_303 The tension between Regulatory Compliance Verification and Public Welfare Paramount - the deepest structural tension in this case - was not explicitly...
2D: Transformation Classification
stalemate 81%
LLM classification Phase 1 entities + 2C Q&C

The Board's conclusions produce a multi-party stalemate in which at least three distinct obligation clusters remain simultaneously valid and unresolved: (1) City Engineer J faces a persisting disclosure obligation under Code Section II.4.a that the Board's temporal finding does not extinguish, leaving J's ethical status indeterminate — neither fully cleared nor formally sanctioned; (2) Principal Engineer R faces a verification obligation and a proactive public-welfare notification obligation that the Board frames as sequential but which operate in practical tension when flooding harm has already materialized and affected parties require timely information; and (3) the multi-causal flooding harm creates a shared-responsibility stalemate between Firm BWJ's design deficiency and third-party property owner modifications, with no authoritative apportionment of causal weight. The Board's repeated use of qualified language — 'should confirm,' 'if Firm BWJ determines,' 'does not fully account for,' 'not explicitly resolved' — reflects an institutional acknowledgment that the ethical tensions persist rather than resolve.

Reasoning

The Board's resolution does not produce a clean handoff of obligations to a single party, nor does it cycle responsibilities between parties over time. Instead, multiple valid but incompatible obligations remain simultaneously active and unresolved: City Engineer J's disclosure obligation persists unaddressed alongside the Board's temporal-mitigation finding of no actual conflict; Principal Engineer R's error acknowledgment obligation coexists in unresolved tension with the verification-first sequencing the Board recommends; and the multi-causal flooding harm leaves both the design deficiency obligation and the third-party contribution question open simultaneously. The Board acknowledges these competing duties across nearly every conclusion without definitively prioritizing one over another, which is the defining signature of stalemate in the Marchais-Roubelat framework.

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_J Departs BWJ for City J's departure from BWJ to join the City creates the foundational revolving-door conflict condition that subsequently constrains every future interacti...
CausalLink_Developer Retains Firm BWJ The developer's retention of Firm BWJ initiates the professional engagement that triggers BWJ's and Principal Engineer R's regulatory compliance oblig...
CausalLink_R Designs Stormwater Plans R's design of the stormwater plans is the central professional act that should fulfill regulatory compliance and watershed protection obligations, but...
CausalLink_J Reviews and Approves BWJ Pla J's review and approval of plans submitted by former employer BWJ simultaneously invokes the conflict-of-interest recusal obligation (which the action...
CausalLink_City Engages IBM for Review The City's engagement of IBM as an independent reviewer fulfills the post-error independent verification obligation triggered by the flooding complain...
CausalLink_R Acknowledges Error and Remed Principal Engineer R's acknowledgment of the stormwater design error and initiation of remediation fulfills the core professional accountability and e...
Question Emergence (18)
QuestionEmergence_1 This question emerged because the action of J reviewing BWJ's plans - his former employer - placed two legitimate but competing professional obligatio...
QuestionEmergence_2 This question emerged because the convergence of a confirmed design deficiency, actual third-party harm, and causally complex flooding created a situa...
QuestionEmergence_3 This question emerged as a refinement of Q1 because the data established not merely that a conflict existed, but that J took no documented proactive d...
QuestionEmergence_4 This question emerged because the flooding harm materialized against third parties who had no contractual relationship with R, forcing a confrontation...
QuestionEmergence_5 This question emerged because IBM's identification of third-party contributing factors introduced a causation complexity that the standard error-ackno...
QuestionEmergence_6 This question emerged because the Board invoked a temporal mitigation conclusion ('not recent') without grounding it in any articulated factual standa...
QuestionEmergence_7 This question arose because the data - prior employment ties followed by approval of the former employer's deficient plans - is structurally ambiguous...
QuestionEmergence_8 This question emerged because the data places R at the intersection of two time-sensitive obligations that pull in opposite directions: the ethical no...
QuestionEmergence_9 This question arose because the regulatory standard and the public welfare obligation are structurally decoupled: a design can satisfy the letter of t...
QuestionEmergence_10 This question emerged because the two warrants do not merely conflict in their conclusions - they conflict in their underlying theories of what transp...
QuestionEmergence_11 This question emerged because City Engineer J occupied a structurally conflicted position - approving work by his former employer - without disclosing...
QuestionEmergence_12 This question emerged because Firm IBM's independent analysis provided empirical confirmation of both regulatory non-compliance and downstream harm, c...
QuestionEmergence_13 This question emerged because Principal Engineer R's sequential response - waiting for IBM confirmation before acknowledging error - sits at the inter...
QuestionEmergence_14 This question emerged because the deontological framing demands a categorical answer about R's notification duty, but the factual record introduces ca...
QuestionEmergence_15 This question emerged as a counterfactual stress-test of the conflict-of-interest analysis: if J's prior employment relationship is the central ethica...
QuestionEmergence_16 This question emerged because the Board's conclusion that no conflict existed rested entirely on the temporal gap between J's departure and his approv...
QuestionEmergence_17 This question emerged because the sequential structure of the case (design → construction → flooding → complaint → IBM review → acknowledgment) reveal...
QuestionEmergence_18 This question emerged because the IBM analysis introduced causal complexity that the original ethical framework - built around a straightforward desig...
Resolution Patterns (21)
ResolutionPattern_1 The Board concluded that Engineer J's review and approval of Firm BWJ's plans was ethical because sufficient time had passed since his departure from ...
ResolutionPattern_2 The Board concluded that Principal Engineer R's primary obligation was to re-review Firm IBM's analysis to confirm whether an error existed before for...
ResolutionPattern_3 Conclusion 103 resolved the disclosure question by finding that Code Section II.4.a's appearance-based standard creates an affirmative proactive discl...
ResolutionPattern_4 Conclusion 102 resolved the disclosure question by holding that even if elapsed time was sufficient to eliminate substantive conflict, J retained an i...
ResolutionPattern_5 Conclusion 103 resolved R's obligations by finding that the Board's verification-first recommendation establishes a floor rather than a ceiling, and t...
ResolutionPattern_6 The board concluded that Principal Engineer R's ethical obligation under Code Section III.1.a extends beyond merely acknowledging a design error to af...
ResolutionPattern_7 The board concluded that while the NSPE Code does not explicitly mandate post-construction stormwater monitoring, the public welfare paramount princip...
ResolutionPattern_8 The board concluded that City Engineer J had an affirmative proactive disclosure obligation under Code Section II.4.a that was triggered by the prior ...
ResolutionPattern_9 The board concluded that the Board's 'not recent' finding was analytically incomplete because it left the temporal threshold implicit rather than arti...
ResolutionPattern_10 The board concluded that the flooding harm to neighboring property owners created an independent ethical obligation for Principal Engineer R under Cod...
ResolutionPattern_11 The board concluded that Principal Engineer R bears an affirmative obligation to communicate the full multi-causal picture because NSPE Code Section I...
ResolutionPattern_12 The board concluded that a genuine tension existed between objectivity and unconscious loyalty, and resolved it by holding that NSPE Code Section II.4...
ResolutionPattern_13 The board concluded that R's error acknowledgment obligation and independent verification obligation operate in sequence rather than in conflict: R mu...
ResolutionPattern_14 The board concluded that NSPE Code Section I.1's public welfare mandate imposes obligations on Principal Engineer R that are not fully satisfied by re...
ResolutionPattern_15 The board concluded that J failed his duty of impartiality on deontological grounds because the duty includes a procedural dimension requiring verifia...
ResolutionPattern_16 The board concluded that both virtue ethics (candor) and deontological ethics (NSPE III.8 personal responsibility) independently required Principal En...
ResolutionPattern_17 The board concluded that a temporal gap of less than one year would have changed its conflict-of-interest finding for J, and that R's failure to commi...
ResolutionPattern_18 The board concluded that regardless of whether the design deficiency was a necessary-but-insufficient or a fully sufficient cause of the flooding, Pri...
ResolutionPattern_19 The board resolved the tension between objectivity and conflict-of-interest recusal by applying a temporal attenuation framework - concluding that suf...
ResolutionPattern_20 The board concluded that the error acknowledgment obligation and the professional accountability interest in verification are not mutually exclusive, ...
ResolutionPattern_21 The Board resolved the tension between regulatory compliance and public welfare by concluding that compliance with the 25-year recurrence interval sta...
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