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
Community Engagement for Infrastructure Projects
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
208 entities
Pass 1: Contextual Framework
  • 16 Roles
  • 26 States
  • 16 Resources
Pass 2: Normative Requirements
  • 37 Principles
  • 12 Obligations
  • 33 Constraints
  • 37 Capabilities
Pass 3: Temporal Dynamics
  • 31 Temporal Dynamics
Phase 2 Analytical Extraction
2A: Code Provisions 9
LLM detect algorithmic linking Case text + Phase 1 entities
I.1. Hold paramount the safety, health, and welfare of the public.
I.3. Issue public statements only in an objective and truthful manner.
I.5. Avoid deceptive acts.
II.1.d. Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent ...
II.1.f. Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to p...
II.3.a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information...
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.
III.7. Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment...
2B: Precedent Cases 5
LLM extraction Case text
BER Case 60-3 distinguishing
linked
When an engineering firm provides sub-professional services, the Canons of Ethics and Rules of Professional Conduct do not necessarily apply to those services.
BER Case 98-2 analogizing
linked
The NSPE Code of Ethics applies universally to all NSPE members; it would be a major error to apply one standard of conduct to one set of members and another standard to another set.
BER Case 88-6 analogizing
linked
An engineer who is aware of a safety or public welfare concern and takes no further action after being directed to stay silent fails to fulfill the ethical obligation to hold paramount the safety, health, and welfare of the public.
BER Case 09-10 supporting
linked
When an engineer learns of a potential ethical or licensure violation by another engineer or firm, the engineer should first seek clarification from the party in question and, if not satisfied, may be required to report the matter to the state engineering licensure board.
BER Case 21-7 supporting
linked
A registered professional engineer is obliged to include relevant and pertinent information in reports; a report lacking such information fails to help stakeholders make informed decisions and does not protect public safety, health, and welfare.
2C: Questions & Conclusions 21 24
Board text parsed LLM analytical Q&C LLM Q-C linking Case text + 2A provisions
Questions (21)
Question_1 Should Engineer M challenge the validity of Firm DBA’s report?
Question_2 Should Engineer M raise any concerns with the City, as the client, and, if so, how?
Question_3 Are Firm DBA’s actions ethical?
Question_101 Does the City's explicit instruction to Firm DBA to conduct public engagement sessions in an inequitable manner implicate the City itself in an ethica...
Question_102 At what point does Engineer M's continued association with the project - after raising concerns that were dismissed by both Firm DBA and potentially t...
Question_103 Does the routing of a major public infrastructure project through Community P - a historically underserved, underrepresented, and overburdened neighbo...
Question_104 Is the Firm DBA communications and public relations department operating within an appropriate scope of engineering practice when it designs and execu...
Question_201 How should Engineer M balance the obligation to hold paramount the safety, health, and welfare of the public - including Community P - against the dut...
Question_202 Does the principle requiring engineers to report known Code violations to appropriate authorities conflict with the principle of resolving disputes at...
Question_203 Does the obligation to avoid injuring the professional reputation of another engineer conflict with the obligation to issue truthful public statements...
Question_204 When the City cites economic, political, and social considerations to justify directing inequitable public engagement, how should Engineer M weigh the...
Question_301 From a deontological perspective, did Engineer M fulfill their categorical duty to hold paramount the safety, health, and welfare of the public by rai...
Question_302 From a deontological perspective, does the City's explicit instruction to Firm DBA to conduct inequitable public engagement sessions relieve Firm DBA'...
Question_303 From a consequentialist perspective, does the harm imposed on Community P - a historically underserved, underrepresented, and overburdened neighborhoo...
Question_304 From a virtue ethics perspective, did Firm DBA's licensed professional engineers demonstrate the professional integrity and moral courage expected of ...
Question_305 From a virtue ethics perspective, did Engineer M demonstrate sufficient professional courage and integrity by expressing concern to Firm DBA but conti...
Question_306 From a consequentialist perspective, would Engineer M's reporting of Firm DBA's violations to the state licensure board produce better long-term outco...
Question_401 If Engineer M had formally documented their concerns about the inequitable session locations and lack of written comment mechanisms in writing to Firm...
Question_402 If Engineer M had refused to continue as lead engineer on the project upon learning that Firm DBA submitted the misleading public engagement report wi...
Question_403 If the City had not explicitly instructed Firm DBA to conduct the public engagement sessions in an inequitable manner, would Firm DBA's licensed profe...
Question_404 If virtual meetings and written comment mechanisms had been provided alongside the in-person sessions held in Community Q, would the participation gap...
Conclusions (24)
Conclusion_3 The actions of Firm DBA are not ethical under the Code as the services provided were under the supervision and ownership of licensed professional engi...
Conclusion_101 Beyond the Board's finding that Firm DBA's actions are unethical because its services were conducted under the supervision and ownership of licensed p...
Conclusion_102 The Board's conclusion that Firm DBA's actions are unethical does not fully address the independent ethical culpability of the City as a directing par...
Conclusion_103 The Board's finding that Firm DBA's actions are unethical has direct downstream consequences for Engineer M's own ethical standing that the Board's ex...
Conclusion_201 In response to Q101: The City's explicit instruction to Firm DBA to conduct public engagement sessions in an inequitable manner does implicate the Cit...
Conclusion_202 In response to Q102: Engineer M's continued association with the project after Firm DBA dismissed concerns and submitted the misleading report crosses...
Conclusion_203 In response to Q103: The routing of a major public infrastructure project through Community P based on a fraudulent public engagement record constitut...
Conclusion_204 In response to Q104: Firm DBA's communications and public relations department is operating in a domain that, when embedded within an engineering proj...
Conclusion_205 In response to Q201: The tension between Engineer M's obligation to hold paramount the public welfare and the duty to serve the client faithfully is r...
Conclusion_206 In response to Q202: The obligation to report known Code violations to appropriate authorities and the principle of resolving disputes at the lowest p...
Conclusion_207 In response to Q203: The obligation to avoid injuring the professional reputation of another engineer does not prohibit Engineer M from formally chall...
Conclusion_208 In response to Q301: From a deontological perspective, Engineer M did not fully discharge the categorical duty to hold paramount the safety, health, a...
Conclusion_209 In response to Q302: From a deontological perspective, the City's explicit instruction to Firm DBA to conduct inequitable public engagement sessions d...
Conclusion_210 In response to Q303: From a consequentialist perspective, the harm imposed on Community P by routing a major highway upgrade through a historically un...
Conclusion_211 In response to Q304: From a virtue ethics perspective, Firm DBA's licensed professional engineers failed to demonstrate the professional integrity and...
Conclusion_212 In response to Q305: From a virtue ethics perspective, Engineer M's decision to express concern to Firm DBA but continue associating with the project ...
Conclusion_213 In response to Q306: From a consequentialist perspective, Engineer M's reporting of Firm DBA's violations to the state licensure board - after exhaust...
Conclusion_214 In response to Q401: If Engineer M had formally documented concerns about the inequitable session locations and lack of written comment mechanisms in ...
Conclusion_215 In response to Q402: If Engineer M had refused to continue as lead engineer upon learning that Firm DBA submitted the misleading public engagement rep...
Conclusion_216 In response to Q403: The City's explicit instruction to Firm DBA to conduct the public engagement sessions in an inequitable manner is a significant f...
Conclusion_217 In response to Q404: Even if virtual meetings and written comment mechanisms had been provided alongside the in-person sessions held in Community Q, t...
Conclusion_301 The tension between client loyalty and public welfare paramountcy was not resolved in this case - it was suppressed. The City's explicit direction to ...
Conclusion_302 The obligation to avoid deceptive acts and to issue only truthful, objective professional statements came into direct tension with the principle of av...
Conclusion_303 The principle requiring engineers to resolve disputes at the lowest possible level first and the principle requiring reporting of known Code violation...
2D: Transformation Classification
oscillation 74%
LLM classification Phase 1 entities + 2C Q&C

Ethical responsibility cycles among Firm DBA, Engineer M, and the City across sequential phases: Firm DBA holds primary obligation during outreach design and execution; upon submitting the misleading report, active obligation shifts to Engineer M to escalate; upon Engineer M's escalation to the City, obligation shifts to the City to correct the record; upon City inaction, obligation returns to Engineer M to escalate to the licensure board and consider disassociation; throughout, Firm DBA's licensed PEs retain a residual unconditional duty that never fully transfers away. The Board's graduated escalation framework (C4, C10, C24) explicitly structures this cycling, with each failed resolution level reactivating Engineer M's obligation at a higher tier.

Reasoning

The Board's resolution establishes a recurring, cyclical pattern of obligation movement rather than a clean handoff or unresolved stalemate. Responsibility for the public engagement failure cycles between Firm DBA (as executing party), Engineer M (as lead engineer with oversight duty), and the City (as directing client), with each party's culpability activating and reactivating depending on the phase of escalation — Firm DBA's submission of the misleading report triggers Engineer M's escalation duty, City inaction then re-triggers Engineer M's reporting obligation, and the cycle of accountability returns to each party as prior-level resolution fails. This back-and-forth movement of active obligation across parties across sequential project phases — outreach design, session execution, report submission, escalation, and potential licensure board reporting — is structurally oscillatory rather than a single transfer or a frozen stalemate.

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_City Engages Firm DBA The City's engagement of Firm DBA initiates the procurement relationship that subsequently enables client-directed procedural manipulation, placing th...
CausalLink_Scheduling Sessions Inaccessib Firm DBA's scheduling of sessions at inaccessible times and locations directly violates the equitable public engagement constraint and the completenes...
CausalLink_Excluding Written and Virtual Excluding written and virtual participation modes compounds the inaccessible scheduling by eliminating all alternative pathways for Community P to pro...
CausalLink_Engineer M Raises Concerns Engineer M raising concerns fulfills the subcontractor ethical compliance oversight obligation and initiates the required graduated escalation sequenc...
CausalLink_Firm DBA Dismisses Concerns Firm DBA's dismissal of Engineer M's concerns violates the completeness and accuracy obligation by refusing to correct the deficient engagement proces...
CausalLink_Producing Misleading Outreach Firm DBA's production of a misleading outreach report directly violates its completeness and accuracy obligations and every constraint requiring factu...
CausalLink_Engineer M Confronts Firm DBA Engineer M's formal confrontation of Firm DBA fulfills the subcontractor ethical compliance oversight obligation and is the required first step in the...
CausalLink_Engineer M Escalates to City Engineer M's escalation to the City fulfills the graduated escalation obligation triggered by Firm DBA's non-compliance and serves the paramount publi...
Question Emergence (21)
QuestionEmergence_1 This question emerged because Firm DBA's dismissal of Engineer M's concerns left a fraudulent report in the official project record, directly triggeri...
QuestionEmergence_2 This question emerged because Firm DBA's non-compliance exhausted the lowest-level resolution pathway, making City escalation the next required step u...
QuestionEmergence_3 This question emerged because Firm DBA's conduct involved both licensed PE supervisors and a communications department, making the scope of applicable...
QuestionEmergence_4 This question emerged because the City's direct role in directing the inequitable engagement process transformed the standard client-escalation pathwa...
QuestionEmergence_5 This question emerged because the sequential dismissal of Engineer M's concerns by both Firm DBA and potentially the City created a situation where co...
QuestionEmergence_6 This question arose because the data - a fraudulent engagement report produced under City direction that routes infrastructure through an overburdened...
QuestionEmergence_7 This question arose because the organizational structure of Firm DBA - a communications department operating within a PE-supervised firm - creates gen...
QuestionEmergence_8 This question arose because the City's role as both the client and the directing party of the fraudulent engagement collapses the normal two-step stru...
QuestionEmergence_9 This question arose because the NSPE Code contains two procedural obligations - report known violations to appropriate authorities, and resolve disput...
QuestionEmergence_10 This question arose because the same act - formally contesting Firm DBA's report - is simultaneously required by one set of Code obligations and poten...
QuestionEmergence_11 This question emerged because the City's invocation of economic, political, and social justifications created a plausible but contested warrant for cl...
QuestionEmergence_12 This question emerged because the deontological framing exposed a structural gap between the procedurally correct graduated escalation pathway and the...
QuestionEmergence_13 This question emerged because the City's explicit instruction created a facially plausible defense for Firm DBA's engineers - that they were executing...
QuestionEmergence_14 This question emerged because the consequentialist framework's standard aggregation logic was destabilized by the intersection of two data facts: the ...
QuestionEmergence_15 This question emerged because the virtue ethics framework exposed the gap between the external appearance of professional compliance - following City ...
QuestionEmergence_16 This question emerged because Engineer M's conduct occupies an ambiguous middle ground between the virtue ethics ideals of courage and integrity: the ...
QuestionEmergence_17 This question emerged because consequentialist analysis requires comparing outcome streams across multiple escalation pathways, and the data shows tha...
QuestionEmergence_18 This counterfactual question emerged because the sequence of Engineer M's informal post-hoc concern-raising versus a hypothetical formal pre-session i...
QuestionEmergence_19 This counterfactual question emerged because the non-association obligation and the public welfare paramountcy obligation point in directly opposite d...
QuestionEmergence_20 This counterfactual question emerged because the City's explicit direction to Firm DBA introduces a causal and moral complexity that the standard subc...
QuestionEmergence_21 This question arose because Firm DBA's decision to schedule sessions exclusively in Community Q - without virtual, written, or geographically proximat...
Resolution Patterns (24)
ResolutionPattern_1 The board concluded that Firm DBA's actions were unethical because the services were rendered under the supervision and ownership of licensed professi...
ResolutionPattern_2 The board concluded that Firm DBA's ethical violation was compounded - not mitigated - by routing public engagement through a communications departmen...
ResolutionPattern_3 The board concluded that the City's explicit direction to conduct inequitable engagement sessions implicated the City itself in an ethical violation a...
ResolutionPattern_4 The board concluded that Engineer M's ethical standing was directly implicated by Firm DBA's unethical conduct and that Engineer M's obligations requi...
ResolutionPattern_5 The board concluded that Engineer M could not balance the obligation to serve the City against the obligation to protect Community P's welfare because...
ResolutionPattern_6 The board concluded that Engineer M's continued association crossed an ethical threshold once the misleading report was submitted and recognized as su...
ResolutionPattern_7 The board concluded that routing a major public infrastructure project through Community P on the basis of a fraudulent engagement record constitutes ...
ResolutionPattern_8 The board concluded that Firm DBA's communications and public relations department was operating within the domain of engineering ethics because its o...
ResolutionPattern_9 The board concluded that the tension between Engineer M's paramount public welfare obligation and the duty to serve the City faithfully was resolved b...
ResolutionPattern_10 The board concluded that the reporting obligation under II.1.f and the lowest-level-first resolution principle operate in sequence rather than in conf...
ResolutionPattern_11 The board concluded that Engineer M's formal challenge to Firm DBA's report does not violate the obligation to protect professional reputation because...
ResolutionPattern_12 The board concluded that Engineer M did not fully discharge the categorical duty to hold paramount public welfare because stopping at an informal obje...
ResolutionPattern_13 The board concluded that the City's explicit instruction does not relieve Firm DBA's licensed engineers of their independent duty not to deceive becau...
ResolutionPattern_14 The board concluded that the harm to Community P almost certainly outweighs the City's cited justifications because the consequentialist analysis must...
ResolutionPattern_15 The board concluded that Firm DBA's licensed engineers failed the virtue ethics standard because they demonstrated neither the practical wisdom to rec...
ResolutionPattern_16 The board concluded that Engineer M's continued association after Firm DBA dismissed concerns and submitted a fraudulent report fell short of the virt...
ResolutionPattern_17 The board concluded that licensure board reporting produces better long-term outcomes than City-level escalation alone because the City is not a neutr...
ResolutionPattern_18 The board concluded that pre-session written documentation would have produced two significant consequences regardless of Firm DBA's response - a cont...
ResolutionPattern_19 The board concluded that disassociation alone would have been ethically necessary but insufficient because it would have removed Engineer M's implicit...
ResolutionPattern_20 The board concluded that the City's explicit instruction is a significant factor that makes the City a co-responsible party in the ethical violation, ...
ResolutionPattern_21 The board concluded that virtual meetings and written comment mechanisms, while valuable, would have addressed only part of the structural inequity be...
ResolutionPattern_22 The board concluded that the tension between client loyalty and public welfare was not legitimately resolved in this case but suppressed, because the ...
ResolutionPattern_23 The board concluded that Engineer M was obligated to formally challenge Firm DBA's report because the report constituted deceptive misrepresentation r...
ResolutionPattern_24 The board concluded that graduated escalation is not a mechanism for indefinitely deferring accountability but a structured pathway with defined trigg...
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