{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Action_Accept_Peer_Reviewer_Role",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the peer reviewer role entirely, citing potential conflicts of interest or discomfort with confidentiality obligations",
    "Accept the role but seek clarification from the program organizers about how conflicts between confidentiality and safety obligations would be handled before signing anything",
    "Accept the role conditionally, requesting that the confidentiality agreement include explicit carve-outs for mandatory safety disclosures"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by professional duty, collegial responsibility, and a genuine commitment to improving engineering practice through structured peer oversight. Participation may also reflect trust in the profession\u0027s self-regulatory mechanisms and a desire to contribute to quality assurance across the field.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining removes Engineer A from the ethical dilemma entirely but weakens the peer review program\u0027s pool of qualified reviewers and represents a missed opportunity for professional contribution and ethical leadership",
    "Seeking prior clarification is arguably the most prudent choice \u2014 it surfaces the latent tension before commitment and may result in stronger, more ethically sound program guidelines that protect all parties",
    "Requesting a modified agreement proactively protects Engineer A\u0027s ability to act on safety obligations and sets a constructive precedent, though program administrators may resist modifications or view the request as overreach"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that accepting a professional role is itself a morally loaded act \u2014 engineers should enter peer review programs with full awareness that their paramount obligation to public safety cannot be waived or suspended by program participation, even before any conflict arises.",
  "proeth-scenario:ethicalTension": "Voluntary professional service vs. the foreseeable risk of being placed in situations where confidentiality obligations may conflict with public safety duties. Engineer A may not yet anticipate that accepting this role could force a future confrontation between two core professional values.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s professional credibility and integrity are staked on fulfilling the role conscientiously. If Engineer A is unprepared for ethical complexity inherent in the role, the consequences could affect public safety, professional reputation, and the legitimacy of peer review programs broadly.",
  "proeth:description": "Engineer A voluntarily agrees to serve as a peer reviewer within an organized peer review program, taking on the associated professional responsibilities and obligations of that role.",
  "proeth:foreseenUnintendedEffects": [
    "Exposure to confidential firm information that may create future ethical conflicts",
    "Assumption of dual obligations \u2014 to the peer review program and to public safety \u2014 that could come into tension"
  ],
  "proeth:fulfillsObligation": [
    "Support for professional development and improvement of engineering practice",
    "Participation in organized professional self-regulation",
    "Collegial responsibility to assist fellow engineers in improving practice"
  ],
  "proeth:guidedByPrinciple": [
    "Enhancement of professional practice",
    "Collegial cooperation",
    "Professional self-regulation",
    "Voluntary service to the profession"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer / Peer Reviewer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Contribute to the improvement of professional engineering practice through collegial evaluation and constructive feedback",
  "proeth:requiresCapability": [
    "Engineering judgment and technical expertise",
    "Ability to evaluate professional practice and documentation",
    "Understanding of peer review program procedures and ethics"
  ],
  "proeth:temporalMarker": "Pre-review; prior to any site visits or firm evaluations",
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Peer Reviewer Role"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Action_Sign_Confidentiality_Agreement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Sign the agreement as written, assuming it is standard and absolute in scope",
    "Refuse to sign until legal counsel or the engineering society clarifies the interaction between the agreement and professional safety obligations",
    "Sign the agreement but document in writing \u2014 to program administrators \u2014 Engineer A\u0027s understanding that safety-related disclosures required by professional codes of ethics are not covered by the confidentiality terms"
  ],
  "proeth-scenario:characterMotivation": "Engineer A signs the confidentiality agreement in good faith as a procedural precondition of participation, likely viewing it as a reasonable professional norm that protects the reviewed firm from competitive harm and encourages candid disclosure during the review process.",
  "proeth-scenario:consequencesIfAlternative": [
    "Signing without reflection, as written, creates a false sense that confidentiality is unconditional, potentially paralyzing Engineer A later when safety violations are discovered and disclosure feels legally prohibited",
    "Refusing to sign delays or prevents participation but protects Engineer A from ambiguity and may prompt the program to develop clearer, more ethically sound agreement language",
    "Documenting the carve-out interpretation in writing is a proactive and professionally sound approach that creates a record, clarifies intent, and reduces legal risk while preserving the ability to act on safety obligations \u2014 arguably the most defensible course"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that signing a legal or professional agreement does not \u2014 and cannot \u2014 override fundamental ethical obligations embedded in engineering codes of conduct. Students should learn that confidentiality agreements in professional contexts are implicitly bounded by public safety imperatives, and that engineers must understand this hierarchy before signing.",
  "proeth-scenario:ethicalTension": "Respect for contractual and professional commitments vs. the pre-existing, non-waivable obligation under engineering codes of ethics to protect public health and safety. The agreement creates a legally and professionally binding constraint that will later collide directly with Engineer A\u0027s paramount duty.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The signed agreement creates real legal exposure for Engineer A if confidentiality is later breached, even for legitimate safety reasons. It also establishes the core tension that drives the remainder of the narrative. If Engineer A misunderstands the agreement as absolute, public safety may be compromised.",
  "proeth:description": "Engineer A signs a formal confidentiality agreement committing to non-disclosure of confidential information about firms encountered during the peer review process, as a precondition of participation.",
  "proeth:foreseenUnintendedEffects": [
    "Creation of a binding contractual obligation that could conflict with future public safety reporting duties",
    "Potential constraint on Engineer A\u0027s ability to act freely if safety violations are later discovered"
  ],
  "proeth:fulfillsObligation": [
    "Honoring program requirements for participation",
    "Supporting the confidentiality foundation that makes peer review programs effective",
    "Respecting the trust relationship between peer reviewer and reviewed firm",
    "NSPE Code Section III.4 \u2014 commitment to non-disclosure of confidential business and technical information"
  ],
  "proeth:guidedByPrinciple": [
    "Confidentiality as a foundation of trust",
    "Encouraging maximum professional disclosure",
    "Integrity in honoring commitments",
    "Support for effective peer review mechanisms"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer / Peer Reviewer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Confidentiality commitment vs. potential future public safety obligation",
    "proeth:resolutionReasoning": "At the time of signing, the conflict was only potential and not yet active; Engineer A proceeded with signing as a necessary condition of participation, with the safety obligation remaining latent unless triggered by discovery of violations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Satisfy the program\u0027s precondition for participation, build trust with reviewed firms, and encourage maximum disclosure during reviews",
  "proeth:requiresCapability": [
    "Understanding of professional ethics obligations",
    "Ability to assess implications of contractual commitments",
    "Knowledge of NSPE Code provisions"
  ],
  "proeth:temporalMarker": "Pre-review; at the time of selection as peer reviewer, before conducting any reviews",
  "proeth:withinCompetence": true,
  "rdfs:label": "Sign Confidentiality Agreement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Action_Conduct_Technical_Documentation_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct only a cursory review, focusing on easily verifiable surface-level compliance to minimize the risk of discovering uncomfortable findings",
    "Conduct the review thoroughly but selectively document findings, omitting potential violations from the formal record to avoid conflict",
    "Conduct the review thoroughly and document all findings completely and accurately, including potential violations"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is fulfilling the core technical function of the peer review role \u2014 applying professional expertise to evaluate whether Engineer B\u0027s firm\u0027s design work meets applicable standards, codes, and quality benchmarks. The motivation is a combination of professional duty, intellectual rigor, and the constructive intent to help improve engineering practice.",
  "proeth-scenario:consequencesIfAlternative": [
    "A cursory review fails the profession, the public, and the purpose of the peer review program \u2014 safety violations go undetected and Engineer A has not fulfilled the role accepted in Action 1",
    "Selective documentation represents a form of professional dishonesty and could expose Engineer A to disciplinary action; it also leaves the safety risk unaddressed in the official record while Engineer A still possesses knowledge of the violations",
    "Full, accurate documentation \u2014 the appropriate course \u2014 creates the evidentiary basis for subsequent actions and ensures Engineer A can defend the findings professionally and legally if escalation becomes necessary"
  ],
  "proeth-scenario:decisionSignificance": "Highlights that competent, diligent technical review is itself an ethical act \u2014 cutting corners or conducting a superficial review to avoid uncomfortable findings would represent a failure of professional duty. Engineers must be prepared to follow the evidence wherever it leads, even when findings are inconvenient.",
  "proeth-scenario:ethicalTension": "The obligation to conduct a thorough, honest, and complete review vs. the awareness that a thorough review may uncover information that triggers a conflict between confidentiality and safety obligations. There is also a tension between collegial generosity toward a peer and the objectivity required of a credible reviewer.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The quality and thoroughness of this review directly determines whether safety violations are detected at all. An incomplete review could leave dangerous conditions unaddressed. Conversely, a rigorous review that surfaces violations sets in motion the ethical dilemma that defines the rest of the case.",
  "proeth:description": "Engineer A actively reviews the technical documentation associated with Engineer B\u0027s firm\u0027s recent design projects as part of the formal peer review visit, exercising professional judgment to evaluate compliance and quality of work.",
  "proeth:foreseenUnintendedEffects": [
    "Potential discovery of problematic work that could create ethical obligations conflicting with the confidentiality agreement",
    "Possibility of identifying issues that could strain the collegial peer review relationship"
  ],
  "proeth:fulfillsObligation": [
    "Fulfillment of peer reviewer role and program obligations",
    "Diligent and thorough professional evaluation",
    "Service to the profession through quality assurance",
    "Competent exercise of engineering judgment"
  ],
  "proeth:guidedByPrinciple": [
    "Thoroughness and diligence in professional review",
    "Collegial support for professional improvement",
    "Honest and objective evaluation",
    "Competent engineering practice"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer / Peer Reviewer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Perform a thorough and constructive evaluation of Engineer B\u0027s professional practice to support improvement and quality assurance",
  "proeth:requiresCapability": [
    "Technical expertise to evaluate design documentation",
    "Knowledge of state and local safety codes",
    "Ability to identify code violations and safety risks",
    "Professional judgment in assessing quality of engineering work"
  ],
  "proeth:temporalMarker": "During the peer review visit to Engineer B\u0027s firm",
  "proeth:withinCompetence": true,
  "rdfs:label": "Conduct Technical Documentation Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Action_Assess_Imminence_of_Public_Risk",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Treat all discovered violations as automatically imminent and immediately contact authorities without attempting internal resolution",
    "Dismiss the violations as minor or ambiguous and take no further action, deferring entirely to Engineer B\u0027s professional judgment",
    "Consult with a trusted senior colleague, ethics board, or legal counsel before making the imminence determination, to validate the assessment"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is exercising the professional judgment that is central to engineering ethics \u2014 recognizing that not all safety concerns are equivalent in urgency, and that the appropriate response pathway depends on the severity and immediacy of the risk. Engineer A is attempting to act proportionately and deliberately rather than reactively.",
  "proeth-scenario:consequencesIfAlternative": [
    "Bypassing Engineer B entirely may be warranted in genuinely imminent cases but is disproportionate for serious-but-non-imminent violations \u2014 it destroys the collaborative value of peer review and may expose Engineer A to criticism for failing to follow prescribed resolution steps",
    "Dismissing real violations is a serious ethical failure that abdicates Engineer A\u0027s professional responsibility and could result in public harm, disciplinary action, and legal liability",
    "Consulting a third party before acting is often prudent \u2014 it validates the risk assessment, provides a record of due diligence, and may offer guidance on the appropriate escalation pathway, though it introduces a time delay that must be weighed against urgency"
  ],
  "proeth-scenario:decisionSignificance": "One of the most critical judgment calls in the scenario \u2014 teaches students that ethical decision-making in engineering is not simply rule-following but requires calibrated professional judgment about risk severity, urgency, and proportionality of response. The distinction between imminent and serious-but-non-imminent risk determines which resolution pathway is appropriate.",
  "proeth-scenario:ethicalTension": "The desire to follow due process and give Engineer B an opportunity to respond vs. the obligation to act urgently if public safety is at imminent risk. Misjudging imminence in either direction carries serious consequences: overreacting may damage professional relationships and the peer review program\u0027s credibility; underreacting may allow harm to occur.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "If Engineer A misjudges the risk as non-imminent when it is actually imminent, people could be harmed during the time spent in deliberative resolution. If Engineer A overestimates imminence, the collegial resolution pathway is bypassed unnecessarily, potentially damaging professional relationships and undermining the peer review program\u0027s cooperative model.",
  "proeth:description": "Following discovery of potential safety code violations, Engineer A exercises professional judgment to determine whether the risk constitutes an imminent threat to public health and safety requiring urgent action, or a serious but non-imminent concern permitting a deliberative resolution process.",
  "proeth:foreseenUnintendedEffects": [
    "Underestimating imminence could delay necessary protective action and result in harm",
    "Overestimating imminence could bypass the preferred deliberative process and damage the peer review relationship and program integrity prematurely"
  ],
  "proeth:fulfillsObligation": [
    "Exercise of appropriate engineering judgment and discretion",
    "Paramount duty to protect public health and safety (NSPE Code Section II.1.e)",
    "Responsible professional decision-making under conditions of uncertainty"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as paramount professional obligation",
    "Appropriate judgment and discretion in complex ethical situations",
    "Proportionality of response to severity of risk",
    "Responsible stewardship of professional authority"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer / Peer Reviewer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Urgency of imminent public safety risk vs. deliberative process preserving confidentiality and peer review program integrity",
    "proeth:resolutionReasoning": "The NSPE Code and BER guidance establish that if imminent risk is determined (loss of life, serious injury), Engineer A must bypass the deliberative process and act immediately; if risk is serious but not imminent, the preferred path is to first engage Engineer B, preserving confidentiality to the extent possible"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Determine the appropriate urgency and sequence of response to protect public health and safety while exercising appropriate judgment and discretion",
  "proeth:requiresCapability": [
    "Technical engineering judgment to assess severity and imminence of safety risk",
    "Knowledge of applicable safety codes and standards",
    "Ability to weigh competing ethical obligations under uncertainty",
    "Experience with risk assessment in engineering contexts"
  ],
  "proeth:temporalMarker": "Immediately post-discovery of potential violations, before taking any further action",
  "proeth:withinCompetence": true,
  "rdfs:label": "Assess Imminence of Public Risk"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Action_Notify_Engineer_B_of_Violations",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Skip direct notification of Engineer B and immediately report the violations to regulatory authorities or licensing boards",
    "Notify Engineer B but set no clear timeline or expectation for corrective action, allowing the situation to drift without resolution",
    "Notify Engineer B in writing rather than verbally, creating a formal record of the notification and the specific violations identified"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by both professional protocol and collegial respect \u2014 giving Engineer B the opportunity to acknowledge and correct the violations before external authorities are involved. This reflects a commitment to due process, a belief in professional self-correction, and a desire to resolve the matter at the lowest necessary level of escalation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Bypassing Engineer B may be appropriate if violations are imminent, but for non-imminent cases it skips a professionally required step, damages collegial trust, and may undermine the peer review program\u0027s credibility as a constructive mechanism",
    "Notifying without establishing a clear timeline is ineffective \u2014 it gives the appearance of action while allowing Engineer B to delay indefinitely, potentially prolonging public risk and leaving Engineer A in an ambiguous position regarding when escalation is warranted",
    "Written notification is generally superior to verbal notification \u2014 it creates an unambiguous record of what was communicated, when, and what response (if any) was received, which is essential if escalation to authorities later becomes necessary"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the prescribed ethical resolution hierarchy: internal notification before external escalation, when risk permits. Students learn that professional ethics often requires giving peers the opportunity to self-correct, while also understanding that this step is time-bounded and conditional on Engineer B\u0027s response \u2014 it is not an indefinite deferral of responsibility.",
  "proeth-scenario:ethicalTension": "Loyalty to professional collegiality and the cooperative spirit of peer review vs. the risk that notifying Engineer B first \u2014 rather than authorities \u2014 could allow Engineer B to conceal violations, delay corrective action, or retaliate. There is also tension between the confidentiality agreement (which Engineer B may invoke) and Engineer A\u0027s obligation to raise safety concerns.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If Engineer B responds constructively and takes corrective action, the matter is resolved without breaching confidentiality or involving authorities \u2014 the ideal outcome. If Engineer B is defensive, dismissive, or retaliatory, Engineer A must be prepared to escalate. Delay in escalation, if Engineer B is unresponsive, could allow unsafe conditions to persist.",
  "proeth:description": "Engineer A expeditiously initiates a direct discussion with Engineer B about the discovered potential safety code violations, seeking clarification and early resolution before considering any escalation to external authorities.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer B may fail to take corrective action, requiring Engineer A to escalate to authorities and breach confidentiality",
    "Discussion may reveal that the violations are less serious than initially assessed, avoiding unnecessary escalation",
    "The collegial peer review relationship may be strained by the confrontation",
    "Engineer B may take corrective action, resolving the issue without breach of confidentiality"
  ],
  "proeth:fulfillsObligation": [
    "Paramount duty to protect public health and safety (NSPE Code Section II.1.e)",
    "Collegial professional responsibility to engage Engineer B directly before external escalation",
    "Proportionate response that preserves confidentiality to the extent possible",
    "Honest and direct communication consistent with professional integrity"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as paramount obligation",
    "Collegial and direct engagement as preferred first step",
    "Proportionality \u2014 least invasive action taken first",
    "Professional integrity and honest communication",
    "Good faith effort to resolve issues internally before external escalation"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer / Peer Reviewer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Confidentiality and peer review program integrity vs. public safety obligation",
    "proeth:resolutionReasoning": "Engineer A resolves the conflict by taking the least invasive action first \u2014 direct notification to Engineer B \u2014 which partially honors confidentiality (no external disclosure yet) while fulfilling the safety obligation; this approach preserves the possibility of internal resolution and defers the more serious confidentiality breach of external reporting unless Engineer B fails to act"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Seek clarification of the potential violations, give Engineer B the opportunity to explain or correct the issues, and achieve early resolution while preserving confidentiality and the peer review relationship to the greatest extent possible",
  "proeth:requiresCapability": [
    "Professional communication and interpersonal skills",
    "Technical expertise to articulate specific concerns about code violations",
    "Ethical reasoning to navigate competing obligations",
    "Judgment to distinguish between clarification needs and confirmed violations"
  ],
  "proeth:temporalMarker": "Post-discovery; first action in the prescribed resolution sequence, assuming risk is serious but not immediately imminent",
  "proeth:violatesObligation": [
    "Partial tension with confidentiality agreement \u2014 though disclosure is to Engineer B (the reviewed party) rather than external authorities, the confrontation signals potential future breach"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Notify Engineer B of Violations"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Action_Escalate_to_Proper_Authorities",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decide that the confidentiality agreement is legally binding and take no further action after Engineer B fails to respond, rationalizing that the obligation has been discharged by notifying Engineer B",
    "Report the violations anonymously to authorities rather than as a named complainant, attempting to trigger investigation while minimizing personal exposure",
    "Seek guidance from the engineering society\u0027s ethics board or legal counsel before making the final decision to escalate, to confirm that escalation is both ethically required and legally defensible given the confidentiality agreement"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by the paramount professional obligation to protect public health and safety \u2014 an obligation that, under engineering codes of ethics, supersedes contractual confidentiality commitments when the two are in direct conflict. Having exhausted the internal resolution pathway, Engineer A recognizes that inaction would constitute a failure of professional duty.",
  "proeth-scenario:consequencesIfAlternative": [
    "Treating the confidentiality agreement as absolute and taking no further action is an ethical failure \u2014 it prioritizes a contractual obligation over the paramount duty to protect public safety, potentially resulting in public harm and exposing Engineer A to disciplinary action for knowingly allowing unsafe conditions to persist",
    "Anonymous reporting may trigger an investigation and protect the public, but it may also be less credible or actionable than a named report; it also fails to model the professional courage that engineering ethics requires, and Engineer A may still be identifiable given the context of the peer review",
    "Consulting the ethics board or legal counsel before escalating is a prudent intermediate step that validates the decision, provides legal protection, and ensures Engineer A acts with full awareness of the consequences \u2014 this is often the most defensible and professionally sound approach before taking an action with significant legal and professional implications"
  ],
  "proeth-scenario:decisionSignificance": "The definitive teaching moment of the case: students learn that engineering codes of ethics establish an explicit priority hierarchy in which public safety is paramount and cannot be contractually waived. Confidentiality is a real and important professional value, but it is not absolute \u2014 it yields when public welfare is at stake. This action also models the importance of exhausting internal remedies before escalating, demonstrating that escalation is a last resort, not a first response.",
  "proeth-scenario:ethicalTension": "The binding confidentiality agreement and the professional norm of honoring commitments vs. the non-waivable ethical and legal obligation to prevent harm to the public. This is the central ethical conflict of the entire scenario \u2014 a direct collision between two legitimate professional values, resolved by the explicit hierarchy established in engineering codes of ethics that places public safety above all other obligations.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Escalating to authorities may expose Engineer A to legal action from Engineer B for breach of the confidentiality agreement, professional retaliation, or damage to collegial relationships. Failing to escalate, however, risks public harm, Engineer A\u0027s own professional liability for knowing about safety violations and failing to act, and potential disciplinary action by the engineering licensing board.",
  "proeth:description": "If Engineer B fails to take appropriate corrective action following notification, Engineer A decides to cooperate with proper authorities by furnishing information and assistance as required, overriding the confidentiality agreement in fulfillment of the paramount obligation to protect public health and safety.",
  "proeth:foreseenUnintendedEffects": [
    "Breach of the signed confidentiality agreement and potential legal or professional consequences for Engineer A",
    "Erosion of trust in peer review programs generally, potentially deterring future participation and candid disclosure",
    "Damage to the collegial relationship between Engineer A and Engineer B",
    "Possible professional or legal consequences for Engineer B",
    "Potential chilling effect on peer review program effectiveness and participation"
  ],
  "proeth:fulfillsObligation": [
    "Paramount duty to protect public health and safety (NSPE Code Section II.1.e)",
    "Obligation to cooperate with proper authorities regarding known or alleged code violations",
    "Ultimate professional responsibility as a licensed engineer to the public",
    "Fulfillment of the escalation pathway prescribed by BER guidance"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety as the paramount and overriding professional obligation",
    "Hierarchy of professional obligations \u2014 safety above confidentiality",
    "Obligation to cooperate with authorities when violations endanger the public",
    "Professional integrity in acting on known safety risks despite personal cost",
    "Exhaustion of less invasive remedies before escalation"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer / Peer Reviewer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Confidentiality obligation and peer review program integrity vs. paramount public safety obligation",
    "proeth:resolutionReasoning": "The BER and NSPE Code establish a clear hierarchy in which the paramount obligation to protect public health and safety overrides confidentiality when Engineer B has failed to take corrective action; the confidentiality breach is justified as the only remaining means of fulfilling the safety obligation, and is taken only after the less invasive remedy of direct notification to Engineer B has been exhausted without result"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Ensure that the public health and safety violations are addressed by competent authorities when Engineer B has failed to self-correct, thereby fulfilling Engineer A\u0027s paramount professional obligation",
  "proeth:requiresCapability": [
    "Knowledge of proper reporting channels and authorities",
    "Ability to document and communicate technical violations clearly to non-engineering authorities",
    "Ethical resolve to act against personal and contractual interests in service of public safety",
    "Professional judgment to confirm that escalation is warranted and that Engineer B has genuinely failed to act"
  ],
  "proeth:temporalMarker": "Post-discussion with Engineer B; conditional action triggered only if Engineer B fails to take corrective action",
  "proeth:violatesObligation": [
    "Confidentiality agreement \u2014 formal commitment to non-disclosure is breached",
    "NSPE Code Section III.4 \u2014 obligation not to disclose confidential business affairs or technical processes without consent"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Escalate to Proper Authorities"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Peer_Review_Program_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why do professional engineering bodies establish peer review programs, and what values do they reflect?",
    "Does participation in a peer review program carry implicit ethical obligations beyond those spelled out in a confidentiality agreement?",
    "How should peer review program designers anticipate conflicts between confidentiality and public safety?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral for most parties at this stage; Engineer A may feel professional recognition upon selection; Engineer B\u0027s firm may feel mild apprehension about external scrutiny",
  "proeth-scenario:ethicalImplications": "Reveals the foundational tension embedded in the program design itself: confidentiality is needed for candid review, yet public safety may require disclosure. The program\u0027s existence creates the very dilemma Engineer A will face.",
  "proeth-scenario:learningMoment": "Illustrates how professional institutions create frameworks that simultaneously protect the public and bind individual engineers to obligations that may later conflict with one another.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Granted authority and responsibility as a peer reviewer; enters a role with ethical obligations",
    "engineer_b": "Firm becomes subject to external evaluation; professional work exposed to scrutiny",
    "professional_body": "Fulfills its mandate to uphold engineering standards",
    "public": "Indirectly protected by the existence of a quality assurance mechanism"
  },
  "proeth:activatesConstraint": [
    "Peer_Review_Program_Rules_Constraint",
    "Professional_Participation_Norms_Constraint"
  ],
  "proeth:causesStateChange": "A formal peer review ecosystem is activated; Engineer A enters a role with defined duties and constraints",
  "proeth:createsObligation": [
    "Obligation_To_Follow_Program_Procedures",
    "Obligation_To_Sign_Confidentiality_Agreement"
  ],
  "proeth:description": "An organized peer review program is instituted, creating a formal structure for engineers to evaluate each other\u0027s work. This exogenous institutional arrangement sets the conditions under which Engineer A is selected and bound by its rules.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Before Engineer A\u0027s selection; program pre-exists the case narrative",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Peer Review Program Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Confidentiality_Agreement_Binding",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should confidentiality agreements in peer review programs include explicit carve-outs for public safety disclosures?",
    "Does signing a confidentiality agreement transfer moral responsibility for later harm if disclosure is withheld?",
    "At what point does a contractual obligation become subordinate to a professional ethical duty?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Likely routine and unremarkable for Engineer A at the time of signing; in retrospect, this moment becomes charged with significance once violations are discovered",
  "proeth-scenario:ethicalImplications": "Highlights the tension between contractual fidelity and professional duty to the public. The routine act of signing creates a constraint that will directly conflict with the paramount engineering obligation to protect public safety.",
  "proeth-scenario:learningMoment": "Demonstrates how routine procedural acts (signing agreements) can create significant ethical constraints that only become visible when later circumstances change. Engineers must understand the full implications of agreements before signing.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Constrained in future disclosure; the signed agreement will later create moral and professional tension",
    "engineer_b": "Gains a reasonable expectation of privacy regarding review findings",
    "professional_body": "Program integrity protected by confidentiality norms",
    "public": "Unaware; confidentiality constraint may later impede timely disclosure of safety risks"
  },
  "proeth:activatesConstraint": [
    "Confidentiality_Agreement_Constraint",
    "Non_Disclosure_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/181#Action_Sign_Confidentiality_Agreement",
  "proeth:causesStateChange": "Engineer A transitions from a free agent to a contractually constrained reviewer; all subsequent discoveries are subject to confidentiality obligations",
  "proeth:createsObligation": [
    "Obligation_To_Maintain_Confidentiality_Of_Review_Findings",
    "Obligation_To_Use_Information_Only_For_Review_Purpose"
  ],
  "proeth:description": "Upon signing, the confidentiality agreement becomes legally and professionally binding on Engineer A, creating a formal constraint on disclosure of information obtained during the review. This is an automatic legal outcome triggered by the act of signing.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Immediately upon Engineer A signing the confidentiality agreement, prior to any site visit",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Confidentiality Agreement Binding"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Safety_Violations_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the discovery of a safety violation automatically override a confidentiality agreement, or must Engineer A weigh the severity of the risk first?",
    "What is Engineer A\u0027s ethical responsibility if the violations are serious but not immediately life-threatening?",
    "How does the NSPE Code of Ethics resolve conflicts between contractual obligations and public safety duties?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Alarm and moral distress for Engineer A, who is caught between contractual loyalty and professional duty; potential fear or defensiveness for Engineer B if informed; concern and vulnerability for members of the public exposed to unsafe designs; tension for the professional body whose program is now implicated",
  "proeth-scenario:ethicalImplications": "Reveals the foundational hierarchy of engineering ethics: public safety is paramount and supersedes contractual arrangements. Also surfaces questions about the adequacy of institutional design when confidentiality norms and safety obligations are not explicitly reconciled in program rules.",
  "proeth-scenario:learningMoment": "This is the central ethical turning point of the case. Students should understand that the discovery of a public safety hazard is not merely a fact-finding outcome but an event that instantiates a hierarchy of professional obligations, with public safety superseding confidentiality.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Faces immediate ethical crisis; professional reputation and legal standing hinge on how the discovery is handled; psychological burden of holding knowledge of public risk",
    "engineer_b": "Professional conduct called into question; faces potential disciplinary action, legal liability, and reputational damage",
    "professional_body": "Program\u0027s credibility depends on how this situation is resolved; may need to revisit confidentiality agreement design",
    "public": "Lives and safety are at risk from designs that may not meet code requirements; most severely affected stakeholder",
    "state_and_local_authorities": "Unaware of violations; their regulatory function is implicated"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Mandatory_Reporting_Obligation_Constraint",
    "NSPE_Code_Section_III_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/181#Action_Conduct_Technical_Documentation_Review",
  "proeth:causesStateChange": "Case transforms from a routine peer review into an active public safety crisis; Engineer A now bears dual and conflicting obligations; the ethical dilemma is fully instantiated",
  "proeth:createsObligation": [
    "Obligation_To_Assess_Imminence_Of_Risk",
    "Obligation_To_Notify_Engineer_B",
    "Obligation_To_Escalate_If_Engineer_B_Fails_To_Act",
    "Obligation_To_Protect_Public_Health_And_Safety"
  ],
  "proeth:description": "During examination of Engineer B\u0027s technical documentation, Engineer A discovers evidence of potential violations of state and local safety codes that could endanger public health and safety. This is a critical outcome event that fundamentally changes the ethical landscape of the narrative.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During the technical documentation review visit to Engineer B\u0027s firm",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Safety Violations Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Ethical_Dilemma_Instantiated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is this a true dilemma (no right answer) or a conflict with a clear resolution under professional ethics codes?",
    "What resources or colleagues could Engineer A consult without violating confidentiality?",
    "How does the existence of a prescribed resolution sequence (notify Engineer B first, then escalate) affect the moral weight of Engineer A\u0027s choices?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Deep moral distress and anxiety for Engineer A; sense of being trapped between professional loyalty and civic duty; potential isolation as Engineer A cannot easily seek counsel due to confidentiality constraints",
  "proeth-scenario:ethicalImplications": "Surfaces the meta-ethical question of how to prioritize obligations when they conflict. Illustrates that engineering ethics is not merely rule-following but requires judgment about the relative weight of duties, with public safety serving as the tiebreaker in most professional codes.",
  "proeth-scenario:learningMoment": "Demonstrates that ethical dilemmas in engineering are not abstract philosophical puzzles but concrete situations with real stakes. Students should learn to recognize when competing obligations create a genuine conflict and understand that professional codes provide guidance for resolution.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Bears the full psychological and professional weight of the dilemma; must act under uncertainty with significant consequences either way",
    "engineer_b": "Unaware of the dilemma; outcome will significantly affect their professional standing",
    "professional_body": "Program design is implicitly on trial; resolution will set precedent",
    "public": "Safety depends on how Engineer A resolves this dilemma; passive but most vulnerable stakeholder"
  },
  "proeth:activatesConstraint": [
    "Ethical_Conflict_Resolution_Procedure_Constraint",
    "Professional_Judgment_Required_Constraint"
  ],
  "proeth:causesStateChange": "Engineer A enters a state of active ethical conflict requiring deliberate resolution; the case moves from discovery to decision-making phase",
  "proeth:createsObligation": [
    "Obligation_To_Assess_Relative_Weight_Of_Competing_Duties",
    "Obligation_To_Follow_Prescribed_Resolution_Sequence"
  ],
  "proeth:description": "The discovery of safety violations creates an active, irresolvable tension between Engineer A\u0027s contractual confidentiality obligation and the professional duty to protect public health and safety. This is an automatic trigger event arising from the co-existence of two conflicting binding obligations.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Immediately following the discovery of safety violations during the review",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Ethical Dilemma Instantiated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Engineer_B_Notified_of_Violations",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why is it ethically important to notify Engineer B before going directly to authorities, assuming the risk is not immediately life-threatening?",
    "What constitutes a reasonable timeframe for Engineer B to take corrective action before escalation is warranted?",
    "How does Engineer B\u0027s response (or lack thereof) affect the distribution of moral responsibility?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Shock, defensiveness, or alarm for Engineer B upon learning of violations; relief for Engineer A that the first step has been taken; continued anxiety as outcome depends on Engineer B\u0027s response; public remains unaware and vulnerable",
  "proeth-scenario:ethicalImplications": "Demonstrates the principle of proportionality in ethical response: escalating directly to authorities without first giving Engineer B the chance to correct violations may be disproportionate. Also raises questions about collegial responsibility and the duty to self-correct when violations are identified.",
  "proeth-scenario:learningMoment": "Illustrates the importance of the prescribed sequential resolution: giving the responsible engineer the first opportunity to correct violations respects professional collegiality while still prioritizing safety. Students should understand why this sequence exists and what it accomplishes.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Has fulfilled the first obligation in the resolution sequence; professional exposure reduced but not eliminated; must now wait and monitor",
    "engineer_b": "Faces a critical choice point; professional and legal consequences now depend on their response; reputation and license at risk",
    "professional_body": "Resolution sequence is being followed correctly, validating program design",
    "public": "Marginally safer in that the responsible party is now aware; actual safety depends on Engineer B\u0027s corrective action"
  },
  "proeth:activatesConstraint": [
    "Engineer_B_Corrective_Action_Obligation_Constraint",
    "Reasonable_Timeframe_For_Remediation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/181#Action_Notify_Engineer_B_of_Violations",
  "proeth:causesStateChange": "Responsibility for remediation is formally transferred to Engineer B; Engineer A\u0027s obligation shifts to monitoring and conditional escalation; the confidentiality boundary is partially breached within the professional relationship",
  "proeth:createsObligation": [
    "Engineer_B_Obligation_To_Take_Corrective_Action",
    "Engineer_A_Obligation_To_Monitor_Engineer_B_Response",
    "Engineer_A_Conditional_Obligation_To_Escalate_If_No_Action"
  ],
  "proeth:description": "As an outcome of Engineer A\u0027s notification action, Engineer B becomes aware of the identified safety code violations in their firm\u0027s design work. This event shifts moral and corrective responsibility to Engineer B and starts a clock on remediation.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following Engineer A\u0027s decision to notify Engineer B, as the first step in the prescribed resolution sequence",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer B Notified of Violations"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Corrective_Action_Deadline_Triggered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How long is too long to wait for Engineer B to take corrective action when public safety is at stake?",
    "Does the existence of a remediation window reduce or increase Engineer A\u0027s moral responsibility for ongoing public risk?",
    "What evidence of corrective action should Engineer A require before deciding not to escalate?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Tense waiting period for Engineer A; potential anxiety or urgency for Engineer B to respond; public remains unaware and at risk during this window",
  "proeth-scenario:ethicalImplications": "Reveals the tension between procedural fairness (giving Engineer B a chance to correct) and urgency (public safety may not wait). Raises questions about how professional codes should specify timeframes for remediation in safety-critical contexts.",
  "proeth-scenario:learningMoment": "Teaches students about the role of procedural sequence in ethical resolution and the concept of conditional obligations that become unconditional upon failure of a precondition. Also highlights the tension between giving professionals a chance to self-correct and the urgency of public safety.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "authorities": "Not yet involved; will be activated if Engineer B fails to act",
    "engineer_a": "Enters a monitoring role with a conditional duty to escalate; professional standing depends on appropriate response to Engineer B\u0027s actions or inactions",
    "engineer_b": "Has a defined window to demonstrate professional responsibility; inaction will trigger escalation with more severe consequences",
    "public": "Continues to be at risk during the remediation window; safety outcome deferred"
  },
  "proeth:activatesConstraint": [
    "Escalation_Trigger_Condition_Constraint",
    "Engineer_A_Monitoring_Duty_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/181#Action_Notify_Engineer_B_of_Violations",
  "proeth:causesStateChange": "A conditional escalation obligation is now armed and will become unconditional if Engineer B fails to take corrective action; the situation enters a waiting and monitoring phase",
  "proeth:createsObligation": [
    "Obligation_To_Monitor_Engineer_B_Response",
    "Conditional_Obligation_To_Escalate_Upon_Inaction"
  ],
  "proeth:description": "Upon notification of violations, an implicit or explicit deadline for Engineer B to take corrective action is automatically activated. If Engineer B fails to act within a reasonable timeframe, Engineer A\u0027s conditional obligation to escalate to proper authorities becomes unconditional.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Immediately upon Engineer B being notified; deadline period begins",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Corrective Action Deadline Triggered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#Event_Confidentiality_Obligation_Overridden",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does breaching a confidentiality agreement to protect public safety expose Engineer A to legal liability, and how do professional ethics codes address this?",
    "What would have happened\u2014ethically and legally\u2014if Engineer A had chosen to honor the confidentiality agreement and remained silent?",
    "How should the outcome of this case inform the design of future peer review confidentiality agreements?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Relief and moral clarity for Engineer A after a period of conflict and uncertainty; potential anger, shame, or fear for Engineer B as external authorities become involved; vindication for the public safety imperative; gravity of the situation fully realized by all parties",
  "proeth-scenario:ethicalImplications": "Definitively resolves the central ethical tension of the case by affirming the hierarchy of professional obligations. Reveals that confidentiality, while important, is an instrumental value (serving trust and candor) rather than a terminal value, and must yield to the terminal value of public safety. Also raises questions about institutional design: could better-crafted agreements have prevented the dilemma entirely?",
  "proeth-scenario:learningMoment": "The most important teaching moment in the case: public safety is the paramount obligation in engineering ethics and supersedes contractual confidentiality arrangements. Students should understand that this is not a close call under professional ethics codes, and that following the prescribed sequence protects Engineer A professionally while fulfilling the duty to the public.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "authorities": "Now empowered and obligated to investigate and enforce safety codes",
    "engineer_a": "Has fulfilled professional obligations; may face professional or legal consequences for breaching confidentiality but is protected by ethics codes; professional integrity preserved",
    "engineer_b": "Faces formal regulatory investigation; potential license suspension, fines, or legal liability; professional reputation severely damaged",
    "professional_body": "Resolution validates the prescribed sequence; may prompt review of confidentiality agreement language to explicitly address safety override provisions",
    "public": "Safety interests are now actively protected by regulatory authorities; risk of harm reduced through official intervention"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Mandatory_Authority_Disclosure_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/181#Action_Escalate_to_Proper_Authorities",
  "proeth:causesStateChange": "Confidentiality constraint is formally subordinated to public safety obligation; authorities are now informed and empowered to act; Engineer B faces external regulatory scrutiny; the case enters its resolution phase",
  "proeth:createsObligation": [
    "Obligation_To_Fully_Cooperate_With_Authorities",
    "Obligation_To_Provide_Complete_Accurate_Information_To_Authorities"
  ],
  "proeth:description": "When Engineer A escalates to proper authorities, the confidentiality agreement is effectively overridden by the paramount professional obligation to protect public health and safety. This is an automatic legal and ethical outcome: disclosure to authorities supersedes the contractual non-disclosure constraint.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Upon Engineer A escalating to proper authorities after Engineer B fails to take corrective action",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Confidentiality Obligation Overridden"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#CausalChain_17a0c983",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A voluntarily agrees to serve as a peer reviewer within an organized peer review program, [leading to signing] a formal confidentiality agreement committing to non-disclosure of confidential information",
  "proeth:causalSequence": [
    {
      "proeth:description": "An organized peer review program is instituted, creating the formal context and requirement for confidentiality",
      "proeth:element": "Peer Review Program Established",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A voluntarily agrees to participate, triggering the obligation to sign the confidentiality agreement",
      "proeth:element": "Accept Peer Reviewer Role",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A formally signs the agreement, converting a voluntary choice into a binding legal and professional obligation",
      "proeth:element": "Sign Confidentiality Agreement",
      "proeth:step": 3
    },
    {
      "proeth:description": "The agreement becomes enforceable, constraining Engineer A\u0027s future disclosure options",
      "proeth:element": "Confidentiality Agreement Binding",
      "proeth:step": 4
    },
    {
      "proeth:description": "The binding confidentiality obligation becomes one pole of the later ethical tension when safety violations are discovered",
      "proeth:element": "Ethical Dilemma Instantiated",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Peer Reviewer Role",
  "proeth:counterfactual": "Without Engineer A accepting the reviewer role, no confidentiality agreement would have been signed and no binding obligation would exist",
  "proeth:effect": "Confidentiality Agreement Binding",
  "proeth:necessaryFactors": [
    "Voluntary acceptance of peer reviewer role",
    "Existence of an organized peer review program",
    "Formal confidentiality agreement as program requirement"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Acceptance of role + program structure requiring confidentiality + Engineer A\u0027s signature"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#CausalChain_d13876c8",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "During examination of Engineer B\u0027s technical documentation, Engineer A discovers evidence of potential safety code violations",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A\u0027s role acceptance authorizes and obligates the technical review",
      "proeth:element": "Accept Peer Reviewer Role",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A actively examines Engineer B\u0027s firm\u0027s technical documentation",
      "proeth:element": "Conduct Technical Documentation Review",
      "proeth:step": 2
    },
    {
      "proeth:description": "Evidence of potential safety code violations is identified within the documentation",
      "proeth:element": "Safety Violations Discovered",
      "proeth:step": 3
    },
    {
      "proeth:description": "Discovery immediately creates tension between confidentiality obligations and public safety duties",
      "proeth:element": "Ethical Dilemma Instantiated",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A exercises professional judgment to evaluate urgency and severity of the discovered violations",
      "proeth:element": "Assess Imminence of Public Risk",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Conduct Technical Documentation Review",
  "proeth:counterfactual": "Without conducting the technical documentation review, the violations would not have been discovered by Engineer A; they may have remained hidden indefinitely",
  "proeth:effect": "Safety Violations Discovered",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s active review of technical documentation",
    "Actual existence of safety code violations in Engineer B\u0027s work",
    "Engineer A\u0027s professional competence to identify violations"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (discovery); Engineer B (originating violations)",
  "proeth:sufficientFactors": [
    "Active review + existing violations + technical competence of reviewer"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#CausalChain_6e83f454",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The discovery of safety violations creates an active, irresolvable tension between Engineer A\u0027s contractual confidentiality obligation and professional duty to protect public safety",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A is legally and professionally bound to non-disclosure",
      "proeth:element": "Confidentiality Agreement Binding",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A uncovers evidence of potential safety code violations during review",
      "proeth:element": "Safety Violations Discovered",
      "proeth:step": 2
    },
    {
      "proeth:description": "Confidentiality obligation and public safety duty come into direct, active conflict",
      "proeth:element": "Ethical Dilemma Instantiated",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A attempts to resolve the dilemma by evaluating the urgency of the risk",
      "proeth:element": "Assess Imminence of Public Risk",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A pursues the least-disclosure path first, attempting resolution within confidentiality bounds",
      "proeth:element": "Notify Engineer B of Violations",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Safety Violations Discovered",
  "proeth:counterfactual": "Without the discovery of violations, no ethical dilemma would arise; without the confidentiality agreement, disclosure would be straightforward; either factor alone is insufficient to produce the dilemma",
  "proeth:effect": "Ethical Dilemma Instantiated",
  "proeth:necessaryFactors": [
    "Pre-existing binding confidentiality agreement",
    "Discovery of genuine safety code violations",
    "Engineer A\u0027s professional duty to protect public safety",
    "Incompatibility between disclosure and confidentiality in this context"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (for entering the role); Engineer B (for creating the violations); Program administrators (for inadequate override provisions)",
  "proeth:sufficientFactors": [
    "Binding confidentiality + discovered violations + professional safety duty = irresolvable ethical conflict"
  ],
  "proeth:withinAgentControl": false
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#CausalChain_987595df",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As an outcome of Engineer A\u0027s notification action, Engineer B becomes aware of the identified safety violations [and] upon notification of violations, an implicit or explicit deadline for Engineer B to take corrective action is triggered",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A determines that direct notification to Engineer B is the appropriate first step",
      "proeth:element": "Assess Imminence of Public Risk",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A expeditiously communicates the discovered violations to Engineer B",
      "proeth:element": "Notify Engineer B of Violations",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B gains formal awareness of the safety code violations",
      "proeth:element": "Engineer B Notified of Violations",
      "proeth:step": 3
    },
    {
      "proeth:description": "An implicit or explicit deadline for Engineer B to remediate violations is activated",
      "proeth:element": "Corrective Action Deadline Triggered",
      "proeth:step": 4
    },
    {
      "proeth:description": "If Engineer B fails to act within the deadline, Engineer A proceeds to escalation",
      "proeth:element": "Escalate to Proper Authorities",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Notify Engineer B of Violations",
  "proeth:counterfactual": "Without notification, Engineer B would have no formal awareness of the violations and no deadline would be triggered; Engineer A would face immediate escalation pressure",
  "proeth:effect": "Corrective Action Deadline Triggered",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s decision to notify Engineer B",
    "Successful communication of the nature and severity of violations",
    "Professional or programmatic norms establishing a response expectation"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (for triggering the deadline via notification); Engineer B (for bearing the corrective obligation)",
  "proeth:sufficientFactors": [
    "Notification + awareness of violations + professional accountability norms = deadline obligation on Engineer B"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/181#",
    "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/181#CausalChain_eca5cf08",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "If Engineer B fails to take appropriate corrective action following notification, Engineer A decides [to escalate]; when Engineer A escalates to proper authorities, the confidentiality agreement is effectively overridden by the superior obligation to protect public safety",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B is given an opportunity to remediate violations without external disclosure",
      "proeth:element": "Corrective Action Deadline Triggered",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B does not take appropriate corrective action within the deadline period",
      "proeth:element": "Engineer B Fails to Act",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A makes the volitional decision to report violations to regulatory or safety authorities",
      "proeth:element": "Escalate to Proper Authorities",
      "proeth:step": 3
    },
    {
      "proeth:description": "The act of escalation effectively supersedes the confidentiality agreement, justified by the primacy of public safety",
      "proeth:element": "Confidentiality Obligation Overridden",
      "proeth:step": 4
    },
    {
      "proeth:description": "Proper authorities gain knowledge of violations and can mandate corrective action, fulfilling Engineer A\u0027s paramount professional duty",
      "proeth:element": "Public Safety Protected",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Escalate to Proper Authorities",
  "proeth:counterfactual": "If Engineer B had taken timely corrective action, escalation would not have occurred and confidentiality would have remained intact; if no proper authorities existed, escalation would be impossible",
  "proeth:effect": "Confidentiality Obligation Overridden",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s failure to take corrective action within the deadline",
    "Engineer A\u0027s professional duty to protect public safety superseding confidentiality",
    "Engineer A\u0027s volitional decision to escalate",
    "Existence of proper authorities with jurisdiction over the violations"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (for escalation decision); Engineer B (for inaction that necessitated escalation)",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s inaction + imminent public risk + Engineer A\u0027s escalation decision = confidentiality override"
  ],
  "proeth:withinAgentControl": true
}