{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Contractor_Retains_Engineer_B",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Consult Engineer A before retaining any specialist to ensure alignment with overall design responsibilities",
    "Retain a licensed structural or geotechnical engineer with demonstrated foundation design experience",
    "Assign foundation design back to Engineer A as the engineer of record for the project"
  ],
  "proeth-scenario:characterMotivation": "The contractor likely sought to reduce costs, accelerate the schedule, or maintain control over subcontracted design work by selecting Engineer B independently, possibly without fully appreciating the competence requirements for structural footing design or the ethical implications of bypassing Engineer A\u0027s oversight role.",
  "proeth-scenario:consequencesIfAlternative": [
    "Consulting Engineer A first would have surfaced the competence concern before any commitment was made, likely preventing the ethical conflict entirely and preserving collaborative trust on the project",
    "Hiring a qualified structural engineer would have eliminated the competence risk, satisfied professional standards, and removed any basis for Engineer A\u0027s concern, though it might have cost more or taken longer to procure",
    "Keeping foundation design within Engineer A\u0027s scope would have maintained unified engineering responsibility, reduced coordination risk, and avoided the jurisdictional ambiguity that enabled the ethical problem"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how non-engineer decision-makers can inadvertently create ethical crises by treating engineering specializations as interchangeable, and how procurement decisions made outside professional channels can introduce systemic safety risks that engineers must then navigate.",
  "proeth-scenario:ethicalTension": "Contractual autonomy and business efficiency versus public safety and the professional norm that safety-critical structural work must be assigned to demonstrably qualified engineers. The contractor\u0027s right to manage subcontractors conflicts with the engineering profession\u0027s duty to protect public welfare.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Structural integrity of the industrial facility, public and worker safety, legal liability for all parties, the professional reputations of both engineers, and the integrity of the design/build project delivery model.",
  "proeth:description": "The construction contractor separately retained Engineer B, a chemical engineer, to design structural footings for the industrial facility without apparent consultation with Engineer A. This decision placed a potentially unqualified engineer in a safety-critical structural design role.",
  "proeth:foreseenUnintendedEffects": [
    "Risk of retaining an engineer outside their area of competence",
    "Potential conflict with Engineer A\u0027s oversight role",
    "Structural safety risks from unqualified design work"
  ],
  "proeth:fulfillsObligation": [
    "Exercised contractual authority to retain specialists for specific project tasks"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety paramount in construction decisions",
    "Competence verification before engagement",
    "Coordination with prime design professional"
  ],
  "proeth:hasAgent": "Construction Contractor (Project Owner/Manager)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Project efficiency vs. competence verification",
    "proeth:resolutionReasoning": "Contractor resolved in favor of operational expediency, retaining Engineer B without apparent verification of structural/foundation design competence, creating the ethical conflict that drives the rest of the case"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fill the structural footing design role on an active construction project efficiently and independently of Engineer A",
  "proeth:requiresCapability": [
    "Project management and contractor authority to retain specialists",
    "Basic due diligence in verifying professional qualifications for assigned tasks"
  ],
  "proeth:temporalMarker": "During construction phase",
  "proeth:violatesObligation": [
    "Duty to ensure retained engineers are competent for the specific task assigned",
    "Duty to protect public safety by engaging qualified professionals for safety-critical structural work",
    "Implicit duty to coordinate specialist retention with the prime engineer on a design/build project"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Contractor Retains Engineer B"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Engineer_B_Accepts_Structural_Assignment",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the commission and honestly communicate to the contractor that foundation design falls outside Engineer B\u0027s competence",
    "Accept only a limited advisory role while recommending the contractor also retain a qualified structural engineer for the actual design",
    "Proactively disclose the competence gap to Engineer A and seek collaborative supervision or mentorship before proceeding"
  ],
  "proeth-scenario:characterMotivation": "Engineer B may have been motivated by financial opportunity, professional ambition, overconfidence in the transferability of engineering fundamentals across subdisciplines, or a genuine but mistaken belief that a chemical engineering background was sufficient for structural footing design. Engineer B may also have lacked awareness of the profession\u0027s competence boundary norms.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would have been the ethically correct action: the contractor would have been forced to find a qualified engineer, the safety risk would have been averted, and Engineer B\u0027s professional integrity would have been preserved",
    "A limited advisory role might have been appropriate if clearly scoped, but only if a qualified engineer retained ultimate design responsibility; this alternative would require transparency with all parties",
    "Proactive disclosure to Engineer A would have been an act of professional honesty that could have transformed the situation into a collaborative resolution rather than an adversarial confrontation, potentially allowing the project to proceed safely"
  ],
  "proeth-scenario:decisionSignificance": "Directly illustrates NSPE Code of Ethics provisions requiring engineers to practice only within their competence. Teaches students that holding an engineering license in one discipline does not confer competence across all engineering tasks, and that accepting an assignment outside one\u0027s expertise is itself an ethical violation regardless of outcome.",
  "proeth-scenario:ethicalTension": "Personal economic interest and willingness to take on new challenges versus the foundational engineering ethics principle that practitioners must only perform services within their areas of competence. Engineer B\u0027s self-assessment of capability conflicts with the objective standard of demonstrated training and experience.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Structural failure risk, potential injury or death to facility occupants and workers, Engineer B\u0027s professional license and reputation, legal exposure for Engineer B and the contractor, and the broader credibility of engineering self-regulation.",
  "proeth:description": "Engineer B, holding a chemical engineering degree with no apparent subsequent training in foundation design, accepted a commission specifically and solely to design structural footings for an industrial facility. This decision placed Engineer B in a role outside their established area of competence.",
  "proeth:foreseenUnintendedEffects": [
    "Risk of producing structurally inadequate footing designs due to lack of competence",
    "Potential public safety hazard from unqualified structural design",
    "Exposure to professional liability and disciplinary action"
  ],
  "proeth:fulfillsObligation": [
    "Held a valid professional engineering license satisfying the legal threshold for practice"
  ],
  "proeth:guidedByPrinciple": [
    "Competence as a prerequisite to practice in a specific technical domain",
    "Public safety paramount \u2014 structural footing failures carry severe safety consequences",
    "Professional honesty \u2014 accurately representing one\u0027s qualifications and limitations",
    "Ethics exceed legal minimums \u2014 licensure alone does not confer competence in all engineering subfields"
  ],
  "proeth:hasAgent": "Engineer B (Professional Engineer, Chemical Engineering Background)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional self-interest and legal permissibility vs. ethical competence obligation and public safety",
    "proeth:resolutionReasoning": "Engineer B resolved by accepting the assignment, prioritizing the engagement opportunity and relying on licensure as sufficient justification, contrary to the Code\u0027s requirement that competence in the specific technical field \u2014 not just general PE status \u2014 be the operative standard"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure and perform a professional engineering engagement designing structural footings for the contractor",
  "proeth:requiresCapability": [
    "Formal education or equivalent training in structural engineering or geotechnical/foundation engineering",
    "Experience in designing structural footings for industrial facilities",
    "Knowledge of soil-structure interaction, load calculations, bearing capacity, and applicable structural codes",
    "Ability to exercise sound engineering judgment in structural footing design"
  ],
  "proeth:temporalMarker": "During construction phase, at point of engagement",
  "proeth:violatesObligation": [
    "NSPE Code Section II.2. \u2014 obligation to perform services only in areas of competence",
    "NSPE Code Section II.2.a. \u2014 obligation to undertake assignments only when qualified by education or experience in the specific technical fields involved",
    "Obligation to hold public safety paramount by declining work for which one is not competent",
    "Professional obligation to self-assess and decline engagements outside one\u0027s expertise"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Engineer B Accepts Structural Assignment"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Engineer_A_Investigates_Engineer_B_s_Qualification",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Take no action and assume the contractor vetted Engineer B\u0027s qualifications adequately",
    "Raise concerns informally with colleagues without conducting a formal investigation",
    "Immediately report concerns to the client or authorities without first gathering evidence"
  ],
  "proeth-scenario:characterMotivation": "Engineer A was motivated by professional responsibility for the overall project\u0027s integrity, concern for public safety, and an ethical obligation to verify that all engineering work on the project meets competence standards. As the engineer already engaged on the project, Engineer A recognized a duty to act on warning signs rather than ignore them.",
  "proeth-scenario:consequencesIfAlternative": [
    "Inaction would constitute a failure of professional responsibility; if a structural failure later occurred, Engineer A could face ethical and legal liability for knowingly ignoring warning signs",
    "Informal peer discussion without investigation would not generate the documented factual basis needed to support a credible formal concern, weakening any subsequent escalation",
    "Premature escalation without investigation could constitute an unfair and potentially defamatory accusation against Engineer B, damaging Engineer B\u0027s reputation without evidentiary justification and undermining Engineer A\u0027s own credibility"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical engineering practice requires proactive due diligence, not passive acceptance of others\u0027 credentials. Teaches that when public safety is implicated, engineers have an affirmative obligation to investigate concerns rather than assume competence, even when doing so is socially or professionally uncomfortable.",
  "proeth-scenario:ethicalTension": "The duty to investigate and protect public safety conflicts with potential professional courtesy norms that discourage scrutinizing a peer\u0027s credentials, and with the practical risk that investigating a contractor-retained engineer could damage working relationships or be perceived as territorial overreach.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The factual foundation for all subsequent ethical action depends on this investigation. If Engineer A had not investigated, any later intervention would lack evidentiary basis. The quality and thoroughness of the investigation determines the credibility of Engineer A\u0027s subsequent concerns.",
  "proeth:description": "Engineer A actively investigated Engineer B\u0027s educational background and professional experience to assess whether Engineer B possessed the competence necessary to design structural footings. Engineer A was unable to establish any apparent subsequent training in foundation design beyond Engineer B\u0027s chemical engineering degree.",
  "proeth:foreseenUnintendedEffects": [
    "Findings could create professional conflict with the contractor who retained Engineer B",
    "Investigation results could obligate Engineer A to take disruptive corrective action",
    "Could damage working relationship with Engineer B and the contractor"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to form an objective, evidence-based judgment before reporting concerns about a colleague",
    "Obligation to hold public safety paramount by proactively assessing whether structural design work is being performed by a competent engineer",
    "Obligation to act on knowledge of potential Code violations by another engineer"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety paramount \u2014 structural footing competence directly affects facility safety",
    "Objectivity and evidence-based professional judgment before making allegations",
    "Responsibility to the profession to uphold competence standards",
    "Due diligence before escalation"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer, Prime Design Engineer on Project)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Thoroughness of qualification assessment vs. urgency of intervening in ongoing potentially unsafe structural design",
    "proeth:resolutionReasoning": "Engineer A resolved by conducting the investigation first to establish an objective basis, consistent with the Discussion\u0027s framing that Engineer A must have \u0027an objective basis to determine whether Engineer B has sufficient education, experience and training\u0027 before proceeding to further action"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Establish an objective, evidence-based assessment of Engineer B\u0027s qualifications for structural footing design before deciding how to act",
  "proeth:requiresCapability": [
    "Knowledge of what educational background and experience structural footing design requires",
    "Ability to review and evaluate another engineer\u0027s credentials and professional history",
    "Professional judgment to assess competence gaps in a specific technical domain"
  ],
  "proeth:temporalMarker": "During construction phase, after learning of Engineer B\u0027s retention",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Investigates Engineer B\u0027s Qualifications"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Engineer_A_Reports_Concerns_to_Contractor",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Bypass the contractor and report concerns directly to the client or regulatory authorities immediately",
    "Document concerns in writing but take no further action, leaving the decision entirely to the contractor",
    "Attempt to resolve the concern privately with Engineer B before involving the contractor at all"
  ],
  "proeth-scenario:characterMotivation": "Having established a factual basis for concern through investigation, Engineer A was motivated to fulfill the ethical obligation to report the risk to a party with direct authority to remedy it. Reporting to the contractor represented the most immediate and least disruptive escalation path, consistent with professional norms of attempting resolution at the lowest effective level first.",
  "proeth-scenario:consequencesIfAlternative": [
    "Bypassing the contractor might be justified in extreme urgency but would likely damage the working relationship prematurely and could be seen as disproportionate before lower-level resolution was attempted",
    "Documenting without acting would create a paper trail but would not discharge Engineer A\u0027s affirmative duty to protect public safety; passive documentation alone is ethically insufficient when a known risk exists",
    "Going directly to Engineer B first is actually the sequence recommended in the Discussion section as the next step after the contractor report, suggesting this alternative is not wrong but rather represents a different ordering of ethically appropriate actions"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the principle that engineers must report safety-relevant concerns to parties with the authority and ability to act, even when doing so creates interpersonal or contractual friction. Also demonstrates the importance of the chain of escalation: reporting to the contractor first before bypassing to higher authorities reflects proportionate and procedurally appropriate ethics practice.",
  "proeth-scenario:ethicalTension": "The duty to report a safety concern to protect the public conflicts with the risk of damaging the professional relationship with the contractor, the possibility of being seen as obstructionist on the project, and uncertainty about whether Engineer A\u0027s assessment of Engineer B\u0027s competence is definitive enough to justify formal concern.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The contractor\u0027s response to this report will determine whether the problem is resolved quickly or escalates further. If the contractor dismisses the concern, Engineer A faces the harder ethical choices ahead. The report also creates a documented record that Engineer A fulfilled initial notification obligations.",
  "proeth:description": "After investigating Engineer B\u0027s qualifications and finding no apparent foundation design training, Engineer A reported his competence concerns about Engineer B to the construction contractor. This was Engineer A\u0027s first formal escalation of the issue to a party with authority over the project.",
  "proeth:foreseenUnintendedEffects": [
    "Could damage Engineer A\u0027s working relationship with the contractor",
    "Contractor may dismiss concerns and allow Engineer B to continue",
    "Could create project delays or disputes if contractor acts on the concerns",
    "Reporting to contractor alone may prove insufficient if contractor does not act"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to report known or reasonably suspected competence deficiencies that endanger public safety",
    "Obligation to notify the client/contractor of concerns affecting the project",
    "Obligation to take action when aware of a potential Code violation by another engineer",
    "Obligation to hold public safety paramount in all professional decisions"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety paramount \u2014 structural footing failures can cause serious harm",
    "Professional responsibility to act on observed competence concerns",
    "Transparency with the client about material project risks",
    "Duty to the profession to uphold competence standards"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer, Prime Design Engineer on Project)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public safety and ethical duty to report vs. client relationship preservation and project continuity",
    "proeth:resolutionReasoning": "Engineer A resolved in favor of reporting to the contractor, consistent with the Code obligation to act and with the Discussion\u0027s guidance that Engineer A must make concerns known to the client; the contractor\u0027s authority over Engineer B made this the logical first point of escalation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Alert the contractor \u2014 who retained Engineer B and holds authority over the project \u2014 to the competence concerns, enabling the contractor to take corrective action",
  "proeth:requiresCapability": [
    "Professional communication skills to articulate competence concerns clearly and objectively",
    "Knowledge of NSPE Code provisions to ground the concerns in ethical obligations",
    "Judgment about appropriate escalation pathways within a design/build project structure"
  ],
  "proeth:temporalMarker": "During construction phase, after completing qualification investigation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Reports Concerns to Contractor"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Engineer_A_Confronts_Engineer_B_Directly",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Skip direct confrontation with Engineer B and escalate immediately to the client and regulatory authorities",
    "Confront Engineer B informally and without a clear recommendation to withdraw, leaving the outcome ambiguous",
    "Request a three-way meeting with Engineer B and the contractor simultaneously rather than a bilateral confrontation"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by the professional obligation to give Engineer B a direct opportunity to recognize and correct the ethical problem before institutional escalation occurs. This peer-level intervention respects Engineer B\u0027s professional agency and dignity while fulfilling Engineer A\u0027s duty to communicate the concern clearly and formally to the engineer most directly responsible.",
  "proeth-scenario:consequencesIfAlternative": [
    "Skipping direct confrontation would deny Engineer B the opportunity to self-correct and could be criticized as procedurally unfair; it might also weaken Engineer A\u0027s position with authorities who expect evidence that lower-level resolution was attempted",
    "An informal confrontation without a clear withdrawal recommendation would fail to communicate the seriousness of the concern and would not create the clear decision point needed to trigger Engineer B\u0027s ethical obligation to respond",
    "A three-way meeting might diffuse personal tension but could also allow the contractor to deflect or mediate in ways that obscure the core professional ethics issue, which is fundamentally between the two engineers as licensed professionals"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that ethical engineering practice sometimes requires uncomfortable direct peer confrontation rather than routing all concerns through organizational hierarchies. Demonstrates the principle that the engineer closest to the problem has a first-line responsibility to address it, and that giving a peer the opportunity to self-correct is both ethically respectful and procedurally important before escalating to authorities.",
  "proeth-scenario:ethicalTension": "The duty to confront a peer about a serious competence concern conflicts with professional courtesy norms, the discomfort of direct confrontation, and the risk that Engineer B may react defensively or that the confrontation may permanently damage a professional relationship. There is also tension between respecting Engineer B\u0027s autonomy and the imperative to protect public safety.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "This confrontation is the pivotal moment of the narrative. Engineer B\u0027s response will determine whether the ethical crisis is resolved through professional self-regulation or must escalate to institutional intervention. Engineer A\u0027s ability to communicate concerns clearly, professionally, and with documented evidence is critical to the legitimacy of any subsequent action.",
  "proeth:description": "As a prospective required action identified in the Discussion, Engineer A must directly confront Engineer B to communicate competence concerns and formally recommend that Engineer B withdraw from the structural footing design assignment. This is a peer-level professional intervention prior to further escalation.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer B may refuse to withdraw, requiring further escalation",
    "Confrontation may create professional animosity between Engineer A and Engineer B",
    "If Engineer B withdraws, project may face delays in finding a qualified replacement",
    "Direct confrontation creates a clear record of Engineer A having fulfilled the ethical obligation to notify Engineer B"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to directly notify the engineer whose conduct raises ethical concerns before escalating to third parties",
    "Obligation to give Engineer B the opportunity to self-correct and withdraw voluntarily",
    "Obligation to act affirmatively to protect public safety from potentially incompetent structural design",
    "Obligation to uphold professional standards within the engineering community"
  ],
  "proeth:guidedByPrinciple": [
    "Professional responsibility to intervene when a colleague\u0027s work poses public safety risks",
    "Procedural fairness \u2014 Engineer B deserves direct notification before external escalation",
    "Public safety paramount \u2014 structural footing design incompetence can cause serious harm",
    "Duty to the profession to maintain competence standards"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer, Prime Design Engineer on Project)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Peer professional courtesy and giving Engineer B a chance to self-correct vs. urgency of stopping potentially unsafe structural design work",
    "proeth:resolutionReasoning": "The Discussion resolves this by making direct confrontation a mandatory ethical step \u2014 Engineer A must confront Engineer B first, accepting the time cost of this process in exchange for procedural fairness and the possibility of voluntary resolution before escalation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Give Engineer B the opportunity to voluntarily recognize the competence deficiency and withdraw from the project, resolving the ethical problem without requiring escalation to authorities",
  "proeth:requiresCapability": [
    "Professional communication and interpersonal skills for a difficult peer confrontation",
    "Ability to articulate specific competence deficiencies with reference to Code obligations",
    "Professional courage to confront a peer about ethical violations"
  ],
  "proeth:temporalMarker": "Prospective \u2014 required next step identified in the Discussion section",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Confronts Engineer B Directly"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Engineer_B_Decides_Whether_to_Withdraw",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Withdraw voluntarily and immediately upon Engineer A\u0027s recommendation",
    "Refuse to withdraw but propose bringing in a qualified structural engineer as a supervisor or co-designer",
    "Refuse to withdraw and challenge Engineer A\u0027s authority to make such a recommendation, escalating the dispute to the contractor or client"
  ],
  "proeth-scenario:characterMotivation": "Engineer B must weigh professional integrity, the ethics code\u0027s competence requirements, and the potential consequences of continuing against the financial and reputational costs of withdrawing from a commission already accepted. The motivation to withdraw would stem from recognizing the validity of Engineer A\u0027s concern; the motivation to refuse would stem from defensiveness, financial interest, or genuine disagreement about the competence assessment.",
  "proeth-scenario:consequencesIfAlternative": [
    "Voluntary withdrawal is the ethically correct and professionally honorable response; it resolves the crisis, demonstrates integrity, and limits reputational damage compared to forced removal through regulatory action",
    "Proposing co-design with a qualified engineer is a potentially acceptable middle path if the qualified engineer assumes genuine design authority, but only if all parties including Engineer A agree it adequately addresses the competence gap",
    "Challenging Engineer A\u0027s authority would escalate the conflict, likely result in regulatory involvement, and place Engineer B\u0027s license at greater risk while doing nothing to resolve the underlying safety concern"
  ],
  "proeth-scenario:decisionSignificance": "This decision point illustrates the concept of ethical agency and professional accountability: the ethics system functions most efficiently when engineers self-regulate in response to legitimate peer concern. It also demonstrates that the consequences of an ethical decision ramify outward, as Engineer B\u0027s choice determines the scope and intensity of subsequent institutional involvement.",
  "proeth-scenario:ethicalTension": "Engineer B\u0027s financial interest and professional pride in having accepted the commission conflict directly with the ethical obligation to practice only within areas of competence and to prioritize public safety over personal gain. There is also a tension between deference to a peer\u0027s judgment and Engineer B\u0027s own self-assessment of capability.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Voluntary withdrawal would resolve the safety risk with minimal institutional disruption and preserve Engineer B\u0027s professional reputation to the greatest extent possible. Refusal forces Engineer A into a more adversarial and publicly consequential escalation path, increases regulatory scrutiny of Engineer B, and leaves the structural safety risk unresolved.",
  "proeth:description": "Following Engineer A\u0027s direct confrontation and recommendation, Engineer B faces a prospective decision about whether to voluntarily withdraw from the structural footing design assignment. Acquiescence would resolve the ethical problem; refusal would trigger Engineer A\u0027s obligation to escalate to the client and authorities.",
  "proeth:foreseenUnintendedEffects": [
    "Acquiescence: project delay while a qualified structural engineer is found; reputational impact of withdrawing",
    "Refusal: triggers Engineer A\u0027s escalation to client and authorities; potential disciplinary action; continued public safety risk from unqualified structural design"
  ],
  "proeth:fulfillsObligation": [
    "If withdrawing: fulfills NSPE Code Section II.2. and II.2.a. obligations to perform only within areas of competence",
    "If withdrawing: fulfills obligation to hold public safety above personal or financial interest"
  ],
  "proeth:guidedByPrinciple": [
    "Competence as a prerequisite to practice in a specific technical domain",
    "Public safety paramount over professional self-interest",
    "Professional integrity \u2014 willingness to self-correct when confronted with valid concerns",
    "Ethics exceed legal minimums \u2014 PE licensure does not confer competence in all subfields"
  ],
  "proeth:hasAgent": "Engineer B (Professional Engineer, Chemical Engineering Background)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Financial self-interest and contractual commitment vs. ethical obligation to withdraw from work outside one\u0027s competence",
    "proeth:resolutionReasoning": "The Code and Discussion are unambiguous that Engineer B should withdraw; the Discussion states that Engineer A should recommend withdrawal, implying withdrawal is the ethically correct choice for Engineer B; refusal to withdraw would represent a continued and now fully knowing violation of the Code"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "If acquiescing: withdraw from an assignment outside one\u0027s competence, preserving professional integrity and public safety. If refusing: continue the engagement, maintaining the financial and professional relationship with the contractor despite the competence concern",
  "proeth:requiresCapability": [
    "Self-awareness and honest self-assessment of competence limitations",
    "Professional integrity to prioritize ethical obligations over financial interests",
    "Willingness to communicate withdrawal to the contractor and manage the professional consequences"
  ],
  "proeth:temporalMarker": "Prospective \u2014 contingent on Engineer A\u0027s direct confrontation occurring",
  "proeth:violatesObligation": [
    "If refusing: continues violation of NSPE Code Section II.2. and II.2.a.",
    "If refusing: violates obligation to hold public safety paramount",
    "If refusing: disregards a direct, Code-grounded recommendation from a peer engineer"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Engineer B Decides Whether to Withdraw"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Action_Engineer_A_Escalates_to_Client_and_Authorities",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Withdraw from the project personally without escalating to the client or authorities, thereby removing Engineer A\u0027s own liability exposure",
    "Escalate to the client only, without involving regulatory or professional authorities, and allow the client to make the final decision",
    "Issue a formal written warning to Engineer B and the contractor but take no further action, treating documentation as sufficient discharge of duty"
  ],
  "proeth-scenario:characterMotivation": "If Engineer B refuses to withdraw, Engineer A is motivated by the paramount obligation to protect public safety, which supersedes professional courtesy, project continuity, and personal comfort. At this stage, Engineer A has exhausted peer-level resolution options and must invoke institutional mechanisms to prevent a foreseeable safety risk from materializing.",
  "proeth-scenario:consequencesIfAlternative": [
    "Withdrawing without escalating would protect Engineer A from direct project liability but would abandon the public safety obligation; if a structural failure later occurred, Engineer A\u0027s knowledge of the risk and failure to report it fully could still result in ethical and legal consequences",
    "Escalating to the client only might be sufficient if the client has both the authority and the technical sophistication to act appropriately, but omitting regulatory authorities leaves the profession\u0027s oversight function unfulfilled and may be inadequate if the client also fails to act",
    "Documentation without full escalation creates a record of awareness but does not discharge the affirmative duty to act; passive documentation in the face of a known, unresolved safety risk is ethically insufficient and could be characterized as a knowing failure to prevent foreseeable harm"
  ],
  "proeth-scenario:decisionSignificance": "Represents the endpoint of the ethical escalation ladder and illustrates that when self-regulation fails, engineers have an obligation to engage external oversight mechanisms. Teaches that protecting public safety is a non-negotiable duty that ultimately overrides interpersonal and organizational considerations, and that the engineering profession\u0027s credibility depends on engineers being willing to make this difficult call.",
  "proeth-scenario:ethicalTension": "The duty to protect the public through institutional escalation conflicts with loyalty to the project and the contractor relationship, the potential harm to Engineer B\u0027s career and reputation from regulatory involvement, uncertainty about whether Engineer A\u0027s competence assessment will be validated by authorities, and the personal and professional costs to Engineer A of becoming a formal complainant.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Public and worker safety at the facility, the structural integrity of the building, Engineer A\u0027s own ethical and potentially legal liability if a failure occurs after a known concern was not fully escalated, Engineer B\u0027s professional license, the contractor\u0027s project and legal exposure, and the broader integrity of professional engineering self-regulation as a public safety mechanism.",
  "proeth:description": "If Engineer B refuses to withdraw, Engineer A is obligated to escalate the competence concern beyond the contractor to the client and to relevant professional or regulatory authorities. This prospective action represents a formal, institutional-level escalation of the ethical violation.",
  "proeth:foreseenUnintendedEffects": [
    "Significant disruption to the design/build project timeline and contractor relationships",
    "Potential disciplinary proceedings against Engineer B",
    "Reputational consequences for Engineer B",
    "Engineer A may face professional friction for escalating against the contractor\u0027s retained engineer",
    "Regulatory involvement may expose additional project issues to scrutiny"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code obligation to bring known ethical violations and competence concerns to the attention of appropriate authorities",
    "Obligation to hold public safety paramount above project continuity and client relationships",
    "Obligation to take all available steps to prevent unqualified structural design from proceeding",
    "Obligation to act when direct peer confrontation has failed to resolve the ethical problem"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety paramount \u2014 structural footing failures can cause catastrophic harm",
    "Institutional accountability \u2014 professional and regulatory bodies exist to enforce competence standards",
    "Duty to the profession to maintain and enforce competence standards through available channels",
    "Proportionality \u2014 escalation to authorities is appropriate when peer-level intervention has failed"
  ],
  "proeth:hasAgent": "Engineer A (Professional Engineer, Prime Design Engineer on Project)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public safety and Code compliance vs. project continuity, client loyalty, and professional relationships",
    "proeth:resolutionReasoning": "The Discussion resolves this explicitly \u2014 if Engineer B refuses to withdraw, escalation to the client and authorities is not optional but obligatory; the public safety imperative and Code obligations override all competing relationship and project continuity considerations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Trigger institutional intervention \u2014 from the client and/or regulatory/professional authorities \u2014 to remove Engineer B from the structural footing design role and protect public safety through channels with enforcement authority",
  "proeth:requiresCapability": [
    "Knowledge of appropriate regulatory and professional authority channels for reporting competence violations",
    "Ability to document and present the competence concern clearly and objectively to authorities",
    "Professional courage to escalate against a contractor-retained engineer despite relationship risks"
  ],
  "proeth:temporalMarker": "Prospective \u2014 contingent on Engineer B refusing to withdraw after direct confrontation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Escalates to Client and Authorities"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Event_Engineer_B_s_Lack_of_Qualifications_Confirmed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what threshold of evidence should Engineer A feel obligated to act \u2014 suspicion, reasonable concern, or confirmed incompetence?",
    "Does Engineer A\u0027s obligation to report change if Engineer B\u0027s structural footing designs are later reviewed by a qualified structural engineer?",
    "How does the concept of \u0027practicing in areas of competence\u0027 apply differently to a sole practitioner versus an engineer working within a multidisciplinary team?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences alarm, professional discomfort, and a sense of obligation to act; Engineer B may be unaware of Engineer A\u0027s investigation; the contractor may be indifferent or unaware of the competency gap; future facility users face unrecognized risk",
  "proeth-scenario:ethicalImplications": "Reveals the tension between professional collegiality (not wanting to undermine a fellow engineer) and public safety obligations; demonstrates that competence is not self-certified but must be verifiable; raises the question of whether licensing alone is sufficient evidence of competence for a specialized task",
  "proeth-scenario:learningMoment": "The moment a professional engineer gains knowledge of a competency risk is the moment their ethical obligations crystallize; ignorance is no longer available as a defense, and the engineer must act. This illustrates NSPE Code obligations regarding public safety and peer competence.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Unaware that the structural foundation of their facility may be designed by an unqualified engineer",
    "contractor": "Exposed to legal and safety liability for retaining an unqualified engineer for a critical structural task",
    "engineer_a": "Now possesses knowledge that triggers affirmative professional duties; inaction after this point would itself constitute an ethical violation",
    "engineer_b": "Professional reputation and license are at risk if the incompetent assignment proceeds; potential liability for structural failures",
    "public": "Workers and future occupants face potential structural safety hazard from improperly designed footings"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Competence_Verification_Constraint",
    "PeerOversight_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/110#Action_Engineer_A_Investigates_Engineer_B_s_Qualification",
  "proeth:causesStateChange": "Engineer B\u0027s assignment transitions from a potentially questionable arrangement to a confirmed competency risk; Engineer A\u0027s professional duty to act is now triggered; the project\u0027s structural integrity is placed in question",
  "proeth:createsObligation": [
    "Engineer_A_Must_Report_Concerns",
    "Contractor_Must_Be_Notified",
    "Potential_Escalation_Obligation_If_Unresolved"
  ],
  "proeth:description": "Engineer A\u0027s investigation yields a finding: no evidence of training or competency in foundation design exists in Engineer B\u0027s background, despite Engineer B being a chemical engineer assigned to design structural footings. This is the evidentiary outcome of Engineer A\u0027s investigative action.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A Investigates Engineer B\u0027s Qualifications; before Engineer A Reports Concerns to Contractor",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer B\u0027s Lack of Qualifications Confirmed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Event_Contractor_Receives_Safety_Concern",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "If the contractor dismisses Engineer A\u0027s concerns and insists Engineer B continue, what are Engineer A\u0027s remaining options and obligations?",
    "How should Engineer A document this communication, and why does documentation matter in engineering ethics cases?",
    "Does the contractor\u0027s response (or lack thereof) affect Engineer A\u0027s professional liability for subsequent structural failures?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Contractor may feel defensive, annoyed at the complication, or genuinely concerned; Engineer A may feel relief at having fulfilled an initial duty but anxiety about whether the contractor will act; Engineer B remains unaware of the formal concern being raised",
  "proeth-scenario:ethicalImplications": "Illustrates the limits of hierarchical reporting when the authority figure (contractor) has a financial interest in maintaining the status quo; raises the question of when an engineer\u0027s duty to the public supersedes their duty to their client or employer",
  "proeth-scenario:learningMoment": "Reporting concerns through the chain of authority is a necessary but not always sufficient step; students should understand that the ethical obligation does not end with reporting \u2014 it continues until the safety concern is resolved or escalated appropriately",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Remains unaware but is one step closer to being protected if the contractor responds appropriately",
    "contractor": "Now legally and ethically accountable for the Engineer B arrangement; inaction after this point is a knowing choice with compounded liability",
    "engineer_a": "Has fulfilled an initial reporting obligation; now enters a waiting period where contractor\u0027s response will determine next steps",
    "engineer_b": "Unaware but increasingly at professional risk as the concern is now formally documented",
    "public": "Safety interests are being advocated for through proper channels; outcome depends on contractor\u0027s response"
  },
  "proeth:activatesConstraint": [
    "Contractor_Duty_To_Respond_Constraint",
    "PublicSafety_Paramount_Constraint",
    "OrganizationalKnowledge_Liability_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/110#Action_Engineer_A_Reports_Concerns_to_Contractor",
  "proeth:causesStateChange": "The contractor can no longer claim ignorance of the competency risk; organizational liability for the arrangement is now established; Engineer A\u0027s next obligation depends on how the contractor responds",
  "proeth:createsObligation": [
    "Contractor_Must_Investigate_Or_Act",
    "Contractor_Accountability_For_Inaction",
    "Engineer_A_Escalation_Obligation_If_Contractor_Fails_To_Act"
  ],
  "proeth:description": "The contractor becomes formally aware of Engineer A\u0027s concerns about Engineer B\u0027s qualifications for foundation design, creating a documented moment of organizational knowledge about the potential competency risk. This is the outcome of Engineer A\u0027s reporting action.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A Reports Concerns to Contractor; before Engineer A Confronts Engineer B Directly",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Contractor Receives Safety Concern"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Event_Project_Construction_Commences",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does a design/build arrangement differ from traditional design-bid-build in terms of engineer authority and oversight?",
    "What professional obligations does Engineer A assume at project commencement that may not be explicitly stated in the contract?",
    "How might the contractor\u0027s dual role as both client and construction manager create conflicts of interest later in the project?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences professional confidence and responsibility; contractor is focused on project delivery and cost management; client anticipates successful facility completion",
  "proeth-scenario:ethicalImplications": "Reveals how project delivery structures can obscure or complicate lines of professional responsibility; establishes the tension between contractual authority (contractor) and professional authority (Engineer A) that will intensify when Engineer B is introduced",
  "proeth-scenario:learningMoment": "Design/build arrangements create complex overlapping authority structures; students should understand that the project delivery method shapes who has oversight authority and how professional responsibilities are distributed from the outset",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Entrusts safety and quality of facility to the design/build team",
    "contractor": "Gains authority to manage project execution, including future decisions about subcontracting engineering work",
    "engineer_a": "Assumes professional obligations as prime design engineer, including oversight duties that will later be tested",
    "public": "Future occupants and neighbors of the industrial facility have latent safety interests now being shaped by project structure"
  },
  "proeth:activatesConstraint": [
    "ProfessionalCompetence_Constraint",
    "PrimacyOfPublicSafety_Constraint",
    "Scope_Of_Engagement_Constraint"
  ],
  "proeth:causesStateChange": "Project enters active construction phase; Engineer A assumes prime design engineering role with associated professional responsibilities; contractor assumes project management authority",
  "proeth:createsObligation": [
    "Engineer_A_Oversight_Obligation",
    "Contractor_Coordination_Obligation",
    "Design_Integrity_Obligation"
  ],
  "proeth:description": "The design/build industrial facility project begins, establishing the collaborative working relationship between Engineer A and the construction contractor. This initiates the professional context within which all subsequent events unfold.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Project outset, before contractor retains Engineer B",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Project Construction Commences"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Event_Engineer_B_Confrontation_Outcome_Determined",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How should Engineer A frame the confrontation with Engineer B to be both professionally respectful and unambiguous about the safety concern?",
    "If Engineer B argues that their professional license entitles them to practice in any engineering domain, how should Engineer A respond?",
    "What professional and legal consequences might Engineer B face if they refuse to withdraw and a structural failure later occurs?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer B may feel professionally humiliated, defensive, or \u2014 if self-aware \u2014 genuinely concerned about their own overreach; Engineer A experiences tension between professional collegiality and safety duty; both engineers face reputational stakes",
  "proeth-scenario:ethicalImplications": "Tests the limits of professional autonomy versus community accountability; reveals that a professional license is not a blank check to practice outside one\u0027s competence; highlights the ethical courage required to challenge a peer when public safety is at stake",
  "proeth-scenario:learningMoment": "Peer-to-peer professional accountability is a legitimate and sometimes necessary mechanism in engineering ethics; students should understand that confronting a peer about competency is not a personal attack but a professional obligation rooted in public safety",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Unaware but protected or endangered depending on Engineer B\u0027s response",
    "contractor": "Outcome of confrontation will determine whether contractor is drawn back into the resolution process",
    "engineer_a": "Professional integrity is on the line; how Engineer A handles the confrontation will define their ethical standing in this case",
    "engineer_b": "Career-defining moment: withdrawal preserves professional integrity; continued resistance compounds ethical and legal exposure",
    "public": "Structural safety outcome is directly shaped by this confrontation result"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "PeerAccountability_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/110#Action_Engineer_A_Confronts_Engineer_B_Directly",
  "proeth:causesStateChange": "The confrontation bifurcates the narrative: Engineer B\u0027s response either resolves the competency risk (withdrawal) or confirms the need for immediate escalation beyond the contractor and Engineer B",
  "proeth:createsObligation": [
    "If Engineer B withdraws: Obligation_To_Confirm_Withdrawal_And_Monitor",
    "If Engineer B refuses: Obligation_To_Escalate_To_Client_And_Authorities_Immediately"
  ],
  "proeth:description": "Following Engineer A\u0027s direct confrontation of Engineer B, an outcome is produced: Engineer B either acknowledges the competency concern and agrees to withdraw, or resists and continues with the assignment. This outcome state determines the trajectory of subsequent escalation.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A Confronts Engineer B Directly; concurrent with Engineer B Decides Whether to Withdraw",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer B Confrontation Outcome Determined"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Event_Escalation_Necessity_Triggered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what point does Engineer A\u0027s failure to escalate externally become an independent ethical violation, separate from Engineer B\u0027s original misconduct?",
    "How should Engineer A weigh the potential harm to the project (delays, costs, damaged relationships) against the public safety obligation to escalate?",
    "What protections, if any, exist for Engineer A if the contractor retaliates for escalating to the client or licensing board?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A faces profound professional stress \u2014 escalating externally risks the project, the contractor relationship, and Engineer A\u0027s own position; Engineer B faces potential licensing consequences; the contractor faces legal exposure; all parties are in high-stakes territory",
  "proeth-scenario:ethicalImplications": "Reveals the ultimate test of professional integrity: acting in the public interest when it is personally costly; demonstrates that engineering codes of ethics are not aspirational guidelines but binding obligations with real consequences for non-compliance; highlights the systemic function of licensing boards as backstop safety mechanisms when project hierarchies fail",
  "proeth-scenario:learningMoment": "When internal channels fail, engineers have an affirmative duty to escalate externally \u2014 this is not optional whistleblowing but a mandatory professional obligation under codes of ethics. Students should understand that public safety obligations supersede loyalty to clients, employers, or colleagues.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Will be informed of a safety risk they were unaware of; may lose confidence in the project team",
    "contractor": "Faces client notification, potential project disruption, and legal liability for knowingly employing an unqualified engineer after being warned",
    "engineer_a": "Must choose between self-preservation (staying silent) and professional integrity (escalating); either choice carries significant personal and professional consequences",
    "engineer_b": "Faces potential licensing board investigation and professional discipline",
    "licensing_board": "Receives a formal competency complaint requiring investigation",
    "public": "Safety interests are now being escalated to authorities with power to intervene; outcome depends on regulatory responsiveness"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "MandatoryEscalation_Constraint",
    "LicensingBoard_Reporting_Constraint",
    "ClientNotification_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/110#Action_Engineer_B_Decides_Whether_to_Withdraw__refusal_ou",
  "proeth:causesStateChange": "The situation escalates from an internal project dispute to a public safety emergency requiring external intervention; Engineer A\u0027s professional obligations now extend beyond the project hierarchy to external authorities; the project\u0027s continuation under current conditions becomes ethically untenable",
  "proeth:createsObligation": [
    "Engineer_A_Must_Notify_Client_Immediately",
    "Engineer_A_Must_Report_To_Licensing_Board_Or_Relevant_Authority",
    "Engineer_A_Must_Consider_Project_Withdrawal_If_Safety_Unresolved"
  ],
  "proeth:description": "If Engineer B refuses to withdraw and the contractor fails to act, the conditions for mandatory escalation to the client and relevant authorities are automatically met, transforming Engineer A\u0027s optional escalation into a binding professional obligation. This is an automatic trigger event produced by the combined failure of prior resolution attempts.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "After Engineer B Decides Whether to Withdraw (negative outcome) and Contractor inaction confirmed; before Engineer A Escalates to Client and Authorities",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Escalation Necessity Triggered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#Event_Prior_BER_Precedents_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the existence of prior BER precedent change the moral weight of Engineer A\u0027s obligations \u2014 does it make them clearer, heavier, or both?",
    "Should engineering ethics precedents be binding in the way legal precedents are, or should each case be analyzed fresh on its own facts?",
    "What do the three prior cases (71-2, 78-5, 85-3) collectively reveal about how the profession\u0027s understanding of peer oversight obligations has evolved over 14 years?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral for immediate parties (they are unaware of the precedent analysis); significant for students and practitioners who recognize that their obligations are shaped by decades of accumulated professional judgment",
  "proeth-scenario:ethicalImplications": "Reveals that professional ethics is a living tradition, not a static rulebook; demonstrates the value of institutional memory in maintaining consistent standards; raises questions about the authority and legitimacy of professional self-regulation through bodies like the BER",
  "proeth-scenario:learningMoment": "Engineering ethics is not ad hoc \u2014 it is grounded in a body of precedent that provides guidance and consistency; students should learn to research prior BER cases when facing ethical dilemmas, and understand that ignorance of established precedent is not a defense",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Benefits from clear precedent-based guidance on how to proceed; cannot claim uncertainty about obligations",
    "engineer_b": "Subject to well-established standards of competency that have been consistently enforced",
    "engineering_profession": "Demonstrates institutional memory and consistency in ethical standard-setting",
    "students": "Gain access to a rich body of case law for understanding how abstract ethical principles apply in concrete situations"
  },
  "proeth:activatesConstraint": [
    "Precedent_Consistency_Constraint",
    "EthicalFramework_Constraint"
  ],
  "proeth:causesStateChange": "The current case is situated within an established ethical tradition; Engineer A\u0027s obligations are not novel but are grounded in decades of precedent; the BER\u0027s analysis is constrained to be consistent with prior rulings",
  "proeth:createsObligation": [
    "Engineer_A_Must_Act_Consistent_With_Established_Precedent",
    "BER_Must_Apply_Precedent_Consistently"
  ],
  "proeth:description": "A historical sequence of prior Board of Ethical Review cases (71-2, 78-5, and 85-3) spanning 1971 to 1985 exists as established precedent, shaping the ethical framework applied to Engineer A\u0027s current obligations. These precedents are exogenous facts that constrain the analysis.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Historical; 1971 through 1985, prior to the current case",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Prior BER Precedents Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_f56a352d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The construction contractor separately retained Engineer B, a chemical engineer, to design structural [foundations], establishing the precondition for the qualification gap that Engineer A\u0027s investigation would later confirm",
  "proeth:causalSequence": [
    {
      "proeth:description": "Contractor hires Engineer B, a chemical engineer, for structural foundation design without discipline-specific vetting",
      "proeth:element": "Contractor Retains Engineer B",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B accepts the assignment despite lacking apparent training or competency in foundation design",
      "proeth:element": "Engineer B Accepts Structural Assignment",
      "proeth:step": 2
    },
    {
      "proeth:description": "The design/build project begins with Engineer B in a structural role, embedding the qualification risk into the project structure",
      "proeth:element": "Project Construction Commences",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A, recognizing a potential competency mismatch, actively investigates Engineer B\u0027s background",
      "proeth:element": "Engineer A Investigates Engineer B\u0027s Qualifications",
      "proeth:step": 4
    },
    {
      "proeth:description": "Investigation yields no evidence of foundation design training or competency, confirming the qualification gap",
      "proeth:element": "Engineer B\u0027s Lack of Qualifications Confirmed",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Contractor Retains Engineer B",
  "proeth:counterfactual": "Had the contractor retained a licensed structural or geotechnical engineer, no qualification gap would have existed and Engineer A\u0027s investigation would have found no concern",
  "proeth:effect": "Engineer B\u0027s Lack of Qualifications Confirmed",
  "proeth:necessaryFactors": [
    "Contractor\u0027s decision to hire outside the scope of Engineer B\u0027s demonstrated competency",
    "Engineer B holding only a chemical engineering degree with no foundation design training",
    "Absence of contractor vetting process for discipline-specific qualifications"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Construction Contractor",
  "proeth:sufficientFactors": [
    "Combination of contractor\u0027s unilateral hiring decision + Engineer B\u0027s mismatched credentials + lack of pre-engagement qualification screening"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_ede4d325",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B, holding a chemical engineering degree with no apparent subsequent training in foundation design, accepts the structural assignment, directly producing the competency mismatch that Engineer A\u0027s investigation confirms",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B voluntarily accepts foundation design work without possessing requisite competency",
      "proeth:element": "Engineer B Accepts Structural Assignment",
      "proeth:step": 1
    },
    {
      "proeth:description": "Project proceeds with Engineer B embedded in a structural role, obscuring the competency gap until scrutinized",
      "proeth:element": "Project Construction Commences",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A exercises professional diligence and investigates Engineer B\u0027s credentials",
      "proeth:element": "Engineer A Investigates Engineer B\u0027s Qualifications",
      "proeth:step": 3
    },
    {
      "proeth:description": "Investigation confirms no evidence of foundation design competency",
      "proeth:element": "Engineer B\u0027s Lack of Qualifications Confirmed",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A reports findings to contractor, formally placing the safety risk on record",
      "proeth:element": "Contractor Receives Safety Concern",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Accepts Structural Assignment",
  "proeth:counterfactual": "Had Engineer B declined the assignment or disclosed qualification limits, the confirmed lack of qualifications would not have become an active project risk requiring investigation",
  "proeth:effect": "Engineer B\u0027s Lack of Qualifications Confirmed",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s volitional acceptance of work outside demonstrated competency",
    "Absence of supplementary foundation design training or experience",
    "No disclosure by Engineer B of qualification limitations to the contractor or Engineer A"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s acceptance of the assignment + mismatched credentials + failure to self-disclose limitations"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_04a15138",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A actively investigated Engineer B\u0027s educational background and professional experience; after finding no apparent foundation design training, Engineer A reports concerns to the contractor, with the investigation serving as the direct evidentiary basis for the report",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A proactively examines Engineer B\u0027s credentials upon recognizing a potential discipline mismatch",
      "proeth:element": "Engineer A Investigates Engineer B\u0027s Qualifications",
      "proeth:step": 1
    },
    {
      "proeth:description": "Investigation produces a definitive finding of no foundation design training or competency",
      "proeth:element": "Engineer B\u0027s Lack of Qualifications Confirmed",
      "proeth:step": 2
    },
    {
      "proeth:description": "Armed with confirmed findings, Engineer A formally communicates the safety concern to the contractor",
      "proeth:element": "Engineer A Reports Concerns to Contractor",
      "proeth:step": 3
    },
    {
      "proeth:description": "Contractor is formally placed on notice of the qualification risk, triggering contractor-level responsibility to act",
      "proeth:element": "Contractor Receives Safety Concern",
      "proeth:step": 4
    },
    {
      "proeth:description": "If contractor fails to act on the reported concern, conditions for mandatory escalation by Engineer A are met",
      "proeth:element": "Escalation Necessity Triggered",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Investigates Engineer B\u0027s Qualifications",
  "proeth:counterfactual": "Without the investigation, Engineer A would have lacked the evidentiary basis to formally report concerns; the contractor would have remained unaware of the qualification risk",
  "proeth:effect": "Engineer A Reports Concerns to Contractor",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s decision to investigate rather than ignore the potential competency concern",
    "The investigation yielding confirmatory negative findings",
    "Engineer A\u0027s professional obligation to act on confirmed safety-relevant findings"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Confirmed qualification gap + Engineer A\u0027s ethical duty to protect public safety + accessible reporting channel to contractor"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_fb9742ec",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After investigating Engineer B\u0027s qualifications and finding no apparent foundation design training, Engineer A reports concerns to the contractor, directly causing the contractor to become formally aware of Engineer A\u0027s concerns about Engineer B\u0027s qualifications",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A formally communicates confirmed qualification concerns to the contractor",
      "proeth:element": "Engineer A Reports Concerns to Contractor",
      "proeth:step": 1
    },
    {
      "proeth:description": "Contractor is placed on formal notice, acquiring both knowledge and responsibility to act",
      "proeth:element": "Contractor Receives Safety Concern",
      "proeth:step": 2
    },
    {
      "proeth:description": "Concurrent with or following contractor notification, Engineer A directly confronts Engineer B per ethical obligations",
      "proeth:element": "Engineer A Confronts Engineer B Directly",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B either withdraws or refuses, determining the next required action",
      "proeth:element": "Engineer B Confrontation Outcome Determined",
      "proeth:step": 4
    },
    {
      "proeth:description": "Contractor inaction combined with Engineer B\u0027s refusal triggers mandatory escalation obligation for Engineer A",
      "proeth:element": "Escalation Necessity Triggered",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Reports Concerns to Contractor",
  "proeth:counterfactual": "Without Engineer A\u0027s report, the contractor would not have been formally on notice; any subsequent harm would have occurred without the contractor having had an opportunity to intervene",
  "proeth:effect": "Contractor Receives Safety Concern",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s prior investigation yielding confirmed negative findings",
    "Engineer A\u0027s decision to report rather than remain silent",
    "A functioning communication channel between Engineer A and the contractor"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Confirmed qualification gap + Engineer A\u0027s report + contractor\u0027s receipt of the communication"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_1c62e567",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A must directly confront Engineer B; following Engineer A\u0027s direct confrontation and recommendation, Engineer B faces a prospective decision to withdraw or refuse, with the confrontation being the proximate trigger of the outcome determination",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A directly and formally raises the competency concern with Engineer B and recommends withdrawal",
      "proeth:element": "Engineer A Confronts Engineer B Directly",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B makes a volitional decision to withdraw or refuse, bifurcating the subsequent causal pathway",
      "proeth:element": "Engineer B Confrontation Outcome Determined",
      "proeth:step": 2
    },
    {
      "proeth:description": "If Engineer B withdraws, the safety risk is mitigated; if Engineer B refuses, escalation becomes mandatory",
      "proeth:element": "Engineer B Decides Whether to Withdraw",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B\u0027s refusal combined with contractor inaction activates Engineer A\u0027s obligation to escalate",
      "proeth:element": "Escalation Necessity Triggered",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A escalates the competence concern to the client and relevant authorities to protect public safety",
      "proeth:element": "Engineer A Escalates to Client and Authorities",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Confronts Engineer B Directly",
  "proeth:counterfactual": "Without direct confrontation, Engineer B would not have been formally presented with the opportunity to self-correct; the outcome determination event would not have been triggered, and escalation pathways would have been bypassed",
  "proeth:effect": "Engineer B Confrontation Outcome Determined",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s direct confrontation providing Engineer B with explicit notice of the competency concern",
    "Engineer B\u0027s volitional capacity to choose withdrawal or refusal",
    "The confrontation occurring before irreversible structural design decisions are finalized"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (for initiating confrontation); Engineer B (for the outcome decision)",
  "proeth:sufficientFactors": [
    "Direct confrontation by Engineer A + Engineer B\u0027s awareness of the ethical and professional stakes + Engineer B\u0027s decision-making capacity"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_14d10167",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "If Engineer B refuses to withdraw and the contractor fails to act, the conditions for mandatory escalation are triggered; Engineer B\u0027s refusal decision is the pivotal volitional act that makes escalation necessity a live condition",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B makes the pivotal decision to refuse withdrawal despite Engineer A\u0027s direct confrontation",
      "proeth:element": "Engineer B Decides Whether to Withdraw",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B\u0027s refusal combined with contractor inaction satisfies all conditions making escalation mandatory for Engineer A",
      "proeth:element": "Escalation Necessity Triggered",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A fulfills the escalation obligation by notifying the client and relevant professional or regulatory authorities",
      "proeth:element": "Engineer A Escalates to Client and Authorities",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Engineer B Decides Whether to Withdraw",
  "proeth:counterfactual": "Had Engineer B chosen to withdraw, escalation necessity would not have been triggered regardless of contractor behavior; the causal chain to authority escalation would have been severed",
  "proeth:effect": "Escalation Necessity Triggered",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s refusal to withdraw following direct confrontation",
    "Contractor\u0027s concurrent failure to act on the reported concern",
    "Engineer A\u0027s continued presence on the project with knowledge of the unresolved risk"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer B (primary); Contractor (secondary for inaction)",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s refusal + contractor inaction + Engineer A\u0027s professional obligation to protect public safety"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/110#",
    "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/110#CausalChain_71823dad",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A historical sequence of prior Board of Ethical Review cases (71-2, 78-5, and 85-3) spanning 1971 to [the case date] established the normative and procedural framework that informed Engineer A\u0027s understanding of the duty to investigate a colleague\u0027s competency and act on findings",
  "proeth:causalSequence": [
    {
      "proeth:description": "Cases 71-2, 78-5, and 85-3 collectively establish that engineers must assess colleague competency and act on safety-relevant findings",
      "proeth:element": "Prior BER Precedents Established",
      "proeth:step": 1
    },
    {
      "proeth:description": "The design/build project creates the professional context in which Engineer A encounters Engineer B\u0027s structural assignment",
      "proeth:element": "Project Construction Commences",
      "proeth:step": 2
    },
    {
      "proeth:description": "Guided by precedent-established duty, Engineer A initiates a competency investigation rather than deferring to contractor judgment",
      "proeth:element": "Engineer A Investigates Engineer B\u0027s Qualifications",
      "proeth:step": 3
    },
    {
      "proeth:description": "Investigation confirms the competency gap, validating the precedent-guided decision to investigate",
      "proeth:element": "Engineer B\u0027s Lack of Qualifications Confirmed",
      "proeth:step": 4
    },
    {
      "proeth:description": "Precedent further guides Engineer A to report findings to the contractor as the first required escalation step",
      "proeth:element": "Engineer A Reports Concerns to Contractor",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Prior BER Precedents Established",
  "proeth:counterfactual": "Without established BER precedents, Engineer A might have treated the competency concern as a matter of professional courtesy rather than ethical obligation, potentially forgoing investigation and reporting",
  "proeth:effect": "Engineer A Investigates Engineer B\u0027s Qualifications",
  "proeth:necessaryFactors": [
    "Existence of prior BER cases establishing that engineers have an affirmative duty to assess colleague competency",
    "Engineer A\u0027s awareness of or access to these precedents",
    "The precedents being sufficiently analogous to the present situation to guide Engineer A\u0027s conduct"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineering Profession / Board of Ethical Review (institutional); Engineer A (individual application)",
  "proeth:sufficientFactors": [
    "BER precedents establishing duty + Engineer A\u0027s professional awareness + present circumstances triggering application of the duty"
  ],
  "proeth:withinAgentControl": true
}