{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Action_Franchiser_Instructs_Confidentiality_to_Engineer_B",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engineer B could have immediately declined the engagement upon receiving the confidentiality instruction",
    "Engineer B could have accepted the engagement but negotiated with the franchiser to modify or remove the confidentiality condition before proceeding",
    "Engineer B could have sought guidance from his professional engineering society or legal counsel before deciding whether to accept the condition"
  ],
  "proeth-scenario:characterMotivation": "The franchiser sought to control the narrative of its transition, likely fearing that early disclosure would create professional friction, prompt Engineer A to become uncooperative during the remaining contract period, or complicate the review of Engineer A\u0027s prior work. The instruction reflects a desire to manage business risk through information control.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining immediately would have protected Engineer B\u0027s ethical standing entirely, though it would mean forgoing the engagement and potentially straining his relationship with the franchiser.",
    "Negotiating the condition would have demonstrated professional assertiveness and may have led the franchiser to accept a more ethical arrangement, though the franchiser might have withdrawn the offer.",
    "Seeking outside guidance would have provided Engineer B with informed support for his decision, potentially strengthening his position in negotiations with the franchiser, though it would have delayed the engagement."
  ],
  "proeth-scenario:decisionSignificance": "This is a pivotal teaching moment on the limits of client authority. Clients can legitimately request confidentiality on many matters, but they cannot ethically direct an engineer to conceal information in ways that harm another engineer or compromise the public interest. Students must learn to distinguish legitimate confidentiality from ethically impermissible concealment.",
  "proeth-scenario:ethicalTension": "Client confidentiality and business prerogative vs. Engineer B\u0027s professional obligation of honesty and his duty not to act in a manner that harms a fellow engineer\u0027s legitimate professional interests. The franchiser\u0027s instruction places Engineer B in a position where client loyalty directly conflicts with core engineering ethics canons.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer B\u0027s professional integrity and license standing; Engineer A\u0027s right to fair professional treatment; the broader norm of trust within the engineering profession; potential NSPE Code of Ethics violations if Engineer B complies; the franchiser\u0027s own legal and reputational exposure.",
  "proeth:description": "At the time of retaining Engineer B, the franchiser explicitly instructed Engineer B not to disclose his relationship with the franchiser to Engineer A, imposing a confidentiality condition on the engagement.",
  "proeth:foreseenUnintendedEffects": [
    "Placing Engineer B in direct conflict between client loyalty and professional obligations under NSPE Code Section III.8.a",
    "Potentially depriving Engineer A of the opportunity to provide context or explanations for his design decisions",
    "Creating an ethically compromised situation for Engineer B regardless of which obligation he prioritized"
  ],
  "proeth:fulfillsObligation": [
    "Client\u0027s prerogative to set terms of engagement with retained engineers",
    "Business interest in managing a sensitive personnel and vendor transition"
  ],
  "proeth:guidedByPrinciple": [
    "Client confidentiality and business control",
    "Transition management"
  ],
  "proeth:hasAgent": "Franchiser (Client/Major Franchise Organization)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client control over transition vs. Engineer B\u0027s independent professional obligations",
    "proeth:resolutionReasoning": "The franchiser resolved this in favor of its own business interests, placing the burden of the ethical conflict entirely on Engineer B"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Control the transition narrative, prevent potential disruption or conflict between the two engineers, and protect the franchiser\u0027s business interests during the sensitive overlap period",
  "proeth:requiresCapability": [
    "Contract terms negotiation",
    "Business transition management",
    "Understanding of engineering professional norms (at least implicitly)"
  ],
  "proeth:temporalMarker": "At the time of Engineer B\u0027s retention; prior to Engineer B\u0027s review",
  "proeth:violatesObligation": [
    "Spirit of NSPE Code Section III.8.a, which supports Engineer A\u0027s right to know his work is under review",
    "Fair dealing toward Engineer A as a professional whose work and reputation were being evaluated"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Franchiser Instructs Confidentiality to Engineer B"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Action_Engineer_B_Accepts_Project_Without_Clarification",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Ask the franchiser directly why disclosure to Engineer A was prohibited before agreeing to the condition",
    "Accept the engagement but explicitly state to the franchiser that he would need to disclose his role to Engineer A before conducting any review of Engineer A\u0027s work",
    "Decline the engagement on the grounds that the confidentiality condition was incompatible with his professional ethical obligations"
  ],
  "proeth-scenario:characterMotivation": "Engineer B likely accepted the engagement motivated by professional opportunity, financial benefit, and a desire to build a relationship with a significant client. He may have rationalized the confidentiality condition as a routine business request or assumed the franchiser had legitimate reasons, prioritizing the opportunity over careful ethical scrutiny of the condition imposed.",
  "proeth-scenario:consequencesIfAlternative": [
    "Asking for clarification might have revealed the franchiser\u0027s reasoning, potentially exposing whether the instruction was a legitimate business concern or an attempt to use Engineer B against Engineer A\u0027s interests, allowing for a more informed decision.",
    "Accepting with a stated disclosure commitment would have placed Engineer B on ethically stronger footing from the outset, though the franchiser might have rejected this condition and sought a more compliant engineer.",
    "Declining would have fully protected Engineer B\u0027s ethical standing and sent a clear signal to the franchiser that professional ethics are non-negotiable conditions of engagement, though at the cost of the business opportunity."
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that the moment of accepting an engagement is a critical ethical checkpoint. Engineers must actively interrogate conditions attached to their retention, especially when those conditions involve concealment from other professionals. Passive acceptance of a client\u0027s framing does not absolve an engineer of ethical responsibility for what follows.",
  "proeth-scenario:ethicalTension": "Professional self-interest and deference to client instructions vs. the engineer\u0027s independent ethical obligation to scrutinize conditions of engagement that may conflict with professional duties. Engineer B\u0027s acceptance without clarification reflects a tension between commercial pragmatism and proactive ethical responsibility.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer B\u0027s long-term professional credibility and license; the precedent set for how Engineer B will handle future client pressure; Engineer A\u0027s ongoing professional interests; the quality and integrity of the engineering review itself, which may be compromised if conducted under ethically clouded conditions.",
  "proeth:description": "Engineer B accepted the franchiser\u0027s engagement and its confidentiality condition without first exploring or clarifying the reason why the client did not want Engineer B to disclose his relationship with the franchiser to Engineer A.",
  "proeth:foreseenUnintendedEffects": [
    "Accepting the confidentiality condition without understanding its rationale left Engineer B without a principled basis for evaluating whether compliance was ethically permissible",
    "Engineer B\u0027s subsequent decision to disclose anyway suggests the confidentiality condition was not fully internalized or agreed to at the outset",
    "Failure to clarify potentially enabled the franchiser to place Engineer B in an ethically untenable position"
  ],
  "proeth:guidedByPrinciple": [
    "NSPE Code Section II.4: duty as faithful agent and trustee",
    "Professional responsibility to assess ethical dimensions of engagements before acceptance",
    "Informed consent and clarity in professional relationships"
  ],
  "proeth:hasAgent": "Engineer B (Successor Design Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Promptness in serving client needs vs. ethical due diligence before engagement",
    "proeth:resolutionReasoning": "Engineer B implicitly prioritized client responsiveness over ethical clarification, accepting the engagement without resolving the conflict between the confidentiality instruction and his Section III.8.a obligations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure the engineering engagement and begin work promptly in response to the client\u0027s stated urgency regarding pending design concerns",
  "proeth:requiresCapability": [
    "Professional ethical judgment",
    "Client relationship management",
    "Understanding of NSPE Code obligations when reviewing another engineer\u0027s work"
  ],
  "proeth:temporalMarker": "At the time of retention; before beginning the design review",
  "proeth:violatesObligation": [
    "Professional obligation to clarify the ethical implications of client instructions before accepting an engagement that places professional duties in conflict (noted explicitly as ethically problematic by the Board)",
    "Duty of due diligence in understanding the terms and ethical dimensions of a new client relationship"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Accepts Project Without Clarification"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Action_Engineer_B_Reviews_Design_Information",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Pause the review and notify the franchiser that he intended to disclose his role to Engineer A before proceeding further",
    "Conduct only a high-level preliminary assessment and refuse to finalize any findings until the disclosure issue was resolved",
    "Withdraw from the engagement entirely rather than conduct a substantive review of a colleague\u0027s work under conditions of concealment"
  ],
  "proeth-scenario:characterMotivation": "Engineer B proceeded with the review in fulfillment of his contractual obligation to the franchiser, likely believing that conducting the technical work was separable from the ethical question of disclosure, or that he could resolve the disclosure issue after completing his initial assessment. He may have also felt time pressure given the pending design concerns at multiple facilities.",
  "proeth-scenario:consequencesIfAlternative": [
    "Pausing and notifying the franchiser would have been a strong ethical stand, potentially prompting the franchiser to reconsider the confidentiality instruction, though it risked the franchiser terminating Engineer B\u0027s engagement.",
    "Limiting the scope of review would have partially mitigated the ethical harm while maintaining some service to the franchiser, though it would have been a compromise rather than a full resolution of the ethical problem.",
    "Withdrawing entirely would have been the most ethically consistent response given that the problematic condition remained in place, fully protecting Engineer B\u0027s integrity, though at the cost of the engagement."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that taking substantive professional action under ethically compromised conditions deepens moral culpability. Students should understand that each step taken under a problematic arrangement is a new decision point, and that proceeding with technical work does not suspend or defer ethical obligations \u2014 it enacts them.",
  "proeth-scenario:ethicalTension": "Fulfillment of contractual duties to the client vs. the ethical obligation to avoid reviewing and potentially undermining a fellow engineer\u0027s work under conditions of concealment. Proceeding with the review while still bound by the concealment instruction compounds the initial ethical compromise of accepting the condition.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The legitimacy and fairness of the design review itself; Engineer A\u0027s right to respond to or contextualize his own design decisions before they are evaluated by an undisclosed successor; public safety implications if the review process is compromised by its ethically irregular structure; Engineer B\u0027s professional standing.",
  "proeth:description": "One week after being retained and receiving the confidentiality instruction, Engineer B proceeded to review the pending design information related to several franchise facilities that had been designed by Engineer A.",
  "proeth:foreseenUnintendedEffects": [
    "Conducting the review without Engineer A\u0027s knowledge meant Engineer B lacked the benefit of Engineer A\u0027s explanations or context for technical decisions, potentially limiting the review\u0027s completeness",
    "The review created the factual predicate for the subsequent notification decision that would put Engineer B in direct conflict with the client\u0027s confidentiality instruction"
  ],
  "proeth:fulfillsObligation": [
    "Contractual obligation to the franchiser to perform the requested design review",
    "Professional competence obligation to conduct a thorough engineering review"
  ],
  "proeth:guidedByPrinciple": [
    "NSPE Code Section II.4: faithful agent and trustee obligations to the client",
    "NSPE Code Section III.8.a: professional norms regarding review of another engineer\u0027s work",
    "Competent and thorough engineering practice"
  ],
  "proeth:hasAgent": "Engineer B (Successor Design Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client service urgency vs. timely notification to Engineer A under Section III.8.a",
    "proeth:resolutionReasoning": "Engineer B proceeded with the review, deferring the notification decision; the Board accepted this sequencing as consistent with Section III.8.a given the short timeframe involved"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill the scope of his engagement by assessing pending design concerns across the franchise facilities and forming preliminary conclusions to report to the franchiser",
  "proeth:requiresCapability": [
    "Engineering design review and analysis",
    "Evaluation of facility design concerns across multiple locations",
    "Professional judgment in assessing another engineer\u0027s design work"
  ],
  "proeth:temporalMarker": "One week after retention; prior to notifying Engineer A",
  "proeth:violatesObligation": [
    "NSPE Code Section III.8.a: proceeding with review of another engineer\u0027s work without prior notification to that engineer (though the Board ultimately found the one-week delay before notification was not unreasonable)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Reviews Design Information"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Action_Engineer_B_Notifies_Engineer_A_of_Relationship_and",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Maintain the confidentiality as instructed and never disclose his relationship or review findings to Engineer A",
    "Disclose to Engineer A immediately upon being retained, before conducting any review, defying the franchiser\u0027s instruction from the outset",
    "Withdraw from the engagement without disclosing to Engineer A, removing himself from the ethical conflict without fully resolving it"
  ],
  "proeth-scenario:characterMotivation": "Engineer B ultimately chose to disclose his relationship and review findings to Engineer A, likely motivated by his professional conscience and recognition that continued concealment violated his ethical obligations under engineering codes of conduct. The one-week delay suggests an internal deliberation process in which professional duty eventually overcame the client\u0027s instruction and initial self-interest.",
  "proeth-scenario:consequencesIfAlternative": [
    "Maintaining confidentiality throughout would have constituted a clear violation of engineering ethics codes, potentially exposing Engineer B to disciplinary action, and would have allowed Engineer A\u0027s professional interests to be harmed without recourse.",
    "Immediate disclosure upon retention would have been the most ethically consistent course, fully honoring professional obligations from the start, though it would likely have resulted in the franchiser terminating Engineer B\u0027s engagement immediately.",
    "Withdrawing without disclosure would have protected Engineer B from further complicity but would have left Engineer A uninformed and unable to respond to the review of his work, representing an incomplete ethical resolution."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that corrective ethical action, even when delayed, carries moral weight and practical consequence. However, students should critically examine whether disclosure after the fact fully remedies the prior ethical compromises, and whether Engineer B\u0027s overall conduct \u2014 accepting the condition, proceeding with the review, and then disclosing \u2014 represents an adequate ethical standard or a cautionary example of reactive rather than proactive ethics.",
  "proeth-scenario:ethicalTension": "Loyalty to the client\u0027s explicit instruction vs. the engineer\u0027s overriding professional obligation of honesty, fairness to fellow engineers, and adherence to the NSPE Code of Ethics. Engineer B\u0027s disclosure represents a resolution of this tension in favor of professional ethics, though the delay and the prior acceptance of the condition mean the resolution is partial rather than complete.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer B\u0027s professional integrity and license standing; the franchiser\u0027s trust and potential termination of Engineer B\u0027s engagement as a consequence of defying its instruction; Engineer A\u0027s ability to respond to the review and protect his professional reputation; the broader norm that engineering ethics cannot be overridden by client instructions; potential NSPE ethics board scrutiny of all parties.",
  "proeth:description": "Following his review of the design information, and contrary to the franchiser\u0027s explicit instruction, Engineer B notified Engineer A of his relationship with the franchiser and the preliminary results of his design review.",
  "proeth:foreseenUnintendedEffects": [
    "Direct violation of the franchiser\u0027s explicit confidentiality instruction, constituting a breach of the faithful agent and trustee duty under NSPE Code Section II.4",
    "Potential harm to the franchiser\u0027s business interests and transition management strategy",
    "Possible prejudice to the franchiser\u0027s ability to control the narrative of the engineering transition"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code Section III.8.a: notification to Engineer A that his work was being reviewed by another engineer for the same client"
  ],
  "proeth:guidedByPrinciple": [
    "NSPE Code Section III.8.a: professional transparency between engineers when one reviews another\u0027s work",
    "NSPE Code Section II.4: faithful agent and trustee obligations",
    "Professional integrity and peer respect among engineers"
  ],
  "proeth:hasAgent": "Engineer B (Successor Design Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional obligation to notify Engineer A (Section III.8.a) vs. duty of loyalty and fair dealing to the client (Section II.4)",
    "proeth:resolutionReasoning": "Engineer B resolved the conflict in favor of Section III.8.a notification, but the Board concluded this was the wrong resolution: the faithful agent and trustee duty under Section II.4, combined with the explicit client instruction, should have prevailed; the Board found that the benefits of disclosure did not outweigh the detriments to the client"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill his professional obligation under NSPE Code Section III.8.a to notify Engineer A that his work was being reviewed, and to provide Engineer A with the preliminary results so Engineer A could offer context or explanations for his technical decisions",
  "proeth:requiresCapability": [
    "Ethical judgment in resolving competing professional obligations",
    "Professional communication with peer engineers",
    "Understanding of NSPE Code Sections II.4 and III.8.a and their relative weight"
  ],
  "proeth:temporalMarker": "One week after retention; immediately following completion of the design review",
  "proeth:violatesObligation": [
    "NSPE Code Section II.4: duty as faithful agent and trustee to act in the client\u0027s best interests",
    "Direct client instruction not to disclose Engineer B\u0027s relationship with the franchiser to Engineer A",
    "General duty of loyalty and fair dealing to the client as defined by the Board\u0027s interpretation of \u0027trustee\u0027"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Notifies Engineer A of Relationship and Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Action_Franchiser_Terminates_Engineer_A",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Terminate Engineer A immediately without notice or transition period",
    "Communicate concerns to Engineer A and offer a remediation period before deciding on non-renewal",
    "Conduct a transparent competitive review process, notifying Engineer A that the contract is under evaluation"
  ],
  "proeth-scenario:characterMotivation": "The franchiser sought to exercise its legitimate contractual right to change service providers, likely driven by business dissatisfaction, cost considerations, or a desire for fresh engineering perspectives. The formal notice of non-renewal reflects an intent to act within legal bounds while pursuing a strategic transition.",
  "proeth-scenario:consequencesIfAlternative": [
    "Immediate termination without notice could expose the franchiser to contractual liability, leave facilities without engineering coverage, and damage the franchiser\u0027s professional reputation in the engineering community.",
    "Offering a remediation period might resolve underlying concerns and preserve a proven working relationship, avoiding transition risks and costs, though it delays any desired change.",
    "A transparent competitive review would uphold fairness norms, potentially motivate Engineer A to improve, and give Engineer B and others a clear ethical basis for participation, reducing the ethical complications that follow in this case."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that clients retain the legal right to terminate professional relationships, but the manner and process of transition carries ethical weight. Students should examine how business decisions create downstream ethical obligations for all parties involved.",
  "proeth-scenario:ethicalTension": "Legitimate business autonomy vs. professional fairness and duty of care to an established engineering partner. The franchiser\u0027s right to choose its engineers conflicts with the implicit professional trust built over a multi-year relationship.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s livelihood and professional reputation; continuity and quality of engineering services for the franchiser\u0027s facilities; potential public safety implications if the transition is mishandled; integrity of the professional engineering marketplace.",
  "proeth:description": "The franchiser made a deliberate business decision to end its multi-year engineering relationship with Engineer A, providing formal notice of non-renewal before the contract expired.",
  "proeth:foreseenUnintendedEffects": [
    "Disruption to ongoing design projects",
    "Need to manage transition overlap between Engineer A and a successor engineer",
    "Potential for ethical complications during the transition period"
  ],
  "proeth:fulfillsObligation": [
    "Contractual obligation to provide notice of non-renewal",
    "Business prerogative to select engineering partners"
  ],
  "proeth:guidedByPrinciple": [
    "Client autonomy in selecting engineering services",
    "Contractual good faith"
  ],
  "proeth:hasAgent": "Franchiser (Client/Major Franchise Organization)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Business continuity vs. fair treatment of incumbent engineer",
    "proeth:resolutionReasoning": "Franchiser prioritized operational continuity by overlapping the transition, leveraging the contractual notice period to bring in a successor without waiting for full expiration"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Transition to a new engineering firm while maintaining business continuity and legal compliance with contractual notice requirements",
  "proeth:requiresCapability": [
    "Contract management",
    "Vendor relationship management",
    "Business continuity planning"
  ],
  "proeth:temporalMarker": "Several years into the relationship; prior to contract expiration",
  "proeth:withinCompetence": true,
  "rdfs:label": "Franchiser Terminates Engineer A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Action_Franchiser_Retains_Engineer_B_Early",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Wait until Engineer A\u0027s contract formally expires before retaining Engineer B",
    "Retain Engineer B in a disclosed advisory capacity with Engineer A\u0027s knowledge, framing it as a collaborative transition",
    "Hire an independent third-party reviewer unconnected to the successor role to assess pending design concerns"
  ],
  "proeth-scenario:characterMotivation": "The franchiser sought to minimize operational disruption and ensure continuity of engineering oversight during the transition period. By retaining Engineer B early, the franchiser aimed to address pending design concerns without waiting for Engineer A\u0027s contract to lapse, prioritizing business continuity over transparency.",
  "proeth-scenario:consequencesIfAlternative": [
    "Waiting until contract expiration would eliminate the overlap conflict entirely, though it risks a gap in engineering coverage and delays resolution of pending design concerns.",
    "A disclosed advisory engagement would respect Engineer A\u0027s professional standing, potentially allow for knowledge transfer, and place Engineer B in a far less ethically compromised position, though it requires the franchiser to be transparent about its transition plans.",
    "An independent third-party review would address pending design concerns without implicating the successor engineer, preserving cleaner professional boundaries, though it adds cost and complexity."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates how client decisions that appear purely logistical can create layered ethical complications for engineers. Students should recognize that the timing of a successor engineer\u0027s engagement relative to an incumbent\u0027s active contract is ethically significant, not merely a scheduling matter.",
  "proeth-scenario:ethicalTension": "Operational efficiency and client prerogative vs. professional fairness and transparency toward the incumbent engineer. The franchiser\u0027s desire for a seamless transition conflicts with Engineer A\u0027s reasonable expectation to complete his contractual scope without a shadow competitor reviewing his work.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional dignity and ability to complete his contractual obligations; integrity of the design review process; Engineer B\u0027s ethical standing from the moment of engagement; potential for conflicting or duplicative engineering judgments on active projects affecting public safety.",
  "proeth:description": "Before Engineer A\u0027s contract expired, the franchiser proactively retained Engineer B to review pending design concerns across multiple franchise facilities, initiating a transition overlap.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer B would be reviewing Engineer A\u0027s work while Engineer A was still under contract",
    "Potential for conflict between Engineer B\u0027s obligations to the client and professional norms regarding review of another engineer\u0027s active work",
    "Risk of Engineer A learning of Engineer B\u0027s engagement during the active contract period"
  ],
  "proeth:fulfillsObligation": [
    "Client\u0027s right to seek engineering services from a provider of its choosing",
    "Business obligation to address pending design concerns without delay"
  ],
  "proeth:guidedByPrinciple": [
    "Client autonomy",
    "Business continuity",
    "Faithful stewardship of franchise operations"
  ],
  "proeth:hasAgent": "Franchiser (Client/Major Franchise Organization)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Operational urgency vs. professional transparency toward Engineer A",
    "proeth:resolutionReasoning": "Franchiser resolved the conflict in favor of operational urgency and transition control, accepting the ethical tension created by overlapping the two engineering relationships"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Ensure uninterrupted engineering oversight of pending design concerns and establish Engineer B as a capable successor before Engineer A\u0027s departure",
  "proeth:requiresCapability": [
    "Engineering vendor selection and management",
    "Assessment of pending design concerns",
    "Contract negotiation"
  ],
  "proeth:temporalMarker": "Before Engineer A\u0027s contract expiration; during the notice period",
  "proeth:violatesObligation": [
    "Spirit of fair dealing toward Engineer A, whose work was being reviewed without full transparency during an active contractual relationship"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Franchiser Retains Engineer B Early"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Contract_Non-Renewal_Notice_Received",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What obligations does Engineer A retain to the franchiser after receiving non-renewal notice?",
    "Does the franchiser have an ethical duty to give Engineer A sufficient notice to complete pending work responsibly?",
    "How should pending design concerns be handled when a professional relationship is ending?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences surprise, disappointment, and concern about income loss and professional standing; franchiser may feel relief or discomfort about ending a long relationship; no emotional impact on Engineer B yet",
  "proeth-scenario:ethicalImplications": "Reveals tension between contractual rights (franchiser\u0027s right to non-renew) and ethical obligations (duty to ensure continuity and safety); highlights that termination of a professional relationship must be managed with care to avoid harm to third parties and public interest",
  "proeth-scenario:learningMoment": "Contract termination does not end professional obligations immediately; both parties retain duties during the wind-down period, and pending technical concerns must be responsibly addressed regardless of relationship status",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Income stream threatened; professional identity disrupted; must manage wind-down while potentially seeking new clients",
    "engineer_b": "Not yet involved but this event creates the vacancy that will lead to his engagement",
    "franchiser": "Now accountable for ensuring continuity of design services; faces logistical and ethical challenges in transition",
    "public": "Risk of design service gap if transition is poorly managed; pending concerns left unresolved pose potential safety issues"
  },
  "proeth:activatesConstraint": [
    "Orderly_Transition_Obligation",
    "Confidentiality_Of_Client_Information_During_Winddown",
    "Engineer_A_Continued_Duty_Until_Expiry"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/126#Action_Franchiser_Terminates_Engineer_A",
  "proeth:causesStateChange": "Professional relationship enters wind-down phase; Engineer A now operates under a defined end date; franchiser begins successor search; pending design concerns become urgent to resolve",
  "proeth:createsObligation": [
    "Engineer_A_Must_Continue_Competent_Service_Until_Expiry",
    "Franchiser_Must_Allow_Orderly_Transition",
    "Pending_Design_Concerns_Must_Be_Addressed"
  ],
  "proeth:description": "Engineer A receives formal notice from the franchiser that their contract will not be renewed, signaling the end of the multi-year professional relationship. This notice creates a defined countdown to contract expiration and triggers Engineer A\u0027s awareness that succession planning is underway.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Several weeks before contract expiration (precise timing unspecified)",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Contract Non-Renewal Notice Received"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Multi-Year_Relationship_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What professional obligations does a long-term relationship create beyond those in a single contract?",
    "How should engineers protect themselves from over-reliance on a single client relationship?",
    "Does a multi-year relationship create any implied duty of good faith in termination?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A likely feels professional security and loyalty; franchiser views Engineer A as a reliable resource; no tension yet but seeds of dependency are planted",
  "proeth-scenario:ethicalImplications": "Reveals how sustained professional relationships generate informal expectations that may not be legally binding but carry ethical weight; raises questions about what clients owe long-term service providers beyond contractual minimums",
  "proeth-scenario:learningMoment": "Long-term professional relationships create both value and vulnerability; engineers should be aware of how dependency relationships can complicate transitions and ethical obligations",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Established professional identity and income stream tied to this relationship; vulnerability created by over-reliance on single client",
    "engineer_b": "Not yet involved; unaware of relationship",
    "franchiser": "Institutional knowledge locked in Engineer A; transition costs will be high if relationship ends",
    "public": "Benefiting from consistent design standards maintained by experienced engineer"
  },
  "proeth:activatesConstraint": [
    "Loyalty_To_Client_Constraint",
    "Continuity_Of_Service_Expectation"
  ],
  "proeth:causesStateChange": "Stable professional relationship active; Engineer A holds primary design authority for franchiser; mutual reliance established",
  "proeth:createsObligation": [
    "Engineer_A_Ongoing_Service_Duty",
    "Franchiser_Good_Faith_Dealing"
  ],
  "proeth:description": "Engineer A and the franchiser had developed a long-standing professional relationship over multiple years, creating mutual expectations of continuity and trust. This relationship forms the baseline context from which all subsequent disruptions emerge.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to case events (background state)",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Multi-Year Relationship Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Parallel_Engagement_Overlap_Created",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what point does accepting an engagement with a client become ethically problematic if a predecessor engineer is still under contract?",
    "What should Engineer B have done upon learning that Engineer A was still under contract?",
    "Does the franchiser\u0027s instruction to maintain confidentiality change Engineer B\u0027s ethical obligations?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer B may feel uncomfortable if he later learns the full picture; Engineer A, once informed, will likely feel blindsided and professionally disrespected; franchiser may be indifferent or deliberately strategic",
  "proeth-scenario:ethicalImplications": "Exposes fundamental tension between client authority and professional ethical codes; reveals how clients can inadvertently or deliberately place engineers in ethically untenable positions; highlights the NSPE requirement that successor engineers notify predecessors before proceeding",
  "proeth-scenario:learningMoment": "The simultaneous engagement of a successor engineer before the predecessor\u0027s contract expires is a critical ethical trigger point; engineers must understand their obligations when asked to operate in this overlap zone",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional standing undermined while still under contract; work potentially being second-guessed without knowledge or opportunity to respond",
    "engineer_b": "Placed in ethically compromised position by franchiser\u0027s instructions; professional reputation at risk",
    "franchiser": "Gains tactical advantage but creates legal and ethical exposure; potentially violating implied duties to Engineer A",
    "public": "Risk of design errors if two engineers are working at cross-purposes without coordination"
  },
  "proeth:activatesConstraint": [
    "Conflict_Of_Interest_Constraint",
    "Predecessor_Engineer_Rights_Constraint",
    "Professional_Courtesy_Norms",
    "NSPE_Code_Section_On_Successor_Engineers"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/126#Action_Franchiser_Retains_Engineer_B_Early",
  "proeth:causesStateChange": "Two engineers now simultaneously engaged with same client on related matters; Engineer A unaware; ethical conflict zone activated; NSPE successor engineer norms now directly applicable",
  "proeth:createsObligation": [
    "Engineer_B_Must_Contact_Engineer_A_Before_Proceeding",
    "Engineer_B_Must_Not_Review_Work_Without_Notification",
    "Franchiser_Must_Not_Use_Engineer_B_To_Circumvent_Engineer_A"
  ],
  "proeth:description": "As a direct result of the franchiser retaining Engineer B before Engineer A\u0027s contract expired, a period of simultaneous engagement exists where both engineers hold roles related to the same client. This overlap creates an inherently conflicted situation where Engineer A remains the active engineer of record while Engineer B is conducting preliminary reviews.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Between Engineer B\u0027s retention and Engineer A\u0027s contract expiration",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Parallel Engagement Overlap Created"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Confidentiality_Instruction_Imposed_on_Engineer_B",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is an engineer ever ethically permitted to follow a client\u0027s instruction to conceal his engagement from a predecessor engineer still under contract?",
    "What should Engineer B have said or done when given this instruction?",
    "How does this instruction affect the franchiser\u0027s own ethical standing in this situation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer B may feel pressure, discomfort, or moral unease; franchiser likely views this as a routine business instruction; Engineer A is unaware and thus unaffected emotionally at this moment",
  "proeth-scenario:ethicalImplications": "Illustrates the foundational principle that professional ethical obligations are not subordinate to client preferences; reveals how clients can attempt to weaponize engineers\u0027 loyalty against other professionals; raises questions about complicity when engineers accept ethically problematic instructions without objection",
  "proeth-scenario:learningMoment": "Client instructions that conflict with professional ethical codes are not binding on engineers; engineers must recognize when a client instruction crosses the line from reasonable business direction into ethically impermissible territory",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Unaware but directly harmed by being kept in the dark about a review of his work",
    "engineer_b": "Professional integrity immediately at risk; must choose between client compliance and ethical code adherence; career consequences possible either way",
    "franchiser": "Attempting to control information flow for business reasons but creating ethical and potentially legal liability",
    "public": "Indirectly at risk if suppression of information leads to uncoordinated design decisions"
  },
  "proeth:activatesConstraint": [
    "Client_Instruction_Compliance_Pressure",
    "Competing_Professional_Ethics_Obligation",
    "Engineer_B_Notification_Duty_To_Engineer_A"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/126#Action_Franchiser_Instructs_Confidentiality_to_Engineer_B",
  "proeth:causesStateChange": "Engineer B now operating under a client instruction that directly conflicts with professional ethical codes; the instruction itself is ethically suspect and creates an immediate obligation for Engineer B to push back or clarify",
  "proeth:createsObligation": [
    "Engineer_B_Must_Evaluate_Whether_Instruction_Is_Ethically_Permissible",
    "Engineer_B_Must_Resolve_Conflict_Between_Client_And_Code"
  ],
  "proeth:description": "The franchiser\u0027s explicit instruction to Engineer B not to disclose his relationship to Engineer A becomes an active constraint on Engineer B\u0027s behavior, creating a direct conflict between client instructions and professional ethical obligations. This is not a decision by Engineer B but an external imposition that shapes the ethical landscape he must navigate.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "At time of Engineer B\u0027s retention (before review begins)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Confidentiality Instruction Imposed on Engineer B"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Engineer_A_Kept_Uninformed_During_Review",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the length of time Engineer A was kept uninformed affect the severity of the ethical violation?",
    "What concrete harms does Engineer A suffer from being kept uninformed, even if his contract ultimately expires normally?",
    "Should Engineer B have disclosed immediately upon retention, or was a brief delay to assess the situation acceptable?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A is unaware and thus not yet emotionally affected; Engineer B may experience growing discomfort as he proceeds with the review; franchiser is indifferent or satisfied with information control",
  "proeth-scenario:ethicalImplications": "Reveals that information asymmetry created by client instruction can itself constitute an ethical violation; highlights how professional harm can occur without the victim\u0027s awareness; raises questions about the temporal dimension of ethical obligations",
  "proeth-scenario:learningMoment": "The harm of withholding information from a predecessor engineer is not merely procedural; it denies the engineer the opportunity to defend their work, provide context, and maintain professional dignity. Time matters in ethical violations.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional interests harmed without awareness; unable to provide context or respond to review findings; dignity as a professional undermined",
    "engineer_b": "Accumulating ethical liability with each day of non-disclosure; review results obtained under ethically compromised conditions",
    "franchiser": "Temporarily achieving information control goal but building ethical and reputational risk",
    "public": "Design review proceeding without benefit of predecessor engineer\u0027s institutional knowledge and context"
  },
  "proeth:activatesConstraint": [
    "Engineer_A_Right_To_Know_About_Review_Of_Work",
    "Predecessor_Engineer_Dignity_Constraint",
    "Professional_Courtesy_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/126#Action_Franchiser_Instructs_Confidentiality_to_Engineer_B",
  "proeth:causesStateChange": "Engineer A operates under false assumption of sole engagement; his work is being evaluated without his knowledge or opportunity to respond; professional harm accumulating in background",
  "proeth:createsObligation": [
    "Obligation_To_Remedy_Information_Asymmetry_As_Soon_As_Possible"
  ],
  "proeth:description": "As a direct consequence of the franchiser\u0027s confidentiality instruction and Engineer B\u0027s initial compliance, Engineer A remains unaware that his work is being reviewed by a successor engineer while he is still under contract. This state of uninformed vulnerability persists for approximately one week.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During the one-week period between Engineer B\u0027s retention and his notification to Engineer A",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer A Kept Uninformed During Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Design_Review_Completed_Under_Conflict",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the fact that Engineer B eventually notified Engineer A retroactively cure the ethical problem with conducting the review first?",
    "Should the franchiser be required to give Engineer A an opportunity to respond to Engineer B\u0027s preliminary findings?",
    "How does the absence of Engineer A\u0027s input potentially affect the quality and fairness of the design review?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer B may feel professional satisfaction at completing the review but underlying discomfort about the conditions; franchiser is satisfied; Engineer A remains unaware",
  "proeth-scenario:ethicalImplications": "Demonstrates that technical competence does not excuse procedural ethical violations; reveals how the conditions under which professional work is conducted affect its integrity; raises questions about whether findings obtained through ethically compromised processes should carry full professional weight",
  "proeth-scenario:learningMoment": "The sequence in which professional actions occur matters ethically; a technically competent review conducted under ethically compromised conditions has diminished integrity. Procedure and substance are both important in professional practice.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Work evaluated without opportunity to provide context, explain decisions, or respond to concerns; professional reputation potentially affected by one-sided assessment",
    "engineer_b": "Review findings tainted by procedural ethical violation; professional credibility of findings potentially undermined",
    "franchiser": "Has obtained review results but under conditions that could expose them to challenge",
    "public": "Design concerns assessed, which is positive, but without full information from the engineer who created the work"
  },
  "proeth:activatesConstraint": [
    "Review_Integrity_Constraint",
    "Fairness_To_Predecessor_Engineer_Constraint",
    "Competence_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/126#Action_Engineer_B_Reviews_Design_Information",
  "proeth:causesStateChange": "Preliminary review findings now exist; these findings were generated without Engineer A\u0027s input or knowledge; the results carry ethical baggage that may affect their reliability and fairness",
  "proeth:createsObligation": [
    "Engineer_B_Must_Share_Preliminary_Results_With_Engineer_A",
    "Franchiser_Must_Allow_Engineer_A_Opportunity_To_Respond"
  ],
  "proeth:description": "Engineer B completes his review of the franchiser\u0027s pending design information while still operating under the confidentiality instruction and before notifying Engineer A. The review results are obtained in an ethically compromised context, raising questions about the validity and fairness of the assessment.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "One week after Engineer B\u0027s retention, immediately before notification to Engineer A",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Design Review Completed Under Conflict"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#Event_Engineer_A_Informed_of_Successor_Engagement",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer B\u0027s eventual disclosure redeem his initial compliance with the confidentiality instruction, or does the one-week delay remain a separate ethical violation?",
    "How should Engineer A respond to this notification \u2014 with cooperation, protest, or both?",
    "What does Engineer B\u0027s decision to disclose despite client instructions tell us about the hierarchy of professional obligations?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences shock, betrayal toward the franchiser, and mixed feelings about Engineer B (appreciation for eventual disclosure, frustration at the delay); Engineer B may feel relief at having done the right thing but anxiety about franchiser reaction; franchiser may feel their instructions were violated",
  "proeth-scenario:ethicalImplications": "Illustrates that professional ethical obligations ultimately supersede client instructions when they conflict; demonstrates that partial remediation of ethical violations has real but limited value; raises questions about the moral significance of timing in ethical compliance",
  "proeth-scenario:learningMoment": "Belated disclosure, while better than no disclosure, does not fully remedy the harm of delayed notification; however, Engineer B\u0027s decision to override the client\u0027s instruction demonstrates the primacy of professional ethical obligations over client directives",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Now able to respond to findings; professional dignity partially restored; must process the reality that his work was reviewed without his knowledge for a week",
    "engineer_b": "Ethical standing improved by disclosure; may face pushback from franchiser for violating confidentiality instruction; demonstrates professional integrity",
    "franchiser": "Information control strategy partially defeated; must now manage Engineer A\u0027s informed response; relationship with Engineer B complicated",
    "public": "Better served by having both engineers\u0027 perspectives available for design decisions"
  },
  "proeth:activatesConstraint": [
    "Engineer_A_Right_To_Respond_To_Findings",
    "Professional_Dialogue_Between_Engineers_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/126#Action_Engineer_B_Notifies_Engineer_A_of_Relationship_and",
  "proeth:causesStateChange": "Information asymmetry partially resolved; Engineer A now aware of parallel engagement; professional dialogue between engineers becomes possible; Engineer B\u0027s ethical standing partially restored by belated disclosure",
  "proeth:createsObligation": [
    "Engineer_A_Should_Cooperate_In_Transition",
    "Engineer_B_Should_Consider_Engineer_A_Input_In_Final_Assessment",
    "Franchiser_Should_Allow_Engineer_A_To_Respond"
  ],
  "proeth:description": "One week after being retained, Engineer B notifies Engineer A of his relationship with the franchiser and shares the preliminary review results. This notification, while belated, partially remedies the ethical violation of non-disclosure and shifts the ethical landscape significantly.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "One week after Engineer B\u0027s retention",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer A Informed of Successor Engagement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#CausalChain_fe014efe",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The franchiser made a deliberate business decision to end its multi-year engineering relationship with Engineer A; before Engineer A\u0027s contract expired, the franchiser proactively retained Engineer B \u2014 together these actions created conditions in which Engineer A\u0027s long-standing professional relationship was replaced under circumstances that denied Engineer A the ability to protect their professional interests",
  "proeth:causalSequence": [
    {
      "proeth:description": "Franchiser simultaneously ends one engineering relationship and begins another before the first has formally concluded",
      "proeth:element": "Franchiser Terminates Engineer A and Retains Engineer B Early (Actions 1 \u0026 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Franchiser adds a confidentiality layer that structurally prevents Engineer A from learning of the transition",
      "proeth:element": "Franchiser Instructs Confidentiality to Engineer B (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B\u0027s uncritical acceptance and compliance enables the review to proceed under conditions disadvantageous to Engineer A",
      "proeth:element": "Engineer B Accepts Without Clarification and Conducts Review (Actions 4 \u0026 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The review is finalized before Engineer A has any knowledge of or input into the process",
      "proeth:element": "Design Review Completed Under Conflict (Event 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A learns of the completed transition and review after the fact, with no meaningful opportunity to have influenced the process or protected professional interests during it",
      "proeth:element": "Engineer A Informed of Successor Engagement (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Franchiser Terminates Engineer A (Action 1) combined with Franchiser Retains Engineer B Early (Action 2)",
  "proeth:counterfactual": "Had the franchiser either delayed Engineer B\u0027s retention until after Engineer A\u0027s contract expired, or omitted the confidentiality instruction, Engineer A would have had meaningful opportunity to be informed of and respond to the transition, preserving professional dignity and the ability to contest the review process",
  "proeth:effect": "Multi-Year Relationship Established (Event 1) undermined; Engineer A\u0027s professional interests structurally disadvantaged throughout transition",
  "proeth:necessaryFactors": [
    "Franchiser\u0027s decision to terminate Engineer A",
    "Franchiser\u0027s decision to retain Engineer B before termination was complete",
    "Franchiser\u0027s confidentiality instruction preventing Engineer B from disclosing the transition",
    "Engineer B\u0027s compliance with the confidentiality instruction during the review period"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Franchiser (primary architect of the disadvantaging conditions); Engineer B (secondary, for compliance enabling the outcome)",
  "proeth:sufficientFactors": [
    "Termination + early replacement retention + confidentiality suppression + Engineer B compliance = Engineer A\u0027s professional interests systematically disadvantaged throughout the transition without opportunity for recourse"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#CausalChain_b120110e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct result of the franchiser retaining Engineer B before Engineer A\u0027s contract expired, a period of parallel engagement overlap was created",
  "proeth:causalSequence": [
    {
      "proeth:description": "Franchiser makes deliberate decision to end the multi-year engineering relationship with Engineer A",
      "proeth:element": "Franchiser Terminates Engineer A (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A receives formal notice of non-renewal, establishing a known contract end date",
      "proeth:element": "Contract Non-Renewal Notice Received (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Before Engineer A\u0027s contract expires, franchiser proactively engages Engineer B to review pending design work",
      "proeth:element": "Franchiser Retains Engineer B Early (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Both engineers are simultaneously engaged by the same franchiser, creating a structural conflict of interest",
      "proeth:element": "Parallel Engagement Overlap Created (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B completes design review while the conflict of interest remains unresolved and Engineer A is uninformed",
      "proeth:element": "Design Review Completed Under Conflict (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Franchiser Retains Engineer B Early (Action 2)",
  "proeth:counterfactual": "Had the franchiser waited until Engineer A\u0027s contract formally expired before retaining Engineer B, no overlap period would have existed and the foundational conflict would have been avoided",
  "proeth:effect": "Parallel Engagement Overlap Created (Event 3)",
  "proeth:necessaryFactors": [
    "Franchiser\u0027s decision to retain Engineer B prior to Engineer A\u0027s contract expiration",
    "Engineer A\u0027s contract still being active at time of Engineer B\u0027s retention",
    "Engineer B\u0027s acceptance of the engagement without requiring sequential timing"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Franchiser",
  "proeth:sufficientFactors": [
    "Combination of early retention timing + active existing contract = structural conflict of interest overlap"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#CausalChain_39f5ff1e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The franchiser\u0027s explicit instruction to Engineer B not to disclose his relationship to Engineer A became a direct cause of Engineer A being kept uninformed; as a direct consequence of the franchiser\u0027s confidentiality instruction and Engineer B\u0027s initial compliance, Engineer A remained unaware",
  "proeth:causalSequence": [
    {
      "proeth:description": "At the moment of retention, franchiser explicitly instructs Engineer B not to disclose the engagement to Engineer A",
      "proeth:element": "Franchiser Instructs Confidentiality to Engineer B (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B accepts the engagement and its confidentiality condition without seeking ethical clarification or establishing disclosure boundaries",
      "proeth:element": "Engineer B Accepts Project Without Clarification (Action 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "The instruction becomes an operative constraint on Engineer B\u0027s professional conduct",
      "proeth:element": "Confidentiality Instruction Imposed on Engineer B (Event 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A remains unaware of Engineer B\u0027s engagement and the concurrent review of design work",
      "proeth:element": "Engineer A Kept Uninformed During Review (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B completes the design review while Engineer A remains uninformed, embedding the conflict into the completed work product",
      "proeth:element": "Design Review Completed Under Conflict (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Franchiser Instructs Confidentiality to Engineer B (Action 3)",
  "proeth:counterfactual": "Without the confidentiality instruction, Engineer B would have had no imposed barrier to disclosing the relationship to Engineer A; without Engineer B\u0027s compliance, the instruction alone would have been insufficient to suppress disclosure",
  "proeth:effect": "Confidentiality Instruction Imposed on Engineer B (Event 4) and Engineer A Kept Uninformed During Review (Event 5)",
  "proeth:necessaryFactors": [
    "Franchiser\u0027s explicit issuance of a confidentiality instruction at the time of retention",
    "Engineer B\u0027s initial compliance with that instruction",
    "Absence of any independent disclosure mechanism to inform Engineer A"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Franchiser (primary); Engineer B (secondary for compliance)",
  "proeth:sufficientFactors": [
    "Franchiser\u0027s confidentiality instruction + Engineer B\u0027s compliance + no alternative disclosure channel = Engineer A kept uninformed during the review period"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#CausalChain_8ab4b0e2",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B accepted the franchiser\u0027s engagement and its confidentiality condition without first exploring the ethical implications, and subsequently Engineer B completes his review of the franchiser\u0027s pending design information while still operating under the conflict of interest",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B accepts engagement and confidentiality condition without ethical due diligence",
      "proeth:element": "Engineer B Accepts Project Without Clarification (Action 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "One week after retention, Engineer B proceeds to review pending design information without having resolved the conflict",
      "proeth:element": "Engineer B Reviews Design Information (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A remains unaware throughout the review period due to Engineer B\u0027s compliance with confidentiality instruction",
      "proeth:element": "Engineer A Kept Uninformed During Review (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B completes the review while the conflict of interest remains active and undisclosed to Engineer A",
      "proeth:element": "Design Review Completed Under Conflict (Event 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Only after the review is complete does Engineer B notify Engineer A, meaning the conflicted review cannot be undone",
      "proeth:element": "Engineer A Informed of Successor Engagement (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Accepts Project Without Clarification (Action 4)",
  "proeth:counterfactual": "Had Engineer B sought ethical clarification before accepting or before beginning the review, the conflict would have been identified and either resolved or the review deferred, preventing completion under conflicted conditions",
  "proeth:effect": "Design Review Completed Under Conflict (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s acceptance of the engagement without ethical clarification",
    "Engineer B\u0027s acceptance of the confidentiality condition as a binding constraint",
    "Engineer B proceeding to review design information before resolving the conflict",
    "Absence of a self-imposed pause pending ethics review"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Unclarified acceptance + confidentiality compliance + proceeding with review = design review completed under unresolved conflict of interest"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/126#",
    "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/126#CausalChain_0c49b6c9",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following his review of the design information, and contrary to the franchiser\u0027s explicit instruction, Engineer B notifies Engineer A of his relationship with the franchiser \u2014 the sequencing of review before notification is causally significant",
  "proeth:causalSequence": [
    {
      "proeth:description": "Franchiser creates structural disincentive for timely disclosure by Engineer B",
      "proeth:element": "Franchiser Instructs Confidentiality to Engineer B (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B conducts the review without prior notification to Engineer A",
      "proeth:element": "Engineer B Reviews Design Information (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Review is finalized while Engineer A remains uninformed",
      "proeth:element": "Design Review Completed Under Conflict (Event 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B discloses the engagement to Engineer A only after the review is complete, contrary to the franchiser\u0027s instruction but too late to allow Engineer A to participate in or contest the review",
      "proeth:element": "Engineer B Notifies Engineer A of Relationship and Review (Action 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A learns of the successor engagement and completed review, with limited recourse to challenge the process or its outputs",
      "proeth:element": "Engineer A Informed of Successor Engagement (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Reviews Design Information (Action 5)",
  "proeth:counterfactual": "Had Engineer B notified Engineer A before conducting the review, Engineer A could have raised objections, sought involvement, or escalated the conflict prior to the review being completed, preserving Engineer A\u0027s professional interests",
  "proeth:effect": "Engineer A Informed of Successor Engagement (Event 7) \u2014 but only after review completion, limiting remediation",
  "proeth:necessaryFactors": [
    "Engineer B completing the design review before issuing notification",
    "Engineer B\u0027s subsequent decision to notify Engineer A contrary to the franchiser\u0027s instruction",
    "The temporal gap between review completion and notification"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer B (for sequencing review before notification); Franchiser (for creating conditions that incentivized delayed disclosure)",
  "proeth:sufficientFactors": [
    "Review completion before disclosure + delayed notification = Engineer A informed only after the conflicted work product was finalized, limiting ability to contest or participate in the review"
  ],
  "proeth:withinAgentControl": true
}