Step 4: Case Synthesis

Build a coherent case model from extracted entities

Back to Case
Sustainable Development—Threatened Species
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
104 entities
Pass 1: Contextual Framework
  • 8 Roles
  • 22 States
  • 7 Resources
Pass 2: Normative Requirements
  • 14 Principles
  • 8 Obligations
  • 3 Constraints
  • 11 Capabilities
Pass 3: Temporal Dynamics
  • 31 Temporal Dynamics
Phase 2 Analytical Extraction
2A: Code Provisions 5
LLM detect algorithmic linking Case text + Phase 1 entities
I.3. Issue public statements only in an objective and truthful manner.
I.5. Avoid deceptive acts.
II.3.a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information...
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.4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or forme...
2B: Precedent Cases 3
LLM extraction Case text
BER Case No. 89-7 distinguishing
linked
Engineers act as agents or trustees for clients and are expected to maintain confidentiality of client information, especially where the client has confided information and the engineer lacks specific technical expertise in the relevant discipline.
BER Case No. 97-13 distinguishing
linked
An engineer who lacks expertise in the relevant technical area and whose conclusions are based on mere surmise or speculation should act cautiously, verbally report concerns to the client, and refrain from including unverified information in a final report, but should follow up to ensure corrective action is taken.
BER Case No. 04-8 distinguishing
linked
An engineer who discovers a client's violation of environmental laws/regulations has an obligation to inform the client of the violation and necessary remedial steps, and to report the matter to appropriate authorities if the client fails to take corrective action.
2C: Questions & Conclusions 16 16
Board text parsed LLM analytical Q&C LLM Q-C linking Case text + 2A provisions
Questions (16)
Question_1 Was it ethical for Engineer A not to include the information about the threat to the bird species in a written report that will be submitted to a publ...
Question_101 Does verbally informing the developer client about the threatened species risk, without including it in the written report, satisfy Engineer A's profe...
Question_102 Should the firm biologist's professional opinion on species risk have been independently verified or elevated to a formal finding requiring mandatory ...
Question_103 Does the fact that the bird species is 'threatened' rather than 'endangered' create a lower threshold of disclosure obligation, and if so, is that dis...
Question_104 What is Engineer A's obligation if the developer client, after being verbally informed, instructs Engineer A to omit the species risk from the written...
Question_201 How should Engineer A balance the duty of Confidentiality of Client Information against the duty of Objectivity in Written Report when a public author...
Question_202 Does Loyalty to Developer Client conflict with Public Welfare in Wetlands Case when the developer's commercial interest in project approval is undermi...
Question_203 How should Complete Reporting in Written Report be balanced against Transparency in Client Disclosure when the engineer chooses to satisfy the latter ...
Question_204 Is there an inherent tension between Environmental Stewardship in Wetlands Analysis and Loyalty to Developer Client that the NSPE Code's sustainable d...
Question_301 From a deontological perspective, did Engineer A fulfill the professional duty of objective and truthful reporting under Section II.3.a by omitting th...
Question_302 From a consequentialist perspective, did the potential benefit to the developer client of omitting the threatened species information from the public ...
Question_303 Did Engineer A act with professional integrity, as a virtue-ethics analysis would require, by disclosing the threatened species concern verbally to th...
Question_401 If the bird species had been classified as federally 'endangered' rather than merely 'threatened,' would the Board still have reached the same conclus...
Question_402 If Engineer A had not even verbally disclosed the biologist's concern to the developer client, would the Board's finding of an ethics violation regard...
Question_403 If the firm's biologist had not identified any threat to the bird species during the analysis, would the Board still have found any duty on Engineer A...
Question_404 If the written report had been intended solely for the developer client's internal use and not for submission to a public authority considering the pr...
Conclusions (16)
Conclusion_1 It was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a pu...
Conclusion_101 The Board's conclusion implies that verbal disclosure to the developer client, while satisfying an internal advisement duty, does not discharge Engine...
Conclusion_102 The Board's reasoning does not hinge on the bird species being classified as 'threatened' rather than 'endangered,' and this suggests the regulatory l...
Conclusion_103 The case reveals an unresolved tension the Board's conclusion only implicitly settles: when a client's commercial interest in project approval conflic...
Conclusion_201 Verbal disclosure to the developer client (Q101) does not discharge Engineer A's ethical obligation because the public authority, not the client, is t...
Conclusion_202 The classification of the species as 'threatened' rather than 'endangered' (Q103) does not lower Engineer A's disclosure obligation. The Board's reaso...
Conclusion_203 If the developer client had instructed Engineer A to omit the species risk after verbal disclosure (Q104), compliance would cross an ethical boundary ...
Conclusion_204 From a deontological standpoint (Q301), Engineer A failed to fulfill the duty of objective and truthful reporting under Section II.3.a. The duty is no...
Conclusion_205 A consequentialist analysis (Q302) supports the Board's conclusion: the localized commercial benefit to the developer from omitting the finding is out...
Conclusion_206 Under a virtue-ethics lens (Q303), Engineer A's conduct reflects a divided professional character: candor toward the client but concealment toward the...
Conclusion_207 Had the species been federally 'endangered' rather than 'threatened' (Q401), the Board's conclusion would likely have been even more unambiguous, as e...
Conclusion_208 If Engineer A had failed to disclose the concern even verbally to the developer client (Q402), the ethics violation would extend beyond the reporting ...
Conclusion_209 If the written report had been intended solely for the developer's internal use rather than submission to a public authority (Q404), the ethical calcu...
Conclusion_301 The case resolves the apparent tension between Confidentiality of Client Information and Objectivity in Written Report by treating them as operating o...
Conclusion_302 Verbal disclosure to the developer client (Transparency in Client Disclosure) and complete written disclosure to the public authority (Complete Report...
Conclusion_303 Rather than existing in true conflict, Environmental Stewardship in Wetlands Analysis and the engineer's objectivity/reporting duties are mutually rei...
2D: Transformation Classification
transfer 60%
LLM classification Phase 1 entities + 2C Q&C

Engineer A attempted a one-way shift of the disclosure obligation from the public-facing written-report channel to the private client-facing verbal channel, treating client notification as functionally equivalent to regulatory disclosure. The Board blocked this shift, ruling the two obligations are non-interchangeable and that the non-delegable duty to the public authority remains fixed on Engineer A until fulfilled through the written report itself—an invalid or 'failed' transfer rather than a completed one.

Reasoning

The core dynamic in this case is an attempted—but rejected—transfer of obligation: Engineer A tried to discharge his duty to the public authority by shifting it into a private verbal disclosure to the developer client, effectively attempting to move the obligation from the 'public reporting' scenario set to the 'client relationship' scenario set. The Board explicitly refused to recognize this as a valid transfer, holding in C2 and C5 that 'verbal disclosure to the developer client... does not discharge Engineer A's separate and independent obligation to the public authority,' meaning the duty never actually left Engineer A's shoulders with respect to the written report.

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_Environmental Analysis Undertaking Because Engineer A undertook the environmental analysis out of faithfulness to the client, this action set in motion the causal chain that surfaced th...
CausalLink_Verbal Concern Disclosure The verbal disclosure, guided jointly by faithfulness to client and sustainable development, partially discharged Engineer A's duty to communicate the...
CausalLink_Written Report Omission The written report omission violates the duty to include all pertinent information and to protect the environment precisely because it suppressed the ...
CausalLink_Code Section Addition Adding a new code section in the name of sustainable development created the normative material that would later be modified and applied, showing that...
CausalLink_Code Language Modification Modifying the code language, still guided by sustainable development, refined the environmental obligations that the Board of Ethical Review ultimatel...
CausalLink_Board Ethical Determination A1, the Board's determination on Engineer A's written report omission, is guided by Sustainable Development, Objectivity and Truthfulness in Reports, ...
CausalLink_Species Threat Reporting A2, the Species Threat Reporting, is guided by Sustainable Development since it represents the point at which the firm's biologist translated the iden...
Question Emergence (16)
QuestionEmergence_1 The question arises because Engineer A's technical competence allowed identification of a threatened species risk that is directly relevant to a publi...
QuestionEmergence_2 The question arises because Engineer A's action split the disclosure between an informal verbal channel to the client and a formal written channel to ...
QuestionEmergence_3 The question emerges because the biologist's assessment of threatened species risk was never elevated beyond an internal, informal exchange despite it...
QuestionEmergence_4 The question arises because the case data conflates a legal classification distinction with an ethical obligation question, exposing uncertainty about...
QuestionEmergence_5 The question arises because verbal disclosure to the client does not resolve whether the engineer's written report, submitted to a public authority, c...
QuestionEmergence_6 The question arises because Engineer A's report was submitted for use in a public regulatory proceeding while containing information the client would ...
QuestionEmergence_7 The question arises because Engineer A's written report omitted the biologist's species concern while mentioning it only verbally to the client, creat...
QuestionEmergence_8 The question emerges because Engineer A's choice to split disclosure across two channels, verbal to the client and silent in the report, exposes a gap...
QuestionEmergence_9 The question arose because Engineer A's written report omitted the biologist's species concern while only verbally raising it with the client, creatin...
QuestionEmergence_10 The question arises because Engineer A's written report omitted information that a strict reading of Section II.3.a treats as pertinent, while the eng...
QuestionEmergence_11 The question arises because Engineer A's written omission of a known species risk, despite verbally mentioning it to the client, creates an unresolved...
QuestionEmergence_12 The question arises because Engineer A's split disclosure, verbal to the client but absent from the formal report, exposes an unresolved conflict betw...
QuestionEmergence_13 This question emerged because the Board's decision rested on a specific regulatory status (threatened) that sits on a spectrum of protection levels, p...
QuestionEmergence_14 The question emerges because removing the verbal disclosure act would test whether the written omission was judged in isolation or was implicitly cons...
QuestionEmergence_15 This question arises because the case facts intertwine the duty to report with the fact of actual risk discovery, and removing that fact forces clarif...
QuestionEmergence_16 The question arises because the Board's original conclusion relied on the report's function as an input to a public regulatory decision, so changing t...
Resolution Patterns (16)
ResolutionPattern_1 Given that the biologist had reached a clear conclusion about threat to the species and the report was headed to a public authority deciding on the pr...
ResolutionPattern_2 Because the developer client and the public authority occupy distinct roles with distinct information needs, the board reasoned that Engineer A's priv...
ResolutionPattern_3 Since the board did not premise its determination on the species being endangered rather than threatened, it treated the biologist's unambiguous, mate...
ResolutionPattern_4 Even if the developer client had directly instructed omission, the board's reasoning treats the objectivity requirement as a public-protection duty th...
ResolutionPattern_5 Because the public authority makes its regulatory decision based on the written report alone, the board concluded that verbal disclosure to the client...
ResolutionPattern_6 Given that the biologist's finding constituted a real risk to protected habitat, the Board concluded that the 'threatened' versus 'endangered' distinc...
ResolutionPattern_7 Because the written report was destined for a public authority's regulatory reliance, the Board reasoned that even an explicit client instruction to o...
ResolutionPattern_8 Since Engineer A knowingly omitted the biologist's finding from a report meant for public authority review, the Board concluded under a deontological ...
ResolutionPattern_9 Weighing the asymmetry between the developer's narrow commercial gain and the broader, dispersed harms to habitat and public decisionmaking, the Board...
ResolutionPattern_10 Because Engineer A was forthright with the client yet silent toward the public authority on the same material finding, the Board concluded that this d...
ResolutionPattern_11 Given that the actual case involved a 'threatened' species and the board still found nondisclosure unethical, the board reasons that had the species b...
ResolutionPattern_12 Because Engineer A did verbally inform the developer client in the actual case, the board's finding centers only on the written report omission, but h...
ResolutionPattern_13 Since in the actual case the report was submitted to a public authority making a regulatory decision, the board grounds its unethical-omission finding...
ResolutionPattern_14 Because the species-threat finding concerned environmental welfare rather than the developer's private business affairs, and because the report was de...
ResolutionPattern_15 Given that Engineer A verbally informed the client but omitted the same information from the report submitted to the public authority, the board concl...
ResolutionPattern_16 Given that the firm's own biologist produced an unambiguous finding of threat to the species and the written report was destined for a public authorit...
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