PASS 3: Temporal Dynamics
Case 106: Confidentiality of Competitor Information Submitted to Government Agency
Timeline Overview
OWL-Time Temporal Structure 10 relations time: = w3.org/2006/time
Extracted Actions (7)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A voluntarily ends her employment with the government agency, a deliberate career decision that activates and crystallizes her post-employment ethical obligations regarding the confidential information she accumulated during her tenure.
Temporal Marker: End of government agency employment
Mental State: deliberate
Intended Outcome: Transition out of government employment, presumably to pursue better career opportunities in the private sector
Fulfills Obligations:
- Right to professional mobility and freedom of employment
Guided By Principles:
- Engineer's right to pursue professional advancement
- Faithful agency and trusteeship obligations that survive employment termination
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A is exercising her fundamental right to career mobility and self-determination, seeking better opportunities, higher compensation, greater professional challenge, or an exit from public sector constraints. Her motivation is personal and professional advancement—a universally recognized and legitimate aspiration.
Ethical Tension: The tension is between an individual engineer's right to pursue career opportunities freely (a foundational principle in a market economy and professional autonomy) and the lingering fiduciary-like duties owed to the public agency, the regulatory process, and the private companies whose confidential information she stewarded. Resignation is legal and normal, but it does not extinguish the obligations incurred during tenure.
Learning Significance: Teaches students that the end of an employment relationship does not terminate all ethical obligations arising from it. This is a critical and often underappreciated principle: confidentiality duties, in particular, are not employment-contingent but information-contingent. Students must understand that 'I no longer work there' is never a defense for disclosing information obtained in a position of trust.
Stakes: Engineer A's post-employment professional obligations crystallize at this moment; the regulatory agency loses a knowledgeable employee; the ethical clock starts ticking on how she will handle the confidential information she carries with her into the private sector.
Decision Point: Yes - Story can branch here
- Remain at the government agency, forgoing private sector opportunities to avoid the conflict entirely
- Resign but proactively seek formal legal or ethics counsel to document and clarify her post-employment obligations before accepting any new position
- Resign and enter a voluntary cooling-off period before joining any firm that operates in the sectors she regulated
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Resign_from_Government_Agency",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Remain at the government agency, forgoing private sector opportunities to avoid the conflict entirely",
"Resign but proactively seek formal legal or ethics counsel to document and clarify her post-employment obligations before accepting any new position",
"Resign and enter a voluntary cooling-off period before joining any firm that operates in the sectors she regulated"
],
"proeth-scenario:characterMotivation": "Engineer A is exercising her fundamental right to career mobility and self-determination, seeking better opportunities, higher compensation, greater professional challenge, or an exit from public sector constraints. Her motivation is personal and professional advancement\u2014a universally recognized and legitimate aspiration.",
"proeth-scenario:consequencesIfAlternative": [
"Remaining would eliminate the conflict but would represent a significant personal sacrifice of career freedom; it also sets an unreasonably high bar that could deter qualified engineers from entering public service",
"Seeking formal counsel proactively would represent best-practice ethical behavior, creating a documented record of good faith and clarifying the precise boundaries of her obligations\u2014a model outcome for ethics education",
"A voluntary cooling-off period would reduce (though not eliminate) the risk that her specific knowledge remains competitively relevant, and would signal good faith to former employers and the public, though it is not legally required and may be professionally costly"
],
"proeth-scenario:decisionSignificance": "Teaches students that the end of an employment relationship does not terminate all ethical obligations arising from it. This is a critical and often underappreciated principle: confidentiality duties, in particular, are not employment-contingent but information-contingent. Students must understand that \u0027I no longer work there\u0027 is never a defense for disclosing information obtained in a position of trust.",
"proeth-scenario:ethicalTension": "The tension is between an individual engineer\u0027s right to pursue career opportunities freely (a foundational principle in a market economy and professional autonomy) and the lingering fiduciary-like duties owed to the public agency, the regulatory process, and the private companies whose confidential information she stewarded. Resignation is legal and normal, but it does not extinguish the obligations incurred during tenure.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "Engineer A\u0027s post-employment professional obligations crystallize at this moment; the regulatory agency loses a knowledgeable employee; the ethical clock starts ticking on how she will handle the confidential information she carries with her into the private sector.",
"proeth:description": "Engineer A voluntarily ends her employment with the government agency, a deliberate career decision that activates and crystallizes her post-employment ethical obligations regarding the confidential information she accumulated during her tenure.",
"proeth:foreseenUnintendedEffects": [
"Triggering of ongoing confidentiality obligations regarding Company X\u0027s proprietary information",
"Creation of potential conflict-of-interest scenarios if she joins a competitor of any company whose information she reviewed",
"Separation from the institutional context that originally justified her access to confidential information"
],
"proeth:fulfillsObligation": [
"Right to professional mobility and freedom of employment"
],
"proeth:guidedByPrinciple": [
"Engineer\u0027s right to pursue professional advancement",
"Faithful agency and trusteeship obligations that survive employment termination"
],
"proeth:hasAgent": "Engineer A (departing Government Agency Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional freedom versus residual confidentiality obligations",
"proeth:resolutionReasoning": "The BER concludes that resignation and subsequent private employment are not inherently unethical; the ethical weight falls on what Engineer A does with the information she carries, not on the act of leaving government service itself"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Transition out of government employment, presumably to pursue better career opportunities in the private sector",
"proeth:requiresCapability": [
"Self-assessment of post-employment ethical obligations",
"Awareness of confidentiality duties that survive employment"
],
"proeth:temporalMarker": "End of government agency employment",
"proeth:withinCompetence": true,
"rdfs:label": "Resign from Government Agency"
}
Description: Engineer A makes the affirmative decision to accept an engineering position with Company Y, knowing it is a direct competitor of Company X, whose confidential and proprietary design information she accessed during her government tenure. This is the central ethical decision of the case.
Temporal Marker: Immediately following resignation from government agency
Mental State: deliberate
Intended Outcome: Advance her engineering career by joining a private-sector company in the same industry domain she gained expertise in through government work
Fulfills Obligations:
- Legitimate exercise of professional mobility rights
- Pursuit of career advancement consistent with engineering competence
Guided By Principles:
- Engineer's right to professional mobility
- Obligation to avoid circumstances that could appear to influence professional judgment
- Duty to serve as faithful agent and trustee to new employer without compromising obligations to former indirect clients
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A seeks to advance her career in a specialized technical field where Company Y likely offers superior compensation, more complex engineering challenges, or better growth prospects. Her motivation is legitimate professional ambition. She may also genuinely believe she can maintain the necessary ethical boundaries between her prior knowledge and her new role.
Ethical Tension: This is the case's central ethical crucible. The tension is multidimensional: Engineer A's right to employment in her field of expertise vs. Company X's right to protection of its confidential information; Company Y's interest in hiring the most qualified candidate vs. the integrity of the competitive marketplace; the BER's conclusion that the action is permissible vs. the intuitive discomfort many feel about the arrangement. The case forces students to distinguish between the mere possession of knowledge and its impermissible use.
Learning Significance: This is the primary teaching moment of the entire case. The BER's nuanced conclusion—that accepting the position is ethically permissible but disclosure is not—teaches students to resist binary thinking. Ethics often requires not a yes/no answer but a conditional one: 'yes, but only if.' Students learn to disaggregate the act of employment from the act of disclosure, and to understand that the ethical obligation lies in behavior within the new role, not in the career decision itself.
Stakes: Company X's competitive position and trade secrets; the fairness of the engineering marketplace; Engineer A's career and professional license; Company Y's potential liability if confidential information is improperly used; public confidence in the integrity of the regulatory system and the engineering profession.
Decision Point: Yes - Story can branch here
- Decline the position at Company Y specifically because of the conflict of interest, and seek employment at a non-competing firm
- Accept the position but immediately and proactively disclose the conflict to both Company Y's leadership and the former government agency, establishing formal information barriers
- Accept the position conditionally, negotiating a formal agreement with Company Y that she will not be assigned to projects where Company X's confidential design information would be relevant or advantageous
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Accept_Position_at_Competitor",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the position at Company Y specifically because of the conflict of interest, and seek employment at a non-competing firm",
"Accept the position but immediately and proactively disclose the conflict to both Company Y\u0027s leadership and the former government agency, establishing formal information barriers",
"Accept the position conditionally, negotiating a formal agreement with Company Y that she will not be assigned to projects where Company X\u0027s confidential design information would be relevant or advantageous"
],
"proeth-scenario:characterMotivation": "Engineer A seeks to advance her career in a specialized technical field where Company Y likely offers superior compensation, more complex engineering challenges, or better growth prospects. Her motivation is legitimate professional ambition. She may also genuinely believe she can maintain the necessary ethical boundaries between her prior knowledge and her new role.",
"proeth-scenario:consequencesIfAlternative": [
"Declining would be the most conservative choice and would eliminate all risk, but the BER explicitly holds this is not required\u2014making this alternative a useful discussion point about the difference between what ethics requires and what ethics permits",
"Proactive disclosure and formal information barriers (a \u0027screen\u0027 or \u0027ethical wall\u0027) would represent a gold-standard approach that exceeds minimum ethical requirements and could serve as a model for institutional best practices in managing post-government employment conflicts",
"Negotiating a scoped role would be a practical middle path that attempts to operationalize the ethical obligation structurally, though it raises questions about enforceability and whether Company Y would agree to such constraints"
],
"proeth-scenario:decisionSignificance": "This is the primary teaching moment of the entire case. The BER\u0027s nuanced conclusion\u2014that accepting the position is ethically permissible but disclosure is not\u2014teaches students to resist binary thinking. Ethics often requires not a yes/no answer but a conditional one: \u0027yes, but only if.\u0027 Students learn to disaggregate the act of employment from the act of disclosure, and to understand that the ethical obligation lies in behavior within the new role, not in the career decision itself.",
"proeth-scenario:ethicalTension": "This is the case\u0027s central ethical crucible. The tension is multidimensional: Engineer A\u0027s right to employment in her field of expertise vs. Company X\u0027s right to protection of its confidential information; Company Y\u0027s interest in hiring the most qualified candidate vs. the integrity of the competitive marketplace; the BER\u0027s conclusion that the action is permissible vs. the intuitive discomfort many feel about the arrangement. The case forces students to distinguish between the mere possession of knowledge and its impermissible use.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "Company X\u0027s competitive position and trade secrets; the fairness of the engineering marketplace; Engineer A\u0027s career and professional license; Company Y\u0027s potential liability if confidential information is improperly used; public confidence in the integrity of the regulatory system and the engineering profession.",
"proeth:description": "Engineer A makes the affirmative decision to accept an engineering position with Company Y, knowing it is a direct competitor of Company X, whose confidential and proprietary design information she accessed during her government tenure. This is the central ethical decision of the case.",
"proeth:foreseenUnintendedEffects": [
"Placing herself in a position where she holds competitively valuable information about Company Y\u0027s direct competitor",
"Creating ongoing tension between her duty to her new employer and her residual confidentiality obligations to Company X",
"Potential appearance of impropriety or conflict of interest regardless of her actual conduct"
],
"proeth:fulfillsObligation": [
"Legitimate exercise of professional mobility rights",
"Pursuit of career advancement consistent with engineering competence"
],
"proeth:guidedByPrinciple": [
"Engineer\u0027s right to professional mobility",
"Obligation to avoid circumstances that could appear to influence professional judgment",
"Duty to serve as faithful agent and trustee to new employer without compromising obligations to former indirect clients"
],
"proeth:hasAgent": "Engineer A (newly hired Engineer at Company Y)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional freedom and career advancement versus protection of Company X\u0027s confidential information and avoidance of conflict of interest appearance",
"proeth:resolutionReasoning": "The BER resolves the conflict by permitting the employment decision while imposing a strict ongoing non-disclosure obligation, rejecting the more restrictive position that prior access to a competitor\u0027s information should bar employment entirely; this balances professional mobility against confidentiality protection"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Advance her engineering career by joining a private-sector company in the same industry domain she gained expertise in through government work",
"proeth:requiresCapability": [
"Ability to perform engineering work at Company Y without drawing on Company X\u0027s confidential information",
"Ethical self-regulation and ongoing judgment about what information may or may not be disclosed",
"Awareness of the boundary between general expertise developed through government work and specific confidential knowledge about Company X"
],
"proeth:temporalMarker": "Immediately following resignation from government agency",
"proeth:withinCompetence": true,
"rdfs:label": "Accept Position at Competitor"
}
Description: Engineer A must make continuous, ongoing decisions throughout her employment at Company Y not to disclose the confidential and proprietary design information she learned about Company X during her government tenure. This is framed by the BER as the primary and non-negotiable ethical obligation arising from the case.
Temporal Marker: Ongoing throughout employment at Company Y and potentially indefinitely thereafter
Mental State: deliberate
Intended Outcome: Honor residual confidentiality obligations to Company X while fulfilling duties to new employer Company Y, maintaining professional integrity and compliance with NSPE Code
Fulfills Obligations:
- NSPE Code obligation not to disclose confidential information about former clients or employers without consent
- Duty to serve as faithful agent and trustee respecting the trust placed in her by Company X through the regulatory process
- Obligation to avoid conduct that could appear to improperly influence professional judgment
Guided By Principles:
- Confidentiality as a foundational engineering ethical obligation
- Faithful agency and trusteeship to former indirect clients
- Avoidance of conflicts of interest and their appearance
- Integrity and honesty in professional conduct
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A is motivated by her internalized professional ethics, her awareness of the BER's guidance, and potentially by legal exposure under trade secret law. She may also be motivated by personal integrity—a genuine commitment to honoring the trust placed in her during her government tenure. Importantly, this is not a single decision but a continuous pattern of restraint across her entire tenure at Company Y.
Ethical Tension: The ongoing tension is between Engineer A's duty to be a maximally effective and competitive employee for Company Y (which might be served by leveraging her unique knowledge of competitors) and her absolute, non-negotiable duty to protect Company X's confidential information. There is also an internal tension between what she knows and what she is permitted to act upon—a psychologically demanding form of professional compartmentalization.
Learning Significance: Teaches students that ethical compliance in confidentiality contexts is not a one-time decision but a continuous, active practice requiring ongoing vigilance. This challenges the common misconception that ethics is only about dramatic decision moments. Students also learn about the concept of 'use prohibition'—that confidential information cannot be used even when not literally 'disclosed' to others, and that the obligation persists indefinitely regardless of how much time passes.
Stakes: Company X's trade secrets and competitive position; Engineer A's professional license and reputation; Company Y's legal liability for misappropriation of trade secrets; the integrity of the engineering profession's self-regulatory framework; potential civil and criminal liability under trade secret law.
Decision Point: Yes - Story can branch here
- Disclose Company X's confidential design information to Company Y colleagues, rationalizing that her knowledge is now part of her general professional expertise
- Passively allow Company X's confidential information to influence her design decisions at Company Y without explicitly sharing it, reasoning that she is not technically 'disclosing' anything
- Proactively recuse herself from any Company Y project where her knowledge of Company X's designs could provide an unfair advantage, and document this recusal formally
Narrative Role: resolution
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Withhold_Company_X_Confidential_Information",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Disclose Company X\u0027s confidential design information to Company Y colleagues, rationalizing that her knowledge is now part of her general professional expertise",
"Passively allow Company X\u0027s confidential information to influence her design decisions at Company Y without explicitly sharing it, reasoning that she is not technically \u0027disclosing\u0027 anything",
"Proactively recuse herself from any Company Y project where her knowledge of Company X\u0027s designs could provide an unfair advantage, and document this recusal formally"
],
"proeth-scenario:characterMotivation": "Engineer A is motivated by her internalized professional ethics, her awareness of the BER\u0027s guidance, and potentially by legal exposure under trade secret law. She may also be motivated by personal integrity\u2014a genuine commitment to honoring the trust placed in her during her government tenure. Importantly, this is not a single decision but a continuous pattern of restraint across her entire tenure at Company Y.",
"proeth-scenario:consequencesIfAlternative": [
"Active disclosure would be a clear and serious ethical violation, likely constituting trade secret misappropriation, grounds for license revocation, civil liability for both Engineer A and Company Y, and a fundamental breach of the public trust that underlies the regulatory system",
"Passive use without explicit disclosure is a subtler but equally serious violation\u2014this alternative is pedagogically valuable precisely because it illustrates that the ethical prohibition covers use as well as disclosure, and that self-deception about the distinction is a common failure mode",
"Proactive recusal and documentation represents the highest standard of ethical practice, going beyond what is minimally required to create structural safeguards against inadvertent violation\u2014an exemplary model for students to consider adopting in their own careers"
],
"proeth-scenario:decisionSignificance": "Teaches students that ethical compliance in confidentiality contexts is not a one-time decision but a continuous, active practice requiring ongoing vigilance. This challenges the common misconception that ethics is only about dramatic decision moments. Students also learn about the concept of \u0027use prohibition\u0027\u2014that confidential information cannot be used even when not literally \u0027disclosed\u0027 to others, and that the obligation persists indefinitely regardless of how much time passes.",
"proeth-scenario:ethicalTension": "The ongoing tension is between Engineer A\u0027s duty to be a maximally effective and competitive employee for Company Y (which might be served by leveraging her unique knowledge of competitors) and her absolute, non-negotiable duty to protect Company X\u0027s confidential information. There is also an internal tension between what she knows and what she is permitted to act upon\u2014a psychologically demanding form of professional compartmentalization.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "resolution",
"proeth-scenario:stakes": "Company X\u0027s trade secrets and competitive position; Engineer A\u0027s professional license and reputation; Company Y\u0027s legal liability for misappropriation of trade secrets; the integrity of the engineering profession\u0027s self-regulatory framework; potential civil and criminal liability under trade secret law.",
"proeth:description": "Engineer A must make continuous, ongoing decisions throughout her employment at Company Y not to disclose the confidential and proprietary design information she learned about Company X during her government tenure. This is framed by the BER as the primary and non-negotiable ethical obligation arising from the case.",
"proeth:foreseenUnintendedEffects": [
"Potential limitation on the full scope of contributions Engineer A can make to Company Y",
"Ongoing cognitive and professional burden of self-monitoring knowledge boundaries",
"Possible disadvantage to Company Y if Engineer A must recuse herself from certain competitive analyses"
],
"proeth:fulfillsObligation": [
"NSPE Code obligation not to disclose confidential information about former clients or employers without consent",
"Duty to serve as faithful agent and trustee respecting the trust placed in her by Company X through the regulatory process",
"Obligation to avoid conduct that could appear to improperly influence professional judgment"
],
"proeth:guidedByPrinciple": [
"Confidentiality as a foundational engineering ethical obligation",
"Faithful agency and trusteeship to former indirect clients",
"Avoidance of conflicts of interest and their appearance",
"Integrity and honesty in professional conduct"
],
"proeth:hasAgent": "Engineer A (Engineer at Company Y)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Duty of full service to current employer versus absolute confidentiality obligation to former indirect client",
"proeth:resolutionReasoning": "The BER resolves unambiguously in favor of non-disclosure as the primary obligation, framing it as the condition under which the employment itself is ethically permissible; there is no balancing \u2014 confidentiality is the non-negotiable constraint, and Engineer A\u0027s utility to Company Y must operate within that boundary"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Honor residual confidentiality obligations to Company X while fulfilling duties to new employer Company Y, maintaining professional integrity and compliance with NSPE Code",
"proeth:requiresCapability": [
"Ethical self-regulation and ongoing professional judgment",
"Ability to distinguish between general industry expertise and specific confidential knowledge about Company X",
"Capacity to recuse or limit involvement in matters where Company X\u0027s confidential information would be materially relevant"
],
"proeth:temporalMarker": "Ongoing throughout employment at Company Y and potentially indefinitely thereafter",
"proeth:violatesObligation": [
"Potential partial limitation of full faithful agency to new employer Company Y if withholding creates gaps in her contributions"
],
"proeth:withinCompetence": true,
"rdfs:label": "Withhold Company X Confidential Information"
}
Description: In the historical reference case BER 82-6, an engineer retained by the US government to study a dam failure accepted a subsequent retention by the contractor who had filed a claim against the government for additional compensation. The BER deemed this decision unethical.
Temporal Marker: Historical reference case, cited in discussion section
Mental State: deliberate
Intended Outcome: Accept new professional engagement with the contractor, presumably for compensation and professional work, without apparent recognition that it directly conflicted with obligations to the former government client
Guided By Principles:
- Faithful agency and trusteeship
- Avoidance of conflicts of interest
- Confidentiality of former client information
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: The engineer in BER 82-6 was likely motivated by financial opportunity, professional interest in a complex technical case, or a belief that his expertise was genuinely valuable to both parties at different stages. He may have rationalized that his initial work for the government was complete and that his subsequent engagement was independent and separate.
Ethical Tension: The tension is between the engineer's economic self-interest and professional opportunity on one side, and the duty of loyalty, impartiality, and conflict-of-interest avoidance on the other. There is also a tension between the engineer's subjective belief in his own objectivity and the objective appearance of impropriety that arises from switching sides in an adversarial proceeding.
Learning Significance: This reference case teaches students about the 'switching sides' problem in forensic and expert engineering contexts. It establishes that prior engagement with one party in a dispute creates obligations that survive the formal end of that engagement. Students learn that the appearance of impartiality is as professionally important as actual impartiality, and that financial opportunity does not justify compromising the integrity of an adversarial process.
Stakes: The integrity of the dam failure investigation; the fairness of the government's legal position; the contractor's right to a fair claims process; the credibility of engineering expert testimony; the engineer's professional reputation and license.
Decision Point: Yes - Story can branch here
- Decline the contractor's retention entirely, citing the irreconcilable conflict created by his prior work for the government
- Disclose his prior government engagement to the contractor and allow the contractor to make an informed decision about whether to retain him with full knowledge of the conflict
- Seek an ethics opinion or legal counsel before accepting the retention to determine whether the conflict was waivable
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Accept_Retention_by_Opposing_Party__BER_82-6_",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the contractor\u0027s retention entirely, citing the irreconcilable conflict created by his prior work for the government",
"Disclose his prior government engagement to the contractor and allow the contractor to make an informed decision about whether to retain him with full knowledge of the conflict",
"Seek an ethics opinion or legal counsel before accepting the retention to determine whether the conflict was waivable"
],
"proeth-scenario:characterMotivation": "The engineer in BER 82-6 was likely motivated by financial opportunity, professional interest in a complex technical case, or a belief that his expertise was genuinely valuable to both parties at different stages. He may have rationalized that his initial work for the government was complete and that his subsequent engagement was independent and separate.",
"proeth-scenario:consequencesIfAlternative": [
"Declining would be the ethically correct outcome per the BER\u0027s analysis\u2014it would preserve the integrity of both his prior work and the adversarial process, at the cost of the financial opportunity",
"Disclosure alone would be insufficient if the conflict is non-waivable, but it would at least demonstrate good faith; the BER\u0027s analysis suggests that even with disclosure, the conflict in this case was too fundamental to be waived",
"Seeking prior counsel would represent best-practice ethical behavior and might have led him to the correct conclusion before creating the violation\u2014a valuable lesson about proactive ethics consultation"
],
"proeth-scenario:decisionSignificance": "This reference case teaches students about the \u0027switching sides\u0027 problem in forensic and expert engineering contexts. It establishes that prior engagement with one party in a dispute creates obligations that survive the formal end of that engagement. Students learn that the appearance of impartiality is as professionally important as actual impartiality, and that financial opportunity does not justify compromising the integrity of an adversarial process.",
"proeth-scenario:ethicalTension": "The tension is between the engineer\u0027s economic self-interest and professional opportunity on one side, and the duty of loyalty, impartiality, and conflict-of-interest avoidance on the other. There is also a tension between the engineer\u0027s subjective belief in his own objectivity and the objective appearance of impropriety that arises from switching sides in an adversarial proceeding.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "The integrity of the dam failure investigation; the fairness of the government\u0027s legal position; the contractor\u0027s right to a fair claims process; the credibility of engineering expert testimony; the engineer\u0027s professional reputation and license.",
"proeth:description": "In the historical reference case BER 82-6, an engineer retained by the US government to study a dam failure accepted a subsequent retention by the contractor who had filed a claim against the government for additional compensation. The BER deemed this decision unethical.",
"proeth:foreseenUnintendedEffects": [
"Direct conflict between knowledge and duties gained from government engagement and obligations to new contractor client",
"Exploitation of confidential information and access gained through government retention to benefit an adverse party"
],
"proeth:guidedByPrinciple": [
"Faithful agency and trusteeship",
"Avoidance of conflicts of interest",
"Confidentiality of former client information"
],
"proeth:hasAgent": "Engineer (unnamed, BER Case 82-6 reference)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional opportunity versus loyalty and confidentiality obligations to former client",
"proeth:resolutionReasoning": "BER resolves unambiguously against the engineer, establishing that prior client loyalty and the absence of consent override the engineer\u0027s interest in new employment; this case is cited as precedent for the principle that post-engagement obligations are real and enforceable"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Accept new professional engagement with the contractor, presumably for compensation and professional work, without apparent recognition that it directly conflicted with obligations to the former government client",
"proeth:requiresCapability": [
"Recognition of conflict of interest arising from sequential adverse engagements",
"Ethical judgment to decline engagements that compromise former client obligations"
],
"proeth:temporalMarker": "Historical reference case, cited in discussion section",
"proeth:violatesObligation": [
"NSPE Code Section III.4.b \u2014 obligation not to accept employment adverse to former client without consent",
"Duty of faithful agency and trusteeship to former government client",
"Obligation to avoid conflicts of interest arising from prior professional relationships"
],
"proeth:withinCompetence": true,
"rdfs:label": "Accept Retention by Opposing Party (BER 82-6)"
}
Description: In the historical reference case BER 85-4, the forensic engineer decided he could not provide an engineering and safety analysis report favorable to the plaintiff after completing his review and analysis, because the results indicated the plaintiff rather than the defendant was at fault.
Temporal Marker: Historical reference case, during first engagement with plaintiff's attorney
Mental State: deliberate
Intended Outcome: Maintain professional integrity and honesty by refusing to produce a report whose conclusions would misrepresent his engineering findings
Fulfills Obligations:
- Obligation to provide honest and objective engineering analysis
- Duty not to misrepresent engineering findings
- Integrity in professional conduct
Guided By Principles:
- Honesty and objectivity in engineering analysis
- Professional integrity
- Faithful agency to client within bounds of ethical conduct
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: The forensic engineer in BER 85-4 was motivated by professional integrity and honest technical analysis. Having completed his review, his findings pointed to the plaintiff's fault rather than the defendant's—and he correctly recognized that he could not in good conscience produce a report contradicting his own technical conclusions simply because it would benefit his client.
Ethical Tension: The tension is between the engineer's duty to his client (the plaintiff's attorney, who retained him expecting a favorable report) and his overriding duty to technical honesty and objectivity. There is also a tension between financial self-interest (completing the engagement and being paid) and professional integrity (refusing to produce a misleading or dishonest report).
Learning Significance: This action is a positive ethical exemplar within an otherwise cautionary case. It teaches students that forensic and expert engineers owe their primary duty to technical truth, not to the party that retained them. Students learn the critical distinction between advocacy (the attorney's role) and objective analysis (the engineer's role), and that an engineer must be willing to deliver findings that are adverse to the retaining party when the evidence compels it.
Stakes: The integrity of the forensic engineering process; the fairness of the legal proceeding; the plaintiff's and defendant's right to accurate technical analysis; the engineer's professional credibility; public confidence in engineering expert testimony.
Decision Point: Yes - Story can branch here
- Produce a report favorable to the plaintiff despite his findings, through selective omission, framing, or distortion of the technical evidence
- Withdraw from the engagement without explanation, neither producing a report nor disclosing his findings to the plaintiff's attorney
- Disclose his findings to the plaintiff's attorney and offer to produce an honest report reflecting those findings, allowing the attorney to decide whether to use it
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Decline_Favorable_Plaintiff_Report__BER_85-4_",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Produce a report favorable to the plaintiff despite his findings, through selective omission, framing, or distortion of the technical evidence",
"Withdraw from the engagement without explanation, neither producing a report nor disclosing his findings to the plaintiff\u0027s attorney",
"Disclose his findings to the plaintiff\u0027s attorney and offer to produce an honest report reflecting those findings, allowing the attorney to decide whether to use it"
],
"proeth-scenario:characterMotivation": "The forensic engineer in BER 85-4 was motivated by professional integrity and honest technical analysis. Having completed his review, his findings pointed to the plaintiff\u0027s fault rather than the defendant\u0027s\u2014and he correctly recognized that he could not in good conscience produce a report contradicting his own technical conclusions simply because it would benefit his client.",
"proeth-scenario:consequencesIfAlternative": [
"Producing a dishonest favorable report would constitute a serious ethical violation, potentially fraud, and could expose the engineer to license revocation, civil liability, and criminal charges\u2014as well as causing direct harm to the defendant and the justice system",
"Silent withdrawal might avoid producing a dishonest report but would be professionally ambiguous and potentially problematic if the attorney then retained another expert without knowing the technical findings; it also fails the standard of transparent professional communication",
"Disclosing findings honestly and offering to produce an accurate report is actually the best-practice approach\u2014it respects the attorney-client relationship while maintaining engineering integrity, and it is what the engineer appears to have done before being terminated, making this the ethically correct path"
],
"proeth-scenario:decisionSignificance": "This action is a positive ethical exemplar within an otherwise cautionary case. It teaches students that forensic and expert engineers owe their primary duty to technical truth, not to the party that retained them. Students learn the critical distinction between advocacy (the attorney\u0027s role) and objective analysis (the engineer\u0027s role), and that an engineer must be willing to deliver findings that are adverse to the retaining party when the evidence compels it.",
"proeth-scenario:ethicalTension": "The tension is between the engineer\u0027s duty to his client (the plaintiff\u0027s attorney, who retained him expecting a favorable report) and his overriding duty to technical honesty and objectivity. There is also a tension between financial self-interest (completing the engagement and being paid) and professional integrity (refusing to produce a misleading or dishonest report).",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "The integrity of the forensic engineering process; the fairness of the legal proceeding; the plaintiff\u0027s and defendant\u0027s right to accurate technical analysis; the engineer\u0027s professional credibility; public confidence in engineering expert testimony.",
"proeth:description": "In the historical reference case BER 85-4, the forensic engineer decided he could not provide an engineering and safety analysis report favorable to the plaintiff after completing his review and analysis, because the results indicated the plaintiff rather than the defendant was at fault.",
"proeth:foreseenUnintendedEffects": [
"Termination of the engagement with plaintiff\u0027s attorney",
"Creation of a situation where his knowledge of the case and its findings could be exploited by adverse parties",
"Exposure of the plaintiff\u0027s litigation strategy and weaknesses through his subsequent availability"
],
"proeth:fulfillsObligation": [
"Obligation to provide honest and objective engineering analysis",
"Duty not to misrepresent engineering findings",
"Integrity in professional conduct"
],
"proeth:guidedByPrinciple": [
"Honesty and objectivity in engineering analysis",
"Professional integrity",
"Faithful agency to client within bounds of ethical conduct"
],
"proeth:hasAgent": "Engineer A (forensic engineer, BER Case 85-4 reference)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client service and retention of engagement versus professional honesty and integrity",
"proeth:resolutionReasoning": "Engineer correctly resolves in favor of honesty; the BER affirms this decision but notes that the subsequent decision to accept retention by the opposing party was the ethical failure, not this initial refusal"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Maintain professional integrity and honesty by refusing to produce a report whose conclusions would misrepresent his engineering findings",
"proeth:requiresCapability": [
"Engineering and safety analysis expertise",
"Professional judgment to recognize when findings cannot support client\u0027s position",
"Ethical courage to decline producing a misleading report"
],
"proeth:temporalMarker": "Historical reference case, during first engagement with plaintiff\u0027s attorney",
"proeth:withinCompetence": true,
"rdfs:label": "Decline Favorable Plaintiff Report (BER 85-4)"
}
Description: In the historical reference case BER 85-4, after being terminated by the plaintiff's attorney, the forensic engineer agreed to provide a separate and independent engineering and safety analysis report for the defendant's attorney in the same case. The BER deemed this decision unethical.
Temporal Marker: Historical reference case, following termination of first engagement
Mental State: deliberate
Intended Outcome: Accept a new professional engagement to provide an engineering report for the defendant, framed as a separate and independent analysis
Guided By Principles:
- Faithful agency and trusteeship to former client
- Confidentiality of information gained in professional relationships
- Avoidance of conflicts of interest and their appearance
- Honesty about the limits of one's ability to provide independent analysis given prior involvement
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: After being terminated by the plaintiff's attorney (presumably because his findings were unfavorable to the plaintiff), the forensic engineer was motivated by a combination of financial interest in completing paid work, a belief that his analysis was valid and deserved to be used, and possibly a rationalization that since he had already done the work and reached honest conclusions, providing them to the defendant's attorney was merely allowing truth to prevail.
Ethical Tension: The tension is between the engineer's genuine technical findings (which happened to favor the defendant) and the structural integrity of the adversarial legal process, which depends on experts maintaining loyalty to their retaining party through the proceeding. There is also a tension between the engineer's self-interest in being compensated for completed work and his duty to avoid conflicts of interest. Most acutely, there is a tension between 'my findings are honest, therefore using them is ethical' and 'the process by which I came to be in this position is itself ethically compromised.'
Learning Significance: This is the case's most pedagogically rich cautionary moment. The BER's finding of unethicality despite the engineer's honest findings teaches students the crucial lesson that procedural integrity and substantive correctness are both necessary—neither alone is sufficient. Students learn that 'switching sides' in litigation is unethical even when the engineer believes (and may be correct) that his analysis is objective. The case also teaches about the appearance of impropriety and the systemic harms that result when experts are perceived as available to the highest bidder.
Stakes: The integrity of the adversarial legal system; the defendant's and plaintiff's right to a fair proceeding with unconflicted experts; the credibility of forensic engineering as a profession; the engineer's license and reputation; the precedent set for how engineering experts navigate litigation conflicts.
Decision Point: Yes - Story can branch here
- Decline the defendant's attorney's retention entirely, recognizing that his prior engagement by the opposing party creates an irreconcilable conflict regardless of his findings
- Accept the defendant's retention only after full disclosure to both attorneys and the court, allowing a judicial determination of whether the conflict is waivable in the interests of justice
- Withdraw entirely from the case in all capacities, making his findings available to neither party, and document his reasoning for future reference
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Accept_Retention_by_Defendant_s_Attorney__BER_85-4",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the defendant\u0027s attorney\u0027s retention entirely, recognizing that his prior engagement by the opposing party creates an irreconcilable conflict regardless of his findings",
"Accept the defendant\u0027s retention only after full disclosure to both attorneys and the court, allowing a judicial determination of whether the conflict is waivable in the interests of justice",
"Withdraw entirely from the case in all capacities, making his findings available to neither party, and document his reasoning for future reference"
],
"proeth-scenario:characterMotivation": "After being terminated by the plaintiff\u0027s attorney (presumably because his findings were unfavorable to the plaintiff), the forensic engineer was motivated by a combination of financial interest in completing paid work, a belief that his analysis was valid and deserved to be used, and possibly a rationalization that since he had already done the work and reached honest conclusions, providing them to the defendant\u0027s attorney was merely allowing truth to prevail.",
"proeth-scenario:consequencesIfAlternative": [
"Declining the defendant\u0027s retention would be the ethically correct outcome per the BER\u2014it would preserve the integrity of the adversarial process and the engineer\u0027s professional standing, even though his honest findings would go unused in this proceeding",
"Full disclosure to both parties and the court introduces a transparency mechanism that might, in some jurisdictions and circumstances, allow a court to make an informed decision about whether to permit the testimony\u2014a nuanced alternative that acknowledges the complexity of the situation without simply ignoring the conflict",
"Complete withdrawal with documentation would protect the engineer\u0027s integrity and avoid the conflict, though it raises questions about whether his findings should somehow reach the court through other means\u2014a discussion point about the limits of individual ethical action within a systemic context"
],
"proeth-scenario:decisionSignificance": "This is the case\u0027s most pedagogically rich cautionary moment. The BER\u0027s finding of unethicality despite the engineer\u0027s honest findings teaches students the crucial lesson that procedural integrity and substantive correctness are both necessary\u2014neither alone is sufficient. Students learn that \u0027switching sides\u0027 in litigation is unethical even when the engineer believes (and may be correct) that his analysis is objective. The case also teaches about the appearance of impropriety and the systemic harms that result when experts are perceived as available to the highest bidder.",
"proeth-scenario:ethicalTension": "The tension is between the engineer\u0027s genuine technical findings (which happened to favor the defendant) and the structural integrity of the adversarial legal process, which depends on experts maintaining loyalty to their retaining party through the proceeding. There is also a tension between the engineer\u0027s self-interest in being compensated for completed work and his duty to avoid conflicts of interest. Most acutely, there is a tension between \u0027my findings are honest, therefore using them is ethical\u0027 and \u0027the process by which I came to be in this position is itself ethically compromised.\u0027",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "The integrity of the adversarial legal system; the defendant\u0027s and plaintiff\u0027s right to a fair proceeding with unconflicted experts; the credibility of forensic engineering as a profession; the engineer\u0027s license and reputation; the precedent set for how engineering experts navigate litigation conflicts.",
"proeth:description": "In the historical reference case BER 85-4, after being terminated by the plaintiff\u0027s attorney, the forensic engineer agreed to provide a separate and independent engineering and safety analysis report for the defendant\u0027s attorney in the same case. The BER deemed this decision unethical.",
"proeth:foreseenUnintendedEffects": [
"Exploitation of confidential information and case knowledge gained during the plaintiff engagement",
"Effective use of the plaintiff\u0027s litigation vulnerability (revealed by his inability to provide a favorable report) to benefit the opposing party",
"Violation of residual confidentiality and loyalty obligations to the plaintiff\u0027s attorney as former client"
],
"proeth:guidedByPrinciple": [
"Faithful agency and trusteeship to former client",
"Confidentiality of information gained in professional relationships",
"Avoidance of conflicts of interest and their appearance",
"Honesty about the limits of one\u0027s ability to provide independent analysis given prior involvement"
],
"proeth:hasAgent": "Engineer A (forensic engineer, BER Case 85-4 reference)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional opportunity and freedom to accept new engagements versus residual confidentiality and loyalty to former client",
"proeth:resolutionReasoning": "BER resolves unambiguously against acceptance, establishing that the engineer should have recognized both the ethical violation and the real motivation behind the defendant attorney\u0027s retention; the BER further holds that the engineer should have fully discussed the issue with the former client rather than accepting the new engagement, reinforcing that residual obligations require active management, not passive avoidance"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Accept a new professional engagement to provide an engineering report for the defendant, framed as a separate and independent analysis",
"proeth:requiresCapability": [
"Recognition of conflict of interest arising from sequential adverse engagements in the same matter",
"Ethical judgment to decline engagements that exploit former client\u0027s confidential information",
"Ability to recognize when claimed independence is not credible given prior involvement"
],
"proeth:temporalMarker": "Historical reference case, following termination of first engagement",
"proeth:violatesObligation": [
"NSPE Code Section II.4.b \u2014 obligation to avoid conflicts of interest",
"Residual confidentiality obligation to former client (plaintiff\u0027s attorney)",
"Duty not to exploit information gained in confidence during prior engagement",
"Obligation to avoid circumstances that could appear to improperly influence professional judgment",
"Duty to fully discuss the ethical conflict with the former client before proceeding"
],
"proeth:withinCompetence": true,
"rdfs:label": "Accept Retention by Defendant\u0027s Attorney (BER 85-4)"
}
Description: Engineer A actively receives and handles confidential and proprietary design information submitted by Company X and other companies during her tenure at the government agency. This represents an ongoing, role-sanctioned decision to engage with sensitive third-party information in her official regulatory capacity.
Temporal Marker: During tenure at government agency
Mental State: deliberate
Intended Outcome: Fulfill official regulatory duties by reviewing and processing company design submissions for facility approval
Fulfills Obligations:
- Duty to perform official government agency responsibilities
- Duty to serve as faithful agent and trustee to the regulatory body
- Duty to facilitate fair regulatory review of all submitting companies
Guided By Principles:
- Faithful agency and trusteeship
- Public interest and fair regulatory process
- Confidentiality of client and employer information
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A is fulfilling her legitimate, role-sanctioned regulatory duties at the government agency, reviewing facility design submissions as part of the approval process. Her motivation is professional competence and public service, not personal gain—yet her access to sensitive third-party IP is an unavoidable structural feature of the role.
Ethical Tension: The tension exists between effective regulatory oversight (which requires deep access to proprietary technical information) and the intellectual property rights and competitive interests of the companies submitting that information. The engineer's duty to the public interest through rigorous review conflicts with the implicit confidentiality expectations of the submitting companies.
Learning Significance: Teaches students that ethical obligations can be incurred passively through role-based access, not only through active wrongdoing. Engineers in regulatory, governmental, or quasi-judicial positions must recognize that privileged access to third-party information creates durable confidentiality duties that survive the role itself. This challenges the assumption that 'doing your job' is ethically neutral.
Stakes: The competitive advantage and trade secret integrity of Company X and other submitting firms; the integrity of the regulatory process; the public trust in government agencies as neutral arbiters; Engineer A's own long-term professional reputation and licensure.
Decision Point: Yes - Story can branch here
- Recuse herself from reviewing submissions from companies she anticipates having future professional relationships with
- Formally document and acknowledge in writing the confidentiality obligations she is incurring with each submission reviewed
- Limit her engagement to only the minimum information necessary to complete the regulatory review, avoiding deeper study of proprietary design details
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Action_Access_Confidential_Design_Information",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Recuse herself from reviewing submissions from companies she anticipates having future professional relationships with",
"Formally document and acknowledge in writing the confidentiality obligations she is incurring with each submission reviewed",
"Limit her engagement to only the minimum information necessary to complete the regulatory review, avoiding deeper study of proprietary design details"
],
"proeth-scenario:characterMotivation": "Engineer A is fulfilling her legitimate, role-sanctioned regulatory duties at the government agency, reviewing facility design submissions as part of the approval process. Her motivation is professional competence and public service, not personal gain\u2014yet her access to sensitive third-party IP is an unavoidable structural feature of the role.",
"proeth-scenario:consequencesIfAlternative": [
"Recusal would reduce her regulatory effectiveness and might be impractical given the breadth of her role, but would proactively limit future conflicts of interest\u2014raising the question of whether such foresight is realistic or even required",
"Formal documentation would create a clear record of her obligations and could serve as a self-governance mechanism, though it would not change the substance of the obligations already created by law and professional codes",
"Minimizing engagement might compromise the quality of regulatory review and public safety outcomes, illustrating the genuine conflict between thoroughness in public service and limiting future competitive harm"
],
"proeth-scenario:decisionSignificance": "Teaches students that ethical obligations can be incurred passively through role-based access, not only through active wrongdoing. Engineers in regulatory, governmental, or quasi-judicial positions must recognize that privileged access to third-party information creates durable confidentiality duties that survive the role itself. This challenges the assumption that \u0027doing your job\u0027 is ethically neutral.",
"proeth-scenario:ethicalTension": "The tension exists between effective regulatory oversight (which requires deep access to proprietary technical information) and the intellectual property rights and competitive interests of the companies submitting that information. The engineer\u0027s duty to the public interest through rigorous review conflicts with the implicit confidentiality expectations of the submitting companies.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "The competitive advantage and trade secret integrity of Company X and other submitting firms; the integrity of the regulatory process; the public trust in government agencies as neutral arbiters; Engineer A\u0027s own long-term professional reputation and licensure.",
"proeth:description": "Engineer A actively receives and handles confidential and proprietary design information submitted by Company X and other companies during her tenure at the government agency. This represents an ongoing, role-sanctioned decision to engage with sensitive third-party information in her official regulatory capacity.",
"proeth:foreseenUnintendedEffects": [
"Accumulation of competitively sensitive knowledge about multiple companies that could create future conflicts of interest",
"Creation of lasting confidentiality obligations that would survive her employment"
],
"proeth:fulfillsObligation": [
"Duty to perform official government agency responsibilities",
"Duty to serve as faithful agent and trustee to the regulatory body",
"Duty to facilitate fair regulatory review of all submitting companies"
],
"proeth:guidedByPrinciple": [
"Faithful agency and trusteeship",
"Public interest and fair regulatory process",
"Confidentiality of client and employer information"
],
"proeth:hasAgent": "Engineer A (Government Agency Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Official regulatory access versus long-term confidentiality burden",
"proeth:resolutionReasoning": "Access was justified and required by official role; the ethical resolution is that access is permissible but imposes a corresponding and lasting duty of non-disclosure, not that access should be avoided"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Fulfill official regulatory duties by reviewing and processing company design submissions for facility approval",
"proeth:requiresCapability": [
"Engineering judgment to evaluate facility designs",
"Knowledge of regulatory standards and approval processes",
"Ability to handle and safeguard confidential technical documentation"
],
"proeth:temporalMarker": "During tenure at government agency",
"proeth:withinCompetence": true,
"rdfs:label": "Access Confidential Design Information"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changesDescription: Through a series of Board of Ethical Review decisions from 1974 through 1985 and beyond, a body of precedent addressing confidentiality and conflicts of interest in engineering practice comes into existence. This historical accumulation of decisions constitutes an exogenous contextual event that shapes the normative framework applicable to Engineer A's situation.
Temporal Marker: 1974 through 1985 and beyond (prior to and contextualizing the present case)
Activates Constraints:
- Precedent_Consistency_Constraint
- Professional_Code_Interpretation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: For students and practitioners, the existence of this precedent framework is reassuring — it signals that the profession has grappled with these issues before and has developed considered positions. For Engineer A, it means her situation is not unprecedented and that clear guidance exists.
- engineer_a: Her situation is governed by established precedent, reducing uncertainty about what is ethically required but also removing the excuse of ambiguity
- engineering_profession: The existence of a body of precedent demonstrates institutional maturity and self-regulatory capacity
- company_x_and_y: Both companies operate in a professional environment where engineers are bound by a known and developed ethical framework
- students_and_practitioners: Have access to reasoned guidance on how to handle similar situations
Learning Moment: Students should understand that professional ethics is not purely situational or personal — it is informed by an evolving body of institutional reasoning. Prior BER cases are not merely historical curiosities but active normative resources that shape what is ethically required in current situations.
Ethical Implications: Highlights the role of institutional memory and precedent in professional ethics — ethics is not reinvented from scratch in each situation but is shaped by accumulated professional wisdom. Also raises questions about accessibility: are engineers actually aware of BER precedents, and if not, does the normative framework function as intended?
- How much weight should prior BER decisions carry when analyzing a new ethical situation? Are they binding, persuasive, or merely illustrative?
- Does the existence of a well-developed body of precedent on confidentiality suggest that the engineering profession has adequately addressed this issue, or do structural problems remain?
- How should an engineer who is unfamiliar with BER precedents be expected to navigate situations that those precedents address?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Event_BER_Precedent_Framework_Established",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"How much weight should prior BER decisions carry when analyzing a new ethical situation? Are they binding, persuasive, or merely illustrative?",
"Does the existence of a well-developed body of precedent on confidentiality suggest that the engineering profession has adequately addressed this issue, or do structural problems remain?",
"How should an engineer who is unfamiliar with BER precedents be expected to navigate situations that those precedents address?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "For students and practitioners, the existence of this precedent framework is reassuring \u2014 it signals that the profession has grappled with these issues before and has developed considered positions. For Engineer A, it means her situation is not unprecedented and that clear guidance exists.",
"proeth-scenario:ethicalImplications": "Highlights the role of institutional memory and precedent in professional ethics \u2014 ethics is not reinvented from scratch in each situation but is shaped by accumulated professional wisdom. Also raises questions about accessibility: are engineers actually aware of BER precedents, and if not, does the normative framework function as intended?",
"proeth-scenario:learningMoment": "Students should understand that professional ethics is not purely situational or personal \u2014 it is informed by an evolving body of institutional reasoning. Prior BER cases are not merely historical curiosities but active normative resources that shape what is ethically required in current situations.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"company_x_and_y": "Both companies operate in a professional environment where engineers are bound by a known and developed ethical framework",
"engineer_a": "Her situation is governed by established precedent, reducing uncertainty about what is ethically required but also removing the excuse of ambiguity",
"engineering_profession": "The existence of a body of precedent demonstrates institutional maturity and self-regulatory capacity",
"students_and_practitioners": "Have access to reasoned guidance on how to handle similar situations"
},
"proeth:activatesConstraint": [
"Precedent_Consistency_Constraint",
"Professional_Code_Interpretation_Constraint"
],
"proeth:causesStateChange": "The ethical analysis of Engineer A\u0027s situation is anchored to and constrained by an established body of professional precedent; the outcome is not purely discretionary but must be consistent with prior BER reasoning.",
"proeth:createsObligation": [
"Obligation_To_Interpret_Current_Case_Consistently_With_Prior_BER_Decisions"
],
"proeth:description": "Through a series of Board of Ethical Review decisions from 1974 through 1985 and beyond, a body of precedent addressing confidentiality and conflicts of interest in engineering practice comes into existence. This historical accumulation of decisions constitutes an exogenous contextual event that shapes the normative framework applicable to Engineer A\u0027s situation.",
"proeth:emergencyStatus": "low",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "1974 through 1985 and beyond (prior to and contextualizing the present case)",
"proeth:urgencyLevel": "low",
"rdfs:label": "BER Precedent Framework Established"
}
Description: In the referenced BER Case 85-4, after Engineer A (the forensic engineer in that case) declines to produce a favorable report for the plaintiff, the opportunity to serve as the plaintiff's expert is effectively foreclosed. This is an outcome — the closing off of one professional path — that leads to the subsequent retention by the defendant's attorney.
Temporal Marker: Referenced as prior precedent; occurred in or around 1985
Activates Constraints:
- Objectivity_And_Honesty_Constraint
- Independence_Of_Expert_Opinion_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: The engineer in BER 85-4 experiences the tension between professional integrity and the practical consequences of honesty — losing a client and potentially facing pressure or professional consequences. The plaintiff's attorney experiences frustration and must seek other experts.
- engineer_ber_85_4: Demonstrates professional integrity but loses the engagement; faces the subsequent ethical complexity of potential retention by the defendant
- plaintiff: Loses a potentially knowledgeable expert; must find an expert willing to support their position honestly or abandon the claim
- defendant: May benefit from the engineer's honest assessment through subsequent retention
- legal_system: The case illustrates both the value and the vulnerability of honest expert testimony
Learning Moment: Students should recognize that professional integrity sometimes forecloses professional opportunities and creates new ethical complexities. The engineer's honest refusal in BER 85-4 is ethically required but generates the subsequent conflict-of-interest question about retention by the defendant.
Ethical Implications: Reveals the complex intersection of professional honesty, confidentiality, and conflict of interest in expert witness contexts. Demonstrates that doing the right thing (refusing to misrepresent findings) can create new ethical challenges rather than resolving all ethical concerns cleanly.
- Does an engineer who declines to produce a favorable report for one party have an obligation to decline retention by the opposing party, even if their honest assessment would support that party's position?
- What confidential information does the engineer acquire through the initial plaintiff engagement, and how does that constrain subsequent conduct?
- How does this precedent illuminate the relationship between professional honesty and conflict of interest management?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Event_Favorable_Report_Opportunity_Foreclosed__BER_85-4_",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Does an engineer who declines to produce a favorable report for one party have an obligation to decline retention by the opposing party, even if their honest assessment would support that party\u0027s position?",
"What confidential information does the engineer acquire through the initial plaintiff engagement, and how does that constrain subsequent conduct?",
"How does this precedent illuminate the relationship between professional honesty and conflict of interest management?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "The engineer in BER 85-4 experiences the tension between professional integrity and the practical consequences of honesty \u2014 losing a client and potentially facing pressure or professional consequences. The plaintiff\u0027s attorney experiences frustration and must seek other experts.",
"proeth-scenario:ethicalImplications": "Reveals the complex intersection of professional honesty, confidentiality, and conflict of interest in expert witness contexts. Demonstrates that doing the right thing (refusing to misrepresent findings) can create new ethical challenges rather than resolving all ethical concerns cleanly.",
"proeth-scenario:learningMoment": "Students should recognize that professional integrity sometimes forecloses professional opportunities and creates new ethical complexities. The engineer\u0027s honest refusal in BER 85-4 is ethically required but generates the subsequent conflict-of-interest question about retention by the defendant.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"defendant": "May benefit from the engineer\u0027s honest assessment through subsequent retention",
"engineer_ber_85_4": "Demonstrates professional integrity but loses the engagement; faces the subsequent ethical complexity of potential retention by the defendant",
"legal_system": "The case illustrates both the value and the vulnerability of honest expert testimony",
"plaintiff": "Loses a potentially knowledgeable expert; must find an expert willing to support their position honestly or abandon the claim"
},
"proeth:activatesConstraint": [
"Objectivity_And_Honesty_Constraint",
"Independence_Of_Expert_Opinion_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/106#Action_Decline_Favorable_Plaintiff_Report__BER_85-4_",
"proeth:causesStateChange": "The engineer\u0027s relationship with the plaintiff is terminated or foreclosed; the engineer\u0027s honest assessment creates the conditions for a new engagement with the opposing party, raising questions about sequential retention and confidentiality.",
"proeth:createsObligation": [
"Maintain_Honest_Professional_Assessment",
"Avoid_Advocacy_That_Compromises_Technical_Integrity"
],
"proeth:description": "In the referenced BER Case 85-4, after Engineer A (the forensic engineer in that case) declines to produce a favorable report for the plaintiff, the opportunity to serve as the plaintiff\u0027s expert is effectively foreclosed. This is an outcome \u2014 the closing off of one professional path \u2014 that leads to the subsequent retention by the defendant\u0027s attorney.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Referenced as prior precedent; occurred in or around 1985",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Favorable Report Opportunity Foreclosed (BER 85-4)"
}
Description: Through repeated exposure to proprietary design submissions from Company X and other firms, Engineer A accumulates a body of sensitive technical knowledge. This accumulation is an emergent outcome of her routine regulatory duties rather than a discrete volitional act.
Temporal Marker: During tenure at government agency (ongoing, prior to resignation)
Activates Constraints:
- Confidentiality_Obligation_Constraint
- Fiduciary_Duty_To_Submitting_Companies_Constraint
- Government_Employee_Conduct_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A likely experiences no alarm at the time — the accumulation feels routine and professional. In retrospect, the weight of this knowledge becomes a source of ethical anxiety. Company X and other firms remain unaware, creating a latent vulnerability they cannot perceive or guard against.
- engineer_a: Carries an invisible ethical burden that constrains future career choices; may not fully appreciate the significance until a conflict materializes
- company_x: Proprietary competitive advantages are now held in the mind of a government reviewer who may later work for a competitor; Company X has no recourse or awareness
- government_agency: Institutional integrity depends on employees honoring confidentiality norms that are difficult to enforce once knowledge is internalized
- public: Regulatory system's legitimacy depends on submitting companies trusting that confidential information will not be exploited
Learning Moment: Students should recognize that confidentiality obligations are not limited to deliberate disclosure acts — they attach to knowledge itself, and the passive accumulation of proprietary information through professional duties creates lasting ethical responsibilities that survive employment changes.
Ethical Implications: Reveals a structural tension in regulatory roles: the government needs technically expert reviewers, but expertise gained through access to proprietary information creates potential future conflicts of interest. Highlights the difference between knowledge as a professional asset and knowledge as an ethical liability.
- If Engineer A never deliberately sought out confidential information but simply absorbed it through her duties, does she bear the same ethical responsibility as someone who actively sought it out?
- What institutional safeguards could a government agency implement to reduce the ethical burden placed on individual engineers in regulatory roles?
- At what point does general professional expertise become impermissibly entangled with specific confidential knowledge?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Event_Confidential_Knowledge_Accumulated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"If Engineer A never deliberately sought out confidential information but simply absorbed it through her duties, does she bear the same ethical responsibility as someone who actively sought it out?",
"What institutional safeguards could a government agency implement to reduce the ethical burden placed on individual engineers in regulatory roles?",
"At what point does general professional expertise become impermissibly entangled with specific confidential knowledge?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer A likely experiences no alarm at the time \u2014 the accumulation feels routine and professional. In retrospect, the weight of this knowledge becomes a source of ethical anxiety. Company X and other firms remain unaware, creating a latent vulnerability they cannot perceive or guard against.",
"proeth-scenario:ethicalImplications": "Reveals a structural tension in regulatory roles: the government needs technically expert reviewers, but expertise gained through access to proprietary information creates potential future conflicts of interest. Highlights the difference between knowledge as a professional asset and knowledge as an ethical liability.",
"proeth-scenario:learningMoment": "Students should recognize that confidentiality obligations are not limited to deliberate disclosure acts \u2014 they attach to knowledge itself, and the passive accumulation of proprietary information through professional duties creates lasting ethical responsibilities that survive employment changes.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"company_x": "Proprietary competitive advantages are now held in the mind of a government reviewer who may later work for a competitor; Company X has no recourse or awareness",
"engineer_a": "Carries an invisible ethical burden that constrains future career choices; may not fully appreciate the significance until a conflict materializes",
"government_agency": "Institutional integrity depends on employees honoring confidentiality norms that are difficult to enforce once knowledge is internalized",
"public": "Regulatory system\u0027s legitimacy depends on submitting companies trusting that confidential information will not be exploited"
},
"proeth:activatesConstraint": [
"Confidentiality_Obligation_Constraint",
"Fiduciary_Duty_To_Submitting_Companies_Constraint",
"Government_Employee_Conduct_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/106#Action_Access_Confidential_Design_Information",
"proeth:causesStateChange": "Engineer A transitions from ordinary employee to a person carrying a confidential knowledge burden that persists beyond her employment; the ethical risk profile of any future employment in the same industry is permanently elevated.",
"proeth:createsObligation": [
"Perpetual_Non_Disclosure_Of_Proprietary_Information",
"Awareness_Of_Future_Conflict_Potential",
"Duty_Not_To_Exploit_Regulatory_Access_For_Private_Gain"
],
"proeth:description": "Through repeated exposure to proprietary design submissions from Company X and other firms, Engineer A accumulates a body of sensitive technical knowledge. This accumulation is an emergent outcome of her routine regulatory duties rather than a discrete volitional act.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "During tenure at government agency (ongoing, prior to resignation)",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Confidential Knowledge Accumulated"
}
Description: Upon Engineer A accepting a position at Company Y — a direct competitor of Company X — a conflict of interest situation comes into existence as an automatic consequence of the employment transition. This is not a decision but the structural outcome of two facts coinciding: Engineer A's confidential knowledge and her new competitive employment context.
Temporal Marker: At the moment Engineer A's employment at Company Y commences
Activates Constraints:
- Conflict_Of_Interest_Prohibition_Constraint
- Confidentiality_Active_Duty_Constraint
- Loyalty_To_New_Employer_Constraint
- Non_Exploitation_Of_Prior_Access_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel the tension between professional opportunity and ethical constraint acutely. Company Y may be unaware of the full scope of the ethical complexity they have introduced. Company X, if aware, would feel vulnerable and potentially betrayed by the regulatory system they trusted.
- engineer_a: Faces ongoing ethical vigilance requirement; career advancement at Company Y may be constrained by what she cannot use or share; risk of professional discipline if confidentiality is breached
- company_y: Gains a technically expert employee but also inherits potential legal and reputational risk if confidential information is later found to have been used
- company_x: Competitive disadvantage risk materializes; proprietary information now resides with an employee of a direct competitor
- government_agency: Institutional credibility is implicated; the case raises questions about revolving-door policies and post-employment restrictions
- engineering_profession: The case tests whether professional ethical codes are sufficient to manage conflicts that structural employment transitions create
Learning Moment: Students should understand that a conflict of interest is a structural condition, not merely an intention. The conflict exists the moment the incompatible roles and knowledge coincide, regardless of whether Engineer A intends to misuse the information. The ethical obligation is to manage and disclose the conflict, not merely to avoid bad intent.
Ethical Implications: Exposes the revolving-door problem in regulatory contexts: technical expertise that makes someone valuable as a regulator is the same expertise that makes them valuable to regulated industries, creating structural incentives for knowledge exploitation. Highlights the gap between legal permissibility (taking the job is allowed) and full ethical management (active ongoing obligations remain).
- Does Engineer A have an obligation to disclose her prior access to Company X's confidential information to Company Y before or upon accepting the position?
- Should government agencies implement post-employment restrictions (cooling-off periods) for engineers with access to proprietary regulatory submissions? What would be the costs and benefits?
- Is it sufficient for Engineer A to simply resolve not to disclose confidential information, or are more active measures required to manage this conflict?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Event_Competitive_Conflict_Situation_Arises",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Does Engineer A have an obligation to disclose her prior access to Company X\u0027s confidential information to Company Y before or upon accepting the position?",
"Should government agencies implement post-employment restrictions (cooling-off periods) for engineers with access to proprietary regulatory submissions? What would be the costs and benefits?",
"Is it sufficient for Engineer A to simply resolve not to disclose confidential information, or are more active measures required to manage this conflict?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may feel the tension between professional opportunity and ethical constraint acutely. Company Y may be unaware of the full scope of the ethical complexity they have introduced. Company X, if aware, would feel vulnerable and potentially betrayed by the regulatory system they trusted.",
"proeth-scenario:ethicalImplications": "Exposes the revolving-door problem in regulatory contexts: technical expertise that makes someone valuable as a regulator is the same expertise that makes them valuable to regulated industries, creating structural incentives for knowledge exploitation. Highlights the gap between legal permissibility (taking the job is allowed) and full ethical management (active ongoing obligations remain).",
"proeth-scenario:learningMoment": "Students should understand that a conflict of interest is a structural condition, not merely an intention. The conflict exists the moment the incompatible roles and knowledge coincide, regardless of whether Engineer A intends to misuse the information. The ethical obligation is to manage and disclose the conflict, not merely to avoid bad intent.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"company_x": "Competitive disadvantage risk materializes; proprietary information now resides with an employee of a direct competitor",
"company_y": "Gains a technically expert employee but also inherits potential legal and reputational risk if confidential information is later found to have been used",
"engineer_a": "Faces ongoing ethical vigilance requirement; career advancement at Company Y may be constrained by what she cannot use or share; risk of professional discipline if confidentiality is breached",
"engineering_profession": "The case tests whether professional ethical codes are sufficient to manage conflicts that structural employment transitions create",
"government_agency": "Institutional credibility is implicated; the case raises questions about revolving-door policies and post-employment restrictions"
},
"proeth:activatesConstraint": [
"Conflict_Of_Interest_Prohibition_Constraint",
"Confidentiality_Active_Duty_Constraint",
"Loyalty_To_New_Employer_Constraint",
"Non_Exploitation_Of_Prior_Access_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/106#Action_Accept_Position_at_Competitor",
"proeth:causesStateChange": "The ethical situation transforms from latent risk to active conflict of interest; Engineer A now simultaneously holds confidential knowledge advantageous to Company Y and owes duties of non-disclosure to Company X; the tension between employer loyalty and prior confidentiality obligations is fully activated.",
"proeth:createsObligation": [
"Ongoing_Non_Disclosure_Of_Company_X_Proprietary_Information",
"Potential_Duty_To_Notify_Relevant_Parties_Of_Conflict",
"Duty_To_Avoid_Work_Assignments_Exploiting_Confidential_Knowledge"
],
"proeth:description": "Upon Engineer A accepting a position at Company Y \u2014 a direct competitor of Company X \u2014 a conflict of interest situation comes into existence as an automatic consequence of the employment transition. This is not a decision but the structural outcome of two facts coinciding: Engineer A\u0027s confidential knowledge and her new competitive employment context.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "At the moment Engineer A\u0027s employment at Company Y commences",
"proeth:urgencyLevel": "high",
"rdfs:label": "Competitive Conflict Situation Arises"
}
Description: As a consequence of Engineer A's resignation and entry into competitive employment, her pre-existing confidentiality obligations — previously somewhat abstract — become concretely and urgently operative. The obligation does not newly arise but is triggered into active, high-stakes relevance by the changed employment context.
Temporal Marker: Concurrent with commencement of employment at Company Y
Activates Constraints:
- Non_Disclosure_Constraint_Perpetual
- Duty_Not_To_Exploit_Regulatory_Knowledge_Constraint
- Professional_Code_Compliance_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A must now consciously police the boundary between what she knows generally as a professional and what she knows specifically from confidential access — a psychologically demanding and ongoing task. The burden is invisible to colleagues but constant for Engineer A.
- engineer_a: Daily professional conduct is constrained; must avoid certain work assignments or conversations; risk of inadvertent disclosure creates ongoing stress
- company_y: May find Engineer A's contributions in certain areas unexpectedly limited; may not understand why without disclosure
- company_x: Relies entirely on Engineer A's personal ethical commitment for protection — has no enforcement mechanism
- engineering_profession: The adequacy of self-regulation through professional codes is tested; the case becomes precedent (BER) for how such situations should be handled
Learning Moment: Students should appreciate that professional ethical obligations are not discharged by simply not doing something wrong — they require active, ongoing management. The duty of confidentiality here is perpetual and demands conscious behavioral compliance, not just passive non-action.
Ethical Implications: Reveals the limits of individual ethical commitment as a sole safeguard for confidentiality in competitive industries. Raises questions about whether professional codes, without enforcement mechanisms, place an unfair burden on individuals while leaving injured parties (Company X) without meaningful protection.
- How can Engineer A practically manage the boundary between her general professional knowledge and her specifically confidential knowledge when they may be deeply intertwined?
- What responsibilities does Company Y have once it knows (or should know) that Engineer A may carry confidential knowledge from a competitor?
- Is the reliance on individual professional ethics sufficient to protect Company X's interests, or should structural/legal mechanisms be required?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Event_Perpetual_Confidentiality_Obligation_Activated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"How can Engineer A practically manage the boundary between her general professional knowledge and her specifically confidential knowledge when they may be deeply intertwined?",
"What responsibilities does Company Y have once it knows (or should know) that Engineer A may carry confidential knowledge from a competitor?",
"Is the reliance on individual professional ethics sufficient to protect Company X\u0027s interests, or should structural/legal mechanisms be required?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A must now consciously police the boundary between what she knows generally as a professional and what she knows specifically from confidential access \u2014 a psychologically demanding and ongoing task. The burden is invisible to colleagues but constant for Engineer A.",
"proeth-scenario:ethicalImplications": "Reveals the limits of individual ethical commitment as a sole safeguard for confidentiality in competitive industries. Raises questions about whether professional codes, without enforcement mechanisms, place an unfair burden on individuals while leaving injured parties (Company X) without meaningful protection.",
"proeth-scenario:learningMoment": "Students should appreciate that professional ethical obligations are not discharged by simply not doing something wrong \u2014 they require active, ongoing management. The duty of confidentiality here is perpetual and demands conscious behavioral compliance, not just passive non-action.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"company_x": "Relies entirely on Engineer A\u0027s personal ethical commitment for protection \u2014 has no enforcement mechanism",
"company_y": "May find Engineer A\u0027s contributions in certain areas unexpectedly limited; may not understand why without disclosure",
"engineer_a": "Daily professional conduct is constrained; must avoid certain work assignments or conversations; risk of inadvertent disclosure creates ongoing stress",
"engineering_profession": "The adequacy of self-regulation through professional codes is tested; the case becomes precedent (BER) for how such situations should be handled"
},
"proeth:activatesConstraint": [
"Non_Disclosure_Constraint_Perpetual",
"Duty_Not_To_Exploit_Regulatory_Knowledge_Constraint",
"Professional_Code_Compliance_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/106#Action_Accept_Position_at_Competitor",
"proeth:causesStateChange": "The confidentiality obligation shifts from a passive background duty to an active, operationally significant constraint governing Engineer A\u0027s day-to-day professional conduct at Company Y.",
"proeth:createsObligation": [
"Never_Disclose_Company_X_Proprietary_Information",
"Avoid_Work_That_Would_Require_Use_Of_Confidential_Knowledge",
"Potentially_Notify_Company_Y_Of_Limitations_On_Her_Contributions"
],
"proeth:description": "As a consequence of Engineer A\u0027s resignation and entry into competitive employment, her pre-existing confidentiality obligations \u2014 previously somewhat abstract \u2014 become concretely and urgently operative. The obligation does not newly arise but is triggered into active, high-stakes relevance by the changed employment context.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "Concurrent with commencement of employment at Company Y",
"proeth:urgencyLevel": "high",
"rdfs:label": "Perpetual Confidentiality Obligation Activated"
}
Description: In the referenced BER Case 82-6, an engineer who had previously been retained by one party in a dispute is subsequently retained by the opposing party. This event — the retention by the opposing party — is an outcome that creates a direct conflict of interest and serves as a precedential analog to Engineer A's situation.
Temporal Marker: Referenced as prior precedent; occurred in or around 1982
Activates Constraints:
- Conflict_Of_Interest_Constraint
- Loyalty_And_Confidentiality_To_Prior_Client_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: The unnamed engineer in BER 82-6 faces divided loyalties and the discomfort of knowing that prior confidential knowledge may be relevant to — and potentially advantageous in — the new engagement. Both parties likely feel a sense of betrayal or vulnerability.
- engineer_ber_82_6: Professional reputation and ethical standing are at risk; must navigate competing obligations
- first_party: Confidential information shared in trust is now potentially accessible to an adversary
- opposing_party: May benefit from engineer's prior access but also risks engaging someone with conflicted loyalties
- engineering_profession: The case tests and ultimately reinforces the principle that confidentiality obligations survive the end of an engagement
Learning Moment: Students should recognize that BER 82-6 establishes the principle that confidentiality obligations are not dissolved by the end of a professional relationship and that accepting an engagement with an opposing party triggers heightened ethical scrutiny. This principle directly informs Engineer A's obligations.
Ethical Implications: Demonstrates that professional loyalty and confidentiality are not merely contractual obligations but ethical ones that persist beyond the formal engagement. Raises questions about whether the engineering profession's self-regulatory mechanisms adequately protect parties who share confidential information in professional contexts.
- What distinguishes a permissible change of client from an impermissible conflict of interest? Where is the line?
- Should the engineer in BER 82-6 have declined the retention by the opposing party outright, or is disclosure and management sufficient?
- How does this precedent apply to Engineer A's situation, and what are the relevant similarities and differences?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/106#Event_Engineer_Retained_By_Opposing_Party__BER_82-6_",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"What distinguishes a permissible change of client from an impermissible conflict of interest? Where is the line?",
"Should the engineer in BER 82-6 have declined the retention by the opposing party outright, or is disclosure and management sufficient?",
"How does this precedent apply to Engineer A\u0027s situation, and what are the relevant similarities and differences?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "The unnamed engineer in BER 82-6 faces divided loyalties and the discomfort of knowing that prior confidential knowledge may be relevant to \u2014 and potentially advantageous in \u2014 the new engagement. Both parties likely feel a sense of betrayal or vulnerability.",
"proeth-scenario:ethicalImplications": "Demonstrates that professional loyalty and confidentiality are not merely contractual obligations but ethical ones that persist beyond the formal engagement. Raises questions about whether the engineering profession\u0027s self-regulatory mechanisms adequately protect parties who share confidential information in professional contexts.",
"proeth-scenario:learningMoment": "Students should recognize that BER 82-6 establishes the principle that confidentiality obligations are not dissolved by the end of a professional relationship and that accepting an engagement with an opposing party triggers heightened ethical scrutiny. This principle directly informs Engineer A\u0027s obligations.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"engineer_ber_82_6": "Professional reputation and ethical standing are at risk; must navigate competing obligations",
"engineering_profession": "The case tests and ultimately reinforces the principle that confidentiality obligations survive the end of an engagement",
"first_party": "Confidential information shared in trust is now potentially accessible to an adversary",
"opposing_party": "May benefit from engineer\u0027s prior access but also risks engaging someone with conflicted loyalties"
},
"proeth:activatesConstraint": [
"Conflict_Of_Interest_Constraint",
"Loyalty_And_Confidentiality_To_Prior_Client_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/106#Action_Accept_Retention_by_Opposing_Party__BER_82-6_",
"proeth:causesStateChange": "A conflict of interest is created by the engineer\u0027s simultaneous or sequential relationships with opposing parties; the BER\u0027s resolution of this case creates precedent applicable to Engineer A\u0027s situation.",
"proeth:createsObligation": [
"Disclosure_Of_Prior_Relationship",
"Non_Use_Of_Confidential_Information_From_Prior_Engagement"
],
"proeth:description": "In the referenced BER Case 82-6, an engineer who had previously been retained by one party in a dispute is subsequently retained by the opposing party. This event \u2014 the retention by the opposing party \u2014 is an outcome that creates a direct conflict of interest and serves as a precedential analog to Engineer A\u0027s situation.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Referenced as prior precedent; occurred in or around 1982",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Engineer Retained By Opposing Party (BER 82-6)"
}
Causal Chains (7)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Through repeated exposure to proprietary design submissions from Company X and other firms, Engineer A accumulated confidential knowledge as a direct consequence of actively receiving and handling that information in her government role
Necessary Factors (NESS):
- Engineer A's active role in receiving and handling submissions
- Repeated exposure to proprietary design data over time
- Nature of government agency role providing access to competitor submissions
- Absence of compartmentalization preventing knowledge accumulation
Sufficient Factors:
- Combination of official access authority + repeated exposure + proprietary content + no knowledge barriers = inevitable accumulation of confidential knowledge
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Access Confidential Design Information (Action 1)
Engineer A actively receives and handles proprietary design submissions from Company X and other firms in her government agency role -
Repeated Exposure Cycle
Ongoing professional duties require continued engagement with confidential technical data over the course of employment -
Knowledge Internalization
Proprietary design details, methodologies, and competitive information become embedded in Engineer A's professional knowledge base -
Confidential Knowledge Accumulated (Event 1)
Engineer A now possesses a body of confidential knowledge that creates future ethical and legal obligations regardless of her employment status -
Perpetual Confidentiality Obligation Activated (Event 3)
The accumulated knowledge triggers ongoing duties of non-disclosure that survive her government employment
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_330009ec",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Through repeated exposure to proprietary design submissions from Company X and other firms, Engineer A accumulated confidential knowledge as a direct consequence of actively receiving and handling that information in her government role",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A actively receives and handles proprietary design submissions from Company X and other firms in her government agency role",
"proeth:element": "Access Confidential Design Information (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Ongoing professional duties require continued engagement with confidential technical data over the course of employment",
"proeth:element": "Repeated Exposure Cycle",
"proeth:step": 2
},
{
"proeth:description": "Proprietary design details, methodologies, and competitive information become embedded in Engineer A\u0027s professional knowledge base",
"proeth:element": "Knowledge Internalization",
"proeth:step": 3
},
{
"proeth:description": "Engineer A now possesses a body of confidential knowledge that creates future ethical and legal obligations regardless of her employment status",
"proeth:element": "Confidential Knowledge Accumulated (Event 1)",
"proeth:step": 4
},
{
"proeth:description": "The accumulated knowledge triggers ongoing duties of non-disclosure that survive her government employment",
"proeth:element": "Perpetual Confidentiality Obligation Activated (Event 3)",
"proeth:step": 5
}
],
"proeth:cause": "Access Confidential Design Information (Action 1)",
"proeth:counterfactual": "Without Engineer A\u0027s active receipt and handling of confidential submissions, the proprietary knowledge would not have been internalized; had she been assigned to non-confidential review functions, the conflict would not have arisen",
"proeth:effect": "Confidential Knowledge Accumulated (Event 1)",
"proeth:necessaryFactors": [
"Engineer A\u0027s active role in receiving and handling submissions",
"Repeated exposure to proprietary design data over time",
"Nature of government agency role providing access to competitor submissions",
"Absence of compartmentalization preventing knowledge accumulation"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Combination of official access authority + repeated exposure + proprietary content + no knowledge barriers = inevitable accumulation of confidential knowledge"
],
"proeth:withinAgentControl": true
}
Causal Language: Upon Engineer A accepting a position at Company Y — a direct competitor of Company X — a conflict of interest situation arises as a direct consequence of her resignation and entry into competitive employment
Necessary Factors (NESS):
- Prior accumulation of Company X confidential knowledge (Event 1)
- Voluntary resignation from the neutral government agency role
- Affirmative acceptance of employment at Company Y, a direct competitor
- Company Y operating in the same competitive space as Company X
Sufficient Factors:
- Accumulated confidential knowledge + departure from neutral role + entry into direct competitor employment = sufficient to generate a fully realized conflict of interest
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Confidential Knowledge Accumulated (Event 1)
Engineer A possesses internalized proprietary knowledge about Company X from her government role -
Resign from Government Agency (Action 2)
Engineer A voluntarily terminates her neutral government position, removing the structural separation between her knowledge and competitive use -
Accept Position at Competitor (Action 3)
Engineer A affirmatively accepts employment at Company Y, a direct competitor of Company X -
Competitive Conflict Situation Arises (Event 2)
The combination of prior confidential knowledge and new competitive employment creates an active ethical conflict -
Perpetual Confidentiality Obligation Activated (Event 3)
Pre-existing confidentiality duties are triggered in their most demanding form by the competitive employment context
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_67c2fa01",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Upon Engineer A accepting a position at Company Y \u2014 a direct competitor of Company X \u2014 a conflict of interest situation arises as a direct consequence of her resignation and entry into competitive employment",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A possesses internalized proprietary knowledge about Company X from her government role",
"proeth:element": "Confidential Knowledge Accumulated (Event 1)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A voluntarily terminates her neutral government position, removing the structural separation between her knowledge and competitive use",
"proeth:element": "Resign from Government Agency (Action 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A affirmatively accepts employment at Company Y, a direct competitor of Company X",
"proeth:element": "Accept Position at Competitor (Action 3)",
"proeth:step": 3
},
{
"proeth:description": "The combination of prior confidential knowledge and new competitive employment creates an active ethical conflict",
"proeth:element": "Competitive Conflict Situation Arises (Event 2)",
"proeth:step": 4
},
{
"proeth:description": "Pre-existing confidentiality duties are triggered in their most demanding form by the competitive employment context",
"proeth:element": "Perpetual Confidentiality Obligation Activated (Event 3)",
"proeth:step": 5
}
],
"proeth:cause": "Resign from Government Agency (Action 2) + Accept Position at Competitor (Action 3)",
"proeth:counterfactual": "Had Engineer A accepted a position at a non-competing firm or in a different industry sector, the competitive conflict would not have materialized; had she not accumulated confidential knowledge, the move would have been ethically unproblematic",
"proeth:effect": "Competitive Conflict Situation Arises (Event 2)",
"proeth:necessaryFactors": [
"Prior accumulation of Company X confidential knowledge (Event 1)",
"Voluntary resignation from the neutral government agency role",
"Affirmative acceptance of employment at Company Y, a direct competitor",
"Company Y operating in the same competitive space as Company X"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Accumulated confidential knowledge + departure from neutral role + entry into direct competitor employment = sufficient to generate a fully realized conflict of interest"
],
"proeth:withinAgentControl": true
}
Causal Language: As a consequence of Engineer A's resignation and entry into competitive employment, her pre-existing confidentiality obligations are activated in their most demanding and perpetual form, requiring continuous non-disclosure throughout her employment at Company Y
Necessary Factors (NESS):
- Prior existence of confidentiality obligations arising from government access to proprietary data
- Engineer A's transition into a role where confidential knowledge could provide competitive advantage
- The competitive relationship between Company X and Company Y
- Absence of any waiver or release from confidentiality obligations by affected parties
Sufficient Factors:
- Pre-existing confidentiality duty + competitive employment context + no waiver = sufficient to activate perpetual and ongoing non-disclosure obligations
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Access Confidential Design Information (Action 1)
Original source of confidentiality obligation through government role access -
Competitive Conflict Situation Arises (Event 2)
Transition to competitor employment transforms latent duty into active, operationally demanding obligation -
Perpetual Confidentiality Obligation Activated (Event 3)
Engineer A's duty of non-disclosure becomes continuous and ongoing throughout Company Y employment -
Withhold Company X Confidential Information (Action 4)
Engineer A must make repeated, affirmative decisions not to disclose confidential information in her daily work -
Ethical Compliance or Violation Outcome
Engineer A either successfully maintains confidentiality (ethical compliance) or fails to do so (ethical violation with professional and legal consequences)
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_74a87004",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "As a consequence of Engineer A\u0027s resignation and entry into competitive employment, her pre-existing confidentiality obligations are activated in their most demanding and perpetual form, requiring continuous non-disclosure throughout her employment at Company Y",
"proeth:causalSequence": [
{
"proeth:description": "Original source of confidentiality obligation through government role access",
"proeth:element": "Access Confidential Design Information (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Transition to competitor employment transforms latent duty into active, operationally demanding obligation",
"proeth:element": "Competitive Conflict Situation Arises (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A\u0027s duty of non-disclosure becomes continuous and ongoing throughout Company Y employment",
"proeth:element": "Perpetual Confidentiality Obligation Activated (Event 3)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A must make repeated, affirmative decisions not to disclose confidential information in her daily work",
"proeth:element": "Withhold Company X Confidential Information (Action 4)",
"proeth:step": 4
},
{
"proeth:description": "Engineer A either successfully maintains confidentiality (ethical compliance) or fails to do so (ethical violation with professional and legal consequences)",
"proeth:element": "Ethical Compliance or Violation Outcome",
"proeth:step": 5
}
],
"proeth:cause": "Competitive Conflict Situation Arises (Event 2)",
"proeth:counterfactual": "Had Engineer A remained in government service or moved to a non-competing employer, the confidentiality obligations would have remained latent and less operationally demanding; the perpetual activation is specifically caused by the competitive employment choice",
"proeth:effect": "Perpetual Confidentiality Obligation Activated (Event 3)",
"proeth:necessaryFactors": [
"Prior existence of confidentiality obligations arising from government access to proprietary data",
"Engineer A\u0027s transition into a role where confidential knowledge could provide competitive advantage",
"The competitive relationship between Company X and Company Y",
"Absence of any waiver or release from confidentiality obligations by affected parties"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Pre-existing confidentiality duty + competitive employment context + no waiver = sufficient to activate perpetual and ongoing non-disclosure obligations"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A must make continuous, ongoing decisions throughout her employment at Company Y not to disclose confidential information, with each decision representing an affirmative ethical choice that either satisfies or violates her perpetual confidentiality obligation
Necessary Factors (NESS):
- Engineer A's ongoing awareness of what information is confidential
- Repeated situational opportunities or pressures to disclose at Company Y
- Active volitional choice in each instance to withhold rather than share
- Sufficient professional knowledge to distinguish confidential from non-confidential information
Sufficient Factors:
- Continuous awareness of confidential information + repeated non-disclosure decisions + no coercive disclosure pressure = sufficient for ongoing ethical compliance
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Perpetual Confidentiality Obligation Activated (Event 3)
Ongoing duty of non-disclosure established as binding professional obligation -
Competitive Employment Context at Company Y
Daily work environment creates recurring situations where confidential knowledge is potentially relevant and valuable -
Withhold Company X Confidential Information (Action 4)
Engineer A makes affirmative, repeated decisions to refrain from disclosing confidential information in each relevant situation -
BER Precedent Framework Consulted (Event 4)
Established ethical precedents inform the scope and application of non-disclosure obligations in ambiguous situations -
Ethical Compliance or Professional Misconduct Determination
Cumulative pattern of disclosure decisions determines whether Engineer A has honored or violated her professional obligations
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_231779de",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A must make continuous, ongoing decisions throughout her employment at Company Y not to disclose confidential information, with each decision representing an affirmative ethical choice that either satisfies or violates her perpetual confidentiality obligation",
"proeth:causalSequence": [
{
"proeth:description": "Ongoing duty of non-disclosure established as binding professional obligation",
"proeth:element": "Perpetual Confidentiality Obligation Activated (Event 3)",
"proeth:step": 1
},
{
"proeth:description": "Daily work environment creates recurring situations where confidential knowledge is potentially relevant and valuable",
"proeth:element": "Competitive Employment Context at Company Y",
"proeth:step": 2
},
{
"proeth:description": "Engineer A makes affirmative, repeated decisions to refrain from disclosing confidential information in each relevant situation",
"proeth:element": "Withhold Company X Confidential Information (Action 4)",
"proeth:step": 3
},
{
"proeth:description": "Established ethical precedents inform the scope and application of non-disclosure obligations in ambiguous situations",
"proeth:element": "BER Precedent Framework Consulted (Event 4)",
"proeth:step": 4
},
{
"proeth:description": "Cumulative pattern of disclosure decisions determines whether Engineer A has honored or violated her professional obligations",
"proeth:element": "Ethical Compliance or Professional Misconduct Determination",
"proeth:step": 5
}
],
"proeth:cause": "Withhold Company X Confidential Information (Action 4)",
"proeth:counterfactual": "Without continuous, affirmative non-disclosure decisions, Engineer A\u0027s mere possession of confidential knowledge combined with competitive employment would likely result in inadvertent or deliberate disclosure; passive non-action is insufficient given the active competitive pressures of the new role",
"proeth:effect": "Ethical Compliance Maintained Under Perpetual Confidentiality Obligation (Event 3 resolution)",
"proeth:necessaryFactors": [
"Engineer A\u0027s ongoing awareness of what information is confidential",
"Repeated situational opportunities or pressures to disclose at Company Y",
"Active volitional choice in each instance to withhold rather than share",
"Sufficient professional knowledge to distinguish confidential from non-confidential information"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Continuous awareness of confidential information + repeated non-disclosure decisions + no coercive disclosure pressure = sufficient for ongoing ethical compliance"
],
"proeth:withinAgentControl": true
}
Causal Language: In the historical reference case BER 82-6, an engineer retained by the US government to study a dam subsequently accepted retention by the opposing party in related litigation, directly creating the conflict of interest scenario that the BER was called upon to evaluate
Necessary Factors (NESS):
- Prior retention by and exposure to confidential information from the first party (US government)
- Existence of an opposing party with adverse interests in the same matter
- Engineer's affirmative decision to accept the opposing retention
- Absence of consent from the original retaining party
Sufficient Factors:
- Prior confidential retention + adverse party retention + no consent = sufficient to constitute the ethical conflict evaluated in BER 82-6
Responsibility Attribution:
Agent: Engineer in BER 82-6
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Initial Government Retention (BER 82-6)
Engineer accepts retention by US government to study the dam, receiving confidential information and developing a professional relationship -
Litigation Arises Between Parties
A dispute develops in which the government and another party hold adverse interests related to the dam study -
Accept Retention by Opposing Party (Action 5)
Engineer affirmatively accepts retention by the party with interests adverse to the original government client -
Engineer Retained By Opposing Party (Event 5)
The conflict of interest is fully realized, with the engineer now serving parties with directly adverse interests in the same matter -
BER Precedent Framework Established (Event 4)
BER 82-6 ruling establishes precedent that such dual retention violates professional ethics, contributing to the framework applied in Engineer A's case
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_8d254ede",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "In the historical reference case BER 82-6, an engineer retained by the US government to study a dam subsequently accepted retention by the opposing party in related litigation, directly creating the conflict of interest scenario that the BER was called upon to evaluate",
"proeth:causalSequence": [
{
"proeth:description": "Engineer accepts retention by US government to study the dam, receiving confidential information and developing a professional relationship",
"proeth:element": "Initial Government Retention (BER 82-6)",
"proeth:step": 1
},
{
"proeth:description": "A dispute develops in which the government and another party hold adverse interests related to the dam study",
"proeth:element": "Litigation Arises Between Parties",
"proeth:step": 2
},
{
"proeth:description": "Engineer affirmatively accepts retention by the party with interests adverse to the original government client",
"proeth:element": "Accept Retention by Opposing Party (Action 5)",
"proeth:step": 3
},
{
"proeth:description": "The conflict of interest is fully realized, with the engineer now serving parties with directly adverse interests in the same matter",
"proeth:element": "Engineer Retained By Opposing Party (Event 5)",
"proeth:step": 4
},
{
"proeth:description": "BER 82-6 ruling establishes precedent that such dual retention violates professional ethics, contributing to the framework applied in Engineer A\u0027s case",
"proeth:element": "BER Precedent Framework Established (Event 4)",
"proeth:step": 5
}
],
"proeth:cause": "Accept Retention by Opposing Party (BER 82-6) (Action 5)",
"proeth:counterfactual": "Had the engineer declined retention by the opposing party or obtained informed consent from the government, the ethical conflict central to BER 82-6 would not have arisen; the BER precedent would not have been established in this form",
"proeth:effect": "Engineer Retained By Opposing Party (BER 82-6) (Event 5)",
"proeth:necessaryFactors": [
"Prior retention by and exposure to confidential information from the first party (US government)",
"Existence of an opposing party with adverse interests in the same matter",
"Engineer\u0027s affirmative decision to accept the opposing retention",
"Absence of consent from the original retaining party"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer in BER 82-6",
"proeth:sufficientFactors": [
"Prior confidential retention + adverse party retention + no consent = sufficient to constitute the ethical conflict evaluated in BER 82-6"
],
"proeth:withinAgentControl": true
}
Causal Language: In the referenced BER Case 85-4, after Engineer A (the forensic engineer in that case) declines to provide a favorable engineering report, the opportunity for the plaintiff to obtain that report from this engineer is permanently foreclosed, triggering the subsequent retention by the defendant's attorney
Necessary Factors (NESS):
- Forensic engineer's honest professional assessment that a favorable plaintiff report was not supportable
- Plaintiff attorney's termination of the engineer following the unfavorable assessment
- The engineer's ethical commitment to honest reporting over client-favorable outcomes
- Existence of the defendant's attorney as an alternative retaining party
Sufficient Factors:
- Honest professional assessment incompatible with plaintiff's position + termination by plaintiff attorney + availability of defendant retention = sufficient to produce the dual-retention ethical scenario in BER 85-4
Responsibility Attribution:
Agent: Forensic Engineer in BER 85-4
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Initial Retention by Plaintiff's Attorney (BER 85-4)
Forensic engineer is retained by plaintiff's attorney and receives confidential case information and strategy -
Decline Favorable Plaintiff Report (Action 6)
Engineer determines honest professional assessment cannot support a favorable plaintiff report and declines to provide one -
Termination by Plaintiff's Attorney
Plaintiff's attorney terminates the engineer's retention upon receiving the unfavorable assessment -
Accept Retention by Defendant's Attorney (Action 7)
Engineer accepts retention by defendant's attorney, creating the dual-exposure ethical conflict -
BER Precedent Framework Established (Event 4)
BER 85-4 ruling on whether the engineer may serve the defendant after plaintiff retention contributes to the precedent framework governing Engineer A's situation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_6e01aae7",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "In the referenced BER Case 85-4, after Engineer A (the forensic engineer in that case) declines to provide a favorable engineering report, the opportunity for the plaintiff to obtain that report from this engineer is permanently foreclosed, triggering the subsequent retention by the defendant\u0027s attorney",
"proeth:causalSequence": [
{
"proeth:description": "Forensic engineer is retained by plaintiff\u0027s attorney and receives confidential case information and strategy",
"proeth:element": "Initial Retention by Plaintiff\u0027s Attorney (BER 85-4)",
"proeth:step": 1
},
{
"proeth:description": "Engineer determines honest professional assessment cannot support a favorable plaintiff report and declines to provide one",
"proeth:element": "Decline Favorable Plaintiff Report (Action 6)",
"proeth:step": 2
},
{
"proeth:description": "Plaintiff\u0027s attorney terminates the engineer\u0027s retention upon receiving the unfavorable assessment",
"proeth:element": "Termination by Plaintiff\u0027s Attorney",
"proeth:step": 3
},
{
"proeth:description": "Engineer accepts retention by defendant\u0027s attorney, creating the dual-exposure ethical conflict",
"proeth:element": "Accept Retention by Defendant\u0027s Attorney (Action 7)",
"proeth:step": 4
},
{
"proeth:description": "BER 85-4 ruling on whether the engineer may serve the defendant after plaintiff retention contributes to the precedent framework governing Engineer A\u0027s situation",
"proeth:element": "BER Precedent Framework Established (Event 4)",
"proeth:step": 5
}
],
"proeth:cause": "Decline Favorable Plaintiff Report (BER 85-4) (Action 6)",
"proeth:counterfactual": "Had the forensic engineer provided the favorable report despite honest reservations, the plaintiff\u0027s attorney would not have terminated the engagement, the defendant\u0027s attorney would not have retained the engineer, and the BER 85-4 ethical question would not have arisen in this form",
"proeth:effect": "Favorable Report Opportunity Foreclosed (BER 85-4) (Event 6)",
"proeth:necessaryFactors": [
"Forensic engineer\u0027s honest professional assessment that a favorable plaintiff report was not supportable",
"Plaintiff attorney\u0027s termination of the engineer following the unfavorable assessment",
"The engineer\u0027s ethical commitment to honest reporting over client-favorable outcomes",
"Existence of the defendant\u0027s attorney as an alternative retaining party"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Forensic Engineer in BER 85-4",
"proeth:sufficientFactors": [
"Honest professional assessment incompatible with plaintiff\u0027s position + termination by plaintiff attorney + availability of defendant retention = sufficient to produce the dual-retention ethical scenario in BER 85-4"
],
"proeth:withinAgentControl": true
}
Causal Language: Through a series of Board of Ethical Review decisions from 1974 through 1985 and beyond, a body of precedent is established that provides the normative and interpretive framework within which Engineer A's confidentiality obligations are defined, scoped, and enforced
Necessary Factors (NESS):
- Existence of prior BER cases presenting analogous conflict-of-interest and confidentiality scenarios
- BER's institutional authority to issue binding or persuasive ethical interpretations
- Applicability of BER precedents to Engineer A's specific fact pattern
- Engineer A's professional obligation to be aware of and comply with established ethical precedents
Sufficient Factors:
- Established BER precedents on confidentiality + analogous fact pattern in Engineer A's case + professional obligation to follow ethical guidance = sufficient normative framework to define Engineer A's obligations with specificity
Responsibility Attribution:
Agent: NSPE Board of Ethical Review (institutional) and Engineer A (compliance obligation)
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Historical BER Cases (1974-1985)
Series of BER decisions address conflict of interest, confidentiality, and dual retention scenarios in engineering practice -
BER Precedent Framework Established (Event 4)
Accumulated decisions create coherent body of ethical guidance with precedential authority -
Framework Applied to Engineer A's Situation
BER precedents from cases 82-6 and 85-4 provide directly applicable guidance on confidentiality obligations in competitive employment and dual-retention scenarios -
Perpetual Confidentiality Obligation Scoped and Defined (Event 3)
The BER framework gives specific content to Engineer A's obligations, clarifying what must be withheld, for how long, and under what circumstances -
Withhold Company X Confidential Information (Action 4)
Engineer A's ongoing non-disclosure decisions are informed and shaped by the BER precedent framework
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/106#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/106#CausalChain_21d0e031",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Through a series of Board of Ethical Review decisions from 1974 through 1985 and beyond, a body of precedent is established that provides the normative and interpretive framework within which Engineer A\u0027s confidentiality obligations are defined, scoped, and enforced",
"proeth:causalSequence": [
{
"proeth:description": "Series of BER decisions address conflict of interest, confidentiality, and dual retention scenarios in engineering practice",
"proeth:element": "Historical BER Cases (1974-1985)",
"proeth:step": 1
},
{
"proeth:description": "Accumulated decisions create coherent body of ethical guidance with precedential authority",
"proeth:element": "BER Precedent Framework Established (Event 4)",
"proeth:step": 2
},
{
"proeth:description": "BER precedents from cases 82-6 and 85-4 provide directly applicable guidance on confidentiality obligations in competitive employment and dual-retention scenarios",
"proeth:element": "Framework Applied to Engineer A\u0027s Situation",
"proeth:step": 3
},
{
"proeth:description": "The BER framework gives specific content to Engineer A\u0027s obligations, clarifying what must be withheld, for how long, and under what circumstances",
"proeth:element": "Perpetual Confidentiality Obligation Scoped and Defined (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "Engineer A\u0027s ongoing non-disclosure decisions are informed and shaped by the BER precedent framework",
"proeth:element": "Withhold Company X Confidential Information (Action 4)",
"proeth:step": 5
}
],
"proeth:cause": "BER Precedent Framework Established (Event 4)",
"proeth:counterfactual": "Without the BER Precedent Framework, Engineer A\u0027s obligations would rest solely on the general text of the NSPE Code, leaving significant ambiguity about scope, duration, and application of confidentiality duties in competitive employment contexts; the framework does not create the obligation but defines its contours",
"proeth:effect": "Perpetual Confidentiality Obligation Activated (Event 3) \u2014 normative grounding",
"proeth:necessaryFactors": [
"Existence of prior BER cases presenting analogous conflict-of-interest and confidentiality scenarios",
"BER\u0027s institutional authority to issue binding or persuasive ethical interpretations",
"Applicability of BER precedents to Engineer A\u0027s specific fact pattern",
"Engineer A\u0027s professional obligation to be aware of and comply with established ethical precedents"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "NSPE Board of Ethical Review (institutional) and Engineer A (compliance obligation)",
"proeth:sufficientFactors": [
"Established BER precedents on confidentiality + analogous fact pattern in Engineer A\u0027s case + professional obligation to follow ethical guidance = sufficient normative framework to define Engineer A\u0027s obligations with specificity"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (10)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| BER Case No. 85-4 |
before
Entity1 is before Entity2 |
current Engineer A case |
time:before
http://www.w3.org/2006/time#before |
The aforementioned cases represent the longstanding BER positions... Shifting to the facts in the cu... [more] |
| Engineer A's access to confidential Company X information |
during
Entity1 occurs entirely within the duration of Entity2 |
Engineer A's tenure at the government agency |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
During Engineer A's tenure with the government agency, Engineer A receives access to confidential an... [more] |
| Engineer A's tenure at the government agency |
before
Entity1 is before Entity2 |
Engineer A's employment with Company Y |
time:before
http://www.w3.org/2006/time#before |
Engineer A ends her employment with the government agency and accepts an engineering position with C... [more] |
| Engineer A's employment at government agency |
meets
Entity1 ends exactly when Entity2 begins |
Engineer A's employment at Company Y |
time:intervalMeets
http://www.w3.org/2006/time#intervalMeets |
Engineer A ends her employment with the government agency and accepts an engineering position with C... [more] |
| Engineer A's initial review and analysis for Attorney Z (BER 85-4) |
before
Entity1 is before Entity2 |
termination of Engineer A's services by Attorney Z |
time:before
http://www.w3.org/2006/time#before |
Following Engineer A's review and analysis, Engineer A determined that he could not provide an engin... [more] |
| termination of Engineer A's services by Attorney Z (BER 85-4) |
before
Entity1 is before Entity2 |
Attorney X retaining Engineer A for the defendant |
time:before
http://www.w3.org/2006/time#before |
Engineer A's services were terminated and his fee was paid in full. Thereafter, Attorney X, represen... [more] |
| BER Case No. 74-2 |
before
Entity1 is before Entity2 |
BER Case No. 82-6 |
time:before
http://www.w3.org/2006/time#before |
Case numbers imply chronological order: 74-2 (circa 1974) precedes 82-6 (circa 1982), as referenced ... [more] |
| BER Case No. 82-6 |
before
Entity1 is before Entity2 |
BER Case No. 85-4 |
time:before
http://www.w3.org/2006/time#before |
Case numbers imply chronological order: 82-6 (circa 1982) precedes 85-4 (circa 1985), as referenced ... [more] |
| Engineer A's confidentiality obligation to Company X |
after
Entity1 is after Entity2 |
Engineer A's tenure at the government agency |
time:after
http://www.w3.org/2006/time#after |
It must be recognized that, while an engineer may not currently have a professional relationship wit... [more] |
| companies submitting confidential design information |
before
Entity1 is before Entity2 |
Engineer A gaining access to that information |
time:before
http://www.w3.org/2006/time#before |
Engineer A receives access to confidential and proprietary design information provided by companies ... [more] |
About Allen Relations & OWL-Time
Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.
Each relation includes both a ProEthica custom property and a
time:* OWL-Time property for maximum compatibility.