{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Action_Owner_Consents_to_Notifying_Engineer_A",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Refuse to accept Engineer B\u0027s condition and seek a different reviewer willing to conduct the review covertly",
    "Agree to notify Engineer A and simultaneously use the notification as an opportunity to renegotiate or terminate Engineer A\u0027s contract",
    "Accept the notification requirement and approach Engineer A collaboratively, framing the peer review as a shared quality assurance measure rather than an adversarial audit"
  ],
  "proeth-scenario:characterMotivation": "The owner\u0027s consent to notify Engineer A is reluctant and pragmatic rather than principled \u2014 they want the peer review to proceed and Engineer B\u0027s refusal has made notification the only available path forward. The owner is not necessarily convinced that notification is the right thing to do, but is willing to defer to professional norms in order to achieve their safety and risk-management goals.",
  "proeth-scenario:consequencesIfAlternative": [
    "Seeking a more compliant reviewer would likely result in the same ethical refusal from any competent engineer aware of professional obligations, or \u2014 if a compliant reviewer is found \u2014 produce a tainted review conducted by an engineer willing to compromise their ethics, which undermines the review\u0027s value",
    "Using notification as a pretext for contract renegotiation would likely escalate conflict with Engineer A and could expose the owner to breach-of-contract claims, while also tainting the peer review with an apparent ulterior motive",
    "A collaborative framing might have reduced Engineer A\u0027s defensiveness and increased the likelihood of cooperation, potentially avoiding the refusal that follows \u2014 this represents a missed opportunity for a better outcome"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that professional ethical norms can and do constrain client behavior, not just engineer behavior. Illustrates how a well-positioned engineer (Engineer B) can effectively advocate for ethical process by making it a condition of engagement. Also introduces the concept that ethical compliance can be reluctant and still count as compliance \u2014 though it raises questions about whether the owner\u0027s attitude will affect how they handle Engineer A\u0027s subsequent refusal.",
  "proeth-scenario:ethicalTension": "The owner\u0027s preference for information control and conflict avoidance is in tension with the professional norms Engineer B has insisted upon. The owner must weigh their desire for a clean, uncontested review against the requirement to engage transparently with Engineer A. There is also a subtle tension between the owner\u0027s authority over the project and the limits that professional ethics place on how that authority may be exercised.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "The viability of the peer review process, the owner\u2013Engineer A relationship, and the downstream risk that Engineer A will react adversely to notification \u2014 which is exactly what occurs. The owner\u0027s reluctance signals that they have not fully internalized the professional rationale for notification, which may affect how they respond to Engineer A\u0027s refusal.",
  "proeth:description": "Faced with Engineer B\u0027s refusal to proceed covertly, the owner reluctantly agrees to notify Engineer A of the planned peer review. This represents a recalibration of the owner\u0027s initial preference for confidentiality in deference to professional norms.",
  "proeth:foreseenUnintendedEffects": [
    "Potential conflict with Engineer A",
    "Risk that Engineer A might object or obstruct the review"
  ],
  "proeth:fulfillsObligation": [
    "Deferred to professional norms governing peer review",
    "Took a step toward protecting public safety by enabling the review to proceed properly"
  ],
  "proeth:guidedByPrinciple": [
    "Respect for professional obligations",
    "Public safety",
    "Good-faith engagement with professional process"
  ],
  "proeth:hasAgent": "Owner (Client/Project Developer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Owner\u0027s confidentiality preference vs. enabling a professionally valid peer review",
    "proeth:resolutionReasoning": "Owner recognized that the peer review could not proceed without notification and that safety concerns outweighed the preference for confidentiality"
  },
  "proeth:hasMentalState": "reluctant but deliberate",
  "proeth:intendedOutcome": "Preserve the peer review engagement with Engineer B by conceding the notification requirement, while still obtaining the safety assurance needed for the second tower",
  "proeth:requiresCapability": [
    "Client decision-making authority",
    "Willingness to adapt procurement approach"
  ],
  "proeth:temporalMarker": "After Engineer B objects to the covert assignment",
  "proeth:withinCompetence": true,
  "rdfs:label": "Owner Consents to Notifying Engineer A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Action_Engineer_A_Refuses_Peer_Review_Consent",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Consent to the peer review while requesting that the scope and process be clearly defined and that findings be shared with Engineer A before being finalized",
    "Consent to the peer review and proactively engage with Engineer B collaboratively, offering to explain design decisions and address questions directly",
    "Withdraw from the second tower project entirely rather than refusing the peer review, allowing the owner to retain a new engineer of record without the ethical conflict"
  ],
  "proeth-scenario:characterMotivation": "Engineer A\u0027s refusal likely stems from a combination of professional defensiveness, fear of reputational damage from a formal finding of errors, concern about liability exposure, and possibly genuine belief that the peer review is punitive or unwarranted. Having already been associated with significant design errors in the first tower, Engineer A may perceive the peer review as a threat to their professional standing and financial interests rather than as a legitimate quality assurance measure.",
  "proeth-scenario:consequencesIfAlternative": [
    "Consenting with defined process conditions would be ethically compliant while still protecting Engineer A\u0027s legitimate interests in procedural fairness \u2014 this is arguably the most professionally mature response and would likely satisfy the BER\u0027s standard",
    "Proactive collaborative engagement would demonstrate professional integrity, potentially improve the quality of the peer review, and position Engineer A as a cooperative professional rather than a defensive one \u2014 the best possible outcome for Engineer A\u0027s reputation",
    "Withdrawing from the project, while costly, would be more ethically defensible than refusing the review and would at least remove Engineer A from a situation where their defensiveness poses a public safety risk"
  ],
  "proeth-scenario:decisionSignificance": "Identified by the BER as an ethical violation, this action provides a clear negative example for teaching. Students learn that professional obligations do not disappear when compliance is personally inconvenient or professionally threatening. The case illustrates that the duty to protect public safety supersedes personal professional interests, and that refusing legitimate peer review is itself an ethical breach \u2014 not a neutral exercise of professional discretion. It also raises questions about what enforcement mechanisms exist when engineers refuse to cooperate.",
  "proeth-scenario:ethicalTension": "Engineer A\u0027s self-interest in protecting their reputation and livelihood conflicts directly with their professional obligation to prioritize public safety and cooperate with legitimate oversight processes. The NSPE Code\u0027s requirement to hold public safety paramount (Section I) is in direct conflict with Engineer A\u0027s instinct toward self-preservation. There is also a tension between an engineer\u0027s autonomy over their own work product and the profession\u0027s collective interest in quality assurance.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Public safety is the paramount stake \u2014 if Engineer A\u0027s plans for the second tower contain errors similar to those in the first and no peer review occurs, occupants of the second tower face potential structural risk. Engineer A\u0027s professional license is also at stake, as the BER\u0027s finding implies that this refusal could itself be grounds for disciplinary action. The owner\u0027s project timeline, budget, and legal exposure are all affected.",
  "proeth:description": "After being formally notified of the planned peer review of their second tower plans, Engineer A objects and refuses to consent to the review. The BER identifies this refusal as an ethical violation, as it prioritizes personal professional interests over the obligation to cooperate in the interest of public safety.",
  "proeth:foreseenUnintendedEffects": [
    "Creates ethical violation per BER findings",
    "Leaves the second tower\u0027s design safety unverified",
    "Undermines owner\u0027s ability to protect public safety",
    "May expose Engineer A to greater professional liability"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety paramount",
    "Professional accountability",
    "Cooperation with legitimate review processes"
  ],
  "proeth:hasAgent": "Engineer A (Engineer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Self-protection of professional reputation vs. Public safety and professional cooperation obligations",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict in favor of self-protection, which the BER identifies as ethically impermissible; public safety and professional cooperation obligations must take precedence over personal reputational interests"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Protect professional reputation and design authority by preventing external scrutiny of their work, particularly in the context of already-discovered errors in the first tower",
  "proeth:requiresCapability": [
    "Professional judgment about ethical obligations",
    "Willingness to subordinate personal interests to public safety"
  ],
  "proeth:temporalMarker": "After being notified of the peer review by the owner",
  "proeth:violatesObligation": [
    "Obligation to hold public health, safety, and welfare paramount above personal or professional interests",
    "Obligation to cooperate with peer review processes as identified by the BER",
    "Obligation to support the client\u0027s right to obtain independent review of engineering work",
    "NSPE Code obligation not to obstruct another engineer from practicing professionally"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Engineer A Refuses Peer Review Consent"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Action_Engineer_A_Creates_Flawed_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Request a self-directed internal review or bring in a junior engineer to independently check the plans before submission",
    "Proactively disclose uncertainty about specific design elements to the owner and recommend a formal peer review before construction",
    "Decline to design the second tower until lessons learned from the first tower\u0027s construction phase are fully incorporated"
  ],
  "proeth-scenario:characterMotivation": "Engineer A likely proceeded with professional confidence in their own competence, possibly under time or contractual pressure to deliver plans for both towers simultaneously or in close succession. The mirror-image design may have created false assurance that a single design framework could be applied without sufficient independent verification for each structure.",
  "proeth-scenario:consequencesIfAlternative": [
    "An internal review may have caught the design errors before construction began, avoiding the entire downstream ethical conflict and protecting public safety without involving a third party",
    "Proactive disclosure would have demonstrated professional integrity, potentially preserved the client relationship, and allowed a peer review to be arranged collaboratively \u2014 eliminating the covert-review dynamic entirely",
    "Declining the second tower until construction feedback was integrated would have delayed the project but produced a safer, more defensible design, and modeled appropriate professional humility"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how professional competence obligations (NSPE Code Section II.2) require engineers to perform services only in areas of competence and to have work reviewed when errors are possible. Teaches that delivering flawed work \u2014 even unintentionally \u2014 creates downstream ethical and legal liability and underscores the importance of internal quality control processes before plan submission.",
  "proeth-scenario:ethicalTension": "Professional duty to deliver thorough, accurate engineering work versus schedule demands, client expectations, and the economic incentive to retain a lucrative two-tower contract. Self-confidence in one\u0027s own expertise can conflict with the humility required to recognize and disclose one\u0027s own errors.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Structural integrity of both towers, public safety of future occupants, Engineer A\u0027s professional license and reputation, owner\u0027s financial investment, and the legal liability exposure for all parties. If errors go undetected into the second tower, the consequences could include structural failure, injury, or death.",
  "proeth:description": "Engineer A develops design plans for both mirror-image towers, introducing significant design errors into the work product. This decision to proceed and deliver flawed plans represents a professional failure at the initial design stage.",
  "proeth:foreseenUnintendedEffects": [
    "None foreseen by Engineer A; errors suggest oversight or negligence rather than intent"
  ],
  "proeth:fulfillsObligation": [
    "Accepted a commission within nominal professional scope"
  ],
  "proeth:guidedByPrinciple": [
    "Competence",
    "Public safety",
    "Professional integrity"
  ],
  "proeth:hasAgent": "Engineer A (Engineer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Delivery efficiency vs. Design accuracy",
    "proeth:resolutionReasoning": "Insufficient quality control suggests timeline or resource pressures were implicitly prioritized over exhaustive design verification"
  },
  "proeth:hasMentalState": "deliberate in producing plans, likely negligent regarding errors",
  "proeth:intendedOutcome": "Deliver complete and accurate design plans for both towers to the owner",
  "proeth:requiresCapability": [
    "Structural or architectural engineering design",
    "Self-review and quality assurance",
    "Peer-level design verification"
  ],
  "proeth:temporalMarker": "Initial design phase, prior to construction of either tower",
  "proeth:violatesObligation": [
    "NSPE Code obligation to hold public safety, health, and welfare paramount",
    "Obligation to perform services only in areas of competence",
    "Obligation to practice with honesty and integrity in engineering work product"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Engineer A Creates Flawed Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Action_Owner_Retains_Engineer_B_Covertly",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Notify Engineer A upfront and request their cooperation with a peer review as a contractual condition of proceeding with the second tower",
    "Terminate Engineer A\u0027s contract for the second tower entirely based on the demonstrated errors in the first tower and hire a new engineer of record",
    "Engage Engineer B openly as a construction-phase oversight engineer rather than framing the engagement as a peer review of Engineer A\u0027s plans"
  ],
  "proeth-scenario:characterMotivation": "The owner\u0027s primary motivation is self-protection and risk mitigation following the costly discovery of design errors in the first tower. Having lost confidence in Engineer A, the owner seeks an independent assessment of the second tower\u0027s plans while avoiding a potentially adversarial confrontation with Engineer A, whom they may still be contractually obligated to retain. The covert approach reflects a business instinct to manage information and control the narrative.",
  "proeth-scenario:consequencesIfAlternative": [
    "Upfront notification would have been more transparent and professionally appropriate, potentially allowing Engineer A to participate constructively \u2014 though it risks confrontation, it avoids the ethical violations that follow in the narrative",
    "Terminating Engineer A would have been a clean break that eliminated the peer review conflict entirely, though it carries contractual, financial, and timeline costs and does not guarantee the second engineer avoids similar errors",
    "Reframing the engagement might have achieved the owner\u0027s safety goals while sidestepping the peer review notification issue, though it could be seen as a semantic workaround rather than a genuine resolution"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that clients, even when acting in good faith to protect safety, can inadvertently pressure engineers into ethically compromised positions. Teaches students that the owner\u0027s role in an engineering project carries ethical responsibilities, not just legal ones, and that circumventing professional norms \u2014 even with good intentions \u2014 can undermine the integrity of the review process itself. Sets up the pivotal lesson about Engineer B\u0027s obligations.",
  "proeth-scenario:ethicalTension": "The owner\u0027s legitimate interest in protecting their investment and ensuring building safety conflicts with Engineer A\u0027s professional right to know that their work is under review. Transparency and fairness to the engineer of record are in tension with the owner\u0027s desire for an unfiltered, uncontested independent assessment. There is also a tension between the owner\u0027s authority to hire consultants and the professional norms that govern how peer reviews must be conducted.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The integrity of the peer review process, Engineer A\u0027s right to professional due process, Engineer B\u0027s ethical standing if they comply, and the owner\u0027s exposure to claims of bad faith dealing with Engineer A. A covert review could also produce findings that are legally or professionally difficult to act upon.",
  "proeth:description": "After discovering significant design errors in the first tower, the owner decides to obtain a peer review of Engineer A\u0027s plans for the second tower and retains Engineer B without informing Engineer A. This is a deliberate choice to conduct a covert review, circumventing Engineer A\u0027s awareness.",
  "proeth:foreseenUnintendedEffects": [
    "Potential professional and ethical conflict with Engineer B\u0027s obligations",
    "Risk of undermining the peer review\u0027s utility if Engineer A\u0027s cooperation is later needed"
  ],
  "proeth:fulfillsObligation": [
    "Exercised due diligence in seeking to protect the second project after discovering prior errors"
  ],
  "proeth:guidedByPrinciple": [
    "Owner\u0027s right to seek peer review",
    "Duty to protect public safety",
    "Respect for professional norms"
  ],
  "proeth:hasAgent": "Owner (Client/Project Developer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Confidentiality and conflict avoidance vs. Professional notification obligations",
    "proeth:resolutionReasoning": "Owner prioritized confidentiality but was overridden by Engineer B\u0027s professional obligations, forcing a reconsideration"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Obtain an independent assessment of the second tower\u0027s design integrity without alerting Engineer A, preserving confidentiality and avoiding potential conflict",
  "proeth:requiresCapability": [
    "Project management decision-making",
    "Understanding of engineering procurement"
  ],
  "proeth:temporalMarker": "After discovery of errors during first tower construction, before second tower begins",
  "proeth:violatesObligation": [
    "Obligation to respect the professional relationship and rights of Engineer A as engineer of record",
    "Implicit obligation not to direct a second engineer to act in violation of professional codes"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Owner Retains Engineer B Covertly"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Action_Engineer_B_Refuses_Covert_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept the assignment and conduct the covert review, rationalizing that public safety outweighs the notification obligation",
    "Accept the assignment but unilaterally notify Engineer A without the owner\u0027s consent before proceeding",
    "Decline the assignment entirely and withdraw from the engagement rather than negotiating the notification condition"
  ],
  "proeth-scenario:characterMotivation": "Engineer B is motivated by adherence to professional ethical obligations, specifically the duty to treat colleagues with fairness and to notify an engineer whose work is being reviewed before proceeding. Engineer B recognizes that conducting a covert review would compromise their own integrity, potentially harm Engineer A\u0027s professional standing without due process, and violate the collegial norms that sustain the engineering profession\u0027s self-regulatory legitimacy.",
  "proeth-scenario:consequencesIfAlternative": [
    "Conducting the covert review would violate professional ethics, expose Engineer B to disciplinary action, potentially invalidate the review\u0027s findings in any subsequent legal proceeding, and undermine the collegial norms that protect all engineers from similar treatment",
    "Unilaterally notifying Engineer A without owner consent would achieve the ethical goal but breach the Engineer B\u2013owner relationship and potentially expose Engineer B to claims of unauthorized disclosure, though it is arguably still more defensible than the covert alternative",
    "Withdrawing entirely would protect Engineer B\u0027s ethics but leave the owner without a path to a legitimate peer review, potentially resulting in the owner proceeding without any review \u2014 a worse outcome for public safety"
  ],
  "proeth-scenario:decisionSignificance": "This is the central ethically correct action of the case and the primary teaching moment. It illustrates NSPE Code obligations regarding fair treatment of fellow engineers and the peer review notification requirement. Students learn that ethical behavior sometimes requires refusing a client\u0027s direct request, that professional norms exist to protect all parties including the public, and that integrity in process is as important as the outcome of the review itself.",
  "proeth-scenario:ethicalTension": "Engineer B faces tension between satisfying a client\u0027s request \u2014 and the associated business relationship and compensation \u2014 versus upholding professional obligations to a fellow engineer. There is also tension between the owner\u0027s genuine safety interest (which Engineer B likely shares) and the means the owner has chosen to pursue it. Doing the right thing risks losing the engagement entirely.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer B\u0027s professional license and reputation if they comply with an ethically improper request; the legitimacy and defensibility of the peer review findings; Engineer A\u0027s right to professional due process; and the broader integrity of the peer review system as a public safety mechanism. If Engineer B complies covertly, the entire review process is tainted.",
  "proeth:description": "Upon receiving the assignment to conduct a peer review of Engineer A\u0027s plans without Engineer A\u0027s knowledge, Engineer B declines to proceed under those conditions, citing the professional obligation to notify the engineer whose work is being reviewed. This is the central ethically correct action identified by the BER.",
  "proeth:foreseenUnintendedEffects": [
    "Owner dissatisfaction or potential loss of the engagement",
    "Delay in resolving the safety concern for the second tower"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Professional Obligation III.7.a: obligation to notify engineer whose work is under review before proceeding",
    "Obligation to act with integrity and not participate in professionally improper conduct",
    "Obligation to protect the interests of Engineer A as a fellow professional"
  ],
  "proeth:guidedByPrinciple": [
    "Professional integrity",
    "Collegial respect",
    "Adherence to established peer review protocols",
    "Honesty"
  ],
  "proeth:hasAgent": "Engineer B (Peer Reviewer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client service and public safety urgency vs. Professional notification obligation to Engineer A",
    "proeth:resolutionReasoning": "Engineer B determined that professional obligations are non-negotiable preconditions for the engagement and cannot be waived by client preference, even in the presence of safety urgency"
  },
  "proeth:hasMentalState": "deliberate and principled",
  "proeth:intendedOutcome": "Ensure that any peer review conducted complies with professional ethical obligations, specifically the requirement to notify Engineer A before reviewing their work",
  "proeth:requiresCapability": [
    "Knowledge of NSPE ethical obligations",
    "Professional judgment regarding peer review protocols",
    "Ability to communicate ethical boundaries to clients"
  ],
  "proeth:temporalMarker": "Upon receiving the peer review assignment from the owner",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Refuses Covert Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Action_Owner_Selects_Post-Refusal_Strategy",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Proceed with a limited peer review using Engineer B\u0027s professional judgment without Engineer A\u0027s cooperation, documenting Engineer A\u0027s refusal formally and adjusting the scope of review accordingly",
    "Terminate Engineer A\u0027s contract for the second tower based on the demonstrated errors and the refusal to cooperate with safety oversight, and retain a new engineer of record who will work collaboratively with Engineer B",
    "Proceed with construction without any peer review, accepting the risk and relying on standard inspection processes to catch any errors"
  ],
  "proeth-scenario:characterMotivation": "The owner is motivated by the need to resolve an impasse that threatens both the safety of the second tower and the project timeline. Having already invested significantly in Engineer A\u0027s plans and facing the prospect of further delays or costs, the owner must balance risk management, contractual obligations, financial constraints, and public safety duties. Each available option carries different cost, time, and liability profiles.",
  "proeth-scenario:consequencesIfAlternative": [
    "A limited peer review without Engineer A\u0027s cooperation is imperfect but better than no review \u2014 Engineer B can still identify errors in the plans, though without Engineer A\u0027s design rationale some issues may be harder to evaluate. This option preserves the safety function of the review while documenting Engineer A\u0027s ethical failure for potential disciplinary referral",
    "Replacing Engineer A is the most ethically robust option from a public safety standpoint, ensuring that the second tower is designed and reviewed by engineers committed to cooperative quality assurance \u2014 but it carries significant cost, delay, and potential litigation risk from Engineer A",
    "Proceeding without any peer review after known errors in the first tower and a documented refusal of oversight would almost certainly constitute negligence, expose the owner to massive liability in the event of structural failure, and represent a profound ethical failure by the owner \u2014 this option is identified as clearly unacceptable"
  ],
  "proeth-scenario:decisionSignificance": "Functions as the scenario\u0027s prospective ethical decision point, inviting students to apply everything learned from the prior actions to a consequential real-world choice. Teaches that ethical obligations do not end when a process breaks down \u2014 the owner retains a duty to pursue public safety through available means. Also illustrates that clients bear ethical responsibilities in engineering projects, not just engineers, and that the structure of available choices is itself shaped by the ethical failures that preceded this moment.",
  "proeth-scenario:ethicalTension": "The owner faces a three-way tension among public safety (the paramount concern), financial and contractual self-interest (minimizing cost and delay), and fairness to Engineer A (who, despite their ethical failure, retains contractual and professional rights). The option to proceed with construction without any peer review is the most ethically indefensible but may appear attractive if the owner underweights safety relative to schedule. The option to replace Engineer A is ethically cleanest but most costly.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "The highest stakes of the entire scenario converge here: the structural safety of a building that will house people, the owner\u0027s legal and financial liability, the professional futures of both engineers, and the precedent set for how the profession handles peer review refusals. Choosing to proceed without any review in the face of known prior errors would be an egregious ethical failure that could result in structural harm, legal liability, and regulatory action.",
  "proeth:description": "Faced with Engineer A\u0027s refusal to consent to the peer review, the owner must choose among three options: proceed with a limited peer review without Engineer A\u0027s cooperation, proceed with construction without any peer review, or replace Engineer A entirely. This prospective decision carries significant ethical and safety implications.",
  "proeth:foreseenUnintendedEffects": [
    "Proceeding without peer review risks replicating errors from the first tower",
    "Replacing Engineer A introduces transition costs and delays but may be the most comprehensive safety remedy",
    "A limited peer review without Engineer A\u0027s cooperation may yield incomplete findings"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to seek safety assurance for the second tower given known prior errors",
    "Obligation to protect public welfare by not proceeding with a potentially flawed design without review"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety paramount",
    "Due diligence",
    "Responsible project stewardship"
  ],
  "proeth:hasAgent": "Owner (Client/Project Developer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Project continuity and cost efficiency vs. Rigorous safety assurance through independent peer review",
    "proeth:resolutionReasoning": "The BER discussion contextualizes Engineer A\u0027s non-cooperation as ethically impermissible and implies the owner\u0027s best path to safety assurance \u2014 given Engineer A\u0027s refusal \u2014 is replacement of Engineer A, though the case leaves the final decision to the owner"
  },
  "proeth:hasMentalState": "deliberate under constraint",
  "proeth:intendedOutcome": "Resolve the impasse created by Engineer A\u0027s refusal in a way that adequately protects the second tower\u0027s structural integrity and the public safety of future occupants",
  "proeth:requiresCapability": [
    "Project management authority",
    "Risk assessment judgment",
    "Contractual authority to replace Engineer A if necessary"
  ],
  "proeth:temporalMarker": "Prospective decision point following Engineer A\u0027s refusal, before second tower construction begins",
  "proeth:violatesObligation": [
    "Proceeding without any peer review would violate the owner\u0027s implicit duty to ensure structural safety given prior known errors"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Owner Selects Post-Refusal Strategy"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Event_Design_Errors_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what earlier stage could these design errors have been caught, and what professional obligations existed at those stages to ensure they were?",
    "Does the discovery of significant errors in Tower One create a professional or ethical obligation to proactively review Tower Two before construction begins, even absent an owner request?",
    "How should the engineering profession balance the presumption of a licensed engineer\u0027s competence against the demonstrated risk of unchecked errors in high-stakes projects?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Owner experiences alarm and financial anxiety upon discovering the scope of errors; construction team faces uncertainty and potential work stoppages; Engineer A faces professional embarrassment, defensiveness, and fear of reputational damage; broader project stakeholders feel distrust and concern about structural safety",
  "proeth-scenario:ethicalImplications": "Reveals the tension between professional autonomy and accountability; exposes the limits of self-certification when public safety is at stake; raises questions about whether the profession\u0027s peer review norms are sufficiently enforced or merely aspirational; highlights how economic pressures may discourage engineers from acknowledging errors or welcoming external scrutiny",
  "proeth-scenario:learningMoment": "Illustrates how design errors that escape pre-construction review are often only revealed under the stress of actual construction, and how a single professional\u0027s deficient work can cascade into safety risks, financial harm, and erosion of trust \u2014 underscoring the systemic value of peer review and quality assurance before construction begins.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "construction_team": "Work potentially halted or revised mid-project; confusion about revised specifications; schedule disruption",
    "engineer_a": "Professional reputation damaged; competence called into question; potential liability exposure; heightened sensitivity to external scrutiny",
    "engineering_profession": "Confidence in professional self-regulation tested; peer review mechanisms validated as necessary safeguard",
    "future_tower_two_occupants": "Latent safety risk if similar errors persist into Tower Two; public safety interest implicated",
    "owner": "Financial losses from construction delays and remediation costs; loss of confidence in Engineer A; motivation to seek independent review for Tower Two"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Engineer_Competence_Obligation",
    "Design_Integrity_Verification_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Engineer_A_Creates_Flawed_Plans",
  "proeth:causesStateChange": "Project status shifts from routine construction to deficiency-remediation mode; owner\u0027s confidence in Engineer A\u0027s work is undermined; Tower Two plans become suspect by association; a basis for peer review of Tower Two is established",
  "proeth:createsObligation": [
    "Owner_Seek_Remediation_For_Tower_One",
    "Owner_Reassess_Tower_Two_Plans",
    "Engineer_A_Correct_Deficiencies",
    "Notify_Relevant_Parties_Of_Errors"
  ],
  "proeth:description": "Significant design errors in Engineer A\u0027s plans are discovered during construction of the first tower, revealing a pattern of deficient professional work. This discovery occurs organically through the construction process rather than through any deliberate investigative decision.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During construction of Tower One",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Design Errors Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Event_Tower_Two_Plans_Implicated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When a design error is found in one project, what professional obligation does the engineer of record have to proactively flag related projects that may share the same flaw?",
    "Should owners of large multi-structure developments be required to conduct peer reviews as a standard contractual practice rather than an exceptional measure?",
    "How does the mirror-image design relationship change the ethical calculus for both the owner and Engineer A regarding Tower Two?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Owner feels compounding dread \u2014 not only is Tower One compromised, but Tower Two is now also in doubt before construction even begins; Engineer A may feel cornered, knowing that scrutiny of Tower Two is now rationally inevitable; future occupants of Tower Two face an unacknowledged risk",
  "proeth-scenario:ethicalImplications": "Highlights the systemic risk created when professional quality control is deferred until errors manifest physically; raises questions about whether Engineer A had an independent obligation to audit Tower Two plans upon discovery of Tower One errors; underscores the public safety dimension of engineering practice beyond the immediate client relationship",
  "proeth-scenario:learningMoment": "Demonstrates how professional errors rarely stay contained \u2014 design deficiencies can propagate across related projects, multiplying risk and liability, and illustrates why proactive quality assurance across an entire project portfolio is preferable to reactive error discovery.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Faces expanded professional exposure; errors in one project now threaten to invalidate a second project\u0027s plans",
    "engineering_profession": "The case for mandatory peer review of high-stakes projects is reinforced by this automatic implication",
    "future_tower_two_occupants": "Public safety interest heightened; unverified plans represent a latent hazard",
    "owner": "Faces doubled financial and schedule risk; now must decide how to address Tower Two before committing further resources"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Design_Integrity_Verification_Constraint",
    "Owner_Due_Diligence_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Engineer_A_Creates_Flawed_Plans",
  "proeth:causesStateChange": "Tower Two\u0027s pre-construction status shifts from presumptively adequate to presumptively suspect; the logical basis for a peer review of Tower Two is established; the owner\u0027s motivation to retain Engineer B is triggered",
  "proeth:createsObligation": [
    "Owner_Commission_Independent_Review_Tower_Two",
    "Verify_Tower_Two_Plans_Before_Construction",
    "Engineer_A_Disclose_Potential_Mirror_Errors"
  ],
  "proeth:description": "Because the two towers are mirror-image designs by the same engineer, the discovery of errors in Tower One\u0027s plans automatically implicates the structural reliability of Tower Two\u0027s plans. This is not a decision but an automatic logical and physical consequence of the shared design lineage.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Immediately following discovery of Tower One errors",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Tower Two Plans Implicated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Event_Engineer_B_Notification_Obligation_Activated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why does the professional code require notification before peer review, and what harms does this requirement prevent?",
    "Is Engineer B\u0027s refusal to conduct a covert review an act of professional courage, routine compliance, or both?",
    "How should Engineer B respond if the owner threatens to find a different engineer who will conduct the review covertly?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer B experiences professional clarity \u2014 the obligation is unambiguous \u2014 but also tension from the owner\u0027s evident desire for a covert process; the owner feels frustrated that a straightforward business decision has been complicated by professional norms; Engineer A remains unaware at this stage",
  "proeth-scenario:ethicalImplications": "Reveals the tension between client service and professional integrity; demonstrates that engineers owe duties to the profession and to colleagues, not only to clients; raises the question of whether professional norms that protect engineers from covert scrutiny are in tension with public safety interests when the engineer being protected has a demonstrated error history",
  "proeth-scenario:learningMoment": "Illustrates that professional obligations are not optional accommodations to client preferences \u2014 they are binding constraints that engineers must assert even when clients resist, and that professional codes exist partly to protect engineers from being instrumentalized against their colleagues.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Gains the right to be notified and to respond \u2014 a procedural protection that professional codes afford",
    "engineer_b": "Must assert professional independence against client pressure; risks losing the engagement if owner refuses to notify Engineer A",
    "engineering_profession": "Professional norms are tested against client economic interests; the outcome demonstrates whether self-regulation is meaningful",
    "owner": "Loses the option of a covert review; must confront Engineer A or abandon the peer review entirely"
  },
  "proeth:activatesConstraint": [
    "Peer_Notification_Before_Review_Constraint",
    "Professional_Collegiality_Obligation",
    "NSPE_Code_Section_III_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Owner_Retains_Engineer_B_Covertly",
  "proeth:causesStateChange": "Engineer B\u0027s engagement is conditioned on notification; covert review becomes professionally impermissible; the owner is forced to choose between transparent review and no review",
  "proeth:createsObligation": [
    "Engineer_B_Must_Notify_Engineer_A_Before_Proceeding",
    "Engineer_B_Must_Decline_Covert_Review",
    "Owner_Must_Consent_To_Notification_Or_Lose_Engineer_B"
  ],
  "proeth:description": "Upon being retained by the owner to conduct a covert peer review, Engineer B\u0027s professional obligations automatically activate the requirement to notify Engineer A before proceeding. This is not a discretionary choice by Engineer B but a binding professional norm triggered by the circumstances of retention.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Upon Owner Retaining Engineer B Covertly",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer B Notification Obligation Activated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Event_Owner_Forced_Into_Transparency",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the owner\u0027s \u0027reluctant\u0027 agreement to notify Engineer A suggest that professional norms are working as intended, or does it reveal a gap between formal compliance and genuine ethical commitment?",
    "What does it mean for a professional to hold firm on an ethical requirement against client resistance, and what personal and professional risks does this entail?",
    "If the owner had simply found a different engineer willing to conduct the review covertly, what would that reveal about the enforceability of professional ethics?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Owner feels constrained and perhaps resentful that professional norms have overridden a business preference; Engineer B may feel the discomfort of having imposed a condition on a client; the situation carries an undercurrent of anticipated conflict with Engineer A",
  "proeth-scenario:ethicalImplications": "Illustrates the practical enforceability of professional codes when individual engineers are willing to assert them; raises questions about whether professional norms that depend on individual courage are sufficiently robust; highlights the role of professional codes as structural constraints on client power",
  "proeth-scenario:learningMoment": "Shows how professional norms can structurally reshape power dynamics in a project \u2014 the owner\u0027s economic authority is constrained by the engineer\u0027s professional obligations, demonstrating that engineering ethics are not merely aspirational but have practical force.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Will now be formally notified and given the opportunity to respond \u2014 a procedural right protected by professional norms",
    "engineer_b": "Maintains professional integrity; relationship with owner may be strained but is ethically sound",
    "owner": "Must now engage directly with Engineer A on a sensitive topic; faces potential relationship damage with Engineer A; gains a professionally defensible process"
  },
  "proeth:activatesConstraint": [
    "Owner_Must_Notify_Engineer_A_Constraint",
    "Transparent_Engagement_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Engineer_B_Refuses_Covert_Review",
  "proeth:causesStateChange": "Owner\u0027s preferred covert strategy is foreclosed; the engagement shifts to a transparent, professionally compliant process; Engineer A is about to be drawn into the situation",
  "proeth:createsObligation": [
    "Owner_Notify_Engineer_A_Of_Peer_Review_Intent",
    "Owner_Provide_Engineer_A_Opportunity_To_Respond"
  ],
  "proeth:description": "As a direct consequence of Engineer B\u0027s refusal to proceed covertly, the owner is placed in a position where notification of Engineer A is the only path to obtaining the peer review. This outcome is not chosen freely but is structurally compelled by Engineer B\u0027s professional stance.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following Engineer B Refuses Covert Review",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Owner Forced Into Transparency"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Event_Engineer_A_Notified_Of_Review",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What ethical obligations does Engineer A acquire upon being notified of the peer review, and how do those obligations interact with any personal interest in protecting their professional reputation?",
    "Is there a meaningful ethical difference between an engineer who was never notified of a peer review and one who was notified and chose to obstruct it?",
    "How should professional codes address situations where the engineer whose work is under review has a demonstrated history of errors in related work?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences a mixture of defensiveness, anxiety, and perhaps resentment upon learning that the owner is seeking independent review of their work \u2014 particularly given the already-discovered errors in Tower One; the owner feels the tension of having initiated a potentially confrontational process; Engineer B awaits Engineer A\u0027s response",
  "proeth-scenario:ethicalImplications": "Highlights the tension between an engineer\u0027s legitimate interest in professional reputation and the public\u0027s interest in safety verification; raises questions about whether professional notification norms adequately balance these competing interests; illustrates how procedural fairness and substantive safety goals can come into conflict",
  "proeth-scenario:learningMoment": "Demonstrates that professional notification is not merely a courtesy but a formal trigger for obligations \u2014 once notified, Engineer A is no longer a passive party but an active professional with specific ethical duties to respond constructively to legitimate peer review.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Professional competence is formally under scrutiny; must decide how to respond, with significant ethical and reputational stakes attached to that decision",
    "engineer_b": "Engagement is now contingent on Engineer A\u0027s response; professional obligations have been fulfilled to this point",
    "owner": "Has fulfilled the notification obligation but now faces uncertainty about Engineer A\u0027s response and its implications for the project timeline",
    "public": "Notification is a procedural step toward a safety review that serves the public interest"
  },
  "proeth:activatesConstraint": [
    "Engineer_A_Professional_Response_Obligation",
    "Engineer_A_Cooperation_With_Peer_Review_Constraint",
    "NSPE_Code_Cooperation_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Owner_Consents_to_Notifying_Engineer_A",
  "proeth:causesStateChange": "Engineer A transitions from uninvolved party to notified stakeholder with active professional obligations; the ethical burden shifts to Engineer A to respond appropriately; the stage is set for Engineer A\u0027s refusal",
  "proeth:createsObligation": [
    "Engineer_A_Must_Respond_To_Notification",
    "Engineer_A_Ethically_Obligated_To_Cooperate_With_Peer_Review",
    "Engineer_A_Must_Not_Obstruct_Public_Safety_Review"
  ],
  "proeth:description": "Following the owner\u0027s consent to notification, Engineer A is formally informed that a peer review of the Tower Two plans is being sought. This notification is an outcome of the owner\u0027s decision and Engineer B\u0027s insistence, and it triggers a new set of professional obligations for Engineer A.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following Owner Consents to Notifying Engineer A",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer A Notified Of Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#Event_Peer_Review_Process_Blocked",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "If an engineer can block a peer review simply by refusing consent, what does this reveal about the adequacy of professional self-regulation as a public safety mechanism?",
    "The BER concludes that Engineer A is ethically obligated to cooperate \u2014 but what practical enforcement mechanisms exist, and are they sufficient to protect the public?",
    "Should the discovery of significant errors in Tower One have automatically triggered a mandatory review of Tower Two under regulatory or contractual frameworks, independent of Engineer A\u0027s consent?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Owner experiences frustration and alarm \u2014 the safety mechanism they sought has been blocked by the very engineer whose competence is in question; Engineer B faces professional disappointment and may feel complicit in the blockage through the notification requirement; Engineer A may feel temporary relief but faces growing ethical and reputational exposure; future Tower Two occupants face unacknowledged risk",
  "proeth-scenario:ethicalImplications": "Exposes the gap between aspirational professional ethics and enforceable standards; raises fundamental questions about whether professional self-regulation is adequate when individual engineers can obstruct safety reviews; highlights the conflict between an engineer\u0027s personal interest in avoiding scrutiny and the public\u0027s interest in safety verification; challenges the adequacy of consent-based peer review norms in high-stakes situations",
  "proeth-scenario:learningMoment": "Reveals that professional ethics are not self-enforcing \u2014 an engineer who refuses to cooperate with legitimate peer review creates a gap between the ethical standard (cooperation is obligatory) and the practical reality (no immediate mechanism to compel compliance), and illustrates why professional norms must be backed by enforcement mechanisms to be effective.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Has committed what the BER characterizes as an ethical violation; professional standing is now doubly at risk \u2014 from the original errors and from the obstruction",
    "engineer_b": "Engagement is effectively suspended; must advise owner on options; professional integrity has been maintained throughout",
    "engineering_profession": "Self-regulatory credibility is tested \u2014 if engineers can simply refuse peer review, the profession\u0027s ability to police itself is undermined",
    "owner": "Left without a verified set of Tower Two plans; faces a strategic decision about how to proceed before construction; potential financial and legal exposure if Tower Two proceeds on flawed plans",
    "public": "Safety verification has been blocked; Tower Two occupants face potential risk from unreviewed plans"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Owner_Must_Seek_Alternative_Review_Mechanism",
    "Engineer_A_Ethical_Violation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/15#Action_Engineer_A_Refuses_Peer_Review_Consent",
  "proeth:causesStateChange": "Peer review process is suspended; public safety verification of Tower Two plans is delayed or prevented; Engineer A\u0027s professional conduct is now itself an ethical issue; the owner must identify a new strategy before Tower Two construction begins",
  "proeth:createsObligation": [
    "Owner_Identify_Post_Refusal_Strategy",
    "Engineer_A_Faces_Ethical_Censure_For_Obstruction",
    "Engineering_Profession_Address_Obstruction_Norm",
    "Engineer_B_Advise_Owner_On_Available_Options"
  ],
  "proeth:description": "Engineer A\u0027s refusal to consent to the peer review produces the outcome of a blocked review process \u2014 the safety verification mechanism that the owner sought and that Engineer B was prepared to conduct cannot proceed in its intended form. This blockage is an outcome with direct consequences for public safety and project progression.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following Engineer A Refuses Peer Review Consent",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Peer Review Process Blocked"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#CausalChain_4f1ac361",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct consequence of Engineer B\u0027s refusal to proceed covertly, the owner is placed in a position requiring transparency",
  "proeth:causalSequence": [
    {
      "proeth:description": "Owner attempts to initiate covert peer review, creating the ethical conflict",
      "proeth:element": "Owner Retains Engineer B Covertly (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Professional obligation to notify Engineer A is triggered by the covert retention",
      "proeth:element": "Engineer B Notification Obligation Activated (Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B declines the assignment as structured, citing professional ethics obligations",
      "proeth:element": "Engineer B Refuses Covert Review (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Owner loses the covert option and must choose a transparent path forward",
      "proeth:element": "Owner Forced Into Transparency (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Owner reluctantly agrees to notify Engineer A as a precondition for proceeding with peer review",
      "proeth:element": "Owner Consents to Notifying Engineer A (Action 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Refuses Covert Review (Action 3)",
  "proeth:counterfactual": "If Engineer B had agreed to conduct the covert review, the owner would not have been forced into transparency; the outcome depends entirely on Engineer B\u0027s ethical refusal",
  "proeth:effect": "Owner Forced Into Transparency (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s firm refusal to conduct the review without notifying Engineer A",
    "Owner\u0027s continued need for a peer review of Tower Two plans given the safety implications",
    "Absence of any alternative path to obtain a legitimate peer review without transparency"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s refusal combined with the owner\u0027s ongoing need for peer review is sufficient to force the transparency outcome, as no ethical engineer would conduct the covert review"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#CausalChain_81152a73",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following the owner\u0027s consent to notification, Engineer A is formally informed that a peer review of their plans is planned",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B\u0027s refusal eliminates the covert option, compelling owner toward transparency",
      "proeth:element": "Owner Forced Into Transparency (Event 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Owner reluctantly agrees to the notification condition required by Engineer B",
      "proeth:element": "Owner Consents to Notifying Engineer A (Action 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Formal notification is delivered to Engineer A regarding the planned peer review",
      "proeth:element": "Engineer A Notified Of Review (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A responds to notification by objecting to and refusing consent for the peer review",
      "proeth:element": "Engineer A Refuses Peer Review Consent (Action 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s refusal produces the outcome of a blocked peer review process",
      "proeth:element": "Peer Review Process Blocked (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Owner Consents to Notifying Engineer A (Action 4)",
  "proeth:counterfactual": "Without the owner\u0027s consent to notify, Engineer A would not have been formally informed; the notification is entirely contingent on the owner\u0027s agreement to transparency",
  "proeth:effect": "Engineer A Notified Of Review (Event 5)",
  "proeth:necessaryFactors": [
    "Owner\u0027s consent to proceed with notification after Engineer B\u0027s refusal",
    "Engineer B\u0027s prior refusal establishing notification as a precondition",
    "Formal communication mechanism to deliver notification to Engineer A"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Owner",
  "proeth:sufficientFactors": [
    "Owner\u0027s consent combined with Engineer B\u0027s notification requirement is sufficient to produce the formal notification event"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#CausalChain_8376d759",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Significant design errors in Engineer A\u0027s plans are discovered during construction of the first tower",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A develops design plans for both mirror-image towers, embedding significant design errors into the documents",
      "proeth:element": "Engineer A Creates Flawed Plans (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Construction proceeds based on Engineer A\u0027s flawed plans, materializing the design errors in physical form",
      "proeth:element": "Construction Commences on Tower One",
      "proeth:step": 2
    },
    {
      "proeth:description": "Significant design errors are identified during the construction phase of the first tower",
      "proeth:element": "Design Errors Discovered (Event 1)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Mirror-image design relationship causes Tower Two plans to fall under immediate suspicion of containing identical or related errors",
      "proeth:element": "Tower Two Plans Implicated (Event 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Owner responds to discovered errors by seeking a covert peer review of Tower Two plans, initiating the ethics conflict chain",
      "proeth:element": "Owner Retains Engineer B Covertly (Action 2)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Creates Flawed Plans (Action 1)",
  "proeth:counterfactual": "Without Engineer A\u0027s design errors, no significant flaws would have been present to discover; errors would not have emerged during construction",
  "proeth:effect": "Design Errors Discovered (Event 1)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s introduction of significant design errors into the plans",
    "Construction of the first tower proceeding to a stage where errors become detectable",
    "Existence of a review or inspection process during construction"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of flawed design + active construction + observable discrepancy between design and structural reality"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#CausalChain_f93c1509",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Because the two towers are mirror-image designs by the same engineer, the discovery of errors in Tower One directly implicates the Tower Two plans",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A creates flawed plans for both towers using shared mirror-image design methodology",
      "proeth:element": "Engineer A Creates Flawed Plans (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Errors surface during Tower One construction, raising alarm about design quality",
      "proeth:element": "Design Errors Discovered (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Mirror-image design relationship logically extends suspicion of errors to Tower Two plans",
      "proeth:element": "Tower Two Plans Implicated (Event 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Owner acts on Tower Two implication by seeking covert peer review to assess risk before proceeding",
      "proeth:element": "Owner Retains Engineer B Covertly (Action 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Retention of Engineer B for covert review triggers Engineer B\u0027s professional ethical obligations",
      "proeth:element": "Engineer B Notification Obligation Activated (Event 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Design Errors Discovered (Event 1)",
  "proeth:counterfactual": "If the towers were independent designs or by different engineers, discovery of errors in Tower One would not necessarily implicate Tower Two; without the mirror-image relationship, Tower Two plans would not be automatically suspect",
  "proeth:effect": "Tower Two Plans Implicated (Event 2)",
  "proeth:necessaryFactors": [
    "Discovery of significant errors in Tower One plans",
    "Mirror-image design relationship between the two towers",
    "Common authorship by Engineer A establishing shared design logic and methodology"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of discovered errors + mirror-image design + same engineer authorship is sufficient to rationally implicate Tower Two without independent inspection"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#CausalChain_71fc4e7c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon being retained by the owner to conduct a covert peer review, Engineer B\u0027s professional obligation to notify Engineer A is activated",
  "proeth:causalSequence": [
    {
      "proeth:description": "Mirror-image design implication creates urgency for owner to assess Tower Two risk",
      "proeth:element": "Tower Two Plans Implicated (Event 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Owner chooses covert retention of Engineer B, bypassing notification of Engineer A",
      "proeth:element": "Owner Retains Engineer B Covertly (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Covert assignment activates Engineer B\u0027s professional duty to notify Engineer A before proceeding",
      "proeth:element": "Engineer B Notification Obligation Activated (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B declines to proceed with the covert review in fulfillment of professional obligations",
      "proeth:element": "Engineer B Refuses Covert Review (Action 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B\u0027s refusal compels the owner to reconsider the covert approach and move toward transparency",
      "proeth:element": "Owner Forced Into Transparency (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Owner Retains Engineer B Covertly (Action 2)",
  "proeth:counterfactual": "If the owner had retained Engineer B openly and with Engineer A\u0027s knowledge, no notification obligation conflict would have been activated; the obligation arises specifically from the covert framing of the assignment",
  "proeth:effect": "Engineer B Notification Obligation Activated (Event 3)",
  "proeth:necessaryFactors": [
    "Owner\u0027s decision to retain Engineer B specifically under covert conditions",
    "Engineer B\u0027s awareness of professional ethical obligations regarding notification of the engineer of record",
    "The covert nature of the retention being the triggering condition for the ethical conflict"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Owner",
  "proeth:sufficientFactors": [
    "Retention of Engineer B under covert conditions is alone sufficient to activate the notification obligation, as professional codes require Engineer B to inform Engineer A regardless of owner preference"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/15#",
    "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/15#CausalChain_28211b28",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A\u0027s refusal to consent to the peer review produces the outcome of a blocked review process",
  "proeth:causalSequence": [
    {
      "proeth:description": "Original design errors create the foundational condition requiring peer review",
      "proeth:element": "Engineer A Creates Flawed Plans (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Formal notification places Engineer A in the position of deciding whether to consent",
      "proeth:element": "Engineer A Notified Of Review (Event 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A objects to and refuses consent for the peer review of Tower Two plans",
      "proeth:element": "Engineer A Refuses Peer Review Consent (Action 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Refusal produces immediate blockage of the peer review process",
      "proeth:element": "Peer Review Process Blocked (Event 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Owner is forced to choose among alternative strategies to address the blocked review and ongoing safety risk",
      "proeth:element": "Owner Selects Post-Refusal Strategy (Action 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Refuses Peer Review Consent (Action 5)",
  "proeth:counterfactual": "If Engineer A had consented to the peer review, the process would have proceeded; the blockage is entirely attributable to Engineer A\u0027s refusal decision",
  "proeth:effect": "Peer Review Process Blocked (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s active refusal to consent to the peer review",
    "Absence of a legal or regulatory mechanism compelling Engineer A\u0027s cooperation at this stage",
    "The peer review process being structured in a way that requires Engineer A\u0027s consent to proceed"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Engineer A\u0027s refusal alone is sufficient to block the peer review given the consent-dependent structure of the process, absent owner exercising override options"
  ],
  "proeth:withinAgentControl": true
}