Step 4: Case Synthesis

Build a coherent case model from extracted entities

Back to Case
Confidentiality of Competitor Information Submitted to Government 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
72 entities
Pass 1: Contextual Framework
  • 10 Roles
  • 12 States
  • 7 Resources
Pass 2: Normative Requirements
  • 9 Principles
  • 6 Obligations
  • 2 Constraints
  • 6 Capabilities
Pass 3: Temporal Dynamics
  • 20 Temporal Dynamics
Phase 2 Analytical Extraction
2A: Code Provisions 4
LLM detect algorithmic linking Case text + Phase 1 entities
II.4. Engineers shall act for each employer or client as faithful agents or trustees.
II.4.a. Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of the...
III.4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or forme...
III.4.a. Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific pr...
2B: Precedent Cases 3
LLM extraction Case text
linked
A part-time consultant arrangement to municipalities by engineers in private practice does not preclude providing normal engineering services to the same municipalities when loyalties are not divided.
linked
An engineer retained by one party (e.g., the government) cannot ethically be retained by an opposing party (e.g., a contractor with a claim against that government) without the former client's consent, per Code Section III.4.b.
linked
An engineer retains an ethical obligation to protect confidential information and maintain a duty of trust and loyalty to a former client even after the professional relationship has ended, and cannot simply claim to provide a 'separate and independent' analysis for an opposing party.
2C: Questions & Conclusions 15 17
Board text parsed LLM analytical Q&C LLM Q-C linking Case text + 2A provisions
Questions (15)
Question_1 What are Engineer A’s ethical obligations under these circumstances?
Question_101 How long does Engineer A's duty of confidentiality regarding Company X's design information persist after leaving the government agency—does it expire...
Question_102 What practical safeguards or information barriers should Company Y implement to ensure Engineer A does not inadvertently apply or disclose Company X's...
Question_103 Did Engineer A have any obligation to notify the government agency or Company X about her move to a competitor, given her prior access to their confid...
Question_104 Should Engineer A recuse herself from specific projects at Company Y that directly involve or compete against designs she reviewed as a government emp...
Question_201 How should Engineer A's right to Employment Mobility be balanced against her ongoing duty of Loyalty to Former Employer and Clients, particularly rega...
Question_202 Does Conflict of Interest Avoidance by Engineer A conflict with her Employment Mobility, given that any position at a direct competitor like Company Y...
Question_203 How can Engineer A reconcile her Faithful Agent Duty to Company Y with the Confidentiality of Company X Design Information, if fully serving Company Y...
Question_204 Is there an inherent tension between Confidentiality of Company X Information and Engineer A's new Loyalty Duty to Company Y, since full loyalty to a ...
Question_301 From a deontological perspective, did Engineer A fulfill her duty of confidentiality to Company X despite no longer being employed by the Government A...
Question_302 Would the outcome of Engineer A accepting employment with Company Y still be justified from a consequentialist standpoint if Company X's competitive p...
Question_303 Did Engineer A act with professional integrity by proactively informing Company Y of her confidentiality obligations before accepting employment, even...
Question_401 If Company X had consented to Engineer A's disclosure of its confidential design information to Company Y, would the Board's conclusion restricting En...
Question_402 If Engineer A had moved to a non-competing firm rather than Company Y, a direct competitor of Company X, would the Board still have imposed the same c...
Question_403 If Engineer A had never had actual access to Company X's confidential design submissions during her government tenure, would the Board's conditional a...
Conclusions (17)
Conclusion_1 Engineer A is free to pursue employment with Company Y provided Engineer A does not disclose any confidential and proprietary design information Engin...
Conclusion_101 The Board's conditional approval implies that Engineer A's confidentiality obligation to Company X survives indefinitely and is not tied to her employ...
Conclusion_102 The Board's conclusion, while framed around disclosure, leaves unaddressed the more subtle risk of inadvertent or unconscious application of Company X...
Conclusion_103 The Board's conditional permission reveals an inherent structural tension in Engineer A's new role: her duty as a faithful agent to Company Y (to appl...
Conclusion_201 Regarding Q101, Engineer A's duty of confidentiality toward Company X's design information is best understood as indefinite rather than time-limited. ...
Conclusion_202 In response to Q102, practical safeguards Company Y should consider include establishing an information barrier (ethical wall) that excludes Engineer ...
Conclusion_203 On Q103, the Board's conclusion does not indicate any obligation for Engineer A to notify the government agency or Company X of her move to a competit...
Conclusion_204 Regarding Q104, while the Board did not explicitly require recusal, a reasonable extension of its reasoning suggests that Engineer A should voluntaril...
Conclusion_205 From a deontological perspective (Q301), Engineer A fulfills her duty of confidentiality not because of any ongoing contractual relationship with the ...
Conclusion_206 On Q302, a consequentialist evaluation of the Board's conditional approval would depend on downstream outcomes rather than intent. If Engineer A's pre...
Conclusion_207 Regarding Q303, Engineer A's proactive disclosure to Company Y before accepting employment reflects a virtue-based conception of professional integrit...
Conclusion_208 In response to Q401, if Company X had explicitly consented to disclosure of its confidential design information to Company Y, the ethical constraint u...
Conclusion_209 On Q402, had Engineer A moved to a non-competing firm, the practical risk of harm from disclosure would be substantially reduced, but the underlying c...
Conclusion_210 Regarding Q403, if Engineer A had never actually accessed Company X's confidential submissions during her government tenure, there would be no confide...
Conclusion_301 The Board resolves the apparent conflict between Employment Mobility and Loyalty to Former Employer and Clients not by subordinating one to the other,...
Conclusion_302 Conflict of Interest Avoidance is not treated as an absolute bar to working for a direct competitor; rather, the Board implicitly prioritizes behavior...
Conclusion_303 The Faithful Agent Duty owed to Company Y and the Confidentiality obligation owed to Company X are reconciled by scoping the faithful agent duty: Engi...
2D: Transformation Classification
stalemate 72%
LLM classification Phase 1 entities + 2C Q&C

Engineer A is permanently embedded in a dual-obligation structure: confidentiality to Company X (indefinite, per C2/C5) and faithful agency to Company Y (C4/C17), with neither duty superseding or dissolving the other. Rather than a clean handoff or cyclical alternation, the Board's resolution locks Engineer A into simultaneous, ongoing compliance with both obligations, scoping rather than resolving the underlying tension (C4: 'not a tension the Board resolves through elimination but through prioritization').

Reasoning

Engineer A remains permanently bound by an indefinite confidentiality duty to Company X while simultaneously owing a faithful agent/loyalty duty to Company Y, and the Board does not eliminate either obligation but requires both to coexist indefinitely. This matches the framework's stalemate pattern where stakeholders 'cannot quit the scenario, as they seem to be trapped in the set of rules,' since Engineer A cannot fully discharge either duty without the other constraining it for the remainder of her career.

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_Government Employment Acceptance Engineer A's acceptance of government employment set up the causal chain leading to access of confidential information, meaning this initial action ca...
CausalLink_Confidential Information Submission Company X's submission of confidential information to the government office directly caused the confidential information access that later became ethi...
CausalLink_Employment Termination The termination of Engineer A's government employment causally enabled the acceptance of the competitor position, which later fed into the compromised...
CausalLink_Competitor Position Acceptance Accepting the competitor position was guided by the duty to be a faithful agent and trustee and to avoid the appearance of influenced judgment, which ...
CausalLink_Board Adjudication Decision The board adjudication decision fulfilled the duty of nondisclosure of former employer confidential information and was guided by faithful agency and ...
Question Emergence (15)
QuestionEmergence_1 The question emerged because Engineer A's career move from a regulatory position with access to a competitor's confidential data into employment with ...
QuestionEmergence_2 The question arises because the NSPE Code and BER precedents establish that confidentiality duties survive employment changes, but they do not specify...
QuestionEmergence_3 The question emerges because the transition of an engineer holding confidential information into a competitor's employ creates a practical gap between...
QuestionEmergence_4 The question arose because Engineer A's dual role history, first as a government engineer with access to Company X's confidential data, then as an emp...
QuestionEmergence_5 The question arises because Engineer A's career transition creates a structural conflict of interest that the NSPE Code and prior BER precedents addre...
QuestionEmergence_6 The question arises because a single career transition creates two legitimate but conflicting obligations, personal employment freedom versus continui...
QuestionEmergence_7 The question arises because the facts of her employment transition satisfy the conditions for two competing obligations, loyalty and confidentiality o...
QuestionEmergence_8 The question arises because Engineer A's transition between employers created a situation where two legitimate obligations, loyalty to a current emplo...
QuestionEmergence_9 The question emerged because Engineer A's employment transition placed her under two simultaneous obligations whose demands could conflict, prompting ...
QuestionEmergence_10 The question arises because Engineer A's transition from a regulatory role with access to Company X's confidential submissions to a competitor positio...
QuestionEmergence_11 The question arose because the ethical judgment about Engineer A's job acceptance was originally framed around foreseeable consequences, but the possi...
QuestionEmergence_12 The question emerged because Engineer A's transition between employers with overlapping business interests placed her confidentiality obligations and ...
QuestionEmergence_13 The question emerges because the Board's original ruling assumed lack of consent as a factual predicate for finding Engineer A's conduct improper, and...
QuestionEmergence_14 The question arises because the Board's imposition of confidentiality conditions could be justified either by the general duty to protect former emplo...
QuestionEmergence_15 The question arises because the Board's conditional approval rests ambiguously on either the fact of confidential access (a data-dependent warrant) or...
Resolution Patterns (17)
ResolutionPattern_1 Given that Engineer A possessed confidential Company X information from her government role and sought employment at a competitor, the Board concluded...
ResolutionPattern_2 Because the duty under III.4 is grounded in the nature of the information rather than the employment status that produced it, the Board concluded that...
ResolutionPattern_3 Given that expertise can be applied unconsciously and that Engineer A may be placed on competing projects, the Board's silence on this risk implies th...
ResolutionPattern_4 Because Engineer A's confidentiality duty to Company X predates and outweighs her new duty to Company Y, and because Company Y accepted her employment...
ResolutionPattern_5 Given that the duty under III.4 attaches to the information itself and that no public disclosure or consent occurred, the Board concluded that Enginee...
ResolutionPattern_6 Given that Engineer A moved to a direct competitor while holding confidential knowledge from her government role, the board concluded that practical b...
ResolutionPattern_7 Because BER 85-4 anchors the obligation in nondisclosure rather than notification, the board concluded that Engineer A had no duty to alert the agency...
ResolutionPattern_8 Since certain Company Y projects directly paralleled designs Engineer A had reviewed as a government employee, the board reasoned that voluntary recus...
ResolutionPattern_9 Given that Engineer A's government employment had ended but the confidentiality obligation was treated as role-based rather than contractual, the boar...
ResolutionPattern_10 Because the board's approval was conditional and based only on information available at the time of hiring, a consequentialist evaluation would judge ...
ResolutionPattern_11 Given that Engineer A disclosed her prior access to Company X's information before accepting Company Y's offer, and given that the Code's II.4.a. only...
ResolutionPattern_12 Because III.4. textually conditions the nondisclosure duty on the absence of consent, the board reasoned that explicit consent from Company X would re...
ResolutionPattern_13 Given that Company Y is a direct competitor in the actual facts, and given that the board reasoned confidentiality duties attach to information sensit...
ResolutionPattern_14 Because the board's conditional approval rested on Engineer A having actually reviewed Company X's confidential submissions, it reasoned that in the a...
ResolutionPattern_15 Given that Engineer A's duty of confidentiality persists beyond her government tenure, and given that she disclosed this obligation to Company Y befor...
ResolutionPattern_16 Given that Engineer A had not disclosed any confidential information and her move to a competitor created only an appearance of conflict rather than a...
ResolutionPattern_17 Because Engineer A's knowledge base separates into general engineering competence and Company X specific confidential details, the Board concluded she...
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