Step 4: Case Synthesis

Build a coherent case model from extracted entities

Back to Case

Excess Stormwater Runoff

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

111 entities

Pass 1: Contextual Framework

9 Roles
21 States
10 Resources

Pass 2: Normative Requirements

5 Principles
11 Obligations
4 Constraints
14 Capabilities

Pass 3: Temporal Dynamics

37 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 transitioning employment during the pendency of a related matter has an ongoing duty to former and current employers/clients and must obtain consent before disclosing or participating in matters implicating the former employer's interests.

BER Case 16-7 supporting

linked

An engineer who discovers that data underlying prior work was inaccurate, leading to different conclusions, has an affirmative obligation to inform the client of the inaccuracy and the revised conclusions.

BER Case 95-5 supporting

linked

Engineers have an affirmative duty to disclose discovered inaccuracies in underlying data and resulting changes in conclusions to their clients.

BER Case 93-8 supporting

linked

Engineers, as members of a learned profession, have a basic ethical obligation to accept responsibility for their professional services and to use their skill and expertise for the betterment of society.

2C: Questions & Conclusions 16 18

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

Questions (16)

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 Does the fact that City Engineer J's review was only 'administrative' (for conformance with policy) rather than an independent technical/engineering r...

Question_102 To what extent should the affected property owner's own construction of extensive paved areas and a large outbuilding reduce Firm BWJ's or Engineer R'...

Question_103 Even if no actual conflict of interest exists, should City Engineer J have disclosed his prior employment at Firm BWJ to City C when reviewing BWJ's p...

Question_104 What ethical duty, if any, does Principal Engineer R owe directly to the non-client property owners harmed by the subdivision's stormwater design, as ...

Question_201 How should the timing-based reasoning that excuses City Engineer J's conflict (transition 'not recent') be reconciled with the general conflict-of-int...

Question_202 Should Principal Engineer R's duty to protect public welfare through prompt corrective design action be balanced against, or take priority over, the p...

Question_301 From a deontological perspective, did City Engineer J fulfill the duty to disclose known or potential conflicts of interest before reviewing and appro...

Question_302 From a consequentialist standpoint, does the fact that actual flooding damage occurred to nearby properties outweigh the Board's procedural conclusion...

Question_303 Did Principal Engineer R act with professional integrity by committing to re-review Firm IBM's independent analysis rather than immediately disputing ...

Question_304 Did Principal Engineer R fulfill the duty to accept personal responsibility for professional activities by agreeing to confirm whether an error exists...

Question_401 If City Engineer J's move from Firm BWJ to City C had occurred shortly before he reviewed and approved BWJ's subdivision plans, rather than well in th...

Question_402 If City Engineer J's review of BWJ's plans had involved substantive technical evaluation of stormwater calculations rather than administrative conform...

Question_403 If the property owner's paved areas and outbuilding construction had not contributed to the flooding, would the Board's directive that Principal Engin...

Question_404 If Firm IBM's independent modeling had shown post-development flows consistent with pre-development conditions rather than substantially larger flows,...

Conclusions (18)

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 The Board's finding of 'no conflict' addresses only the substantive conflict-of-interest question, not the independent, standalone disclosure obligati...

Conclusion_102 The Board's no-conflict conclusion is reinforced by the limited, administrative nature of City Engineer J's review, which was confined to conformance ...

Conclusion_103 The Board's directive that Principal Engineer R re-review Firm IBM's analysis does not resolve, and should not be read to diminish, R's independent du...

Conclusion_104 The Board's sequencing—first verify whether an error exists, then acknowledge it if confirmed—reflects a professional-accountability norm but leaves u...

Conclusion_201 Because City Engineer J's role was limited to administrative conformance review rather than independent technical verification of the stormwater calcu...

Conclusion_202 Even absent an actual conflict of interest, Code provision II.4.a covers conflicts that merely 'appear' to influence judgment. Best practice under thi...

Conclusion_203 There is a tension between the Board's timing-based reasoning (transition 'not recent' negates conflict) and the plain text of II.4.a, which condition...

Conclusion_204 The Board's approach of directing Principal Engineer R to first re-review Firm IBM's analysis before acknowledging error reflects a reasonable sequenc...

Conclusion_205 From a deontological standpoint, Engineer J's duty under II.4.a is a duty to disclose, which is procedurally distinct from a duty to recuse. Even if t...

Conclusion_206 From a consequentialist perspective, the actual harm suffered by property owners (flooding damage) is causally linked to the technical adequacy of Fir...

Conclusion_207 Principal Engineer R's willingness to re-review Firm IBM's independent findings rather than immediately dispute them demonstrates professional integri...

Conclusion_208 If City Engineer J's transition from Firm BWJ to City C had occurred immediately before his review of BWJ's plans, the Board would likely have found a...

Conclusion_209 Had Firm IBM's independent modeling shown post-development flows consistent with pre-development conditions, the Board would likely not have directed ...

Conclusion_301 The Board resolved the tension between 'Conflict of Interest in Plan Approval' and 'Conflict of Interest in Review Timing' by treating temporal remote...

Conclusion_302 The case reveals an implicit prioritization: 'Professional Accountability in Runoff Error' is treated as a precondition to 'Public Welfare in Correcti...

Conclusion_303 The Board's handling of City Engineer J's role shows that 'Conflict of Interest in Plan Approval' was implicitly diluted by an unstated assumption abo...

2D: Transformation Classification

phase_lag 68%

LLM classification Phase 1 entities + 2C Q&C

The subdivision was designed and approved under one set of assumed conditions (pre-construction modeling), but the consequences of the design (flooding, insufficient culvert capacity, excess runoff) only surfaced years later through complaints and IBM's independent post-hoc analysis, creating a retrospective obligation for Engineer R to reconfirm and potentially correct the original design. Simultaneously, City Engineer J's conflict-of-interest exposure is evaluated through a temporal lens ('not recent'), treating elapsed time as dispositive of reduced ethical risk rather than triggering renewed scrutiny.

Reasoning

The core ethical situation is structured around a temporal gap: Firm BWJ's stormwater design was approved and construction completed, but the design deficiency only became apparent after flooding occurred and Firm IBM's independent modeling retrospectively revealed 'substantially larger' post-development runoff flows. This mirrors the framework's phase_lag pattern precisely, where 'obligations emerge or become clear only after time has passed' and the original engineer 'faces obligations regarding a situation whose consequences were not apparent during original design.' A secondary, related phase-lag dynamic appears in the Board's temporal reasoning about Engineer J's employment transition, where the passage of time is used to diminish (rather than trigger) an ethical obligation.

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 (7)

CausalLink_Employment Transition Although Employment Transition carries no committed fulfills or violates edge, its causal link to the Conflict Allegation raised by City Engineer J sh...

CausalLink_Firm Retention Firm Retention lacks any recorded normative edge, yet as the action that keeps Principal Engineer R attached to Firm BWJ during the events leading to ...

CausalLink_Plan Review Approval Plan Review Approval has no committed fulfills or violates edge, but because it directly causes Plan Release and thereby Subdivision Completion, and b...

CausalLink_Property Modification Construction Property Modification Construction carries no formal normative edge, yet its causal role in producing the Exacerbation Finding attributed to the compl...

CausalLink_Independent Review Engagement Independent Review Engagement is not marked as fulfilling or violating any duty, but as the City's response to Flooding Complaints it causally produce...

CausalLink_Subdivision Design A1, the Subdivision Design by Principal Engineer R, carries no explicit fulfillment or violation label yet it is the causal root of Property Flooding,...

CausalLink_Error Acknowledgment Remediation A2, the Error Acknowledgment Remediation, fulfills the duty to acknowledge errors (III.1.a) and the duty of responsibility for professional activities...

Question Emergence (16)

QuestionEmergence_1 The question arises because City Engineer J occupied dual roles over time (former BWJ employee, then municipal reviewer) and the record shows no expli...

QuestionEmergence_2 The question emerges because the independent runoff analysis and flooding events establish that harm occurred, but it is unclear whether Engineer R's ...

QuestionEmergence_3 The question arises because the scope of City Engineer J's review is ambiguous, being labeled 'administrative' yet still resulting in approval of a pl...

QuestionEmergence_4 The question arises because the flooding damage resulted from an intervening cause (owner construction) layered on top of a preexisting design deficie...

QuestionEmergence_5 The question arises because the Code's language extends conflict of interest concerns beyond actual bias to mere appearance, creating ambiguity about ...

QuestionEmergence_6 This question arose because the harm fell on parties who never contracted with R, creating a gap between the narrow scope of R's formal engagement wit...

QuestionEmergence_7 The question emerges because BER Case 14-8 applies a timing based exception to conflict of interest rules, but City C Policy and general conflict of i...

QuestionEmergence_8 The question arises because the data create urgency (ongoing flooding harm to property owners) that pulls toward immediate action, while professional ...

QuestionEmergence_9 The question arose because the timing and nature of Engineer J's move from Firm BWJ to City C created an ambiguous conflict of interest situation that...

QuestionEmergence_10 The question arises because the Board evaluated J's conduct against a procedural rule (Conflict of Interest in Plan Approval) while the actual harm to...

QuestionEmergence_11 The question arises because the same data, a third-party analysis contradicting the engineer's prior work, can be read either as evidence demanding im...

QuestionEmergence_12 The question arises because a verified design deficiency (excess runoff, culvert insufficiency) coexists with an independent, non-engineering cause (o...

QuestionEmergence_13 The question arises because the Board's conclusion hinged on timing as an implicit rebuttal to the conflict of interest warrant, and altering that tim...

QuestionEmergence_14 The question arises because the Board's conclusion depends entirely on characterizing the nature of J's review, and the case facts leave open whether ...

QuestionEmergence_15 The question arises because the Board's cautious phrasing (confirm whether an error exists) signals unresolved uncertainty about causal attribution be...

QuestionEmergence_16 This question emerges because Toulmin's warrant for requiring re-review is ambiguous between a result-contingent standard (only for actual noncomplian...

Resolution Patterns (18)

ResolutionPattern_1 Given that J's move from BWJ to City C had occurred long before his review of BWJ's subdivision plans, the Board concluded that the passage of time di...

ResolutionPattern_2 Because IBM's analysis conflicted with BWJ's original modeling but the source of the discrepancy remained unconfirmed, the Board directed R to re-revi...

ResolutionPattern_3 Even though the Board found timing sufficient to dispel an actual conflict, the appearance standard in II.4.a does not reference elapsed time, so J's ...

ResolutionPattern_4 Because J's approval involved only a check against City C's administrative requirements rather than an independent technical assessment of BWJ's runof...

ResolutionPattern_5 Although the owner's construction activity may have worsened the flooding, the Board reasoned that this contributory cause does not relieve R of the s...

ResolutionPattern_6 Given that flooding damage already occurred and an independent firm's modeling pointed to a likely design flaw, the Board's conclusion suggests Engine...

ResolutionPattern_7 Because City Engineer J's role was limited to checking conformance with policy rather than independently verifying the stormwater calculations, the Bo...

ResolutionPattern_8 Even though no actual conflict was found, the Board's analysis suggests that because II.4.a's language covers appearance of influence, best practice w...

ResolutionPattern_9 Given that the Board rested its no-conflict finding on the transition being 'not recent,' the analysis identifies a tension with the Code's plain text...

ResolutionPattern_10 Because Firm IBM's modeling raised a credible but not yet confirmed claim of design error, the Board found it reasonable for Engineer R to first re-re...

ResolutionPattern_11 Given that J appears to have privately concluded the transition was too old to matter rather than telling City C about it, the Board reasons that II.4...

ResolutionPattern_12 Because the flooding stems from BWJ's engineering design choices rather than from J's conformance-only review, the Board concludes that real-world dam...

ResolutionPattern_13 Since R responded to IBM's credible contrary analysis by agreeing to re-review rather than reflexively rejecting it, the Board treats this as integrit...

ResolutionPattern_14 Applying the reasoning of BER Case 14-8, the Board reasons that had J moved to City C shortly before reviewing BWJ's plans, the unresolved recency of ...

ResolutionPattern_15 Because IBM's actual findings showed materially higher post-development runoff, the Board directed R to re-review, but reasons that absent such a cred...

ResolutionPattern_16 Given that Engineer J's departure from Firm BWJ was temporally remote from his review of BWJ's plans, the Board concluded no conflict existed, reasoni...

ResolutionPattern_17 Given that owner-caused modifications muddied the causal picture despite IBM's runoff findings and existing flooding, the Board directed Engineer R to...

ResolutionPattern_18 Given that Engineer J's review was administrative rather than technical, the Board treated the residual conflict as low-stakes and found no conflict, ...

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 4

2C: Questions & Conclusions 16 18

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)