Step 4: Case Synthesis
Build a coherent case model from extracted entities
Withholding Information Useful to Client/Public Agency
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
174 entitiesPass 1: Contextual Framework
- 12 Roles
- 14 States
- 14 Resources
Pass 2: Normative Requirements
- 27 Principles
- 23 Obligations
- 21 Constraints
- 39 Capabilities
Pass 3: Temporal Dynamics
- 24 Temporal Dynamics
Phase 2 Analytical Extraction
2A: Code Provisions 4
LLM detect
algorithmic linking
Case text + Phase 1 entities
I.4.
Act for each employer or client as faithful agents or trustees.
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...
III.7.
Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment...
III.8.a.
Engineers shall conform with state registration laws in the practice of engineering.
2B: Precedent Cases 1
LLM extraction
Case text
BER Case 96-8
analogizing
linked
2C: Questions & Conclusions 17 21
Board text parsed
LLM analytical Q&C
LLM Q-C linking
Case text + 2A provisions
Questions (17)
Question_1
What are Engineer A’s ethical obligations under these facts?
Question_101
Does Engineer A have an affirmative duty to verify XYZ Engineering's certificate of authority status before concluding a violation has occurred, and i...
Question_102
To what extent does Engineer A's status as a direct competitor of Engineer X - and as the firm that previously served Client L - create a structural c...
Question_103
Does the ethical framework change if Engineer A has reason to believe that XYZ Engineering's lack of a certificate of authority is willful rather than...
Question_104
What obligation, if any, does Engineer A have toward Client L - a former client now potentially receiving engineering services from an unlicensed firm...
Question_201
Does the Collegial Pre-Reporting Engagement principle conflict with the Mandatory Reporting Obligation principle when Engineer A's competitive interes...
Question_202
Does the Competitive Fairness Dimension of XYZ Engineering's Unauthorized Practice - which benefits Engineer A if XYZ is removed from competition - co...
Question_203
Does the Licensure Integrity principle - which demands that unauthorized practice be reported to protect the profession and the public - conflict with...
Question_204
Does the Engineering Business-Profession Duality principle - which acknowledges Engineer A's legitimate competitive interests - conflict with the Juri...
Question_301
From a deontological perspective, does Engineer A have an unconditional duty to report XYZ Engineering's lack of a certificate of authority to the Sta...
Question_302
From a virtue ethics standpoint, does the collegial-first approach prescribed by the Board reflect the disposition of a professionally virtuous engine...
Question_303
From a consequentialist perspective, does the Board's graduated reporting sequence - collegial contact first, formal report only if unsatisfied - prod...
Question_304
From a deontological perspective, does the epistemic verification obligation - requiring Engineer A to confirm XYZ Engineering's non-compliance before...
Question_401
If Engineer A had no prior business relationship with Client L - and therefore had no competitive stake in XYZ Engineering's engagement - would the Bo...
Question_402
What if Engineer X, upon being contacted collegially by Engineer A, acknowledged the missing certificate of authority but continued providing engineer...
Question_403
If the BER 96-8 peer review precedent had established that confidentiality obligations fully override reporting duties even in cases of safety violati...
Question_404
What if Engineer A had immediately reported XYZ Engineering to the State P licensure board without first contacting Engineer X, and it subsequently em...
Conclusions (21)
Conclusion_1
Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question.
Conclusion_2
If Engineer A is not sufficiently satisfied with Engineer X's explanation, Engineer A may be required to report this matter to the state engineering l...
Conclusion_101
Before initiating collegial contact with Engineer X, Engineer A bears an affirmative epistemic duty to independently verify XYZ Engineering's certific...
Conclusion_102
The Board's graduated sequence - collegial contact first, formal report only if Engineer A remains unsatisfied - implicitly assumes that Engineer A ca...
Conclusion_103
The Board's recommendation that Engineer A 'may be required' to report to the State P licensure board if unsatisfied with Engineer X's explanation und...
Conclusion_104
The Board's analysis is silent on Engineer A's obligations toward Client L, yet the facts present a distinct ethical dimension that the Board's two co...
Conclusion_105
The Board's graduated reporting framework - collegial contact preceding formal regulatory report - draws implicit support from the analogous structure...
Conclusion_201
In response to Q101, Engineer A does bear an affirmative duty to verify XYZ Engineering's certificate of authority status before treating the matter a...
Conclusion_202
In response to Q102, Engineer A's status as a direct competitor of Engineer X - and specifically as the firm that previously served Client L - creates...
Conclusion_203
In response to Q103, the distinction between inadvertent and willful non-compliance by XYZ Engineering is ethically significant and should affect both...
Conclusion_204
In response to Q104, Engineer A's ethical obligations toward Client L are more constrained than they might initially appear. The NSPE Code's public we...
Conclusion_205
In response to Q201, the tension between the Collegial Pre-Reporting Engagement principle and the Mandatory Reporting Obligation principle is real and...
Conclusion_206
In response to Q301 and Q304 considered together from a deontological perspective, Engineer A does not have an unconditional duty to report immediatel...
Conclusion_207
In response to Q302, the collegial-first approach prescribed by the Board does reflect the disposition of a professionally virtuous engineer when appl...
Conclusion_208
In response to Q303, the Board's graduated reporting sequence - collegial contact first, formal report only if unsatisfied - produces better aggregate...
Conclusion_209
In response to Q401, if Engineer A had no prior business relationship with Client L and no competitive stake in XYZ Engineering's engagement, the Boar...
Conclusion_210
In response to Q402, if Engineer X, upon collegial contact by Engineer A, acknowledged the missing certificate of authority but continued providing en...
Conclusion_211
In response to Q404, if Engineer A had immediately reported XYZ Engineering to the State P licensure board without first contacting Engineer X, and it...
Conclusion_301
The central principle tension in this case - between Collegial Pre-Reporting Engagement and Mandatory Reporting Obligation - is resolved not by subord...
Conclusion_302
The most structurally complex principle tension in this case is the conflict between Competitive Motivation Scrutiny and the Epistemic Verification Ob...
Conclusion_303
The Engineering Business-Profession Duality principle - which acknowledges that Engineer A simultaneously holds legitimate competitive interests and p...
LLM classification
Phase 1 entities + 2C Q&C
Engineer A's obligations cycle conditionally between an epistemic verification role, a collegial-engagement role, and a formal-reporting role, while Engineer X's obligations shift between a passive subject of inquiry, an active respondent with a cure opportunity, and a potential regulatory violator — with the locus of active duty alternating between the two parties at each phase transition defined by the Board's graduated sequence.
Reasoning
The Board's graduated framework creates a recurring, conditional cycle of obligation between Engineer A and Engineer X rather than a clean one-time handoff or a permanent stalemate. Responsibility moves from Engineer A (verification duty) to Engineer X (explanation/remediation duty) and potentially back to Engineer A (formal reporting duty) depending on Engineer X's response, with the possibility of further regulatory cycling if the licensure board becomes involved. This back-and-forth pattern — triggered by phase conditions (collegial contact, Engineer X's response, satisfaction threshold) — matches the oscillation definition of stakeholders going 'to and fro between different sets of rules' as circumstances change.
LLM batched analysis
label-to-URI resolution
Phase 1 entities + 2C Q&C + 2A provisions
Causal-Normative Links (5)
CausalLink_Accept Engagement Without Cert
Engineer X's acceptance of an engagement in State P without obtaining a certificate of authority directly violates the jurisdictional pre-practice com...
CausalLink_Decide Response to Discovered
Engineer A's deliberation about how to respond to the discovered violation is the central ethical decision point, requiring simultaneous satisfaction ...
CausalLink_Contact Engineer X Directly
Directly contacting Engineer X fulfills the collegial pre-reporting engagement obligation by giving Engineer X the opportunity to remedy an apparently...
CausalLink_Report Violation to Authoritie
Reporting the violation to authorities ultimately fulfills the mandatory unlicensed practice reporting obligation and preserves licensure system integ...
CausalLink_Obtain Certificate of Authorit
Obtaining the certificate of authority is the remedial action that directly fulfills Engineer X's pre-practice compliance obligation under State P law...
Question Emergence (17)
QuestionEmergence_1
This foundational question emerged because the discovery of a competitor's regulatory non-compliance at the moment of a former-client relationship tra...
QuestionEmergence_2
This question emerged because the Toulmin warrant authorizing the move from 'Engineer A knows of a violation' to 'Engineer A must report' depends enti...
QuestionEmergence_3
This question emerged because the data - Engineer A discovering a competitor's violation immediately after losing a client to that competitor - create...
QuestionEmergence_4
This question emerged because the Toulmin warrant structure for Engineer A's reporting obligation contains an embedded intent-sensitivity: the same da...
QuestionEmergence_5
This question emerged because Client L occupies a dual role in the ethical structure - simultaneously a member of the public whom Engineer A has a gen...
QuestionEmergence_6
This question arose because the same data event - Engineer A discovering XYZ's non-compliance while holding a competitive stake in XYZ's market exit -...
QuestionEmergence_7
This question emerged because the data - Engineer A losing Client L to XYZ and then discovering XYZ's non-compliance - creates a structural conflict b...
QuestionEmergence_8
This question arose because the data - XYZ's ongoing unauthorized practice in State P - places Engineer A at the intersection of two warrants that pre...
QuestionEmergence_9
This question arose because the data - Engineer A discovering XYZ's non-compliance in the same market where XYZ displaced him - makes it structurally ...
QuestionEmergence_10
This question arose because the deontological framing of the reporting obligation - which strips motivation from the duty calculus - collides with the...
QuestionEmergence_11
This question arose because the Board's prescribed sequence - collegial contact before formal report - is structurally indistinguishable in outward be...
QuestionEmergence_12
This question arose because the Board's graduated sequence embeds a consequentialist assumption - that collegial correction produces better outcomes t...
QuestionEmergence_13
This question arose because the Board's requirement that Engineer A confirm non-compliance before reporting introduces a verification threshold that i...
QuestionEmergence_14
This question arose because the Board's analysis acknowledges Engineer A's competitive stake but does not resolve whether that stake modifies the stru...
QuestionEmergence_15
This question arose because the Board's graduated sequence is calibrated to inadvertent violations, but the scenario describes a post-notification sta...
QuestionEmergence_16
This question emerged because BER 96-8 established the foundational warrant hierarchy that the Board analogically transferred to Engineer A's certific...
QuestionEmergence_17
This question emerged because the ethical framework governing Engineer A's reporting decision contains an internal tension between the duty to report ...
Resolution Patterns (21)
ResolutionPattern_1
The Board concluded that the graduated reporting sequence remains sound even when Engineer A is a competitor, but that its application requires Engine...
ResolutionPattern_2
The Board concluded that the word 'may' in Conclusion_2 reflects the contingency of the factual predicate (i.e., whether Engineer X's explanation reso...
ResolutionPattern_3
The Board concluded that Engineer A's first obligation is to communicate directly with Engineer X to obtain clarification, reflecting the profession's...
ResolutionPattern_4
The Board concluded that if Engineer A is not sufficiently satisfied with Engineer X's explanation, Engineer A may be required to report the matter to...
ResolutionPattern_5
The Board concluded that Engineer A bears an affirmative epistemic duty to independently verify XYZ Engineering's certificate of authority status thro...
ResolutionPattern_6
The Board - through the conclusion's own analysis filling the Board's silence - determined that while Engineer A has a conceptual duty under I.4 and t...
ResolutionPattern_7
The Board resolved the tension between collegial engagement and mandatory reporting by distinguishing the present case from BER 96-8 on the ground tha...
ResolutionPattern_8
The Board concluded that Engineer A bears an affirmative verification duty calibrated to reasonable professional confidence rather than absolute certa...
ResolutionPattern_9
The Board concluded that Engineer A's competitive stake does not eliminate the reporting obligation but does impose a heightened duty of self-scrutiny...
ResolutionPattern_10
The Board concluded that the ethical framework is not static across all non-compliance scenarios: where non-compliance appears inadvertent, the colleg...
ResolutionPattern_11
The board concluded that Engineer A has no affirmative obligation to directly contact Client L because the former-client relationship does not sustain...
ResolutionPattern_12
The board concluded that the Collegial Pre-Reporting Engagement principle and the Mandatory Reporting Obligation principle are not irreconcilable, but...
ResolutionPattern_13
The board concluded that from a deontological perspective Engineer A does not have an unconditional duty to report immediately, but does have a catego...
ResolutionPattern_14
The board concluded that the collegial-first approach does reflect the disposition of a professionally virtuous engineer when applied in good faith, b...
ResolutionPattern_15
The board concluded that the graduated reporting sequence produces better consequentialist outcomes than immediate mandatory reporting because it filt...
ResolutionPattern_16
The board concluded that competitive motivation does not alter the reporting sequence but does introduce two additional obligations - motivational tra...
ResolutionPattern_17
The board concluded that Engineer A's obligation to report to the State P licensure board became substantially immediate upon Engineer X's acknowledgm...
ResolutionPattern_18
The board concluded that Engineer A would face significant ethical exposure under Code III.7 because the competitive context transforms the failure to...
ResolutionPattern_19
The board concluded that the apparent conflict between collegial engagement and mandatory reporting is resolved through structured sequencing rather t...
ResolutionPattern_20
The board concluded that Engineer A's competitive motivation and the epistemic verification obligation are not in conflict but are structurally aligne...
ResolutionPattern_21
The Board concluded that mixed-motive reporting is ethically permissible when the underlying duty is genuine, the procedural sequence (verification, c...
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
-
Obligation Coverage
-
E2
Action Mapping
-
Action Mapping
-
E3
Composition
-
Composition
-
Q&C
Alignment
-
Alignment
-
LLM
Refinement
-
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
-
Characters
-
4.2
Timeline
-
Timeline
-
4.3
Conflicts
-
Conflicts
-
4.4
Decisions
-
Decisions
-