36 entities 7 actions 6 events 5 causal chains 17 temporal relations
Timeline Overview
Action Event 13 sequenced markers
Participation in Contract Negotiations During tenure as City Engineer, prior to resignation announcement
Resignation and Partial Disclosure At time of resignation announcement
Accepting Employment with AE&R Prior to or concurrent with resignation announcement; formalized shortly after announcement when AE&R publicly announced the hire
Disclosure and City Acceptance Seeking Post-hire, immediately upon formal transition to AE&R
Voluntary Recusal from City Projects Post-hire, ongoing throughout transition period
Adopting One-Year Cooling-Off Period Post-hire, decision point at commencement of employment at AE&R
AE&R Assigns Engineer D to City Contracts Post-hire, upon Engineer D joining AE&R as associate
Engineer D's Resignation Announced At the point of resignation announcement
AE&R Public Hire Announcement Shortly after Engineer D's resignation announcement
Prior AE&R Contract History Exposed Concurrent with or immediately following AE&R's public hire announcement
Conflict of Interest State Established Upon commencement of Engineer D's employment at AE&R
Cooling-Off Period Obligation Activated Upon commencement of Engineer D's employment at AE&R, with reference to historical BER precedents
City Project Involvement Risk Created Upon AE&R assigning Engineer D to city contracts
OWL-Time Temporal Structure 17 relations time: = w3.org/2006/time
Engineer D's resignation announcement time:before Firm AE&R's announcement of Engineer D as newly hired associate
engineers' resignation from US government (Case 58-1) time:intervalMeets entry into contract with foreign government (Case 58-1)
Engineer B's selection for road project design (Case 11-12) time:before Engineer B beginning preliminary design services (Case 11-12)
Engineer B's termination (Case 11-12) time:before Engineer A's firm offering to perform design work (Case 11-12)
Engineer A's resignation from private firm (Case 14-8) time:intervalDuring legal review of the water rights analysis (Case 14-8)
State X highway department's refusal (Case 15-8) time:before Engineer P joining AE firm as independent contractor (Case 15-8)
one-year cooling-off period (Case 15-8 / Engineer D scenario) time:intervalStarts Engineer D's departure from City Engineer role
Engineer A's employment at private firm (Case 14-8) time:before Engineer A's employment at the State (Case 14-8)
Engineer D's resignation announcement time:before Engineer D accepting position at unnamed firm
AE&R projects for the City time:intervalDuring Engineer D's tenure as City Engineer
contract negotiations by US government engineers (Case 58-1) time:intervalOverlaps engineers' active US government employment (Case 58-1)
Engineer A's review of Engineer B's preliminary work (Case 11-12) time:intervalDuring Engineer B's preliminary design services (Case 11-12)
Engineer A stamping water rights analysis (Case 14-8) time:before legal review of the analysis (Case 14-8)
Engineer P's request for permission to leave (Case 15-8) time:before State X highway department's refusal of permission (Case 15-8)
Engineer D's isolation from former projects time:intervalDuring remaining active duration of former City contracts
confidentiality obligation time:intervalOverlaps Engineer D's post-employment period at AE&R
Engineer D's tenure as City Engineer time:before Engineer D's employment at Firm AE&R
Extracted Actions (7)
Volitional professional decisions with intentions and ethical context

Description: Engineer D made the volitional decision to accept a position as associate at Firm AE&R — a firm that had completed many projects under Engineer D's direct oversight as City Engineer. This decision represents the core revolving-door action that crystallizes all subsequent conflict-of-interest obligations.

Temporal Marker: Prior to or concurrent with resignation announcement; formalized shortly after announcement when AE&R publicly announced the hire

Mental State: deliberate

Intended Outcome: Advance private-sector career by joining an established AE firm with which Engineer D had a substantial working relationship, leveraging professional reputation and experience

Fulfills Obligations:
  • Legitimate exercise of the right to seek and accept private employment (affirmed in Case 58-1)
  • Pursuit of professional advancement within one's area of competence
Guided By Principles:
  • Avoidance of conflicts of interest
  • Protection of public trust in engineering profession
  • Confidentiality of information obtained in professional capacity
  • Ethical spirit of revolving door provisions even absent legal mandate
Required Capabilities:
Self-assessment of conflict-of-interest exposure Knowledge of post-employment ethical obligations Ability to identify which city matters require recusal or disclosure
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Career advancement, financial opportunity, and professional recognition are the primary motivations. AE&R likely offered Engineer D a position precisely because of the insider knowledge, municipal relationships, and credibility accumulated during public service — and Engineer D accepted because the offer represented a logical and lucrative career progression. There is no indication of corrupt intent, which makes this scenario particularly instructive: ethically problematic revolving-door situations frequently arise from entirely understandable personal motivations.

Ethical Tension: Engineers have the right to pursue private employment and advance their careers. Yet NSPE Code obligations — particularly regarding conflicts of interest, confidentiality, and public trust — do not terminate at the moment of resignation. The tension is between individual economic liberty and the structural integrity of public procurement. There is also tension between AE&R's legitimate business interest in hiring experienced talent and the public's interest in preventing the commodification of insider governmental access.

Learning Significance: This is the central revolving-door case study moment. Students learn that accepting private employment with a firm one has regulated or overseen is not automatically unethical, but it triggers a cascade of affirmative obligations — disclosure, recusal, cooling-off — that must be honored. The action itself is the fulcrum on which all subsequent ethical analysis turns.

Stakes: The integrity of all prior contract awards involving AE&R may be called into question retroactively. Future city contracts involving AE&R gain an unfair competitive advantage if Engineer D participates. Public confidence in municipal procurement is at risk. Engineer D's professional license and reputation are at risk. AE&R's standing as a reputable firm is at risk if the hire is perceived as purchasing governmental access.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline the AE&R offer and accept a position with a firm that has no prior relationship with the municipality
  • Accept the AE&R offer but only after a self-imposed waiting period following departure from city employment, reducing the recency and potency of insider knowledge
  • Accept the offer contingent on negotiating explicit contractual terms with AE&R that prohibit Engineer D's involvement in any city-related work for a defined period

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_Accepting_Employment_with_AE_R",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the AE\u0026R offer and accept a position with a firm that has no prior relationship with the municipality",
    "Accept the AE\u0026R offer but only after a self-imposed waiting period following departure from city employment, reducing the recency and potency of insider knowledge",
    "Accept the offer contingent on negotiating explicit contractual terms with AE\u0026R that prohibit Engineer D\u0027s involvement in any city-related work for a defined period"
  ],
  "proeth-scenario:characterMotivation": "Career advancement, financial opportunity, and professional recognition are the primary motivations. AE\u0026R likely offered Engineer D a position precisely because of the insider knowledge, municipal relationships, and credibility accumulated during public service \u2014 and Engineer D accepted because the offer represented a logical and lucrative career progression. There is no indication of corrupt intent, which makes this scenario particularly instructive: ethically problematic revolving-door situations frequently arise from entirely understandable personal motivations.",
  "proeth-scenario:consequencesIfAlternative": [
    "Avoiding AE\u0026R entirely eliminates the conflict but may represent an unnecessary sacrifice of legitimate career opportunity \u2014 it is the most conservative but not necessarily the ethically required choice",
    "A voluntary waiting period reduces but does not eliminate the conflict; it signals good faith and allows institutional memory to fade, but does not address the confidentiality obligations regarding specific project knowledge",
    "Negotiating explicit recusal terms before accepting the offer is arguably the most ethically sophisticated choice \u2014 it creates contractual accountability, protects both parties, and demonstrates proactive conflict management rather than reactive damage control"
  ],
  "proeth-scenario:decisionSignificance": "This is the central revolving-door case study moment. Students learn that accepting private employment with a firm one has regulated or overseen is not automatically unethical, but it triggers a cascade of affirmative obligations \u2014 disclosure, recusal, cooling-off \u2014 that must be honored. The action itself is the fulcrum on which all subsequent ethical analysis turns.",
  "proeth-scenario:ethicalTension": "Engineers have the right to pursue private employment and advance their careers. Yet NSPE Code obligations \u2014 particularly regarding conflicts of interest, confidentiality, and public trust \u2014 do not terminate at the moment of resignation. The tension is between individual economic liberty and the structural integrity of public procurement. There is also tension between AE\u0026R\u0027s legitimate business interest in hiring experienced talent and the public\u0027s interest in preventing the commodification of insider governmental access.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The integrity of all prior contract awards involving AE\u0026R may be called into question retroactively. Future city contracts involving AE\u0026R gain an unfair competitive advantage if Engineer D participates. Public confidence in municipal procurement is at risk. Engineer D\u0027s professional license and reputation are at risk. AE\u0026R\u0027s standing as a reputable firm is at risk if the hire is perceived as purchasing governmental access.",
  "proeth:description": "Engineer D made the volitional decision to accept a position as associate at Firm AE\u0026R \u2014 a firm that had completed many projects under Engineer D\u0027s direct oversight as City Engineer. This decision represents the core revolving-door action that crystallizes all subsequent conflict-of-interest obligations.",
  "proeth:foreseenUnintendedEffects": [
    "Creation of direct conflict of interest between former public duties and new private role",
    "Potential exploitation \u2014 actual or perceived \u2014 of insider knowledge and city relationships",
    "Triggering of revolving door ethical scrutiny and potential cooling-off obligations",
    "Reputational risk to both Engineer D and AE\u0026R if transition is not managed transparently"
  ],
  "proeth:fulfillsObligation": [
    "Legitimate exercise of the right to seek and accept private employment (affirmed in Case 58-1)",
    "Pursuit of professional advancement within one\u0027s area of competence"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflicts of interest",
    "Protection of public trust in engineering profession",
    "Confidentiality of information obtained in professional capacity",
    "Ethical spirit of revolving door provisions even absent legal mandate"
  ],
  "proeth:hasAgent": "Engineer D (City Engineer, transitioning to AE\u0026R Associate)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Engineer\u0027s right to employment vs. public interest in preventing exploitation of insider access",
    "proeth:resolutionReasoning": "While legally permissible, the ethical weight of the public interest obligations requires that this decision be accompanied by robust mitigation measures \u2014 full disclosure, voluntary recusal from conflicted matters, and adherence to a cooling-off period \u2014 rather than treated as unconditionally acceptable"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Advance private-sector career by joining an established AE firm with which Engineer D had a substantial working relationship, leveraging professional reputation and experience",
  "proeth:requiresCapability": [
    "Self-assessment of conflict-of-interest exposure",
    "Knowledge of post-employment ethical obligations",
    "Ability to identify which city matters require recusal or disclosure"
  ],
  "proeth:temporalMarker": "Prior to or concurrent with resignation announcement; formalized shortly after announcement when AE\u0026R publicly announced the hire",
  "proeth:violatesObligation": [
    "Obligation to avoid conflicts of interest that compromise integrity or the public interest (NSPE Code Section II.4)",
    "Obligation to avoid circumstances where private interest conflicts with public duties (NSPE Code Section III.2)",
    "Duty to protect confidential information obtained in public role from exploitation in private role",
    "Obligation to avoid the appearance of impropriety in the transition from public to private employment"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accepting Employment with AE\u0026R"
}

Description: Post-hire, Engineer D faces the implied decision of whether to proactively seek full disclosure of the conflict to the City and obtain the City's acceptance of Engineer D's participation in city-related matters at AE&R. This is a forward-looking volitional choice with significant ethical weight.

Temporal Marker: Post-hire, immediately upon formal transition to AE&R

Mental State: deliberate (implied obligation)

Intended Outcome: Cure or mitigate the conflict of interest by obtaining informed consent from the City, thereby enabling Engineer D to potentially contribute to city-related work at AE&R without ongoing ethical violation

Fulfills Obligations:
  • NSPE Code Section II.4(a) — obligation to disclose all known or potential conflicts of interest to employer and clients
  • Duty of transparency to former public employer
  • Obligation to protect public interest by enabling informed oversight
Guided By Principles:
  • Full and timely disclosure as a foundational conflict-management tool
  • Transparency
  • Faithful agency to all affected parties
  • Public interest protection
Required Capabilities:
Conflict-of-interest analysis Knowledge of city procurement matters and Engineer D's prior involvement Professional ethics judgment Communication with former employer
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer D may be motivated by a genuine desire to comply with ethical obligations, or alternatively by a desire to obtain institutional 'permission' that provides cover for continued involvement in city matters. The motivation matters ethically: disclosure sought in good faith to enable genuine recusal decisions is categorically different from disclosure sought strategically to manufacture consent for ongoing participation.

Ethical Tension: NSPE Code provisions require engineers to disclose conflicts and obtain consent from affected parties before proceeding. Yet the disclosure obligation exists in tension with the adequacy of consent: can a city meaningfully 'accept' Engineer D's participation in matters where the city itself may not fully understand the depth of Engineer D's insider knowledge? There is also tension between procedural compliance (disclosure made = obligation fulfilled) and substantive ethics (disclosure made but conflict remains real).

Learning Significance: Teaches students that disclosure is necessary but not sufficient — it is a prerequisite for ethical participation, not a license for it. Students also learn to analyze the quality and completeness of disclosure, the capacity of the receiving party to give informed consent, and the difference between disclosing a conflict and resolving one.

Stakes: If disclosure is not made, Engineer D operates in ongoing violation of conflict-of-interest obligations, exposing both Engineer D and AE&R to professional discipline, legal liability, and reputational harm. If disclosure is made but the city's acceptance is uninformed or coerced, the ethical problem persists beneath a procedural veneer. If disclosure is made fully and the city withholds acceptance, Engineer D has a clear obligation to recuse entirely.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Make no disclosure and rely on the assumption that departure from city employment automatically terminates conflict obligations
  • Make disclosure to the city but simultaneously advocate for the city's acceptance, framing the conflict as manageable rather than presenting it neutrally
  • Make full written disclosure to the city, document the city's response, and allow the city to make an uninfluenced determination without Engineer D's advocacy

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_Disclosure_and_City_Acceptance_Seeking",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Make no disclosure and rely on the assumption that departure from city employment automatically terminates conflict obligations",
    "Make disclosure to the city but simultaneously advocate for the city\u0027s acceptance, framing the conflict as manageable rather than presenting it neutrally",
    "Make full written disclosure to the city, document the city\u0027s response, and allow the city to make an uninfluenced determination without Engineer D\u0027s advocacy"
  ],
  "proeth-scenario:characterMotivation": "Engineer D may be motivated by a genuine desire to comply with ethical obligations, or alternatively by a desire to obtain institutional \u0027permission\u0027 that provides cover for continued involvement in city matters. The motivation matters ethically: disclosure sought in good faith to enable genuine recusal decisions is categorically different from disclosure sought strategically to manufacture consent for ongoing participation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Failing to disclose is a clear NSPE Code violation and exposes Engineer D to disciplinary action; it also leaves AE\u0026R vulnerable to contract challenges if the conflict is later discovered",
    "Advocacy-laden disclosure compromises the integrity of the consent process; the city\u0027s \u0027acceptance\u0027 under such circumstances may not constitute genuine informed consent and would not provide ethical cover",
    "Full neutral written disclosure with documented response is the most defensible approach \u2014 it satisfies the letter and spirit of disclosure obligations and creates a clear record for any future review"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that disclosure is necessary but not sufficient \u2014 it is a prerequisite for ethical participation, not a license for it. Students also learn to analyze the quality and completeness of disclosure, the capacity of the receiving party to give informed consent, and the difference between disclosing a conflict and resolving one.",
  "proeth-scenario:ethicalTension": "NSPE Code provisions require engineers to disclose conflicts and obtain consent from affected parties before proceeding. Yet the disclosure obligation exists in tension with the adequacy of consent: can a city meaningfully \u0027accept\u0027 Engineer D\u0027s participation in matters where the city itself may not fully understand the depth of Engineer D\u0027s insider knowledge? There is also tension between procedural compliance (disclosure made = obligation fulfilled) and substantive ethics (disclosure made but conflict remains real).",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If disclosure is not made, Engineer D operates in ongoing violation of conflict-of-interest obligations, exposing both Engineer D and AE\u0026R to professional discipline, legal liability, and reputational harm. If disclosure is made but the city\u0027s acceptance is uninformed or coerced, the ethical problem persists beneath a procedural veneer. If disclosure is made fully and the city withholds acceptance, Engineer D has a clear obligation to recuse entirely.",
  "proeth:description": "Post-hire, Engineer D faces the implied decision of whether to proactively seek full disclosure of the conflict to the City and obtain the City\u0027s acceptance of Engineer D\u0027s participation in city-related matters at AE\u0026R. This is a forward-looking volitional choice with significant ethical weight.",
  "proeth:foreseenUnintendedEffects": [
    "City may decline to accept the conflict, restricting Engineer D\u0027s role at AE\u0026R more severely than anticipated",
    "Disclosure may trigger formal procurement restrictions or legal review",
    "Failure to seek disclosure leaves Engineer D in ongoing ethical violation if participating in city matters"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code Section II.4(a) \u2014 obligation to disclose all known or potential conflicts of interest to employer and clients",
    "Duty of transparency to former public employer",
    "Obligation to protect public interest by enabling informed oversight"
  ],
  "proeth:guidedByPrinciple": [
    "Full and timely disclosure as a foundational conflict-management tool",
    "Transparency",
    "Faithful agency to all affected parties",
    "Public interest protection"
  ],
  "proeth:hasAgent": "Engineer D (AE\u0026R Associate, former City Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Full disclosure as conflict cure vs. situations where conflict is too entrenched for disclosure to suffice",
    "proeth:resolutionReasoning": "Disclosure is a necessary but not always sufficient step; for matters where Engineer D had direct procurement authority or supervisory responsibility, recusal or cooling-off may be required even after disclosure, because the conflict may be too structural to cure through consent alone"
  },
  "proeth:hasMentalState": "deliberate (implied obligation)",
  "proeth:intendedOutcome": "Cure or mitigate the conflict of interest by obtaining informed consent from the City, thereby enabling Engineer D to potentially contribute to city-related work at AE\u0026R without ongoing ethical violation",
  "proeth:requiresCapability": [
    "Conflict-of-interest analysis",
    "Knowledge of city procurement matters and Engineer D\u0027s prior involvement",
    "Professional ethics judgment",
    "Communication with former employer"
  ],
  "proeth:temporalMarker": "Post-hire, immediately upon formal transition to AE\u0026R",
  "proeth:violatesObligation": [
    "If disclosure is not sought: ongoing violation of conflict-of-interest obligations",
    "If disclosure is sought but incomplete: partial fulfillment insufficient to cure conflict"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Disclosure and City Acceptance Seeking"
}

Description: Post-hire, Engineer D faces the implied decision of whether to voluntarily recuse from all active city projects that were formerly under Engineer D's oversight as City Engineer, regardless of whether disclosure has been made or accepted. This represents an independent ethical obligation distinct from the cooling-off question.

Temporal Marker: Post-hire, ongoing throughout transition period

Mental State: deliberate (implied ethical obligation)

Intended Outcome: Prevent exploitation of insider knowledge and supervisory relationships in private-sector work on the same projects Engineer D previously managed publicly, protecting both the City's interests and the integrity of the engineering profession

Fulfills Obligations:
  • Obligation to avoid conflicts of interest that compromise professional integrity
  • Duty to protect confidential information obtained in public role
  • Obligation to preserve public trust in municipal engineering processes
  • Faithful agency to former public employer/client through non-exploitation of insider access
Guided By Principles:
  • Avoidance of conflicts of interest
  • Confidentiality
  • Objectivity and impartiality
  • Protection of public interest
Required Capabilities:
Identification of which projects create direct conflicts Professional discipline to self-impose recusal Communication with AE&R management about scope limitations
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Voluntary recusal requires Engineer D to subordinate financial and professional interests at AE&R to ethical obligations — a genuinely costly choice. The motivation to recuse stems from internalized professional ethics, concern for reputation, and recognition that participation in formerly supervised projects creates an unjustifiable appearance of impropriety regardless of actual intent. Resistance to recusal is motivated by the value Engineer D brings to those specific projects and AE&R's likely expectation that Engineer D's city relationships will be commercially leveraged.

Ethical Tension: The tension is between Engineer D's value to AE&R (which is partly predicated on city relationships and project knowledge) and the ethical obligation to avoid exploiting public-service insider access for private gain. There is also tension between the absence of a legal mandate for recusal and the presence of a clear ethical mandate — students must grapple with the gap between what is legally required and what professional ethics demand.

Learning Significance: Illustrates the principle that ethical obligations can exceed legal requirements, and that the absence of a law prohibiting conduct does not make that conduct ethically permissible. Students learn to apply the 'appearance of impropriety' standard and to understand recusal as an affirmative duty, not merely a reactive response to discovered conflicts.

Stakes: If Engineer D participates in active city projects at AE&R without recusal, the integrity of those projects is compromised, the city's interests may be subordinated to AE&R's, and other competing firms are disadvantaged. Engineer D's prior supervisory role means that participation constitutes a de facto exploitation of public trust for private commercial benefit.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Participate fully in all city projects at AE&R, reasoning that departure from city employment terminated all obligations
  • Participate in city projects only in an advisory or background capacity, without direct client contact or decision-making authority
  • Recuse from all projects that were active during Engineer D's tenure but participate in new city projects initiated after departure

Narrative Role: falling_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_Voluntary_Recusal_from_City_Projects",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Participate fully in all city projects at AE\u0026R, reasoning that departure from city employment terminated all obligations",
    "Participate in city projects only in an advisory or background capacity, without direct client contact or decision-making authority",
    "Recuse from all projects that were active during Engineer D\u0027s tenure but participate in new city projects initiated after departure"
  ],
  "proeth-scenario:characterMotivation": "Voluntary recusal requires Engineer D to subordinate financial and professional interests at AE\u0026R to ethical obligations \u2014 a genuinely costly choice. The motivation to recuse stems from internalized professional ethics, concern for reputation, and recognition that participation in formerly supervised projects creates an unjustifiable appearance of impropriety regardless of actual intent. Resistance to recusal is motivated by the value Engineer D brings to those specific projects and AE\u0026R\u0027s likely expectation that Engineer D\u0027s city relationships will be commercially leveraged.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full participation without recusal is a clear ethical violation under NSPE standards and would likely constitute grounds for disciplinary action; it also exposes AE\u0026R to contract integrity challenges",
    "Background participation is ethically insufficient \u2014 the conflict of interest inheres in the knowledge and relationships Engineer D brings, not merely in the visibility of Engineer D\u0027s role",
    "Limiting recusal to active projects while participating in new ones is a reasonable middle position but requires careful analysis of whether \u0027new\u0027 projects genuinely lack connection to Engineer D\u0027s prior insider knowledge"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the principle that ethical obligations can exceed legal requirements, and that the absence of a law prohibiting conduct does not make that conduct ethically permissible. Students learn to apply the \u0027appearance of impropriety\u0027 standard and to understand recusal as an affirmative duty, not merely a reactive response to discovered conflicts.",
  "proeth-scenario:ethicalTension": "The tension is between Engineer D\u0027s value to AE\u0026R (which is partly predicated on city relationships and project knowledge) and the ethical obligation to avoid exploiting public-service insider access for private gain. There is also tension between the absence of a legal mandate for recusal and the presence of a clear ethical mandate \u2014 students must grapple with the gap between what is legally required and what professional ethics demand.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If Engineer D participates in active city projects at AE\u0026R without recusal, the integrity of those projects is compromised, the city\u0027s interests may be subordinated to AE\u0026R\u0027s, and other competing firms are disadvantaged. Engineer D\u0027s prior supervisory role means that participation constitutes a de facto exploitation of public trust for private commercial benefit.",
  "proeth:description": "Post-hire, Engineer D faces the implied decision of whether to voluntarily recuse from all active city projects that were formerly under Engineer D\u0027s oversight as City Engineer, regardless of whether disclosure has been made or accepted. This represents an independent ethical obligation distinct from the cooling-off question.",
  "proeth:foreseenUnintendedEffects": [
    "Reduced immediate value to AE\u0026R if Engineer D cannot work on the firm\u0027s most significant city contracts",
    "Potential resentment from AE\u0026R principals who expected Engineer D to contribute to city project work",
    "Demonstrates professional integrity that may enhance long-term reputation"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to avoid conflicts of interest that compromise professional integrity",
    "Duty to protect confidential information obtained in public role",
    "Obligation to preserve public trust in municipal engineering processes",
    "Faithful agency to former public employer/client through non-exploitation of insider access"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflicts of interest",
    "Confidentiality",
    "Objectivity and impartiality",
    "Protection of public interest"
  ],
  "proeth:hasAgent": "Engineer D (AE\u0026R Associate, former City Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Continuity and efficiency of city project work vs. objectivity and fairness concerns from former official\u0027s private involvement",
    "proeth:resolutionReasoning": "Short-term efficiency gains from Engineer D\u0027s involvement in active city projects do not outweigh the structural conflict created by a former public official privately overseeing work they previously managed publicly; recusal is the ethically required resolution"
  },
  "proeth:hasMentalState": "deliberate (implied ethical obligation)",
  "proeth:intendedOutcome": "Prevent exploitation of insider knowledge and supervisory relationships in private-sector work on the same projects Engineer D previously managed publicly, protecting both the City\u0027s interests and the integrity of the engineering profession",
  "proeth:requiresCapability": [
    "Identification of which projects create direct conflicts",
    "Professional discipline to self-impose recusal",
    "Communication with AE\u0026R management about scope limitations"
  ],
  "proeth:temporalMarker": "Post-hire, ongoing throughout transition period",
  "proeth:violatesObligation": [
    "If recusal is not adopted: violation of conflict-of-interest obligations and confidentiality duties",
    "Potential violation of objectivity and impartiality standards"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Voluntary Recusal from City Projects"
}

Description: Post-hire, Engineer D faces the implied decision of whether to voluntarily adopt an approximately one-year cooling-off period before participating in any procurement matters before the City, mirroring the ethical spirit of statutory cooling-off provisions even in the absence of a legal mandate.

Temporal Marker: Post-hire, decision point at commencement of employment at AE&R

Mental State: deliberate (implied ethical obligation informed by BER precedent)

Intended Outcome: Prevent the exploitation of insider relationships and procurement influence for a sufficient period to allow the City's procurement processes to operate without the distorting effect of Engineer D's recent public authority, thereby protecting both the public interest and the profession's integrity

Fulfills Obligations:
  • Obligation to uphold the ethical spirit of revolving door provisions
  • Duty to protect the public interest in fair procurement
  • Obligation to avoid exploitation of insider contacts and influence gained in public service
  • Consistency with BER precedent (Case 15-8) on cooling-off obligations
Guided By Principles:
  • Ethical obligations exceed minimum legal requirements
  • Avoidance of conflicts of interest
  • Protection of public trust
  • Consistency with established BER ethical precedent
Required Capabilities:
Self-discipline to observe voluntary ethical constraints Ability to identify which activities constitute 'procurement matters' subject to the cooling-off Communication with AE&R management to establish and enforce the cooling-off boundary
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Adopting a voluntary cooling-off period requires Engineer D to accept a significant short-term professional constraint in service of long-term ethical integrity and public trust. The motivation to adopt such a period comes from genuine commitment to the spirit of conflict-of-interest law and recognition that the revolving door problem is structural, not merely transactional. Resistance is motivated by AE&R's commercial interest in immediately leveraging Engineer D's municipal access and relationships.

Ethical Tension: The cooling-off period addresses the temporal dimension of the conflict: even after full disclosure and recusal from specific projects, Engineer D's recent insider status creates an ongoing informational and relational advantage in procurement contexts. The tension is between the legitimate competitive value of Engineer D's experience and the illegitimate advantage derived from recent governmental authority. There is also tension between voluntary ethical compliance and the absence of a legal mandate — why adopt a restriction the law does not require?

Learning Significance: Introduces students to the concept of the 'spirit vs. letter' of ethical rules and the role of voluntary self-regulation in professional ethics. The BER's historical analysis of cooling-off periods (from Case 58-1 through Case 15-8) provides a rich precedential backdrop for discussing how the profession has evolved its understanding of post-employment obligations. Students learn that ethical maturity involves exceeding minimum compliance.

Stakes: Without a cooling-off period, Engineer D's participation in procurement matters exploits the recency of governmental authority — competitors who lack this insider access are structurally disadvantaged, and the city's procurement process is distorted. With a cooling-off period, Engineer D foregoes short-term commercial opportunity but preserves long-term professional credibility and the integrity of the public procurement system.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Reject the cooling-off concept entirely, reasoning that departure from city employment immediately terminates all procurement-related restrictions
  • Adopt a shorter cooling-off period (e.g., 90 days) that satisfies a minimal ethical threshold without imposing the full one-year constraint
  • Adopt the one-year cooling-off period but negotiate with AE&R for compensation that offsets the commercial cost of the restriction, making the ethical choice economically viable

Narrative Role: falling_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_Adopting_One-Year_Cooling-Off_Period",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Reject the cooling-off concept entirely, reasoning that departure from city employment immediately terminates all procurement-related restrictions",
    "Adopt a shorter cooling-off period (e.g., 90 days) that satisfies a minimal ethical threshold without imposing the full one-year constraint",
    "Adopt the one-year cooling-off period but negotiate with AE\u0026R for compensation that offsets the commercial cost of the restriction, making the ethical choice economically viable"
  ],
  "proeth-scenario:characterMotivation": "Adopting a voluntary cooling-off period requires Engineer D to accept a significant short-term professional constraint in service of long-term ethical integrity and public trust. The motivation to adopt such a period comes from genuine commitment to the spirit of conflict-of-interest law and recognition that the revolving door problem is structural, not merely transactional. Resistance is motivated by AE\u0026R\u0027s commercial interest in immediately leveraging Engineer D\u0027s municipal access and relationships.",
  "proeth-scenario:consequencesIfAlternative": [
    "Rejecting the cooling-off period entirely leaves Engineer D and AE\u0026R exposed to ethical complaints and reputational damage; it also signals that the hire was intended to exploit governmental access, which is the precise concern cooling-off periods are designed to address",
    "A shortened cooling-off period may be insufficient given the depth and recency of Engineer D\u0027s insider knowledge and relationships; it risks being perceived as a token gesture rather than genuine ethical compliance",
    "Negotiating compensated recusal is a sophisticated and ethically sound approach \u2014 it aligns incentives, makes compliance sustainable, and demonstrates that AE\u0026R values Engineer D for long-term professional merit rather than short-term governmental access"
  ],
  "proeth-scenario:decisionSignificance": "Introduces students to the concept of the \u0027spirit vs. letter\u0027 of ethical rules and the role of voluntary self-regulation in professional ethics. The BER\u0027s historical analysis of cooling-off periods (from Case 58-1 through Case 15-8) provides a rich precedential backdrop for discussing how the profession has evolved its understanding of post-employment obligations. Students learn that ethical maturity involves exceeding minimum compliance.",
  "proeth-scenario:ethicalTension": "The cooling-off period addresses the temporal dimension of the conflict: even after full disclosure and recusal from specific projects, Engineer D\u0027s recent insider status creates an ongoing informational and relational advantage in procurement contexts. The tension is between the legitimate competitive value of Engineer D\u0027s experience and the illegitimate advantage derived from recent governmental authority. There is also tension between voluntary ethical compliance and the absence of a legal mandate \u2014 why adopt a restriction the law does not require?",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Without a cooling-off period, Engineer D\u0027s participation in procurement matters exploits the recency of governmental authority \u2014 competitors who lack this insider access are structurally disadvantaged, and the city\u0027s procurement process is distorted. With a cooling-off period, Engineer D foregoes short-term commercial opportunity but preserves long-term professional credibility and the integrity of the public procurement system.",
  "proeth:description": "Post-hire, Engineer D faces the implied decision of whether to voluntarily adopt an approximately one-year cooling-off period before participating in any procurement matters before the City, mirroring the ethical spirit of statutory cooling-off provisions even in the absence of a legal mandate.",
  "proeth:foreseenUnintendedEffects": [
    "Delayed contribution to AE\u0026R\u0027s city-related business development for approximately one year",
    "Potential competitive disadvantage for AE\u0026R relative to firms not subject to such constraints",
    "Establishes a clear, defensible ethical boundary that protects Engineer D from future allegations of impropriety"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to uphold the ethical spirit of revolving door provisions",
    "Duty to protect the public interest in fair procurement",
    "Obligation to avoid exploitation of insider contacts and influence gained in public service",
    "Consistency with BER precedent (Case 15-8) on cooling-off obligations"
  ],
  "proeth:guidedByPrinciple": [
    "Ethical obligations exceed minimum legal requirements",
    "Avoidance of conflicts of interest",
    "Protection of public trust",
    "Consistency with established BER ethical precedent"
  ],
  "proeth:hasAgent": "Engineer D (AE\u0026R Associate, former City Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Timeliness of Engineer D\u0027s contribution to AE\u0026R vs. ethical need for cooling-off embargo on city procurement",
    "proeth:resolutionReasoning": "The absence of a legal prohibition does not eliminate the ethical obligation; BER precedent and NSPE Code principles establish that the ethical standard exceeds the legal minimum, requiring a voluntary cooling-off period of approximately one year before Engineer D participates in city procurement matters"
  },
  "proeth:hasMentalState": "deliberate (implied ethical obligation informed by BER precedent)",
  "proeth:intendedOutcome": "Prevent the exploitation of insider relationships and procurement influence for a sufficient period to allow the City\u0027s procurement processes to operate without the distorting effect of Engineer D\u0027s recent public authority, thereby protecting both the public interest and the profession\u0027s integrity",
  "proeth:requiresCapability": [
    "Self-discipline to observe voluntary ethical constraints",
    "Ability to identify which activities constitute \u0027procurement matters\u0027 subject to the cooling-off",
    "Communication with AE\u0026R management to establish and enforce the cooling-off boundary"
  ],
  "proeth:temporalMarker": "Post-hire, decision point at commencement of employment at AE\u0026R",
  "proeth:violatesObligation": [
    "If cooling-off is not adopted: violation of the ethical spirit of revolving door principles, even if no legal violation occurs",
    "Risk of violating NSPE Code conflict-of-interest provisions through participation in city procurement matters"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Adopting One-Year Cooling-Off Period"
}

Description: AE&R principals face the implied decision of whether to place Engineer D in responsible charge of active city contracts, a decision that would directly exploit Engineer D's insider knowledge and prior supervisory relationships in violation of conflict-of-interest principles.

Temporal Marker: Post-hire, upon Engineer D joining AE&R as associate

Mental State: deliberate

Intended Outcome: Maximize the return on hiring Engineer D by deploying their expertise and city relationships on active and prospective city contracts, leveraging insider knowledge for competitive advantage

Guided By Principles:
  • Avoidance of conflicts of interest
  • Protection of public trust
  • Professional integrity in procurement
  • Ethical obligations of firms as well as individual engineers
Required Capabilities:
Conflict-of-interest identification at the firm level Project assignment decisions that account for ethical constraints Internal compliance and ethics management
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: AE&R's principals are motivated by commercial logic: Engineer D's insider knowledge, existing relationships with city staff, and familiarity with active project details represent immediate competitive and operational value. Assigning Engineer D to city contracts maximizes the return on the hiring investment. This motivation is not corrupt in isolation — firms routinely hire experienced professionals for their relevant expertise — but becomes ethically impermissible when that expertise derives from recent regulatory or supervisory authority over the same firm.

Ethical Tension: AE&R has a legitimate business interest in utilizing its employees' skills and experience. However, assigning Engineer D to city contracts directly exploits the structural advantage created by the revolving door — converting public-service insider access into private commercial gain. The tension is between the firm's fiduciary duty to its principals (maximize value from the hire) and its professional ethical obligations not to exploit conflicts of interest or compromise the integrity of public procurement.

Learning Significance: Expands the ethical analysis beyond the individual engineer to the organizational level. Students learn that firms, not just individual engineers, bear ethical obligations under NSPE standards, and that enabling a conflict of interest is itself an ethical violation even if the firm is not the primary actor. This action also illustrates how organizational incentives can pressure individuals to compromise their ethical obligations post-transition.

Stakes: If AE&R assigns Engineer D to city contracts, the firm becomes complicit in the conflict-of-interest violation and exposes itself to contract challenges, debarment proceedings, and reputational damage. The city's procurement integrity is directly compromised. Other competing firms are unfairly disadvantaged. Engineer D faces professional discipline. The broader professional community's trust in the integrity of public-private transitions is eroded.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • AE&R proactively implements an internal firewall, prohibiting Engineer D from any involvement — direct or advisory — in city-related matters for the duration of the cooling-off period
  • AE&R assigns Engineer D exclusively to non-municipal projects, leveraging Engineer D's technical expertise while avoiding the conflict-of-interest problem entirely
  • AE&R consults its own ethics counsel and establishes a formal conflict-of-interest management plan for Engineer D's transition, documented and disclosed to the city, before making any project assignments

Narrative Role: resolution

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_AE_R_Assigns_Engineer_D_to_City_Contracts",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "AE\u0026R proactively implements an internal firewall, prohibiting Engineer D from any involvement \u2014 direct or advisory \u2014 in city-related matters for the duration of the cooling-off period",
    "AE\u0026R assigns Engineer D exclusively to non-municipal projects, leveraging Engineer D\u0027s technical expertise while avoiding the conflict-of-interest problem entirely",
    "AE\u0026R consults its own ethics counsel and establishes a formal conflict-of-interest management plan for Engineer D\u0027s transition, documented and disclosed to the city, before making any project assignments"
  ],
  "proeth-scenario:characterMotivation": "AE\u0026R\u0027s principals are motivated by commercial logic: Engineer D\u0027s insider knowledge, existing relationships with city staff, and familiarity with active project details represent immediate competitive and operational value. Assigning Engineer D to city contracts maximizes the return on the hiring investment. This motivation is not corrupt in isolation \u2014 firms routinely hire experienced professionals for their relevant expertise \u2014 but becomes ethically impermissible when that expertise derives from recent regulatory or supervisory authority over the same firm.",
  "proeth-scenario:consequencesIfAlternative": [
    "An internal firewall is a recognized best practice in conflict-of-interest management \u2014 it protects the firm, Engineer D, and the city, and signals institutional commitment to ethical compliance beyond minimum legal requirements",
    "Assigning Engineer D to non-municipal work is the most conservative and operationally clean solution; it eliminates the conflict entirely but may underutilize Engineer D\u0027s most directly relevant experience in the short term",
    "A formal documented conflict management plan developed with ethics counsel is the most sophisticated organizational response \u2014 it creates accountability, demonstrates good faith, and provides a defensible record if the arrangement is later scrutinized"
  ],
  "proeth-scenario:decisionSignificance": "Expands the ethical analysis beyond the individual engineer to the organizational level. Students learn that firms, not just individual engineers, bear ethical obligations under NSPE standards, and that enabling a conflict of interest is itself an ethical violation even if the firm is not the primary actor. This action also illustrates how organizational incentives can pressure individuals to compromise their ethical obligations post-transition.",
  "proeth-scenario:ethicalTension": "AE\u0026R has a legitimate business interest in utilizing its employees\u0027 skills and experience. However, assigning Engineer D to city contracts directly exploits the structural advantage created by the revolving door \u2014 converting public-service insider access into private commercial gain. The tension is between the firm\u0027s fiduciary duty to its principals (maximize value from the hire) and its professional ethical obligations not to exploit conflicts of interest or compromise the integrity of public procurement.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "If AE\u0026R assigns Engineer D to city contracts, the firm becomes complicit in the conflict-of-interest violation and exposes itself to contract challenges, debarment proceedings, and reputational damage. The city\u0027s procurement integrity is directly compromised. Other competing firms are unfairly disadvantaged. Engineer D faces professional discipline. The broader professional community\u0027s trust in the integrity of public-private transitions is eroded.",
  "proeth:description": "AE\u0026R principals face the implied decision of whether to place Engineer D in responsible charge of active city contracts, a decision that would directly exploit Engineer D\u0027s insider knowledge and prior supervisory relationships in violation of conflict-of-interest principles.",
  "proeth:foreseenUnintendedEffects": [
    "Exposure of AE\u0026R to ethical and reputational risk if the conflict is publicly scrutinized",
    "Potential disqualification from city contracts if the City identifies the conflict",
    "Contribution to the perception that the engineering profession exploits revolving door relationships"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflicts of interest",
    "Protection of public trust",
    "Professional integrity in procurement",
    "Ethical obligations of firms as well as individual engineers"
  ],
  "proeth:hasAgent": "AE\u0026R Principals (private AE firm leadership)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "AE\u0026R\u0027s business interest in leveraging Engineer D\u0027s insider access vs. ethical obligation to avoid exploiting revolving door relationships",
    "proeth:resolutionReasoning": "AE\u0026R\u0027s short-term competitive interest does not justify exploiting Engineer D\u0027s insider relationships; the firm has an independent ethical obligation to isolate Engineer D from conflicted city matters and should not use the hire as a vehicle for gaining unfair procurement advantage"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maximize the return on hiring Engineer D by deploying their expertise and city relationships on active and prospective city contracts, leveraging insider knowledge for competitive advantage",
  "proeth:requiresCapability": [
    "Conflict-of-interest identification at the firm level",
    "Project assignment decisions that account for ethical constraints",
    "Internal compliance and ethics management"
  ],
  "proeth:temporalMarker": "Post-hire, upon Engineer D joining AE\u0026R as associate",
  "proeth:violatesObligation": [
    "Obligation to avoid exploiting conflicts of interest for competitive advantage",
    "Duty to protect the integrity of public procurement processes",
    "NSPE Code obligation to act in a manner that upholds the honor and dignity of the profession",
    "Obligation not to solicit or accept engagements that create conflicts of interest"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "AE\u0026R Assigns Engineer D to City Contracts"
}

Description: Engineer D regularly participated in contract negotiation, award, and senior-level project review involving AE firms, including AE&R, throughout tenure as City Engineer. This established the insider knowledge, relationships, and influence that later generate ethical concerns upon departure.

Temporal Marker: During tenure as City Engineer, prior to resignation announcement

Mental State: deliberate

Intended Outcome: Fulfill assigned public duties as primary contact for AE firms and contractors; ensure proper contract award and project oversight on behalf of the municipality

Fulfills Obligations:
  • Duty to serve the public interest as a public-sector engineer
  • Professional obligation to provide competent engineering oversight
  • Obligation to act as a faithful agent to the municipality as client
Guided By Principles:
  • Public safety, health, and welfare as paramount
  • Faithful agency to public employer/client
  • Competence in professional duties
Required Capabilities:
Contract negotiation and administration Senior-level engineering project review Evaluation of AE firm qualifications and performance Municipal procurement oversight
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer D was fulfilling the core responsibilities of the City Engineer role — serving as the primary liaison between the municipality and AE firms. The motivation was professional duty and institutional function, not necessarily improper intent. However, the cumulative effect of repeated interactions with AE&R created deep familiarity, trust, and informational asymmetry that would later become ethically significant.

Ethical Tension: Effective public service requires building working relationships with private firms, yet those same relationships create the conditions for future conflicts of interest. The tension is between performing the job well (relationship-building, institutional knowledge) and maintaining the structural independence that public trust demands.

Learning Significance: Illustrates how conflicts of interest are rarely created by a single dramatic act but instead accumulate gradually through routine professional conduct. Students learn that ordinary job performance can generate extraordinary ethical obligations upon departure — the 'revolving door' problem is seeded long before anyone resigns.

Stakes: Public trust in procurement integrity, fair competition among AE firms, the municipality's ability to receive unbiased professional advice, and Engineer D's long-term professional reputation. If the relationship with AE&R was perceived as preferential even during tenure, retroactive scrutiny could taint prior contract awards.

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_Participation_in_Contract_Negotiations",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Rotate primary firm contacts among multiple city staff to distribute relationships and reduce individual dependency",
    "Implement formal recusal protocols whenever a single firm accumulates a disproportionate share of city contracts",
    "Proactively document all substantive interactions with AE firms to create an auditable record of arm\u0027s-length dealings"
  ],
  "proeth-scenario:characterMotivation": "Engineer D was fulfilling the core responsibilities of the City Engineer role \u2014 serving as the primary liaison between the municipality and AE firms. The motivation was professional duty and institutional function, not necessarily improper intent. However, the cumulative effect of repeated interactions with AE\u0026R created deep familiarity, trust, and informational asymmetry that would later become ethically significant.",
  "proeth-scenario:consequencesIfAlternative": [
    "Distributing relationships would reduce Engineer D\u0027s personal leverage and insider knowledge, making post-departure conflicts less acute \u2014 but may reduce operational efficiency during tenure",
    "Formal recusal protocols would signal institutional integrity and create documented evidence of fairness, substantially reducing conflict-of-interest exposure upon departure",
    "Robust documentation would protect Engineer D and the city from later allegations of favoritism and would clarify the scope of confidential information Engineer D legitimately possesses"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how conflicts of interest are rarely created by a single dramatic act but instead accumulate gradually through routine professional conduct. Students learn that ordinary job performance can generate extraordinary ethical obligations upon departure \u2014 the \u0027revolving door\u0027 problem is seeded long before anyone resigns.",
  "proeth-scenario:ethicalTension": "Effective public service requires building working relationships with private firms, yet those same relationships create the conditions for future conflicts of interest. The tension is between performing the job well (relationship-building, institutional knowledge) and maintaining the structural independence that public trust demands.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public trust in procurement integrity, fair competition among AE firms, the municipality\u0027s ability to receive unbiased professional advice, and Engineer D\u0027s long-term professional reputation. If the relationship with AE\u0026R was perceived as preferential even during tenure, retroactive scrutiny could taint prior contract awards.",
  "proeth:description": "Engineer D regularly participated in contract negotiation, award, and senior-level project review involving AE firms, including AE\u0026R, throughout tenure as City Engineer. This established the insider knowledge, relationships, and influence that later generate ethical concerns upon departure.",
  "proeth:foreseenUnintendedEffects": [
    "Accumulation of privileged insider knowledge about city projects and procurement",
    "Development of professional relationships with private firms that could later create conflict-of-interest concerns",
    "Creation of conditions that would constrain future private employment options"
  ],
  "proeth:fulfillsObligation": [
    "Duty to serve the public interest as a public-sector engineer",
    "Professional obligation to provide competent engineering oversight",
    "Obligation to act as a faithful agent to the municipality as client"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety, health, and welfare as paramount",
    "Faithful agency to public employer/client",
    "Competence in professional duties"
  ],
  "proeth:hasAgent": "Engineer D (City Engineer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill assigned public duties as primary contact for AE firms and contractors; ensure proper contract award and project oversight on behalf of the municipality",
  "proeth:requiresCapability": [
    "Contract negotiation and administration",
    "Senior-level engineering project review",
    "Evaluation of AE firm qualifications and performance",
    "Municipal procurement oversight"
  ],
  "proeth:temporalMarker": "During tenure as City Engineer, prior to resignation announcement",
  "proeth:withinCompetence": true,
  "rdfs:label": "Participation in Contract Negotiations"
}

Description: Engineer D chose to announce resignation from the City Engineer position and disclosed acceptance of a position at an unnamed engineering firm. The decision to withhold the specific firm's identity at the time of announcement represents a partial disclosure that deferred full transparency.

Temporal Marker: At time of resignation announcement

Mental State: deliberate

Intended Outcome: Formally notify the municipality of impending departure while managing the timing and scope of disclosure about the new employer, potentially to avoid immediate scrutiny or allow AE&R to control its own announcement

Fulfills Obligations:
  • Basic professional courtesy of providing resignation notice
  • Partial transparency regarding intent to enter private sector
Guided By Principles:
  • Transparency and full disclosure
  • Avoidance of conflicts of interest
  • Faithful agency to public employer through end of tenure
Required Capabilities:
Conflict-of-interest identification and disclosure Professional judgment regarding transition ethics Knowledge of NSPE Code obligations
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer D may have withheld the specific firm's identity to avoid premature awkwardness, protect ongoing negotiations, honor a confidentiality request from AE&R, or simply because the offer was not yet finalized. The motivation blends practical self-interest (protecting the new opportunity) with a plausible professional rationale (avoiding disruption to city operations during transition).

Ethical Tension: The duty of full transparency to the public employer conflicts with the natural human desire to control the timing and framing of personal career announcements. There is also tension between loyalty to the incoming employer (AE&R's potential interest in confidentiality) and the city's right to know who will be receiving Engineer D's insider knowledge. NSPE Canon obligations to act in the public interest press toward full disclosure; personal and relational interests press toward deferral.

Learning Significance: Demonstrates that partial disclosure can itself be an ethical violation — transparency is not a binary but a spectrum, and strategic omission of material facts can undermine the spirit of disclosure obligations even when some information is shared. Students learn to interrogate not just whether disclosure was made, but whether it was complete, timely, and actionable.

Stakes: The city loses the opportunity to immediately assess conflicts, reassign Engineer D from sensitive matters, or begin protective measures. Delayed identification of AE&R as the destination firm compresses the window for institutional response and may allow Engineer D to continue influencing matters that directly benefit the future employer.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Disclose both the resignation and the specific identity of AE&R simultaneously and immediately
  • Resign without disclosing any future employment until after departure, relying on post-separation disclosure
  • Consult the city's ethics officer or legal counsel before making any announcement to determine what disclosure is legally and ethically required

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Action_Resignation_and_Partial_Disclosure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose both the resignation and the specific identity of AE\u0026R simultaneously and immediately",
    "Resign without disclosing any future employment until after departure, relying on post-separation disclosure",
    "Consult the city\u0027s ethics officer or legal counsel before making any announcement to determine what disclosure is legally and ethically required"
  ],
  "proeth-scenario:characterMotivation": "Engineer D may have withheld the specific firm\u0027s identity to avoid premature awkwardness, protect ongoing negotiations, honor a confidentiality request from AE\u0026R, or simply because the offer was not yet finalized. The motivation blends practical self-interest (protecting the new opportunity) with a plausible professional rationale (avoiding disruption to city operations during transition).",
  "proeth-scenario:consequencesIfAlternative": [
    "Full simultaneous disclosure would allow the city to immediately recuse Engineer D from all AE\u0026R-related matters, protecting institutional integrity and demonstrating Engineer D\u0027s good faith \u2014 though it may create personal and professional awkwardness",
    "Delaying all disclosure until after departure would likely worsen the ethical situation, leaving the city with no opportunity to manage the transition, and could constitute a violation of fiduciary duty",
    "Consulting ethics counsel first would model best practice, create a documented record of good-faith compliance efforts, and likely result in a structured, legally sound disclosure plan \u2014 the most defensible path"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that partial disclosure can itself be an ethical violation \u2014 transparency is not a binary but a spectrum, and strategic omission of material facts can undermine the spirit of disclosure obligations even when some information is shared. Students learn to interrogate not just whether disclosure was made, but whether it was complete, timely, and actionable.",
  "proeth-scenario:ethicalTension": "The duty of full transparency to the public employer conflicts with the natural human desire to control the timing and framing of personal career announcements. There is also tension between loyalty to the incoming employer (AE\u0026R\u0027s potential interest in confidentiality) and the city\u0027s right to know who will be receiving Engineer D\u0027s insider knowledge. NSPE Canon obligations to act in the public interest press toward full disclosure; personal and relational interests press toward deferral.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The city loses the opportunity to immediately assess conflicts, reassign Engineer D from sensitive matters, or begin protective measures. Delayed identification of AE\u0026R as the destination firm compresses the window for institutional response and may allow Engineer D to continue influencing matters that directly benefit the future employer.",
  "proeth:description": "Engineer D chose to announce resignation from the City Engineer position and disclosed acceptance of a position at an unnamed engineering firm. The decision to withhold the specific firm\u0027s identity at the time of announcement represents a partial disclosure that deferred full transparency.",
  "proeth:foreseenUnintendedEffects": [
    "Triggering ethical scrutiny under revolving door principles",
    "Creating a window of ambiguity during which conflict-of-interest obligations are unclear",
    "Allowing ongoing participation in city matters during the notice period without full conflict disclosure"
  ],
  "proeth:fulfillsObligation": [
    "Basic professional courtesy of providing resignation notice",
    "Partial transparency regarding intent to enter private sector"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency and full disclosure",
    "Avoidance of conflicts of interest",
    "Faithful agency to public employer through end of tenure"
  ],
  "proeth:hasAgent": "Engineer D (City Engineer, transitioning to private sector)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Transparency to current public employer vs. loyalty to incoming private employer",
    "proeth:resolutionReasoning": "Engineer D resolved the tension in favor of the new private employer by withholding the firm name, but the ethical weight of the competing obligation \u2014 full disclosure to the public employer \u2014 was stronger given the City\u0027s need to manage active procurement and project relationships during the transition period"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Formally notify the municipality of impending departure while managing the timing and scope of disclosure about the new employer, potentially to avoid immediate scrutiny or allow AE\u0026R to control its own announcement",
  "proeth:requiresCapability": [
    "Conflict-of-interest identification and disclosure",
    "Professional judgment regarding transition ethics",
    "Knowledge of NSPE Code obligations"
  ],
  "proeth:temporalMarker": "At time of resignation announcement",
  "proeth:violatesObligation": [
    "Full and timely disclosure of conflicts of interest to the public employer",
    "Obligation to avoid even the appearance of impropriety in public-sector role",
    "Duty to disclose material information affecting the City\u0027s ability to manage transition and conflict"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Resignation and Partial Disclosure"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changes

Description: The public announcement of Engineer D's hire by AE&R renders visible the historical pattern of AE&R receiving contracts during Engineer D's tenure, creating a factual record that invites scrutiny of whether those awards were influenced by the prospective employment relationship. This is an outcome of the public announcement rather than a new action.

Temporal Marker: Concurrent with or immediately following AE&R's public hire announcement

Activates Constraints:
  • Retroactive_Conflict_Review_Constraint
  • Appearance_of_Impropriety_Constraint
  • Public_Trust_Preservation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer D may feel unjustly accused if decisions were merit-based; AE&R may feel their competitive success is being retroactively tainted; city officials may feel institutional embarrassment; the public may feel betrayed

Stakeholder Consequences:
  • engineer_d: Past professional judgment is now under a cloud; career reputation at risk regardless of actual conduct
  • aer_firm: Business success reframed as potentially improper; future city bids may be disadvantaged
  • city_government: Must conduct potentially costly and disruptive audit of prior procurement
  • competing_ae_firms: May seek redress for contracts they believe were unfairly lost
  • public: Public resources may have been misallocated; democratic accountability in procurement is questioned

Learning Moment: Even legitimate professional success can be ethically compromised by the appearance of impropriety. Students should understand that ethical obligations require proactive management of conflicts, not merely avoiding actual wrongdoing.

Ethical Implications: Illustrates that the appearance of impropriety is treated as an independent ethical harm under professional codes; raises questions about whether public engineers can ever accept employment from firms they regulated without ethical compromise; highlights the asymmetry between private career interests and public accountability obligations

Discussion Prompts:
  • If all of AE&R's contract awards were genuinely merit-based, does the appearance of impropriety still constitute an ethical violation?
  • What documentation practices should public engineers maintain to protect themselves and their employers from retroactive scrutiny?
  • At what point during Engineer D's tenure should the prospect of future employment with AE&R have required recusal from AE&R-related procurement decisions?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Event_Prior_AE_R_Contract_History_Exposed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "If all of AE\u0026R\u0027s contract awards were genuinely merit-based, does the appearance of impropriety still constitute an ethical violation?",
    "What documentation practices should public engineers maintain to protect themselves and their employers from retroactive scrutiny?",
    "At what point during Engineer D\u0027s tenure should the prospect of future employment with AE\u0026R have required recusal from AE\u0026R-related procurement decisions?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer D may feel unjustly accused if decisions were merit-based; AE\u0026R may feel their competitive success is being retroactively tainted; city officials may feel institutional embarrassment; the public may feel betrayed",
  "proeth-scenario:ethicalImplications": "Illustrates that the appearance of impropriety is treated as an independent ethical harm under professional codes; raises questions about whether public engineers can ever accept employment from firms they regulated without ethical compromise; highlights the asymmetry between private career interests and public accountability obligations",
  "proeth-scenario:learningMoment": "Even legitimate professional success can be ethically compromised by the appearance of impropriety. Students should understand that ethical obligations require proactive management of conflicts, not merely avoiding actual wrongdoing.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "aer_firm": "Business success reframed as potentially improper; future city bids may be disadvantaged",
    "city_government": "Must conduct potentially costly and disruptive audit of prior procurement",
    "competing_ae_firms": "May seek redress for contracts they believe were unfairly lost",
    "engineer_d": "Past professional judgment is now under a cloud; career reputation at risk regardless of actual conduct",
    "public": "Public resources may have been misallocated; democratic accountability in procurement is questioned"
  },
  "proeth:activatesConstraint": [
    "Retroactive_Conflict_Review_Constraint",
    "Appearance_of_Impropriety_Constraint",
    "Public_Trust_Preservation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/10#Action_Accepting_Employment_with_AE_R",
  "proeth:causesStateChange": "Historical contract awards to AE\u0026R shift from routine records to evidence requiring justification; the burden of proof on merit-based selection is now implicitly reversed in the court of public opinion",
  "proeth:createsObligation": [
    "City_Must_Audit_Prior_AER_Awards",
    "Engineer_D_Must_Account_for_Prior_Decision_Making_Integrity",
    "AER_Must_Demonstrate_Awards_Were_Merit_Based"
  ],
  "proeth:description": "The public announcement of Engineer D\u0027s hire by AE\u0026R renders visible the historical pattern of AE\u0026R receiving contracts during Engineer D\u0027s tenure, creating a factual record that invites scrutiny of whether those awards were influenced by the prospective employment relationship. This is an outcome of the public announcement rather than a new action.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Concurrent with or immediately following AE\u0026R\u0027s public hire announcement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Prior AE\u0026R Contract History Exposed"
}

Description: Upon Engineer D joining AE&R, a formal conflict-of-interest state is established by operation of professional ethics codes and potentially municipal law, automatically restricting Engineer D's permissible activities regarding city projects. This state exists independent of any conscious decision by Engineer D or AE&R.

Temporal Marker: Upon commencement of Engineer D's employment at AE&R

Activates Constraints:
  • NSPE_Code_Section_III_Conflict_of_Interest_Constraint
  • Cooling_Off_Period_Constraint
  • Restriction_on_City_Project_Participation_Constraint
  • Confidential_Information_Non_Use_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer D may feel constrained or unfairly limited in new role; AE&R principals may feel frustrated by restrictions on their new hire's utility; city officials may feel reassured or may be unaware the constraint exists

Stakeholder Consequences:
  • engineer_d: Professional autonomy at new firm is immediately constrained; must navigate complex disclosure and recusal requirements
  • aer_firm: Business value of Engineer D hire is reduced by conflict restrictions; must implement internal compliance procedures
  • city_government: Has a legal and ethical interest in enforcing the conflict-of-interest state; may need to formally acknowledge or reject Engineer D's disclosure
  • public: Protected by the constraint from potential exploitation of insider knowledge in public procurement

Learning Moment: Ethical constraints arising from professional codes operate automatically upon the occurrence of triggering conditions; individuals cannot opt out by failing to acknowledge them. Students should understand that professional ethics are not merely advisory but create binding obligations.

Ethical Implications: Demonstrates that professional ethics codes create objective constraints independent of subjective intent; raises the question of whether structural conflicts of interest can ever be fully remediated; highlights the tension between professional mobility and public accountability

Discussion Prompts:
  • Should Engineer D have anticipated this conflict-of-interest state before accepting the position, and what does that imply about the timing of ethical obligations?
  • How does the automatic nature of the conflict-of-interest constraint affect the moral responsibility of AE&R's principals who made the hiring decision?
  • What is the difference between a conflict of interest that can be resolved through disclosure and one that cannot be resolved at all?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Event_Conflict_of_Interest_State_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should Engineer D have anticipated this conflict-of-interest state before accepting the position, and what does that imply about the timing of ethical obligations?",
    "How does the automatic nature of the conflict-of-interest constraint affect the moral responsibility of AE\u0026R\u0027s principals who made the hiring decision?",
    "What is the difference between a conflict of interest that can be resolved through disclosure and one that cannot be resolved at all?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer D may feel constrained or unfairly limited in new role; AE\u0026R principals may feel frustrated by restrictions on their new hire\u0027s utility; city officials may feel reassured or may be unaware the constraint exists",
  "proeth-scenario:ethicalImplications": "Demonstrates that professional ethics codes create objective constraints independent of subjective intent; raises the question of whether structural conflicts of interest can ever be fully remediated; highlights the tension between professional mobility and public accountability",
  "proeth-scenario:learningMoment": "Ethical constraints arising from professional codes operate automatically upon the occurrence of triggering conditions; individuals cannot opt out by failing to acknowledge them. Students should understand that professional ethics are not merely advisory but create binding obligations.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "aer_firm": "Business value of Engineer D hire is reduced by conflict restrictions; must implement internal compliance procedures",
    "city_government": "Has a legal and ethical interest in enforcing the conflict-of-interest state; may need to formally acknowledge or reject Engineer D\u0027s disclosure",
    "engineer_d": "Professional autonomy at new firm is immediately constrained; must navigate complex disclosure and recusal requirements",
    "public": "Protected by the constraint from potential exploitation of insider knowledge in public procurement"
  },
  "proeth:activatesConstraint": [
    "NSPE_Code_Section_III_Conflict_of_Interest_Constraint",
    "Cooling_Off_Period_Constraint",
    "Restriction_on_City_Project_Participation_Constraint",
    "Confidential_Information_Non_Use_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/10#Action_Accepting_Employment_with_AE_R",
  "proeth:causesStateChange": "Engineer D\u0027s professional status shifts from \u0027former public official\u0027 to \u0027conflicted private engineer\u0027; a set of automatic restrictions attaches to Engineer D\u0027s professional conduct regardless of explicit acknowledgment",
  "proeth:createsObligation": [
    "Engineer_D_Must_Disclose_Conflict_to_City_and_AER",
    "Engineer_D_Must_Seek_Informed_Consent_from_City",
    "Engineer_D_Must_Not_Use_Confidential_City_Information",
    "AER_Must_Not_Assign_Engineer_D_to_Active_City_Projects",
    "Engineer_D_Must_Observe_Cooling_Off_Period_if_Required"
  ],
  "proeth:description": "Upon Engineer D joining AE\u0026R, a formal conflict-of-interest state is established by operation of professional ethics codes and potentially municipal law, automatically restricting Engineer D\u0027s permissible activities regarding city projects. This state exists independent of any conscious decision by Engineer D or AE\u0026R.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Upon commencement of Engineer D\u0027s employment at AE\u0026R",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Conflict of Interest State Established"
}

Description: Based on the historical precedents established in BER cases from 1958 through 2015, a cooling-off period obligation is triggered by the combination of Engineer D's prior procurement authority and subsequent private-sector employment with a regulated firm. This obligation restricts Engineer D's involvement in city-related work for a defined period regardless of explicit policy mandates.

Temporal Marker: Upon commencement of Engineer D's employment at AE&R, with reference to historical BER precedents

Activates Constraints:
  • Cooling_Off_Period_Constraint
  • Restriction_on_City_Project_Involvement_Constraint
  • Appearance_of_Impropriety_Avoidance_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer D may feel the cooling-off period is punitive or career-limiting; AE&R may feel their investment in Engineer D is deferred; city officials may feel the period provides meaningful protection; the public may be unaware but is the intended beneficiary

Stakeholder Consequences:
  • engineer_d: Career advancement at AE&R is constrained for up to one year; must find non-city work to contribute value to firm
  • aer_firm: Return on investment in Engineer D hire is delayed; must manage workload without his city-specific expertise
  • city_government: Procurement integrity is protected during the most vulnerable post-transition period
  • public: Protected from exploitation of insider knowledge in the period immediately following transition

Learning Moment: Cooling-off periods are not merely bureaucratic formalities but serve a substantive ethical function: they prevent the monetization of public-sector insider knowledge and relationships in private-sector contexts. The period exists to protect public trust even when no actual wrongdoing has occurred.

Ethical Implications: Highlights the tension between professional mobility rights and public interest protection; raises questions about proportionality in cooling-off period design; illustrates how professional ethics codes must fill gaps left by inadequate institutional policy

Discussion Prompts:
  • Is a one-year cooling-off period sufficient given the depth of Engineer D's knowledge of city procurement processes and relationships?
  • Should cooling-off periods be formally codified in municipal employment contracts, or is reliance on professional ethics codes sufficient?
  • How should AE&R structure Engineer D's role during the cooling-off period to extract value from the hire without violating ethical constraints?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Event_Cooling-Off_Period_Obligation_Activated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is a one-year cooling-off period sufficient given the depth of Engineer D\u0027s knowledge of city procurement processes and relationships?",
    "Should cooling-off periods be formally codified in municipal employment contracts, or is reliance on professional ethics codes sufficient?",
    "How should AE\u0026R structure Engineer D\u0027s role during the cooling-off period to extract value from the hire without violating ethical constraints?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer D may feel the cooling-off period is punitive or career-limiting; AE\u0026R may feel their investment in Engineer D is deferred; city officials may feel the period provides meaningful protection; the public may be unaware but is the intended beneficiary",
  "proeth-scenario:ethicalImplications": "Highlights the tension between professional mobility rights and public interest protection; raises questions about proportionality in cooling-off period design; illustrates how professional ethics codes must fill gaps left by inadequate institutional policy",
  "proeth-scenario:learningMoment": "Cooling-off periods are not merely bureaucratic formalities but serve a substantive ethical function: they prevent the monetization of public-sector insider knowledge and relationships in private-sector contexts. The period exists to protect public trust even when no actual wrongdoing has occurred.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "aer_firm": "Return on investment in Engineer D hire is delayed; must manage workload without his city-specific expertise",
    "city_government": "Procurement integrity is protected during the most vulnerable post-transition period",
    "engineer_d": "Career advancement at AE\u0026R is constrained for up to one year; must find non-city work to contribute value to firm",
    "public": "Protected from exploitation of insider knowledge in the period immediately following transition"
  },
  "proeth:activatesConstraint": [
    "Cooling_Off_Period_Constraint",
    "Restriction_on_City_Project_Involvement_Constraint",
    "Appearance_of_Impropriety_Avoidance_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/10#Action_Accepting_Employment_with_AE_R",
  "proeth:causesStateChange": "A time-bounded restriction window opens; Engineer D\u0027s permissible professional activities are circumscribed for approximately one year post-departure from city role",
  "proeth:createsObligation": [
    "Engineer_D_Must_Observe_One_Year_Cooling_Off_Period",
    "Engineer_D_Must_Not_Participate_in_City_Procurement_Activities",
    "AER_Must_Reassign_City_Contract_Work_Away_from_Engineer_D",
    "Engineer_D_Must_Proactively_Disclose_Cooling_Off_Status_to_AER"
  ],
  "proeth:description": "Based on the historical precedents established in BER cases from 1958 through 2015, a cooling-off period obligation is triggered by the combination of Engineer D\u0027s prior procurement authority and subsequent private-sector employment with a regulated firm. This obligation restricts Engineer D\u0027s involvement in city-related work for a defined period regardless of explicit policy mandates.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Upon commencement of Engineer D\u0027s employment at AE\u0026R, with reference to historical BER precedents",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Cooling-Off Period Obligation Activated"
}

Description: When AE&R assigns Engineer D to city contracts, a direct ethical violation risk state is created: Engineer D is placed in a position where participation in active or procurement-related city projects would breach multiple professional obligations simultaneously. This risk state exists as an outcome of the assignment action.

Temporal Marker: Upon AE&R assigning Engineer D to city contracts

Activates Constraints:
  • Immediate_Recusal_Obligation_Constraint
  • Conflict_of_Interest_Breach_Risk_Constraint
  • AER_Supervisory_Responsibility_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer D faces acute ethical discomfort and professional risk; AE&R principals may be oblivious to the violation or may be deliberately exploiting Engineer D's insider status; city officials would feel alarmed if aware; the public's interests are directly threatened

Stakeholder Consequences:
  • engineer_d: Faces potential professional discipline, license revocation, and reputational destruction if violation proceeds
  • aer_firm: Risks loss of city contracts, debarment from future procurement, and reputational damage
  • city_government: Procurement integrity is actively compromised; legal liability may arise
  • competing_ae_firms: Face unfair competition from a firm exploiting insider knowledge
  • public: Public resources may be misallocated through compromised procurement processes

Learning Moment: The assignment of a conflicted engineer to restricted projects is not a passive ethical failure but an active violation requiring immediate remediation. Both the individual engineer and the firm's leadership bear ethical responsibility for allowing the situation to persist.

Ethical Implications: Reveals that organizational actors (firm principals) can create ethical violations by placing individuals in impossible positions; challenges the individualistic framing of engineering ethics by showing how institutional decisions drive individual ethical jeopardy; highlights the firm's independent ethical obligations beyond those of the individual engineer

Discussion Prompts:
  • What responsibility do AE&R's principals bear for assigning Engineer D to city contracts, and does their knowledge of the conflict affect their culpability?
  • If Engineer D was assigned to city contracts without being informed of the ethical restrictions, how does that affect the distribution of moral responsibility?
  • At what point does a firm's exploitation of an employee's insider knowledge become an independent ethical violation separate from the employee's own obligations?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Event_City_Project_Involvement_Risk_Created",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What responsibility do AE\u0026R\u0027s principals bear for assigning Engineer D to city contracts, and does their knowledge of the conflict affect their culpability?",
    "If Engineer D was assigned to city contracts without being informed of the ethical restrictions, how does that affect the distribution of moral responsibility?",
    "At what point does a firm\u0027s exploitation of an employee\u0027s insider knowledge become an independent ethical violation separate from the employee\u0027s own obligations?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer D faces acute ethical discomfort and professional risk; AE\u0026R principals may be oblivious to the violation or may be deliberately exploiting Engineer D\u0027s insider status; city officials would feel alarmed if aware; the public\u0027s interests are directly threatened",
  "proeth-scenario:ethicalImplications": "Reveals that organizational actors (firm principals) can create ethical violations by placing individuals in impossible positions; challenges the individualistic framing of engineering ethics by showing how institutional decisions drive individual ethical jeopardy; highlights the firm\u0027s independent ethical obligations beyond those of the individual engineer",
  "proeth-scenario:learningMoment": "The assignment of a conflicted engineer to restricted projects is not a passive ethical failure but an active violation requiring immediate remediation. Both the individual engineer and the firm\u0027s leadership bear ethical responsibility for allowing the situation to persist.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "aer_firm": "Risks loss of city contracts, debarment from future procurement, and reputational damage",
    "city_government": "Procurement integrity is actively compromised; legal liability may arise",
    "competing_ae_firms": "Face unfair competition from a firm exploiting insider knowledge",
    "engineer_d": "Faces potential professional discipline, license revocation, and reputational destruction if violation proceeds",
    "public": "Public resources may be misallocated through compromised procurement processes"
  },
  "proeth:activatesConstraint": [
    "Immediate_Recusal_Obligation_Constraint",
    "Conflict_of_Interest_Breach_Risk_Constraint",
    "AER_Supervisory_Responsibility_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/10#Action_AE_R_Assigns_Engineer_D_to_City_Contracts",
  "proeth:causesStateChange": "Engineer D is placed in a position of active ethical jeopardy; the assignment creates an immediate obligation to recuse and disclose; failure to act promptly constitutes a continuing violation",
  "proeth:createsObligation": [
    "Engineer_D_Must_Immediately_Recuse_from_Assigned_City_Projects",
    "Engineer_D_Must_Notify_AER_Principals_of_Constraint",
    "AER_Must_Reassign_City_Project_Work",
    "AER_Must_Not_Exploit_Engineer_D_City_Insider_Knowledge"
  ],
  "proeth:description": "When AE\u0026R assigns Engineer D to city contracts, a direct ethical violation risk state is created: Engineer D is placed in a position where participation in active or procurement-related city projects would breach multiple professional obligations simultaneously. This risk state exists as an outcome of the assignment action.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon AE\u0026R assigning Engineer D to city contracts",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "City Project Involvement Risk Created"
}

Description: Engineer D publicly announces resignation from the City Engineer position, triggering an immediate transition period with unresolved conflict-of-interest implications. This announcement creates a liminal state where Engineer D still holds official authority while pursuing private-sector interests.

Temporal Marker: At the point of resignation announcement

Activates Constraints:
  • Conflict_of_Interest_Disclosure_Constraint
  • Confidentiality_Duty_Constraint
  • Duty_of_Loyalty_to_Public_Employer_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer D may feel relief or excitement about new opportunity mixed with anxiety about scrutiny; city officials may feel uncertainty and concern about procurement integrity; AE firms with pending contracts may feel apprehension about fairness of past decisions

Stakeholder Consequences:
  • engineer_d: Enters ethically precarious transition period; all subsequent actions now subject to heightened scrutiny
  • city_government: Faces disruption in senior engineering leadership; must audit ongoing procurement for potential bias
  • ae_firms_with_city_contracts: Prior awards may be questioned for favoritism; competitive fairness concerns arise
  • public: Trust in municipal engineering procurement integrity is placed at risk
  • aer_firm: Gains a high-value hire but inherits reputational and legal risk if transition is mishandled

Learning Moment: A public official's resignation does not end ethical obligations; the announcement itself triggers new duties around disclosure, recusal, and protection of public trust that must be actively managed.

Ethical Implications: Reveals tension between individual career advancement and public fiduciary duty; highlights the 'revolving door' problem where insider knowledge and relationships create structural advantages that may compromise public procurement integrity

Discussion Prompts:
  • At what point during job negotiations should Engineer D have disclosed the conflict of interest to the city?
  • Does the mere announcement of resignation change Engineer D's obligations regarding ongoing procurement decisions?
  • What institutional safeguards should municipalities have in place to manage senior engineer transitions?
Tension: medium Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Event_Engineer_D_s_Resignation_Announced",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what point during job negotiations should Engineer D have disclosed the conflict of interest to the city?",
    "Does the mere announcement of resignation change Engineer D\u0027s obligations regarding ongoing procurement decisions?",
    "What institutional safeguards should municipalities have in place to manage senior engineer transitions?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer D may feel relief or excitement about new opportunity mixed with anxiety about scrutiny; city officials may feel uncertainty and concern about procurement integrity; AE firms with pending contracts may feel apprehension about fairness of past decisions",
  "proeth-scenario:ethicalImplications": "Reveals tension between individual career advancement and public fiduciary duty; highlights the \u0027revolving door\u0027 problem where insider knowledge and relationships create structural advantages that may compromise public procurement integrity",
  "proeth-scenario:learningMoment": "A public official\u0027s resignation does not end ethical obligations; the announcement itself triggers new duties around disclosure, recusal, and protection of public trust that must be actively managed.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "ae_firms_with_city_contracts": "Prior awards may be questioned for favoritism; competitive fairness concerns arise",
    "aer_firm": "Gains a high-value hire but inherits reputational and legal risk if transition is mishandled",
    "city_government": "Faces disruption in senior engineering leadership; must audit ongoing procurement for potential bias",
    "engineer_d": "Enters ethically precarious transition period; all subsequent actions now subject to heightened scrutiny",
    "public": "Trust in municipal engineering procurement integrity is placed at risk"
  },
  "proeth:activatesConstraint": [
    "Conflict_of_Interest_Disclosure_Constraint",
    "Confidentiality_Duty_Constraint",
    "Duty_of_Loyalty_to_Public_Employer_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/10#Action_Resignation_and_Partial_Disclosure",
  "proeth:causesStateChange": "Engineer D transitions from stable public official to departing employee; conflict-of-interest scrutiny window opens; city must manage procurement continuity without compromised decision-maker",
  "proeth:createsObligation": [
    "Disclose_Employment_Negotiations_to_City",
    "Recuse_from_Decisions_Affecting_Prospective_Employer",
    "Maintain_Confidentiality_of_City_Procurement_Information",
    "Complete_Transition_Without_Exploitation_of_Position"
  ],
  "proeth:description": "Engineer D publicly announces resignation from the City Engineer position, triggering an immediate transition period with unresolved conflict-of-interest implications. This announcement creates a liminal state where Engineer D still holds official authority while pursuing private-sector interests.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "At the point of resignation announcement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer D\u0027s Resignation Announced"
}

Description: Firm AE&R publicly announces Engineer D as a newly hired associate shortly after Engineer D's resignation announcement, creating a publicly visible record of the employment relationship and its timing relative to Engineer D's tenure as City Engineer. This announcement makes the prior professional relationship between AE&R and Engineer D a matter of public record.

Temporal Marker: Shortly after Engineer D's resignation announcement

Activates Constraints:
  • Appearance_of_Impropriety_Constraint
  • Conflict_of_Interest_Disclosure_Constraint
  • Cooling_Off_Period_Consideration_Constraint
  • Prior_Relationship_Scrutiny_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer D may feel exposed or defensive as the relationship is scrutinized publicly; AE&R principals may feel confident in their hire but anxious about reputational risk; competing AE firms may feel vindicated in any prior suspicions of favoritism; city officials may feel embarrassed or alarmed

Stakeholder Consequences:
  • engineer_d: Professional reputation now publicly linked to potential impropriety; past decisions as City Engineer will be re-examined
  • aer_firm: Faces reputational risk and potential loss of future city contracts; prior awards may be audited
  • competing_ae_firms: May file complaints or demand review of past procurement decisions they lost to AE&R
  • city_government: Must respond publicly to appearance of compromised procurement; potential legal and political liability
  • public: Confidence in fair use of public funds is undermined; perception of 'pay-to-play' culture may emerge

Learning Moment: The public announcement crystallizes the ethical problem: even if no actual wrongdoing occurred, the appearance of impropriety is itself an ethical violation under professional codes. Students must understand that the timing, visibility, and prior relationship all compound ethical risk.

Ethical Implications: Exposes the structural conflict between the revolving door phenomenon and public procurement integrity; raises questions about whether institutional relationships can ever be ethically severed quickly enough; challenges the distinction between actual corruption and the appearance of corruption as independent ethical violations

Discussion Prompts:
  • Does the fact that AE&R completed many projects under Engineer D's tenure create a presumption of impropriety, or must actual bias be proven?
  • Should AE&R have delayed the public announcement or structured the hire differently to reduce the appearance of impropriety?
  • How should competing firms that lost bids to AE&R respond to this announcement, and what remedies are available to them?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#Event_AE_R_Public_Hire_Announcement",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the fact that AE\u0026R completed many projects under Engineer D\u0027s tenure create a presumption of impropriety, or must actual bias be proven?",
    "Should AE\u0026R have delayed the public announcement or structured the hire differently to reduce the appearance of impropriety?",
    "How should competing firms that lost bids to AE\u0026R respond to this announcement, and what remedies are available to them?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer D may feel exposed or defensive as the relationship is scrutinized publicly; AE\u0026R principals may feel confident in their hire but anxious about reputational risk; competing AE firms may feel vindicated in any prior suspicions of favoritism; city officials may feel embarrassed or alarmed",
  "proeth-scenario:ethicalImplications": "Exposes the structural conflict between the revolving door phenomenon and public procurement integrity; raises questions about whether institutional relationships can ever be ethically severed quickly enough; challenges the distinction between actual corruption and the appearance of corruption as independent ethical violations",
  "proeth-scenario:learningMoment": "The public announcement crystallizes the ethical problem: even if no actual wrongdoing occurred, the appearance of impropriety is itself an ethical violation under professional codes. Students must understand that the timing, visibility, and prior relationship all compound ethical risk.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "aer_firm": "Faces reputational risk and potential loss of future city contracts; prior awards may be audited",
    "city_government": "Must respond publicly to appearance of compromised procurement; potential legal and political liability",
    "competing_ae_firms": "May file complaints or demand review of past procurement decisions they lost to AE\u0026R",
    "engineer_d": "Professional reputation now publicly linked to potential impropriety; past decisions as City Engineer will be re-examined",
    "public": "Confidence in fair use of public funds is undermined; perception of \u0027pay-to-play\u0027 culture may emerge"
  },
  "proeth:activatesConstraint": [
    "Appearance_of_Impropriety_Constraint",
    "Conflict_of_Interest_Disclosure_Constraint",
    "Cooling_Off_Period_Consideration_Constraint",
    "Prior_Relationship_Scrutiny_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/10#Action_Accepting_Employment_with_AE_R",
  "proeth:causesStateChange": "The employment relationship becomes publicly known; prior awards to AE\u0026R during Engineer D\u0027s tenure are now subject to retroactive scrutiny; Engineer D\u0027s dual identity as former regulator and current AE\u0026R employee is established",
  "proeth:createsObligation": [
    "Engineer_D_Must_Disclose_Full_Scope_of_Prior_AER_Relationship",
    "AER_Must_Manage_Engineer_D_City_Project_Assignments",
    "City_Must_Review_Prior_AER_Contract_Awards_for_Bias",
    "Engineer_D_Must_Seek_City_Acceptance_of_New_Role"
  ],
  "proeth:description": "Firm AE\u0026R publicly announces Engineer D as a newly hired associate shortly after Engineer D\u0027s resignation announcement, creating a publicly visible record of the employment relationship and its timing relative to Engineer D\u0027s tenure as City Engineer. This announcement makes the prior professional relationship between AE\u0026R and Engineer D a matter of public record.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Shortly after Engineer D\u0027s resignation announcement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "AE\u0026R Public Hire Announcement"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: Engineer D regularly participated in contract negotiation, award, and senior-level project review — creating the foundational condition that, upon joining AE&R, triggered a formal conflict-of-interest state by operation of professional ethics standards

Necessary Factors (NESS):
  • Engineer D's active role in awarding or overseeing AE&R contracts while City Engineer
  • AE&R's status as a firm that received or competed for city contracts during that period
  • Engineer D's subsequent transition to employment at AE&R
  • Existence of applicable professional ethics codes governing revolving-door conflicts
Sufficient Factors:
  • Combination of prior supervisory/award authority over AE&R contracts + direct employment acceptance at AE&R = sufficient to establish conflict of interest as a matter of professional ethics law
Counterfactual Test: If Engineer D had never participated in AE&R-related contract negotiations or awards, the conflict-of-interest state would not have been established upon hire; alternatively, if Engineer D had joined a firm with no prior city contract history, no conflict would arise
Responsibility Attribution:

Agent: Engineer D
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Participation in Contract Negotiations (Action 1)
    Engineer D exercises governmental authority over contract awards and project reviews involving AE&R and other firms
  2. Prior AE&R Contract History Exposed (Event 3)
    Public hire announcement reveals the historical pattern of AE&R receiving city contracts during Engineer D's tenure
  3. Accepting Employment with AE&R (Action 3)
    Engineer D transitions from regulatory/oversight authority directly to employment at a firm previously subject to that authority
  4. AE&R Public Hire Announcement (Event 2)
    Public announcement crystallizes the appearance and substance of the conflict for professional and public scrutiny
  5. Conflict of Interest State Established (Event 4)
    Formal conflict-of-interest state arises by operation of professional ethics standards, binding Engineer D and AE&R to remediation obligations
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#CausalChain_8558fd20",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer D regularly participated in contract negotiation, award, and senior-level project review \u2014 creating the foundational condition that, upon joining AE\u0026R, triggered a formal conflict-of-interest state by operation of professional ethics standards",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer D exercises governmental authority over contract awards and project reviews involving AE\u0026R and other firms",
      "proeth:element": "Participation in Contract Negotiations (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Public hire announcement reveals the historical pattern of AE\u0026R receiving city contracts during Engineer D\u0027s tenure",
      "proeth:element": "Prior AE\u0026R Contract History Exposed (Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer D transitions from regulatory/oversight authority directly to employment at a firm previously subject to that authority",
      "proeth:element": "Accepting Employment with AE\u0026R (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Public announcement crystallizes the appearance and substance of the conflict for professional and public scrutiny",
      "proeth:element": "AE\u0026R Public Hire Announcement (Event 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Formal conflict-of-interest state arises by operation of professional ethics standards, binding Engineer D and AE\u0026R to remediation obligations",
      "proeth:element": "Conflict of Interest State Established (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Participation in Contract Negotiations (Action 1)",
  "proeth:counterfactual": "If Engineer D had never participated in AE\u0026R-related contract negotiations or awards, the conflict-of-interest state would not have been established upon hire; alternatively, if Engineer D had joined a firm with no prior city contract history, no conflict would arise",
  "proeth:effect": "Conflict of Interest State Established (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer D\u0027s active role in awarding or overseeing AE\u0026R contracts while City Engineer",
    "AE\u0026R\u0027s status as a firm that received or competed for city contracts during that period",
    "Engineer D\u0027s subsequent transition to employment at AE\u0026R",
    "Existence of applicable professional ethics codes governing revolving-door conflicts"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer D",
  "proeth:sufficientFactors": [
    "Combination of prior supervisory/award authority over AE\u0026R contracts + direct employment acceptance at AE\u0026R = sufficient to establish conflict of interest as a matter of professional ethics law"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Post-hire, Engineer D faces the implied decision of whether to proactively seek full disclosure of the conflict and city acceptance — the failure to do so allows the conflict-of-interest state and cooling-off obligation to persist without institutional acknowledgment or structured remediation

Necessary Factors (NESS):
  • Engineer D's awareness of the conflict-of-interest state upon joining AE&R
  • The availability of a disclosure mechanism (city ethics board, professional body, or direct city communication)
  • The absence of automatic institutional detection or enforcement triggering disclosure
  • Engineer D's choice not to proactively disclose (the omission)
Sufficient Factors:
  • Failure to disclose + active assignment to city contracts = sufficient to convert a manageable conflict into an active ethical violation
  • Proactive disclosure alone would not eliminate the conflict but would satisfy transparency obligations and potentially enable structured resolution
Counterfactual Test: If Engineer D had proactively sought full disclosure and city acceptance, the conflict state would still exist but would be managed transparently; the cooling-off obligation might have been formally acknowledged and honored, preventing the escalation to active violation
Responsibility Attribution:

Agent: Engineer D
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Conflict of Interest State Established (Event 4)
    Conflict arises upon Engineer D joining AE&R, creating an immediate disclosure obligation
  2. Disclosure and City Acceptance Seeking — Omission (Action 4)
    Engineer D does not proactively seek full disclosure or city acceptance, allowing the conflict to persist unmanaged
  3. Cooling-Off Period Obligation Activated (Event 5)
    Without disclosure, the cooling-off obligation operates as an unacknowledged constraint, increasing risk of inadvertent violation
  4. Voluntary Recusal Not Adopted (Action 5 — omission)
    Without disclosure framework, recusal is also not formally adopted, compounding the unmanaged conflict
  5. City Project Involvement Risk Created (Event 6)
    The cumulative omissions (no disclosure, no recusal, no cooling-off adoption) create the conditions for direct ethical violation when AE&R assigns Engineer D to city contracts
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#CausalChain_994e599c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Post-hire, Engineer D faces the implied decision of whether to proactively seek full disclosure of the conflict and city acceptance \u2014 the failure to do so allows the conflict-of-interest state and cooling-off obligation to persist without institutional acknowledgment or structured remediation",
  "proeth:causalSequence": [
    {
      "proeth:description": "Conflict arises upon Engineer D joining AE\u0026R, creating an immediate disclosure obligation",
      "proeth:element": "Conflict of Interest State Established (Event 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer D does not proactively seek full disclosure or city acceptance, allowing the conflict to persist unmanaged",
      "proeth:element": "Disclosure and City Acceptance Seeking \u2014 Omission (Action 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Without disclosure, the cooling-off obligation operates as an unacknowledged constraint, increasing risk of inadvertent violation",
      "proeth:element": "Cooling-Off Period Obligation Activated (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Without disclosure framework, recusal is also not formally adopted, compounding the unmanaged conflict",
      "proeth:element": "Voluntary Recusal Not Adopted (Action 5 \u2014 omission)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The cumulative omissions (no disclosure, no recusal, no cooling-off adoption) create the conditions for direct ethical violation when AE\u0026R assigns Engineer D to city contracts",
      "proeth:element": "City Project Involvement Risk Created (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Disclosure and City Acceptance Seeking (Action 4 \u2014 omission or commission)",
  "proeth:counterfactual": "If Engineer D had proactively sought full disclosure and city acceptance, the conflict state would still exist but would be managed transparently; the cooling-off obligation might have been formally acknowledged and honored, preventing the escalation to active violation",
  "proeth:effect": "Conflict of Interest State Established / Cooling-Off Period Obligation Activated (Events 4 \u0026 5)",
  "proeth:necessaryFactors": [
    "Engineer D\u0027s awareness of the conflict-of-interest state upon joining AE\u0026R",
    "The availability of a disclosure mechanism (city ethics board, professional body, or direct city communication)",
    "The absence of automatic institutional detection or enforcement triggering disclosure",
    "Engineer D\u0027s choice not to proactively disclose (the omission)"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer D",
  "proeth:sufficientFactors": [
    "Failure to disclose + active assignment to city contracts = sufficient to convert a manageable conflict into an active ethical violation",
    "Proactive disclosure alone would not eliminate the conflict but would satisfy transparency obligations and potentially enable structured resolution"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer D chose to announce resignation from the City Engineer position and disclosed acceptance of employment at AE&R — triggering an immediate public transition event and rendering visible the historical pattern of AE&R receiving city contracts

Necessary Factors (NESS):
  • Engineer D's volitional decision to resign from city position
  • Engineer D's choice to disclose the AE&R hire publicly rather than privately or not at all
  • AE&R's decision to publicly announce the hire (Action 7 precursor)
  • The existence of a prior contractual relationship between AE&R and the city
Sufficient Factors:
  • Public resignation + public hire announcement together were sufficient to expose the prior AE&R contract history and initiate public and professional scrutiny of the conflict
Counterfactual Test: If Engineer D had resigned without disclosing the AE&R hire, or if AE&R had not publicly announced the hire, the prior contract history might have remained less visible, though the underlying conflict would still exist
Responsibility Attribution:

Agent: Engineer D (primary); AE&R principals (shared)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Resignation and Partial Disclosure (Action 2)
    Engineer D announces resignation and discloses AE&R employment acceptance, initiating the public transition
  2. Engineer D's Resignation Announced (Event 1)
    Public resignation triggers immediate transition scrutiny and activates ethics review obligations
  3. AE&R Public Hire Announcement (Event 2)
    AE&R amplifies the transition by publicly announcing Engineer D as a new associate
  4. Prior AE&R Contract History Exposed (Event 3)
    The combined public announcements render visible AE&R's historical pattern of city contract awards during Engineer D's tenure
  5. Cooling-Off Period Obligation Activated (Event 5)
    Exposure of the prior relationship activates the cooling-off period obligation under BER precedents
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#CausalChain_e25d16e1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer D chose to announce resignation from the City Engineer position and disclosed acceptance of employment at AE\u0026R \u2014 triggering an immediate public transition event and rendering visible the historical pattern of AE\u0026R receiving city contracts",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer D announces resignation and discloses AE\u0026R employment acceptance, initiating the public transition",
      "proeth:element": "Resignation and Partial Disclosure (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Public resignation triggers immediate transition scrutiny and activates ethics review obligations",
      "proeth:element": "Engineer D\u0027s Resignation Announced (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "AE\u0026R amplifies the transition by publicly announcing Engineer D as a new associate",
      "proeth:element": "AE\u0026R Public Hire Announcement (Event 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The combined public announcements render visible AE\u0026R\u0027s historical pattern of city contract awards during Engineer D\u0027s tenure",
      "proeth:element": "Prior AE\u0026R Contract History Exposed (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Exposure of the prior relationship activates the cooling-off period obligation under BER precedents",
      "proeth:element": "Cooling-Off Period Obligation Activated (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Resignation and Partial Disclosure (Action 2)",
  "proeth:counterfactual": "If Engineer D had resigned without disclosing the AE\u0026R hire, or if AE\u0026R had not publicly announced the hire, the prior contract history might have remained less visible, though the underlying conflict would still exist",
  "proeth:effect": "Engineer D\u0027s Resignation Announced / AE\u0026R Public Hire Announcement (Events 1 \u0026 2)",
  "proeth:necessaryFactors": [
    "Engineer D\u0027s volitional decision to resign from city position",
    "Engineer D\u0027s choice to disclose the AE\u0026R hire publicly rather than privately or not at all",
    "AE\u0026R\u0027s decision to publicly announce the hire (Action 7 precursor)",
    "The existence of a prior contractual relationship between AE\u0026R and the city"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer D (primary); AE\u0026R principals (shared)",
  "proeth:sufficientFactors": [
    "Public resignation + public hire announcement together were sufficient to expose the prior AE\u0026R contract history and initiate public and professional scrutiny of the conflict"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer D made the volitional decision to accept a position as associate at Firm AE&R — a firm that had an existing contractual relationship with the city — which, based on historical precedents established in BER cases from 1958 through 2015, activated a cooling-off period obligation

Necessary Factors (NESS):
  • Engineer D's acceptance of employment at AE&R specifically (not just any firm)
  • AE&R's status as a firm with active or recent city contracts overseen by Engineer D
  • Existence of BER precedent establishing cooling-off norms for such transitions
  • Engineer D's prior exercise of contract award or supervisory authority over AE&R
Sufficient Factors:
  • Employment acceptance at a firm with prior city contract relationship + Engineer D's prior oversight authority = sufficient to activate cooling-off obligation under established BER precedent
Counterfactual Test: If Engineer D had accepted employment at a firm with no prior city contract relationship, the cooling-off obligation specific to city projects would not have been activated; if no BER precedent existed, the obligation might not have been formally recognized
Responsibility Attribution:

Agent: Engineer D (primary); AE&R principals (contributing)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Participation in Contract Negotiations (Action 1)
    Engineer D accumulates oversight authority and decision-making power over AE&R contracts during city tenure
  2. Accepting Employment with AE&R (Action 3)
    Engineer D accepts associate position at AE&R, crossing the threshold that triggers ethics obligations
  3. Conflict of Interest State Established (Event 4)
    Formal conflict state arises, creating the predicate condition for cooling-off obligation
  4. Prior AE&R Contract History Exposed (Event 3)
    Public visibility of prior relationship confirms the factual basis for the cooling-off obligation
  5. Cooling-Off Period Obligation Activated (Event 5)
    BER precedent-based cooling-off obligation is activated, requiring Engineer D and AE&R to refrain from city project involvement for approximately one year
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#CausalChain_0bf63b61",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer D made the volitional decision to accept a position as associate at Firm AE\u0026R \u2014 a firm that had an existing contractual relationship with the city \u2014 which, based on historical precedents established in BER cases from 1958 through 2015, activated a cooling-off period obligation",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer D accumulates oversight authority and decision-making power over AE\u0026R contracts during city tenure",
      "proeth:element": "Participation in Contract Negotiations (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer D accepts associate position at AE\u0026R, crossing the threshold that triggers ethics obligations",
      "proeth:element": "Accepting Employment with AE\u0026R (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Formal conflict state arises, creating the predicate condition for cooling-off obligation",
      "proeth:element": "Conflict of Interest State Established (Event 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Public visibility of prior relationship confirms the factual basis for the cooling-off obligation",
      "proeth:element": "Prior AE\u0026R Contract History Exposed (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER precedent-based cooling-off obligation is activated, requiring Engineer D and AE\u0026R to refrain from city project involvement for approximately one year",
      "proeth:element": "Cooling-Off Period Obligation Activated (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accepting Employment with AE\u0026R (Action 3)",
  "proeth:counterfactual": "If Engineer D had accepted employment at a firm with no prior city contract relationship, the cooling-off obligation specific to city projects would not have been activated; if no BER precedent existed, the obligation might not have been formally recognized",
  "proeth:effect": "Cooling-Off Period Obligation Activated (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer D\u0027s acceptance of employment at AE\u0026R specifically (not just any firm)",
    "AE\u0026R\u0027s status as a firm with active or recent city contracts overseen by Engineer D",
    "Existence of BER precedent establishing cooling-off norms for such transitions",
    "Engineer D\u0027s prior exercise of contract award or supervisory authority over AE\u0026R"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer D (primary); AE\u0026R principals (contributing)",
  "proeth:sufficientFactors": [
    "Employment acceptance at a firm with prior city contract relationship + Engineer D\u0027s prior oversight authority = sufficient to activate cooling-off obligation under established BER precedent"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: When AE&R assigns Engineer D to city contracts, a direct ethical violation risk state is created: Engineer D would be working in responsible charge of projects for which they previously held oversight authority as City Engineer — the precise scenario the cooling-off period obligation was designed to prevent

Necessary Factors (NESS):
  • AE&R's decision to place Engineer D in responsible charge of active city contracts
  • The existence of active city contracts at AE&R that overlap with Engineer D's prior oversight jurisdiction
  • Engineer D's failure to invoke voluntary recusal (Action 5 not taken)
  • The prior establishment of the conflict-of-interest state (Event 4)
Sufficient Factors:
  • Assignment to responsible charge of city contracts + active conflict-of-interest state + absence of recusal = sufficient to create direct ethical violation
  • Even without formal assignment, Engineer D's presence at AE&R during active city contracts creates appearance-of-impropriety risk
Counterfactual Test: If AE&R had assigned Engineer D exclusively to non-city projects, or if Engineer D had invoked voluntary recusal, the direct ethical violation risk would not have materialized; if the cooling-off period had been adopted (Action 6), assignment to city contracts would have been deferred
Responsibility Attribution:

Agent: AE&R principals (primary decision-makers on assignment); Engineer D (shared — obligation to refuse improper assignment)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Accepting Employment with AE&R (Action 3)
    Engineer D joins AE&R, establishing the foundational conflict condition
  2. Cooling-Off Period Obligation Activated (Event 5)
    Ethics obligation requiring abstention from city project involvement is activated but not yet honored
  3. Voluntary Recusal Not Adopted (Action 5 — omission)
    Engineer D does not proactively recuse from city projects, leaving the decision to AE&R's assignment process
  4. AE&R Assigns Engineer D to City Contracts (Action 7)
    AE&R places Engineer D in responsible charge of active city contracts, completing the chain of ethical violation
  5. City Project Involvement Risk Created (Event 6)
    Direct ethical violation risk state is created, exposing Engineer D, AE&R, and the city to conflicts of interest, appearance of impropriety, and potential professional sanctions
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/10#",
    "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/10#CausalChain_d3d3ab72",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "When AE\u0026R assigns Engineer D to city contracts, a direct ethical violation risk state is created: Engineer D would be working in responsible charge of projects for which they previously held oversight authority as City Engineer \u2014 the precise scenario the cooling-off period obligation was designed to prevent",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer D joins AE\u0026R, establishing the foundational conflict condition",
      "proeth:element": "Accepting Employment with AE\u0026R (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Ethics obligation requiring abstention from city project involvement is activated but not yet honored",
      "proeth:element": "Cooling-Off Period Obligation Activated (Event 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer D does not proactively recuse from city projects, leaving the decision to AE\u0026R\u0027s assignment process",
      "proeth:element": "Voluntary Recusal Not Adopted (Action 5 \u2014 omission)",
      "proeth:step": 3
    },
    {
      "proeth:description": "AE\u0026R places Engineer D in responsible charge of active city contracts, completing the chain of ethical violation",
      "proeth:element": "AE\u0026R Assigns Engineer D to City Contracts (Action 7)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Direct ethical violation risk state is created, exposing Engineer D, AE\u0026R, and the city to conflicts of interest, appearance of impropriety, and potential professional sanctions",
      "proeth:element": "City Project Involvement Risk Created (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "AE\u0026R Assigns Engineer D to City Contracts (Action 7)",
  "proeth:counterfactual": "If AE\u0026R had assigned Engineer D exclusively to non-city projects, or if Engineer D had invoked voluntary recusal, the direct ethical violation risk would not have materialized; if the cooling-off period had been adopted (Action 6), assignment to city contracts would have been deferred",
  "proeth:effect": "City Project Involvement Risk Created (Event 6)",
  "proeth:necessaryFactors": [
    "AE\u0026R\u0027s decision to place Engineer D in responsible charge of active city contracts",
    "The existence of active city contracts at AE\u0026R that overlap with Engineer D\u0027s prior oversight jurisdiction",
    "Engineer D\u0027s failure to invoke voluntary recusal (Action 5 not taken)",
    "The prior establishment of the conflict-of-interest state (Event 4)"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "AE\u0026R principals (primary decision-makers on assignment); Engineer D (shared \u2014 obligation to refuse improper assignment)",
  "proeth:sufficientFactors": [
    "Assignment to responsible charge of city contracts + active conflict-of-interest state + absence of recusal = sufficient to create direct ethical violation",
    "Even without formal assignment, Engineer D\u0027s presence at AE\u0026R during active city contracts creates appearance-of-impropriety risk"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (17)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
Engineer D's resignation announcement before
Entity1 is before Entity2
Firm AE&R's announcement of Engineer D as newly hired associate time:before
http://www.w3.org/2006/time#before
Engineer D announces plans to step down as the City Engineer...Shortly after Engineer D's announceme... [more]
engineers' resignation from US government (Case 58-1) meets
Entity1 ends exactly when Entity2 begins
entry into contract with foreign government (Case 58-1) time:intervalMeets
http://www.w3.org/2006/time#intervalMeets
At about the time the various contract negotiations were wrapping up, the engineers resigned from th... [more]
Engineer B's selection for road project design (Case 11-12) before
Entity1 is before Entity2
Engineer B beginning preliminary design services (Case 11-12) time:before
http://www.w3.org/2006/time#before
With Engineer A's advice and concurrence, Smithtown selected Engineer B to provide design services f... [more]
Engineer B's termination (Case 11-12) before
Entity1 is before Entity2
Engineer A's firm offering to perform design work (Case 11-12) time:before
http://www.w3.org/2006/time#before
Following the termination of Engineer B under the terms and conditions of his contract with the town... [more]
Engineer A's resignation from private firm (Case 14-8) during
Entity1 occurs entirely within the duration of Entity2
legal review of the water rights analysis (Case 14-8) time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
During the legal review, Engineer A resigned from their firm and went to work for the State
State X highway department's refusal (Case 15-8) before
Entity1 is before Entity2
Engineer P joining AE firm as independent contractor (Case 15-8) time:before
http://www.w3.org/2006/time#before
In response, Engineer P left the State X highway department and joined the AE firm not as an 'employ... [more]
one-year cooling-off period (Case 15-8 / Engineer D scenario) starts
Entity1 and Entity2 start at the same time, Entity1 ends first
Engineer D's departure from City Engineer role time:intervalStarts
http://www.w3.org/2006/time#intervalStarts
Engineer D could voluntarily abstain from participation in procurement matters before the City...for... [more]
Engineer A's employment at private firm (Case 14-8) before
Entity1 is before Entity2
Engineer A's employment at the State (Case 14-8) time:before
http://www.w3.org/2006/time#before
Engineer A resigned from their firm and went to work for the State—the State being an objector to th... [more]
Engineer D's resignation announcement before
Entity1 is before Entity2
Engineer D accepting position at unnamed firm time:before
http://www.w3.org/2006/time#before
Engineer D announces plans to step down as the City Engineer and indicates that they accepted a posi... [more]
AE&R projects for the City during
Entity1 occurs entirely within the duration of Entity2
Engineer D's tenure as City Engineer time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
AE&R completed many projects for the City during Engineer D's tenure as City Engineer
contract negotiations by US government engineers (Case 58-1) overlaps
Entity1 starts before Entity2 and ends during Entity2
engineers' active US government employment (Case 58-1) time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Several of those engineers negotiated with at least two AE firms with the intent of taking part in t... [more]
Engineer A's review of Engineer B's preliminary work (Case 11-12) during
Entity1 occurs entirely within the duration of Entity2
Engineer B's preliminary design services (Case 11-12) time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
after Engineer B began to perform preliminary design services, Engineer A, in his role as town engin... [more]
Engineer A stamping water rights analysis (Case 14-8) before
Entity1 is before Entity2
legal review of the analysis (Case 14-8) time:before
http://www.w3.org/2006/time#before
Engineer A worked for a private company and stamped a water rights analysis for a client, and that a... [more]
Engineer P's request for permission to leave (Case 15-8) before
Entity1 is before Entity2
State X highway department's refusal of permission (Case 15-8) time:before
http://www.w3.org/2006/time#before
Engineer P requested permission from the State X highway department to accept the new position; howe... [more]
Engineer D's isolation from former projects during
Entity1 occurs entirely within the duration of Entity2
remaining active duration of former City contracts time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects unti... [more]
confidentiality obligation overlaps
Entity1 starts before Entity2 and ends during Entity2
Engineer D's post-employment period at AE&R time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps
Confidentiality is another ethical obligation that continues after one severs employment (Code Secti... [more]
Engineer D's tenure as City Engineer before
Entity1 is before Entity2
Engineer D's employment at Firm AE&R time:before
http://www.w3.org/2006/time#before
Engineer D announces plans to step down as the City Engineer...Shortly after Engineer D's announceme... [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.