Step 4: Case Synthesis

Build a coherent case model from extracted entities

Back to Case

Public Health, Safety, and Welfare—Driverless/Autonomous Vehicle

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

62 entities

Pass 1: Contextual Framework

2 Roles
10 States
2 Resources

Pass 2: Normative Requirements

4 Principles
10 Obligations
2 Constraints
9 Capabilities

Pass 3: Temporal Dynamics

23 Temporal Dynamics

Phase 2 Analytical Extraction

2A: Code Provisions 5

LLM detect algorithmic linking Case text + Phase 1 entities

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

II.1. Engineers shall hold paramount the safety, health, and welfare of the public.

II.1.b. Engineers shall approve only those engineering documents that are in conformity with applicable standards.

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.

2B: Precedent Cases 1

LLM extraction Case text

BER Case 96-4 analogizing

Engineers have an obligation to disclose safety-related technical concerns and recommend further testing/study based on technical findings alone, separate from business or financial considerations, so that employers can make informed decisions in furtherance of public health, safety, and welfare; engineers should strive to do no harm in the performance of their professional services.

2C: Questions & Conclusions 14 9

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

Questions (14)

Question_1 What are Engineer A’s ethical obligations?

Question_101 Who should bear ultimate responsibility for the ethical trade-offs encoded in the autonomous vehicle's crash-decision algorithm—the individual enginee...

Question_102 Should vehicle purchasers or passengers be informed that the autonomous system may be designed to prioritize minimizing total harm rather than maximiz...

Question_103 Given the significant uncertainty surrounding autonomous vehicle technology, does the risk assessment team have an obligation to recommend delaying de...

Question_104 What obligations does Engineer A have if the manufacturer rejects the team's safety concerns and proceeds with a crash algorithm the engineer believes...

Question_201 How should the principle of prioritizing vehicle passenger safety in the crash algorithm be balanced against the broader principle of minimizing total...

Question_202 Does the principle of public safety in autonomous vehicle risk assessment, which considers all road users, conflict with a crash algorithm principle t...

Question_203 If minimizing overall harm sometimes requires exposing vehicle passengers to greater risk than pedestrians, does this create tension with an engineer'...

Question_301 From a deontological perspective, did Engineer A fulfill his duty to hold paramount the safety, health, and welfare of the public while serving on the...

Question_302 From a consequentialist standpoint, does programming the vehicle to minimize harm to the greatest number of people (potentially sacrificing passenger ...

Question_303 Did Engineer A act with professional integrity, in the virtue-ethics sense, by committing to clearly and unambiguously voice his safety concerns and p...

Question_401 If Engineer A had not been formally assigned as a member of the engineering risk assessment team but instead only reviewed the recommendation after it...

Question_402 If the crash scenario under consideration were avoidable rather than unavoidable, would the Board's conclusion that the prime ethical obligation is to...

Question_403 If the scenario instead posed a choice between a certain fatality for the vehicle's passengers versus a probable but non-life-threatening injury to a ...

Conclusions (9)

Conclusion_1 Engineer A has a responsibility to fully and actively participate as a member of the engineering risk management team, clearly and unambiguously expre...

Conclusion_101 The Board's conclusion that Engineer A must actively participate and voice concerns presumes that individual advocacy within the team is sufficient to...

Conclusion_102 The Board's conclusion establishes a substantive ethical standard (minimize harm to the least number of persons) but does not address a procedural dim...

Conclusion_103 The Board's conclusion treats 'minimize harm to the least number of persons' as a stable ethical rule, but this formulation may not hold uniformly acr...

Conclusion_201 Regarding Q101, responsibility for the ethical trade-offs encoded in the crash-decision algorithm is not solely Engineer A's individual burden, but he...

Conclusion_202 Regarding Q104, if the manufacturer rejects the team's safety concerns and proceeds with a crash algorithm Engineer A believes is unsafe, his obligati...

Conclusion_301 The Board resolves the apparent conflict between a passenger-favoring 'Safety in Crash Algorithm Recommendation' principle and the broader 'Public Saf...

Conclusion_302 The 'Do No Harm in Autonomous Vehicle Case' principle functions as the tie-breaker that operationalizes the paramount safety duty into a concrete deci...

Conclusion_303 The Board's resolution is procedural rather than fully substantive: it prioritizes minimizing harm as the answer to the narrow crash-algorithm questio...

2D: Transformation Classification

stalemate 72%

LLM classification Phase 1 entities + 2C Q&C

Engineer A, the risk assessment team, and the manufacturer remain bound by simultaneously valid but incompletely reconciled obligations: (1) passenger-protection loyalty vs. aggregate public-safety minimization, (2) individual professional accountability vs. collective/corporate responsibility for the encoded algorithm, and (3) design-phase safety obligations vs. an unaddressed disclosure/informed-consent obligation to purchasers. None of these tensions is definitively closed off by the Board; each stakeholder continues operating under the same unresolved rule-set rather than a rule-set shifting to a new configuration.

Reasoning

The Board articulates a substantive rule (minimize harm to the least number of persons) but multiple competing obligations remain simultaneously valid and unresolved: the passenger-favoring duty of client loyalty versus the broader public-safety duty to all road users, and the individual engineer's non-transferable duty to voice concerns versus the collective/corporate locus of ultimate accountability. As C9 explicitly notes, this resolution is 'procedural rather than fully substantive,' leaving Engineer A and the manufacturer 'trapped' between principles that are not hierarchically settled beyond the narrow fact pattern presented.

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

CausalLink_Consultant Team Assignment Because New Technology Uncertainty drives the manufacturer to form the consultant team, this action carries no direct normative weight itself but sets...

CausalLink_Risk Team Participation Because Risk Team Participation causally leads to Safety Concern Expression, Engineer A's active engagement fulfills the responsibility to fully parti...

CausalLink_Safety Concern Expression Since Safety Concern Expression arises directly from Risk Team Participation and precedes the manufacturer's System Outcome Selection that causes both...

CausalLink_Technical Options Exploration Technical Options Exploration fulfills the responsibility to explore risk-mitigating alternatives and, guided by do no harm and public safety, causall...

CausalLink_Further Study Proposal Further Study Proposal fulfills the responsibility to propose additional study when needed and, following causally from Technical Options Exploration,...

Question Emergence (14)

QuestionEmergence_1 The question arises because Engineer A sits within a Pre-Utilization Study Window facing a Crash Outcome Objective Conflict where the paramount duty t...

QuestionEmergence_2 The question arises because the crash-decision algorithm embeds an ethical trade-off that no single actor fully controls, so the same data supports bo...

QuestionEmergence_3 The question arises because the engineer's paramount duty to public welfare (minimizing total harm) structurally conflicts with the individual purchas...

QuestionEmergence_4 Because the case data leaves the actual level of danger and the adequacy of further study both unresolved, it is unclear whether the paramount safety ...

QuestionEmergence_5 The question arises because Engineer A has fulfilled his procedural duties to raise concerns and propose mitigation, yet the manufacturer's rejection ...

QuestionEmergence_6 The question arises because Autonomous Vehicle Technology Uncertainty and the Crash Outcome Objective Conflict expose that no single algorithmic rule ...

QuestionEmergence_7 The question arises because Engineer A must recommend a crash algorithm where no outcome avoids harm, exposing an unresolved conflict between a public...

QuestionEmergence_8 The question arises because the same crash scenario data supports two plausible but conflicting readings of the engineer's paramount safety obligation...

QuestionEmergence_9 The question arises because an unavoidable crash scenario forces a choice between competing harms, and the ethical assessment of Engineer A's conduct ...

QuestionEmergence_10 The question arises because the Crash Outcome Objective Conflict exposes a structural disagreement over which ethical framework, aggregate welfare ver...

QuestionEmergence_11 The question arises because the Pre-Utilization Study Window created a choice point where silent deference and vocal advocacy both seemed like plausib...

QuestionEmergence_12 The question arises because the Board's conclusion rests on Engineer A's formal team assignment as the basis for his participation duty, and altering ...

QuestionEmergence_13 The question arose because the Board's ethical conclusion was built specifically on the assumption of an unavoidable crash, and changing that foundati...

QuestionEmergence_14 This question arose because BER Case 96-4 established a principle under one specific risk distribution, and reversing that distribution tests whether ...

Resolution Patterns (9)

ResolutionPattern_1 Given that Engineer A sits on the risk assessment team and the crash scenario is unavoidable, the board concluded he must actively participate, voice ...

ResolutionPattern_2 Because the manufacturer, not Engineer A individually, will implement the final crash algorithm, the board's extension concludes that his personal obl...

ResolutionPattern_3 Given that the algorithm's harm-minimizing logic could subject passengers to unexpected risk, this analysis extends Engineer A's do-no-harm duty to re...

ResolutionPattern_4 Because the board's harm-minimization rule was grounded in one specific severity configuration, this analysis concludes that reversing which party bea...

ResolutionPattern_5 Given Engineer A's status as a licensed team member alongside a corporate entity holding final authority, the board's reasoning concludes that his per...

ResolutionPattern_6 Given that the manufacturer rejected the team's safety concerns and Engineer A still believed the algorithm unsafe, the board concluded his duty does ...

ResolutionPattern_7 Given that pedestrians, cyclists, and motorcyclists were also exposed to risk from the algorithm, the board concluded that the passenger-favoring prin...

ResolutionPattern_8 Given that harm could not be avoided and the team faced a genuine trade-off between groups, the board concluded that minimizing the number of people h...

ResolutionPattern_9 Given that the board only had before it the narrow crash-algorithm trade-off, it concluded that minimizing harm answers that specific question, while ...

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