{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Recommend_Additional_Safety_Testing",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept the test results as sufficient and sign off on the product without escalating the concern",
    "Raise the concern informally and verbally without creating a formal written recommendation",
    "Recommend a limited, lower-cost supplementary investigation rather than a full new series of tests"
  ],
  "proeth-scenario:characterMotivation": "Engineer A observed empirical anomalies in product safety performance that existing standards did not adequately address, triggering a professional duty to protect public safety even in the absence of explicit regulatory requirements governing the new product category. The motivation was rooted in technical judgment and internalized engineering ethics rather than external mandate.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Engineer A accepts results without escalation: The safety concern goes unaddressed internally; Engineer A potentially violates professional ethical obligations; if harm later occurs, Engineer A bears moral and possibly legal liability for failing to act on known concerns. The narrative never reaches its central ethical conflict.",
    "If Engineer A raises concern only informally: The concern may be more easily dismissed or ignored without a paper trail; Engineer A loses the protective documentation that a formal recommendation provides; the ethical record of having flagged the issue is ambiguous and harder to rely on in later proceedings such as the public hearing.",
    "If Engineer A recommends a limited investigation: Company X may be more receptive, potentially preserving the employment relationship and resulting in at least partial additional scrutiny of the product. However, if the limited investigation is insufficient to surface the safety issue, the underlying risk to consumers persists and Engineer A may have compromised thoroughness for organizational acceptance."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that an engineer\u0027s ethical duty to safeguard public safety is not bounded by the minimum requirements of existing standards. Engineers must exercise independent professional judgment even when products technically pass current benchmarks, and must be willing to formally escalate safety concerns through proper internal channels regardless of anticipated organizational resistance.",
  "proeth-scenario:ethicalTension": "Professional obligation to protect public safety (NSPE Code Canon 1) conflicts with organizational loyalty and deference to employer judgment on business decisions. Additionally, the absence of governing standards for the new product creates tension between acting on precautionary principle versus respecting the limits of one\u0027s formal authority and the sufficiency of passed existing tests.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Consumer safety and potential physical harm to end users if the inconsistent performance reflects a genuine latent defect; Engineer A\u0027s professional credibility and standing within Company X; the product\u0027s market timeline and Company X\u0027s financial interests; and the integrity of the engineering profession\u0027s commitment to public welfare over commercial convenience.",
  "proeth:description": "Engineer A observed inconsistent product performance following completed standard safety testing and formally recommended to Supervisor B that Company X conduct a new series of tests to assess consumer safety. This decision was made despite the product having passed existing safety parameters and in the absence of any governing standards specific to the new product.",
  "proeth:foreseenUnintendedEffects": [
    "Potential delay in product launch",
    "Additional cost burden to Company X",
    "Possible friction with management over recommendation"
  ],
  "proeth:fulfillsObligation": [
    "Duty to hold public safety, health, and welfare paramount (NSPE Code)",
    "Obligation to notify employer of safety concerns observed in the course of professional work",
    "Duty to act within area of professional competence by flagging concerns rather than unilaterally deciding product is unsafe",
    "Obligation to use internal channels before pursuing external remedies"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare paramount over commercial interests",
    "Professional honesty and integrity in reporting observations",
    "Proactive risk identification as part of engineering practice",
    "Exhaustion of internal remedies before external escalation"
  ],
  "proeth:hasAgent": "Engineer A (Company X employee, professional engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public safety obligation vs. employer commercial interests and existing compliance",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict in favor of public safety by making the recommendation, while respecting procedural norms by directing the recommendation to a supervisor rather than taking unilateral or external action at this stage"
  },
  "proeth:hasMentalState": "deliberate and conscientious",
  "proeth:intendedOutcome": "Prompt Company X to conduct additional testing to resolve inconsistent performance concerns and mitigate potential consumer safety risks before product release",
  "proeth:requiresCapability": [
    "Engineering judgment to identify anomalous product performance",
    "Ability to assess safety implications of inconsistent performance data",
    "Professional communication to articulate safety concerns to management",
    "Knowledge of product safety testing methodologies"
  ],
  "proeth:temporalMarker": "During and following completion of standard safety testing, prior to resignation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Recommend Additional Safety Testing"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Reject_Additional_Testing_Recommendation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept the recommendation and authorize a modified, cost-constrained version of additional testing",
    "Reject the recommendation but formally document the rejection and the safety concern in company records",
    "Escalate the decision to a higher level of corporate leadership or a safety review board rather than issuing a final rejection at the supervisory level"
  ],
  "proeth-scenario:characterMotivation": "Company X\u0027s management prioritized financial performance and time-to-market competitiveness, concluding that the product had met existing applicable safety standards and that the cost and delay associated with additional testing were not justified by Engineer A\u0027s concerns. The motivation reflects a rational business calculus that discounts precautionary action when regulatory compliance has already been achieved.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Company X authorizes modified testing: Some additional safety scrutiny occurs, potentially surfacing the concern at reduced cost; Engineer A\u0027s professional relationship with the company is preserved; the narrative may resolve earlier without resignation or public hearing involvement, though the adequacy of modified testing remains uncertain.",
    "If Company X rejects but formally documents: The rejection creates an institutional record acknowledging the safety concern, which could later serve as evidence of negligence if harm occurs; it also provides Engineer A with clearer documentation supporting any future whistleblowing or testimony, potentially strengthening the ethical and legal basis for Engineer A\u0027s later actions.",
    "If the decision is escalated internally: Higher leadership may apply a different risk calculus, particularly if legal or reputational risks are surfaced more explicitly; the decision gains legitimacy through broader deliberation; however, escalation may also simply delay the same outcome if organizational culture uniformly prioritizes cost and speed."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates how organizational decision-making structures can suppress legitimate safety concerns through economic rationalization. Highlights the systemic pressure engineers face when institutional incentives are misaligned with precautionary safety principles, and illustrates why engineering codes of ethics must empower individual engineers to act even when organizational authority pushes back.",
  "proeth-scenario:ethicalTension": "Corporate fiduciary responsibility to shareholders and competitive business interests conflict with the broader duty of care owed to consumers and the public. Management must also balance trust in existing regulatory frameworks against the professional judgment of an internal engineer who is signaling that those frameworks may be inadequate for a novel product.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Company X risks long-term reputational and legal liability if the product causes consumer harm; consumers are exposed to a potentially unsafe product; Engineer A is placed in an untenable professional position; the organizational culture signal sent to other engineers at Company X may discourage future safety escalations.",
  "proeth:description": "Company X\u0027s management, through the decision-making process involving Supervisor B and organizational leadership, rejected Engineer A\u0027s recommendation to conduct additional safety testing. The rejection was explicitly based on the projected cost of additional testing and the anticipated delay to product launch.",
  "proeth:foreseenUnintendedEffects": [
    "Potential unresolved safety concerns remaining in the product",
    "Risk of future liability if safety issues materialize post-launch",
    "Possible dissatisfaction or departure of Engineer A"
  ],
  "proeth:fulfillsObligation": [
    "Compliance with existing applicable safety standards and testing procedures",
    "Exercise of business judgment within legal and regulatory boundaries"
  ],
  "proeth:guidedByPrinciple": [
    "Cost-benefit analysis in product development decisions",
    "Compliance-based rather than precautionary approach to safety",
    "Business efficiency and market competitiveness"
  ],
  "proeth:hasAgent": "Company X management / Supervisor B (corporate decision-makers)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Consumer safety precaution vs. commercial cost and schedule",
    "proeth:resolutionReasoning": "Company X resolved the conflict by deferring to existing regulatory compliance and the absence of mandatory standards, prioritizing commercial considerations over precautionary additional testing"
  },
  "proeth:hasMentalState": "deliberate and commercially motivated",
  "proeth:intendedOutcome": "Avoid additional cost and product launch delays while relying on the sufficiency of completed standard safety testing",
  "proeth:requiresCapability": [
    "Corporate risk assessment and management decision-making",
    "Evaluation of regulatory compliance status",
    "Business judgment regarding cost-benefit of additional testing"
  ],
  "proeth:temporalMarker": "Shortly after Engineer A\u0027s recommendation, prior to Engineer A\u0027s resignation",
  "proeth:violatesObligation": [
    "Arguably, a broader ethical obligation to proactively investigate credible safety concerns raised by a qualified engineer, even absent regulatory mandate",
    "Duty of responsible care toward consumers when a professional engineer has flagged potential unique safety risks"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Reject Additional Testing Recommendation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Resign_From_Company_X",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Remain employed at Company X while continuing to advocate internally through additional memos, meetings, or escalation to higher leadership",
    "Remain employed but simultaneously report the safety concern to an external regulatory authority before resigning",
    "Resign and immediately and proactively contact the relevant regulatory agency to disclose the safety concern rather than waiting for a public hearing"
  ],
  "proeth-scenario:characterMotivation": "Engineer A\u0027s resignation most plausibly reflects a judgment that continued employment at Company X was incompatible with fulfilling professional ethical obligations \u2014 either because remaining would implicitly endorse a decision Engineer A believed was unsafe, or because the organizational environment made it impossible to advocate effectively for consumer protection. The resignation may also reflect a desire to preserve personal integrity and avoid complicity in potential future harm.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Engineer A remains and continues internal advocacy: The safety concern stays alive within Company X and may eventually gain traction, particularly if new evidence emerges; however, Engineer A risks professional marginalization, retaliation, or being pressured out; the ongoing internal presence may also create legal complexity around confidentiality obligations if Engineer A later seeks to testify.",
    "If Engineer A remains and reports externally before resigning: This is the most aggressive protective action and most directly serves public safety; however, it likely triggers immediate employment termination and potential legal action by Company X for breach of confidentiality; it also raises the BER 08-10 precedent question of whether external reporting is premature before exhausting internal remedies.",
    "If Engineer A resigns and proactively contacts regulators: The safety concern reaches regulatory attention more quickly than waiting for a hearing announcement; Engineer A acts on the affirmative duty to protect public safety rather than waiting passively; however, Engineer A must navigate confidentiality obligations and the risk of acting on incomplete information without the institutional resources to conduct further investigation."
  ],
  "proeth-scenario:decisionSignificance": "Raises the question of when resignation is the ethically appropriate response to an unresolved organizational safety conflict versus when it represents an abdication of the engineer\u0027s internal advocacy role. Also introduces the concept of post-employment ethical obligations \u2014 resignation does not terminate an engineer\u0027s duty to public safety, as the subsequent hearing scenario demonstrates. Students should examine whether resignation was premature, necessary, or insufficient as an ethical response.",
  "proeth-scenario:ethicalTension": "Personal economic security and career continuity conflict with professional integrity and the engineer\u0027s internalized duty to public safety. There is also tension between loyalty to an employer who has provided legitimate employment and the engineer\u0027s higher-order obligation to the public. The decision to resign rather than remain and continue internal advocacy raises questions about whether exit is more or less ethical than sustained internal dissent.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s livelihood, professional reputation, and future employability; the loss of an internal safety advocate within Company X; the question of whether Engineer A retains any standing or obligation to act on the safety concern after leaving; and the signal sent to Company X that safety dissent leads to employee departure rather than policy reconsideration.",
  "proeth:description": "At an unspecified point after Company X rejected the additional testing recommendation, Engineer A made the volitional decision to resign from employment at Company X. The case does not specify the explicit reasons for resignation, but it occurs in the context of the unresolved safety concern and the rejection of Engineer A\u0027s professional recommendation.",
  "proeth:foreseenUnintendedEffects": [
    "Loss of direct ability to influence Company X\u0027s product safety decisions from within",
    "Potential future tension between confidentiality obligations to former employer and public safety obligations",
    "Preservation of Engineer A\u0027s professional integrity by not continuing to be associated with a product Engineer A believed raised unresolved safety concerns"
  ],
  "proeth:fulfillsObligation": [
    "Protection of personal professional integrity by not continuing association with a product believed to have unresolved safety concerns",
    "Implicit recognition that internal remedies had been exhausted at the recommendation level"
  ],
  "proeth:guidedByPrinciple": [
    "Professional integrity and personal ethical standards",
    "Engineer\u0027s right to disengage from situations that compromise professional values",
    "Implicit acknowledgment that further internal escalation was unlikely to succeed"
  ],
  "proeth:hasAgent": "Engineer A (Company X employee, professional engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Continued internal influence over safety vs. personal professional integrity and disengagement",
    "proeth:resolutionReasoning": "Engineer A resolved in favor of resignation, likely judging that internal remedies were exhausted and continued employment was professionally untenable, while accepting the consequent constraints on future action"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Departure from an employment situation where Engineer A\u0027s professional safety judgment was overridden and concerns left unaddressed",
  "proeth:requiresCapability": [
    "Professional self-assessment of ethical boundaries",
    "Understanding of post-employment confidentiality obligations",
    "Judgment about the limits of internal advocacy"
  ],
  "proeth:temporalMarker": "Unspecified time after Company X\u0027s rejection of additional testing recommendation, at least one year before the hearing announcement",
  "proeth:violatesObligation": [
    "Arguably, ongoing internal advocacy obligation \u2014 resignation ends Engineer A\u0027s ability to continue pressing for safety improvements from within the organization",
    "Some interpretations of engineering ethics suggest engineers should exhaust all internal escalation paths before disengaging"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Resign From Company X"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Consider_Testifying_at_Public_Hearing",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline to testify and take no action, treating the matter as resolved by resignation and the passage of time",
    "Submit written technical information anonymously or through a third party rather than testifying directly",
    "Consult with an attorney and the relevant engineering professional society before deciding whether and how to testify"
  ],
  "proeth-scenario:characterMotivation": "Engineer A is motivated by the convergence of a formal public process that creates a legitimate and structured channel for disclosure, a renewed sense of professional obligation to public safety triggered by the hearing announcement, and the recognition that the safety concern identified during employment has never been resolved. The one-year gap and the government-initiated nature of the hearing may also reduce Engineer A\u0027s concern about confidentiality obligations, as the public forum was not initiated by Engineer A.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Engineer A declines to testify: Relevant safety information is withheld from a government regulatory process specifically designed to address the product category in question; Engineer A may avoid legal and professional risk in the short term but potentially bears moral responsibility if consumers are later harmed by a risk Engineer A could have helped regulators identify; the public interest is not served.",
    "If Engineer A submits information anonymously: Some safety information reaches the regulatory process while Engineer A reduces personal legal exposure; however, anonymous submissions may carry less evidentiary weight, cannot be cross-examined or clarified, and may be dismissed more easily; Engineer A also cannot fully discharge a professional duty through concealment of identity in a formal proceeding.",
    "If Engineer A consults legal and professional advisors first: This is arguably the most procedurally sound approach, ensuring Engineer A understands confidentiality obligations, the scope of permissible disclosure, and the professional ethics framework before acting; it may delay participation but significantly reduces the risk of acting improperly; it also demonstrates the kind of deliberate, informed ethical reasoning the engineering profession expects."
  ],
  "proeth-scenario:decisionSignificance": "This is the central ethical decision of the case and the primary teaching vehicle. It illustrates that ethical obligations do not terminate with employment, that legitimate public processes can create affirmative duties to participate, and that the conditions under which disclosure is ethical \u2014 including the nature of the forum, the specificity of the safety concern, and the exhaustion of internal remedies \u2014 must be carefully analyzed. The case ultimately concludes Engineer A may testify under specific conditions, making this a nuanced rather than absolute ethical ruling.",
  "proeth-scenario:ethicalTension": "Post-employment confidentiality obligations to a former employer conflict with the engineer\u0027s continuing duty to protect public safety. The engineer must also weigh the risk of acting on potentially incomplete or dated technical information against the risk of withholding relevant safety knowledge from a regulatory process. There is further tension between self-interest \u2014 including potential legal exposure and reputational risk \u2014 and civic and professional duty.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Consumer safety on a broad scale if the product category is widely distributed; Engineer A\u0027s legal exposure for potential breach of confidentiality or nondisclosure agreements; Engineer A\u0027s professional reputation and future career prospects; the integrity and completeness of the government regulatory process; and the precedent set for how engineers balance post-employment loyalty against ongoing public safety obligations.",
  "proeth:description": "One year after resigning from Company X, upon learning that the relevant government agency announced a public safety standards hearing covering the new product category, Engineer A faces and actively considers the decision of whether to participate as a witness at the hearing. This is the central volitional decision analyzed in the case.",
  "proeth:foreseenUnintendedEffects": [
    "Potential breach of confidentiality obligations to Company X if testimony discloses protected information",
    "Possible legal exposure from former employer",
    "Positive contribution to public safety standards development if testimony is appropriate and objective",
    "Risk of testimony exceeding Engineer A\u0027s technical competence boundaries"
  ],
  "proeth:fulfillsObligation": [
    "Duty to consider public safety obligations as a professional engineer when presented with a relevant public forum",
    "Obligation to bring safety concerns to appropriate governmental authorities when internal remedies have been exhausted (consistent with BER 76-4)",
    "Duty to assess competence boundaries before agreeing to serve as expert witness"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety, health, and welfare as paramount engineering obligation",
    "Truthfulness and objectivity in professional communications",
    "Respect for confidentiality obligations even after employment ends",
    "Engineers should engage with governmental processes when they have relevant safety knowledge"
  ],
  "proeth:hasAgent": "Engineer A (former Company X employee, professional engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public safety advocacy vs. confidentiality and competence constraints",
    "proeth:resolutionReasoning": "The Board resolves that participation is ethically permissible \u2014 and potentially obligatory if Engineer A holds a good faith safety belief \u2014 provided the three conditions of competence, objectivity, and confidentiality compliance are satisfied, reconciling the competing priorities through conditional participation rather than absolute prohibition or mandate"
  },
  "proeth:hasMentalState": "deliberative and conscientious",
  "proeth:intendedOutcome": "Determine whether participating as a hearing witness would appropriately fulfill Engineer A\u0027s public safety obligations while respecting confidentiality and professional competence boundaries",
  "proeth:requiresCapability": [
    "Technical expertise in the specific product safety area being addressed at the hearing",
    "Ability to provide objective, evidence-based testimony",
    "Professional judgment to distinguish between what can be disclosed and what is protected by confidentiality",
    "Understanding of formal governmental hearing procedures and expert witness standards"
  ],
  "proeth:temporalMarker": "One year after resignation, at the time of the government agency\u0027s public safety standards hearing announcement",
  "proeth:withinCompetence": true,
  "rdfs:label": "Consider Testifying at Public Hearing"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Verbally_Report_Findings_to_Client",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Wait until the written report is complete before disclosing any findings to XYZ Corporation",
    "Disclose findings verbally and simultaneously provide a written preliminary summary to create a documented record",
    "Decline to advise XYZ Corporation in advance and submit findings directly to the regulatory authority as part of the formal hearing process"
  ],
  "proeth-scenario:characterMotivation": "Engineer Doe in BER 76-4 was motivated by a professional obligation to inform the client of findings that directly contradicted the client\u0027s apparent position, while also exercising judgment about the appropriate timing and form of disclosure \u2014 choosing verbal advisement before the written report was complete, likely to give the client an opportunity to respond or correct course before findings became formal and public.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Engineer Doe waits for the written report: The disclosure is fully documented from the outset, reducing ambiguity about what was communicated and when; however, if XYZ Corporation has already submitted data to the regulatory authority before receiving Engineer Doe\u0027s findings, the opportunity to influence the client\u0027s behavior before the public hearing is lost.",
    "If Engineer Doe provides verbal disclosure with a written preliminary summary: This approach combines the timeliness of early disclosure with the evidentiary protection of documentation; it is arguably the most professionally sound approach and reduces the risk of the client later disputing that findings were communicated.",
    "If Engineer Doe bypasses the client and reports directly to regulators: This approach most directly serves the public interest and regulatory process but may breach the client relationship prematurely, violating the norm of exhausting client-directed remedies before external escalation \u2014 the very issue analyzed in BER 08-10."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the importance of the form, timing, and documentation of professional communications in engineering ethics. Verbal reporting without written follow-up creates evidentiary ambiguity and can undermine the engineer\u0027s ability to demonstrate that disclosure occurred. This action also establishes the factual predicate for the subsequent regulatory reporting decision, showing how earlier procedural choices shape later ethical obligations.",
  "proeth-scenario:ethicalTension": "The duty of candor and timely disclosure to a client conflicts with the procedural norm of completing a formal written report before communicating findings. There is also tension between client loyalty \u2014 giving XYZ Corporation advance notice and an opportunity to respond \u2014 and the risk that early verbal disclosure without documentation could be denied, misrepresented, or used to pressure the engineer to alter conclusions.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The integrity of Engineer Doe\u0027s professional findings; XYZ Corporation\u0027s ability to claim ignorance of contrary evidence; the regulatory authority\u0027s access to complete information; and the evidentiary foundation for Engineer Doe\u0027s subsequent decision to report to regulators. If verbal disclosure is denied by the client, Engineer Doe\u0027s credibility in the regulatory process is compromised.",
  "proeth:description": "In precedent case BER 76-4, Engineer Doe chose to verbally advise XYZ Corporation of his findings \u2014 that the plant\u0027s discharge would lower water quality below established standards \u2014 before completing a written report, representing a deliberate choice about the form and timing of disclosure to the client.",
  "proeth:foreseenUnintendedEffects": [
    "Client may attempt to suppress or act on findings before written report is completed",
    "Verbal-only disclosure may limit Engineer Doe\u0027s ability to demonstrate the findings were properly communicated"
  ],
  "proeth:fulfillsObligation": [
    "Duty to inform client of material findings relevant to the engagement",
    "Honesty and transparency with client about professional conclusions"
  ],
  "proeth:guidedByPrinciple": [
    "Professional honesty and transparency",
    "Timely communication of findings to client",
    "Public welfare \u2014 findings related to environmental standards protecting public health"
  ],
  "proeth:hasAgent": "Engineer Doe (consulting engineer, BER 76-4)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Timely client notification vs. documentation integrity",
    "proeth:resolutionReasoning": "Engineer Doe prioritized early client notification but the choice of verbal-only disclosure proved consequential when the client subsequently suppressed the findings and terminated the contract"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill professional obligation to inform client of significant findings while the engagement was ongoing, giving the client early notice of the adverse conclusion",
  "proeth:requiresCapability": [
    "Environmental engineering analysis",
    "Professional judgment about timing and form of client communications"
  ],
  "proeth:temporalMarker": "After completing studies but before completing written report (BER 76-4)",
  "proeth:violatesObligation": [
    "Arguably, the decision to report only verbally without completing the written report left the findings undocumented and susceptible to suppression"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Verbally Report Findings to Client"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Report_Findings_to_Regulatory_Authority",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Refuse to report to the regulatory authority, citing client confidentiality, and instead submit a final written report to XYZ Corporation only",
    "Seek legal counsel and attempt to negotiate with XYZ Corporation to voluntarily correct or supplement its regulatory submission before independently reporting",
    "Report findings to the regulatory authority but request that the disclosure be treated as confidential or anonymous"
  ],
  "proeth-scenario:characterMotivation": "Engineer Doe was motivated by the discovery that XYZ Corporation had presented data to the regulatory authority that contradicted Engineer Doe\u0027s own findings, creating a situation in which the regulatory process was proceeding on incomplete or misleading information. The public safety implications of the discharge issue, combined with the active misrepresentation of the situation to regulators, created a compelling obligation to correct the record.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Engineer Doe refuses to report and submits only to the client: The regulatory authority makes decisions based on incomplete and potentially misleading data; public health is not protected; Engineer Doe may later be found to have violated professional ethical obligations by withholding material safety information from a public proceeding; the Board\u0027s analysis suggests this would be ethically impermissible.",
    "If Engineer Doe negotiates with XYZ Corporation first: This approach attempts to exhaust client-directed remedies before external escalation, which is consistent with the BER 08-10 framework; however, it introduces delay during which the regulatory process may advance on false premises, and XYZ Corporation may use the negotiation period to further entrench its public position.",
    "If Engineer Doe reports anonymously or confidentially: The regulatory authority receives the information but cannot effectively examine or rely on it without attribution; the evidentiary value is diminished; and anonymous reporting in a formal regulatory proceeding may not be procedurally permissible or practically effective."
  ],
  "proeth-scenario:decisionSignificance": "This action, validated by the Board as an ethical obligation, establishes the key precedent applied to Engineer A\u0027s situation: when a client or former employer takes a public position that the engineer has professional knowledge to contradict, and when a formal regulatory process is the venue, the engineer\u0027s duty to public safety and regulatory integrity overrides confidentiality concerns. The case is directly cited as precedent for Engineer A\u0027s decision to testify.",
  "proeth-scenario:ethicalTension": "Client confidentiality and loyalty to XYZ Corporation conflict with the duty to provide accurate information to a regulatory authority charged with protecting public welfare. The tension is intensified by the fact that the client has actively taken a contrary public position, effectively transforming a private professional disagreement into a public factual dispute in which Engineer Doe\u0027s silence becomes a form of complicity in potential regulatory deception.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Water quality and public health downstream of the XYZ Corporation plant; the integrity of the regulatory hearing process; Engineer Doe\u0027s professional reputation and potential legal exposure for either reporting or failing to report; XYZ Corporation\u0027s regulatory and legal standing if contrary findings are disclosed; and the broader precedent for engineering professional conduct in regulatory contexts.",
  "proeth:description": "In precedent case BER 76-4, upon learning that XYZ Corporation had called a public hearing and presented data supporting its position that discharge met minimum standards, Engineer Doe faced the decision of whether to report his contrary findings to the regulatory authority. The Board concluded this reporting was an ethical obligation.",
  "proeth:foreseenUnintendedEffects": [
    "Potential legal or professional retaliation from XYZ Corporation",
    "Breach of implicit client confidentiality expectations",
    "Potential adverse regulatory outcome for XYZ Corporation"
  ],
  "proeth:fulfillsObligation": [
    "Paramount duty to public safety, health, and welfare (NSPE Code)",
    "Obligation to provide truthful information to governmental authorities",
    "Duty to correct misleading information before a regulatory body when engineer possesses contrary evidence"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare paramount over client loyalty",
    "Truthfulness and integrity in professional conduct",
    "Engineers\u0027 obligation to engage with public regulatory processes when they possess relevant safety knowledge"
  ],
  "proeth:hasAgent": "Engineer Doe (former consulting engineer, BER 76-4)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Public safety and regulatory integrity vs. client confidentiality and contractual constraints",
    "proeth:resolutionReasoning": "The Board resolved unambiguously in favor of disclosure because failure to meet minimum legally established standards constitutes a direct threat to public health and safety, making the public welfare obligation clearly paramount over residual confidentiality considerations"
  },
  "proeth:hasMentalState": "obligatory and conscientious",
  "proeth:intendedOutcome": "Ensure the regulatory authority had accurate information about the discharge\u0027s impact on water quality standards, correcting the incomplete or misleading picture presented by XYZ Corporation",
  "proeth:requiresCapability": [
    "Environmental engineering expertise to substantiate findings before regulatory authority",
    "Knowledge of applicable environmental quality standards",
    "Ability to present technical findings in regulatory proceedings"
  ],
  "proeth:temporalMarker": "Upon learning of the public hearing called by XYZ Corporation (BER 76-4)",
  "proeth:violatesObligation": [
    "Implicit client confidentiality \u2014 though the Board determined public safety obligation superseded this",
    "Possible contractual constraints from the terminated engagement"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Report Findings to Regulatory Authority"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Action_Escalate_with_External_Reporting_Threat",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Continue internal escalation by reporting the unresolved concern to a higher level of management or a formal safety committee before threatening external reporting",
    "Wait a reasonable additional period \u2014 defined by the severity of the risk and organizational norms \u2014 before reassessing whether external reporting has become necessary",
    "Consult with the company\u0027s legal or compliance function to formally document the unresolved safety concern and create institutional accountability without immediately threatening external reporting"
  ],
  "proeth-scenario:characterMotivation": "Engineer A in BER 08-10 was motivated by genuine concern for worker safety related to the respirator valve placement, frustration that one month had passed without corrective action after an internal report, and a belief that the threat of external regulatory reporting would compel the employer to act. The escalation reflects an attempt to use the credible threat of external accountability to force internal compliance.",
  "proeth-scenario:consequencesIfAlternative": [
    "If Engineer A escalates further internally first: The internal process is more fully exhausted, strengthening the ethical and legal basis for any subsequent external reporting; management at a higher level may resolve the issue without external intervention; the Board\u0027s framework suggests this is the appropriate next step before threatening regulatory action.",
    "If Engineer A waits a reasonable additional period: The proportionality of the response is better calibrated to the actual urgency of the risk; if the risk is genuinely imminent and severe, a waiting period may be inappropriate, but for a concern that has existed for one month without documented harm, additional internal patience may be warranted; this approach avoids the premature escalation finding.",
    "If Engineer A involves legal or compliance functions: The concern is formally institutionalized within the organization, creating accountability and a paper trail without the coercive dimension of threatening external reporting; this approach may be more effective at prompting corrective action while preserving the employment relationship and avoiding the ethical criticism the Board leveled at the threat-based escalation."
  ],
  "proeth-scenario:decisionSignificance": "This action, found premature and unethical by the Board, provides the critical counterpoint in the case\u0027s ethical analysis. It establishes that the manner, timing, and proportionality of escalation matter in engineering ethics \u2014 not just the underlying safety concern. The Board\u0027s finding that this action was premature teaches students that even legitimate safety concerns do not justify bypassing internal processes prematurely, and that threatening external reporting before exhausting internal channels can itself be an ethical violation.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to protect worker safety creates pressure to escalate when internal reports are ignored, but the professional norm of exhausting internal remedies before external escalation \u2014 and the proportionality principle in whistleblowing ethics \u2014 conflicts with the aggressive tactic of threatening regulatory reporting after only one month. The tension is between urgency of safety concern and the procedural requirement to give organizations adequate time and opportunity to self-correct.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Worker safety if the valve placement issue is genuinely dangerous and internal inaction continues; the engineer\u0027s employment and professional standing if the threat is perceived as coercive or insubordinate; the employer\u0027s regulatory exposure if the threat triggers a defensive rather than corrective response; and the precedent for how engineers should calibrate the escalation of safety concerns within organizations.",
  "proeth:description": "In precedent case BER 08-10, after learning one month later that nothing had been done to correct the potentially dangerous respirator valve placement, Engineer A escalated by indicating to the manager that if prompt measures were not taken to correct the problem, Engineer A would be compelled to report the matter to an appropriate federal regulatory agency. The Board found this action premature and unethical.",
  "proeth:foreseenUnintendedEffects": [
    "Potential damage to working relationship with management",
    "Possible premature external escalation before internal mechanisms were exhausted",
    "Risk of regulatory action based on a concern that had not yet been fully investigated internally"
  ],
  "proeth:fulfillsObligation": [
    "Re-escalation of unresolved safety concern demonstrating persistence in public safety advocacy",
    "Urgency of response proportionate to the increasing market exposure of potentially dangerous devices"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety urgency",
    "Proportionate and procedurally appropriate escalation",
    "Internal remedies must be exhausted before external action"
  ],
  "proeth:hasAgent": "Engineer A (MedTech employee, BER 08-10)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Urgency of safety intervention vs. procedural exhaustion of internal remedies",
    "proeth:resolutionReasoning": "The Board resolved that even genuine urgency does not justify bypassing internal mechanisms without first determining what steps are being taken internally; Engineer A should have sought information about internal processes and explored internal escalation paths before threatening external reporting"
  },
  "proeth:hasMentalState": "urgent and coercive",
  "proeth:intendedOutcome": "Use the threat of external regulatory reporting as leverage to compel management to take immediate corrective action on the respirator valve safety issue",
  "proeth:requiresCapability": [
    "Engineering judgment about safety risk severity and urgency",
    "Professional communication and escalation skills",
    "Knowledge of internal organizational escalation mechanisms",
    "Understanding of regulatory reporting obligations and thresholds"
  ],
  "proeth:temporalMarker": "One month after initial report to manager, upon learning no corrective action had been taken (BER 08-10)",
  "proeth:violatesObligation": [
    "Obligation to exhaust internal remedies before threatening external action (per Board\u0027s analysis)",
    "Duty to inquire about and understand internal processes before bypassing them",
    "Professional obligation to use measured escalation rather than coercive threats"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Escalate with External Reporting Threat"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Event_Safety_Inconsistency_Detected",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what threshold of uncertainty should an engineer escalate a safety concern \u2014 must it be proven, or is suspicion sufficient?",
    "How does the fact that safety testing is \u0027standard\u0027 affect Engineer A\u0027s obligations when results are inconsistent?",
    "What institutional pressures might cause an engineer to downplay or ignore an ambiguous safety finding, and how should those pressures be resisted?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A experiences professional alarm and moral concern upon recognizing the safety inconsistency; initial uncertainty about severity and next steps; possible conflict between loyalty to employer and duty to public safety",
  "proeth-scenario:ethicalImplications": "Reveals the tension between epistemic uncertainty (inconsistent, not conclusive results) and the precautionary principle in engineering ethics; highlights that the duty to protect public safety may be triggered before certainty is achieved; exposes how organizational context shapes whether safety signals are acted upon",
  "proeth-scenario:learningMoment": "Safety testing outcomes are not merely technical data points \u2014 they carry professional and ethical weight. Engineers have an obligation to act on safety findings even when those findings are inconvenient or ambiguous. The moment of discovery initiates a chain of ethical responsibilities.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "company_x": "Faces potential liability and reputational risk if safety issue is real; financial interests threatened by potential delays",
    "consumers": "Potentially exposed to an unsafe product; safety at risk without their knowledge",
    "engineer_a": "Thrust into an ethical dilemma; professional obligations activated; career risk emerges",
    "public": "Broad population may be endangered if product reaches market with unresolved safety issues"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Professional_Competence_Obligation",
    "Duty_To_Report_Hazards"
  ],
  "proeth:causesStateChange": "Engineer A transitions from routine testing observer to active safety concern holder; internal reporting obligation activated; tension between employer loyalty and public safety begins",
  "proeth:createsObligation": [
    "Report_Findings_Internally",
    "Recommend_Corrective_Action",
    "Document_Safety_Concerns"
  ],
  "proeth:description": "Inconsistent safety performance is identified in a new consumer product during or after standard safety testing at Company X. This discovery reveals a potential hazard that standard testing protocols did not fully resolve.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During or immediately after standard safety testing (pre-resignation, earliest event in timeline)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Safety Inconsistency Detected"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Event_Additional_Testing_Rejected",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Company X\u0027s rejection of the safety recommendation constitute a violation of engineering ethics, and if so, by whom?",
    "At what point does an engineer\u0027s continued employment become complicity in a safety risk?",
    "What options remain available to Engineer A after the rejection, and what are the ethical and professional consequences of each?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences frustration, professional isolation, and moral distress; Supervisor B and management may feel relief at avoiding costs but also potential unease; the rejection creates a sense of institutional betrayal for Engineer A",
  "proeth-scenario:ethicalImplications": "Exposes the structural power imbalance between individual engineers and corporate employers on safety decisions; reveals how business interests can suppress safety advocacy; raises the question of whether NSPE Code obligations survive employer override; highlights the inadequacy of internal-only reporting when institutions are unresponsive",
  "proeth-scenario:learningMoment": "When an engineer\u0027s internal safety recommendation is rejected on non-technical grounds (cost, schedule), this is a critical inflection point. Engineers must understand that employer rejection does not extinguish their professional obligation to public safety \u2014 it intensifies the ethical dilemma and may trigger obligations to act externally.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "company_x": "Short-term cost savings achieved; long-term liability risk increased; organizational culture of safety potentially undermined",
    "consumers": "Remain unprotected; safety concern moves closer to market without resolution",
    "engineer_a": "Professional integrity compromised by continued association with unresolved safety issue; forced to choose between compliance and conscience",
    "supervisor_b": "Complicit in suppressing a safety recommendation; professional and legal exposure increased"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Whistleblower_Consideration_Constraint",
    "Engineer_Conscience_Clause"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/142#Action_Reject_Additional_Testing_Recommendation__by_Compa",
  "proeth:causesStateChange": "Internal resolution pathway closed; Engineer A\u0027s professional integrity placed in direct conflict with employer\u0027s business decision; the ethical calculus shifts toward external action or resignation",
  "proeth:createsObligation": [
    "Reassess_Continued_Employment",
    "Consider_External_Reporting_Channels",
    "Document_Rejection_Of_Safety_Recommendation"
  ],
  "proeth:description": "Company X formally rejects Engineer A\u0027s recommendation for additional safety testing, citing cost and schedule delay concerns. This institutional decision leaves the safety inconsistency unresolved and Engineer A\u0027s professional concern unaddressed.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Shortly after Engineer A\u0027s recommendation (pre-resignation)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Additional Testing Rejected"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Event_Engineer_A_Departs_Company",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does resigning from Company X fulfill Engineer A\u0027s ethical obligations, or does it merely remove one constraint while leaving others intact?",
    "How do post-employment confidentiality obligations interact with Engineer A\u0027s duty to warn the public about safety risks?",
    "Is resignation itself an ethically sufficient response to an employer\u0027s rejection of a safety recommendation?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A may feel relief from moral distress of complicity, but also anxiety about career consequences, financial uncertainty, and unresolved safety concern; colleagues at Company X may feel surprise, concern, or pressure; management may feel vindicated or threatened",
  "proeth-scenario:ethicalImplications": "Illustrates the persistence of professional obligations beyond employment; raises the question of whether resignation is an act of integrity or an abdication of responsibility to pursue further action; highlights the dual burden engineers carry as both employees and licensed professionals with independent public duties",
  "proeth-scenario:learningMoment": "Resignation is not the end of an engineer\u0027s ethical story \u2014 it changes the nature of obligations but does not eliminate them. Students should understand that a PE\u0027s duty to public safety is not contingent on employment status, while confidentiality obligations regarding proprietary information persist post-employment.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "company_x": "Loses a safety-concerned engineer; safety concern remains unaddressed internally; potential future liability unchanged",
    "consumers": "No immediate change in safety risk; product development continues without Engineer A\u0027s advocacy",
    "engineer_a": "Career disruption; financial risk; professional freedom gained; confidentiality obligations retained; public safety duty retained as PE",
    "engineering_profession": "Case becomes potential precedent for how engineers handle irreconcilable conflicts between employer and public safety"
  },
  "proeth:activatesConstraint": [
    "Former_Employee_Confidentiality_Constraint",
    "Post_Employment_Duty_To_Public_Safety",
    "Proprietary_Information_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/142#Action_Resign_From_Company_X__by_Engineer_A_",
  "proeth:causesStateChange": "Engineer A transitions from employee to former employee; employer loyalty obligations dissolve; confidentiality obligations persist; public safety obligations persist as a licensed professional engineer; Engineer A gains freedom to consider external disclosure",
  "proeth:createsObligation": [
    "Maintain_Confidentiality_Of_Proprietary_Info",
    "Retain_Professional_Duty_To_Public_Safety_As_PE"
  ],
  "proeth:description": "Engineer A\u0027s resignation from Company X takes effect, formally ending the employment relationship and altering Engineer A\u0027s legal and ethical standing with respect to company confidential information and safety concerns. This transition changes but does not eliminate Engineer A\u0027s professional obligations.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Following rejection of additional testing recommendation (exact date unspecified; precedes one-year marker)",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer A Departs Company"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Event_Public_Safety_Hearing_Announced",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the government\u0027s announcement of a public safety hearing create a new obligation for Engineer A to testify, or merely an opportunity?",
    "How does the one-year gap between resignation and the hearing affect Engineer A\u0027s obligations \u2014 does time diminish the duty to act?",
    "What is the significance of the hearing being government-initiated rather than initiated by Engineer A or a consumer group?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences a mix of vindication (safety concerns now publicly recognized), anxiety (decision to testify or not), and renewed moral urgency; potential relief that an external mechanism now exists; possible apprehension about confronting former employer in a public forum",
  "proeth-scenario:ethicalImplications": "Reveals how external institutional mechanisms can resolve ethical deadlocks that internal processes cannot; raises questions about the relationship between civic duty and professional duty; highlights the role of government in creating safe spaces for professional whistleblowing; exposes tension between former employer confidentiality expectations and the public interest served by regulatory testimony",
  "proeth-scenario:learningMoment": "External regulatory processes can create legitimate channels for engineers to fulfill public safety obligations that were blocked internally. The existence of a government hearing changes the ethical landscape \u2014 it provides both opportunity and renewed obligation. Students should understand that public proceedings carry different confidentiality rules than private employment contexts.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "company_x": "Faces external scrutiny of product safety; potential reputational and financial consequences; may learn of Engineer A\u0027s potential testimony",
    "consumers": "Potential protection through regulatory action; safety concerns being formally reviewed",
    "engineer_a": "Opportunity to fulfill professional duty to public safety through legitimate channel; legal protection for testimony in public proceedings; renewed ethical obligation to evaluate participation",
    "engineering_profession": "Regulatory process validates importance of engineer safety advocacy",
    "government_agency": "Fulfilling public protection mandate; creating record of safety standards deliberation"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Civic_Duty_To_Participate_In_Regulatory_Process",
    "Confidentiality_Boundary_Constraint_In_Public_Forum"
  ],
  "proeth:causesStateChange": "A legitimate public forum now exists for Engineer A\u0027s safety concerns; the ethical calculus shifts from \u0027should I act?\u0027 to \u0027how should I act?\u0027; government imprimatur on the hearing provides legal protection and ethical legitimacy for testimony",
  "proeth:createsObligation": [
    "Evaluate_Whether_To_Testify",
    "Assess_What_Information_Can_Be_Disclosed",
    "Consider_Notification_To_Former_Employer_Before_Testifying"
  ],
  "proeth:description": "One year after Engineer A\u0027s resignation, a government agency publicly announces a safety standards hearing covering the specific product category in question. This exogenous governmental action creates a formal, legitimate public channel through which Engineer A\u0027s safety concerns can be officially addressed.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "One year after Engineer A\u0027s resignation",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Public Safety Hearing Announced"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Event_Engineer_A_Faces_Testimony_Decision",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Under what specific conditions does Engineer A\u0027s obligation to testify become strong enough to override confidentiality concerns about former employer information?",
    "How should Engineer A distinguish between proprietary business information and safety-relevant technical findings when preparing testimony?",
    "What does it mean for Engineer A to testify \u0027under specific conditions\u0027 \u2014 what are those conditions and who determines them?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences the full weight of competing professional obligations simultaneously \u2014 loyalty to former employer, duty to public, fear of legal consequences, desire for vindication, and professional conscience; this is a moment of peak moral tension",
  "proeth-scenario:ethicalImplications": "Represents the culminating ethical tension of the entire case: the collision between post-employment confidentiality duties and the engineer\u0027s fundamental obligation to protect public safety; reveals that professional ethics sometimes requires personal sacrifice; demonstrates that ethical obligations can intensify rather than diminish over time when underlying safety concerns remain unresolved; raises profound questions about the social contract between licensed engineers and the public they serve",
  "proeth-scenario:learningMoment": "The convergence of professional knowledge, public safety risk, and a legitimate public forum creates an automatic ethical obligation that engineers cannot simply ignore. Students should understand that the NSPE Code\u0027s public safety mandate does not expire with employment and that government hearings represent a specifically sanctioned channel for safety disclosure. The BER precedents (76-4 and 08-10) exist precisely because this situation recurs.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "company_x": "Faces prospect of former employee testifying against product; potential legal and reputational consequences",
    "consumers": "Safety may be protected if Engineer A testifies effectively; remain at risk if Engineer A declines",
    "engineer_a": "Must navigate complex intersection of confidentiality, public safety duty, and professional integrity; career and legal consequences hang in balance",
    "engineering_profession": "Outcome sets precedent for how engineers handle post-employment safety disclosure obligations",
    "government_agency": "Quality of regulatory decision depends partly on whether knowledgeable witnesses like Engineer A participate"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Professional_Engineer_License_Obligations",
    "Confidentiality_Balancing_Constraint",
    "Former_Employer_Notification_Consideration"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/142#Action_Consider_Testifying_at_Public_Hearing__by_Engineer",
  "proeth:causesStateChange": "Engineer A\u0027s ethical status shifts from passive former employee to active deliberating professional with renewed public safety obligations; the ethical framework must now balance confidentiality, public safety, civic duty, and professional integrity simultaneously",
  "proeth:createsObligation": [
    "Evaluate_Scope_Of_Permissible_Disclosure",
    "Assess_Whether_Safety_Concern_Meets_Threshold_For_Testimony",
    "Consider_Notifying_Former_Employer_Of_Intent_To_Testify",
    "Limit_Testimony_To_Non_Proprietary_Safety_Findings"
  ],
  "proeth:description": "Engineer A finds themselves in a state of active ethical deliberation about whether to testify at the government safety hearing, a condition triggered by the hearing announcement and their possession of relevant safety knowledge. This is not a decision itself but the resulting state of ethical obligation and deliberation that the hearing announcement produces.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Following public announcement of safety hearing (one year post-resignation)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer A Faces Testimony Decision"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#Event_BER_76-4_Client_Conflict_Arises",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How does Engineer Doe\u0027s situation in BER 76-4 parallel Engineer A\u0027s situation, and where do the cases diverge?",
    "What constitutes \u0027exhausting internal channels\u0027 \u2014 is a single rejected recommendation sufficient, or must engineers persist through multiple levels?",
    "How does the consulting engineer relationship in BER 76-4 differ from the employee relationship in Engineer A\u0027s case, and does that difference matter ethically?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer Doe experiences the frustration of being ignored by client; moral urgency intensifies; professional isolation similar to Engineer A\u0027s experience; sense of responsibility without institutional support",
  "proeth-scenario:ethicalImplications": "Establishes the principle that confidentiality obligations are not absolute and yield to public safety when internal remedies fail; demonstrates the sequential nature of engineering ethics obligations (internal first, then external); reveals that the engineering profession has long recognized the tension between client loyalty and public protection",
  "proeth-scenario:learningMoment": "BER 76-4 establishes that exhausting internal reporting channels is a prerequisite for justified external disclosure, and that client/employer non-response to safety concerns activates rather than extinguishes the duty to report externally. This precedent directly informs Engineer A\u0027s situation.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Faces external regulatory scrutiny as consequence of ignoring internal safety report",
    "engineer_doe": "Forced into difficult choice between client loyalty and public safety; professional integrity tested",
    "engineering_profession": "Precedent established for when external reporting is justified",
    "public": "Safety concern escalated to regulatory level; protection more likely"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "External_Reporting_Justification_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/142#Action_Verbally_Report_Findings_to_Client__by_Engineer_Do",
  "proeth:causesStateChange": "Internal reporting pathway exhausted; external reporting to regulatory authority becomes ethically justified and obligatory; client confidentiality yields to public safety imperative",
  "proeth:createsObligation": [
    "Report_To_Regulatory_Authority",
    "Protect_Public_From_Known_Safety_Risk"
  ],
  "proeth:description": "In the precedent case BER 76-4, Engineer Doe\u0027s verbal report of findings to the client results in a conflict situation where the client\u0027s interests diverge from public safety, setting the stage for Engineer Doe\u0027s subsequent external reporting. This outcome establishes the precedent that internal reporting followed by client non-action can justify external disclosure.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During BER 76-4 precedent case (referenced in Discussion section)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "BER 76-4 Client Conflict Arises"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_6059bd58",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A observed inconsistent product performance following completed standard safety testing",
  "proeth:causalSequence": [
    {
      "proeth:description": "Inconsistent safety performance identified in new consumer product during or after standard safety testing",
      "proeth:element": "Safety Inconsistency Detected (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A evaluates the inconsistency against engineering standards and determines it warrants further investigation",
      "proeth:element": "Engineer A\u0027s Professional Assessment",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A formally recommends additional safety testing to address the identified inconsistencies",
      "proeth:element": "Recommend Additional Safety Testing (Action 1)",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Safety Inconsistency Detected (Event 1)",
  "proeth:counterfactual": "Without detecting the safety inconsistency, Engineer A would have had no basis to recommend additional testing; the recommendation was a direct response to the observed anomaly",
  "proeth:effect": "Recommend Additional Safety Testing (Action 1)",
  "proeth:necessaryFactors": [
    "Detection of inconsistent safety performance during/after standard testing",
    "Engineer A\u0027s professional awareness and ethical obligation to act on observed anomalies",
    "Engineer A\u0027s continued employment and access to product data at Company X"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Observed safety inconsistency + professional engineering duty + access to decision-making channels"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_20059d2a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Company X\u0027s management, through the decision-making process involving Supervisor B and organizational hierarchy, formally rejects Engineer A\u0027s recommendation for additional safety testing, citing cost and schedule concerns",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A submits formal recommendation for additional safety testing based on observed inconsistencies",
      "proeth:element": "Recommend Additional Safety Testing (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Supervisor B and Company X organizational hierarchy evaluate the recommendation against business constraints",
      "proeth:element": "Management Review Process",
      "proeth:step": 2
    },
    {
      "proeth:description": "Management determines that cost and schedule concerns outweigh the precautionary safety recommendation",
      "proeth:element": "Cost-Schedule Prioritization Decision",
      "proeth:step": 3
    },
    {
      "proeth:description": "Company X formally communicates rejection of Engineer A\u0027s recommendation",
      "proeth:element": "Reject Additional Testing Recommendation (Action 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The rejection takes effect, leaving the safety inconsistency unaddressed and the product on its original development/release trajectory",
      "proeth:element": "Additional Testing Rejected (Event 2)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Recommend Additional Safety Testing (Action 1)",
  "proeth:counterfactual": "Without Engineer A\u0027s recommendation, there would have been no formal decision to reject; without management\u0027s cost-driven priorities, the recommendation might have been accepted; either change could have altered the outcome",
  "proeth:effect": "Reject Additional Testing Recommendation (Action 2) \u2192 Additional Testing Rejected (Event 2)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s formal recommendation triggering a management decision point",
    "Company X management\u0027s authority to override engineering recommendations",
    "Organizational prioritization of cost and schedule over precautionary safety measures",
    "Absence of mandatory regulatory requirement compelling additional testing"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Company X Management (including Supervisor B and organizational decision-makers)",
  "proeth:sufficientFactors": [
    "Management authority + cost/schedule pressure + lack of binding regulatory mandate = rejection of recommendation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_d18e8c1e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "At an unspecified point after Company X rejected the additional testing recommendation, Engineer A made the decision to resign from Company X",
  "proeth:causalSequence": [
    {
      "proeth:description": "Company X formally rejects safety recommendation, leaving Engineer A in an unresolved ethical conflict",
      "proeth:element": "Additional Testing Rejected (Event 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A evaluates remaining internal options and determines continued employment is incompatible with professional ethics obligations",
      "proeth:element": "Engineer A\u0027s Ethical Assessment",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A makes the volitional decision to resign rather than remain complicit in the unaddressed safety risk",
      "proeth:element": "Resign From Company X (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Resignation takes effect, formally ending Engineer A\u0027s employment and direct access to company information and internal remedies",
      "proeth:element": "Engineer A Departs Company (Event 3)",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Additional Testing Rejected (Event 2)",
  "proeth:counterfactual": "Had Company X accepted the recommendation or offered a compromise safety review, Engineer A may not have resigned; the rejection was the precipitating condition for the departure",
  "proeth:effect": "Resign From Company X (Action 3) \u2192 Engineer A Departs Company (Event 3)",
  "proeth:necessaryFactors": [
    "Company X\u0027s rejection of the safety recommendation creating an ethical conflict for Engineer A",
    "Engineer A\u0027s professional and ethical standards being incompatible with continuing under the rejection decision",
    "Engineer A\u0027s assessment that internal remedies were exhausted or unavailable"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (resignation decision) with shared responsibility attributable to Company X (creating the ethical conflict)",
  "proeth:sufficientFactors": [
    "Unresolved ethical conflict + perceived exhaustion of internal remedies + Engineer A\u0027s professional integrity = resignation decision"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_405b0ae3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "One year after resigning from Company X, upon learning that the relevant government agency announced a public safety standards hearing, Engineer A faces an active ethical deliberation about whether to testify",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A leaves Company X with knowledge of unresolved safety inconsistency",
      "proeth:element": "Engineer A Departs Company (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "One year later, government agency announces public safety standards hearing relevant to the product",
      "proeth:element": "Public Safety Hearing Announced (Event 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A becomes aware of the hearing announcement, recognizing its relevance to the unresolved safety concern",
      "proeth:element": "Engineer A Learns of Hearing",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A enters active ethical deliberation weighing professional duty to public safety against competing obligations",
      "proeth:element": "Consider Testifying at Public Hearing (Action 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A is in a state of active ethical deliberation, facing the decision of whether to testify with material safety knowledge",
      "proeth:element": "Engineer A Faces Testimony Decision (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Public Safety Hearing Announced (Event 4)",
  "proeth:counterfactual": "Without the public hearing announcement, Engineer A would have had no immediate forum or trigger for testimony; without material knowledge of the safety issue, testimony would have been irrelevant",
  "proeth:effect": "Consider Testifying at Public Hearing (Action 4) \u2192 Engineer A Faces Testimony Decision (Event 5)",
  "proeth:necessaryFactors": [
    "Government agency announcing a public safety hearing relevant to the product in question",
    "Engineer A becoming aware of the hearing announcement",
    "Engineer A possessing material knowledge about the safety inconsistency that would be relevant to the hearing",
    "Sufficient time elapsed (one year) creating temporal and employment distance from Company X"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (deliberation and ultimate testimony decision) with the government agency creating the opportunity through the hearing announcement",
  "proeth:sufficientFactors": [
    "Relevant public hearing + Engineer A\u0027s awareness + possession of material safety knowledge = ethical deliberation about testimony obligation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_a05e442d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "In precedent case BER 76-4, Engineer Doe\u0027s verbal report of findings to the client results in a conflict arising from the client\u0027s response to those findings",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer Doe discovers findings with significant implications for client or public safety",
      "proeth:element": "Engineer Doe Identifies Material Findings",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer Doe chooses to advise XYZ Corporation verbally rather than through formal written documentation",
      "proeth:element": "Verbally Report Findings to Client (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "XYZ Corporation receives findings and makes decisions that diverge from Engineer Doe\u0027s professional recommendations",
      "proeth:element": "XYZ Corporation\u0027s Response",
      "proeth:step": 3
    },
    {
      "proeth:description": "The divergence between Engineer Doe\u0027s findings and XYZ Corporation\u0027s response creates a formal ethical conflict",
      "proeth:element": "BER 76-4 Client Conflict Arises (Event 6)",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Verbally Report Findings to Client (Action 5 - BER 76-4)",
  "proeth:counterfactual": "Had Engineer Doe not reported findings, the conflict may have been deferred but public safety risk would have remained; had findings been reported in writing, the conflict might have been more formally structured with clearer accountability",
  "proeth:effect": "BER 76-4 Client Conflict Arises (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer Doe possessing findings material to client safety or interests",
    "Engineer Doe choosing verbal rather than written reporting, limiting formal documentation",
    "XYZ Corporation receiving the findings and making a decision that created conflict",
    "Divergence between Engineer Doe\u0027s professional assessment and XYZ Corporation\u0027s preferred course of action"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer Doe (reporting decision and method) with shared responsibility to XYZ Corporation (response to findings)",
  "proeth:sufficientFactors": [
    "Verbal disclosure of adverse findings + client\u0027s conflicting interests + absence of formal written record = conditions for client conflict"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_ddce0b78",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "In precedent case BER 76-4, upon learning that XYZ Corporation had called a public hearing and presented findings, Engineer Doe reported findings to the regulatory authority",
  "proeth:causalSequence": [
    {
      "proeth:description": "Conflict between Engineer Doe\u0027s findings and XYZ Corporation\u0027s response creates unresolved safety and ethical tension",
      "proeth:element": "BER 76-4 Client Conflict Arises (Event 6)",
      "proeth:step": 1
    },
    {
      "proeth:description": "XYZ Corporation escalates the matter by calling a public hearing and presenting its own version of findings",
      "proeth:element": "XYZ Corporation Calls Public Hearing",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer Doe becomes aware that XYZ Corporation is publicly presenting findings that may diverge from his professional assessment",
      "proeth:element": "Engineer Doe Learns of Public Hearing",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer Doe determines that the public nature of the hearing and the divergence in findings creates an obligation to report to the regulatory authority",
      "proeth:element": "Report Findings to Regulatory Authority (Action 6)",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "BER 76-4 Client Conflict Arises (Event 6)",
  "proeth:counterfactual": "Without XYZ Corporation calling a public hearing, Engineer Doe might not have escalated to regulatory reporting; the public hearing created both the trigger and the justification for external disclosure",
  "proeth:effect": "Report Findings to Regulatory Authority (Action 6 - BER 76-4)",
  "proeth:necessaryFactors": [
    "XYZ Corporation calling a public hearing that triggered a new public forum",
    "Engineer Doe learning of the public hearing and XYZ Corporation\u0027s presentation of findings",
    "Engineer Doe\u0027s assessment that XYZ Corporation\u0027s public presentation was incomplete or misleading relative to his own findings",
    "Existence of a regulatory authority with jurisdiction to receive the report"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer Doe (reporting decision) with XYZ Corporation\u0027s public hearing action serving as the proximate trigger",
  "proeth:sufficientFactors": [
    "Client\u0027s public hearing action + Engineer Doe\u0027s awareness of divergent findings + regulatory authority availability = obligation and decision to report externally"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/142#",
    "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/142#CausalChain_fe22f767",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "In precedent case BER 08-10, after learning one month later that nothing had been done to correct the identified safety issue, the engineer escalated with an external reporting threat",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer identifies and internally reports a safety concern to the organization",
      "proeth:element": "Initial Internal Safety Report (BER 08-10)",
      "proeth:step": 1
    },
    {
      "proeth:description": "One month passes with no corrective action taken by the organization in response to the safety report",
      "proeth:element": "Organization\u0027s Inaction (One Month)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer learns that nothing has been done to correct the identified safety issue",
      "proeth:element": "Engineer Monitors and Confirms Inaction",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer escalates by threatening external reporting to compel organizational action",
      "proeth:element": "Escalate with External Reporting Threat (Action 7)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Organization faces pressure to act on safety concern or face external regulatory/public scrutiny",
      "proeth:element": "Organizational Response to Escalation Threat",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Escalate with External Reporting Threat (Action 7 - BER 08-10)",
  "proeth:counterfactual": "Had the organization taken corrective action within the one-month period, the escalation threat would not have been necessary; the inaction was the direct precipitating cause of escalation",
  "proeth:effect": "Systemic pressure on organizations to address safety concerns before public escalation",
  "proeth:necessaryFactors": [
    "Prior internal reporting of safety concern going unaddressed for a defined period (one month)",
    "Engineer\u0027s continued monitoring of whether corrective action was taken",
    "Engineer\u0027s knowledge of external reporting channels and willingness to use them",
    "Organization\u0027s failure to act creating the conditions requiring escalation"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer in BER 08-10 (escalation decision) with primary causal responsibility attributable to the organization\u0027s failure to act on the initial safety report",
  "proeth:sufficientFactors": [
    "Unaddressed safety concern + elapsed time + organization\u0027s inaction + engineer\u0027s awareness of external channels = escalation with external reporting threat"
  ],
  "proeth:withinAgentControl": true
}