Step 4: Review

Review extracted entities and commit to OntServe

Confidentiality of Competitor Information Submitted to Government Agency
Step 4 of 5
Commit to OntServe
Login to commit entities to OntServe. (280 entities already committed)
Phase 2A: Code Provisions
4 4 committed
code provision reference 4
II.4. individual committed

Engineers shall act for each employer or client as faithful agents or trustees.

codeProvision II.4.
provisionText Engineers shall act for each employer or client as faithful agents or trustees.
appliesTo 34 items
II.4.a. individual committed

Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.

codeProvision II.4.a.
provisionText Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.
appliesTo 38 items
III.4. individual committed

Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.

codeProvision III.4.
provisionText Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they...
appliesTo 57 items
III.4.a. individual committed

Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular and specialized knowledge.

codeProvision III.4.a.
provisionText Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular...
appliesTo 40 items
Phase 2B: Precedent Cases
3 3 committed
precedent case reference 3
BER Case No. 74-2 individual committed

The Board cited this case to illustrate a situation where a part-time consultant arrangement did not create divided loyalties, contrasting with situations where confidentiality obligations may conflict.

caseCitation BER Case No. 74-2
caseNumber 74-2
citationContext The Board cited this case to illustrate a situation where a part-time consultant arrangement did not create divided loyalties, contrasting with situations where confidentiality obligations may conflic...
citationType analogizing
principleEstablished A part-time consultant arrangement to municipalities by engineers in private practice did not preclude those same engineers from providing normal engineering services to the same municipalities, where...
relevantExcerpts 1 items
internalCaseId 104
resolved True
BER Case No. 82-6 individual committed

The Board cited this case to establish that an engineer retained by one client cannot ethically agree to represent an adverse party without the former client's consent, illustrating the duty of loyalty and confidentiality to former clients.

caseCitation BER Case No. 82-6
caseNumber 82-6
citationContext The Board cited this case to establish that an engineer retained by one client cannot ethically agree to represent an adverse party without the former client's consent, illustrating the duty of loyalt...
citationType supporting
principleEstablished It is not ethical for an engineer retained by the US government to subsequently be retained by a contractor filing a claim against that same government without the former client's consent, per NSPE Co...
relevantExcerpts 1 items
internalCaseId 170
resolved True
BER Case No. 85-4 individual committed

The Board cited this case extensively to establish that an engineer who gains access to confidential information from one party cannot subsequently work for an adverse party, even after the original relationship is terminated, because the duty of confidentiality and loyalty persists.

caseCitation BER Case No. 85-4
caseNumber 85-4
citationContext The Board cited this case extensively to establish that an engineer who gains access to confidential information from one party cannot subsequently work for an adverse party, even after the original r...
citationType supporting
principleEstablished An engineer who gains access to confidential information while working for one party retains an ethical obligation to protect that information even after the professional relationship ends, and cannot...
relevantExcerpts 3 items
internalCaseId 172
resolved True
Phase 2C: Questions & Conclusions
42 42 committed
ethical conclusion 25
Conclusion_1 individual committed

Engineer A is free to pursue employment with Company Y provided Engineer A does not disclose any confidential and proprietary design information Engineer A learned about Company X during Engineer A's employment with the government agency and makes this obligation clear to Company Y before accepting employment.

conclusionNumber 1
conclusionText Engineer A is free to pursue employment with Company Y provided Engineer A does not disclose any confidential and proprietary design information Engineer A learned about Company X during Engineer A's ...
conclusionType board_explicit
mentionedEntities {"actions": ["Accept Position at Competitor", "Withhold Company X Confidential Information"], "capabilities": ["Engineer A Prior Government Access Disclosure to Company Y", "Engineer A...
citedProvisions 4 items
answersQuestions 1 items
extractionReasoning The Board concluded that Engineer A's transition to Company Y is ethically permissible (compliance, not a violation) subject to two explicit conditions: (1) Engineer A must not disclose confidential a...
Conclusion_101 individual committed

Beyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion is structurally incomplete because it addresses only the threshold moment of employment acceptance and not the ongoing conduct obligations that persist throughout Engineer A's tenure at Company Y. Engineer A's ethical duties do not terminate once she discloses the conflict and accepts the position; rather, they generate a continuing affirmative obligation to recuse herself from any project, assignment, or internal deliberation at Company Y that directly involves Company X's facility designs, regulatory submissions, or competitive positioning in domains where her government access gave her privileged structural knowledge. This recusal obligation should be documented formally - through written notice to Company Y's management and project assignment records - so that the boundary between permissible general expertise and impermissible use of confidential regulatory knowledge is institutionally traceable and not left to Engineer A's individual judgment alone. The absence of such a documented recusal mechanism creates a structural gap in the Board's otherwise sound conditional permission, because the risk of inadvertent or subconscious use of confidential knowledge is highest precisely in the ongoing work environment where competitive pressures are constant and the line between general expertise and privileged knowledge is difficult to police without formal procedures.

conclusionNumber 101
conclusionText Beyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion...
conclusionType analytical_extension
mentionedEntities {"capabilities": ["Engineer A Adversarial Non-Participation Scope Determination at Company Y", "Engineer A Confidential Information Mental Segregation Impossibility Recognition"], "constraints":...
citedProvisions 3 items
answersQuestions 3 items
Conclusion_102 individual committed

The Board's conclusion requires Engineer A to disclose her prior government access to Company Y before accepting employment, but it does not address whether Company X - the party whose proprietary information is most directly at risk - bears any right to notification or whether Engineer A or Company Y bears any corresponding duty to provide it. This omission is ethically significant. Under the faithful agent and trustee standard, Engineer A's confidentiality obligation runs not merely as a prohibition on disclosure but as an affirmative duty of trust toward the interests of those whose information she holds. Company X submitted its confidential design information to the government agency with a reasonable expectation that the regulatory process would protect it from competitive exploitation. That expectation is materially threatened when an engineer with direct access to those submissions transitions to a direct competitor. While the NSPE Code does not explicitly require notification to Company X, the principle that engineers shall not promote or arrange for new employment to the detriment of a client or employer - read in conjunction with the faithful agent standard - supports the conclusion that Engineer A should at minimum consider whether Company X's interests require some form of protective notice, particularly if Engineer A is assigned to work that directly competes with Company X's approved or pending facility designs. The Board's silence on this point leaves Company X without any procedural protection beyond Engineer A's individual conscience, which is an insufficient safeguard given the structural competitive asymmetry created by the employment transition.

conclusionNumber 102
conclusionText The Board's conclusion requires Engineer A to disclose her prior government access to Company Y before accepting employment, but it does not address whether Company X — the party whose proprietary inf...
conclusionType analytical_extension
mentionedEntities {"constraints": ["Engineer A Post-Public-Employment Confidential Information Non-Use \u2014 Company X Design Information", "Engineer A Regulatory Submission Confidentiality Protection \u2014...
citedProvisions 3 items
answersQuestions 2 items
Conclusion_103 individual committed

The Board acknowledges that the duration of Engineer A's confidentiality obligation is indeterminate but declines to establish any standard or mechanism for when, if ever, that obligation expires. This indeterminacy, left unresolved, creates a practical problem that undermines the workability of the Board's conditional permission over time. From a deontological perspective, the duty of trust that grounds Engineer A's confidentiality obligation does not automatically dissolve with the passage of time, because the obligation derives from the nature of the relationship and the act of entrusting - not from the continued commercial sensitivity of the information. However, from a consequentialist perspective, a perpetual and absolute confidentiality obligation that never accounts for changed circumstances - such as the public disclosure of Company X's facility design through regulatory approval, the obsolescence of the underlying technology, or Company X's own abandonment of the design - would impose career restrictions on Engineer A that are disproportionate to any remaining protective interest. A more analytically complete conclusion would hold that Engineer A's obligation persists as long as the information retains competitive or regulatory sensitivity that was not publicly disclosed through the approval process itself, and that the burden of demonstrating that sensitivity has lapsed falls on Engineer A before she may treat the information as freely usable. This standard preserves the protective purpose of the confidentiality obligation while providing Engineer A with a principled mechanism for assessing when her constraint has been lifted by changed circumstances rather than by the mere passage of time or her own convenience.

conclusionNumber 103
conclusionText The Board acknowledges that the duration of Engineer A's confidentiality obligation is indeterminate but declines to establish any standard or mechanism for when, if ever, that obligation expires. Thi...
conclusionType analytical_extension
mentionedEntities {"constraints": ["Engineer A Post-Employment Duty of Trust Duration \u2014 BER Case 85-4", "Engineer A Post-Employment Confidential Information Retention \u2014 Company X Design Data"],...
citedProvisions 2 items
answersQuestions 2 items
Conclusion_104 individual committed

The Board's analysis does not address the systemic dimension of the revolving-door problem it implicitly resolves at the individual level. By permitting Engineer A's transition to Company Y subject only to individual confidentiality maintenance and pre-employment disclosure, the Board's conclusion, if generalized across the engineering profession, creates a structural incentive problem: government agencies that rely on confidential regulatory submissions from private companies will find that the value of those submissions as competitive intelligence makes their reviewing engineers attractive targets for competitor recruitment, and the individual confidentiality obligation - enforced only through professional ethics rather than institutional policy - is a weak safeguard against systematic erosion of regulatory integrity. The government agency itself bears an institutional responsibility, which the Board does not acknowledge, to establish formal revolving-door policies that restrict post-employment transitions to direct competitors of companies whose confidential submissions an engineer reviewed, at least for a defined cooling-off period. The absence of such a policy does not diminish Engineer A's individual ethical obligations, but it does mean that the ethical burden of protecting regulatory integrity is being borne entirely by individual engineers rather than by the institutional structures best positioned to enforce it. A complete ethical analysis would note that Engineer A's compliance with her individual obligations is necessary but not sufficient to protect the systemic integrity of the regulatory process, and that the Board's silence on institutional responsibility leaves a significant gap in the overall ethical framework governing government-to-private-sector transitions.

conclusionNumber 104
conclusionText The Board's analysis does not address the systemic dimension of the revolving-door problem it implicitly resolves at the individual level. By permitting Engineer A's transition to Company Y subject on...
conclusionType analytical_extension
mentionedEntities {"constraints": ["Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment Contract", "Engineer A Revolving Door Government-to-Competitor Employment Conflict \u2014...
citedProvisions 3 items
answersQuestions 2 items
Conclusion_105 individual committed

The Board's conditional permission for Engineer A to join Company Y does not adequately address the scenario - raised by analogy to BER Case 85-4 - in which Company Y later becomes involved in an adversarial regulatory or legal proceeding against Company X and Engineer A is asked to contribute technical analysis drawing on her domain expertise. In BER Case 85-4, the Board held that an engineer who had provided confidential information to one party in a proceeding could not ethically accept retention by the opposing party, and that claimed naivety about the conflict did not serve as mitigation. Applied to the current case, this precedent implies that if Company X and Company Y become adversaries in any regulatory, contractual, or legal proceeding involving the facility design domain in which Engineer A holds Company X's confidential information, Engineer A would be categorically barred from contributing to Company Y's position in that proceeding - regardless of whether she explicitly references Company X's confidential submissions or claims to rely only on general expertise. The structural knowledge she accumulated through regulatory access creates a conflict that cannot be neutralized by mental segregation alone. The Board's conclusion should have explicitly flagged this downstream adversarial participation risk as a constraint on Engineer A's permissible scope of work at Company Y, rather than leaving it to be inferred from prior BER precedent. Company Y should also be made aware of this constraint at the time of Engineer A's pre-employment disclosure, because it materially affects the range of assignments Engineer A can ethically accept.

conclusionNumber 105
conclusionText The Board's conditional permission for Engineer A to join Company Y does not adequately address the scenario — raised by analogy to BER Case 85-4 — in which Company Y later becomes involved in an adve...
conclusionType analytical_extension
mentionedEntities {"capabilities": ["Engineer A Forensic Expert Side-Switching Conflict Assessment", "Engineer A Confidential Information Mental Segregation Impossibility Recognition"], "constraints": ["Engineer A...
citedProvisions 3 items
answersQuestions 2 items
Conclusion_106 individual committed

The Board's conclusion implicitly assumes that the competitive intelligence value of Engineer A's government access is incidental to Company Y's hiring decision, but it does not address the ethically distinct scenario in which Company Y recruits Engineer A specifically because of her knowledge of Company X's design strategies. If Company Y's hiring motivation is explicitly or primarily the competitive intelligence value of Engineer A's regulatory access - rather than her general engineering expertise - then the employment transition is not merely a permissible revolving-door situation subject to confidentiality constraints, but a structured attempt to exploit the regulatory process for competitive advantage. In that scenario, both Engineer A and Company Y would bear heightened ethical obligations: Engineer A would be obligated to decline the position or, at minimum, to make explicit to Company Y that she cannot and will not provide any information derived from her government access, and Company Y would be obligated under the faithful agent and conflict of interest avoidance principles to refrain from assigning Engineer A to any work where her prior access could provide competitive advantage over Company X. The Board's silence on the motivational dimension of the hiring decision leaves open a significant ethical gap, because the same employment transition that is conditionally permissible when motivated by legitimate expertise recruitment becomes ethically impermissible when motivated by the desire to acquire competitive intelligence through the back channel of a former government reviewer.

conclusionNumber 106
conclusionText The Board's conclusion implicitly assumes that the competitive intelligence value of Engineer A's government access is incidental to Company Y's hiring decision, but it does not address the ethically ...
conclusionType analytical_extension
mentionedEntities {"capabilities": ["Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation", "Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation Organizational",...
citedProvisions 4 items
answersQuestions 2 items
Conclusion_201 individual committed

In response to Q101, Engineer A's ethical obligations extend beyond merely refraining from active disclosure of Company X's confidential design information. A genuinely compliant posture requires Engineer A to proactively recuse herself from any assignment at Company Y that involves competing directly with Company X's approved or pending facility designs, particularly where her government-acquired structural knowledge of Company X's design approaches could - even subconsciously - inform her technical judgments. This recusal should be formalized in writing at the outset of employment, specifying the subject-matter domains from which Engineer A is excluded, and should be documented in a manner accessible to Company Y's project managers so that inadvertent assignment can be prevented. The recusal record also serves a protective function for Engineer A herself, creating a contemporaneous audit trail demonstrating good-faith compliance with her confidentiality obligations. Without such structural safeguards, the Board's conditional permission to accept employment risks becoming a nominal constraint that is practically unenforceable.

conclusionNumber 201
conclusionText In response to Q101, Engineer A's ethical obligations extend beyond merely refraining from active disclosure of Company X's confidential design information. A genuinely compliant posture requires Engi...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Adversarial Non-Participation Scope Determination at Company Y", "Engineer A Confidential Information Mental Segregation Impossibility Recognition"], "constraints":...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_202 individual committed

In response to Q102, the Board's conclusion is incomplete in limiting its disclosure requirement solely to Company Y. Because Company X is the party whose proprietary regulatory submissions are most directly at risk from Engineer A's transition to a direct competitor, basic principles of fairness and the faithful-agent obligation suggest that Company X also has a legitimate interest in knowing that an individual with access to its confidential design information has joined a competing firm. While the NSPE Code does not explicitly mandate notification to the originating company, the spirit of Section III.4 - which protects confidential information concerning the business affairs of clients - implies that Engineer A should at minimum consider whether Company X's consent or awareness is warranted. Notification to Company X would allow that company to assess whether any protective measures are necessary, such as seeking additional assurances or adjusting its ongoing regulatory submissions. The absence of a mandatory notification requirement in the Board's conclusion leaves a structural gap that could undermine the very confidentiality protections the Code is designed to enforce.

conclusionNumber 202
conclusionText In response to Q102, the Board's conclusion is incomplete in limiting its disclosure requirement solely to Company Y. Because Company X is the party whose proprietary regulatory submissions are most d...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Regulatory Submission Confidentiality Protection \u2014 Company X Information", "Engineer A Post-Public-Employment Non-Exploitation of Company X Confidential...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_203 individual committed

In response to Q103, the Board's acknowledgment of the indeterminacy of the confidentiality obligation's duration is ethically significant but practically insufficient without a governing standard. A workable framework should assess expiration of the confidentiality duty against at least three criteria: first, whether the specific design information has entered the public domain through regulatory disclosure, publication, or independent development by third parties; second, whether the technology embodied in Company X's confidential submissions has been superseded to the point where the information no longer confers competitive advantage; and third, whether the passage of time, combined with material changes in the competitive landscape, renders the information commercially inert. Until all three conditions are satisfied, Engineer A's duty to protect Company X's confidential design information should be treated as continuing. This multi-factor standard is consistent with the perpetual confidentiality norm recognized in BER Case 85-4, while providing a principled mechanism for eventual expiration rather than imposing an indefinite and potentially unreasonable burden on Engineer A's professional mobility.

conclusionNumber 203
conclusionText In response to Q103, the Board's acknowledgment of the indeterminacy of the confidentiality obligation's duration is ethically significant but practically insufficient without a governing standard. A ...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Post-Employment Duty of Trust Duration \u2014 BER Case 85-4", "Engineer A Post-Employment Confidential Information Retention \u2014 Company X Design Data"],...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_204 individual committed

In response to Q104, the government agency bears a distinct institutional responsibility to establish formal revolving-door policies governing engineers who have had access to confidential regulatory submissions. The absence of such policies does not diminish Engineer A's individual ethical obligations under the NSPE Code, but it does represent a systemic failure that increases the probability of inadvertent or deliberate misuse of confidential information across the broader population of government engineers transitioning to private practice. The moral burden is not transferred to Engineer A by the agency's omission - her duties under Sections II.4 and III.4 are independent of institutional policy - but the agency's failure to implement structural safeguards creates an environment in which compliance depends entirely on individual ethical judgment rather than enforceable institutional norms. Company Y also bears a derivative responsibility: knowing that Engineer A held government regulatory access, Company Y should not assign her to work that could exploit that access, regardless of whether any formal policy prohibits it.

conclusionNumber 204
conclusionText In response to Q104, the government agency bears a distinct institutional responsibility to establish formal revolving-door policies governing engineers who have had access to confidential regulatory ...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment Contract", "Engineer A Revolving Door Government-to-Competitor Employment Conflict \u2014...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_205 individual committed

In response to Q201, the tension between Competitive Employment Freedom and the Former Client Adversarial Participation Prohibition is real and structural, not merely theoretical. While the Board correctly concludes that Engineer A may accept employment at Company Y, the practical scope of her permissible contributions at Company Y may be significantly constrained by the prohibition on participating in work that directly competes with or adversely affects Company X's interests using knowledge derived from regulatory access. If Company Y's primary business in the relevant facility design domain overlaps substantially with Company X's approved designs, Engineer A's effective utility to Company Y in that domain may be severely limited. This does not render the employment ethically impermissible, but it does mean that both Engineer A and Company Y must enter the employment relationship with clear-eyed awareness that her contribution scope will be bounded. The Board's conclusion permitting employment is therefore accurate but incomplete without acknowledging this structural limitation on Engineer A's role.

conclusionNumber 205
conclusionText In response to Q201, the tension between Competitive Employment Freedom and the Former Client Adversarial Participation Prohibition is real and structural, not merely theoretical. While the Board corr...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Permissible Competitive Employment Acceptance With Confidentiality Constraint Navigation"], "constraints": ["Engineer A Former Regulatory Access Adversarial...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_206 individual committed

In response to Q203, the Board's requirement that Engineer A disclose her prior government access to Company Y before accepting employment creates a genuine tension with her confidentiality obligation toward Company X. The very act of explaining the nature and scope of her access - necessary for Company Y to understand the conflict - risks revealing that Company X submitted confidential design information of a particular character, scope, or strategic significance. Engineer A must therefore calibrate her disclosure to Company Y with care: she should convey the existence and general subject-matter domain of her access without disclosing the substantive content, design details, or competitive implications of Company X's submissions. This calibrated disclosure approach is consistent with Section III.4.a, which requires consent of all interested parties before arranging employment that could disadvantage a former client. In practice, this means Engineer A's disclosure to Company Y should be framed in terms of the categories of information she cannot use, rather than the content of what she knows.

conclusionNumber 206
conclusionText In response to Q203, the Board's requirement that Engineer A disclose her prior government access to Company Y before accepting employment creates a genuine tension with her confidentiality obligation...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Prior Government Access Disclosure to Company Y", "Engineer A Confidential Regulatory Submission Information Boundary Recognition"], "constraints": ["Engineer A...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_207 individual committed

In response to Q204, the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity is one of the most structurally difficult problems in engineering ethics for government-to-private transitions. The Board's resolution - permitting employment with a confidentiality constraint - represents a reasonable middle position, but it underweights the Post-Public-Service Conflict Avoidance principle when the confidential information is technical, long-lived, and directly relevant to the competitor's core business. Where the information Engineer A holds is not merely incidental but constitutes a sustained competitive advantage - as is plausible with facility design data that may remain valid for decades - the Revolving Door Integrity principle's goal of preserving career mobility must yield to a more robust application of conflict avoidance. In such cases, the ethical weight should shift toward requiring Engineer A to avoid not just active disclosure but any role at Company Y where her structural knowledge of Company X's design philosophy could influence project outcomes, even indirectly.

conclusionNumber 207
conclusionText In response to Q204, the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity is one of the most structurally difficult problems in engineering ethics for government-to-...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Revolving Door Government-to-Competitor Employment Conflict \u2014 Company Y", "Engineer A Post-Public-Employment Non-Exploitation of Company X Confidential...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_208 individual committed

In response to Q301, from a deontological perspective, Engineer A's duty as a faithful agent and trustee does generate a categorical obligation to protect Company X's confidential design information that is not contingent on demonstrable harm. The Kantian structure of the faithful-agent duty under Section II.4 treats the obligation of confidentiality as arising from the relationship of trust itself - the government agency's receipt of Company X's proprietary submissions created a duty of protection that Engineer A assumed by virtue of her role, independent of consequences. This means that even if disclosure would cause no measurable competitive harm to Company X - perhaps because the technology has been partially superseded - the categorical duty to refrain from using or disclosing the information persists until the information is genuinely in the public domain. The deontological analysis therefore supports a stricter reading of the confidentiality obligation than the Board's conclusion implies, one that does not permit Engineer A to rely on a harm-minimization calculus to justify reduced vigilance over time.

conclusionNumber 208
conclusionText In response to Q301, from a deontological perspective, Engineer A's duty as a faithful agent and trustee does generate a categorical obligation to protect Company X's confidential design information t...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Post-Employment Duty of Trust Duration \u2014 BER Case 85-4", "Engineer A Faithful Agent Confidentiality Obligation \u2014 Government Agency Regulatory Context"],...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_209 individual committed

In response to Q302, from a consequentialist perspective, the Board's permissive conclusion is vulnerable to a systemic harm objection that individual-level analysis cannot fully address. If the ethical standard permits government engineers to transition to competitors of companies whose confidential submissions they reviewed - provided only that they personally refrain from disclosure - the aggregate effect across many such transitions may be a significant erosion of regulatory integrity. Companies submitting confidential design information to government agencies do so with an expectation that the information will be protected not merely from active disclosure but from the structural informational advantage that a knowledgeable former regulator brings to a competitor. A consequentialist analysis would require the Board to weigh not only the individual case but the rule-level effects of its conclusion: if the rule 'government engineers may join competitors with a confidentiality pledge' becomes standard practice, the chilling effect on candid regulatory submissions could undermine the quality of government oversight. The Board's conclusion is defensible at the individual level but requires supplementation with systemic safeguards - such as mandatory recusal protocols and agency-level revolving-door policies - to be consequentially sound.

conclusionNumber 209
conclusionText In response to Q302, from a consequentialist perspective, the Board's permissive conclusion is vulnerable to a systemic harm objection that individual-level analysis cannot fully address. If the ethic...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Revolving Door Government-to-Competitor Employment Conflict \u2014 Company Y", "Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_210 individual committed

In response to Q303, from a virtue ethics perspective, the standard of genuine professional integrity demands more than passive non-disclosure. An engineer of authentic virtue - one who has internalized the values of trustworthiness, fairness, and professional responsibility rather than merely complying with their letter - would recognize that the structural knowledge of Company X's design approaches accumulated during government service cannot be cleanly partitioned from her professional judgment. The virtue ethics tradition, which asks what a person of good character would do rather than what rules minimally require, supports proactive recusal from any work at Company Y that could benefit from this structural knowledge, even where the benefit would be subconscious or indirect. This is consistent with the capability identified as 'Engineer A Confidential Information Mental Segregation Impossibility Recognition' - the acknowledgment that cognitive compartmentalization of deeply internalized technical knowledge is not reliably achievable. Virtuous conduct therefore requires Engineer A to err on the side of broader recusal rather than narrower, accepting some limitation on her professional contribution as the price of genuine integrity.

conclusionNumber 210
conclusionText In response to Q303, from a virtue ethics perspective, the standard of genuine professional integrity demands more than passive non-disclosure. An engineer of authentic virtue — one who has internaliz...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Confidential Information Mental Segregation Impossibility Recognition", "Engineer A Adversarial Non-Participation Scope Determination at Company Y"], "constraints":...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_211 individual committed

In response to Q304, from a deontological perspective, the duty to disclose a conflict of interest is not directionally limited to the party who benefits from the disclosure. If Engineer A's obligation to disclose to Company Y arises from the principle that parties affected by a conflict deserve notice - as grounded in Section II.4.a - then the same principle applies with equal or greater force to Company X, which is the party whose proprietary interests are most directly threatened. The deontological argument for disclosure to Company X is in fact stronger than for Company Y: Company Y is the beneficiary of Engineer A's expertise and can protect itself through contractual arrangements, whereas Company X is the vulnerable party with no contractual relationship with Engineer A and no independent means of learning about the transition. Failing to notify Company X treats that company merely as an object of the confidentiality obligation rather than as a rights-bearing party entitled to know that its information is now held by an employee of its direct competitor. The Board's silence on this point represents a gap in the deontological completeness of its analysis.

conclusionNumber 211
conclusionText In response to Q304, from a deontological perspective, the duty to disclose a conflict of interest is not directionally limited to the party who benefits from the disclosure. If Engineer A's obligatio...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Prior Government Access Disclosure to Company Y", "Engineer A Post-Government-Employment Competitive Conflict Pre-Acceptance Assessment"], "constraints": ["Engineer A...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_212 individual committed

In response to Q401, if Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and was subsequently assigned to a project directly competing with Company X's approved facility design, the Board's analysis would almost certainly shift from conditional permission to outright prohibition. The triggering threshold for that transition involves two compounding violations: first, the failure to disclose the conflict of interest to Company Y before accepting employment, which violates Section II.4.a independently; and second, the active participation in work that could exploit or be informed by Company X's confidential submissions, which violates Section III.4. The combination of non-disclosure and adversarial assignment would constitute a complete breach of Engineer A's ethical obligations, not merely a procedural deficiency. The specific threshold is therefore not a single act but the conjunction of concealment at hiring and subsequent assignment to conflicted work - either element alone might be remediable, but together they would place Engineer A in a position of irredeemable ethical violation under the NSPE Code.

conclusionNumber 212
conclusionText In response to Q401, if Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and was subsequently assigned t...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Conflict of Interest Disclosure to Company Y \u2014 Current Case", "Engineer A Former Regulatory Access Adversarial Non-Participation \u2014 Company X Matters at...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_213 individual committed

In response to Q402, the presence of an explicit revolving-door clause in Engineer A's government employment contract would not strengthen her underlying ethical obligations under the NSPE Code - those obligations exist independently of contractual provisions - but it would make them legally enforceable and would remove any ambiguity about their scope and duration. Conversely, the absence of such a clause does not diminish Engineer A's ethical duties: the NSPE Code's confidentiality and conflict-of-interest provisions operate as professional ethical standards that bind Engineer A regardless of what her employment contract does or does not specify. The practical effect of a contractual clause would be to align legal and ethical obligations, reducing the risk that Engineer A might rationalize reduced vigilance on the grounds that no formal prohibition exists. The absence of such a clause therefore represents an institutional gap - attributable to the government agency - that increases reliance on Engineer A's individual ethical judgment but does not alter the substance of what that judgment requires.

conclusionNumber 213
conclusionText In response to Q402, the presence of an explicit revolving-door clause in Engineer A's government employment contract would not strengthen her underlying ethical obligations under the NSPE Code — thos...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment Contract", "Engineer A Revolving Door Government-to-Competitor Employment Conflict \u2014...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_214 individual committed

In response to Q403, if Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked to provide technical analysis drawing on her general expertise - without explicitly referencing Company X's confidential submissions - the switching-sides prohibition recognized in BER Case 85-4 would apply with substantial force. The critical insight from BER Case 85-4 is that the prohibition is not limited to cases where the engineer explicitly uses confidential information; it extends to situations where the engineer's prior access creates an appearance of impropriety or a structural conflict that cannot be neutralized by claimed ignorance of the connection. Engineer A's claimed ignorance that her general expertise was informed by her government-acquired knowledge of Company X's design approaches would provide no meaningful mitigation, consistent with the principle that naivety does not exculpate - as reflected in the constraint 'Engineer A Naivety Non-Exculpation - BER Case 85-4.' The adversarial context would trigger a categorical bar on Engineer A's participation, regardless of whether she consciously drew on Company X's confidential submissions.

conclusionNumber 214
conclusionText In response to Q403, if Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked to provide technical analysis drawing on her general...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer A Forensic Expert Side-Switching Conflict Assessment", "Engineer A Adverse Retention Motivation Recognition"], "constraints": ["Engineer A Switching Sides Forensic...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_215 individual committed

In response to Q404, if Company Y specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies - making competitive intelligence an explicit factor in the hiring decision - the Board's conditional permission to accept employment would not hold. This scenario transforms the employment transition from a permissible career move with incidental confidentiality obligations into a deliberate scheme to exploit confidential regulatory submissions for competitive advantage, which is precisely what Sections III.4 and III.4.a are designed to prevent. Under these circumstances, Engineer A would be ethically prohibited from accepting the position, because doing so would make her a willing instrument of the misappropriation of Company X's confidential information, regardless of whether she personally disclosed any specific design details. Company Y would bear independent ethical culpability for structuring a recruitment strategy around the exploitation of confidential government-access information. Both parties would be in violation of the NSPE Code, and Engineer A's obligation would be to decline the offer and, if appropriate, report the circumstances to the relevant professional or regulatory authorities.

conclusionNumber 215
conclusionText In response to Q404, if Company Y specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies — making competitive intelligence an explicit factor i...
conclusionType question_response
mentionedEntities {"capabilities": ["Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation Organizational", "Engineer A Revolving Door Conflict Recognition Government to Company Y"],...
citedProvisions 4 items
answersQuestions 1 items
Conclusion_301 individual committed

The Board resolved the tension between Competitive Employment Freedom and the Confidentiality Obligation toward Company X's regulatory submissions not by subordinating one principle to the other, but by conditioning the former on strict compliance with the latter. This conditional resolution treats confidentiality as a threshold constraint rather than a competing value to be balanced: Engineer A retains the right to pursue private employment, but that right is structurally bounded by a non-negotiable duty to withhold Company X's proprietary design information. The practical effect is that Competitive Employment Freedom is preserved in form but significantly constrained in substance, because Engineer A's utility to Company Y in any work stream touching Company X's design domain is permanently diminished. This case teaches that when a principle rooted in public trust - here, the protection of confidential regulatory submissions - conflicts with a principle rooted in individual professional autonomy, the Board treats the public-trust principle as lexically prior: freedom of employment survives, but only in the space that remains after confidentiality obligations have been fully honored.

conclusionNumber 301
conclusionText The Board resolved the tension between Competitive Employment Freedom and the Confidentiality Obligation toward Company X's regulatory submissions not by subordinating one principle to the other, but ...
conclusionType principle_synthesis
mentionedEntities {"constraints": ["Engineer A Post-Public-Employment Confidential Information Non-Use \u2014 Company X Design Information", "Engineer A Revolving Door Government-to-Competitor Employment Conflict...
citedProvisions 2 items
answersQuestions 2 items
Conclusion_302 individual committed

The interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves partially unresolved. As a faithful agent and trustee - first to the government agency and derivatively to Company X as a submitting party - Engineer A carries a confidentiality duty that predates and survives her relationship with Company Y. When these obligations collide, the faithful-agent duty to the prior principal functions as a hard ceiling on what Engineer A can legitimately offer Company Y. The Loyalty Obligation to Company Y is therefore not merely limited by ethics in the abstract; it is specifically and materially curtailed by the content of what Engineer A knows. This case teaches that loyalty to a current employer is always prospective and conditional, while confidentiality obligations to prior principals are retrospective and categorical. An engineer cannot discharge the former by simply intending not to disclose; she must actively structure her work at Company Y to ensure that the competitive intelligence value of her prior government access is never operationalized, even indirectly. The Board's conclusion gestures at this by requiring pre-employment disclosure, but does not fully articulate the ongoing affirmative conduct - including potential recusal from specific projects - that genuine reconciliation of these two principles demands.

conclusionNumber 302
conclusionText The interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves pa...
conclusionType principle_synthesis
mentionedEntities {"capabilities": ["Engineer A Confidential Information Mental Segregation Impossibility Recognition", "Engineer A Adversarial Non-Participation Scope Determination at Company Y"], "constraints":...
citedProvisions 3 items
answersQuestions 3 items
Conclusion_303 individual committed

The tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must an engineer bear the competitive disadvantage imposed by prior government access to confidential information? The Board acknowledges the indeterminacy of the confidentiality obligation's duration - noting it persists without specifying when it ends - but declines to establish any mechanism for its expiration. This silence reflects an implicit prioritization of Regulatory Submission Confidentiality Protection over Revolving Door Integrity whenever the confidential information is technical and potentially long-lived. The case thus teaches that the revolving-door principle, while legitimate and important for sustaining a pipeline of experienced engineers between public and private sectors, cannot be invoked to erode confidentiality duties whose duration is tied to the competitive sensitivity of the underlying information rather than to the passage of calendar time. The ethical resolution is not a fixed time limit but a functional standard: Engineer A's confidentiality obligation persists as long as the design information she accessed retains competitive value in the marketplace - a standard that requires ongoing professional judgment rather than a one-time disclosure at the moment of employment transition. The absence of a formal revolving-door policy in the government agency's employment framework does not diminish this obligation; it merely shifts the burden of self-governance entirely onto Engineer A, reinforcing that ethical duties under the NSPE Code are independent of and supplementary to whatever contractual or regulatory mechanisms an employer has or has not established.

conclusionNumber 303
conclusionText The tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must a...
conclusionType principle_synthesis
mentionedEntities {"constraints": ["Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment Contract", "Engineer A Post-Employment Confidential Information Retention \u2014 Company X...
citedProvisions 3 items
answersQuestions 3 items
ethical question 17
Question_1 individual committed

What are Engineer A’s ethical obligations under these circumstances?

questionNumber 1
questionText What are Engineer A’s ethical obligations under these circumstances?
questionType board_explicit
extractionReasoning Parsed from imported case text (no LLM)
Question_101 individual committed

Does Engineer A have an obligation to proactively recuse herself from any work at Company Y that directly involves Company X, even if Company Y never explicitly asks her to contribute such knowledge, and how should that recusal be structured and documented?

questionNumber 101
questionText Does Engineer A have an obligation to proactively recuse herself from any work at Company Y that directly involves Company X, even if Company Y never explicitly asks her to contribute such knowledge, ...
questionType implicit
mentionedEntities {"constraints": ["Engineer A Former Regulatory Access Adversarial Non-Participation \u2014 Company X Matters at Company Y"], "obligations": ["Engineer A Former Regulatory Access Adversarial...
relatedProvisions 3 items
Question_102 individual committed

Is the Board's conclusion sufficient in only requiring disclosure to Company Y before accepting employment, or should Engineer A also be required to notify Company X that its confidential information is now held by an employee of a direct competitor?

questionNumber 102
questionText Is the Board's conclusion sufficient in only requiring disclosure to Company Y before accepting employment, or should Engineer A also be required to notify Company X that its confidential information ...
questionType implicit
mentionedEntities {"obligations": ["Engineer A Conflict of Interest Disclosure to Company Y Regarding Company X Access", "Engineer A Regulatory Submission Confidentiality Protection"], "principles":...
relatedProvisions 3 items
Question_103 individual committed

Given that the Board acknowledges the indeterminacy of the confidentiality obligation's duration, what mechanism or standard should govern when, if ever, Engineer A's duty to protect Company X's confidential design information expires, particularly as technology and competitive landscapes evolve?

questionNumber 103
questionText Given that the Board acknowledges the indeterminacy of the confidentiality obligation's duration, what mechanism or standard should govern when, if ever, Engineer A's duty to protect Company X's confi...
questionType implicit
mentionedEntities {"constraints": ["Engineer A Post-Employment Confidential Information Retention \u2014 Company X Design Data", "Engineer A Post-Employment Duty of Trust Duration \u2014 BER Case 85-4"],...
relatedProvisions 1 items
Question_104 individual committed

Does the government agency itself bear any ethical or institutional responsibility to establish formal revolving-door policies that protect the confidentiality of regulatory submissions, and does the absence of such a policy shift any moral burden onto Engineer A or Company Y?

questionNumber 104
questionText Does the government agency itself bear any ethical or institutional responsibility to establish formal revolving-door policies that protect the confidentiality of regulatory submissions, and does the ...
questionType implicit
mentionedEntities {"constraints": ["Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment Contract"], "resources": ["Revolving_Door_Employment_Policy_Regulatory_Engineer",...
relatedProvisions 2 items
Question_201 individual committed

Does the Competitive Employment Freedom principle, which permits Engineer A to accept a position at Company Y, conflict with the Former Client Adversarial Participation Prohibition, which may effectively bar her from contributing to any work that competes directly with Company X, thereby rendering her employment value to Company Y structurally compromised?

questionNumber 201
questionText Does the Competitive Employment Freedom principle, which permits Engineer A to accept a position at Company Y, conflict with the Former Client Adversarial Participation Prohibition, which may effectiv...
questionType principle_tension
mentionedEntities {"constraints": ["Engineer A Government Regulatory Access Competitor Employment Scope Limitation \u2014 Current Case"], "obligations": ["Engineer A Government-to-Private Competitive Employment...
relatedProvisions 2 items
Question_202 individual committed

How does the Loyalty Obligation of Engineer A to Company Y within ethical limits conflict with the Faithful Agent Confidentiality Obligation grounding her duty to protect Company X's information, particularly when Company Y's competitive interests would be advanced by leveraging insights Engineer A gained through regulatory access?

questionNumber 202
questionText How does the Loyalty Obligation of Engineer A to Company Y within ethical limits conflict with the Faithful Agent Confidentiality Obligation grounding her duty to protect Company X's information, part...
questionType principle_tension
mentionedEntities {"capabilities": ["Engineer A Confidential Information Mental Segregation Impossibility Recognition"], "constraints": ["Company Y Non-Exploitation of Engineer A\u0027s Prior Government Access to...
relatedProvisions 3 items
Question_203 individual committed

Does the Conflict of Interest Disclosure Evolution Principle, which requires Engineer A to make her prior government access known to Company Y before accepting employment, tension with the Confidentiality Obligation toward Company X's regulatory submissions, insofar as the very act of disclosure to Company Y may reveal the nature or existence of Company X's proprietary information?

questionNumber 203
questionText Does the Conflict of Interest Disclosure Evolution Principle, which requires Engineer A to make her prior government access known to Company Y before accepting employment, tension with the Confidentia...
questionType principle_tension
mentionedEntities {"constraints": ["Engineer A Conflict of Interest Disclosure to Company Y \u2014 Prior Government Access to Company X Information", "Engineer A Regulatory Submission Confidentiality Protection...
relatedProvisions 3 items
Question_204 individual committed

Does the Post-Public-Service Conflict Avoidance principle, which counsels Engineer A to avoid situations where her government access creates unfair competitive advantage, conflict with the Revolving Door Integrity principle, which is meant to preserve the ability of government engineers to transition to private practice without permanent career restriction, and how should the Board weigh these competing values when the confidential information is technical and long-lived?

questionNumber 204
questionText Does the Post-Public-Service Conflict Avoidance principle, which counsels Engineer A to avoid situations where her government access creates unfair competitive advantage, conflict with the Revolving D...
questionType principle_tension
mentionedEntities {"constraints": ["Engineer A Revolving Door Government-to-Competitor Employment Conflict \u2014 Company Y", "Engineer A Post-Public-Employment Confidential Information Non-Use \u2014 Company X...
relatedProvisions 2 items
Question_301 individual committed

From a deontological perspective, does Engineer A's duty as a faithful agent and trustee to the government agency create a categorical obligation to protect Company X's confidential design information that persists indefinitely after employment ends, regardless of whether disclosure would cause any measurable harm?

questionNumber 301
questionText From a deontological perspective, does Engineer A's duty as a faithful agent and trustee to the government agency create a categorical obligation to protect Company X's confidential design information...
questionType theoretical
mentionedEntities {"obligations": ["Engineer A Post-Public-Employment Confidential Information Non-Use", "Engineer A Regulatory Submission Confidentiality Protection Company X", "Engineer A Former Client...
relatedProvisions 2 items
Question_302 individual committed

From a consequentialist perspective, does the Board's permissive conclusion - allowing Engineer A to join Company Y provided she withholds Company X's information - adequately account for the systemic harm to regulatory integrity if government engineers routinely transition to competitors with privileged knowledge of confidential submissions, even when individual disclosure is avoided?

questionNumber 302
questionText From a consequentialist perspective, does the Board's permissive conclusion — allowing Engineer A to join Company Y provided she withholds Company X's information — adequately account for the systemic...
questionType theoretical
mentionedEntities {"capabilities": ["Engineer A Confidential Information Mental Segregation Impossibility Recognition"], "constraints": ["Engineer A Revolving Door Government-to-Competitor Employment Conflict...
relatedProvisions 2 items
Question_303 individual committed

From a virtue ethics perspective, does an engineer of genuine professional integrity merely refrain from disclosing confidential information, or does virtuous conduct require Engineer A to proactively recuse herself from any work at Company Y that could benefit from - even subconsciously - the structural knowledge of Company X's design approaches she accumulated during government service?

questionNumber 303
questionText From a virtue ethics perspective, does an engineer of genuine professional integrity merely refrain from disclosing confidential information, or does virtuous conduct require Engineer A to proactively...
questionType theoretical
mentionedEntities {"capabilities": ["Engineer A Confidential Information Mental Segregation Impossibility Recognition", "Engineer A Adversarial Non-Participation Scope Determination at Company Y"], "obligations":...
relatedProvisions 3 items
Question_304 individual committed

From a deontological perspective, does Engineer A's obligation to disclose the conflict of interest to Company Y before accepting employment - as the Board requires - also entail a duty to disclose the same potential conflict to Company X, whose proprietary information is at risk, given that Company X is the party whose interests are most directly threatened by the employment transition?

questionNumber 304
questionText From a deontological perspective, does Engineer A's obligation to disclose the conflict of interest to Company Y before accepting employment — as the Board requires — also entail a duty to disclose th...
questionType theoretical
mentionedEntities {"obligations": ["Engineer A Conflict of Interest Disclosure to Company Y Regarding Company X Access", "Engineer A Regulatory Submission Confidentiality Protection"], "principles": ["Conflict of...
relatedProvisions 3 items
Question_401 individual committed

If Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and Company Y subsequently assigned her to a project directly competing with Company X's approved facility design, would the Board's analysis have shifted from a conditional permission to an outright prohibition - and what specific triggering threshold would mark that transition?

questionNumber 401
questionText If Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and Company Y subsequently assigned her to a project...
questionType counterfactual
mentionedEntities {"actions": ["Accept Position at Competitor", "Withhold Company X Confidential Information"], "constraints": ["Engineer A Conflict of Interest Disclosure to Company Y \u2014 Prior Government...
relatedProvisions 3 items
Question_402 individual committed

What if the government agency had included an explicit revolving-door clause in Engineer A's employment contract prohibiting post-employment work for competitors of companies whose confidential submissions she reviewed - would Engineer A's ethical obligations under the NSPE Code have been strengthened, weakened, or simply made more legally enforceable, and does the absence of such a clause diminish her ethical duties?

questionNumber 402
questionText What if the government agency had included an explicit revolving-door clause in Engineer A's employment contract prohibiting post-employment work for competitors of companies whose confidential submis...
questionType counterfactual
mentionedEntities {"constraints": ["Engineer A No Formal Revolving Door Provision Gap \u2014 Government Agency Employment Contract", "Engineer A Revolving Door Government-to-Competitor Conflict \u2014 Current...
relatedProvisions 2 items
Question_403 individual committed

If, analogous to BER Case 85-4, Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked by Company Y to provide technical analysis drawing on her general expertise in the relevant facility design domain - without explicitly referencing Company X's confidential submissions - would the switching-sides prohibition recognized in BER Case 85-4 apply, and would Engineer A's claimed ignorance of the conflict serve as any mitigation?

questionNumber 403
questionText If, analogous to BER Case 85-4, Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked by Company Y to provide technical analysis d...
questionType counterfactual
mentionedEntities {"constraints": ["Engineer A Switching Sides Forensic Expert Bar \u2014 BER Case 85-4", "Engineer A Naivety Non-Exculpation \u2014 BER Case 85-4", "Engineer A Former Regulatory Access Adversarial...
relatedProvisions 2 items
Question_404 individual committed

What if Company Y had specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies - making the competitive intelligence value of her access an explicit factor in the hiring decision - would the Board's conclusion permitting the employment transition still hold, and what additional obligations would arise for both Engineer A and Company Y under the NSPE Code?

questionNumber 404
questionText What if Company Y had specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies — making the competitive intelligence value of her access an expli...
questionType counterfactual
mentionedEntities {"capabilities": ["Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation", "Engineer A Adverse Retention Motivation Recognition"], "constraints": ["Company Y Non-Exploitation...
relatedProvisions 4 items
Phase 2E: Rich Analysis
49 49 committed
causal normative link 7
CausalLink_Resign from Government Agency individual committed

Resigning from the government agency initiates the revolving door transition and, while not inherently unethical, activates all post-public-employment confidentiality and conflict-of-interest constraints that persist indefinitely after departure.

URI case-106#CausalLink_1
action id case-106#Resign_from_Government_Agency
action label Resign from Government Agency
fulfills obligations 2 items
guided by principles 3 items
constrained by 4 items
agent role http://proethica.org/ontology/intermediate#Confidentiality-BoundGovernmentAgencyEngineer
reasoning Resigning from the government agency initiates the revolving door transition and, while not inherently unethical, activates all post-public-employment confidentiality and conflict-of-interest constrai...
confidence 0.82
CausalLink_Accept Position at Competitor individual committed

Accepting a position at Company Y is permissible under competitive employment freedom but simultaneously triggers the full suite of revolving-door constraints requiring disclosure of prior government access to Company X's confidential information and limiting the scope of work Engineer A may perform at the competitor.

URI case-106#CausalLink_2
action id case-106#Accept_Position_at_Competitor
action label Accept Position at Competitor
fulfills obligations 4 items
violates obligations 3 items
guided by principles 5 items
constrained by 9 items
agent role http://proethica.org/ontology/case/106#Engineer_A_Post-Government_Competitor_Employment_Conflict
reasoning Accepting a position at Company Y is permissible under competitive employment freedom but simultaneously triggers the full suite of revolving-door constraints requiring disclosure of prior government ...
confidence 0.85
CausalLink_Withhold Company X Confidentia individual committed

Withholding Company X's confidential design information is the central affirmative ethical duty that fulfills Engineer A's perpetual post-public-employment confidentiality obligations and prevents the competitor from exploiting regulatory access advantages, guided by the faithful agent principle and the indeterminate duration of confidentiality obligations.

URI case-106#CausalLink_3
action id case-106#Withhold_Company_X_Confidential_Information
action label Withhold Company X Confidential Information
fulfills obligations 12 items
guided by principles 11 items
constrained by 8 items
agent role http://proethica.org/ontology/intermediate#Confidentiality-BoundGovernmentAgencyEngineer
reasoning Withholding Company X's confidential design information is the central affirmative ethical duty that fulfills Engineer A's perpetual post-public-employment confidentiality obligations and prevents the...
confidence 0.93
CausalLink_Accept Retention by Opposing P individual committed

Accepting retention by the opposing party in BER 82-6 directly violates the switching-sides prohibition because the engineer had already acquired confidential knowledge through prior engagement with the original retaining party, and the motivation of the opposing party to neutralize that expertise does not exculpate the ethical breach.

URI case-106#CausalLink_4
action id case-106#Accept_Retention_by_Opposing_Party_(BER_82-6)
action label Accept Retention by Opposing Party (BER 82-6)
violates obligations 5 items
guided by principles 3 items
constrained by 4 items
agent role http://proethica.org/ontology/case/106#Engineer_A_Forensic_Expert_Switching_Sides
reasoning Accepting retention by the opposing party in BER 82-6 directly violates the switching-sides prohibition because the engineer had already acquired confidential knowledge through prior engagement with t...
confidence 0.9
CausalLink_Decline Favorable Plaintiff Re individual committed

Declining to issue a favorable plaintiff report in BER 85-4 is the ethically required outcome because Engineer A's prior confidential access to the plaintiff's case forecloses participation on the opposing side regardless of the report's content, and this declination fulfills the duty to fully discuss the conflict with Attorney Z while honoring the perpetual loyalty obligation to the original client.

URI case-106#CausalLink_5
action id case-106#Decline_Favorable_Plaintiff_Report_(BER_85-4)
action label Decline Favorable Plaintiff Report (BER 85-4)
fulfills obligations 5 items
guided by principles 7 items
constrained by 7 items
agent role http://proethica.org/ontology/case/106#Engineer_A_Forensic_Expert_Switching_Sides
reasoning Declining to issue a favorable plaintiff report in BER 85-4 is the ethically required outcome because Engineer A's prior confidential access to the plaintiff's case forecloses participation on the opp...
confidence 0.88
CausalLink_Accept Retention by Defendant' individual committed

Accepting retention by the defendant's attorney (Attorney X) after having already provided confidential forensic work for the plaintiff (Attorney Z's client) constitutes a direct violation of the switching-sides prohibition, the former client confidentiality perpetuation obligation, and the duty to be aware of adverse retention motivations, as established in BER Case 85-4 and analogized from BER 82-6.

URI case-106#CausalLink_6
action id case-106#Accept_Retention_by_Defendant's_Attorney_(BER_85-4)
action label Accept Retention by Defendant's Attorney (BER 85-4)
violates obligations 9 items
guided by principles 7 items
constrained by 8 items
agent role http://proethica.org/ontology/case/106#Engineer_A_Forensic_Expert_Switching_Sides
reasoning Accepting retention by the defendant's attorney (Attorney X) after having already provided confidential forensic work for the plaintiff (Attorney Z's client) constitutes a direct violation of the swit...
confidence 0.95
CausalLink_Access Confidential Design Inf individual committed

Accessing Company X's confidential design information during government agency employment is a legitimate regulatory function that creates the protective obligation to safeguard that information, but any subsequent use or disclosure of that information in a post-employment competitor context violates the post-public-employment non-use prohibition, the revolving door integrity principle, and the faithful agent confidentiality obligation that persists indefinitely after termination.

URI case-106#CausalLink_7
action id case-106#Access_Confidential_Design_Information
action label Access Confidential Design Information
fulfills obligations 3 items
violates obligations 10 items
guided by principles 11 items
constrained by 16 items
agent role http://proethica.org/ontology/intermediate#Confidentiality-BoundGovernmentAgencyEngineer
reasoning Accessing Company X's confidential design information during government agency employment is a legitimate regulatory function that creates the protective obligation to safeguard that information, but ...
confidence 0.9
question emergence 17
QuestionEmergence_1 individual committed

This foundational question emerged because Engineer A's transition from a government regulatory role-where she accumulated uniquely sensitive competitive intelligence about Company X-to employment at Company X's direct competitor activates multiple overlapping ethical warrants simultaneously, none of which alone fully resolves the scope of her duties. The lack of explicit contractual or institutional guidance forces the question of which obligations govern and how they interact.

URI case-106#Q1
question uri case-106#Q1
question text What are Engineer A’s ethical obligations under these circumstances?
data events 4 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer A's accumulation of Company X's confidential design information during government employment, followed by resignation and acceptance of a position at Company Y (a direct competitor of Company...
competing claims One warrant concludes Engineer A must never use or disclose Company X's confidential information and must avoid any work that exploits it, while a competing warrant concludes Engineer A may accept emp...
rebuttal conditions Uncertainty arises because the absence of a formal revolving-door provision in Engineer A's government employment contract and the indeterminate duration of the confidentiality obligation leave unclea...
emergence narrative This foundational question emerged because Engineer A's transition from a government regulatory role—where she accumulated uniquely sensitive competitive intelligence about Company X—to employment at ...
confidence 0.93
QuestionEmergence_2 individual committed

This question arose because the Board's conclusion that disclosure to Company Y before employment is sufficient does not address the ongoing, day-to-day operational reality at Company Y where Engineer A may be assigned Company X-related work without any explicit request for confidential knowledge. The impossibility of reliably segregating internalized confidential information creates pressure for a proactive, structured recusal mechanism rather than a one-time disclosure.

URI case-106#Q2
question uri case-106#Q2
question text Does Engineer A have an obligation to proactively recuse herself from any work at Company Y that directly involves Company X, even if Company Y never explicitly asks her to contribute such knowledge, ...
data events 3 items
data actions 3 items
involves roles 3 items
competing warrants 3 items
data warrant tension Because Engineer A holds Company X's confidential design information in memory and Company Y may assign her work touching Company X without explicitly requesting that knowledge, the warrant requiring ...
competing claims One warrant concludes Engineer A must proactively identify and recuse herself from any Company Y work directly involving Company X regardless of whether she is asked to contribute confidential knowled...
rebuttal conditions The rebuttal condition creating uncertainty is whether mental segregation of confidential information is practically possible: if Engineer A cannot reliably partition her knowledge, even passive parti...
emergence narrative This question arose because the Board's conclusion that disclosure to Company Y before employment is sufficient does not address the ongoing, day-to-day operational reality at Company Y where Engineer...
confidence 0.91
QuestionEmergence_3 individual committed

This question emerged because the Board's analysis is asymmetric-it imposes disclosure obligations running toward Company Y but is silent on obligations running toward Company X, even though Company X is the party whose competitive interests are most directly threatened. The gap between the Board's conclusion and the full scope of parties affected by Engineer A's transition generates the question of whether the disclosure framework is complete.

URI case-106#Q3
question uri case-106#Q3
question text Is the Board's conclusion sufficient in only requiring disclosure to Company Y before accepting employment, or should Engineer A also be required to notify Company X that its confidential information ...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension Company X submitted confidential design information to the government agency in reliance on regulatory confidentiality protections, but the Board's conclusion addresses only Engineer A's disclosure ob...
competing claims One warrant concludes that disclosure to Company Y is sufficient because the confidentiality obligation runs from Engineer A to her employers and the public, not directly to Company X as a third-party...
rebuttal conditions Uncertainty is created by the absence of any established regulatory or ethical precedent requiring reverse notification to the original submitter of confidential information when a government engineer...
emergence narrative This question emerged because the Board's analysis is asymmetric—it imposes disclosure obligations running toward Company Y but is silent on obligations running toward Company X, even though Company X...
confidence 0.88
QuestionEmergence_4 individual committed

This question arose directly from the Board's candid admission of indeterminacy: by acknowledging that the obligation's duration cannot be fixed while simultaneously affirming its existence, the Board created a logical gap that demands a governing mechanism. Without such a mechanism, Engineer A faces either a perpetual career constraint or an unguided judgment call about when she may freely use her accumulated knowledge.

URI case-106#Q4
question uri case-106#Q4
question text Given that the Board acknowledges the indeterminacy of the confidentiality obligation's duration, what mechanism or standard should govern when, if ever, Engineer A's duty to protect Company X's confi...
data events 4 items
data actions 3 items
involves roles 3 items
competing warrants 3 items
data warrant tension The Board's explicit acknowledgment that the duration of the confidentiality obligation is indeterminate, combined with the reality that technology and competitive landscapes evolve such that formerly...
competing claims One warrant concludes the confidentiality obligation persists indefinitely because the original submission was made in reliance on permanent protection, while the competing warrant concludes the oblig...
rebuttal conditions Uncertainty is created by the absence of any agreed standard for measuring when design information loses competitive sensitivity, by the possibility that information considered obsolete by one metric ...
emergence narrative This question arose directly from the Board's candid admission of indeterminacy: by acknowledging that the obligation's duration cannot be fixed while simultaneously affirming its existence, the Board...
confidence 0.92
QuestionEmergence_5 individual committed

This question emerged because the entire ethical burden in the Board's analysis is placed on Engineer A as an individual, yet the structural condition enabling the conflict-unrestricted government-to-competitor transitions by engineers with access to confidential regulatory submissions-is an institutional design failure. The asymmetry between individual obligation and institutional silence raises the question of whether the ethical framework is complete without addressing the agency's own responsibilities.

URI case-106#Q5
question uri case-106#Q5
question text Does the government agency itself bear any ethical or institutional responsibility to establish formal revolving-door policies that protect the confidentiality of regulatory submissions, and does the ...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension The government agency's failure to establish formal revolving-door policies despite routinely granting engineers access to competitors' confidential regulatory submissions creates tension between the ...
competing claims One warrant concludes that the absence of institutional policy does not diminish Engineer A's individual ethical obligations and that she bears full moral responsibility for managing the conflict, whi...
rebuttal conditions Uncertainty is created by the difficulty of assigning institutional moral responsibility in the absence of a legal mandate for revolving-door policies, and by the question of whether Engineer A's indi...
emergence narrative This question emerged because the entire ethical burden in the Board's analysis is placed on Engineer A as an individual, yet the structural condition enabling the conflict—unrestricted government-to-...
confidence 0.89
QuestionEmergence_6 individual committed

This question emerged because the data of Engineer A's government-acquired confidential access combined with her transition to a direct competitor created a collision between two independently valid ethical warrants - one affirming career mobility and one protecting former regulatory clients - neither of which is facially subordinate to the other. The question crystallizes because the prohibition's scope is undefined, making it impossible to determine in advance whether Engineer A's employment value can be realized without violating the adversarial participation bar.

URI case-106#Q6
question uri case-106#Q6
question text Does the Competitive Employment Freedom principle, which permits Engineer A to accept a position at Company Y, conflict with the Former Client Adversarial Participation Prohibition, which may effectiv...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A's accumulation of Company X's confidential design information through government regulatory access, followed by resignation and acceptance of a position at Company Y (a direct competitor), ...
competing claims The Competitive Employment Freedom warrant concludes Engineer A may lawfully join Company Y, while the Former Client Adversarial Participation Prohibition warrant concludes she cannot contribute to wo...
rebuttal conditions Uncertainty arises because the adversarial participation prohibition's scope is indeterminate — if it extends to all competitive work touching Company X's technical domain rather than only direct adve...
emergence narrative This question emerged because the data of Engineer A's government-acquired confidential access combined with her transition to a direct competitor created a collision between two independently valid e...
confidence 0.87
QuestionEmergence_7 individual committed

This question arose because the data of Engineer A's dual relational position - owing loyalty to Company Y as a new employer while carrying a perpetual confidentiality obligation to Company X as a former regulatory subject - placed two warrants in direct operational conflict at the moment competitive advantage could be extracted. The question is irreducible because the loyalty obligation's ethical-limits qualifier and the confidentiality obligation's scope are both undefined, making it impossible to determine where one warrant yields to the other without normative adjudication.

URI case-106#Q7
question uri case-106#Q7
question text How does the Loyalty Obligation of Engineer A to Company Y within ethical limits conflict with the Faithful Agent Confidentiality Obligation grounding her duty to protect Company X's information, part...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A's simultaneous entry into a client relationship with Company Y and her retention of Company X's confidential regulatory submission data triggers both the warrant requiring loyal service to ...
competing claims The Loyalty Obligation warrant concludes Engineer A must actively serve Company Y's competitive interests to the fullest ethical extent, while the Faithful Agent Confidentiality Obligation warrant con...
rebuttal conditions Uncertainty is generated by the qualifier 'within ethical limits' attached to the loyalty obligation — if that qualifier is interpreted broadly to encompass all information asymmetries arising from pr...
emergence narrative This question arose because the data of Engineer A's dual relational position — owing loyalty to Company Y as a new employer while carrying a perpetual confidentiality obligation to Company X as a for...
confidence 0.89
QuestionEmergence_8 individual committed

This question emerged because the data of Engineer A's regulatory access created a structural paradox: the disclosure obligation that normally resolves conflicts of interest cannot be fulfilled without potentially breaching the confidentiality obligation it is meant to coexist with. The question is not merely about competing duties but about a logical incompatibility in the compliance mechanisms of two simultaneously applicable warrants, which the existing ethical framework does not resolve.

URI case-106#Q8
question uri case-106#Q8
question text Does the Conflict of Interest Disclosure Evolution Principle, which requires Engineer A to make her prior government access known to Company Y before accepting employment, tension with the Confidentia...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A's possession of Company X's confidential regulatory submissions and her transition to Company Y simultaneously triggers the disclosure evolution warrant — requiring her to inform Company Y ...
competing claims The Conflict of Interest Disclosure Evolution warrant concludes Engineer A must proactively disclose the nature and scope of her prior government access to Company Y, while the Confidentiality Obligat...
rebuttal conditions Uncertainty arises because the rebuttal condition for the disclosure warrant — that disclosure is impermissible when it itself constitutes a confidentiality breach — is precisely the situation Enginee...
emergence narrative This question emerged because the data of Engineer A's regulatory access created a structural paradox: the disclosure obligation that normally resolves conflicts of interest cannot be fulfilled withou...
confidence 0.91
QuestionEmergence_9 individual committed

This question arose because the data of technically durable confidential information combined with a government-to-competitor transition placed two structurally opposed policy warrants - one protecting the integrity of the regulatory process and one protecting the career mobility of government engineers - in direct conflict with no temporal escape valve. The question is particularly acute because the Board must weigh these values not in the abstract but in a case where the information's longevity means the conflict avoidance obligation could effectively function as a permanent bar, which is precisely what the Revolving Door Integrity principle was designed to prevent.

URI case-106#Q9
question uri case-106#Q9
question text Does the Post-Public-Service Conflict Avoidance principle, which counsels Engineer A to avoid situations where her government access creates unfair competitive advantage, conflict with the Revolving D...
data events 4 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A's accumulation of long-lived technical confidential information through government regulatory access, followed by her transition to a direct competitor, simultaneously activates the Post-Pu...
competing claims The Post-Public-Service Conflict Avoidance warrant concludes Engineer A should decline or severely restrict her role at Company Y to prevent unfair competitive advantage derived from regulatory access...
rebuttal conditions Uncertainty is compounded by the Confidentiality Duration Indeterminacy Principle — the rebuttal condition under which the conflict avoidance obligation would expire (when the confidential information...
emergence narrative This question arose because the data of technically durable confidential information combined with a government-to-competitor transition placed two structurally opposed policy warrants — one protectin...
confidence 0.88
QuestionEmergence_10 individual committed

This question arose because the data of Engineer A's role as a faithful agent and trustee - a status that generates categorical rather than merely consequentialist obligations under deontological analysis - combined with her post-employment retention of confidential information created a foundational jurisprudential dispute about whether fiduciary duties are role-bound or information-bound. The question is irreducible because the deontological framing removes harm-calculus as a resolution mechanism, forcing the analysis to confront whether the duty's categorical character survives role termination, which the existing BER precedent framework addresses only partially and without explicit deontological grounding.

URI case-106#Q10
question uri case-106#Q10
question text From a deontological perspective, does Engineer A's duty as a faithful agent and trustee to the government agency create a categorical obligation to protect Company X's confidential design information...
data events 3 items
data actions 3 items
involves roles 3 items
competing warrants 2 items
data warrant tension Engineer A's acceptance of Company X's confidential design information in her capacity as a faithful agent and trustee of the government agency triggers the deontological warrant that such fiduciary o...
competing claims The Faithful Agent Confidentiality Obligation warrant concludes that Engineer A's duty to protect Company X's confidential design information is categorical, indefinite, and harm-independent — persist...
rebuttal conditions Uncertainty is created by the Confidentiality Duration Indeterminacy Principle and the absence of a formal revolving door provision in Engineer A's government employment contract — the rebuttal condit...
emergence narrative This question arose because the data of Engineer A's role as a faithful agent and trustee — a status that generates categorical rather than merely consequentialist obligations under deontological anal...
confidence 0.86
QuestionEmergence_11 individual committed

This question arose because the Board's analysis operates at the level of individual conduct (withhold the information) while consequentialism demands evaluation at the population level (what happens when all engineers in this position behave identically). The data of routine government-to-competitor transitions combined with the warrant of regulatory submission confidentiality creates an unresolved gap between micro-permissibility and macro-harm.

URI case-106#Q11
question uri case-106#Q11
question text From a consequentialist perspective, does the Board's permissive conclusion — allowing Engineer A to join Company Y provided she withholds Company X's information — adequately account for the systemic...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A's accumulation of confidential regulatory knowledge and subsequent move to a competitor simultaneously activates the individual-level warrant permitting employment with confidentiality cons...
competing claims The individual-disclosure warrant concludes that withholding Company X's information is sufficient ethical compliance, while the systemic-integrity warrant concludes that conditional permission ignore...
rebuttal conditions The individual-sufficiency warrant is rebutted when the structural knowledge Engineer A carries — even without explicit disclosure — provides competitive advantage that undermines the confidentiality ...
emergence narrative This question arose because the Board's analysis operates at the level of individual conduct (withhold the information) while consequentialism demands evaluation at the population level (what happens ...
confidence 0.87
QuestionEmergence_12 individual committed

This question arose because virtue ethics evaluates character dispositions rather than discrete acts, and the data of accumulated structural knowledge creates a situation where the act of refraining from disclosure is insufficient to satisfy the virtue of integrity if subconscious influence remains possible. The gap between what the Board requires (non-disclosure) and what virtue demands (proactive recusal) is the source of the question.

URI case-106#Q12
question uri case-106#Q12
question text From a virtue ethics perspective, does an engineer of genuine professional integrity merely refrain from disclosing confidential information, or does virtuous conduct require Engineer A to proactively...
data events 3 items
data actions 3 items
involves roles 3 items
competing warrants 2 items
data warrant tension The data of deep structural knowledge accumulated over government service triggers both the minimal-compliance warrant (refrain from explicit disclosure) and the virtue-ethics warrant (act as a person...
competing claims The non-disclosure warrant concludes that Engineer A satisfies her obligations by not sharing Company X's information, while the virtuous-character warrant concludes that a person of genuine integrity...
rebuttal conditions The minimal-compliance warrant is rebutted by the recognized incapability of mental segregation — captured in the Confidential Information Mental Segregation Impossibility Recognition Capability entit...
emergence narrative This question arose because virtue ethics evaluates character dispositions rather than discrete acts, and the data of accumulated structural knowledge creates a situation where the act of refraining f...
confidence 0.85
QuestionEmergence_13 individual committed

This question arose because the Board's disclosure obligation is structurally asymmetric - it protects Company Y from unknowing complicity but leaves Company X, the most directly harmed party, without notice or recourse. The deontological demand for consistency in treating all affected parties as ends generates a competing warrant that the Board's analysis does not address.

URI case-106#Q13
question uri case-106#Q13
question text From a deontological perspective, does Engineer A's obligation to disclose the conflict of interest to Company Y before accepting employment — as the Board requires — also entail a duty to disclose th...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension The data of Engineer A holding Company X's confidential information while transitioning to a competitor triggers both the disclosure-to-new-employer warrant (protecting Company Y from unknowing compli...
competing claims The Board's disclosure warrant concludes that Engineer A must inform Company Y of the conflict, while a symmetrical deontological warrant concludes that Company X — as the party whose confidential sub...
rebuttal conditions The Company-Y-only disclosure warrant is rebutted when the deontological principle of treating affected parties as ends in themselves is applied consistently, because Company X is the party whose prop...
emergence narrative This question arose because the Board's disclosure obligation is structurally asymmetric — it protects Company Y from unknowing complicity but leaves Company X, the most directly harmed party, without...
confidence 0.83
QuestionEmergence_14 individual committed

This question arose because the Board's conditional framework does not specify the triggering threshold at which conditions are so thoroughly violated that the permission collapses into prohibition, and the hypothetical of undisclosed transition plus direct competitive assignment tests exactly that unspecified boundary. The absence of a defined threshold in the warrant structure is the source of the question.

URI case-106#Q14
question uri case-106#Q14
question text If Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and Company Y subsequently assigned her to a project...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension The hypothetical data of undisclosed transition combined with direct competitive project assignment simultaneously activates the conditional-permission warrant (employment is permissible with disclosu...
competing claims The conditional-permission warrant concludes that the Board's framework remains operative as long as disclosure occurs and information is withheld, while the prohibition warrant concludes that assignm...
rebuttal conditions The conditional-permission warrant is rebutted when the combination of non-disclosure and direct competitive assignment removes the procedural safeguards (disclosure, scope limitation) that justified ...
emergence narrative This question arose because the Board's conditional framework does not specify the triggering threshold at which conditions are so thoroughly violated that the permission collapses into prohibition, a...
confidence 0.86
QuestionEmergence_15 individual committed

This question arose because the absence of a contractual revolving-door provision creates ambiguity about the relationship between legal enforceability and ethical obligation, and the data of that contractual gap invites the inference that ethical duties are weaker without legal backing. The question tests whether the NSPE Code's warrants are self-sufficient or parasitic on legal instruments, a tension the Board's analysis leaves implicit rather than resolved.

URI case-106#Q15
question uri case-106#Q15
question text What if the government agency had included an explicit revolving-door clause in Engineer A's employment contract prohibiting post-employment work for competitors of companies whose confidential submis...
data events 3 items
data actions 2 items
involves roles 4 items
competing warrants 2 items
data warrant tension The data of a contractual gap — the absence of an explicit revolving-door clause in Engineer A's government employment contract — triggers competing warrants about whether ethical obligations are deri...
competing claims The legal-instrument warrant concludes that the absence of a revolving-door clause diminishes or at least fails to reinforce Engineer A's ethical obligations, while the independent-professional-ethics...
rebuttal conditions The legal-instrument warrant is rebutted by the principle that professional ethical obligations derive from the engineer's role and the nature of the confidential access — not from contractual specifi...
emergence narrative This question arose because the absence of a contractual revolving-door provision creates ambiguity about the relationship between legal enforceability and ethical obligation, and the data of that con...
confidence 0.84
QuestionEmergence_16 individual committed

This question arose because BER Case 85-4 established a switching-sides prohibition grounded in the structural integrity of adversarial proceedings and the impossibility of mentally segregating confidential information, but the current scenario introduces a factual variation - claimed general expertise without explicit confidential reference - that tests whether the prohibition is categorical or contingent on demonstrable information use. The Engineer A Naivety Non-Exculpation constraint simultaneously forecloses the ignorance defense, creating a gap between the precedent's logic and its stated scope that the question is designed to expose.

URI case-106#Q16
question uri case-106#Q16
question text If, analogous to BER Case 85-4, Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked by Company Y to provide technical analysis d...
data events 4 items
data actions 3 items
involves roles 6 items
competing warrants 3 items
data warrant tension Engineer A's accumulation of confidential knowledge about Company X through government regulatory access, combined with the BER 85-4 precedent establishing a switching-sides prohibition for forensic e...
competing claims The switching-sides prohibition warrant concludes that Engineer A is categorically barred from providing technical analysis adverse to Company X in any regulatory or legal proceeding regardless of cla...
rebuttal conditions Uncertainty arises because the rebuttal condition — that Engineer A's analysis draws only on general expertise without referencing Company X's confidential submissions — is practically unverifiable gi...
emergence narrative This question arose because BER Case 85-4 established a switching-sides prohibition grounded in the structural integrity of adversarial proceedings and the impossibility of mentally segregating confid...
confidence 0.87
QuestionEmergence_17 individual committed

This question arose because the Board's original conclusion permitting the employment transition was premised on the assumption that the hiring motivation was legitimate competitive employment rather than targeted extraction of regulatory intelligence, and the introduction of explicit competitive intelligence motivation as a hiring factor destabilizes that premise by activating the Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation constraint and the Adversarial Retention Motivation Awareness Obligation against both parties. The question exposes a structural gap in the Board's analysis: whether the ethical framework addresses only Engineer A's post-employment conduct or also reaches Company Y's institutional intent in structuring the hire, and what additional obligations - such as Engineer A's duty to decline or disclose and Company Y's duty to refrain from exploiting the access - arise when the exploitation is not incidental but deliberate.

URI case-106#Q17
question uri case-106#Q17
question text What if Company Y had specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies — making the competitive intelligence value of her access an expli...
data events 4 items
data actions 4 items
involves roles 4 items
competing warrants 3 items
data warrant tension The explicit recruitment of Engineer A by Company Y because of her government-acquired knowledge of Company X's design strategies transforms the employment transition from a permissible revolving-door...
competing claims The revolving-door integrity and post-public-service conflict avoidance warrants conclude that the Board's permissive employment transition conclusion cannot hold when competitive intelligence exploit...
rebuttal conditions Uncertainty arises because the rebuttal condition that would preserve the Board's permissive conclusion — that Engineer A's personal confidentiality maintenance is sufficient to neutralize Company Y's...
emergence narrative This question arose because the Board's original conclusion permitting the employment transition was premised on the assumption that the hiring motivation was legitimate competitive employment rather ...
confidence 0.89
resolution pattern 25
ResolutionPattern_1 individual committed

The Board concluded that the employment transition is ethically permissible because the NSPE Code does not prohibit engineers from changing employers or joining competitors, but only from weaponizing confidential knowledge gained in prior roles; by requiring both non-disclosure of Company X's proprietary information and pre-employment disclosure of the conflict to Company Y, the Board treated the two conditions as jointly sufficient to satisfy Engineer A's duties under II.4, II.4.a, III.4, and III.4.a.

URI case-106#C1
conclusion uri case-106#C1
conclusion text Engineer A is free to pursue employment with Company Y provided Engineer A does not disclose any confidential and proprietary design information Engineer A learned about Company X during Engineer A's ...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 4 items
weighing process The Board balanced Engineer A's right to pursue private employment against her confidentiality obligations by permitting the transition conditionally — preserving employment freedom while enforcing th...
resolution narrative The Board concluded that the employment transition is ethically permissible because the NSPE Code does not prohibit engineers from changing employers or joining competitors, but only from weaponizing ...
confidence 0.92
ResolutionPattern_2 individual committed

The Board extended C1's conditional permission by finding that the faithful agent standard under II.4 and the confidentiality obligation under III.4 generate not a one-time disclosure duty but a continuing affirmative recusal obligation, and that this obligation must be institutionally documented - through written notice to management and project records - because individual conscience alone is an insufficient safeguard against the subconscious competitive exploitation of privileged knowledge in an ongoing work environment.

URI case-106#C2
conclusion uri case-106#C2
conclusion text Beyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The conclusion weighs Engineer A's loyalty obligation to Company Y against her continuing confidentiality duty to Company X's information by resolving that loyalty cannot extend to assignments where p...
resolution narrative The Board extended C1's conditional permission by finding that the faithful agent standard under II.4 and the confidentiality obligation under III.4 generate not a one-time disclosure duty but a conti...
confidence 0.88
ResolutionPattern_3 individual committed

The Board found that C1's exclusive focus on disclosure to Company Y is structurally incomplete because the faithful agent standard under II.4 and the anti-detriment principle under III.4.a create obligations that run toward Company X as the information's originating party, and that leaving Company X without any procedural protection beyond Engineer A's individual conscience is an insufficient safeguard given the competitive asymmetry the employment transition creates.

URI case-106#C3
conclusion uri case-106#C3
conclusion text The Board's conclusion requires Engineer A to disclose her prior government access to Company Y before accepting employment, but it does not address whether Company X — the party whose proprietary inf...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The conclusion weighs the disclosure obligation to Company Y — which the Board already requires — against the omitted question of whether Company X's status as the party most directly at risk generate...
resolution narrative The Board found that C1's exclusive focus on disclosure to Company Y is structurally incomplete because the faithful agent standard under II.4 and the anti-detriment principle under III.4.a create obl...
confidence 0.85
ResolutionPattern_4 individual committed

The Board resolved the duration indeterminacy by rejecting both a purely temporal expiration and a perpetual absolute prohibition, instead holding under a combined deontological-consequentialist framework that Engineer A's confidentiality duty under III.4 persists as long as the information retains competitive or regulatory sensitivity not publicly dissolved through the approval process itself, with Engineer A bearing the burden of demonstrating that changed circumstances - not mere passage of time - have lifted the constraint.

URI case-106#C4
conclusion uri case-106#C4
conclusion text The Board acknowledges that the duration of Engineer A's confidentiality obligation is indeterminate but declines to establish any standard or mechanism for when, if ever, that obligation expires. Thi...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The conclusion balances the deontological persistence of trust-based duties — which do not dissolve merely with time — against the consequentialist harm of indefinite career restriction by adopting a ...
resolution narrative The Board resolved the duration indeterminacy by rejecting both a purely temporal expiration and a perpetual absolute prohibition, instead holding under a combined deontological-consequentialist frame...
confidence 0.83
ResolutionPattern_5 individual committed

The Board found that C1's individual-level resolution, while ethically sound on its own terms, fails to address the systemic dimension of the revolving-door problem: by permitting the transition subject only to individual confidentiality maintenance, the conclusion implicitly places the entire burden of protecting regulatory integrity on Engineer A's conscience rather than acknowledging that the government agency bears an institutional responsibility - unaddressed by the NSPE Code but ethically cognizable - to establish formal cooling-off policies that structurally prevent the competitive exploitation of confidential regulatory submissions.

URI case-106#C5
conclusion uri case-106#C5
conclusion text The Board's analysis does not address the systemic dimension of the revolving-door problem it implicitly resolves at the individual level. By permitting Engineer A's transition to Company Y subject on...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The conclusion weighs Engineer A's individual ethical compliance — which the Board finds necessary — against the systemic inadequacy of relying solely on individual conscience to protect regulatory in...
resolution narrative The Board found that C1's individual-level resolution, while ethically sound on its own terms, fails to address the systemic dimension of the revolving-door problem: by permitting the transition subje...
confidence 0.81
ResolutionPattern_6 individual committed

The board resolved Q16 by extending BER Case 85-4's switching-sides prohibition to Engineer A's situation, concluding that if Company X and Company Y become adversaries in any regulatory or legal proceeding touching the facility design domain, Engineer A is categorically barred from contributing to Company Y's position - and further concluded that this constraint should have been made explicit in the original permission rather than left to be inferred from precedent, with Company Y notified at the time of pre-employment disclosure.

URI case-106#C6
conclusion uri case-106#C6
conclusion text The Board's conditional permission for Engineer A to join Company Y does not adequately address the scenario — raised by analogy to BER Case 85-4 — in which Company Y later becomes involved in an adve...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board subordinated Engineer A's employment freedom and Company Y's interest in full use of her expertise to the categorical prohibition against adversarial participation derived from BER Case 85-4...
resolution narrative The board resolved Q16 by extending BER Case 85-4's switching-sides prohibition to Engineer A's situation, concluding that if Company X and Company Y become adversaries in any regulatory or legal proc...
confidence 0.87
ResolutionPattern_7 individual committed

The board resolved Q17 by identifying a significant ethical gap in the original conclusion's silence on hiring motivation, determining that if Company Y recruited Engineer A specifically for her competitive intelligence value, the transition is not a permissible revolving-door situation but a structured exploitation of the regulatory process - requiring Engineer A to decline or impose explicit limitations and requiring Company Y to refrain from assigning her to any work where prior access could advantage it over Company X.

URI case-106#C7
conclusion uri case-106#C7
conclusion text The Board's conclusion implicitly assumes that the competitive intelligence value of Engineer A's government access is incidental to Company Y's hiring decision, but it does not address the ethically ...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board balanced Engineer A's right to competitive employment against the faithful-agent and conflict-avoidance obligations by making permissibility contingent on hiring motivation, holding that whe...
resolution narrative The board resolved Q17 by identifying a significant ethical gap in the original conclusion's silence on hiring motivation, determining that if Company Y recruited Engineer A specifically for her compe...
confidence 0.85
ResolutionPattern_8 individual committed

The board concluded in response to Q101 that genuine compliance with confidentiality obligations requires Engineer A to proactively formalize her recusal in writing at the outset of employment, specifying excluded subject-matter domains and making the record accessible to Company Y's project managers, because without such structural safeguards the Board's conditional permission risks becoming a nominal constraint that subconscious knowledge transfer can silently violate.

URI case-106#C8
conclusion uri case-106#C8
conclusion text In response to Q101, Engineer A's ethical obligations extend beyond merely refraining from active disclosure of Company X's confidential design information. A genuinely compliant posture requires Engi...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the tension between Engineer A's employment utility to Company Y and her confidentiality obligations to Company X by requiring formalized written recusal that restricts her assignab...
resolution narrative The board concluded in response to Q101 that genuine compliance with confidentiality obligations requires Engineer A to proactively formalize her recusal in writing at the outset of employment, specif...
confidence 0.9
ResolutionPattern_9 individual committed

The board resolved Q102 by identifying a structural gap in the original conclusion's exclusive focus on disclosure to Company Y, concluding that basic principles of fairness and the faithful-agent obligation suggest Company X also has a legitimate interest in knowing that an individual with access to its confidential design information has joined a competing firm, and that Engineer A should at minimum consider whether Company X's consent or awareness is warranted to allow that company to assess and implement protective measures.

URI case-106#C9
conclusion uri case-106#C9
conclusion text In response to Q102, the Board's conclusion is incomplete in limiting its disclosure requirement solely to Company Y. Because Company X is the party whose proprietary regulatory submissions are most d...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board weighed Engineer A's disclosure obligation to Company Y against the fairness interest of Company X by finding the original conclusion incomplete, holding that the spirit of Section III.4 imp...
resolution narrative The board resolved Q102 by identifying a structural gap in the original conclusion's exclusive focus on disclosure to Company Y, concluding that basic principles of fairness and the faithful-agent obl...
confidence 0.83
ResolutionPattern_10 individual committed

The board resolved Q103 by constructing a three-factor expiration standard - requiring public domain entry, technological supersession, and commercial inertness to all be present before the confidentiality duty expires - treating this multi-factor framework as consistent with BER Case 85-4's perpetual norm while providing a principled and workable mechanism for eventual termination that avoids imposing an indefinite and potentially unreasonable restriction on Engineer A's career.

URI case-106#C10
conclusion uri case-106#C10
conclusion text In response to Q103, the Board's acknowledgment of the indeterminacy of the confidentiality obligation's duration is ethically significant but practically insufficient without a governing standard. A ...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board balanced the deontological pull toward indefinite confidentiality protection — grounded in BER Case 85-4's perpetual norm — against the consequentialist concern that an indefinite and unreas...
resolution narrative The board resolved Q103 by constructing a three-factor expiration standard — requiring public domain entry, technological supersession, and commercial inertness to all be present before the confidenti...
confidence 0.88
ResolutionPattern_11 individual committed

The board concluded that the agency bears a distinct but non-transferable institutional responsibility for the absence of revolving-door policies, because such policies would reduce systemic risk across the population of transitioning engineers; Engineer A's duties under II.4 and III.4 persist independently of that failure, and Company Y acquires a derivative obligation not to assign Engineer A to roles that could exploit her regulatory access.

URI case-106#C11
conclusion uri case-106#C11
conclusion text In response to Q104, the government agency bears a distinct institutional responsibility to establish formal revolving-door policies governing engineers who have had access to confidential regulatory ...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board refused to transfer Engineer A's individual moral burden to the agency's institutional failure, holding that Sections II.4 and III.4 obligations are self-standing, while simultaneously distr...
resolution narrative The board concluded that the agency bears a distinct but non-transferable institutional responsibility for the absence of revolving-door policies, because such policies would reduce systemic risk acro...
confidence 0.91
ResolutionPattern_12 individual committed

The board concluded that Engineer A may accept employment at Company Y because Competitive Employment Freedom is not extinguished by the conflict, but the conclusion identifies a structural gap in the board's reasoning: the prohibition on adversarial participation using regulatory-access-derived knowledge may so substantially restrict Engineer A's permissible work in the overlapping domain that both parties must enter the relationship with explicit awareness of those bounded contributions.

URI case-106#C12
conclusion uri case-106#C12
conclusion text In response to Q201, the tension between Competitive Employment Freedom and the Former Client Adversarial Participation Prohibition is real and structural, not merely theoretical. While the Board corr...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board resolved the tension by permitting employment as the primary outcome while subordinating the adversarial participation prohibition to a role-scoping constraint rather than an employment bar,...
resolution narrative The board concluded that Engineer A may accept employment at Company Y because Competitive Employment Freedom is not extinguished by the conflict, but the conclusion identifies a structural gap in the...
confidence 0.88
ResolutionPattern_13 individual committed

The board concluded that Engineer A can satisfy her pre-employment disclosure obligation to Company Y without breaching her confidentiality duty to Company X by framing disclosure in terms of what she cannot use rather than what she knows, because this approach conveys the existence and general domain of the conflict while withholding the substantive design details and competitive implications that Section III.4 protects.

URI case-106#C13
conclusion uri case-106#C13
conclusion text In response to Q203, the Board's requirement that Engineer A disclose her prior government access to Company Y before accepting employment creates a genuine tension with her confidentiality obligation...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board balanced the disclosure obligation to Company Y against the confidentiality obligation to Company X by restricting the content of disclosure to categories of unusable information rather than...
resolution narrative The board concluded that Engineer A can satisfy her pre-employment disclosure obligation to Company Y without breaching her confidentiality duty to Company X by framing disclosure in terms of what she...
confidence 0.9
ResolutionPattern_14 individual committed

The board reached a permissive-with-constraint resolution, but the conclusion argues this is insufficient when the confidential information constitutes a sustained competitive advantage rather than incidental knowledge, because in those circumstances the structural knowledge of Company X's design philosophy could influence project outcomes even without active disclosure, requiring Engineer A to avoid any role at Company Y where that influence could operate.

URI case-106#C14
conclusion uri case-106#C14
conclusion text In response to Q204, the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity is one of the most structurally difficult problems in engineering ethics for government-to-...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board's middle position is critiqued as underweighting Post-Public-Service Conflict Avoidance when the information is long-lived and technically specific, with the conclusion arguing that Revolvin...
resolution narrative The board reached a permissive-with-constraint resolution, but the conclusion argues this is insufficient when the confidential information constitutes a sustained competitive advantage rather than in...
confidence 0.86
ResolutionPattern_15 individual committed

The board concluded from a deontological perspective that Engineer A's confidentiality obligation is categorical and non-contingent because it arises from the trust relationship created when the agency received Company X's proprietary submissions, not from the consequences of breach; this means the conclusion supports a stricter standard than the board's own analysis implies, one that forecloses reliance on harm-minimization reasoning to justify any relaxation of vigilance as technology evolves.

URI case-106#C15
conclusion uri case-106#C15
conclusion text In response to Q301, from a deontological perspective, Engineer A's duty as a faithful agent and trustee does generate a categorical obligation to protect Company X's confidential design information t...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board's consequentialist flexibility is rejected in favor of a strict Kantian reading under which the faithful-agent duty under Section II.4 is categorical and relationship-grounded, meaning the o...
resolution narrative The board concluded from a deontological perspective that Engineer A's confidentiality obligation is categorical and non-contingent because it arises from the trust relationship created when the agenc...
confidence 0.93
ResolutionPattern_16 individual committed

The Board resolved Q302 by acknowledging that its permissive conclusion survives individual-level consequentialist scrutiny but fails systemic scrutiny unless supplemented by structural safeguards such as mandatory recusal protocols and revolving-door policies, thereby accepting the conclusion conditionally rather than categorically and deferring full consequentialist soundness to institutional-level remedies rather than individual ethical obligation alone.

URI case-106#C16
conclusion uri case-106#C16
conclusion text In response to Q302, from a consequentialist perspective, the Board's permissive conclusion is vulnerable to a systemic harm objection that individual-level analysis cannot fully address. If the ethic...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board weighed individual-level permissibility against systemic rule-level effects and found the former defensible but insufficient without institutional safeguards, subordinating pure individual c...
resolution narrative The Board resolved Q302 by acknowledging that its permissive conclusion survives individual-level consequentialist scrutiny but fails systemic scrutiny unless supplemented by structural safeguards suc...
confidence 0.87
ResolutionPattern_17 individual committed

The Board resolved Q303 by applying the virtue ethics framework's question of what a person of good character would do rather than what rules minimally require, concluding that genuine professional integrity demands proactive recusal from any conflicted work at Company Y - even at professional cost - because the structural knowledge Engineer A holds cannot be reliably segregated from her judgment, making passive non-disclosure an insufficient expression of virtuous conduct.

URI case-106#C17
conclusion uri case-106#C17
conclusion text In response to Q303, from a virtue ethics perspective, the standard of genuine professional integrity demands more than passive non-disclosure. An engineer of authentic virtue — one who has internaliz...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board weighed the virtue ethics demand for authentic integrity against the narrower compliance standard of passive non-disclosure, resolving in favor of broader proactive recusal by treating the i...
resolution narrative The Board resolved Q303 by applying the virtue ethics framework's question of what a person of good character would do rather than what rules minimally require, concluding that genuine professional in...
confidence 0.91
ResolutionPattern_18 individual committed

The Board resolved Q304 by extending the deontological disclosure principle symmetrically, reasoning that if the duty to disclose a conflict arises from the right of affected parties to receive notice, then Company X - as the most directly threatened and most structurally vulnerable party - has an equal or stronger claim to notification than Company Y, and the Board's failure to require such disclosure represents an incomplete application of its own deontological framework.

URI case-106#C18
conclusion uri case-106#C18
conclusion text In response to Q304, from a deontological perspective, the duty to disclose a conflict of interest is not directionally limited to the party who benefits from the disclosure. If Engineer A's obligatio...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The Board weighed the deontological duty of disclosure as between Company Y (the beneficiary with self-protective capacity) and Company X (the vulnerable party with no independent means of protection)...
resolution narrative The Board resolved Q304 by extending the deontological disclosure principle symmetrically, reasoning that if the duty to disclose a conflict arises from the right of affected parties to receive notice...
confidence 0.85
ResolutionPattern_19 individual committed

The Board resolved Q401 by identifying a two-element conjunctive threshold - non-disclosure at hiring plus adversarial assignment - as the specific trigger for outright prohibition, reasoning that the first violation (concealment) removes the procedural safeguard that makes the employment transition conditionally permissible, and the second violation (conflicted assignment) actualizes the harm that the confidentiality obligation was designed to prevent, together constituting an irredeemable breach under the NSPE Code.

URI case-106#C19
conclusion uri case-106#C19
conclusion text In response to Q401, if Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and was subsequently assigned t...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The Board weighed the remediability of each violation independently against their combined effect, concluding that while either element alone might be correctable, their conjunction eliminates the pos...
resolution narrative The Board resolved Q401 by identifying a two-element conjunctive threshold — non-disclosure at hiring plus adversarial assignment — as the specific trigger for outright prohibition, reasoning that the...
confidence 0.92
ResolutionPattern_20 individual committed

The Board resolved Q402 by drawing a clear distinction between the legal and ethical planes: a revolving-door clause would strengthen enforceability and reduce rationalization risk but would not alter the substance of Engineer A's obligations, while the absence of such a clause represents an institutional failure by the government agency that increases the moral burden on Engineer A's individual judgment without diminishing what that judgment ethically demands.

URI case-106#C20
conclusion uri case-106#C20
conclusion text In response to Q402, the presence of an explicit revolving-door clause in Engineer A's government employment contract would not strengthen her underlying ethical obligations under the NSPE Code — thos...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The Board weighed the legal and ethical dimensions of the revolving-door clause question separately, concluding that contractual provisions and professional ethical standards operate on parallel track...
resolution narrative The Board resolved Q402 by drawing a clear distinction between the legal and ethical planes: a revolving-door clause would strengthen enforceability and reduce rationalization risk but would not alter...
confidence 0.93
ResolutionPattern_21 individual committed

The board concluded that the switching-sides prohibition from BER Case 85-4 applies with full force in adversarial proceedings because the prohibition is structural rather than conduct-based - Engineer A's prior access to Company X's confidential submissions creates an irremediable conflict that cannot be neutralized by her claimed ignorance of the connection between her general expertise and that prior access, consistent with the principle that naivety does not exculpate.

URI case-106#C21
conclusion uri case-106#C21
conclusion text In response to Q403, if Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked to provide technical analysis drawing on her general...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 1 items
weighing process The board subordinated Engineer A's professional utility to Company Y entirely to the categorical bar imposed by the switching-sides prohibition, treating the appearance of impropriety as independentl...
resolution narrative The board concluded that the switching-sides prohibition from BER Case 85-4 applies with full force in adversarial proceedings because the prohibition is structural rather than conduct-based — Enginee...
confidence 0.92
ResolutionPattern_22 individual committed

The board concluded that the conditional permission to accept employment at Company Y does not survive when the recruitment is explicitly structured around exploiting Engineer A's confidential government access, because under those circumstances Engineer A would become a willing instrument of misappropriation regardless of whether she personally disclosed specific design details - and Company Y would bear independent ethical culpability under the NSPE Code for engineering the scheme.

URI case-106#C22
conclusion uri case-106#C22
conclusion text In response to Q404, if Company Y specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies — making competitive intelligence an explicit factor i...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the tension between Competitive Employment Freedom and confidentiality obligations by finding that when competitive intelligence is an explicit hiring motive, the employment transit...
resolution narrative The board concluded that the conditional permission to accept employment at Company Y does not survive when the recruitment is explicitly structured around exploiting Engineer A's confidential governm...
confidence 0.94
ResolutionPattern_23 individual committed

The board resolved the conflict between Competitive Employment Freedom and the Confidentiality Obligation by conditioning the former on strict compliance with the latter, establishing that Engineer A may accept employment at Company Y only within the space that remains after her confidentiality duties to Company X's regulatory submissions have been fully honored - a resolution that preserves employment freedom in form while substantially constraining it in substance.

URI case-106#C23
conclusion uri case-106#C23
conclusion text The Board resolved the tension between Competitive Employment Freedom and the Confidentiality Obligation toward Company X's regulatory submissions not by subordinating one principle to the other, but ...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board treated confidentiality not as a value to be balanced against employment freedom but as a hard ceiling that defines the outer boundary within which employment freedom may be exercised, givin...
resolution narrative The board resolved the conflict between Competitive Employment Freedom and the Confidentiality Obligation by conditioning the former on strict compliance with the latter, establishing that Engineer A ...
confidence 0.91
ResolutionPattern_24 individual committed

The board concluded that Engineer A's loyalty obligation to Company Y is materially curtailed by the content of what she knows from prior government access, and that genuine reconciliation of these two principles requires not merely an intent to withhold but active structural measures - including potential recusal - to ensure that the competitive intelligence value of her prior access is never operationalized even indirectly, a standard the board gestures at but does not fully specify.

URI case-106#C24
conclusion uri case-106#C24
conclusion text The interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves pa...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board resolved the collision between the faithful-agent duty and the loyalty obligation by treating the former as categorically prior and retrospective, leaving the latter operative only in the re...
resolution narrative The board concluded that Engineer A's loyalty obligation to Company Y is materially curtailed by the content of what she knows from prior government access, and that genuine reconciliation of these tw...
confidence 0.87
ResolutionPattern_25 individual committed

The board resolved the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity by declining to set a calendar-based expiration for Engineer A's confidentiality obligation and instead establishing a functional standard - the duty persists as long as the information retains competitive value - while noting that the absence of a formal institutional revolving-door policy does not diminish this obligation but merely shifts the entire burden of ongoing professional judgment onto Engineer A herself.

URI case-106#C25
conclusion uri case-106#C25
conclusion text The tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must a...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board implicitly prioritized Regulatory Submission Confidentiality Protection over Revolving Door Integrity by refusing to establish a fixed time limit and instead adopting a functional standard t...
resolution narrative The board resolved the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity by declining to set a calendar-based expiration for Engineer A's confidentiality obligation a...
confidence 0.89
Phase 3: Decision Points
6 6 committed
canonical decision point 6
Engineer A's decision whether to accept employment at Company Y given her prior government access to individual committed

Should Engineer A accept employment at Company Y, and if so, what obligations must she fulfill before accepting?

URI http://proethica.org/ontology/case-106#DP1
focus id DP1
focus number 1
description Engineer A's decision whether to accept employment at Company Y given her prior government access to Company X's confidential regulatory submissions, and what pre-employment obligations attach to that...
decision question Should Engineer A accept employment at Company Y, and if so, what obligations must she fulfill before accepting?
role uri http://proethica.org/ontology/case/106#Engineer_A_Post-Public-Service_Competitor_Employment_Conflict_Avoidance
role label Engineer A
obligation uri http://proethica.org/ontology/intermediate#Post-Public-ServiceCompetitorEmploymentConflictAvoidanceObligation
obligation label Post-Public-Service Competitor Employment Conflict Avoidance Obligation
constraint uri http://proethica.org/ontology/intermediate#CompetitiveEmploymentFreedomWithConfidentialityConstraint
constraint label Competitive Employment Freedom With Confidentiality Constraint
involved action uris 3 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.4", "III.4", "III.4.a"], "data_summary": "Engineer A worked for a government agency that received confidential and proprietary design information from Company X as part...
aligned question uri case-106#Q1
aligned question text What are Engineer A’s ethical obligations under these circumstances?
addresses questions 2 items
board resolution The Board concluded that Engineer A is free to accept employment at Company Y because the NSPE Code does not prohibit engineers from joining competitors, but only from weaponizing confidential informa...
options 3 items
intensity score 0.75
qc alignment score 0.85
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer A's decision whether to accept employment at Company Y given her prior government access to Company X's confidential regulatory submissions, and what pre-employment obligations attach to that...
llm refined question Should Engineer A accept employment at Company Y, and if so, what obligations must she fulfill before accepting?
Engineer A's ongoing obligation to withhold Company X's confidential design information during her t individual committed

Does Engineer A's confidentiality obligation require only passive non-disclosure of Company X's information, or does it also require proactive recusal from assignments at Company Y where her structural knowledge could - even subconsciously - inform her technical judgments?

URI http://proethica.org/ontology/case-106#DP2
focus id DP2
focus number 2
description Engineer A's ongoing obligation to withhold Company X's confidential design information during her tenure at Company Y, including whether passive non-disclosure is sufficient or whether proactive recu...
decision question Does Engineer A's confidentiality obligation require only passive non-disclosure of Company X's information, or does it also require proactive recusal from assignments at Company Y where her structura...
role uri http://proethica.org/ontology/case/106#Engineer_A_Post-Public-Employment_Confidential_Information_Non-Use_Company_X
role label Engineer A
obligation uri http://proethica.org/ontology/intermediate#Post-Public-EmploymentConfidentialInformationNon-UseObligation
obligation label Post-Public-Employment Confidential Information Non-Use Obligation
constraint uri http://proethica.org/ontology/intermediate#ConfidentialInformationMentalSegregationImpossibilityRecognitionCapability
constraint label Confidential Information Mental Segregation Impossibility Recognition Capability
involved action uris 3 items
provision uris 3 items
provision labels 2 items
toulmin {"backing_provisions": ["II.4", "III.4"], "data_summary": "Engineer A has accepted employment at Company Y and holds structural knowledge of Company X\u0027s confidential facility design...
aligned question uri case-106#Q1
aligned question text What are Engineer A’s ethical obligations under these circumstances?
addresses questions 2 items
board resolution The Board concluded that Engineer A must withhold Company X's confidential and proprietary design information throughout her tenure at Company Y. Extended analysis establishes that genuine compliance ...
options 3 items
intensity score 0.8
qc alignment score 0.82
source unified
source candidate ids 3 items
synthesis method algorithmic+llm
llm refined description Engineer A's ongoing obligation to withhold Company X's confidential design information during her tenure at Company Y, including whether passive non-disclosure is sufficient or whether proactive recu...
llm refined question Does Engineer A's confidentiality obligation require only passive non-disclosure of Company X's information, or does it also require proactive recusal from assignments at Company Y where her structura...
Whether Engineer A's disclosure obligation runs only to Company Y as the new employer, or also exten individual committed

Is Engineer A's pre-employment disclosure obligation satisfied by notifying Company Y alone, or does she also bear an obligation to notify Company X that its confidential design information is now held by an employee of a direct competitor?

URI http://proethica.org/ontology/case-106#DP3
focus id DP3
focus number 3
description Whether Engineer A's disclosure obligation runs only to Company Y as the new employer, or also extends to Company X as the party whose proprietary regulatory submissions are most directly at risk from...
decision question Should Engineer A disclose her conflict only to Company Y before accepting employment, or must she also notify Company X that its confidential regulatory submission data is now held by an employee of ...
role uri http://proethica.org/ontology/case/106#Engineer_A_Conflict_of_Interest_Disclosure_to_Company_Y_Regarding_Company_X_Access
role label Engineer A
obligation uri http://proethica.org/ontology/intermediate#ConflictofInterestDisclosuretoNewPrivateEmployerRegardingPriorGovernmentAccessObligation
obligation label Conflict of Interest Disclosure to New Private Employer Regarding Prior Government Access Obligation
constraint uri http://proethica.org/ontology/intermediate#FormerClientConfidentialityPerpetuationObligation
constraint label Former Client Confidentiality Perpetuation Obligation
involved action uris 3 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.4", "III.4", "III.4.a"], "data_summary": "Engineer A holds Company X\u0027s confidential regulatory submission data and is transitioning to Company Y, a direct...
aligned question uri case-106#Q1
aligned question text What are Engineer A’s ethical obligations under these circumstances?
addresses questions 2 items
board resolution The Board required disclosure to Company Y before accepting employment but was silent on any obligation to notify Company X. Extended analysis identifies this as a structural gap: the faithful-agent s...
options 3 items
intensity score 0.72
qc alignment score 0.78
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Whether Engineer A's disclosure obligation runs only to Company Y as the new employer, or also extends to Company X as the party whose proprietary regulatory submissions are most directly at risk from...
llm refined question Is Engineer A's pre-employment disclosure obligation satisfied by notifying Company Y alone, or does she also bear an obligation to notify Company X that its confidential design information is now hel...
The duration and expiration of Engineer A's confidentiality obligation toward Company X's regulatory individual committed

How should Engineer A assess the duration of her confidentiality obligation toward Company X's design information, and by what standard - if any - may she treat that obligation as having expired?

URI http://proethica.org/ontology/case-106#DP4
focus id DP4
focus number 4
description The duration and expiration of Engineer A's confidentiality obligation toward Company X's regulatory submissions, and what standard — if any — governs when that obligation may be treated as having lap...
decision question How should Engineer A assess the duration of her confidentiality obligation toward Company X's design information, and by what standard — if any — may she treat that obligation as having expired?
role uri http://proethica.org/ontology/case/106#Engineer_A_Former_Client_Duty_of_Trust_and_Loyalty_Duration_Assessment
role label Engineer A
obligation uri http://proethica.org/ontology/intermediate#Post-EmploymentDutyofTrustandLoyaltyDurationIndeterminacyConstraint
obligation label Post-Employment Duty of Trust and Loyalty Duration Indeterminacy Constraint
constraint uri http://proethica.org/ontology/intermediate#ConfidentialityDurationIndeterminacyPrinciple
constraint label Confidentiality Duration Indeterminacy Principle
involved action uris 3 items
provision uris 3 items
provision labels 2 items
toulmin {"backing_provisions": ["II.4", "III.4"], "data_summary": "Engineer A accumulated confidential and proprietary design information about Company X\u0027s facility designs during government...
aligned question uri case-106#Q4
aligned question text Given that the Board acknowledges the indeterminacy of the confidentiality obligation's duration, what mechanism or standard should govern when, if ever, Engineer A's duty to protect Company X's confi...
addresses questions 1 items
board resolution The Board acknowledged the indeterminacy of the confidentiality obligation's duration without establishing a governing standard. Extended analysis proposes a three-factor expiration standard: the obli...
options 3 items
intensity score 0.68
qc alignment score 0.76
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description The duration and expiration of Engineer A's confidentiality obligation toward Company X's regulatory submissions, and what standard — if any — governs when that obligation may be treated as having lap...
llm refined question How should Engineer A assess the duration of her confidentiality obligation toward Company X's design information, and by what standard — if any — may she treat that obligation as having expired?
Whether Engineer A's participation in any adversarial regulatory or legal proceeding at Company Y in individual committed

If Company X and Company Y become adversaries in a regulatory or legal proceeding, is Engineer A categorically barred from contributing technical analysis on Company Y's behalf - even analysis she characterizes as drawing only on general expertise - given her prior government access to Company X's confidential submissions?

URI http://proethica.org/ontology/case-106#DP5
focus id DP5
focus number 5
description Whether Engineer A's participation in any adversarial regulatory or legal proceeding at Company Y involving Company X is categorically barred by the switching-sides prohibition from BER Case 85-4, and...
decision question If Company X and Company Y become adversaries in a regulatory or legal proceeding, is Engineer A categorically barred from contributing technical analysis on Company Y's behalf — even analysis she cha...
role uri http://proethica.org/ontology/case/106#Engineer_A_Former_Regulatory_Access_Adversarial_Non-Participation_Company_X
role label Engineer A
obligation uri http://proethica.org/ontology/case/106#Former_Client_Adversarial_Participation_Prohibition_Invoked_By_Engineer_A_Company_X_Knowledge
obligation label Former Client Adversarial Participation Prohibition Invoked By Engineer A Company X Knowledge
constraint uri http://proethica.org/ontology/intermediate#ConfidentialInformationMentalSegregationImpossibilityRecognitionCapability
constraint label Confidential Information Mental Segregation Impossibility Recognition Capability
involved action uris 3 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.4", "III.4", "BER Case 85-4"], "data_summary": "Engineer A holds structural knowledge of Company X\u0027s confidential facility design submissions. Company Y is a...
aligned question uri case-106#Q1
aligned question text What are Engineer A’s ethical obligations under these circumstances?
addresses questions 2 items
board resolution The Board's extended analysis concluded that the switching-sides prohibition from BER Case 85-4 applies with full structural force if Company X and Company Y become adversaries in any regulatory or le...
options 3 items
intensity score 0.78
qc alignment score 0.74
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Whether Engineer A's participation in any adversarial regulatory or legal proceeding at Company Y involving Company X is categorically barred by the switching-sides prohibition from BER Case 85-4, and...
llm refined question If Company X and Company Y become adversaries in a regulatory or legal proceeding, is Engineer A categorically barred from contributing technical analysis on Company Y's behalf — even analysis she cha...
Whether the ethical permissibility of Engineer A's employment transition to Company Y is altered whe individual committed

Does the ethical permissibility of Engineer A accepting employment at Company Y depend on Company Y's hiring motivation - specifically, whether Company Y recruited Engineer A primarily for her general expertise or primarily for the competitive intelligence value of her government-acquired knowledge of Company X's design strategies?

URI http://proethica.org/ontology/case-106#DP6
focus id DP6
focus number 6
description Whether the ethical permissibility of Engineer A's employment transition to Company Y is altered when Company Y's hiring motivation is explicitly or primarily the competitive intelligence value of Eng...
decision question Does the ethical permissibility of Engineer A accepting employment at Company Y depend on Company Y's hiring motivation — specifically, whether Company Y recruited Engineer A primarily for her general...
role uri http://proethica.org/ontology/case/106#Revolving_Door_Integrity_Invoked_By_Engineer_A_Government-to-Private_Transition
role label Engineer A
obligation uri http://proethica.org/ontology/intermediate#Post-Public-ServiceCompetitorEmploymentConflictAvoidanceObligation
obligation label Post-Public-Service Competitor Employment Conflict Avoidance Obligation
constraint uri http://proethica.org/ontology/intermediate#RegulatorySubmissionConfidentialityProtectionObligation
constraint label Regulatory Submission Confidentiality Protection Obligation
involved action uris 3 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.4", "III.4", "III.4.a"], "data_summary": "Engineer A is offered a position at Company Y, a direct competitor of Company X. The Board\u0027s baseline conclusion permits...
aligned question uri case-106#Q1
aligned question text What are Engineer A’s ethical obligations under these circumstances?
addresses questions 2 items
board resolution The Board's extended analysis concluded that the conditional permission to accept employment at Company Y does not survive when Company Y's recruitment is explicitly structured around exploiting Engin...
options 3 items
intensity score 0.82
qc alignment score 0.72
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Whether the ethical permissibility of Engineer A's employment transition to Company Y is altered when Company Y's hiring motivation is explicitly or primarily the competitive intelligence value of Eng...
llm refined question Does the ethical permissibility of Engineer A accepting employment at Company Y depend on Company Y's hiring motivation — specifically, whether Company Y recruited Engineer A primarily for her general...

No narrative elements extracted yet.