PASS 3: Temporal Dynamics
Case 18: Professional Responsibility if Appropriate Authority Fails to Act
Timeline Overview
OWL-Time Temporal Structure 15 relations time: = w3.org/2006/time
Extracted Actions (6)
Volitional professional decisions with intentions and ethical contextDescription: Engineer B escalated beyond the client by sending the original technical report and a cover letter directly to the water supply division of the State Department of the Environment, invoking the appropriate regulatory authority to review the public health risk. This was a deliberate decision to go outside the client relationship to a public authority.
Temporal Marker: After written warning to commissioners; prior to discharge by MWC
Mental State: deliberate
Intended Outcome: Engage the appropriate regulatory authority with jurisdiction over public water supply safety to review and potentially intervene in MWC's decision to delay treatment improvements
Fulfills Obligations:
- Reported endangerment of public health to appropriate public authority
- Fulfilled highest-level professional ethical obligation under NSPE Code
- Completed the required escalation sequence from client notification to regulatory notification
- Protected public health and safety by engaging oversight authority
Guided By Principles:
- Public health and safety paramount
- Duty to report to appropriate authorities
- Professional courage
- Whistleblower obligation
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Having exhausted client-level channels without effect, Engineer B was motivated by the recognition that the public's right to safe water supersedes the client relationship. Notifying the State Department of the Environment was an act of professional conscience: Engineer B determined that when a client proceeds with a decision that poses foreseeable public health harm, the engineer's duty to the public requires engagement with the authority empowered to intervene. This action reflects the highest expression of NSPE Canon 1.
Ethical Tension: This is the sharpest ethical tension in the scenario. Going outside the client relationship to a regulatory authority is a direct breach of client confidentiality norms and professional loyalty expectations, yet NSPE ethics explicitly permit — and in some readings require — such disclosure when public safety is at stake. Engineer B must weigh the near-certain professional consequences (termination, reputational risk within the industry) against the moral imperative to protect public health.
Learning Significance: This action is the ethical climax of the escalation sequence and the most powerful teaching moment in the case. Students learn that professional codes of ethics are not merely aspirational but operational: they provide explicit authorization to override client confidentiality when public safety demands it. The action also demonstrates that ethical courage has professional costs and that fulfilling one's highest duty may require accepting those costs.
Stakes: If Engineer B notifies the regulator, the professional relationship is almost certainly destroyed, but the public authority with power to prevent harm is now informed. If Engineer B does not notify the regulator, the last realistic opportunity to protect the public through institutional channels is forfeited, and Engineer B becomes a passive witness to foreseeable harm. The regulator's response — or failure to respond adequately — will determine whether the escalation was sufficient.
Decision Point: Yes - Story can branch here
- Consult with ABC Engineers before contacting the regulator, seeking the firm's authorization or at least awareness before acting unilaterally
- Contact a public health advocacy organization or the media rather than the regulatory authority, to generate public pressure
- Decline to contact the regulator but document the decision and reasoning, treating the written warning to commissioners as the final professional obligation
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Action_Regulatory_Authority_Notification",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Consult with ABC Engineers before contacting the regulator, seeking the firm\u0027s authorization or at least awareness before acting unilaterally",
"Contact a public health advocacy organization or the media rather than the regulatory authority, to generate public pressure",
"Decline to contact the regulator but document the decision and reasoning, treating the written warning to commissioners as the final professional obligation"
],
"proeth-scenario:characterMotivation": "Having exhausted client-level channels without effect, Engineer B was motivated by the recognition that the public\u0027s right to safe water supersedes the client relationship. Notifying the State Department of the Environment was an act of professional conscience: Engineer B determined that when a client proceeds with a decision that poses foreseeable public health harm, the engineer\u0027s duty to the public requires engagement with the authority empowered to intervene. This action reflects the highest expression of NSPE Canon 1.",
"proeth-scenario:consequencesIfAlternative": [
"Consulting ABC Engineers first might have been professionally courteous but risked the firm instructing Engineer B not to contact the regulator for commercial reasons, potentially blocking the escalation entirely",
"Contacting the media would have been a more aggressive and less institutionally appropriate channel, potentially generating public alarm without the technical review process that regulatory notification triggers; it might also have exposed Engineer B to legal risk",
"Treating the commissioner letter as the final obligation would have been ethically inadequate given that MWC had already demonstrated its intent to ignore the warning; it would have left the public without the protection that regulatory review could provide"
],
"proeth-scenario:decisionSignificance": "This action is the ethical climax of the escalation sequence and the most powerful teaching moment in the case. Students learn that professional codes of ethics are not merely aspirational but operational: they provide explicit authorization to override client confidentiality when public safety demands it. The action also demonstrates that ethical courage has professional costs and that fulfilling one\u0027s highest duty may require accepting those costs.",
"proeth-scenario:ethicalTension": "This is the sharpest ethical tension in the scenario. Going outside the client relationship to a regulatory authority is a direct breach of client confidentiality norms and professional loyalty expectations, yet NSPE ethics explicitly permit \u2014 and in some readings require \u2014 such disclosure when public safety is at stake. Engineer B must weigh the near-certain professional consequences (termination, reputational risk within the industry) against the moral imperative to protect public health.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "If Engineer B notifies the regulator, the professional relationship is almost certainly destroyed, but the public authority with power to prevent harm is now informed. If Engineer B does not notify the regulator, the last realistic opportunity to protect the public through institutional channels is forfeited, and Engineer B becomes a passive witness to foreseeable harm. The regulator\u0027s response \u2014 or failure to respond adequately \u2014 will determine whether the escalation was sufficient.",
"proeth:description": "Engineer B escalated beyond the client by sending the original technical report and a cover letter directly to the water supply division of the State Department of the Environment, invoking the appropriate regulatory authority to review the public health risk. This was a deliberate decision to go outside the client relationship to a public authority.",
"proeth:foreseenUnintendedEffects": [
"Likely to result in discharge from the project by MWC",
"Could create legal or professional complications for ABC Engineers",
"May trigger regulatory review that delays or modifies MWC\u0027s plan",
"Establishes Engineer B\u0027s fulfillment of professional ethical obligations"
],
"proeth:fulfillsObligation": [
"Reported endangerment of public health to appropriate public authority",
"Fulfilled highest-level professional ethical obligation under NSPE Code",
"Completed the required escalation sequence from client notification to regulatory notification",
"Protected public health and safety by engaging oversight authority"
],
"proeth:guidedByPrinciple": [
"Public health and safety paramount",
"Duty to report to appropriate authorities",
"Professional courage",
"Whistleblower obligation"
],
"proeth:hasAgent": "Engineer B (Retained Professional Engineer via ABC Engineers)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Faithful agency to employer/client vs. paramount public health and safety obligation",
"proeth:resolutionReasoning": "The NSPE Code establishes that public health and safety is paramount and overrides faithful agency obligations when those obligations would result in endangerment of the public; Engineer B correctly prioritized regulatory notification"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Engage the appropriate regulatory authority with jurisdiction over public water supply safety to review and potentially intervene in MWC\u0027s decision to delay treatment improvements",
"proeth:requiresCapability": [
"Regulatory process knowledge",
"Professional correspondence",
"Understanding of appropriate escalation pathways",
"Water supply regulatory framework knowledge"
],
"proeth:temporalMarker": "After written warning to commissioners; prior to discharge by MWC",
"proeth:violatesObligation": [
"Potential tension with duty as faithful agent of ABC Engineers if ABC did not concur with escalation"
],
"proeth:withinCompetence": true,
"rdfs:label": "Regulatory Authority Notification"
}
Description: After reading in the newspaper that the State Department of the Environment approved the water source change with only a five-year treatment implementation plan, Engineer B deliberately considered whether continuing professional ethical obligations existed and what further actions, if any, were warranted. This deliberation itself constitutes a volitional decision point about whether to act further.
Temporal Marker: Several months after discharge; after reading newspaper report of regulatory approval
Mental State: deliberate
Intended Outcome: Determine whether additional professional or personal actions were ethically required or appropriate given that the regulatory authority had approved a plan Engineer B assessed as inadequate to prevent public harm
Fulfills Obligations:
- Recognized the boundary between fulfilled professional obligations and personal citizen choices
- Engaged in good-faith ethical deliberation about scope of continuing obligations
Guided By Principles:
- Public health and safety paramount
- Professional integrity
- Recognition of limits of professional vs. personal obligation
- Ethical deliberation as a professional responsibility
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer B is motivated by a lingering sense of professional responsibility and moral unease. Having taken significant escalatory actions, Engineer B now learns that the regulatory process produced an outcome — a five-year implementation delay — that still leaves the public exposed to the risk identified in the original report. The deliberation reflects Engineer B's recognition that professional ethics do not end with a regulatory decision and that the question of 'have I done enough?' must be actively re-examined in light of new information.
Ethical Tension: The core tension is between the reasonable expectation that regulatory approval closes the engineer's obligation and the persistent reality that the approved plan still embodies the risk Engineer B warned against. Engineer B must weigh the exhaustion of available formal channels against the possibility that additional actions — further regulatory appeals, public disclosure, professional society reporting — remain available and ethically required. There is also a personal tension between self-preservation and continued advocacy.
Learning Significance: This action teaches students that professional ethical obligations are dynamic, not static. An engineer's duty does not terminate when a client dismisses them or when a regulator acts. Students learn to ask: 'Given what I now know, is there a remaining action that a reasonable engineer with my knowledge and my obligations to the public should take?' This deliberation models the ongoing nature of ethical responsibility in professional practice.
Stakes: If Engineer B concludes that obligations are fulfilled and takes no further action, the public remains exposed to a risk that Engineer B uniquely understands, and the five-year delay may result in lead exposure harm that further action might have prevented or accelerated remediation of. If Engineer B acts further — by appealing to higher regulatory authority, engaging professional societies, or seeking public disclosure — there are additional professional and legal risks but also the possibility of stronger public protection.
Decision Point: Yes - Story can branch here
- Conclude that notification of the State Department of the Environment fulfilled all professional obligations and take no further action, accepting the regulatory outcome as the system's determination
- Contact the state-level professional engineering society or ethics board to seek guidance on whether further action is required, using institutional resources to resolve the deliberation
- Prepare and submit a formal appeal or supplemental technical comment to the State Department of the Environment challenging the adequacy of the five-year implementation plan, citing the specific health risks documented in the original report
Narrative Role: resolution
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Action_Post-Approval_Further_Action_Deliberation",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Conclude that notification of the State Department of the Environment fulfilled all professional obligations and take no further action, accepting the regulatory outcome as the system\u0027s determination",
"Contact the state-level professional engineering society or ethics board to seek guidance on whether further action is required, using institutional resources to resolve the deliberation",
"Prepare and submit a formal appeal or supplemental technical comment to the State Department of the Environment challenging the adequacy of the five-year implementation plan, citing the specific health risks documented in the original report"
],
"proeth-scenario:characterMotivation": "Engineer B is motivated by a lingering sense of professional responsibility and moral unease. Having taken significant escalatory actions, Engineer B now learns that the regulatory process produced an outcome \u2014 a five-year implementation delay \u2014 that still leaves the public exposed to the risk identified in the original report. The deliberation reflects Engineer B\u0027s recognition that professional ethics do not end with a regulatory decision and that the question of \u0027have I done enough?\u0027 must be actively re-examined in light of new information.",
"proeth-scenario:consequencesIfAlternative": [
"Concluding obligations are fulfilled is defensible under many readings of professional codes, particularly given the extensive prior escalation; however, it risks moral residue if lead exposure harm occurs during the five-year delay and Engineer B had information that might have shortened it",
"Engaging the professional society would be a prudent, institutionally supported path that provides ethical guidance without unilateral action; it might also create a record that protects Engineer B professionally while potentially generating collective pressure on the regulatory outcome",
"Submitting a formal technical appeal would be the most assertive remaining action and the most directly protective of public health; it would also carry the highest professional risk and might be dismissed if the regulatory record already reflects Engineer B\u0027s earlier submission, but it would ensure the engineer\u0027s ongoing dissent is formally documented"
],
"proeth-scenario:decisionSignificance": "This action teaches students that professional ethical obligations are dynamic, not static. An engineer\u0027s duty does not terminate when a client dismisses them or when a regulator acts. Students learn to ask: \u0027Given what I now know, is there a remaining action that a reasonable engineer with my knowledge and my obligations to the public should take?\u0027 This deliberation models the ongoing nature of ethical responsibility in professional practice.",
"proeth-scenario:ethicalTension": "The core tension is between the reasonable expectation that regulatory approval closes the engineer\u0027s obligation and the persistent reality that the approved plan still embodies the risk Engineer B warned against. Engineer B must weigh the exhaustion of available formal channels against the possibility that additional actions \u2014 further regulatory appeals, public disclosure, professional society reporting \u2014 remain available and ethically required. There is also a personal tension between self-preservation and continued advocacy.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "resolution",
"proeth-scenario:stakes": "If Engineer B concludes that obligations are fulfilled and takes no further action, the public remains exposed to a risk that Engineer B uniquely understands, and the five-year delay may result in lead exposure harm that further action might have prevented or accelerated remediation of. If Engineer B acts further \u2014 by appealing to higher regulatory authority, engaging professional societies, or seeking public disclosure \u2014 there are additional professional and legal risks but also the possibility of stronger public protection.",
"proeth:description": "After reading in the newspaper that the State Department of the Environment approved the water source change with only a five-year treatment implementation plan, Engineer B deliberately considered whether continuing professional ethical obligations existed and what further actions, if any, were warranted. This deliberation itself constitutes a volitional decision point about whether to act further.",
"proeth:foreseenUnintendedEffects": [
"Further action could expose Engineer B to professional or legal risk without ABC Engineers\u0027 support",
"Inaction could result in continued public health risk if the five-year timeline proves harmful",
"Further action might be characterized as personal advocacy rather than professional obligation"
],
"proeth:fulfillsObligation": [
"Recognized the boundary between fulfilled professional obligations and personal citizen choices",
"Engaged in good-faith ethical deliberation about scope of continuing obligations"
],
"proeth:guidedByPrinciple": [
"Public health and safety paramount",
"Professional integrity",
"Recognition of limits of professional vs. personal obligation",
"Ethical deliberation as a professional responsibility"
],
"proeth:hasAgent": "Engineer B (Retained Professional Engineer, now discharged from project)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Fulfilled professional ethical obligations vs. ongoing personal moral concern about public health risk",
"proeth:resolutionReasoning": "BER analysis concludes that Engineer B fulfilled professional obligations through regulatory notification and that any further action\u2014such as public communication, advocacy, or contacting other authorities\u2014would be a personal citizen choice rather than a required professional ethical obligation"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Determine whether additional professional or personal actions were ethically required or appropriate given that the regulatory authority had approved a plan Engineer B assessed as inadequate to prevent public harm",
"proeth:requiresCapability": [
"Ethical reasoning",
"Self-assessment of professional obligation scope",
"Understanding of BER precedent and NSPE Code limits",
"Assessment of regulatory adequacy"
],
"proeth:temporalMarker": "Several months after discharge; after reading newspaper report of regulatory approval",
"proeth:withinCompetence": true,
"rdfs:label": "Post-Approval Further Action Deliberation"
}
Description: Engineer B accepted retention by ABC Engineers to evaluate the feasibility and implications of changing MWC's water source from remote reservoirs to a local river. This constitutes a volitional professional commitment to conduct an independent technical assessment.
Temporal Marker: Initial engagement phase, prior to report completion
Mental State: deliberate
Intended Outcome: Provide objective technical evaluation of water source change for cost reduction purposes
Fulfills Obligations:
- Accepted work within area of professional competence
- Agreed to serve as faithful agent of ABC Engineers within ethical limits
Guided By Principles:
- Competence
- Professional integrity
- Faithful agency to employer
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer B accepted the retention as a legitimate professional engagement, motivated by the opportunity to apply technical expertise in evaluating a significant infrastructure decision. There was likely also a professional duty to serve the client competently and an implicit expectation that the findings would be used responsibly to protect public welfare.
Ethical Tension: The tension at this stage is latent but foundational: accepting the engagement creates a dual obligation to the client (ABC Engineers and MWC) and to the broader public whose health depends on the water supply. Engineer B may not yet foresee that these obligations will conflict, but the acceptance itself sets the ethical machinery in motion.
Learning Significance: This action teaches students that accepting a professional engagement is never ethically neutral. Engineers implicitly commit to honest, independent findings regardless of whether those findings serve the client's preferred outcome. The moment of acceptance is the moment professional integrity is pledged.
Stakes: If Engineer B accepts the work and later compromises findings to please the client, public health is endangered and professional integrity is forfeited. If the engagement is conducted honestly, it may produce findings the client dislikes, risking the professional relationship from the outset.
Decision Point: Yes - Story can branch here
- Decline the engagement due to anticipated pressure to validate a cost-cutting decision regardless of safety findings
- Accept the engagement but negotiate explicit contractual language guaranteeing independence of findings
- Accept the engagement but limit scope to feasibility only, excluding safety recommendations
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Action_Water_Source_Evaluation_Accepted",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the engagement due to anticipated pressure to validate a cost-cutting decision regardless of safety findings",
"Accept the engagement but negotiate explicit contractual language guaranteeing independence of findings",
"Accept the engagement but limit scope to feasibility only, excluding safety recommendations"
],
"proeth-scenario:characterMotivation": "Engineer B accepted the retention as a legitimate professional engagement, motivated by the opportunity to apply technical expertise in evaluating a significant infrastructure decision. There was likely also a professional duty to serve the client competently and an implicit expectation that the findings would be used responsibly to protect public welfare.",
"proeth-scenario:consequencesIfAlternative": [
"Declining would have removed Engineer B from the situation entirely, potentially allowing a less scrupulous consultant to conduct the evaluation without any safety-based pushback, leaving the public more vulnerable",
"Negotiating independence clauses upfront might have provided contractual protection when MWC later rejected the findings, giving Engineer B stronger legal and professional standing during the dispute",
"Limiting scope to feasibility without safety recommendations would have been a professional failure from the start, producing an incomplete and potentially misleading report that omitted the most critical public health dimension"
],
"proeth-scenario:decisionSignificance": "This action teaches students that accepting a professional engagement is never ethically neutral. Engineers implicitly commit to honest, independent findings regardless of whether those findings serve the client\u0027s preferred outcome. The moment of acceptance is the moment professional integrity is pledged.",
"proeth-scenario:ethicalTension": "The tension at this stage is latent but foundational: accepting the engagement creates a dual obligation to the client (ABC Engineers and MWC) and to the broader public whose health depends on the water supply. Engineer B may not yet foresee that these obligations will conflict, but the acceptance itself sets the ethical machinery in motion.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "If Engineer B accepts the work and later compromises findings to please the client, public health is endangered and professional integrity is forfeited. If the engagement is conducted honestly, it may produce findings the client dislikes, risking the professional relationship from the outset.",
"proeth:description": "Engineer B accepted retention by ABC Engineers to evaluate the feasibility and implications of changing MWC\u0027s water source from remote reservoirs to a local river. This constitutes a volitional professional commitment to conduct an independent technical assessment.",
"proeth:foreseenUnintendedEffects": [
"Findings might conflict with client\u0027s cost-reduction goals",
"Report conclusions could create professional tension with MWC"
],
"proeth:fulfillsObligation": [
"Accepted work within area of professional competence",
"Agreed to serve as faithful agent of ABC Engineers within ethical limits"
],
"proeth:guidedByPrinciple": [
"Competence",
"Professional integrity",
"Faithful agency to employer"
],
"proeth:hasAgent": "Engineer B (Retained Professional Engineer via ABC Engineers)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client goal alignment vs. independent professional judgment",
"proeth:resolutionReasoning": "Engineer B accepted the engagement, implicitly committing to objective evaluation over client-favorable outcomes"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Provide objective technical evaluation of water source change for cost reduction purposes",
"proeth:requiresCapability": [
"Water systems engineering",
"Water quality assessment",
"Lead leaching risk analysis",
"Public health impact evaluation"
],
"proeth:temporalMarker": "Initial engagement phase, prior to report completion",
"proeth:withinCompetence": true,
"rdfs:label": "Water Source Evaluation Accepted"
}
Description: Engineer B completed and issued a professional report recommending that water treatment improvements must precede or accompany the water source change to prevent lead leaching into the public water supply. This was a deliberate professional judgment translating technical findings into a concrete safety-based recommendation.
Temporal Marker: Report completion phase, after evaluation and prior to MWC decision
Mental State: deliberate
Intended Outcome: Inform MWC and ABC Engineers of the technical necessity of treatment improvements as a precondition to safe water source transition
Fulfills Obligations:
- Held paramount the safety and health of the public
- Provided honest and objective professional opinion
- Acted as faithful agent by delivering technically sound findings
- Issued findings based on competent analysis
Guided By Principles:
- Public health and safety paramount
- Objectivity
- Honesty
- Professional competence
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer B was motivated by professional integrity and a duty to translate technical knowledge into actionable guidance. Having identified a concrete and foreseeable risk — lead leaching caused by changes in water chemistry — Engineer B felt obligated to communicate that risk clearly and recommend the corrective measure within the client's control. The recommendation was the core deliverable and the primary vehicle for fulfilling the engagement's purpose.
Ethical Tension: The recommendation directly conflicts with the client's cost-reduction objective. Recommending treatment improvements prior to the source change adds cost and delay, undermining the financial rationale for the project. Engineer B must choose between softening the findings to preserve the client relationship or issuing an honest, potentially unwelcome assessment. NSPE Canon 1 (hold paramount public safety) is in direct tension with client service obligations.
Learning Significance: This action is a cornerstone teaching moment: the professional report is not merely a technical document but an ethical instrument. Students learn that honest, evidence-based recommendations must not be diluted to match client preferences, and that the report creates a formal record of the engineer's professional judgment that carries lasting ethical and legal significance.
Stakes: If the recommendation is honest and clear, it may be rejected by the client but creates a documented safety warning. If the recommendation is softened or omitted to please the client, Engineer B becomes complicit in a decision that could cause widespread lead poisoning in the public water supply. The report's clarity directly determines the strength of all subsequent escalation actions.
Decision Point: Yes - Story can branch here
- Issue a report that presents treatment improvements as optional or advisory rather than necessary prerequisites
- Issue the report with the full recommendation but include a cost-benefit framing that makes delaying treatment appear more defensible
- Refuse to complete the report until MWC commits in writing to implementing treatment improvements
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Action_Risk-Based_Report_Recommendation_Issued",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Issue a report that presents treatment improvements as optional or advisory rather than necessary prerequisites",
"Issue the report with the full recommendation but include a cost-benefit framing that makes delaying treatment appear more defensible",
"Refuse to complete the report until MWC commits in writing to implementing treatment improvements"
],
"proeth-scenario:characterMotivation": "Engineer B was motivated by professional integrity and a duty to translate technical knowledge into actionable guidance. Having identified a concrete and foreseeable risk \u2014 lead leaching caused by changes in water chemistry \u2014 Engineer B felt obligated to communicate that risk clearly and recommend the corrective measure within the client\u0027s control. The recommendation was the core deliverable and the primary vehicle for fulfilling the engagement\u0027s purpose.",
"proeth-scenario:consequencesIfAlternative": [
"Framing improvements as optional would have given MWC cover to proceed without them while claiming the engineer endorsed the approach, directly endangering the public and compromising Engineer B\u0027s professional standing",
"Embedding the recommendation in a cost-benefit framing might have made the report more palatable but could have obscured the severity of the safety risk, weakening the basis for later regulatory escalation",
"Withholding the report pending commitment would have been an unusual but defensible position; however, it might have led to immediate termination before the safety findings were documented at all, leaving no professional record"
],
"proeth-scenario:decisionSignificance": "This action is a cornerstone teaching moment: the professional report is not merely a technical document but an ethical instrument. Students learn that honest, evidence-based recommendations must not be diluted to match client preferences, and that the report creates a formal record of the engineer\u0027s professional judgment that carries lasting ethical and legal significance.",
"proeth-scenario:ethicalTension": "The recommendation directly conflicts with the client\u0027s cost-reduction objective. Recommending treatment improvements prior to the source change adds cost and delay, undermining the financial rationale for the project. Engineer B must choose between softening the findings to preserve the client relationship or issuing an honest, potentially unwelcome assessment. NSPE Canon 1 (hold paramount public safety) is in direct tension with client service obligations.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If the recommendation is honest and clear, it may be rejected by the client but creates a documented safety warning. If the recommendation is softened or omitted to please the client, Engineer B becomes complicit in a decision that could cause widespread lead poisoning in the public water supply. The report\u0027s clarity directly determines the strength of all subsequent escalation actions.",
"proeth:description": "Engineer B completed and issued a professional report recommending that water treatment improvements must precede or accompany the water source change to prevent lead leaching into the public water supply. This was a deliberate professional judgment translating technical findings into a concrete safety-based recommendation.",
"proeth:foreseenUnintendedEffects": [
"Recommendation adds cost and complexity contrary to client\u0027s cost-reduction goal",
"MWC may reject or delay the recommendation",
"Could create friction with client relationship"
],
"proeth:fulfillsObligation": [
"Held paramount the safety and health of the public",
"Provided honest and objective professional opinion",
"Acted as faithful agent by delivering technically sound findings",
"Issued findings based on competent analysis"
],
"proeth:guidedByPrinciple": [
"Public health and safety paramount",
"Objectivity",
"Honesty",
"Professional competence"
],
"proeth:hasAgent": "Engineer B (Retained Professional Engineer via ABC Engineers)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client cost-reduction goal vs. public safety mandate",
"proeth:resolutionReasoning": "Public health and safety obligation took precedence; Engineer B issued the risk-based recommendation regardless of its conflict with client\u0027s cost goals"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Inform MWC and ABC Engineers of the technical necessity of treatment improvements as a precondition to safe water source transition",
"proeth:requiresCapability": [
"Water quality engineering",
"Lead leaching risk assessment",
"Technical report writing",
"Regulatory standards interpretation"
],
"proeth:temporalMarker": "Report completion phase, after evaluation and prior to MWC decision",
"proeth:withinCompetence": true,
"rdfs:label": "Risk-Based Report Recommendation Issued"
}
Description: Following MWC's decision to proceed with the water source change while delaying treatment improvements, Engineer B chose to verbally warn Water Commissioners at a public meeting of the public health and safety risks. This was a deliberate escalation beyond the written report to ensure decision-makers personally received the safety warning.
Temporal Marker: After MWC voted to proceed with delayed treatment; at public commission meeting
Mental State: deliberate
Intended Outcome: Ensure Water Commissioners personally understood the health and safety risks of proceeding without concurrent treatment improvements; create a documented public record of the warning
Fulfills Obligations:
- Notified client of consequences of decisions overriding Engineer B's professional judgment
- Took affirmative steps to protect public health beyond written report
- Fulfilled duty to advise decision-makers directly of safety risks
Guided By Principles:
- Public health and safety paramount
- Professional courage
- Transparency
- Duty to advise client of consequences
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Upon learning that MWC intended to proceed with the source change while deferring treatment improvements, Engineer B was motivated by an urgent duty to ensure that decision-makers personally and directly understood the health risks they were accepting on behalf of the public. The public meeting provided a venue where commissioners could not later claim ignorance. Engineer B may also have hoped that direct, face-to-face communication would carry persuasive weight that the written report had not.
Ethical Tension: Speaking out at a public meeting escalates the conflict with the client and risks professional embarrassment or retaliation, yet silence in the face of a known public health risk would violate the engineer's paramount duty to public safety. There is also a tension between respecting the client's autonomy to make business decisions and the engineer's obligation not to be passive when those decisions create foreseeable harm to third parties.
Learning Significance: This action illustrates the principle that written documentation alone may be insufficient when public safety is at stake. Students learn that engineers have an affirmative duty to communicate risks through multiple channels and to ensure that warnings are actually received and understood, not merely transmitted. It also demonstrates the personal courage required to speak uncomfortable truths in a public forum.
Stakes: If Engineer B speaks out, the professional relationship with MWC is further strained and termination becomes more likely. If Engineer B remains silent, the commissioners may later claim they were unaware of the risks, and Engineer B loses a critical opportunity to protect the public through direct communication. The public nature of the meeting also means the warning enters the civic record.
Decision Point: Yes - Story can branch here
- Remain silent at the public meeting and rely solely on the written report to convey the warning
- Request a private meeting with commissioners rather than raising concerns in a public forum
- Attend the public meeting but limit remarks to technical observations without explicitly characterizing MWC's decision as unsafe
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Action_Verbal_Warning_to_Commissioners",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Remain silent at the public meeting and rely solely on the written report to convey the warning",
"Request a private meeting with commissioners rather than raising concerns in a public forum",
"Attend the public meeting but limit remarks to technical observations without explicitly characterizing MWC\u0027s decision as unsafe"
],
"proeth-scenario:characterMotivation": "Upon learning that MWC intended to proceed with the source change while deferring treatment improvements, Engineer B was motivated by an urgent duty to ensure that decision-makers personally and directly understood the health risks they were accepting on behalf of the public. The public meeting provided a venue where commissioners could not later claim ignorance. Engineer B may also have hoped that direct, face-to-face communication would carry persuasive weight that the written report had not.",
"proeth-scenario:consequencesIfAlternative": [
"Remaining silent would have left the written report as the only warning, which commissioners had already effectively ignored; it would have represented a missed opportunity to fulfill the escalating duty to protect public safety",
"A private meeting might have preserved the professional relationship longer but would have lacked the public accountability dimension, potentially allowing commissioners to dismiss the concerns without consequence",
"Limiting remarks to neutral technical observations without a clear safety characterization would have been evasive and professionally inadequate, failing to communicate the urgency of the risk in terms decision-makers could not misinterpret"
],
"proeth-scenario:decisionSignificance": "This action illustrates the principle that written documentation alone may be insufficient when public safety is at stake. Students learn that engineers have an affirmative duty to communicate risks through multiple channels and to ensure that warnings are actually received and understood, not merely transmitted. It also demonstrates the personal courage required to speak uncomfortable truths in a public forum.",
"proeth-scenario:ethicalTension": "Speaking out at a public meeting escalates the conflict with the client and risks professional embarrassment or retaliation, yet silence in the face of a known public health risk would violate the engineer\u0027s paramount duty to public safety. There is also a tension between respecting the client\u0027s autonomy to make business decisions and the engineer\u0027s obligation not to be passive when those decisions create foreseeable harm to third parties.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If Engineer B speaks out, the professional relationship with MWC is further strained and termination becomes more likely. If Engineer B remains silent, the commissioners may later claim they were unaware of the risks, and Engineer B loses a critical opportunity to protect the public through direct communication. The public nature of the meeting also means the warning enters the civic record.",
"proeth:description": "Following MWC\u0027s decision to proceed with the water source change while delaying treatment improvements, Engineer B chose to verbally warn Water Commissioners at a public meeting of the public health and safety risks. This was a deliberate escalation beyond the written report to ensure decision-makers personally received the safety warning.",
"proeth:foreseenUnintendedEffects": [
"Could antagonize MWC commissioners and damage professional relationship",
"Public meeting setting creates reputational and political exposure for MWC",
"May not change MWC\u0027s decision but establishes Engineer B\u0027s professional diligence"
],
"proeth:fulfillsObligation": [
"Notified client of consequences of decisions overriding Engineer B\u0027s professional judgment",
"Took affirmative steps to protect public health beyond written report",
"Fulfilled duty to advise decision-makers directly of safety risks"
],
"proeth:guidedByPrinciple": [
"Public health and safety paramount",
"Professional courage",
"Transparency",
"Duty to advise client of consequences"
],
"proeth:hasAgent": "Engineer B (Retained Professional Engineer via ABC Engineers)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client relationship maintenance vs. affirmative duty to warn",
"proeth:resolutionReasoning": "The public health risk was sufficiently serious that Engineer B prioritized explicit warning over diplomatic restraint"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Ensure Water Commissioners personally understood the health and safety risks of proceeding without concurrent treatment improvements; create a documented public record of the warning",
"proeth:requiresCapability": [
"Professional communication",
"Risk articulation to non-technical decision-makers",
"Public meeting participation"
],
"proeth:temporalMarker": "After MWC voted to proceed with delayed treatment; at public commission meeting",
"proeth:withinCompetence": true,
"rdfs:label": "Verbal Warning to Commissioners"
}
Description: Engineer B followed up the verbal warning with a formal written letter to the Water Commissioners explicitly detailing the health and safety risks of proceeding with the water source change without concurrent treatment improvements. This created a documented professional record of the warning.
Temporal Marker: After public meeting verbal warning; prior to regulatory escalation
Mental State: deliberate
Intended Outcome: Create a formal, written, and documented record of the health and safety warning to commissioners; ensure the warning could not be dismissed as informal or ambiguous
Fulfills Obligations:
- Documented professional safety warning in writing as required by ethical practice
- Provided client with clear and specific information about consequences of their decision
- Fulfilled duty to notify client formally of overridden professional judgment
Guided By Principles:
- Public health and safety paramount
- Professional documentation standards
- Honesty and transparency
- Duty to advise client of consequences
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer B recognized that verbal warnings, however sincere, are ephemeral and deniable. The written letter was motivated by the need to create an unambiguous, dated, documented record that the commissioners had been explicitly informed of the specific health and safety risks. This also reflects professional prudence: if harm later occurred, the letter would demonstrate that Engineer B had fulfilled the duty to warn.
Ethical Tension: The formal letter makes the professional disagreement with the client a matter of permanent record, effectively signaling that Engineer B is prepared to stand behind the warning regardless of consequences to the professional relationship. This creates tension between loyalty to the client and the paramount duty to public safety, and raises the question of whether documenting the warning is sufficient or whether further escalation is required.
Learning Significance: Students learn the critical professional practice of following up verbal communications with written documentation, particularly when safety is at stake. The lesson extends beyond procedure: the written warning is an ethical act that transforms an oral exchange into a binding professional statement and creates accountability for both the engineer and the client. It also illustrates the concept of 'notice' in professional liability contexts.
Stakes: The written letter protects Engineer B's professional record and creates evidence of due diligence. However, if MWC ignores it — as they do — it also crystallizes the moment at which Engineer B must decide whether client-level communication has been exhausted and regulatory escalation is warranted. Failure to send the letter would weaken any subsequent escalation by suggesting the engineer had not fully engaged the client.
Decision Point: Yes - Story can branch here
- Send an internal memo to ABC Engineers rather than directly to MWC commissioners, routing the concern through the contracting firm
- Send the letter but frame it as offering additional consulting services to implement the treatment improvements, softening the warning into a commercial proposal
- Send the letter to MWC's legal counsel rather than the commissioners, to ensure it entered the formal legal record
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Action_Formal_Written_Warning_Sent",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Send an internal memo to ABC Engineers rather than directly to MWC commissioners, routing the concern through the contracting firm",
"Send the letter but frame it as offering additional consulting services to implement the treatment improvements, softening the warning into a commercial proposal",
"Send the letter to MWC\u0027s legal counsel rather than the commissioners, to ensure it entered the formal legal record"
],
"proeth-scenario:characterMotivation": "Engineer B recognized that verbal warnings, however sincere, are ephemeral and deniable. The written letter was motivated by the need to create an unambiguous, dated, documented record that the commissioners had been explicitly informed of the specific health and safety risks. This also reflects professional prudence: if harm later occurred, the letter would demonstrate that Engineer B had fulfilled the duty to warn.",
"proeth-scenario:consequencesIfAlternative": [
"Routing through ABC Engineers might have diluted the message or allowed the firm to suppress it for commercial reasons, leaving the commissioners without direct notice and weakening Engineer B\u0027s ethical standing",
"Framing the warning as a commercial proposal would have compromised the integrity of the safety communication, potentially allowing MWC to treat it as self-interested rather than professionally obligatory",
"Sending to legal counsel might have triggered a defensive posture from MWC, potentially accelerating termination while also ensuring the warning was legally documented \u2014 a mixed outcome with uncertain protective value for the public"
],
"proeth-scenario:decisionSignificance": "Students learn the critical professional practice of following up verbal communications with written documentation, particularly when safety is at stake. The lesson extends beyond procedure: the written warning is an ethical act that transforms an oral exchange into a binding professional statement and creates accountability for both the engineer and the client. It also illustrates the concept of \u0027notice\u0027 in professional liability contexts.",
"proeth-scenario:ethicalTension": "The formal letter makes the professional disagreement with the client a matter of permanent record, effectively signaling that Engineer B is prepared to stand behind the warning regardless of consequences to the professional relationship. This creates tension between loyalty to the client and the paramount duty to public safety, and raises the question of whether documenting the warning is sufficient or whether further escalation is required.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "The written letter protects Engineer B\u0027s professional record and creates evidence of due diligence. However, if MWC ignores it \u2014 as they do \u2014 it also crystallizes the moment at which Engineer B must decide whether client-level communication has been exhausted and regulatory escalation is warranted. Failure to send the letter would weaken any subsequent escalation by suggesting the engineer had not fully engaged the client.",
"proeth:description": "Engineer B followed up the verbal warning with a formal written letter to the Water Commissioners explicitly detailing the health and safety risks of proceeding with the water source change without concurrent treatment improvements. This created a documented professional record of the warning.",
"proeth:foreseenUnintendedEffects": [
"Written record increases MWC\u0027s legal and regulatory exposure",
"May further antagonize MWC and jeopardize the professional engagement",
"Establishes Engineer B\u0027s professional diligence in any future investigation or litigation"
],
"proeth:fulfillsObligation": [
"Documented professional safety warning in writing as required by ethical practice",
"Provided client with clear and specific information about consequences of their decision",
"Fulfilled duty to notify client formally of overridden professional judgment"
],
"proeth:guidedByPrinciple": [
"Public health and safety paramount",
"Professional documentation standards",
"Honesty and transparency",
"Duty to advise client of consequences"
],
"proeth:hasAgent": "Engineer B (Retained Professional Engineer via ABC Engineers)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional relationship continuity vs. formal safety documentation",
"proeth:resolutionReasoning": "Public health documentation obligation outweighed the risk to the professional relationship"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Create a formal, written, and documented record of the health and safety warning to commissioners; ensure the warning could not be dismissed as informal or ambiguous",
"proeth:requiresCapability": [
"Technical writing",
"Risk communication",
"Professional correspondence"
],
"proeth:temporalMarker": "After public meeting verbal warning; prior to regulatory escalation",
"proeth:withinCompetence": true,
"rdfs:label": "Formal Written Warning Sent"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: MWC decided to proceed with switching from remote reservoirs to the local river as a water source, explicitly choosing to delay the treatment improvements Engineer B had recommended as prerequisites. This outcome directly contradicts the safety-first sequencing in Engineer B's report.
Temporal Marker: After Engineer B's report was submitted; before public meeting warning
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Engineer_Must_Warn_Affected_Parties
- Duty_To_Notify_Regulatory_Authority
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Frustration and alarm for Engineer B, whose professional recommendations are overridden; indifference or optimism from MWC commissioners focused on cost savings; potential anxiety among community members if informed; moral distress for Engineer B facing a client-versus-public conflict
- engineer_b: Professional integrity challenged; obligation to act further is now triggered; risk of client conflict if escalation pursued
- mwc_commissioners: Short-term financial relief; long-term legal and reputational exposure if health harms materialize
- water_consumers: Unknowingly exposed to increased risk of lead leaching from untreated source water; no informed consent
- abc_engineers: Organizational reputation at risk if associated with an unsafe outcome; potential liability exposure
- state_regulators: Not yet informed; unaware that a safety-relevant decision has been made against expert advice
Learning Moment: This event illustrates the foundational ethics principle that engineers' primary obligation is to public safety, not client satisfaction. When a client overrides safety-critical recommendations, the engineer's professional duty does not end — it intensifies. Students should recognize this as the moment Engineer B's ethical obligations shift from advisory to protective.
Ethical Implications: Reveals the core tension in engineering ethics between client authority and public welfare; exposes how cost-benefit reasoning by non-engineers can override technical safety judgments; raises questions about the limits of client autonomy when third-party harm is foreseeable
- At what point does a client's decision to override safety recommendations transform an engineer's advisory role into an obligation to act unilaterally?
- Does Engineer B bear any moral responsibility for the risk now that the client has formally rejected the recommendation?
- How should engineers balance loyalty to clients with duties to the public when these come into direct conflict?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Event_Water_Source_Change_Decided",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"At what point does a client\u0027s decision to override safety recommendations transform an engineer\u0027s advisory role into an obligation to act unilaterally?",
"Does Engineer B bear any moral responsibility for the risk now that the client has formally rejected the recommendation?",
"How should engineers balance loyalty to clients with duties to the public when these come into direct conflict?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Frustration and alarm for Engineer B, whose professional recommendations are overridden; indifference or optimism from MWC commissioners focused on cost savings; potential anxiety among community members if informed; moral distress for Engineer B facing a client-versus-public conflict",
"proeth-scenario:ethicalImplications": "Reveals the core tension in engineering ethics between client authority and public welfare; exposes how cost-benefit reasoning by non-engineers can override technical safety judgments; raises questions about the limits of client autonomy when third-party harm is foreseeable",
"proeth-scenario:learningMoment": "This event illustrates the foundational ethics principle that engineers\u0027 primary obligation is to public safety, not client satisfaction. When a client overrides safety-critical recommendations, the engineer\u0027s professional duty does not end \u2014 it intensifies. Students should recognize this as the moment Engineer B\u0027s ethical obligations shift from advisory to protective.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"abc_engineers": "Organizational reputation at risk if associated with an unsafe outcome; potential liability exposure",
"engineer_b": "Professional integrity challenged; obligation to act further is now triggered; risk of client conflict if escalation pursued",
"mwc_commissioners": "Short-term financial relief; long-term legal and reputational exposure if health harms materialize",
"state_regulators": "Not yet informed; unaware that a safety-relevant decision has been made against expert advice",
"water_consumers": "Unknowingly exposed to increased risk of lead leaching from untreated source water; no informed consent"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Engineer_Must_Warn_Affected_Parties",
"Duty_To_Notify_Regulatory_Authority"
],
"proeth:causedByAction": "http://proethica.org/cases/18#Action_Risk-Based_Report_Recommendation_Issued",
"proeth:causesStateChange": "Project status shifts from evaluation phase to active implementation despite known safety risks; Engineer B\u0027s professional obligations to public safety are now in direct tension with client authority",
"proeth:createsObligation": [
"Engineer_B_Must_Warn_Commissioners",
"Engineer_B_Must_Issue_Written_Warning",
"Engineer_B_Must_Consider_Regulatory_Escalation",
"Engineer_B_Must_Document_Risk_Formally"
],
"proeth:description": "MWC decided to proceed with switching from remote reservoirs to the local river as a water source, explicitly choosing to delay the treatment improvements Engineer B had recommended as prerequisites. This outcome directly contradicts the safety-first sequencing in Engineer B\u0027s report.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After Engineer B\u0027s report was submitted; before public meeting warning",
"proeth:urgencyLevel": "high",
"rdfs:label": "Water Source Change Decided"
}
Description: MWC terminated Engineer B and ABC Engineers from the project following Engineer B's escalation to the State Department of the Environment, subsequently retaining XYZ Consultants. This discharge is a direct consequence of Engineer B's whistleblowing actions.
Temporal Marker: After Regulatory Authority Notification; before XYZ report issued
Activates Constraints:
- Discharged_Engineer_Residual_Duty_Constraint
- PublicSafety_Obligation_Persists_Post_Discharge
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer B likely experiences professional vulnerability, possible vindication of having done the right thing, and uncertainty about future obligations; ABC Engineers may feel organizational exposure and frustration; MWC commissioners may feel relief at removing a dissenting voice; the public remains unaware and unprotected
- engineer_b: Loss of income from this project; professional retaliation for ethical action; potential chilling effect on future whistleblowing; but also moral clarity about having acted correctly
- abc_engineers: Organizational financial loss; potential reputational harm; forced to evaluate whether to support or distance from Engineer B's actions
- mwc: Short-term relief from dissent; increased legal and reputational risk if harm occurs and discharge is seen as retaliatory suppression of safety warnings
- xyz_consultants: Inherit a politically charged project; face pressure to produce a favorable report; risk complicity if they knowingly downplay risks
- water_consumers: Lose the advocate who had been warning about their safety; risk increases as critical voice is removed from project
Learning Moment: This event demonstrates that retaliation for ethical action is a real professional risk, and that discharge does not extinguish an engineer's public safety obligations. Students should understand that NSPE Code obligations persist beyond the client relationship when public health is at stake.
Ethical Implications: Exposes the vulnerability of ethical engineers to retaliatory discharge; raises questions about whether professional codes of ethics are enforceable when clients can simply replace dissenting engineers; highlights the systemic problem of 'opinion shopping' in safety-sensitive contexts
- Does being discharged from a project relieve an engineer of further ethical obligations regarding known public safety risks?
- What does it mean for professional integrity if engineers self-censor safety warnings to avoid being fired?
- Should engineering professional societies or licensing boards provide protections for engineers who are discharged for raising safety concerns?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Event_Engineer_B_Discharged",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Does being discharged from a project relieve an engineer of further ethical obligations regarding known public safety risks?",
"What does it mean for professional integrity if engineers self-censor safety warnings to avoid being fired?",
"Should engineering professional societies or licensing boards provide protections for engineers who are discharged for raising safety concerns?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer B likely experiences professional vulnerability, possible vindication of having done the right thing, and uncertainty about future obligations; ABC Engineers may feel organizational exposure and frustration; MWC commissioners may feel relief at removing a dissenting voice; the public remains unaware and unprotected",
"proeth-scenario:ethicalImplications": "Exposes the vulnerability of ethical engineers to retaliatory discharge; raises questions about whether professional codes of ethics are enforceable when clients can simply replace dissenting engineers; highlights the systemic problem of \u0027opinion shopping\u0027 in safety-sensitive contexts",
"proeth-scenario:learningMoment": "This event demonstrates that retaliation for ethical action is a real professional risk, and that discharge does not extinguish an engineer\u0027s public safety obligations. Students should understand that NSPE Code obligations persist beyond the client relationship when public health is at stake.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"abc_engineers": "Organizational financial loss; potential reputational harm; forced to evaluate whether to support or distance from Engineer B\u0027s actions",
"engineer_b": "Loss of income from this project; professional retaliation for ethical action; potential chilling effect on future whistleblowing; but also moral clarity about having acted correctly",
"mwc": "Short-term relief from dissent; increased legal and reputational risk if harm occurs and discharge is seen as retaliatory suppression of safety warnings",
"water_consumers": "Lose the advocate who had been warning about their safety; risk increases as critical voice is removed from project",
"xyz_consultants": "Inherit a politically charged project; face pressure to produce a favorable report; risk complicity if they knowingly downplay risks"
},
"proeth:activatesConstraint": [
"Discharged_Engineer_Residual_Duty_Constraint",
"PublicSafety_Obligation_Persists_Post_Discharge"
],
"proeth:causedByAction": "http://proethica.org/cases/18#Action_Regulatory_Authority_Notification",
"proeth:causesStateChange": "Engineer B loses formal project role and client relationship; however, professional ethical obligations to public safety persist independent of employment status; Engineer B transitions from retained advisor to concerned private professional",
"proeth:createsObligation": [
"Engineer_B_Must_Assess_Whether_Further_Action_Required",
"Engineer_B_Must_Not_Abandon_Public_Safety_Concern_Due_To_Discharge",
"ABC_Engineers_Must_Evaluate_Organizational_Response"
],
"proeth:description": "MWC terminated Engineer B and ABC Engineers from the project following Engineer B\u0027s escalation to the State Department of the Environment, subsequently retaining XYZ Consultants. This discharge is a direct consequence of Engineer B\u0027s whistleblowing actions.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After Regulatory Authority Notification; before XYZ report issued",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Engineer B Discharged"
}
Description: XYZ Consultants produced a report stating that insufficient information existed to predict the severity of risk from the water source change, effectively undermining Engineer B's risk-based findings without directly refuting them. This outcome introduces a competing technical narrative into the regulatory record.
Temporal Marker: After Engineer B and ABC Engineers discharged; before state regulatory approval
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Duty_To_Correct_Misleading_Technical_Record
- Engineer_Must_Not_Allow_False_Impression_To_Stand
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer B likely experiences frustration, professional affront, and renewed urgency; XYZ Consultants may experience cognitive dissonance or rationalization; MWC commissioners feel validated; regulators face genuine uncertainty about which technical opinion to credit; the public remains unaware that their safety is being debated through competing consultant reports
- engineer_b: Professional credibility challenged by competing report; must decide whether to respond or allow the contradictory finding to stand in the regulatory record
- xyz_consultants: Potentially complicit in a process designed to suppress safety warnings; face ethical exposure if harm occurs and their report is seen as enabling it
- mwc: Gains regulatory cover through a second opinion; shifts moral responsibility partially to XYZ and regulators
- state_regulators: Now must adjudicate between two expert opinions with different conclusions; decision-making burden increased
- water_consumers: Safety advocacy further diluted; risk of harm increases as the clearest warning is now offset by a competing technical claim
Learning Moment: This event illustrates the ethical problem of 'opinion shopping' — where clients replace engineers who give unwelcome safety findings with consultants more likely to produce favorable reports. Students should recognize this as a systemic threat to engineering's social function as a safety guarantor.
Ethical Implications: Reveals how the market structure of consulting engineering can be exploited to manufacture technical ambiguity and suppress safety warnings; raises questions about whether engineers who produce favorable reports under pressure are complicit in potential harm; highlights the inadequacy of purely adversarial technical review processes for protecting public safety
- Is it ethically permissible for XYZ Consultants to accept this engagement knowing they were hired to replace an engineer who raised safety concerns?
- What obligations do engineers have when they know a competing report may be used to override legitimate safety warnings?
- How should regulatory bodies handle situations where competing technical opinions have been produced under conditions of potential bias?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Event_Contradictory_Consultant_Report_Issued",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Is it ethically permissible for XYZ Consultants to accept this engagement knowing they were hired to replace an engineer who raised safety concerns?",
"What obligations do engineers have when they know a competing report may be used to override legitimate safety warnings?",
"How should regulatory bodies handle situations where competing technical opinions have been produced under conditions of potential bias?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer B likely experiences frustration, professional affront, and renewed urgency; XYZ Consultants may experience cognitive dissonance or rationalization; MWC commissioners feel validated; regulators face genuine uncertainty about which technical opinion to credit; the public remains unaware that their safety is being debated through competing consultant reports",
"proeth-scenario:ethicalImplications": "Reveals how the market structure of consulting engineering can be exploited to manufacture technical ambiguity and suppress safety warnings; raises questions about whether engineers who produce favorable reports under pressure are complicit in potential harm; highlights the inadequacy of purely adversarial technical review processes for protecting public safety",
"proeth-scenario:learningMoment": "This event illustrates the ethical problem of \u0027opinion shopping\u0027 \u2014 where clients replace engineers who give unwelcome safety findings with consultants more likely to produce favorable reports. Students should recognize this as a systemic threat to engineering\u0027s social function as a safety guarantor.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"engineer_b": "Professional credibility challenged by competing report; must decide whether to respond or allow the contradictory finding to stand in the regulatory record",
"mwc": "Gains regulatory cover through a second opinion; shifts moral responsibility partially to XYZ and regulators",
"state_regulators": "Now must adjudicate between two expert opinions with different conclusions; decision-making burden increased",
"water_consumers": "Safety advocacy further diluted; risk of harm increases as the clearest warning is now offset by a competing technical claim",
"xyz_consultants": "Potentially complicit in a process designed to suppress safety warnings; face ethical exposure if harm occurs and their report is seen as enabling it"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Duty_To_Correct_Misleading_Technical_Record",
"Engineer_Must_Not_Allow_False_Impression_To_Stand"
],
"proeth:causedByAction": "http://proethica.org/cases/18#Action_Water_Source_Evaluation_Accepted__by_XYZ_Consultan",
"proeth:causesStateChange": "The technical record before regulators now contains two competing expert assessments; the safety-critical warning from Engineer B is counterbalanced by XYZ\u0027s uncertainty claim; the regulatory decision is now made in an environment of manufactured ambiguity",
"proeth:createsObligation": [
"Engineer_B_Should_Consider_Responding_To_Contradictory_Report",
"Regulators_Obligated_To_Reconcile_Conflicting_Technical_Opinions",
"XYZ_Consultants_Obligated_To_Ensure_Report_Is_Not_Misleading"
],
"proeth:description": "XYZ Consultants produced a report stating that insufficient information existed to predict the severity of risk from the water source change, effectively undermining Engineer B\u0027s risk-based findings without directly refuting them. This outcome introduces a competing technical narrative into the regulatory record.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "After Engineer B and ABC Engineers discharged; before state regulatory approval",
"proeth:urgencyLevel": "high",
"rdfs:label": "Contradictory Consultant Report Issued"
}
Description: The State Department of the Environment approved the water source change, incorporating a five-year plan for treatment implementation, as reported in the newspaper Engineer B read. This approval was granted despite Engineer B's prior notification of health risks, and with the five-year delay in treatment improvements that Engineer B had warned against.
Temporal Marker: Several months after Engineer B's discharge; discovered by Engineer B via newspaper
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Engineer_B_Post_Discharge_Residual_Duty
- Obligation_To_Consider_Further_Escalation
- Duty_To_Protect_Public_From_Known_Hazard
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer B experiences dismay, moral distress, and renewed urgency upon reading the newspaper; a sense of having failed despite having done everything within the conventional scope of professional duty; possible anger at the regulatory outcome; uncertainty about whether further action is now futile or more necessary than ever. MWC commissioners feel vindicated. The public remains unaware of the underlying controversy.
- engineer_b: Prior actions did not prevent the harmful outcome; now faces the hardest ethical question — whether professional duty requires further action even after formal processes have concluded against the engineer's recommendation
- mwc: Legally authorized to proceed; however, moral and legal liability for health outcomes remains
- state_regulators: Have formally assumed partial responsibility for the outcome through their approval; if harm occurs, their decision-making process will be scrutinized
- xyz_consultants: Their report contributed to the regulatory record that enabled approval; share in the moral responsibility chain
- water_consumers: Now face legally sanctioned exposure to lead leaching risk for up to five years without the treatment improvements Engineer B recommended; most vulnerable populations (children, pregnant women) at greatest risk
- public_health_system: Will bear downstream costs if lead exposure harms materialize
Learning Moment: This event forces students to confront the hardest question in engineering ethics: what does an engineer do when they have followed all conventional channels and the system has still produced a dangerous outcome? It illustrates that professional duty may not end when institutional processes conclude, particularly when known public health risks remain unaddressed.
Ethical Implications: Reveals the limits of procedural ethics — doing the right things through proper channels does not guarantee a safe outcome; raises the question of whether engineers have obligations that extend beyond institutional processes when public health is at stake; highlights the tension between respecting regulatory authority and maintaining independent professional judgment about safety; exposes how regulatory approval can create a false sense of legitimacy around decisions that remain ethically problematic
- Engineer B followed every conventional escalation step — warning the client, issuing written warnings, notifying regulators — and the dangerous outcome still occurred. Does this mean Engineer B fulfilled professional obligations, or does the persistence of risk demand further action?
- At what point, if any, does an engineer's obligation to public safety require actions outside formal institutional channels (e.g., media disclosure, public advocacy)?
- How should the five-year treatment delay be evaluated ethically — is a phased implementation plan a reasonable compromise, or does it represent an unacceptable institutionalization of known risk?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Event_Regulatory_Approval_Granted",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Engineer B followed every conventional escalation step \u2014 warning the client, issuing written warnings, notifying regulators \u2014 and the dangerous outcome still occurred. Does this mean Engineer B fulfilled professional obligations, or does the persistence of risk demand further action?",
"At what point, if any, does an engineer\u0027s obligation to public safety require actions outside formal institutional channels (e.g., media disclosure, public advocacy)?",
"How should the five-year treatment delay be evaluated ethically \u2014 is a phased implementation plan a reasonable compromise, or does it represent an unacceptable institutionalization of known risk?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer B experiences dismay, moral distress, and renewed urgency upon reading the newspaper; a sense of having failed despite having done everything within the conventional scope of professional duty; possible anger at the regulatory outcome; uncertainty about whether further action is now futile or more necessary than ever. MWC commissioners feel vindicated. The public remains unaware of the underlying controversy.",
"proeth-scenario:ethicalImplications": "Reveals the limits of procedural ethics \u2014 doing the right things through proper channels does not guarantee a safe outcome; raises the question of whether engineers have obligations that extend beyond institutional processes when public health is at stake; highlights the tension between respecting regulatory authority and maintaining independent professional judgment about safety; exposes how regulatory approval can create a false sense of legitimacy around decisions that remain ethically problematic",
"proeth-scenario:learningMoment": "This event forces students to confront the hardest question in engineering ethics: what does an engineer do when they have followed all conventional channels and the system has still produced a dangerous outcome? It illustrates that professional duty may not end when institutional processes conclude, particularly when known public health risks remain unaddressed.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"engineer_b": "Prior actions did not prevent the harmful outcome; now faces the hardest ethical question \u2014 whether professional duty requires further action even after formal processes have concluded against the engineer\u0027s recommendation",
"mwc": "Legally authorized to proceed; however, moral and legal liability for health outcomes remains",
"public_health_system": "Will bear downstream costs if lead exposure harms materialize",
"state_regulators": "Have formally assumed partial responsibility for the outcome through their approval; if harm occurs, their decision-making process will be scrutinized",
"water_consumers": "Now face legally sanctioned exposure to lead leaching risk for up to five years without the treatment improvements Engineer B recommended; most vulnerable populations (children, pregnant women) at greatest risk",
"xyz_consultants": "Their report contributed to the regulatory record that enabled approval; share in the moral responsibility chain"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Engineer_B_Post_Discharge_Residual_Duty",
"Obligation_To_Consider_Further_Escalation",
"Duty_To_Protect_Public_From_Known_Hazard"
],
"proeth:causedByAction": "http://proethica.org/cases/18#Action_Regulatory_Authority_Notification__Engineer_B_s_pr",
"proeth:causesStateChange": "The regulatory process has concluded with an outcome that Engineer B warned against; the five-year treatment delay is now legally sanctioned; public health risk is now institutionalized; Engineer B\u0027s prior interventions did not prevent the approval; the ethical question shifts from \u0027how to prevent approval\u0027 to \u0027what obligations remain after approval\u0027",
"proeth:createsObligation": [
"Engineer_B_Must_Deliberate_On_Further_Action",
"Engineer_B_Must_Consider_Whether_Prior_Actions_Were_Sufficient",
"Engineer_B_Must_Evaluate_Whether_Additional_Notification_Is_Warranted",
"Engineer_B_Must_Assess_Whether_Regulatory_Decision_Was_Fully_Informed"
],
"proeth:description": "The State Department of the Environment approved the water source change, incorporating a five-year plan for treatment implementation, as reported in the newspaper Engineer B read. This approval was granted despite Engineer B\u0027s prior notification of health risks, and with the five-year delay in treatment improvements that Engineer B had warned against.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Several months after Engineer B\u0027s discharge; discovered by Engineer B via newspaper",
"proeth:urgencyLevel": "critical",
"rdfs:label": "Regulatory Approval Granted"
}
Description: Throughout the case, the water-consuming public remained uninformed about the known lead leaching risks associated with the water source change and the delayed treatment improvements. This ongoing information gap represents a persistent condition affecting the public's ability to protect themselves or advocate for their interests.
Temporal Marker: Ongoing from the point of MWC's decision through regulatory approval and beyond
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Duty_To_Inform_Affected_Parties
- Engineer_B_Post_Approval_Deliberation_Obligation
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: The public, if aware, would likely feel betrayed and alarmed; Engineer B may feel the weight of knowing that vulnerable community members are unaware of risks Engineer B has tried to flag; this gap creates a moral burden that persists even after formal obligations appear to be discharged
- water_consumers: Cannot take protective measures (e.g., using filters, boiling water, advocating for faster treatment implementation) because they are unaware of the risk; most vulnerable populations bear the greatest burden of this information asymmetry
- engineer_b: Faces the question of whether professional duty to the public requires going beyond institutional channels to ensure the public is informed
- mwc: Benefits from public ignorance in the short term; faces greater legal and reputational exposure if harm occurs and the information gap is later exposed
- state_regulators: Approved a plan without ensuring the affected public was informed of the safety controversy; potential accountability gap
- public_health_advocates: Unaware of an issue they might otherwise mobilize around
Learning Moment: This event highlights that engineering ethics is not only about what engineers communicate to clients and regulators, but also about who ultimately receives safety-critical information. Students should consider whether the public — as the ultimate beneficiary of engineering safety obligations — has a right to be directly informed when institutional channels fail to protect them.
Ethical Implications: Reveals a structural gap in engineering ethics frameworks — the focus on institutional notification may leave the public, as the ultimate protected party, without the information needed to protect themselves; raises questions about democratic accountability in technical decision-making; highlights the tension between professional confidentiality norms and the public's right to know about risks to their health
- Does Engineer B have an obligation to inform the public directly, or is notifying the client and regulators sufficient to discharge professional duty?
- How does the public's lack of information about known risks affect the ethical calculus of the decisions made by MWC and regulators?
- Should engineering codes of ethics explicitly address when engineers must go beyond institutional channels to ensure the public is informed of safety risks?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#Event_Health_Risk_Information_Gap",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does Engineer B have an obligation to inform the public directly, or is notifying the client and regulators sufficient to discharge professional duty?",
"How does the public\u0027s lack of information about known risks affect the ethical calculus of the decisions made by MWC and regulators?",
"Should engineering codes of ethics explicitly address when engineers must go beyond institutional channels to ensure the public is informed of safety risks?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "The public, if aware, would likely feel betrayed and alarmed; Engineer B may feel the weight of knowing that vulnerable community members are unaware of risks Engineer B has tried to flag; this gap creates a moral burden that persists even after formal obligations appear to be discharged",
"proeth-scenario:ethicalImplications": "Reveals a structural gap in engineering ethics frameworks \u2014 the focus on institutional notification may leave the public, as the ultimate protected party, without the information needed to protect themselves; raises questions about democratic accountability in technical decision-making; highlights the tension between professional confidentiality norms and the public\u0027s right to know about risks to their health",
"proeth-scenario:learningMoment": "This event highlights that engineering ethics is not only about what engineers communicate to clients and regulators, but also about who ultimately receives safety-critical information. Students should consider whether the public \u2014 as the ultimate beneficiary of engineering safety obligations \u2014 has a right to be directly informed when institutional channels fail to protect them.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"engineer_b": "Faces the question of whether professional duty to the public requires going beyond institutional channels to ensure the public is informed",
"mwc": "Benefits from public ignorance in the short term; faces greater legal and reputational exposure if harm occurs and the information gap is later exposed",
"public_health_advocates": "Unaware of an issue they might otherwise mobilize around",
"state_regulators": "Approved a plan without ensuring the affected public was informed of the safety controversy; potential accountability gap",
"water_consumers": "Cannot take protective measures (e.g., using filters, boiling water, advocating for faster treatment implementation) because they are unaware of the risk; most vulnerable populations bear the greatest burden of this information asymmetry"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Duty_To_Inform_Affected_Parties",
"Engineer_B_Post_Approval_Deliberation_Obligation"
],
"proeth:causedByAction": "http://proethica.org/cases/18#Action_Verbal_Warning_to_Commissioners___Formal_Written_W",
"proeth:causesStateChange": "Public remains uninformed and therefore unable to exercise protective behaviors or political pressure; the information asymmetry between technical experts and affected community represents a structural safety deficit",
"proeth:createsObligation": [
"Engineer_B_Must_Evaluate_Whether_Public_Notification_Is_Warranted",
"Engineer_B_Must_Assess_Whether_Regulatory_Channels_Were_Truly_Exhausted"
],
"proeth:description": "Throughout the case, the water-consuming public remained uninformed about the known lead leaching risks associated with the water source change and the delayed treatment improvements. This ongoing information gap represents a persistent condition affecting the public\u0027s ability to protect themselves or advocate for their interests.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Ongoing from the point of MWC\u0027s decision through regulatory approval and beyond",
"proeth:urgencyLevel": "high",
"rdfs:label": "Health Risk Information Gap"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Engineer B completed and issued a professional report recommending that water treatment improvements be made prior to or concurrent with any water source change, yet MWC decided to proceed with switching from remote reservoirs to the local river while delaying treatment improvements
Necessary Factors (NESS):
- Engineer B's report identifying lead leaching risks
- MWC's authority to override engineering recommendations
- Economic or political motivation to proceed without treatment upgrades
Sufficient Factors:
- MWC's decision-making authority combined with willingness to discount risk-based engineering advice
- Absence of binding regulatory requirement to implement treatment improvements first
Responsibility Attribution:
Agent: Municipal Water Commissioners (MWC)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Water Source Evaluation Accepted
Engineer B is retained by ABC Engineers to evaluate feasibility and implications of changing the water source -
Risk-Based Report Recommendation Issued
Engineer B issues a professional report identifying lead leaching risks and recommending treatment improvements before or concurrent with source change -
Contradictory Consultant Report Issued
XYZ Consultants produce a competing report stating insufficient information exists to predict severity, undermining Engineer B's findings -
Water Source Change Decided
MWC proceeds with the river water source change while deferring treatment improvements, discounting Engineer B's recommendations -
Health Risk Information Gap
The public remains uninformed of the known lead leaching risks associated with the new water source and absence of treatment safeguards
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#CausalChain_6e5d2a6e",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer B completed and issued a professional report recommending that water treatment improvements be made prior to or concurrent with any water source change, yet MWC decided to proceed with switching from remote reservoirs to the local river while delaying treatment improvements",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B is retained by ABC Engineers to evaluate feasibility and implications of changing the water source",
"proeth:element": "Water Source Evaluation Accepted",
"proeth:step": 1
},
{
"proeth:description": "Engineer B issues a professional report identifying lead leaching risks and recommending treatment improvements before or concurrent with source change",
"proeth:element": "Risk-Based Report Recommendation Issued",
"proeth:step": 2
},
{
"proeth:description": "XYZ Consultants produce a competing report stating insufficient information exists to predict severity, undermining Engineer B\u0027s findings",
"proeth:element": "Contradictory Consultant Report Issued",
"proeth:step": 3
},
{
"proeth:description": "MWC proceeds with the river water source change while deferring treatment improvements, discounting Engineer B\u0027s recommendations",
"proeth:element": "Water Source Change Decided",
"proeth:step": 4
},
{
"proeth:description": "The public remains uninformed of the known lead leaching risks associated with the new water source and absence of treatment safeguards",
"proeth:element": "Health Risk Information Gap",
"proeth:step": 5
}
],
"proeth:cause": "Risk-Based Report Recommendation Issued",
"proeth:counterfactual": "Without the report, MWC may have proceeded uninformed; however, the report\u0027s existence did not prevent MWC from proceeding \u2014 the outcome (source change without treatment) would likely have occurred regardless given MWC\u0027s institutional priorities",
"proeth:effect": "Water Source Change Decided",
"proeth:necessaryFactors": [
"Engineer B\u0027s report identifying lead leaching risks",
"MWC\u0027s authority to override engineering recommendations",
"Economic or political motivation to proceed without treatment upgrades"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Municipal Water Commissioners (MWC)",
"proeth:sufficientFactors": [
"MWC\u0027s decision-making authority combined with willingness to discount risk-based engineering advice",
"Absence of binding regulatory requirement to implement treatment improvements first"
],
"proeth:withinAgentControl": true
}
Causal Language: Following MWC's decision to proceed with the water source change while delaying treatment improvements, Engineer B issued a verbal warning to commissioners; MWC terminated Engineer B and ABC Engineers from the project following Engineer B's escalation
Necessary Factors (NESS):
- Engineer B's decision to formally challenge MWC's decision through verbal and written warnings
- MWC's institutional resistance to external criticism of its decisions
- The client-engineer power dynamic giving MWC authority to terminate the engagement
Sufficient Factors:
- Combination of Engineer B's persistent escalation (verbal warning followed by formal written warning) and MWC's unwillingness to accept liability-implicating professional dissent
Responsibility Attribution:
Agent: Municipal Water Commissioners (MWC)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Water Source Change Decided
MWC proceeds with source change against Engineer B's recommendations, creating a direct conflict -
Verbal Warning to Commissioners
Engineer B verbally warns commissioners of the public health risks of proceeding without treatment improvements -
Formal Written Warning Sent
Engineer B escalates by sending a formal written letter documenting the risks and professional objections -
Regulatory Authority Notification
Engineer B further escalates by sending the technical report and cover letter to the State Department of the Environment -
Engineer B Discharged
MWC terminates Engineer B and ABC Engineers in direct response to the regulatory escalation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#CausalChain_b573406f",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Following MWC\u0027s decision to proceed with the water source change while delaying treatment improvements, Engineer B issued a verbal warning to commissioners; MWC terminated Engineer B and ABC Engineers from the project following Engineer B\u0027s escalation",
"proeth:causalSequence": [
{
"proeth:description": "MWC proceeds with source change against Engineer B\u0027s recommendations, creating a direct conflict",
"proeth:element": "Water Source Change Decided",
"proeth:step": 1
},
{
"proeth:description": "Engineer B verbally warns commissioners of the public health risks of proceeding without treatment improvements",
"proeth:element": "Verbal Warning to Commissioners",
"proeth:step": 2
},
{
"proeth:description": "Engineer B escalates by sending a formal written letter documenting the risks and professional objections",
"proeth:element": "Formal Written Warning Sent",
"proeth:step": 3
},
{
"proeth:description": "Engineer B further escalates by sending the technical report and cover letter to the State Department of the Environment",
"proeth:element": "Regulatory Authority Notification",
"proeth:step": 4
},
{
"proeth:description": "MWC terminates Engineer B and ABC Engineers in direct response to the regulatory escalation",
"proeth:element": "Engineer B Discharged",
"proeth:step": 5
}
],
"proeth:cause": "Verbal Warning to Commissioners",
"proeth:counterfactual": "Had Engineer B remained silent after issuing the initial report, termination would likely not have occurred at this stage; the escalation was the proximate trigger for discharge",
"proeth:effect": "Engineer B Discharged",
"proeth:necessaryFactors": [
"Engineer B\u0027s decision to formally challenge MWC\u0027s decision through verbal and written warnings",
"MWC\u0027s institutional resistance to external criticism of its decisions",
"The client-engineer power dynamic giving MWC authority to terminate the engagement"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Municipal Water Commissioners (MWC)",
"proeth:sufficientFactors": [
"Combination of Engineer B\u0027s persistent escalation (verbal warning followed by formal written warning) and MWC\u0027s unwillingness to accept liability-implicating professional dissent"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer B escalated beyond the client by sending the original technical report and a cover letter describing the situation to the State Department of the Environment; the State Department of the Environment approved the water source change, incorporating a five-year compliance schedule
Necessary Factors (NESS):
- Engineer B's submission of the technical report to the regulatory authority
- The State Department of the Environment's independent review authority
- Existence of a regulatory framework permitting conditional approval with compliance schedules
Sufficient Factors:
- Regulatory authority's receipt of both Engineer B's risk-based report and the contradictory XYZ Consultants report, combined with its discretion to grant conditional rather than unconditional approval
Responsibility Attribution:
Agent: State Department of the Environment
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Regulatory Authority Notification
Engineer B sends technical report and explanatory cover letter to the State Department of the Environment after being unable to resolve concerns with MWC -
Contradictory Consultant Report Issued
XYZ Consultants' competing report is also available to the regulatory authority, creating conflicting technical evidence -
Regulatory Approval Granted
State Department of the Environment approves the water source change with a five-year compliance schedule for treatment improvements -
Health Risk Information Gap
Despite regulatory approval, the public remains uninformed of the interim lead leaching risks during the five-year compliance window -
Post-Approval Further Action Deliberation
Engineer B reads of the approval in the newspaper and deliberates whether further action is warranted given ongoing public health risk
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#CausalChain_3908093b",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer B escalated beyond the client by sending the original technical report and a cover letter describing the situation to the State Department of the Environment; the State Department of the Environment approved the water source change, incorporating a five-year compliance schedule",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B sends technical report and explanatory cover letter to the State Department of the Environment after being unable to resolve concerns with MWC",
"proeth:element": "Regulatory Authority Notification",
"proeth:step": 1
},
{
"proeth:description": "XYZ Consultants\u0027 competing report is also available to the regulatory authority, creating conflicting technical evidence",
"proeth:element": "Contradictory Consultant Report Issued",
"proeth:step": 2
},
{
"proeth:description": "State Department of the Environment approves the water source change with a five-year compliance schedule for treatment improvements",
"proeth:element": "Regulatory Approval Granted",
"proeth:step": 3
},
{
"proeth:description": "Despite regulatory approval, the public remains uninformed of the interim lead leaching risks during the five-year compliance window",
"proeth:element": "Health Risk Information Gap",
"proeth:step": 4
},
{
"proeth:description": "Engineer B reads of the approval in the newspaper and deliberates whether further action is warranted given ongoing public health risk",
"proeth:element": "Post-Approval Further Action Deliberation",
"proeth:step": 5
}
],
"proeth:cause": "Regulatory Authority Notification",
"proeth:counterfactual": "Without Engineer B\u0027s notification, the regulatory authority may have lacked the technical detail to impose a five-year compliance condition; however, approval may still have been granted without the protective condition, potentially resulting in a worse public health outcome",
"proeth:effect": "Regulatory Approval Granted",
"proeth:necessaryFactors": [
"Engineer B\u0027s submission of the technical report to the regulatory authority",
"The State Department of the Environment\u0027s independent review authority",
"Existence of a regulatory framework permitting conditional approval with compliance schedules"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "State Department of the Environment",
"proeth:sufficientFactors": [
"Regulatory authority\u0027s receipt of both Engineer B\u0027s risk-based report and the contradictory XYZ Consultants report, combined with its discretion to grant conditional rather than unconditional approval"
],
"proeth:withinAgentControl": true
}
Causal Language: XYZ Consultants produced a report stating that insufficient information existed to predict the severity of risks, thereby providing institutional cover for MWC's decision to proceed and contributing to the public remaining uninformed about the known lead leaching risks
Necessary Factors (NESS):
- XYZ Consultants' willingness to issue a report contradicting Engineer B's findings without resolving the underlying technical dispute
- MWC's use of the contradictory report to justify proceeding without treatment improvements
- Absence of a regulatory or institutional mechanism to reconcile conflicting expert reports before public health decisions are made
Sufficient Factors:
- Combination of contradictory expert reports, MWC's institutional authority, and regulatory approval without mandatory public disclosure created conditions sufficient to sustain the information gap
Responsibility Attribution:
Agent: XYZ Consultants and MWC (shared)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Risk-Based Report Recommendation Issued
Engineer B issues a report identifying lead leaching risks and recommending treatment improvements -
Contradictory Consultant Report Issued
XYZ Consultants issue a competing report claiming insufficient information to predict risk severity, directly undermining Engineer B's findings -
Water Source Change Decided
MWC uses the contradictory report as justification to proceed with the source change without treatment improvements or public disclosure -
Regulatory Approval Granted
Regulatory approval is granted with a five-year compliance window but without mandatory public health disclosure requirements -
Health Risk Information Gap
The water-consuming public remains uninformed of lead leaching risks throughout the case, unable to make informed decisions about water consumption
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#CausalChain_05748c5b",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "XYZ Consultants produced a report stating that insufficient information existed to predict the severity of risks, thereby providing institutional cover for MWC\u0027s decision to proceed and contributing to the public remaining uninformed about the known lead leaching risks",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B issues a report identifying lead leaching risks and recommending treatment improvements",
"proeth:element": "Risk-Based Report Recommendation Issued",
"proeth:step": 1
},
{
"proeth:description": "XYZ Consultants issue a competing report claiming insufficient information to predict risk severity, directly undermining Engineer B\u0027s findings",
"proeth:element": "Contradictory Consultant Report Issued",
"proeth:step": 2
},
{
"proeth:description": "MWC uses the contradictory report as justification to proceed with the source change without treatment improvements or public disclosure",
"proeth:element": "Water Source Change Decided",
"proeth:step": 3
},
{
"proeth:description": "Regulatory approval is granted with a five-year compliance window but without mandatory public health disclosure requirements",
"proeth:element": "Regulatory Approval Granted",
"proeth:step": 4
},
{
"proeth:description": "The water-consuming public remains uninformed of lead leaching risks throughout the case, unable to make informed decisions about water consumption",
"proeth:element": "Health Risk Information Gap",
"proeth:step": 5
}
],
"proeth:cause": "Contradictory Consultant Report Issued",
"proeth:counterfactual": "Without the contradictory report, MWC would have faced a single, uncontested expert finding of risk, making it substantially harder to justify proceeding without treatment improvements or public notification; the information gap would have been more difficult to maintain",
"proeth:effect": "Health Risk Information Gap",
"proeth:necessaryFactors": [
"XYZ Consultants\u0027 willingness to issue a report contradicting Engineer B\u0027s findings without resolving the underlying technical dispute",
"MWC\u0027s use of the contradictory report to justify proceeding without treatment improvements",
"Absence of a regulatory or institutional mechanism to reconcile conflicting expert reports before public health decisions are made"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "XYZ Consultants and MWC (shared)",
"proeth:sufficientFactors": [
"Combination of contradictory expert reports, MWC\u0027s institutional authority, and regulatory approval without mandatory public disclosure created conditions sufficient to sustain the information gap"
],
"proeth:withinAgentControl": true
}
Causal Language: After reading in the newspaper that the State Department of the Environment approved the water source change, Engineer B deliberated whether further action was warranted; throughout the case, the water-consuming public remained uninformed about the known lead leaching risks
Necessary Factors (NESS):
- Engineer B's awareness of the regulatory approval and its implications for ongoing public health risk
- The absence of any other actor (MWC, XYZ Consultants, regulatory authority) taking responsibility for public notification
- Engineer B's continued possession of technical knowledge establishing the risk
Sufficient Factors:
- Engineer B's deliberation without further action, combined with all other actors' failure to disclose, was sufficient to sustain the information gap in the absence of any alternative disclosure mechanism
Responsibility Attribution:
Agent: Engineer B (indirect); MWC and Regulatory Authority (direct)
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Engineer B Discharged
Engineer B is removed from the project, limiting formal channels for further intervention -
Regulatory Approval Granted
State approval is granted with a five-year compliance window, signaling institutional closure without public disclosure -
Post-Approval Further Action Deliberation
Engineer B learns of approval via newspaper and deliberates whether professional ethics require further action -
Health Risk Information Gap
In the absence of further action by Engineer B or any other party, the public remains uninformed of lead leaching risks
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/18#",
"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/18#CausalChain_81354536",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "After reading in the newspaper that the State Department of the Environment approved the water source change, Engineer B deliberated whether further action was warranted; throughout the case, the water-consuming public remained uninformed about the known lead leaching risks",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B is removed from the project, limiting formal channels for further intervention",
"proeth:element": "Engineer B Discharged",
"proeth:step": 1
},
{
"proeth:description": "State approval is granted with a five-year compliance window, signaling institutional closure without public disclosure",
"proeth:element": "Regulatory Approval Granted",
"proeth:step": 2
},
{
"proeth:description": "Engineer B learns of approval via newspaper and deliberates whether professional ethics require further action",
"proeth:element": "Post-Approval Further Action Deliberation",
"proeth:step": 3
},
{
"proeth:description": "In the absence of further action by Engineer B or any other party, the public remains uninformed of lead leaching risks",
"proeth:element": "Health Risk Information Gap",
"proeth:step": 4
}
],
"proeth:cause": "Post-Approval Further Action Deliberation",
"proeth:counterfactual": "Had Engineer B taken further action \u2014 such as notifying public health authorities, media, or the public directly \u2014 the information gap may have been closed despite prior discharge; the deliberation without resolution was a missed intervention opportunity",
"proeth:effect": "Health Risk Information Gap",
"proeth:necessaryFactors": [
"Engineer B\u0027s awareness of the regulatory approval and its implications for ongoing public health risk",
"The absence of any other actor (MWC, XYZ Consultants, regulatory authority) taking responsibility for public notification",
"Engineer B\u0027s continued possession of technical knowledge establishing the risk"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Engineer B (indirect); MWC and Regulatory Authority (direct)",
"proeth:sufficientFactors": [
"Engineer B\u0027s deliberation without further action, combined with all other actors\u0027 failure to disclose, was sufficient to sustain the information gap in the absence of any alternative disclosure mechanism"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (15)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| MWC decision to proceed without treatment |
before
Entity1 is before Entity2 |
Engineer B's warning at public meeting |
time:before
http://www.w3.org/2006/time#before |
The MWC met and decided to proceed with the change in water source but to construct water treatment ... [more] |
| XYZ Consultants report |
after
Entity1 is after Entity2 |
Engineer B's original report |
time:after
http://www.w3.org/2006/time#after |
XYZ Consultants provided a report to the Water Commission indicating that insufficient information w... [more] |
| XYZ Consultants report |
before
Entity1 is before Entity2 |
State Department of the Environment approval |
time:before
http://www.w3.org/2006/time#before |
Several months later, Engineer B read in the local newspaper that the professional engineer in charg... [more] |
| MWC discharge of Engineer B |
before
Entity1 is before Entity2 |
newspaper report of regulatory approval |
time:before
http://www.w3.org/2006/time#before |
Several months later, Engineer B read in the local newspaper that...the State Department of the Envi... [more] |
| State Department of the Environment approval |
before
Entity1 is before Entity2 |
five-year water treatment implementation |
time:before
http://www.w3.org/2006/time#before |
The professional engineer...had approved the change of water source, with a five-year implementation... [more] |
| BER Case 76-4 |
before
Entity1 is before Entity2 |
BER Case 89-7 |
time:before
http://www.w3.org/2006/time#before |
Case numbers 76-4 and 89-7 suggest sequential BER case numbering by year, implying 76-4 precedes 89-... [more] |
| BER Case 89-7 |
before
Entity1 is before Entity2 |
BER Case 20-4 |
time:before
http://www.w3.org/2006/time#before |
Case numbers 89-7 and 20-4 suggest sequential BER case numbering by year, implying 89-7 precedes 20-... [more] |
| water treatment improvements |
before
Entity1 is before Entity2 |
water source change |
time:before
http://www.w3.org/2006/time#before |
Engineer B's report recommended the need for appropriate water treatment prior to making the change ... [more] |
| Engineer B's warning at public meeting |
before
Entity1 is before Entity2 |
Engineer B's written letter to Water Commissioners |
time:before
http://www.w3.org/2006/time#before |
Following the meeting, Engineer B provided the Water Commissioners with a letter detailing the risk ... [more] |
| Engineer B's written letter to Water Commissioners |
before
Entity1 is before Entity2 |
Engineer B's report and letter to State Department of the Environment |
time:before
http://www.w3.org/2006/time#before |
Engineer B subsequently sent the original report with a letter to the water supply division of the S... [more] |
| Engineer B's report and letter to State Department of the Environment |
before
Entity1 is before Entity2 |
MWC discharge of Engineer B and ABC Engineers |
time:before
http://www.w3.org/2006/time#before |
The MWC discharged Engineer B and ABC Engineers from project involvement in the water source change,... [more] |
| MWC discharge of Engineer B and ABC Engineers |
meets
Entity1 ends exactly when Entity2 begins |
retention of XYZ Consultants |
time:intervalMeets
http://www.w3.org/2006/time#intervalMeets |
The MWC discharged Engineer B and ABC Engineers from project involvement in the water source change,... [more] |
| water source change |
before
Entity1 is before Entity2 |
water treatment improvements (per MWC decision) |
time:before
http://www.w3.org/2006/time#before |
The MWC met and decided to proceed with the change in water source but to construct water treatment ... [more] |
| Engineer B's deliberation on continuing obligations |
after
Entity1 is after Entity2 |
newspaper report of regulatory approval |
time:after
http://www.w3.org/2006/time#after |
Engineer B continued to be concerned that public health and safety would be at risk and considered w... [more] |
| BER Case 20-4 |
equals
Entity1 and Entity2 have the same start and end times |
current case (Engineer B escalation to State Department) |
time:intervalEquals
http://www.w3.org/2006/time#intervalEquals |
BER Case 20-4 is directly related to the current case. In Case 20-4, Engineer B, the same Engineer B... [more] |
About Allen Relations & OWL-Time
Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.
Each relation includes both a ProEthica custom property and a
time:* OWL-Time property for maximum compatibility.