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

Independence of Peer Reviewer

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

144 entities

Pass 1: Contextual Framework

9 Roles
15 States
5 Resources

Pass 2: Normative Requirements

24 Principles
23 Obligations
20 Constraints
25 Capabilities

Pass 3: Temporal Dynamics

23 Temporal Dynamics

Phase 2 Analytical Extraction

2A: Code Provisions 8

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.1.c. Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or ...

III.1.a. Engineers shall acknowledge their errors and shall not distort or alter the facts.

III.1.f. Engineers shall treat all persons with dignity, respect, fairness and without discrimination.

III.4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or forme...

III.7.a. Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless...

2B: Precedent Cases 3

LLM extraction Case text

BER Case 18-10 analogizing

linked

So long as the agency approves and the work complies with applicable state laws and regulations regarding conflicts of interest, it is not unethical for an engineer who conducted a peer review to later participate in a design-build joint venture submitting a proposal for the same project.

BER Case 96-8 analogizing

linked

A peer reviewer who discovers potential safety code violations must first discuss concerns with the engineer being reviewed, and if unresolved, must advise that engineer of the obligation to inform authorities and then do so.

93-3 distinguishing

linked

A prior case addressed the scenario where an owner refused to advise the engineer whose work was being reviewed of the planned peer review.

2C: Questions & Conclusions 18 20

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

Questions (18)

Question_1 Is Engineer B ethically required to make certain that Engineer A is advised of the planned peer review?

Question_2 Is Engineer A ethically required to cooperate with the peer review of Engineer B?

Question_101 If Owner had never consented to notifying Engineer A and had insisted on a covert review, would Engineer B have been ethically required to withdraw fr...

Question_102 Does Engineer A's continued involvement on the second tower project—despite known design defects in the first tower—itself raise an independent ethica...

Question_103 What obligation, if any, does Engineer B have to report the discovered design defects in the first tower to relevant authorities or the public if Owne...

Question_104 Should the Board have addressed whether Owner bears an independent ethical obligation to proactively notify Engineer A of the peer review, rather than...

Question_201 Does Engineer B's obligation of transparency and notification toward Engineer A conflict with Engineer B's duty of loyalty and confidentiality toward ...

Question_202 Does Engineer A's invocation of professional integrity and resistance to an unsolicited peer review conflict with the paramount duty to protect public...

Question_203 How does Engineer A's right to professional accountability review—implying some degree of procedural fairness in how the review is conducted—conflict ...

Question_204 Does Engineer B's safety disclosure obligation—requiring escalation when public welfare is at risk—conflict with the confidentiality constraints gover...

Question_301 From a deontological perspective, did Engineer B fulfill a categorical duty of professional transparency by insisting that Engineer A be notified of t...

Question_302 From a deontological perspective, did Engineer A violate a professional duty to acknowledge errors and cooperate with legitimate oversight when refusi...

Question_303 From a consequentialist perspective, did Engineer A's refusal to cooperate with the peer review create a net harm to public safety by leaving the seco...

Question_304 From a virtue ethics standpoint, did Engineer B demonstrate the virtues of professional integrity and collegial respect by simultaneously refusing to ...

Question_401 If Engineer B had complied with the Owner's instruction and conducted the peer review covertly without notifying Engineer A, would Engineer B have vio...

Question_402 If Engineer A had proactively disclosed the design errors in the first tower and voluntarily requested a peer review of the second tower's plans, woul...

Question_403 If the two towers had not been mirror-image designs and the second tower's plans were entirely independent of the first, would the known design defect...

Question_404 If the Owner had terminated Engineer A from the project before retaining Engineer B for the peer review, would Engineer B still have been ethically ob...

Conclusions (20)

Conclusion_1 Engineer B is ethically required to make certain that Engineer A is advised of the planned peer review.

Conclusion_101 Beyond the Board's finding that Engineer B is ethically required to notify Engineer A of the planned peer review, the notification obligation is not m...

Conclusion_102 The Board's conclusion that Engineer B must ensure Engineer A is notified implicitly resolves the tension between client loyalty and collegial transpa...

Conclusion_103 The Board's explicit conclusions address only Engineer B's notification duty and Engineer A's cooperation duty, but the case facts generate a third, u...

Conclusion_104 Engineer A's refusal to consent to the peer review, while superficially framed as a defense of professional integrity, is ethically untenable given th...

Conclusion_105 The Board's framing places the notification duty primarily on Engineer B, but the case facts also implicate an independent ethical obligation on the O...

Conclusion_201 In response to Q101: If Owner had insisted on a covert review and refused to consent to notifying Engineer A, Engineer B would have been ethically req...

Conclusion_202 In response to Q102: Engineer A's continued involvement on the second tower project despite confirmed design defects in the structurally identical fir...

Conclusion_203 In response to Q103: Engineer B bears an independent safety disclosure obligation that survives and transcends the peer review engagement itself. If O...

Conclusion_204 In response to Q104: The Board's framing of the notification duty primarily as Engineer B's responsibility is analytically incomplete. Owner, as the p...

Conclusion_205 In response to Q201: When Owner explicitly instructs secrecy, the tension between Engineer B's transparency obligation toward Engineer A and Engineer ...

Conclusion_206 In response to Q202: Engineer A's invocation of professional integrity as grounds for resisting the peer review is ethically untenable given the confi...

Conclusion_207 In response to Q301 and Q304: From a deontological perspective, Engineer B's conduct exemplifies categorical compliance with professional transparency...

Conclusion_208 In response to Q401: If Engineer B had complied with Owner's instruction and conducted the peer review covertly, Engineer B would have violated profes...

Conclusion_209 In response to Q402: If Engineer A had proactively disclosed the design errors in the first tower and voluntarily requested a peer review of the secon...

Conclusion_210 In response to Q403: Even if the two towers had not been mirror-image designs and the second tower's plans were entirely independent of the first, the...

Conclusion_211 In response to Q404: If Owner had terminated Engineer A from the project before retaining Engineer B for the peer review, Engineer B's ethical obligat...

Conclusion_301 The tension between Engineer B's duty of loyalty to the Owner as client and Engineer B's obligation of transparency toward Engineer A was resolved by ...

Conclusion_302 The tension between Engineer A's claimed right to professional integrity and resistance to an unsolicited review, and the paramount duty to protect pu...

Conclusion_303 The interaction among Engineer B's confidentiality obligations, safety disclosure duties, and the scope of the peer review engagement reveals a hierar...

2D: Transformation Classification

transfer 78%

LLM classification Phase 1 entities + 2C Q&C

The ethical obligation to ensure procedural integrity and public safety is transferred from the Owner's control (who attempted to suppress it) to Engineer B as a non-waivable categorical duty. If the Owner takes no corrective action, the obligation transfers further outward to relevant public authorities. The original holder (Owner) is relieved of discretionary control because the duty exists independently of the client relationship and falls to whichever actor can legitimately discharge it.

Reasoning

The Board resolved the central tension cleanly rather than leaving it unresolved—explicitly stating in C3 and C19 that 'no genuine tension existed once the instruction's illegitimacy is recognized,' which rules out stalemate. The dominant pattern is a one-time reassignment of obligation: the notification/safety duty shifts away from being a waivable client matter and lands definitively on Engineer B (and is escalated to authorities if the Owner fails to act), representing a clean handoff of responsibility to the appropriate actor.

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

CausalLink_Confidential Review Assignment By assigning the review under confidentiality, the Owner suppressed the disclosure mechanism that Professional Obligation III.7.a requires, and this s...

CausalLink_Peer Review Refusal Engineer B's refusal to proceed without proper consent fulfils the obligation to avoid unauthorized disclosure, and this refusal matters causally beca...

CausalLink_Notification Consent The Owner's granting of consent fulfils the disclosure obligation and opens the path for peer review, making this action causally significant because ...

CausalLink_Peer Review Consent Refusal Engineer A's refusal to allow peer review of the second tower violates multiple obligations simultaneously, and the causal gravity of this action is s...

Question Emergence (18)

QuestionEmergence_1 The question arose because Engineer A's refusal to cooperate sits at the intersection of two genuine obligations: the duty to support professional acc...

QuestionEmergence_2 This question arose because Owner removed the procedural condition, Engineer A's consent, that would have made Engineer B's participation straightforw...

QuestionEmergence_3 This question arose because the case presents two distinct wrongs by Engineer A, namely prior design defects and present obstruction of review, and th...

QuestionEmergence_4 This question arose because Engineer B possesses knowledge of a concrete public safety risk from the first tower defects but acquired that knowledge w...

QuestionEmergence_5 The question emerged because the Board's analysis focused on Engineer B's conduct under NSPE Code obligations while leaving unexamined whether the Own...

QuestionEmergence_6 This question arose because the Owner placed Engineer B in a structural conflict by instructing secrecy at the precise moment when professional norms ...

QuestionEmergence_7 This question emerged because two independently valid professional obligations collided at the moment Engineer A refused peer review while known desig...

QuestionEmergence_8 This question arose because two legitimate structural features of professional peer review pulled in opposite directions once Engineer A refused conse...

QuestionEmergence_9 This question arose because Engineer B entered the engagement under confidentiality terms that were designed to govern ordinary review scope, but the ...

QuestionEmergence_10 This question arose because the Owner's covert review instruction placed Engineer B at the intersection of two genuine professional obligations, one r...

QuestionEmergence_11 This question arose because the data record combines two distinct facts, confirmed prior design defects and an active refusal to permit review of a se...

QuestionEmergence_12 This question arose because the data established a direct causal chain from Engineer A's refusal to a structurally dangerous design remaining unreview...

QuestionEmergence_13 The question arose because Engineer B's conduct involved two distinct acts, refusing the covert review and demanding notification of Engineer A, each ...

QuestionEmergence_14 This question arose because the data presents a scenario where the procedural wrong of covert review and the substantive good of technically competent...

QuestionEmergence_15 This question arose because the original case analysis assumed an adversarial posture in which Engineer A refused consent and the Owner instructed cov...

QuestionEmergence_16 This question arose because the original case rested on a tight logical link between the known defects in the first tower and the ethical justificatio...

QuestionEmergence_17 This question arose because the original notification obligation was constructed around Engineer A's concurrent presence on the project, and the hypot...

QuestionEmergence_18 This question arose because Engineer B was placed in a situation where the Owner's covert review instruction directly contested the professional norm ...

Resolution Patterns (20)

ResolutionPattern_1 Because Owner retained Engineer B to review Engineer A's plans without Engineer A's knowledge, and because III.7.a conditions such a review on the oth...

ResolutionPattern_2 Because III.7.a independently conditions the legitimacy of a peer review on the reviewed engineer's knowledge, the board concluded that the Owner's co...

ResolutionPattern_3 Because the Owner's instruction to proceed covertly would have made Engineer B complicit in a violation of III.7.a rather than merely requiring a diff...

ResolutionPattern_4 Because Engineer B acquired knowledge of significant safety-threatening defects in the first tower through the engagement, and because Engineer A's re...

ResolutionPattern_5 Because the second tower shared a mirror-image design with a tower already known to contain significant defects, Engineer A's refusal to cooperate wit...

ResolutionPattern_6 Because Owner held complete information about the defects and had direct authority over both engineers, the board concluded that framing the notificat...

ResolutionPattern_7 Because Engineer B treated the notification requirement as a non-negotiable professional duty rather than a factor to weigh against client preferences...

ResolutionPattern_8 Because III.7.a makes notification a precondition rather than a preference, the board concluded that a technically excellent covert review would still...

ResolutionPattern_9 Because the notification requirement exists to protect Engineer A from unsolicited scrutiny without knowledge, the board concluded that Engineer A's v...

ResolutionPattern_10 Because the mirror-image relationship made it reasonable to infer that the first tower's defects were present in the second, the board concluded that ...

ResolutionPattern_11 Given that Engineer A's employment had ended before Engineer B was retained, the board concluded that the structural premise of III.7.a., an ongoing c...

ResolutionPattern_12 Given that the Owner's instruction demanded covert conduct that would deceive Engineer A, the board concluded that client loyalty ends at the point wh...

ResolutionPattern_13 Given that confirmed defects in the first tower created a concrete safety risk for the second tower of identical design, the board concluded that Engi...

ResolutionPattern_14 Given that confirmed defects in the first tower made a concrete safety risk foreseeable, the board concluded that confidentiality in this engagement w...

ResolutionPattern_15 Given that the Owner's insistence on secrecy made it impossible for Engineer B to satisfy the notification requirement that III.7.a. treats as a preco...

ResolutionPattern_16 Because the first tower's defects were confirmed and the second tower was structurally identical, the board found that Engineer A's continued involvem...

ResolutionPattern_17 Because owner inaction combined with a blocked peer review left known structural defects unaddressed in a project affecting public safety, the board c...

ResolutionPattern_18 Because Owner held the direct contractual relationship with Engineer A and issued the covert instruction, the board found that framing notification so...

ResolutionPattern_19 Because III.7.a. makes notification of the original engineer a precondition for a permissible peer review, the board found that Owner's covert instruc...

ResolutionPattern_20 Because confirmed defects in the first tower created a direct safety concern for the structurally identical second tower, the board concluded that Eng...

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

Pipeline Steps

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 8

2B: Precedent Cases 3

2C: Questions & Conclusions 18 20

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)