PASS 3: Temporal Dynamics
Case 132: Public Health and Safety— Observed Structural Defects and Inspection by County Building Official
Timeline Overview
OWL-Time Temporal Structure 27 relations time: = w3.org/2006/time
Extracted Actions (5)
Volitional professional decisions with intentions and ethical contextDescription: After the county building official failed to return Engineer A's phone call, Engineer A made no further attempt to escalate the structural safety concern to the official's supervisor, the fire marshal, or any other agency with jurisdictional authority, effectively ending active regulatory pursuit of the matter.
Temporal Marker: Following the unanswered call to the county building official (exact date unspecified)
Mental State: deliberate (by omission — a conscious choice to not pursue further escalation)
Intended Outcome: Implicitly, to allow the regulatory process to proceed on its own timeline after the initial contact, and to avoid overstepping the perceived boundaries of the engineer's role as a private consultant
Guided By Principles:
- Engineers shall not bow to employment situations or external inaction when dangers are present (BER 89-7, 90-5, 92-6)
- Engineers shall hold public safety paramount above all other considerations (NSPE Code Section I.1)
- Persistence in regulatory escalation is required when initial contacts are unresponsive
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A appears to have concluded — incorrectly from an ethical standpoint — that the duty to notify public authorities had been fulfilled by the single phone call to the county building official. The decision not to escalate may also reflect professional reluctance to appear adversarial, deference to institutional processes, uncertainty about the engineer's authority to escalate beyond the client relationship, or an underestimation of the collapse risk given that it was characterized as eventual rather than imminent.
Ethical Tension: The core tension is between professional comfort and deference (trusting that the system will work if given time, avoiding conflict with regulatory bodies or the client) and the affirmative public safety obligation that the NSPE Code places on engineers — which does not permit passivity when a known hazard goes unaddressed by the first authority contacted. The 'eventual but not imminent' characterization of the risk also creates tension: does a non-imminent risk justify less aggressive escalation?
Learning Significance: This is the primary ethical failure of the case and its most important teaching moment. The Board of Ethical Review determined that Engineer A's failure to escalate after the official's non-response was a violation of ethical obligations. Students learn that the duty to protect public safety is not discharged by a single good-faith attempt — it requires persistence, escalation through alternative channels, and documented follow-through until a responsible authority has actually engaged with the hazard.
Stakes: By ending active regulatory pursuit, Engineer A leaves a known structural hazard without any governmental oversight or enforcement action. The building may be re-occupied, the structural risk may worsen, and if collapse occurs, Engineer A bears significant ethical — and potentially legal — responsibility for having identified the risk and then abandoned the escalation process after a single unanswered call. The public, occupants, and future visitors to the building are all at risk.
Decision Point: Yes - Story can branch here
- Escalate within 24–48 hours of the unreturned call to the county building official's supervisor, documenting the original call, its date and time, and the failure to receive a response
- Contact the fire marshal or state building safety authority in parallel, framing the notification as a public safety concern that requires regulatory attention given the local official's non-response
- Send a formal written report of findings to the county building official via certified mail, with copies to the official's supervisor and the fire marshal, creating an undeniable paper trail that compels institutional response
Narrative Role: falling_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Action_Decision_Not_to_Further_Escalate",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Escalate within 24\u201348 hours of the unreturned call to the county building official\u0027s supervisor, documenting the original call, its date and time, and the failure to receive a response",
"Contact the fire marshal or state building safety authority in parallel, framing the notification as a public safety concern that requires regulatory attention given the local official\u0027s non-response",
"Send a formal written report of findings to the county building official via certified mail, with copies to the official\u0027s supervisor and the fire marshal, creating an undeniable paper trail that compels institutional response"
],
"proeth-scenario:characterMotivation": "Engineer A appears to have concluded \u2014 incorrectly from an ethical standpoint \u2014 that the duty to notify public authorities had been fulfilled by the single phone call to the county building official. The decision not to escalate may also reflect professional reluctance to appear adversarial, deference to institutional processes, uncertainty about the engineer\u0027s authority to escalate beyond the client relationship, or an underestimation of the collapse risk given that it was characterized as eventual rather than imminent.",
"proeth-scenario:consequencesIfAlternative": [
"Escalating to a supervisor is the most direct and procedurally appropriate next step \u2014 it respects the chain of authority while ensuring the hazard is not lost in an individual official\u0027s voicemail; this is what the Board of Ethical Review indicated was required",
"Contacting the fire marshal or state authority broadens the regulatory net and is particularly appropriate given that the building\u0027s hazard originated in the context of a fire investigation \u2014 the fire marshal has both jurisdictional interest and independent authority to act",
"A formal written report sent via certified mail to multiple officials simultaneously is the most documentable and professionally defensible escalation path \u2014 it creates legal notice, forces institutional acknowledgment, and demonstrates that Engineer A took every reasonable step to protect the public"
],
"proeth-scenario:decisionSignificance": "This is the primary ethical failure of the case and its most important teaching moment. The Board of Ethical Review determined that Engineer A\u0027s failure to escalate after the official\u0027s non-response was a violation of ethical obligations. Students learn that the duty to protect public safety is not discharged by a single good-faith attempt \u2014 it requires persistence, escalation through alternative channels, and documented follow-through until a responsible authority has actually engaged with the hazard.",
"proeth-scenario:ethicalTension": "The core tension is between professional comfort and deference (trusting that the system will work if given time, avoiding conflict with regulatory bodies or the client) and the affirmative public safety obligation that the NSPE Code places on engineers \u2014 which does not permit passivity when a known hazard goes unaddressed by the first authority contacted. The \u0027eventual but not imminent\u0027 characterization of the risk also creates tension: does a non-imminent risk justify less aggressive escalation?",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "falling_action",
"proeth-scenario:stakes": "By ending active regulatory pursuit, Engineer A leaves a known structural hazard without any governmental oversight or enforcement action. The building may be re-occupied, the structural risk may worsen, and if collapse occurs, Engineer A bears significant ethical \u2014 and potentially legal \u2014 responsibility for having identified the risk and then abandoned the escalation process after a single unanswered call. The public, occupants, and future visitors to the building are all at risk.",
"proeth:description": "After the county building official failed to return Engineer A\u0027s phone call, Engineer A made no further attempt to escalate the structural safety concern to the official\u0027s supervisor, the fire marshal, or any other agency with jurisdictional authority, effectively ending active regulatory pursuit of the matter.",
"proeth:foreseenUnintendedEffects": [
"The structural hazard would remain unaddressed by regulatory authority",
"Public safety risk would persist without official corrective action",
"Engineer A\u0027s professional and ethical obligations would remain unfulfilled"
],
"proeth:guidedByPrinciple": [
"Engineers shall not bow to employment situations or external inaction when dangers are present (BER 89-7, 90-5, 92-6)",
"Engineers shall hold public safety paramount above all other considerations (NSPE Code Section I.1)",
"Persistence in regulatory escalation is required when initial contacts are unresponsive"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer and Structural Engineer, hired by Client B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Proportionality of response to non-imminent risk vs. duty to persist in protecting public safety",
"proeth:resolutionReasoning": "Engineer A implicitly resolved the conflict by treating the non-imminent risk as sufficient justification for not escalating further; the Board rejected this reasoning, determining that the ongoing public safety obligation required escalation to the county official\u0027s supervisor, fire marshal, or other agencies regardless of the non-imminent characterization of the risk"
},
"proeth:hasMentalState": "deliberate (by omission \u2014 a conscious choice to not pursue further escalation)",
"proeth:intendedOutcome": "Implicitly, to allow the regulatory process to proceed on its own timeline after the initial contact, and to avoid overstepping the perceived boundaries of the engineer\u0027s role as a private consultant",
"proeth:requiresCapability": [
"Knowledge of regulatory escalation channels and alternative agencies with jurisdictional authority",
"Ability to communicate structural risk findings persuasively to multiple levels of regulatory authority",
"Professional judgment to assess when initial regulatory contacts are insufficient and escalation is required"
],
"proeth:temporalMarker": "Following the unanswered call to the county building official (exact date unspecified)",
"proeth:violatesObligation": [
"Obligation to continue pursuing corrective action until the public safety risk is adequately addressed (NSPE Code Section I.1)",
"Obligation to escalate to higher or alternative authorities when the initial regulatory contact is unresponsive",
"Obligation not to permit professional duties to be subordinated to the inaction of others when public safety is at stake",
"NSPE Code obligation to notify appropriate authorities and persist in doing so when the safety of the public is at risk"
],
"proeth:withinCompetence": true,
"rdfs:label": "Decision Not to Further Escalate"
}
Description: Upon observing structural instability during a fire investigation, Engineer A voluntarily expanded the scope of work beyond the contracted fire origin-and-cause investigation to perform a preliminary structural assessment of the building.
Temporal Marker: During the fire investigation (exact date unspecified)
Mental State: deliberate
Intended Outcome: Identify and document structural hazards observed incidentally during the fire investigation to protect public safety
Fulfills Obligations:
- NSPE Code obligation to hold public safety, health, and welfare paramount
- Obligation to use professional knowledge and skill in the public interest when a hazard is observed
- Obligation to act on competence — Engineer A was also a structural engineer and thus qualified to perform the assessment
Guided By Principles:
- Public safety paramount (NSPE Code Section I.1)
- Engineers shall act in such a manner as to uphold public safety when their professional judgment is engaged
- Professional responsibility extends beyond the strict contractual scope when public welfare is at stake
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A's professional training and ethical instincts compelled recognition that observed structural deficiencies — sagging roof, outward-leaning walls — posed a safety risk that could not be ignored simply because they fell outside the contracted scope of fire origin-and-cause investigation. The engineer felt a duty to the public that superseded the boundaries of the engagement contract.
Ethical Tension: Contractual fidelity and scope discipline (serving only what the client paid for) versus the engineer's broader public safety obligation under the NSPE Code of Ethics, which requires engineers to hold public safety paramount even when it conflicts with client or contractual constraints.
Learning Significance: Illustrates that an engineer's ethical obligations are not bounded by contract scope — when competence allows recognition of a hazard, professional duty requires action regardless of whether that hazard falls within the paid engagement. Students learn that 'it wasn't my job' is not an ethically acceptable defense when public safety is at stake.
Stakes: If Engineer A ignores the structural instability, an unaddressed collapse risk remains entirely undetected and unreported. If Engineer A acts, they assume new professional and legal responsibilities beyond the original contract, including potential liability for the adequacy of their structural assessment.
Decision Point: Yes - Story can branch here
- Limit observation to fire origin-and-cause only, noting structural concerns in a written report addendum without conducting any assessment
- Decline to assess the structure personally but immediately recommend the client retain a licensed structural engineer before re-occupying the building
- Document the observed conditions photographically and in field notes, then pause all work and consult the client before expanding scope
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Action_Scope_Expansion_to_Structural_Assessment",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Limit observation to fire origin-and-cause only, noting structural concerns in a written report addendum without conducting any assessment",
"Decline to assess the structure personally but immediately recommend the client retain a licensed structural engineer before re-occupying the building",
"Document the observed conditions photographically and in field notes, then pause all work and consult the client before expanding scope"
],
"proeth-scenario:characterMotivation": "Engineer A\u0027s professional training and ethical instincts compelled recognition that observed structural deficiencies \u2014 sagging roof, outward-leaning walls \u2014 posed a safety risk that could not be ignored simply because they fell outside the contracted scope of fire origin-and-cause investigation. The engineer felt a duty to the public that superseded the boundaries of the engagement contract.",
"proeth-scenario:consequencesIfAlternative": [
"The structural risk might be buried in a report addendum and overlooked by the client, delaying remediation and leaving occupants at risk \u2014 but Engineer A\u0027s contractual exposure would be minimized",
"This is arguably a more professionally defensible path that keeps the assessment within qualified structural engineering hands, though it introduces delay and depends on the client acting promptly on the referral",
"Pausing to consult the client respects contractual boundaries and client autonomy but introduces a time lag during which the building could be re-occupied, potentially increasing risk to life safety"
],
"proeth-scenario:decisionSignificance": "Illustrates that an engineer\u0027s ethical obligations are not bounded by contract scope \u2014 when competence allows recognition of a hazard, professional duty requires action regardless of whether that hazard falls within the paid engagement. Students learn that \u0027it wasn\u0027t my job\u0027 is not an ethically acceptable defense when public safety is at stake.",
"proeth-scenario:ethicalTension": "Contractual fidelity and scope discipline (serving only what the client paid for) versus the engineer\u0027s broader public safety obligation under the NSPE Code of Ethics, which requires engineers to hold public safety paramount even when it conflicts with client or contractual constraints.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "If Engineer A ignores the structural instability, an unaddressed collapse risk remains entirely undetected and unreported. If Engineer A acts, they assume new professional and legal responsibilities beyond the original contract, including potential liability for the adequacy of their structural assessment.",
"proeth:description": "Upon observing structural instability during a fire investigation, Engineer A voluntarily expanded the scope of work beyond the contracted fire origin-and-cause investigation to perform a preliminary structural assessment of the building.",
"proeth:foreseenUnintendedEffects": [
"Potential conflict with the defined scope of the client engagement",
"Possible exposure to liability outside contracted services",
"Discovery of findings that would obligate further action beyond the original assignment"
],
"proeth:fulfillsObligation": [
"NSPE Code obligation to hold public safety, health, and welfare paramount",
"Obligation to use professional knowledge and skill in the public interest when a hazard is observed",
"Obligation to act on competence \u2014 Engineer A was also a structural engineer and thus qualified to perform the assessment"
],
"proeth:guidedByPrinciple": [
"Public safety paramount (NSPE Code Section I.1)",
"Engineers shall act in such a manner as to uphold public safety when their professional judgment is engaged",
"Professional responsibility extends beyond the strict contractual scope when public welfare is at stake"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer and Structural Engineer, hired by Client B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Contractual scope adherence vs. public safety duty",
"proeth:resolutionReasoning": "Engineer A resolved the conflict in favor of public safety, consistent with the NSPE Code\u0027s foundational principle that public welfare is the overriding value in engineering practice; the possession of structural engineering competence made this expansion professionally defensible"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Identify and document structural hazards observed incidentally during the fire investigation to protect public safety",
"proeth:requiresCapability": [
"Structural engineering analysis",
"Building assessment and inspection skills",
"Ability to identify signs of lateral instability, roof sag, and wall displacement"
],
"proeth:temporalMarker": "During the fire investigation (exact date unspecified)",
"proeth:withinCompetence": true,
"rdfs:label": "Scope Expansion to Structural Assessment"
}
Description: After concluding the preliminary structural investigation, Engineer A immediately and verbally advised Client B of the structural danger, including the risk of eventual building collapse due to insufficient lateral restraint from recent construction modifications.
Temporal Marker: Immediately following the preliminary structural investigation (exact date unspecified)
Mental State: deliberate
Intended Outcome: Ensure Client B was informed of the structural hazard so that the building owner could take protective action and provide informed consent for further steps
Fulfills Obligations:
- Obligation to notify the client of discovered hazards affecting the safety of the structure
- Obligation to be transparent and forthright with the client about findings material to public safety
- NSPE Code obligation to inform relevant parties of safety risks
Guided By Principles:
- Engineers shall be objective and truthful in professional reports and communications (NSPE Code Section III.3)
- Engineers shall notify clients of consequences when professional judgment is overridden
- Timely disclosure of safety-relevant findings
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A recognized an immediate professional and ethical obligation to ensure the client — as the building owner and the party with direct control over the property — was informed of the danger so that protective action could be taken quickly. Verbal notification was chosen for its speed, reflecting urgency.
Ethical Tension: The imperative for speed (verbal notification is immediate) conflicts with the imperative for documentation and clarity (written notification creates a verifiable record, reduces ambiguity about what was communicated, and protects all parties). There is also tension between serving the client's interests and potentially alarming them in ways that could trigger adverse legal or financial consequences for the client.
Learning Significance: Demonstrates that while verbal notification satisfies an immediate duty to warn, it is insufficient as a standalone professional act in high-stakes safety situations. Students learn the importance of written documentation as both an ethical and professional practice standard — verbal-only warnings, as reinforced by BER 07-10, have been found inadequate by the Board of Ethical Review.
Stakes: If Client B receives only a verbal warning, there is no written record of what was communicated, when, or with what specificity. Client B could later claim ignorance, misunderstand the severity, or fail to act — and Engineer A has no documentation to demonstrate fulfillment of the duty to warn. Occupants of the building remain at risk if the client does not act on an unconfirmed verbal exchange.
Decision Point: Yes - Story can branch here
- Provide an immediate verbal warning followed within 24 hours by a written notice (letter or email) specifying the observed conditions, the risk assessment, and recommended actions
- Refuse to leave the site or allow re-occupancy until a written safety notice is acknowledged by the client in writing
- Notify Client B verbally and simultaneously begin drafting a formal written report to be delivered the same day, treating the situation with the urgency of an emergency disclosure
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Action_Verbal_Notification_to_Client_B",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Provide an immediate verbal warning followed within 24 hours by a written notice (letter or email) specifying the observed conditions, the risk assessment, and recommended actions",
"Refuse to leave the site or allow re-occupancy until a written safety notice is acknowledged by the client in writing",
"Notify Client B verbally and simultaneously begin drafting a formal written report to be delivered the same day, treating the situation with the urgency of an emergency disclosure"
],
"proeth-scenario:characterMotivation": "Engineer A recognized an immediate professional and ethical obligation to ensure the client \u2014 as the building owner and the party with direct control over the property \u2014 was informed of the danger so that protective action could be taken quickly. Verbal notification was chosen for its speed, reflecting urgency.",
"proeth-scenario:consequencesIfAlternative": [
"This is the professionally and ethically superior path \u2014 the verbal warning addresses immediacy while the written follow-up creates a durable record, reduces miscommunication risk, and satisfies the documentation standard expected of licensed engineers",
"This approach maximizes safety but may damage the client relationship and exceed Engineer A\u0027s authority to control site access; however, it demonstrates the highest commitment to public safety over client comfort",
"Combining immediacy with documentation is the gold standard response; it signals to the client the seriousness of the situation and provides Engineer A with defensible evidence of fulfilling the duty to warn"
],
"proeth-scenario:decisionSignificance": "Demonstrates that while verbal notification satisfies an immediate duty to warn, it is insufficient as a standalone professional act in high-stakes safety situations. Students learn the importance of written documentation as both an ethical and professional practice standard \u2014 verbal-only warnings, as reinforced by BER 07-10, have been found inadequate by the Board of Ethical Review.",
"proeth-scenario:ethicalTension": "The imperative for speed (verbal notification is immediate) conflicts with the imperative for documentation and clarity (written notification creates a verifiable record, reduces ambiguity about what was communicated, and protects all parties). There is also tension between serving the client\u0027s interests and potentially alarming them in ways that could trigger adverse legal or financial consequences for the client.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If Client B receives only a verbal warning, there is no written record of what was communicated, when, or with what specificity. Client B could later claim ignorance, misunderstand the severity, or fail to act \u2014 and Engineer A has no documentation to demonstrate fulfillment of the duty to warn. Occupants of the building remain at risk if the client does not act on an unconfirmed verbal exchange.",
"proeth:description": "After concluding the preliminary structural investigation, Engineer A immediately and verbally advised Client B of the structural danger, including the risk of eventual building collapse due to insufficient lateral restraint from recent construction modifications.",
"proeth:foreseenUnintendedEffects": [
"Client B might resist or dispute the findings given that a certificate of occupancy had been issued",
"Verbal-only notification creates no durable record of the warning",
"Client B might take no action, leaving the public safety risk unresolved"
],
"proeth:fulfillsObligation": [
"Obligation to notify the client of discovered hazards affecting the safety of the structure",
"Obligation to be transparent and forthright with the client about findings material to public safety",
"NSPE Code obligation to inform relevant parties of safety risks"
],
"proeth:guidedByPrinciple": [
"Engineers shall be objective and truthful in professional reports and communications (NSPE Code Section III.3)",
"Engineers shall notify clients of consequences when professional judgment is overridden",
"Timely disclosure of safety-relevant findings"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer and Structural Engineer, hired by Client B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Speed of notification vs. formality and documentation of warning",
"proeth:resolutionReasoning": "Engineer A prioritized immediacy of verbal communication; however, consistent with the Board\u0027s reasoning in BER 07-10, a written follow-up would have been ethically required to fully discharge the notification obligation"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Ensure Client B was informed of the structural hazard so that the building owner could take protective action and provide informed consent for further steps",
"proeth:requiresCapability": [
"Clear communication of technical findings to a non-engineer client",
"Ability to convey risk severity and proportionality accurately"
],
"proeth:temporalMarker": "Immediately following the preliminary structural investigation (exact date unspecified)",
"proeth:violatesObligation": [
"Obligation to document safety notifications in writing \u2014 verbal-only notification, as highlighted in BER 07-10, is insufficient to create an enforceable and durable record of the warning"
],
"proeth:withinCompetence": true,
"rdfs:label": "Verbal Notification to Client B"
}
Description: Engineer A recommended to the building owners that they brace the building to prevent collapse, providing a specific remediation action to mitigate the identified structural risk while awaiting regulatory or other corrective action.
Temporal Marker: Following the preliminary structural investigation and notifications (exact date unspecified)
Mental State: deliberate
Intended Outcome: Reduce the risk of building collapse by providing the owners with a concrete interim mitigation measure within the engineer's professional authority to recommend, protecting both the owners and any members of the public who might be exposed to the structure
Fulfills Obligations:
- Obligation to provide professional guidance to mitigate identified safety risks
- Obligation to act in the interest of public safety by recommending protective measures
- Obligation to be forthright with clients and owners about steps needed to address safety hazards (NSPE Code Section III.2)
Guided By Principles:
- Engineers shall hold public safety paramount and shall act to protect the public when safety is at risk (NSPE Code Section I.1)
- Engineers shall be objective and truthful in professional reports and communications (NSPE Code Section III.3)
- Proactive risk mitigation as a professional duty
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Having identified a specific structural deficiency — insufficient lateral restraint — Engineer A sought to provide actionable, technically grounded guidance to the building owners that could reduce the risk of collapse in the near term, even before regulatory or formal remediation processes could be completed. The motivation reflects both engineering competence and a desire to be practically helpful to the client.
Ethical Tension: Providing a specific remediation recommendation (bracing) is a constructive act that serves immediate safety, but it may also create a false sense of security — the owners may interpret 'brace the building' as a complete solution, reducing their urgency to pursue more comprehensive structural engineering review, regulatory compliance, or occupancy restrictions. There is also tension between the engineer's role as investigator versus structural design authority.
Learning Significance: Illustrates that safety recommendations must be accompanied by clear communication of their limitations. Students learn that recommending a mitigation measure without also specifying whether the building should remain occupied during implementation, who is qualified to design the bracing, and what follow-up is required can inadvertently undermine the urgency of the safety message.
Stakes: If the owners implement bracing adequately and promptly, the collapse risk is meaningfully reduced. If they implement inadequate bracing, delay implementation, or treat the recommendation as fully resolving the issue without further structural engineering engagement, the risk of collapse remains — and Engineer A may bear partial responsibility for providing guidance that was acted upon incorrectly.
Decision Point: Yes - Story can branch here
- Recommend bracing explicitly as a temporary emergency measure only, paired with a written directive that the building must not be occupied until a licensed structural engineer has designed and certified the bracing system
- Decline to specify a remediation action within the fire investigation scope and instead provide a written referral to a structural engineer, making clear that remediation design is outside Engineer A's contracted and possibly licensed scope
- Recommend both bracing and immediate voluntary closure of the building pending regulatory review, framing the bracing as insufficient on its own to guarantee safety
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Action_Bracing_Recommendation_to_Owners",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Recommend bracing explicitly as a temporary emergency measure only, paired with a written directive that the building must not be occupied until a licensed structural engineer has designed and certified the bracing system",
"Decline to specify a remediation action within the fire investigation scope and instead provide a written referral to a structural engineer, making clear that remediation design is outside Engineer A\u0027s contracted and possibly licensed scope",
"Recommend both bracing and immediate voluntary closure of the building pending regulatory review, framing the bracing as insufficient on its own to guarantee safety"
],
"proeth-scenario:characterMotivation": "Having identified a specific structural deficiency \u2014 insufficient lateral restraint \u2014 Engineer A sought to provide actionable, technically grounded guidance to the building owners that could reduce the risk of collapse in the near term, even before regulatory or formal remediation processes could be completed. The motivation reflects both engineering competence and a desire to be practically helpful to the client.",
"proeth-scenario:consequencesIfAlternative": [
"This approach correctly frames the engineer\u0027s role, sets appropriate expectations, and protects occupants \u2014 it is more complete and ethically sound than a standalone bracing recommendation",
"This is professionally conservative and avoids scope creep into structural remediation design, but may leave the client without enough guidance to take meaningful immediate action, increasing short-term risk",
"Combining a remediation recommendation with a voluntary closure recommendation is the most safety-protective approach, though it may meet resistance from the client due to the financial and operational impact of closure"
],
"proeth-scenario:decisionSignificance": "Illustrates that safety recommendations must be accompanied by clear communication of their limitations. Students learn that recommending a mitigation measure without also specifying whether the building should remain occupied during implementation, who is qualified to design the bracing, and what follow-up is required can inadvertently undermine the urgency of the safety message.",
"proeth-scenario:ethicalTension": "Providing a specific remediation recommendation (bracing) is a constructive act that serves immediate safety, but it may also create a false sense of security \u2014 the owners may interpret \u0027brace the building\u0027 as a complete solution, reducing their urgency to pursue more comprehensive structural engineering review, regulatory compliance, or occupancy restrictions. There is also tension between the engineer\u0027s role as investigator versus structural design authority.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If the owners implement bracing adequately and promptly, the collapse risk is meaningfully reduced. If they implement inadequate bracing, delay implementation, or treat the recommendation as fully resolving the issue without further structural engineering engagement, the risk of collapse remains \u2014 and Engineer A may bear partial responsibility for providing guidance that was acted upon incorrectly.",
"proeth:description": "Engineer A recommended to the building owners that they brace the building to prevent collapse, providing a specific remediation action to mitigate the identified structural risk while awaiting regulatory or other corrective action.",
"proeth:foreseenUnintendedEffects": [
"Owners might not follow the recommendation, leaving the hazard unmitigated",
"Recommendation without written documentation may not create enforceable accountability",
"Interim bracing may give a false sense of resolution, reducing urgency for permanent structural remediation"
],
"proeth:fulfillsObligation": [
"Obligation to provide professional guidance to mitigate identified safety risks",
"Obligation to act in the interest of public safety by recommending protective measures",
"Obligation to be forthright with clients and owners about steps needed to address safety hazards (NSPE Code Section III.2)"
],
"proeth:guidedByPrinciple": [
"Engineers shall hold public safety paramount and shall act to protect the public when safety is at risk (NSPE Code Section I.1)",
"Engineers shall be objective and truthful in professional reports and communications (NSPE Code Section III.3)",
"Proactive risk mitigation as a professional duty"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer and Structural Engineer, hired by Client B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Advisory recommendation vs. enforceable documented directive",
"proeth:resolutionReasoning": "Engineer A chose to make a verbal recommendation, prioritizing immediacy and the advisory relationship; however, the ethical standard implied by BER 07-10 and the Board\u0027s discussion suggests a written recommendation with follow-up would have been required to fully discharge this obligation"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Reduce the risk of building collapse by providing the owners with a concrete interim mitigation measure within the engineer\u0027s professional authority to recommend, protecting both the owners and any members of the public who might be exposed to the structure",
"proeth:requiresCapability": [
"Structural engineering knowledge sufficient to identify appropriate interim bracing solutions",
"Ability to communicate technical remediation recommendations to non-engineer building owners"
],
"proeth:temporalMarker": "Following the preliminary structural investigation and notifications (exact date unspecified)",
"proeth:violatesObligation": [
"Obligation to document the recommendation in writing to create a durable record",
"Obligation to follow up to confirm whether the bracing recommendation was implemented"
],
"proeth:withinCompetence": true,
"rdfs:label": "Bracing Recommendation to Owners"
}
Description: Engineer A contacted the county building official by phone to report the structural hazard, but did not escalate further after the official failed to return the call, leaving the regulatory notification at a single unanswered attempt.
Temporal Marker: Immediately following or concurrent with notification to Client B (exact date unspecified)
Mental State: deliberate
Intended Outcome: Notify the regulatory authority responsible for building safety so that an official investigation could be initiated and corrective action mandated, given that the official had previously issued a certificate of occupancy for the modified building
Fulfills Obligations:
- Initial obligation to notify the authority having jurisdiction over the building's safety
- Obligation to report conditions that endanger public safety to competent authorities (NSPE Code Section I.1 and III.2)
Guided By Principles:
- Engineers shall notify appropriate authorities when public safety is endangered (NSPE Code Section I.1)
- Engineers shall not complete, sign, or seal plans that are not in conformity with applicable engineering standards
- Persistence in protecting public welfare when initial efforts are insufficient
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A recognized that a county building official, as the governmental authority that issued the certificate of occupancy, held jurisdictional responsibility for the building's safety status and had the regulatory power to order corrective action or restrict occupancy. Contacting the official was an attempt to engage the appropriate public authority — but Engineer A treated a single unanswered phone call as sufficient discharge of that duty.
Ethical Tension: The engineer's duty to notify public authorities conflicts with a tendency toward professional deference and conflict avoidance — assuming that a single good-faith attempt satisfies the obligation. There is also tension between respecting institutional processes (waiting for the official to respond through normal channels) and the urgency of a structural safety risk that may not tolerate bureaucratic delay.
Learning Significance: This is the central ethical failure identified by the Board of Ethical Review. Students learn that a single unanswered phone call does not constitute adequate notification to a public authority when public safety is at stake. The NSPE Code requires engineers to escalate — to supervisors, alternate agencies, or other authorities — when initial contacts are unresponsive. 'I called and they didn't call back' is not ethically sufficient.
Stakes: The county building official is the regulatory gatekeeper with authority to restrict occupancy and mandate repairs. Failure to successfully engage this authority means the building may continue to be occupied or re-occupied without any regulatory oversight of the known structural risk. If the building collapses and it is discovered that the engineer made only one unanswered phone call, the engineer faces serious professional, legal, and reputational consequences.
Decision Point: Yes - Story can branch here
- Follow up the phone call with a written communication (certified letter, email, or formal report) to the county building official documenting the structural findings and requesting a written response or site inspection
- After the phone call goes unreturned within a reasonable period (e.g., 24–48 hours), escalate to the building official's supervisor, the county administrator, or the fire marshal
- Contact multiple agencies simultaneously — the building official, fire marshal, and any state-level building safety authority — to ensure at least one regulatory body receives and acts on the notification
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Action_Call_to_County_Building_Official",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Follow up the phone call with a written communication (certified letter, email, or formal report) to the county building official documenting the structural findings and requesting a written response or site inspection",
"After the phone call goes unreturned within a reasonable period (e.g., 24\u201348 hours), escalate to the building official\u0027s supervisor, the county administrator, or the fire marshal",
"Contact multiple agencies simultaneously \u2014 the building official, fire marshal, and any state-level building safety authority \u2014 to ensure at least one regulatory body receives and acts on the notification"
],
"proeth-scenario:characterMotivation": "Engineer A recognized that a county building official, as the governmental authority that issued the certificate of occupancy, held jurisdictional responsibility for the building\u0027s safety status and had the regulatory power to order corrective action or restrict occupancy. Contacting the official was an attempt to engage the appropriate public authority \u2014 but Engineer A treated a single unanswered phone call as sufficient discharge of that duty.",
"proeth-scenario:consequencesIfAlternative": [
"Written communication creates an official record of the notification, forces the agency to formally acknowledge or respond, and significantly strengthens Engineer A\u0027s ethical and legal position \u2014 this is a minimum standard that should accompany or follow any verbal contact",
"Escalation to a supervisor or alternate agency is exactly what the Board of Ethical Review determined was ethically required; it reflects the principle that when one avenue fails, the engineer\u0027s duty to the public requires pursuing others",
"Multi-agency notification maximizes the likelihood that at least one authority will act, though it risks appearing adversarial to the client and the county; however, in a genuine public safety emergency, this aggressive approach may be ethically justified"
],
"proeth-scenario:decisionSignificance": "This is the central ethical failure identified by the Board of Ethical Review. Students learn that a single unanswered phone call does not constitute adequate notification to a public authority when public safety is at stake. The NSPE Code requires engineers to escalate \u2014 to supervisors, alternate agencies, or other authorities \u2014 when initial contacts are unresponsive. \u0027I called and they didn\u0027t call back\u0027 is not ethically sufficient.",
"proeth-scenario:ethicalTension": "The engineer\u0027s duty to notify public authorities conflicts with a tendency toward professional deference and conflict avoidance \u2014 assuming that a single good-faith attempt satisfies the obligation. There is also tension between respecting institutional processes (waiting for the official to respond through normal channels) and the urgency of a structural safety risk that may not tolerate bureaucratic delay.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "The county building official is the regulatory gatekeeper with authority to restrict occupancy and mandate repairs. Failure to successfully engage this authority means the building may continue to be occupied or re-occupied without any regulatory oversight of the known structural risk. If the building collapses and it is discovered that the engineer made only one unanswered phone call, the engineer faces serious professional, legal, and reputational consequences.",
"proeth:description": "Engineer A contacted the county building official by phone to report the structural hazard, but did not escalate further after the official failed to return the call, leaving the regulatory notification at a single unanswered attempt.",
"proeth:foreseenUnintendedEffects": [
"The official might not respond, leaving the hazard unaddressed by regulatory authority",
"A single phone call creates no written record of the notification attempt",
"Non-response might be interpreted as official indifference, requiring further escalation"
],
"proeth:fulfillsObligation": [
"Initial obligation to notify the authority having jurisdiction over the building\u0027s safety",
"Obligation to report conditions that endanger public safety to competent authorities (NSPE Code Section I.1 and III.2)"
],
"proeth:guidedByPrinciple": [
"Engineers shall notify appropriate authorities when public safety is endangered (NSPE Code Section I.1)",
"Engineers shall not complete, sign, or seal plans that are not in conformity with applicable engineering standards",
"Persistence in protecting public welfare when initial efforts are insufficient"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer and Structural Engineer, hired by Client B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Deference to regulatory authority vs. independent duty to escalate for public safety",
"proeth:resolutionReasoning": "Engineer A resolved the conflict by deferring to the regulatory official and not escalating further; the Board determined this resolution was ethically inadequate given the ongoing public safety risk, and that escalation to the official\u0027s supervisor, fire marshal, or other agencies was required"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Notify the regulatory authority responsible for building safety so that an official investigation could be initiated and corrective action mandated, given that the official had previously issued a certificate of occupancy for the modified building",
"proeth:requiresCapability": [
"Knowledge of regulatory reporting channels and jurisdictional authority",
"Ability to communicate structural risk findings clearly to regulatory officials"
],
"proeth:temporalMarker": "Immediately following or concurrent with notification to Client B (exact date unspecified)",
"proeth:violatesObligation": [
"Obligation to escalate when the initial regulatory contact is unresponsive \u2014 the Board concluded Engineer A should have contacted the county official\u0027s supervisor, the fire marshal, or other agencies after the unanswered call",
"Obligation to document the notification attempt in writing",
"Obligation to persist in pursuing corrective action until the safety risk is adequately addressed"
],
"proeth:withinCompetence": true,
"rdfs:label": "Call to County Building Official"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: A fire breaks out at a building owned by Client B, triggering the need for an engineering investigation. This exogenous event sets the entire case in motion.
Temporal Marker: Prior to investigation; the initiating event of the case
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Property_Damage_Response_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Alarm and distress for Client B as property owner; urgency and professional alertness for Engineer A upon being hired; concern among building occupants or neighbors
- client_b: Property damage, financial loss, potential liability, disruption of use of building
- engineer_a: Professional engagement initiated; responsibility to investigate thoroughly and honestly
- public: Potential safety risk if building is structurally compromised post-fire
- county_building_official: Implicitly put on notice that a previously certified building has suffered damage
Learning Moment: Exogenous events like fires can expose pre-existing structural vulnerabilities that were previously undetected or overlooked, elevating the engineer's investigative responsibilities beyond the immediate cause of the event.
Ethical Implications: Reveals that certificates of occupancy may create false assurance; highlights the gap between regulatory compliance and actual safety; raises questions about ongoing duty of care for building owners and officials
- How does an exogenous event like a fire change the scope of an engineer's professional obligations?
- Should Client B have been conducting routine structural assessments prior to the fire?
- What responsibilities does a building owner have to ensure ongoing structural integrity after receiving a certificate of occupancy?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Event_Fire_Occurs_at_Building",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"How does an exogenous event like a fire change the scope of an engineer\u0027s professional obligations?",
"Should Client B have been conducting routine structural assessments prior to the fire?",
"What responsibilities does a building owner have to ensure ongoing structural integrity after receiving a certificate of occupancy?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Alarm and distress for Client B as property owner; urgency and professional alertness for Engineer A upon being hired; concern among building occupants or neighbors",
"proeth-scenario:ethicalImplications": "Reveals that certificates of occupancy may create false assurance; highlights the gap between regulatory compliance and actual safety; raises questions about ongoing duty of care for building owners and officials",
"proeth-scenario:learningMoment": "Exogenous events like fires can expose pre-existing structural vulnerabilities that were previously undetected or overlooked, elevating the engineer\u0027s investigative responsibilities beyond the immediate cause of the event.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"client_b": "Property damage, financial loss, potential liability, disruption of use of building",
"county_building_official": "Implicitly put on notice that a previously certified building has suffered damage",
"engineer_a": "Professional engagement initiated; responsibility to investigate thoroughly and honestly",
"public": "Potential safety risk if building is structurally compromised post-fire"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Property_Damage_Response_Constraint"
],
"proeth:causesStateChange": "Building transitions from occupied/operational status to damaged/potentially unsafe status; Client B initiates engineering engagement",
"proeth:createsObligation": [
"Hire_Qualified_Investigator",
"Assess_Damage_and_Safety",
"Notify_Relevant_Authorities"
],
"proeth:description": "A fire breaks out at a building owned by Client B, triggering the need for an engineering investigation. This exogenous event sets the entire case in motion.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Prior to investigation; the initiating event of the case",
"proeth:urgencyLevel": "high",
"rdfs:label": "Fire Occurs at Building"
}
Description: During the fire investigation, Engineer A discovers sagging roof and outward-leaning walls, indicating serious structural instability likely caused by recent construction modifications. This discovery transforms a routine fire investigation into a public safety emergency.
Temporal Marker: During the fire investigation; after Engineer A begins on-site assessment
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Duty_to_Warn_Constraint
- Mandatory_Disclosure_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Alarm and professional gravity for Engineer A upon recognizing the danger; anxiety and disbelief for Client B when informed; unease among any occupants or neighbors; heightened sense of professional responsibility for Engineer A
- engineer_a: Thrust into a public safety crisis beyond the original engagement; professional and ethical obligations escalate dramatically; potential liability if findings are not acted upon
- client_b: Faces potential loss of use of building, cost of remediation, and liability for occupant or public safety
- public: At risk of harm if building collapses without warning or remediation
- county_building_official: Prior certificate of occupancy is implicitly called into question; regulatory oversight failure is exposed
- future_occupants: Immediate safety risk if building is not remediated or closed
Learning Moment: The discovery of an unrelated but critical safety hazard during a professional engagement creates a non-negotiable ethical obligation to act beyond the original scope of work. Engineers must recognize that their duty to public safety supersedes the boundaries of their contract.
Ethical Implications: Exposes the tension between contractual obligations to a client and broader duties to public safety; raises questions about the adequacy of regulatory oversight; demonstrates that professional competence creates professional responsibility — knowing about a hazard obligates action
- At what point does a professional obligation to report safety findings override the contractual scope of an engagement?
- How should Engineer A weigh the fact that the collapse is 'eventual but not imminent' when deciding how urgently to act?
- What does this discovery reveal about the limitations of certificates of occupancy as safety guarantees?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Event_Structural_Instability_Discovered",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"At what point does a professional obligation to report safety findings override the contractual scope of an engagement?",
"How should Engineer A weigh the fact that the collapse is \u0027eventual but not imminent\u0027 when deciding how urgently to act?",
"What does this discovery reveal about the limitations of certificates of occupancy as safety guarantees?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Alarm and professional gravity for Engineer A upon recognizing the danger; anxiety and disbelief for Client B when informed; unease among any occupants or neighbors; heightened sense of professional responsibility for Engineer A",
"proeth-scenario:ethicalImplications": "Exposes the tension between contractual obligations to a client and broader duties to public safety; raises questions about the adequacy of regulatory oversight; demonstrates that professional competence creates professional responsibility \u2014 knowing about a hazard obligates action",
"proeth-scenario:learningMoment": "The discovery of an unrelated but critical safety hazard during a professional engagement creates a non-negotiable ethical obligation to act beyond the original scope of work. Engineers must recognize that their duty to public safety supersedes the boundaries of their contract.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"client_b": "Faces potential loss of use of building, cost of remediation, and liability for occupant or public safety",
"county_building_official": "Prior certificate of occupancy is implicitly called into question; regulatory oversight failure is exposed",
"engineer_a": "Thrust into a public safety crisis beyond the original engagement; professional and ethical obligations escalate dramatically; potential liability if findings are not acted upon",
"future_occupants": "Immediate safety risk if building is not remediated or closed",
"public": "At risk of harm if building collapses without warning or remediation"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Duty_to_Warn_Constraint",
"Mandatory_Disclosure_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/132#Action_Scope_Expansion_to_Structural_Assessment",
"proeth:causesStateChange": "Engineer A\u0027s role expands from fire investigator to structural safety whistleblower; building is now known to be at risk of collapse; public safety obligations are fully activated",
"proeth:createsObligation": [
"Immediately_Notify_Client",
"Notify_Relevant_Authorities",
"Recommend_Remediation_Measures",
"Document_Findings_Formally",
"Escalate_If_No_Response"
],
"proeth:description": "During the fire investigation, Engineer A discovers sagging roof and outward-leaning walls, indicating serious structural instability likely caused by recent construction modifications. This discovery transforms a routine fire investigation into a public safety emergency.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "During the fire investigation; after Engineer A begins on-site assessment",
"proeth:urgencyLevel": "critical",
"rdfs:label": "Structural Instability Discovered"
}
Description: The previously issued certificate of occupancy by the county building official is rendered effectively void by Engineer A's findings of structural instability, revealing a failure of the regulatory certification process. This is not a formal administrative act but a factual condition that undermines the legal and safety assurance the certificate was meant to provide.
Temporal Marker: Concurrent with structural instability discovery; the certificate was issued prior to the fire
Activates Constraints:
- Regulatory_Notification_Constraint
- Public_Safety_Disclosure_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Frustration and concern for Engineer A, who must now navigate a regulatory system that has failed; potential defensiveness or embarrassment for the county building official; distrust and anxiety for Client B who relied on the certificate; alarm for the public
- county_building_official: Professional credibility and regulatory authority called into question; potential liability for inadequate oversight
- client_b: Relied on certificate as assurance of safety; now faces uncertainty about legal standing and liability
- engineer_a: Must navigate the politically sensitive task of contradicting a government official's prior determination
- public: Exposed to risk that regulatory certification did not prevent
- regulatory_system: Systemic gap exposed — certificates do not account for post-issuance modifications
Learning Moment: Regulatory certifications like certificates of occupancy are point-in-time assessments that do not guarantee ongoing safety, especially after modifications. Engineers must not defer to regulatory approval when their own professional assessment reveals a hazard.
Ethical Implications: Reveals the limits of regulatory compliance as a proxy for safety; highlights the engineer's independent duty to assess and report rather than defer to official determinations; raises questions about accountability when regulatory systems fail
- Should Engineer A treat the existing certificate of occupancy as a reason to moderate the urgency of the safety concern, or should independent professional judgment take precedence?
- What systemic reforms could prevent the gap between certification and actual ongoing safety?
- How should an engineer communicate findings that implicitly criticize a government official's prior determination?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Event_Certificate_of_Occupancy_Invalidated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Should Engineer A treat the existing certificate of occupancy as a reason to moderate the urgency of the safety concern, or should independent professional judgment take precedence?",
"What systemic reforms could prevent the gap between certification and actual ongoing safety?",
"How should an engineer communicate findings that implicitly criticize a government official\u0027s prior determination?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Frustration and concern for Engineer A, who must now navigate a regulatory system that has failed; potential defensiveness or embarrassment for the county building official; distrust and anxiety for Client B who relied on the certificate; alarm for the public",
"proeth-scenario:ethicalImplications": "Reveals the limits of regulatory compliance as a proxy for safety; highlights the engineer\u0027s independent duty to assess and report rather than defer to official determinations; raises questions about accountability when regulatory systems fail",
"proeth-scenario:learningMoment": "Regulatory certifications like certificates of occupancy are point-in-time assessments that do not guarantee ongoing safety, especially after modifications. Engineers must not defer to regulatory approval when their own professional assessment reveals a hazard.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"client_b": "Relied on certificate as assurance of safety; now faces uncertainty about legal standing and liability",
"county_building_official": "Professional credibility and regulatory authority called into question; potential liability for inadequate oversight",
"engineer_a": "Must navigate the politically sensitive task of contradicting a government official\u0027s prior determination",
"public": "Exposed to risk that regulatory certification did not prevent",
"regulatory_system": "Systemic gap exposed \u2014 certificates do not account for post-issuance modifications"
},
"proeth:activatesConstraint": [
"Regulatory_Notification_Constraint",
"Public_Safety_Disclosure_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/132#Action_Scope_Expansion_to_Structural_Assessment",
"proeth:causesStateChange": "The regulatory assurance provided by the certificate of occupancy is factually nullified; the county building official\u0027s prior determination is called into question; a regulatory gap is exposed",
"proeth:createsObligation": [
"Notify_County_Building_Official_of_Findings",
"Escalate_to_Supervisory_Authority_if_No_Response",
"Document_Discrepancy_Between_Certification_and_Actual_Condition"
],
"proeth:description": "The previously issued certificate of occupancy by the county building official is rendered effectively void by Engineer A\u0027s findings of structural instability, revealing a failure of the regulatory certification process. This is not a formal administrative act but a factual condition that undermines the legal and safety assurance the certificate was meant to provide.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Concurrent with structural instability discovery; the certificate was issued prior to the fire",
"proeth:urgencyLevel": "high",
"rdfs:label": "Certificate of Occupancy Invalidated"
}
Description: After Engineer A calls the county building official to report the structural instability, the official does not return the call, leaving the safety concern unaddressed at the regulatory level. This non-response creates a critical gap in the safety response chain.
Temporal Marker: After Engineer A's call to the county building official; during the post-discovery notification phase
Activates Constraints:
- Escalation_Obligation_Constraint
- PublicSafety_Paramount_Constraint
- Duty_to_Persist_in_Warning_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Frustration and growing alarm for Engineer A, who has attempted to fulfill a notification duty but been met with silence; potential indifference or oversight on the part of the county official; lingering anxiety for Client B; continued risk for the public
- engineer_a: Placed in an ethically precarious position — having attempted notification but not yet achieved a response; must now decide whether to escalate or accept that a single call was sufficient
- county_building_official: Failure to respond may constitute a dereliction of regulatory duty; exposes the official and the county to liability
- client_b: Remains in legal and practical limbo — hazard identified, owner notified, but no regulatory action taken
- public: Continued exposure to structural risk with no regulatory intervention
- regulatory_system: Systemic responsiveness failure exposed — a single unreturned call cannot be the end of a safety notification chain
Learning Moment: A single notification attempt to a regulatory authority is insufficient when a serious safety hazard exists and no response is received. The engineer's duty to protect public safety requires persistence and escalation through alternative channels until the hazard is addressed.
Ethical Implications: Reveals the ethical inadequacy of treating notification as a checkbox exercise; highlights the tension between professional comfort (having 'done something') and genuine responsibility (ensuring the hazard is actually addressed); demonstrates that public safety obligations are outcome-oriented, not process-oriented
- How long should Engineer A wait for a return call before escalating, given that the risk is 'eventual but not imminent'?
- What alternative channels should Engineer A pursue, and in what order of priority?
- Does the fact that the collapse is not imminent reduce Engineer A's obligation to escalate urgently, or does the severity of the eventual consequence demand immediate escalation regardless?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Event_County_Official_Call_Unanswered",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"How long should Engineer A wait for a return call before escalating, given that the risk is \u0027eventual but not imminent\u0027?",
"What alternative channels should Engineer A pursue, and in what order of priority?",
"Does the fact that the collapse is not imminent reduce Engineer A\u0027s obligation to escalate urgently, or does the severity of the eventual consequence demand immediate escalation regardless?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Frustration and growing alarm for Engineer A, who has attempted to fulfill a notification duty but been met with silence; potential indifference or oversight on the part of the county official; lingering anxiety for Client B; continued risk for the public",
"proeth-scenario:ethicalImplications": "Reveals the ethical inadequacy of treating notification as a checkbox exercise; highlights the tension between professional comfort (having \u0027done something\u0027) and genuine responsibility (ensuring the hazard is actually addressed); demonstrates that public safety obligations are outcome-oriented, not process-oriented",
"proeth-scenario:learningMoment": "A single notification attempt to a regulatory authority is insufficient when a serious safety hazard exists and no response is received. The engineer\u0027s duty to protect public safety requires persistence and escalation through alternative channels until the hazard is addressed.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"client_b": "Remains in legal and practical limbo \u2014 hazard identified, owner notified, but no regulatory action taken",
"county_building_official": "Failure to respond may constitute a dereliction of regulatory duty; exposes the official and the county to liability",
"engineer_a": "Placed in an ethically precarious position \u2014 having attempted notification but not yet achieved a response; must now decide whether to escalate or accept that a single call was sufficient",
"public": "Continued exposure to structural risk with no regulatory intervention",
"regulatory_system": "Systemic responsiveness failure exposed \u2014 a single unreturned call cannot be the end of a safety notification chain"
},
"proeth:activatesConstraint": [
"Escalation_Obligation_Constraint",
"PublicSafety_Paramount_Constraint",
"Duty_to_Persist_in_Warning_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/132#Action_Call_to_County_Building_Official",
"proeth:causesStateChange": "The primary regulatory notification channel has failed; Engineer A\u0027s ethical obligation to escalate is now fully and urgently activated; the building remains at risk with no regulatory response",
"proeth:createsObligation": [
"Escalate_to_County_Official_Supervisor",
"Contact_Fire_Marshal_or_Other_Agency",
"Document_Failed_Notification_Attempt",
"Follow_Up_in_Writing_to_County_Official",
"Pursue_All_Available_Channels_Until_Response_Obtained"
],
"proeth:description": "After Engineer A calls the county building official to report the structural instability, the official does not return the call, leaving the safety concern unaddressed at the regulatory level. This non-response creates a critical gap in the safety response chain.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "After Engineer A\u0027s call to the county building official; during the post-discovery notification phase",
"proeth:urgencyLevel": "critical",
"rdfs:label": "County Official Call Unanswered"
}
Description: Despite Engineer A's verbal notification to Client B, call to the county official, and bracing recommendation, the structural collapse risk remains unaddressed — the county has not responded, bracing has not been confirmed as implemented, and no formal written documentation has been issued. The hazard persists in an unresolved state.
Temporal Marker: Following all of Engineer A's initial actions; the state of affairs at the conclusion of the described sequence
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Escalation_Obligation_Constraint
- Formal_Documentation_Constraint
- Duty_to_Persist_in_Warning_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Moral unease and potential denial for Engineer A, who may feel obligations were discharged; continued anxiety for Client B; invisible ongoing risk for the public who are unaware; frustration for ethics reviewers and the BER who conclude Engineer A's actions were insufficient
- engineer_a: Ethical failure identified by BER; professional reputation and potential liability at risk if collapse occurs; demonstrates gap between feeling one has acted and actually fulfilling professional obligations
- client_b: Remains exposed to liability and safety risk; verbal notification without written documentation leaves Client B without a clear record of the hazard or Engineer A's recommendations
- public: Ongoing exposure to structural collapse risk without knowledge or protection
- county_building_official: Regulatory failure persists; no accountability triggered by Engineer A's insufficient escalation
- engineering_profession: Case becomes a teaching example of ethical insufficiency — illustrating that good intentions and partial action do not satisfy professional obligations
Learning Moment: Fulfilling ethical obligations in public safety contexts requires not just initiating action but ensuring that action produces results. Verbal notifications, single phone calls, and informal recommendations are insufficient when a structural hazard remains unaddressed. Engineers must escalate persistently and document formally.
Ethical Implications: Reveals the ethical insufficiency of process compliance versus outcome responsibility; highlights the tension between client loyalty and public safety duties; demonstrates that professional ethics require persistence, not just initiation; raises questions about what 'doing enough' means in safety-critical contexts
- At what point does an engineer's obligation to protect public safety override their obligation to respect client confidentiality or avoid confrontation with regulatory officials?
- What specific additional steps should Engineer A have taken, and what ethical principles justify those steps?
- How does the 'eventual but not imminent' characterization of the collapse risk affect the ethical calculus — does it reduce urgency, or is the severity of the eventual outcome sufficient to demand immediate escalation?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#Event_Collapse_Risk_Remains_Unmitigated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"At what point does an engineer\u0027s obligation to protect public safety override their obligation to respect client confidentiality or avoid confrontation with regulatory officials?",
"What specific additional steps should Engineer A have taken, and what ethical principles justify those steps?",
"How does the \u0027eventual but not imminent\u0027 characterization of the collapse risk affect the ethical calculus \u2014 does it reduce urgency, or is the severity of the eventual outcome sufficient to demand immediate escalation?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Moral unease and potential denial for Engineer A, who may feel obligations were discharged; continued anxiety for Client B; invisible ongoing risk for the public who are unaware; frustration for ethics reviewers and the BER who conclude Engineer A\u0027s actions were insufficient",
"proeth-scenario:ethicalImplications": "Reveals the ethical insufficiency of process compliance versus outcome responsibility; highlights the tension between client loyalty and public safety duties; demonstrates that professional ethics require persistence, not just initiation; raises questions about what \u0027doing enough\u0027 means in safety-critical contexts",
"proeth-scenario:learningMoment": "Fulfilling ethical obligations in public safety contexts requires not just initiating action but ensuring that action produces results. Verbal notifications, single phone calls, and informal recommendations are insufficient when a structural hazard remains unaddressed. Engineers must escalate persistently and document formally.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"client_b": "Remains exposed to liability and safety risk; verbal notification without written documentation leaves Client B without a clear record of the hazard or Engineer A\u0027s recommendations",
"county_building_official": "Regulatory failure persists; no accountability triggered by Engineer A\u0027s insufficient escalation",
"engineer_a": "Ethical failure identified by BER; professional reputation and potential liability at risk if collapse occurs; demonstrates gap between feeling one has acted and actually fulfilling professional obligations",
"engineering_profession": "Case becomes a teaching example of ethical insufficiency \u2014 illustrating that good intentions and partial action do not satisfy professional obligations",
"public": "Ongoing exposure to structural collapse risk without knowledge or protection"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Escalation_Obligation_Constraint",
"Formal_Documentation_Constraint",
"Duty_to_Persist_in_Warning_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/132#Action_Decision_Not_to_Further_Escalate",
"proeth:causesStateChange": "The building remains structurally unsafe; all initial notification actions have been taken but none have produced a confirmed safety response; Engineer A\u0027s ethical obligations remain active and unfulfilled; the situation is ethically unresolved",
"proeth:createsObligation": [
"Issue_Formal_Written_Report_of_Findings",
"Escalate_to_County_Official_Supervisor",
"Contact_Fire_Marshal_or_Alternative_Authority",
"Confirm_Bracing_Implementation",
"Continue_Escalation_Until_Hazard_Addressed"
],
"proeth:description": "Despite Engineer A\u0027s verbal notification to Client B, call to the county official, and bracing recommendation, the structural collapse risk remains unaddressed \u2014 the county has not responded, bracing has not been confirmed as implemented, and no formal written documentation has been issued. The hazard persists in an unresolved state.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Following all of Engineer A\u0027s initial actions; the state of affairs at the conclusion of the described sequence",
"proeth:urgencyLevel": "critical",
"rdfs:label": "Collapse Risk Remains Unmitigated"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: After the county building official failed to return Engineer A's phone call, Engineer A made no further attempts to escalate the matter, directly contributing to the collapse risk remaining unmitigated
Necessary Factors (NESS):
- Engineer A's awareness that the phone call went unanswered
- Engineer A's knowledge that the structural hazard remained active and unresolved
- The existence of alternative escalation pathways (other officials, written notices, public warning) that Engineer A chose not to pursue
Sufficient Factors:
- The combination of an unanswered official call + Engineer A's decision not to escalate further + Client B's inaction on bracing was sufficient to leave the collapse risk unmitigated
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
County Official Call Unanswered
The county building official fails to return Engineer A's call, leaving the hazard without official acknowledgment -
Decision Not to Further Escalate
Engineer A makes no additional attempts to contact authorities, issue written warnings, or pursue alternative reporting channels -
Bracing Recommendation Unimplemented
Building owners do not act on Engineer A's bracing recommendation without enforcement pressure -
Certificate of Occupancy Invalidated but Unenforced
The effectively void certificate of occupancy is not formally revoked due to absence of official follow-through -
Collapse Risk Remains Unmitigated
The structural hazard persists without remediation, enforcement, or public warning
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#CausalChain_f226c8d5",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "After the county building official failed to return Engineer A\u0027s phone call, Engineer A made no further attempts to escalate the matter, directly contributing to the collapse risk remaining unmitigated",
"proeth:causalSequence": [
{
"proeth:description": "The county building official fails to return Engineer A\u0027s call, leaving the hazard without official acknowledgment",
"proeth:element": "County Official Call Unanswered",
"proeth:step": 1
},
{
"proeth:description": "Engineer A makes no additional attempts to contact authorities, issue written warnings, or pursue alternative reporting channels",
"proeth:element": "Decision Not to Further Escalate",
"proeth:step": 2
},
{
"proeth:description": "Building owners do not act on Engineer A\u0027s bracing recommendation without enforcement pressure",
"proeth:element": "Bracing Recommendation Unimplemented",
"proeth:step": 3
},
{
"proeth:description": "The effectively void certificate of occupancy is not formally revoked due to absence of official follow-through",
"proeth:element": "Certificate of Occupancy Invalidated but Unenforced",
"proeth:step": 4
},
{
"proeth:description": "The structural hazard persists without remediation, enforcement, or public warning",
"proeth:element": "Collapse Risk Remains Unmitigated",
"proeth:step": 5
}
],
"proeth:cause": "Decision Not to Further Escalate",
"proeth:counterfactual": "Had Engineer A escalated to alternative authorities or issued formal written warnings after the call went unanswered, there is a reasonable probability that official intervention would have been triggered, mitigating the collapse risk",
"proeth:effect": "Collapse Risk Remains Unmitigated",
"proeth:necessaryFactors": [
"Engineer A\u0027s awareness that the phone call went unanswered",
"Engineer A\u0027s knowledge that the structural hazard remained active and unresolved",
"The existence of alternative escalation pathways (other officials, written notices, public warning) that Engineer A chose not to pursue"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"The combination of an unanswered official call + Engineer A\u0027s decision not to escalate further + Client B\u0027s inaction on bracing was sufficient to leave the collapse risk unmitigated"
],
"proeth:withinAgentControl": true
}
Causal Language: A fire breaks out at a building owned by Client B, triggering the need for an engineering investigation, during which Engineer A discovers sagging roof and outward-leaning walls indicating structural instability
Necessary Factors (NESS):
- The occurrence of the fire as the precipitating event
- The fire's role in either causing or revealing pre-existing structural weaknesses
- Engineer A's presence on-site as a result of the fire investigation mandate
Sufficient Factors:
- The fire event + Engineer A's on-site presence + scope expansion together formed a sufficient set to produce the discovery of structural instability
Responsibility Attribution:
Agent: No single agent directly responsible for the fire as a precipitating event; building owners bear indirect responsibility for pre-existing structural conditions
Type: indirect
Within Agent Control:
No
Causal Sequence:
-
Fire Occurs at Building
Fire breaks out, serving as the precipitating event that brings Engineer A to the site -
Scope Expansion to Structural Assessment
Engineer A observes warning signs and voluntarily expands the investigation scope -
Structural Instability Discovered
Sagging roof and outward-leaning walls identified, indicating imminent collapse risk -
Certificate of Occupancy Invalidated
Discovery renders the existing certificate of occupancy effectively void -
Collapse Risk Remains Unmitigated
Despite discovery and notification attempts, the hazard remains unresolved due to cascading failures in escalation and enforcement
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#CausalChain_6d42dec0",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "A fire breaks out at a building owned by Client B, triggering the need for an engineering investigation, during which Engineer A discovers sagging roof and outward-leaning walls indicating structural instability",
"proeth:causalSequence": [
{
"proeth:description": "Fire breaks out, serving as the precipitating event that brings Engineer A to the site",
"proeth:element": "Fire Occurs at Building",
"proeth:step": 1
},
{
"proeth:description": "Engineer A observes warning signs and voluntarily expands the investigation scope",
"proeth:element": "Scope Expansion to Structural Assessment",
"proeth:step": 2
},
{
"proeth:description": "Sagging roof and outward-leaning walls identified, indicating imminent collapse risk",
"proeth:element": "Structural Instability Discovered",
"proeth:step": 3
},
{
"proeth:description": "Discovery renders the existing certificate of occupancy effectively void",
"proeth:element": "Certificate of Occupancy Invalidated",
"proeth:step": 4
},
{
"proeth:description": "Despite discovery and notification attempts, the hazard remains unresolved due to cascading failures in escalation and enforcement",
"proeth:element": "Collapse Risk Remains Unmitigated",
"proeth:step": 5
}
],
"proeth:cause": "Fire Occurs at Building",
"proeth:counterfactual": "Without the fire, Engineer A would not have been on-site, and the structural instability may have remained undetected until a spontaneous collapse event",
"proeth:effect": "Structural Instability Discovered",
"proeth:necessaryFactors": [
"The occurrence of the fire as the precipitating event",
"The fire\u0027s role in either causing or revealing pre-existing structural weaknesses",
"Engineer A\u0027s presence on-site as a result of the fire investigation mandate"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "No single agent directly responsible for the fire as a precipitating event; building owners bear indirect responsibility for pre-existing structural conditions",
"proeth:sufficientFactors": [
"The fire event + Engineer A\u0027s on-site presence + scope expansion together formed a sufficient set to produce the discovery of structural instability"
],
"proeth:withinAgentControl": false
}
Causal Language: After concluding the preliminary structural investigation, Engineer A immediately and verbally advised Client B of the hazard; however, despite this verbal notification, the collapse risk remained unmitigated
Necessary Factors (NESS):
- Engineer A's obligation to inform the client of discovered hazards
- Client B's receipt of the verbal warning
- Client B's subsequent decision-making authority over the building
Sufficient Factors:
- Verbal notification alone was insufficient to produce mitigation — it required Client B's cooperative action and official enforcement to form a sufficient set for risk resolution
Responsibility Attribution:
Agent: Engineer A (partial); Client B (partial)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Structural Instability Discovered
Engineer A identifies imminent collapse risk during expanded investigation -
Verbal Notification to Client B
Engineer A verbally warns Client B of the structural hazard without issuing written documentation -
Bracing Recommendation to Owners
Engineer A recommends bracing to prevent collapse, but owners do not implement the recommendation -
County Official Call Unanswered
The county building official fails to return Engineer A's call, removing a key enforcement mechanism -
Collapse Risk Remains Unmitigated
Without written directives, owner action, or official enforcement, the structural hazard persists
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#CausalChain_a3fc9fe5",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "After concluding the preliminary structural investigation, Engineer A immediately and verbally advised Client B of the hazard; however, despite this verbal notification, the collapse risk remained unmitigated",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A identifies imminent collapse risk during expanded investigation",
"proeth:element": "Structural Instability Discovered",
"proeth:step": 1
},
{
"proeth:description": "Engineer A verbally warns Client B of the structural hazard without issuing written documentation",
"proeth:element": "Verbal Notification to Client B",
"proeth:step": 2
},
{
"proeth:description": "Engineer A recommends bracing to prevent collapse, but owners do not implement the recommendation",
"proeth:element": "Bracing Recommendation to Owners",
"proeth:step": 3
},
{
"proeth:description": "The county building official fails to return Engineer A\u0027s call, removing a key enforcement mechanism",
"proeth:element": "County Official Call Unanswered",
"proeth:step": 4
},
{
"proeth:description": "Without written directives, owner action, or official enforcement, the structural hazard persists",
"proeth:element": "Collapse Risk Remains Unmitigated",
"proeth:step": 5
}
],
"proeth:cause": "Verbal Notification to Client B",
"proeth:counterfactual": "Even with verbal notification, without Client B acting on the bracing recommendation and without official enforcement, the collapse risk persisted; the notification was necessary but not sufficient to prevent the unmitigated outcome",
"proeth:effect": "Collapse Risk Remains Unmitigated",
"proeth:necessaryFactors": [
"Engineer A\u0027s obligation to inform the client of discovered hazards",
"Client B\u0027s receipt of the verbal warning",
"Client B\u0027s subsequent decision-making authority over the building"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (partial); Client B (partial)",
"proeth:sufficientFactors": [
"Verbal notification alone was insufficient to produce mitigation \u2014 it required Client B\u0027s cooperative action and official enforcement to form a sufficient set for risk resolution"
],
"proeth:withinAgentControl": true
}
Causal Language: Upon observing structural instability during a fire investigation, Engineer A voluntarily expanded the scope to include structural assessment, leading to the discovery of sagging roof and outward-leaning walls
Necessary Factors (NESS):
- Engineer A's voluntary decision to expand investigative scope
- Physical presence at the fire-damaged building
- Engineer A's professional competence to identify structural warning signs
Sufficient Factors:
- Combination of expanded scope + physical presence + engineering expertise was sufficient to produce the discovery
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Fire Occurs at Building
Fire breaks out, triggering the need for an engineering investigation under Engineer A's original mandate -
Scope Expansion to Structural Assessment
Engineer A observes warning signs and voluntarily expands scope beyond the fire investigation -
Structural Instability Discovered
Engineer A identifies sagging roof and outward-leaning walls indicating imminent collapse risk -
Certificate of Occupancy Invalidated
Discovery renders the previously issued certificate of occupancy effectively void -
Collapse Risk Remains Unmitigated
Despite discovery, subsequent failures in escalation leave the hazard unresolved
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#CausalChain_eda057a4",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Upon observing structural instability during a fire investigation, Engineer A voluntarily expanded the scope to include structural assessment, leading to the discovery of sagging roof and outward-leaning walls",
"proeth:causalSequence": [
{
"proeth:description": "Fire breaks out, triggering the need for an engineering investigation under Engineer A\u0027s original mandate",
"proeth:element": "Fire Occurs at Building",
"proeth:step": 1
},
{
"proeth:description": "Engineer A observes warning signs and voluntarily expands scope beyond the fire investigation",
"proeth:element": "Scope Expansion to Structural Assessment",
"proeth:step": 2
},
{
"proeth:description": "Engineer A identifies sagging roof and outward-leaning walls indicating imminent collapse risk",
"proeth:element": "Structural Instability Discovered",
"proeth:step": 3
},
{
"proeth:description": "Discovery renders the previously issued certificate of occupancy effectively void",
"proeth:element": "Certificate of Occupancy Invalidated",
"proeth:step": 4
},
{
"proeth:description": "Despite discovery, subsequent failures in escalation leave the hazard unresolved",
"proeth:element": "Collapse Risk Remains Unmitigated",
"proeth:step": 5
}
],
"proeth:cause": "Scope Expansion to Structural Assessment",
"proeth:counterfactual": "Without the scope expansion, structural instability would likely have gone undetected during the fire investigation, as the original mandate did not include structural assessment",
"proeth:effect": "Structural Instability Discovered",
"proeth:necessaryFactors": [
"Engineer A\u0027s voluntary decision to expand investigative scope",
"Physical presence at the fire-damaged building",
"Engineer A\u0027s professional competence to identify structural warning signs"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Combination of expanded scope + physical presence + engineering expertise was sufficient to produce the discovery"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A contacted the county building official by phone to report the structural hazard, but did not follow up in writing or escalate further after the official failed to return the call
Necessary Factors (NESS):
- Engineer A's professional duty to notify public authorities of imminent public safety hazards
- The phone call as the chosen method of notification
- The county official's availability and responsiveness as a prerequisite for effective communication
Sufficient Factors:
- A phone call alone, without written follow-up or escalation to alternative authorities, was insufficient to constitute a complete discharge of Engineer A's public safety duty
Responsibility Attribution:
Agent: Engineer A (primary); County Building Official (secondary)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Structural Instability Discovered
Engineer A identifies a hazard that triggers a professional and ethical duty to notify public authorities -
Call to County Building Official
Engineer A places a phone call to the county building official as the primary notification method -
County Official Call Unanswered
The county building official does not return the call, breaking the intended communication chain -
Decision Not to Further Escalate
Engineer A takes no additional steps to notify authorities after the call goes unanswered -
Collapse Risk Remains Unmitigated
Without official enforcement triggered, the structural hazard remains unaddressed
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/132#",
"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/132#CausalChain_e8c4eb7d",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A contacted the county building official by phone to report the structural hazard, but did not follow up in writing or escalate further after the official failed to return the call",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A identifies a hazard that triggers a professional and ethical duty to notify public authorities",
"proeth:element": "Structural Instability Discovered",
"proeth:step": 1
},
{
"proeth:description": "Engineer A places a phone call to the county building official as the primary notification method",
"proeth:element": "Call to County Building Official",
"proeth:step": 2
},
{
"proeth:description": "The county building official does not return the call, breaking the intended communication chain",
"proeth:element": "County Official Call Unanswered",
"proeth:step": 3
},
{
"proeth:description": "Engineer A takes no additional steps to notify authorities after the call goes unanswered",
"proeth:element": "Decision Not to Further Escalate",
"proeth:step": 4
},
{
"proeth:description": "Without official enforcement triggered, the structural hazard remains unaddressed",
"proeth:element": "Collapse Risk Remains Unmitigated",
"proeth:step": 5
}
],
"proeth:cause": "Call to County Building Official",
"proeth:counterfactual": "Had Engineer A followed the phone call with written notice or escalated to alternative authorities (e.g., fire marshal, building department supervisor), the official non-response would not have been a terminal barrier to mitigation",
"proeth:effect": "County Official Call Unanswered",
"proeth:necessaryFactors": [
"Engineer A\u0027s professional duty to notify public authorities of imminent public safety hazards",
"The phone call as the chosen method of notification",
"The county official\u0027s availability and responsiveness as a prerequisite for effective communication"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A (primary); County Building Official (secondary)",
"proeth:sufficientFactors": [
"A phone call alone, without written follow-up or escalation to alternative authorities, was insufficient to constitute a complete discharge of Engineer A\u0027s public safety duty"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (27)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| County Commission decision |
before
Entity1 is before Entity2 |
preliminary site investigation studies |
time:before
http://www.w3.org/2006/time#before |
The County Commission decided not to reopen the bridge. Preliminary site investigation studies were ... [more] |
| town approval of changes |
before
Entity1 is before Entity2 |
barn extension construction completion |
time:before
http://www.w3.org/2006/time#before |
The changes were approved by the town, the extension was built, and a certificate of occupancy was i... [more] |
| issuance of certificate of occupancy |
before
Entity1 is before Entity2 |
Engineer A's fire investigation |
time:before
http://www.w3.org/2006/time#before |
Engineer A also learns that following construction modifications, the building was issued a certific... [more] |
| verbal notification to Client B |
meets
Entity1 ends exactly when Entity2 begins |
phone call to county building official |
time:intervalMeets
http://www.w3.org/2006/time#intervalMeets |
Engineer A immediately advises Client B and calls the county building official. |
| phone call to county building official |
before
Entity1 is before Entity2 |
non-return of county building official's call |
time:before
http://www.w3.org/2006/time#before |
Engineer A... calls the county building official. The county building official did not return Engine... [more] |
| Engineer A's notification of Client B and county official |
before
Entity1 is before Entity2 |
recommendation to brace the building |
time:before
http://www.w3.org/2006/time#before |
Engineer A immediately advises Client B and calls the county building official... Engineer A also re... [more] |
| bridge inspector telephone call |
before
Entity1 is before Entity2 |
erection of barricades and signs |
time:before
http://www.w3.org/2006/time#before |
In June 2000, Engineer A received a telephone call from the bridge inspector stating that the bridge... [more] |
| barricades found dumped (Monday) |
before
Entity1 is before Entity2 |
installation of more permanent barricades |
time:before
http://www.w3.org/2006/time#before |
On the following Monday, the barricades were found dumped in the river... More permanent barricades ... [more] |
| installation of more permanent barricades |
before
Entity1 is before Entity2 |
publication of press photos |
time:before
http://www.w3.org/2006/time#before |
More permanent barricades and signs were installed. The press published photos of some of the piles ... [more] |
| press publication of photos |
before
Entity1 is before Entity2 |
receipt of detailed inspection report |
time:before
http://www.w3.org/2006/time#before |
The press published photos... Within a few days, a detailed inspection report prepared by a consulti... [more] |
| receipt of detailed inspection report |
before
Entity1 is before Entity2 |
authorization for bridge replacement |
time:before
http://www.w3.org/2006/time#before |
Within a few days, a detailed inspection report... Within three weeks, Engineer A had obtained autho... [more] |
| authorization for bridge replacement |
before
Entity1 is before Entity2 |
state and federal department reviews |
time:before
http://www.w3.org/2006/time#before |
Within three weeks, Engineer A had obtained authorization for the bridge to be replaced. Several sta... [more] |
| state and federal department reviews |
before
Entity1 is before Entity2 |
rally and petition presentation |
time:before
http://www.w3.org/2006/time#before |
Several state and federal transportation departments needed to complete their reviews... A rally was... [more] |
| rally and petition presentation |
before
Entity1 is before Entity2 |
County Commission decision not to reopen bridge |
time:before
http://www.w3.org/2006/time#before |
A rally was held, and a petition... was presented to the County Commission. The County Commission de... [more] |
| preliminary site investigation studies |
overlaps
Entity1 starts before Entity2 and ends during Entity2 |
environmental, geological, right-of-way studies |
time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps |
Preliminary site investigation studies were begun. Environmental, geological, right-of-way, and othe... [more] |
| non-engineer public works director decision on crutch piles |
before
Entity1 is before Entity2 |
Engineer A's observation of traffic and bridge movement |
time:before
http://www.w3.org/2006/time#before |
A nonengineer public works director decided to have a retired bridge inspector... examine the bridge... [more] |
| barn construction by Engineer A |
before
Entity1 is before Entity2 |
sale of property to Jones |
time:before
http://www.w3.org/2006/time#before |
Engineer A had designed and built a barn with horse stalls on his property. Four years later, Engine... [more] |
| Engineer A's verbal contact with town supervisor (BER 07-10) |
before
Entity1 is before Entity2 |
town supervisor's inaction |
time:before
http://www.w3.org/2006/time#before |
Engineer A verbally contacted the town supervisor, who agreed to review the matter, but no action wa... [more] |
| recent structural changes to building |
before
Entity1 is before Entity2 |
issuance of certificate of occupancy |
time:before
http://www.w3.org/2006/time#before |
Engineer A also learns that following construction modifications, the building was issued a certific... [more] |
| fire at building |
before
Entity1 is before Entity2 |
Engineer A's investigation |
time:before
http://www.w3.org/2006/time#before |
Engineer A is hired by Client B to conduct a building investigation to determine the origin and caus... [more] |
| Engineer A's preliminary structural investigation |
before
Entity1 is before Entity2 |
verbal notification to Client B |
time:before
http://www.w3.org/2006/time#before |
Engineer A performs a preliminary investigation of the building and after speaking with Client B, co... [more] |
| erection of barricades and signs (Friday) |
before
Entity1 is before Entity2 |
barricades found dumped in river (Monday) |
time:before
http://www.w3.org/2006/time#before |
Engineer A had barricades and signs erected within the hour on a Friday afternoon... On the followin... [more] |
| sale of property to Jones |
before
Entity1 is before Entity2 |
Jones's proposed barn extension |
time:before
http://www.w3.org/2006/time#before |
Four years later, Engineer A sold the property, including the barn, to Jones. Later, Jones proposed ... [more] |
| Jones's barn extension construction |
before
Entity1 is before Entity2 |
issuance of certificate of occupancy for barn extension |
time:before
http://www.w3.org/2006/time#before |
The changes were approved by the town, the extension was built, and a certificate of occupancy was i... [more] |
| issuance of certificate of occupancy for barn extension |
before
Entity1 is before Entity2 |
Engineer A learning of the extension |
time:before
http://www.w3.org/2006/time#before |
The changes were approved by the town, the extension was built, and a certificate of occupancy was i... [more] |
| Engineer A learning of barn extension |
before
Entity1 is before Entity2 |
Engineer A's verbal contact with town supervisor |
time:before
http://www.w3.org/2006/time#before |
Engineer A learned of the extension and was concerned... Engineer A verbally contacted the town supe... [more] |
| removal of columns and footings (Jones's modification) |
during
Entity1 occurs entirely within the duration of Entity2 |
barn extension construction |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
Jones proposed to extend the barn and, as part of the extension, removed portions of the columns and... [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.