{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_BER_Case_76-4_Engineer_Files_Written_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Comply with the client\u0027s instruction and refrain from filing the written report, deferring to the client\u0027s authority over the engagement",
    "Withdraw from the engagement entirely rather than either filing the report or suppressing it, avoiding the conflict through exit",
    "File the report with the client privately rather than publicly, creating a record without directly contradicting the client at the hearing"
  ],
  "proeth-scenario:characterMotivation": "The engineer in BER Case 76-4 was motivated by the recognition that a verbal warning, once denied or misrepresented by the client, becomes professionally and legally worthless. When the client actively misrepresented data at a public hearing, the engineer understood that silence would make them complicit in a deception that endangered public safety.",
  "proeth-scenario:consequencesIfAlternative": [
    "Complying with the client\u0027s instruction would make the engineer complicit in the misrepresentation, expose them to professional discipline, and leave the public safety risk undocumented, a clear violation of the NSPE Code that this case was decided to prohibit.",
    "Withdrawal would protect the engineer from complicity but would abandon the public safety obligation; the hazard would remain unreported and the client\u0027s misrepresentation would stand unchallenged, producing a worse outcome for the public than filing the report.",
    "Private filing with the client would create a record but would not correct the public misrepresentation already made at the hearing; it would be a partial measure that fails to address the active deception and may still leave the public safety risk unaddressed."
  ],
  "proeth-scenario:decisionSignificance": "Establishes the foundational precedent that client authority over an engineer\u0027s professional conduct has limits defined by public safety obligations. Students learn that engineers are not mere agents of their clients when safety is at stake, and that written documentation is a professional duty, not a discretionary courtesy.",
  "proeth-scenario:ethicalTension": "Fidelity to the client\u0027s explicit instruction and the value of maintaining professional relationships vs. the engineer\u0027s independent duty to the public and the integrity of the safety record. The client\u0027s instruction to suppress the report directly conflicted with the engineer\u0027s obligation not to be complicit in the concealment of known hazards.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Public safety at the hearing; the integrity of the engineering profession\u0027s independence; the engineer\u0027s license and professional standing; the client\u0027s legal exposure from the misrepresentation; the precedential value for future cases involving client suppression of safety findings.",
  "proeth:description": "In the 1976 precedent case, after a client instructed an engineer not to file a written report following a verbal safety warning, the engineer made the professional decision to file the written report anyway when the client subsequently misrepresented data at a public hearing. This established that engineers cannot be silenced by client instruction when public safety is at stake.",
  "proeth:eventRoleContext": "unnamed; subject of BER Case 76-4",
  "proeth:foreseenUnintendedEffects": [
    "Breach of client instruction and potential termination of engagement",
    "Possible damage to professional relationship with client",
    "Creation of public record contradicting client\u0027s representations"
  ],
  "proeth:fulfillsObligation": [
    "Public safety and welfare primacy over client instruction",
    "Honesty and integrity in professional communications",
    "Duty to correct false or misleading public representations affecting safety"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety supersedes client loyalty",
    "Engineers must not be complicit in misrepresentation affecting public welfare",
    "Written documentation as professional standard for safety communications"
  ],
  "proeth:hasAgent": "Engineer",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client loyalty and instruction compliance vs. public safety and professional integrity",
    "proeth:resolutionReasoning": "Engineer determined that client\u0027s active misrepresentation elevated the public safety obligation beyond the point where client instruction could ethically be followed; written report was the necessary corrective action"
  },
  "proeth:hasMentalState": "deliberate; conscience-driven decision to override client instruction",
  "proeth:intendedOutcome": "Correct the public record after client misrepresentation; fulfill professional duty to public safety over client loyalty",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Professional judgment to recognize when client instruction conflicts with public safety duty",
    "Ability to prepare and file formal written safety report",
    "Courage to act contrary to client instruction"
  ],
  "proeth:temporalMarker": "1976; referenced as precedent in discussion section",
  "proeth:temporalSequence": 1,
  "proeth:violatesObligation": [
    "Client instruction to refrain from filing written report",
    "Duty of faithful agency (overridden by superior public safety obligation)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "BER Case 76-4 Engineer Files Written Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_BER_Case_90-5_Engineer_Discloses_Structural_Defect",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Maintain confidentiality as instructed by the attorney and include no disclosure of the structural defects in any report or communication",
    "Disclose the defects to the client organization\u0027s leadership rather than to tenants or regulators, treating it as an internal safety matter",
    "Withdraw from the engagement and decline to produce any report, neither disclosing nor concealing the defects"
  ],
  "proeth-scenario:characterMotivation": "The engineer in BER Case 90-5 was motivated by the recognition that confidentiality, while a genuine professional value, cannot function as a shield for concealing active threats to tenant safety. The attorney\u0027s instruction, though professionally issued, demanded that the engineer prioritize the client\u0027s legal strategy over the physical safety of identifiable people in the defective structure.",
  "proeth-scenario:consequencesIfAlternative": [
    "Maintaining confidentiality as instructed would expose tenants to unmitigated structural risk, make the engineer complicit in concealment, and create significant professional discipline and legal liability exposure if a failure occurred and the engineer\u0027s prior knowledge was discovered.",
    "Disclosing internally to organizational leadership might prompt remediation but would not guarantee it, and would leave tenants without direct notification of a risk to their safety; it is a partial measure that may be insufficient depending on the organization\u0027s responsiveness.",
    "Withdrawal without disclosure would protect the engineer from producing a misleading report but would leave the hazard unaddressed and unreported; the engineer\u0027s knowledge of the defect would persist as an unresolved ethical burden, and withdrawal alone does not fulfill the duty to warn."
  ],
  "proeth-scenario:decisionSignificance": "Establishes that confidentiality is not an absolute value in engineering ethics and that instructions from non-engineer professionals (such as attorneys) do not override an engineer\u0027s safety obligations. Students learn to recognize when confidentiality is being weaponized against the public interest and to understand the hierarchy of ethical obligations in the NSPE Code.",
  "proeth-scenario:ethicalTension": "Confidentiality obligations to the client and deference to legal counsel\u0027s authority within the engagement vs. the engineer\u0027s independent duty to protect public safety from known structural hazards. This case sharpens the tension by introducing a third-party professional, an attorney, whose instruction the engineer must evaluate against their own ethical code.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Tenant life safety from structural failure; the engineer\u0027s professional and legal liability for knowing concealment of a hazard; the client\u0027s exposure to greater liability if concealment is later discovered; the integrity of the professional confidentiality norm if it is seen to shield safety violations.",
  "proeth:description": "In the 1990 precedent case, despite attorney instruction to keep discovered structural defects confidential due to tenant safety risk, the engineer made the professional decision to disclose the defects. This established that confidentiality obligations to clients cannot override an engineer\u0027s duty to protect public safety from known hazards.",
  "proeth:eventRoleContext": "unnamed; subject of BER Case 90-5",
  "proeth:foreseenUnintendedEffects": [
    "Breach of attorney-client confidentiality instruction",
    "Potential legal consequences for engineer",
    "Exposure of client to liability",
    "Possible termination of professional engagement"
  ],
  "proeth:fulfillsObligation": [
    "Public health, safety, and welfare primacy",
    "Duty to protect third parties (tenants) from known hazards",
    "Professional integrity and honest disclosure"
  ],
  "proeth:guidedByPrinciple": [
    "Engineers shall hold public safety paramount above all other considerations",
    "Confidentiality obligations do not extend to concealing imminent safety hazards",
    "Third-party safety interests can override client confidentiality instructions"
  ],
  "proeth:hasAgent": "Engineer",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client confidentiality obligation vs. tenant safety and public welfare",
    "proeth:resolutionReasoning": "BER determined that the engineer\u0027s paramount duty to public safety cannot be subordinated to client confidentiality instructions when tenants face imminent structural risk; disclosure was ethically required"
  },
  "proeth:hasMentalState": "deliberate; ethically compelled decision against client/attorney instruction",
  "proeth:intendedOutcome": "Protect tenant safety by ensuring structural defects are disclosed and addressed; fulfill paramount public safety obligation",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Structural engineering assessment of defect severity",
    "Professional judgment to recognize when confidentiality must yield to safety",
    "Ability to make and document disclosure decision"
  ],
  "proeth:temporalMarker": "1990; referenced as precedent in discussion section",
  "proeth:temporalSequence": 2,
  "proeth:violatesObligation": [
    "Attorney instruction to maintain confidentiality",
    "Duty of faithful agency to client (overridden by superior safety obligation)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "BER Case 90-5 Engineer Discloses Structural Defects"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_BER_Case_17-3_Forensic_Engineer_Expands_Report_Sco",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Omit the undersized beam finding from the report entirely, treating it as outside scope and directing the client to commission a separate structural review",
    "Verbally inform the client of the undersized beam finding without including it in the formal written report, preserving scope discipline while conveying the information",
    "Halt the forensic engagement and refuse to complete the report until the client formally expands the scope to include the structural finding"
  ],
  "proeth-scenario:characterMotivation": "The forensic engineer in BER Case 17-3 was motivated by the understanding that an engineer\u0027s professional signature on a report carries an implicit representation of completeness with respect to known safety issues. Omitting a discovered structural deficiency because it fell outside the original scope would have made the report misleading by omission and would have left a known hazard undocumented.",
  "proeth-scenario:consequencesIfAlternative": [
    "Omitting the finding entirely would produce a report that is technically within scope but professionally misleading; if the undersized beam later caused a failure, the engineer\u0027s documented awareness would create severe liability exposure and the omission would constitute a violation of the forthright obligation under the NSPE Code.",
    "Verbal notification without written inclusion would partially address the duty to warn but would fail to create a professional record, could be denied by the client, and would leave the formal report incomplete with respect to a known safety issue, BER precedent consistently holds that verbal warnings alone are insufficient.",
    "Halting the engagement to force scope expansion would be an overreach that disrupts the client relationship and delays the completion of the original forensic work; the more proportionate and professionally correct response is to include the finding in the report with appropriate notation of its incidental discovery, as the engineer actually did."
  ],
  "proeth-scenario:decisionSignificance": "Establishes the most directly applicable precedent for Engineer A\u0027s situation: incidental discovery of a safety hazard during a legitimately scoped engagement creates an affirmative reporting obligation that cannot be defeated by scope limitations. Students learn that engineering ethics is not a contractual opt-in system, professional duties attach to knowledge, not to scope.",
  "proeth-scenario:ethicalTension": "Strict adherence to the defined engagement scope, which creates predictable, bounded professional relationships and protects against scope creep, vs. the affirmative duty to report safety-relevant findings discovered in the course of legitimate professional work, regardless of whether those findings were anticipated in the original engagement agreement.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Structural safety of the building under forensic review; the integrity and completeness of the engineering report; the forensic engineer\u0027s professional credibility and liability exposure; the precedential clarification of how scope limitations interact with safety reporting duties across all engineering practice areas.",
  "proeth:description": "In the 2017 precedent case, a forensic engineer independently decided to include findings about an undersized beam in the formal report even though this discovery fell outside the original engagement scope. This established that engineers have an affirmative duty to report safety-relevant findings discovered incidentally, regardless of scope limitations.",
  "proeth:eventRoleContext": "unnamed; subject of BER Case 17-3",
  "proeth:foreseenUnintendedEffects": [
    "Report scope exceeds contracted deliverable",
    "Client may object to inclusion of out-of-scope findings",
    "May create additional liability or remediation obligations for client",
    "Sets precedent for engineer\u0027s affirmative duty to report incidental discoveries"
  ],
  "proeth:fulfillsObligation": [
    "Public safety duty to report known structural hazards",
    "Professional integrity in comprehensive and honest reporting",
    "Affirmative duty to disclose safety-relevant findings regardless of scope"
  ],
  "proeth:guidedByPrinciple": [
    "Engineers shall hold public safety paramount",
    "Scope limitations do not extinguish duty to report discovered safety hazards",
    "Comprehensive and honest professional reporting"
  ],
  "proeth:hasAgent": "Forensic Engineer",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Contracted scope fidelity vs. affirmative duty to report incidental safety findings",
    "proeth:resolutionReasoning": "BER affirmed that the engineer\u0027s independent decision to include out-of-scope safety findings was ethically correct; scope limitations are subordinate to the duty to report discovered hazards that affect public safety"
  },
  "proeth:hasMentalState": "deliberate; proactive professional judgment to expand report beyond contracted scope",
  "proeth:intendedOutcome": "Ensure safety-relevant findings are formally documented and communicated regardless of original engagement boundaries; fulfill public safety obligation",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Structural engineering competence to assess beam adequacy",
    "Professional judgment to recognize safety significance of incidental finding",
    "Ability to document and communicate out-of-scope findings clearly and appropriately"
  ],
  "proeth:temporalMarker": "2017; referenced as precedent in discussion section",
  "proeth:temporalSequence": 3,
  "proeth:violatesObligation": [
    "Strict adherence to contracted engagement scope (minor violation, overridden by safety duty)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "BER Case 17-3 Forensic Engineer Expands Report Scope"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_Retroactive_Ordinance_Enactment",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Apply the sprinkler ordinance prospectively only, exempting projects already under construction",
    "Provide a phased compliance timeline with technical guidance and financial assistance for retrofits",
    "Require third-party engineering review of all retrofit installations before occupancy permit issuance"
  ],
  "proeth-scenario:characterMotivation": "The city sought to reduce fire risk in densely built residential areas by leveraging an existing regulatory mechanism, applying the new sprinkler requirement broadly to maximize public safety coverage without waiting for new construction cycles. The retroactive scope likely reflected urgency and political pressure to act decisively after a recognized hazard.",
  "proeth-scenario:consequencesIfAlternative": [
    "Prospective-only application would leave a cohort of nearly-complete residences unprotected, potentially defeating the public safety goal and creating an inequitable gap between new and slightly older construction.",
    "A phased timeline with support resources would reduce the economic shock and incentivize quality compliance, likely preventing the hasty routing decision, but would delay safety improvements and require administrative infrastructure.",
    "Mandatory engineering review would have caught the hazardous garage routing before occupancy, directly preventing the scenario\u0027s central hazard, but would add cost and delay and require regulatory capacity the city may not possess."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how well-intentioned regulatory action can create downstream compliance pressures that incentivize cost-cutting shortcuts, teaching students that policy design has ethical dimensions and that safety mandates must anticipate implementation risks, not just mandate outcomes.",
  "proeth-scenario:ethicalTension": "Public safety and collective welfare vs. individual property rights, economic fairness to builders mid-project, and the principle against retroactive regulatory burdens. The city balanced precautionary duty against the inequity of changing rules after construction commitments were made.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Fire safety across an entire residential neighborhood; economic hardship on builders; risk that rushed or under-resourced compliance produces hazardous workarounds that nullify the safety benefit the ordinance was designed to achieve.",
  "proeth:description": "The city deliberately extended the sprinkler requirement to all residential projects not yet receiving occupancy permits, imposing retrofit obligations on builders mid-construction. This legislative choice created the compliance burden that led to the builder\u0027s hazardous pipe routing.",
  "proeth:eventRoleContext": "Municipal Authority",
  "proeth:foreseenUnintendedEffects": [
    "Builders forced into rushed or cost-constrained retrofit designs",
    "Increased likelihood of suboptimal pipe routing in existing structures not designed for sprinkler integration",
    "Potential creation of new hazards (e.g., freeze exposure) in solving the fire safety problem"
  ],
  "proeth:fulfillsObligation": [
    "Public health, safety, and welfare protection through fire suppression mandate",
    "Legislative duty to respond to identified community fire risk in closely-spaced residences"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety primacy",
    "Fire risk mitigation in dense residential settings",
    "Precautionary regulation"
  ],
  "proeth:hasAgent": "City Legislative Body",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Fire safety protection vs. fairness and quality of retrofit implementation",
    "proeth:resolutionReasoning": "City resolved in favor of maximum safety coverage, accepting that retrofit compliance might be imperfect or introduce secondary risks not contemplated by the ordinance"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maximize fire safety coverage by closing the loophole of near-complete construction projects escaping sprinkler requirements",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Legislative drafting",
    "Fire code analysis",
    "Assessment of construction phase applicability"
  ],
  "proeth:temporalMarker": "Prior to Engineer A\u0027s involvement; during active construction phase of affected projects",
  "proeth:temporalSequence": 5,
  "proeth:violatesObligation": [
    "Procedural fairness to builders who had planned projects under prior regulatory framework",
    "Duty to anticipate and mitigate unintended consequences of retroactive application"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Retroactive Ordinance Enactment"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_Hazardous_Sprinkler_Pipe_Routing",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Route piping through interior conditioned spaces, accepting higher labor and material costs",
    "Install freeze-protection measures such as heat tape, insulation, or a dry-pipe system configuration in the garage segment",
    "Consult a licensed engineer or the authority having jurisdiction to identify a code-compliant and freeze-safe routing solution"
  ],
  "proeth-scenario:characterMotivation": "The builder was driven by cost minimization and schedule pressure under an unexpected retrofit mandate. Routing through the garage represented the path of least structural disruption and lowest labor cost, likely without full appreciation of, or deliberate disregard for, the freeze-exposure consequences for system operability.",
  "proeth-scenario:consequencesIfAlternative": [
    "Interior routing would increase project cost and complexity but would deliver a reliably functional system, fulfilling both the letter and spirit of the ordinance with no downstream hazard.",
    "Freeze-protection measures would add modest cost but would mitigate the hazard at the point of creation, potentially avoiding the entire ethical dilemma Engineer A later faces.",
    "Professional consultation would likely have identified the freeze risk before installation and produced a compliant, safe design, though it would add time and expense the builder was motivated to avoid."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that technical compliance with a safety regulation is not ethically sufficient if the implementation is foreseeably defective. Teaches students to distinguish between letter-of-the-law compliance and genuine fulfillment of the safety purpose behind a requirement, and to recognize how economic incentives can corrupt safety outcomes.",
  "proeth-scenario:ethicalTension": "Contractual obligation to complete the project affordably and on schedule vs. professional and legal duty to install safety systems that actually function as intended. Compliance in form (pipe installed) conflicts with compliance in substance (system reliably operational in all weather conditions).",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Operability of the fire suppression system in a freeze event; resident life safety; builder\u0027s legal liability; the homeowner\u0027s property and insurance standing; the integrity of the city\u0027s fire safety program.",
  "proeth:description": "The builder chose to route retrofitted sprinkler piping through an unheated garage, exposing the system to freezing temperatures that could render it inoperable. This decision was a cost- or convenience-driven routing choice made during the retrofit installation phase.",
  "proeth:eventRoleContext": "Licensed Contractor",
  "proeth:foreseenUnintendedEffects": [
    "Freeze exposure risk to water-filled pipes in unheated space",
    "Potential pipe burst causing property damage",
    "Potential sprinkler system inoperability during a fire event"
  ],
  "proeth:fulfillsObligation": [
    "Technical compliance with ordinance mandate to install sprinkler system",
    "Completion of retrofit within construction timeline"
  ],
  "proeth:guidedByPrinciple": [
    "Do no harm",
    "Public safety in construction practice",
    "Code compliance in spirit as well as letter"
  ],
  "proeth:hasAgent": "Builder",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Compliance expediency vs. system operational integrity",
    "proeth:resolutionReasoning": "Builder resolved in favor of expedient routing, either failing to assess freeze risk, underweighting it, or accepting it as tolerable, a resolution inconsistent with professional duty of care to occupants"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Achieve ordinance compliance with sprinkler installation using available routing paths through the existing structure",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Fire suppression system design and installation",
    "Knowledge of freeze-protection requirements for wet-pipe sprinkler systems",
    "Assessment of thermal conditions in unheated spaces",
    "NFPA 13 or equivalent code compliance analysis"
  ],
  "proeth:temporalMarker": "During construction/retrofit phase, prior to occupancy permit issuance",
  "proeth:temporalSequence": 7,
  "proeth:violatesObligation": [
    "Duty to install systems in a manner that ensures operational reliability",
    "Professional obligation to avoid creating new hazards while remedying existing ones",
    "Duty of care to future occupants whose fire safety depends on system operability",
    "Applicable plumbing and fire protection codes likely prohibiting freeze-exposed sprinkler piping"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Hazardous Sprinkler Pipe Routing"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_Homeowner_Engages_Engineer_A",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Homeowner could have denied garage access and arranged an alternative equipment storage location",
    "Homeowner could have engaged Engineer A under a broader whole-property safety assessment scope",
    "Homeowner could have hired a single general contractor to coordinate all work, eliminating the separate engagement structure"
  ],
  "proeth-scenario:characterMotivation": "The homeowner sought specialized expertise for a specific project need, retaining wall design, and made a practical accommodation by allowing equipment storage on the property. The homeowner likely had no awareness of the sprinkler routing issue and was acting in good faith to manage a separate construction concern efficiently.",
  "proeth-scenario:consequencesIfAlternative": [
    "Denying garage access would have prevented Engineer A from ever observing the hazardous routing, meaning the freeze risk would remain undetected until a failure event or a future inspection.",
    "A broader scope engagement would have made the sprinkler system review part of Engineer A\u0027s formal mandate, simplifying the ethical analysis and potentially producing a more thorough safety assessment.",
    "A single coordinated contractor might have caught the routing issue internally, but also might have perpetuated it if cost pressures dominated; the separate engagement structure was what positioned an independent professional to observe the hazard."
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that the scope of an engineering engagement defines contractual obligations but does not define the outer boundary of professional ethical responsibility. Incidental access granted for one purpose can create ethical obligations that transcend the original contract, a principle students must internalize before entering practice.",
  "proeth-scenario:ethicalTension": "The homeowner\u0027s scoping decision, intended to limit Engineer A\u0027s engagement to retaining wall work, inadvertently created the conditions under which Engineer A would discover an unrelated hazard. This raises the tension between respecting the defined contractual scope and the broader professional obligations that attach to engineers regardless of engagement boundaries.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The clarity and fairness of the contractual relationship; the homeowner\u0027s reasonable expectations about what Engineer A will and will not do; the foundation for Engineer A\u0027s subsequent ethical obligation; the homeowner\u0027s safety and property interests.",
  "proeth:description": "The homeowner made a deliberate decision to hire Engineer A specifically for retaining wall design and separately granted permission for equipment storage in the garage. This scoping decision defined the contractual relationship and set the boundaries of Engineer A\u0027s formal engagement.",
  "proeth:eventRoleContext": "Property Owner and Client",
  "proeth:foreseenUnintendedEffects": [
    "Engineer A\u0027s presence in garage creates opportunity for incidental observation of sprinkler system routing",
    "No awareness that garage access would lead to discovery of a safety deficiency"
  ],
  "proeth:fulfillsObligation": [
    "Exercised property rights in engaging professional services",
    "Provided reasonable access and accommodation to retained engineer"
  ],
  "proeth:guidedByPrinciple": [
    "Autonomy in property and contract decisions",
    "Good faith engagement of professional services"
  ],
  "proeth:hasAgent": "Homeowner",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Obtain professional engineering services for retaining wall design; provide Engineer A with convenient equipment storage access",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Client decision-making regarding professional service procurement"
  ],
  "proeth:temporalMarker": "Prior to Engineer A\u0027s discovery; at project initiation",
  "proeth:temporalSequence": 10,
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Homeowner Engages Engineer A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_Engineer_A_Observes_Hazardous_Routing",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Treat the observation as outside scope and take no action, reasoning that the sprinkler system is not part of the retaining wall engagement",
    "Verbally mention the concern informally to the homeowner without documenting it, treating it as a casual neighborly observation rather than a professional notification",
    "Contact the city building department directly to report the potentially non-compliant installation without first notifying the homeowner"
  ],
  "proeth-scenario:characterMotivation": "Engineer A applied professional training and judgment automatically upon perceiving the pipe routing, the recognition of a freeze-exposure hazard was an expression of competence, not a choice to investigate beyond scope. However, the decision to mentally assess and characterize the risk rather than dismiss the observation as outside scope represents a volitional professional act.",
  "proeth-scenario:consequencesIfAlternative": [
    "Taking no action would leave the homeowner exposed to a known safety risk and would expose Engineer A to professional and potentially legal liability; it would also violate the NSPE Code\u0027s forthright obligation and contradict all three BER precedents cited in the Discussion.",
    "Informal verbal mention without documentation would partially fulfill the duty to warn but would fail to create a record, leave the homeowner without actionable written guidance, and provide Engineer A no protection if the hazard later causes harm, BER Case 76-4 directly addresses why written documentation is essential.",
    "Contacting the city directly without first notifying the homeowner might trigger regulatory action but would bypass the homeowner\u0027s right to know and opportunity to act, potentially damaging the professional relationship and raising questions about Engineer A\u0027s fidelity to the client."
  ],
  "proeth-scenario:decisionSignificance": "This is the pivotal ethical recognition moment in the scenario. Students learn that professional obligations activate at the moment of knowledge, not at the moment of formal engagement. The act of recognition itself carries ethical weight, and engineers cannot ethically \u0027un-know\u0027 a safety hazard by invoking scope limitations.",
  "proeth-scenario:ethicalTension": "The duty to remain within the defined retaining wall engagement scope and avoid unsolicited involvement in other systems vs. the professional obligation under NSPE Code Section III.2 to be forthright and warn of known hazards to life or property. The tension is between contractual discipline and ethical proactivity.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s professional integrity and license standing; the homeowner\u0027s life safety and property; the operability of a fire suppression system that may be needed in an emergency; Engineer A\u0027s potential liability if the hazard causes harm after being observed but not reported.",
  "proeth:description": "While accessing the garage for equipment storage purposes within the authorized scope of the retaining wall engagement, Engineer A observed the sprinkler pipe routing through the unheated space and recognized it as a freeze-exposure hazard. This moment of professional recognition constituted a volitional act of assessment, not merely passive observation.",
  "proeth:eventRoleContext": "Licensed Professional Engineer, retained for retaining wall design",
  "proeth:foreseenUnintendedEffects": [
    "Discovery creates professional obligation to act beyond contracted scope",
    "Reporting may complicate relationship with homeowner-client",
    "Non-reporting risks complicity in a known safety hazard"
  ],
  "proeth:fulfillsObligation": [
    "Applied professional competence to recognize a safety hazard within field of engineering knowledge",
    "Exercised professional vigilance beyond narrow task focus"
  ],
  "proeth:guidedByPrinciple": [
    "Engineers shall hold public safety, health, and welfare paramount",
    "Professional alertness to hazardous conditions regardless of engagement scope",
    "NSPE Code of Ethics Canon 1: public safety above client and employer interests"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Scope fidelity vs. public safety obligation",
    "proeth:resolutionReasoning": "BER precedent and NSPE ethics canon establish that scope limitations do not extinguish the duty to report observed safety hazards; Engineer A\u0027s professional knowledge creates an obligation upon recognition"
  },
  "proeth:hasMentalState": "deliberate recognition; initially incidental observation escalating to professional assessment",
  "proeth:intendedOutcome": "Accessed garage for equipment storage; upon observing pipe routing, applied professional judgment to assess the safety implications",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Recognition of freeze-exposure risk to water-filled piping",
    "Assessment of sprinkler system operational implications",
    "Understanding of fire suppression system requirements"
  ],
  "proeth:temporalMarker": "During retaining wall project execution, while storing equipment in garage",
  "proeth:temporalSequence": 11,
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Observes Hazardous Routing"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Action_Engineer_A_Notifies_Homeowner_in_Writing",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Provide only a verbal warning to the homeowner and consider the obligation discharged",
    "Refuse to proceed with the retaining wall engagement until the sprinkler issue is resolved, using project leverage to compel action",
    "Prepare a written notification but also contact the builder directly to give them an opportunity to self-correct before the homeowner is formally notified"
  ],
  "proeth-scenario:characterMotivation": "Engineer A acted from a synthesis of professional ethical obligation, self-protective documentation instinct, and genuine concern for the homeowner\u0027s safety. The written form was chosen to create a clear record, ensure the homeowner could not later claim ignorance, and fulfill the specific standard established by BER precedent requiring documented notification rather than mere verbal warning.",
  "proeth-scenario:consequencesIfAlternative": [
    "A verbal-only warning, as established by BER Case 76-4, is insufficient because it creates no record and can be denied or forgotten; if the system later fails during a fire, Engineer A would have no documented evidence of having fulfilled the duty to warn.",
    "Withholding retaining wall services as leverage exceeds Engineer A\u0027s ethical mandate, the duty is to notify, not to enforce remediation, and could expose Engineer A to breach of contract claims while inappropriately conflating two separate professional relationships.",
    "Notifying the builder directly might seem collegial but could allow the builder to pressure the homeowner to dismiss the concern, delay remediation, or dispute the characterization of the hazard; the homeowner, as the property owner and Engineer A\u0027s client, is the appropriate and primary recipient of the notification."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates the resolution of the scenario\u0027s central ethical dilemma and models the correct professional response. Students learn that written notification is the minimum standard for fulfilling the duty to warn, that scope limitations do not extinguish safety obligations, and that ethical action sometimes requires delivering unwelcome information within a defined professional relationship.",
  "proeth-scenario:ethicalTension": "The duty to notify competes with concerns about overstepping the retaining wall engagement scope, damaging the relationship with the homeowner, implicitly criticizing the builder\u0027s work, and potentially creating legal complications. Engineer A must balance forthright professional obligation against relational and contractual prudence.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Homeowner\u0027s informed ability to seek remediation; Engineer A\u0027s professional integrity and license protection; the fire suppression system\u0027s reliability in an emergency; the precedential reinforcement of engineering ethics standards in practice.",
  "proeth:description": "Engineer A makes the professional decision to advise the homeowner in writing of the freeze-exposure risk posed by the sprinkler pipe routing through the unheated garage. This written notification fulfills Engineer A\u0027s ethical obligation as determined by BER precedent while remaining bounded by the duty to report rather than investigate or remediate.",
  "proeth:eventRoleContext": "Licensed Professional Engineer, retained for retaining wall design",
  "proeth:foreseenUnintendedEffects": [
    "Homeowner may be alarmed or dispute the concern",
    "Notification may strain the client relationship",
    "Written record protects Engineer A from future liability for non-disclosure",
    "Homeowner may seek remediation from builder, creating dispute",
    "Notification does not guarantee the hazard will be corrected"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code of Ethics Canon 1: hold public safety, health, and welfare paramount",
    "Duty to notify client of known safety risks affecting their property and safety",
    "Duty of faithful agency to homeowner-client by ensuring client has safety-relevant information",
    "Obligation established by BER precedent (Cases 76-4, 90-5, 17-3) to report discovered hazards in writing",
    "Duty of transparency and honest communication with client"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety primacy over scope and contractual convenience",
    "Written documentation as the standard for discharging safety notification duty",
    "Honest and forthright communication with clients",
    "Engineer\u0027s role as protector of public welfare regardless of engagement scope"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Scope limitation and client relationship preservation vs. public safety reporting duty",
    "proeth:resolutionReasoning": "BER resolves the conflict by calibrating the obligation: Engineer A must notify in writing (fulfilling safety duty) but need not investigate further or recommend mitigation (respecting scope limitation and absence of contractual authority). Written notification is the minimum necessary and sufficient action to discharge the professional ethical obligation."
  },
  "proeth:hasMentalState": "deliberate and obligatory; compliance with professional ethical duty",
  "proeth:intendedOutcome": "Ensure homeowner is informed of the safety risk so the homeowner can take appropriate action; create documented record of notification; discharge Engineer A\u0027s professional ethical obligation",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Professional recognition of freeze-exposure hazard in sprinkler systems",
    "Ability to communicate technical safety concern clearly in writing to a non-engineer client",
    "Knowledge of professional ethical obligations under NSPE Code of Ethics",
    "Understanding of BER precedent regarding scope of duty to report"
  ],
  "proeth:temporalMarker": "Following discovery; during or after retaining wall project execution; present case resolution point",
  "proeth:temporalSequence": 13,
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Notifies Homeowner in Writing"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Event_BER_Precedent_Body_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the existence of 40 years of consistent BER precedent affect the moral weight of Engineer A\u0027s obligation: does precedent create duty, or merely confirm a duty that always existed?",
    "What do the three BER cases have in common, and what distinguishes Engineer A\u0027s situation from each of them?",
    "Should engineers be required to study BER precedent as part of licensure? What does ignorance of professional ethics precedent imply for professional responsibility?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Retrospectively, engineers in the prior cases faced the same internal conflict between scope and duty; for Engineer A, the existence of this precedent may provide moral clarity and professional confidence to act; for students, it illustrates that ethical dilemmas recur across generations",
  "proeth-scenario:ethicalImplications": "Illustrates the role of institutional precedent in defining professional ethics; raises questions about whether ethical obligations are discovered through reasoning or constructed through professional consensus; highlights the tension between individual judgment and institutional authority in professional ethics",
  "proeth-scenario:learningMoment": "Demonstrates how professional ethics evolve through case-based reasoning; shows that BER precedent functions similarly to common law, each case builds on prior decisions to create increasingly clear professional norms; illustrates the importance of institutional memory in professional ethics.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "builders_and_contractors": "Aware that engineers they interact with carry disclosure obligations that transcend contractual boundaries",
    "engineer_a": "Precedent removes ambiguity, professional norms clearly require action; also provides protection against claims of overstepping",
    "engineering_profession": "Consistency of precedent strengthens public trust in engineers as safety guardians",
    "public": "Benefits from a profession with clear, enforced norms around safety disclosure"
  },
  "proeth:activatesConstraint": [
    "NSPE_BER_Precedent_Constraint",
    "Professional_Norm_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/59#Action_BER_Case_76-4_Engineer_Files_Written_Report__BER_C",
  "proeth:causesStateChange": "A normative professional standard is crystallized across three decades: engineers cannot use scope-of-engagement as a shield against reporting known safety hazards; this standard applies retroactively as interpretive authority to new cases",
  "proeth:description": "Through three prior BER cases (1976, 1990, 2017), a body of precedent was established holding that engineers who discover safety hazards outside their contracted scope retain an ethical duty to report those hazards, forming the normative foundation for analyzing Engineer A\u0027s obligations.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "1976 (Case 76-4), 1990 (Case 90-5), 2017 (Case 17-3), prior to the current case",
  "proeth:temporalSequence": 4,
  "proeth:urgencyLevel": "low",
  "rdfs:label": "BER Precedent Body Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Event_Sprinkler_Ordinance_Takes_Effect",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is it ethically justifiable for a city to apply a safety ordinance retroactively to projects already underway? What competing values are at stake?",
    "How should engineers and builders respond when new regulations impose unexpected compliance burdens mid-project?",
    "Does the intent of a safety regulation (fire protection) justify the compliance pressure that may have led to the hazardous pipe routing?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Builder feels burdened and possibly resentful of unexpected regulatory cost; homeowner may feel anxious about delays and added expense; city officials feel satisfied with proactive safety measure",
  "proeth-scenario:ethicalImplications": "Reveals tension between regulatory intent (public safety) and the practical pressures that retroactive mandates place on builders, potentially incentivizing non-compliant or hazardous shortcuts; raises questions about fairness and foreseeability in regulatory design",
  "proeth-scenario:learningMoment": "Illustrates how regulatory changes can impose retroactive obligations and how compliance pressures can lead to shortcuts that create new hazards, the root cause of the subsequent safety risk.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "builder": "Unexpected retrofitting cost and schedule delay; must redesign or adapt construction plans",
    "city": "Increased public fire safety; administrative burden of enforcement",
    "future_occupants": "Greater fire protection once compliant system installed",
    "homeowner": "Potential cost increases passed through contract; occupancy delayed"
  },
  "proeth:activatesConstraint": [
    "Regulatory_Compliance_Constraint",
    "Retroactive_Code_Application_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/59#Action_Retroactive_Ordinance_Enactment",
  "proeth:causesStateChange": "Project\u0027s legal compliance status changed; builder now legally required to install sprinkler system before occupancy permit can be issued",
  "proeth:createsObligation": [
    "Builder_Must_Install_Sprinklers",
    "Homeowner_Must_Comply_Before_Occupancy"
  ],
  "proeth:description": "The city\u0027s retroactive sprinkler ordinance becomes legally binding, applying to all residential projects that have not yet received occupancy permits, including the builder\u0027s project under construction.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Before construction completion; prior to occupancy permit issuance",
  "proeth:temporalSequence": 6,
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Sprinkler Ordinance Takes Effect"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Event_Sprinkler_System_Installed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Who bears moral responsibility for the hazardous routing: the builder who chose it, the city that imposed retroactive requirements, or both?",
    "How does a latent defect (one not immediately visible) complicate the ethics of disclosure and discovery?",
    "Should building inspectors or the permitting process have caught this routing problem before occupancy?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Builder may be unaware of or indifferent to the hazard; homeowner is unaware and therefore not alarmed; future occupants face risk without knowledge; the hazard exists silently",
  "proeth-scenario:ethicalImplications": "Exposes the gap between regulatory compliance and genuine safety; raises questions about builder competence, professional accountability, and whether cost or schedule pressures can morally excuse technically deficient work",
  "proeth-scenario:learningMoment": "Demonstrates how compliance with the letter of a safety regulation can still result in a safety hazard if the implementation is technically deficient; illustrates the concept of latent defects and how regulatory pressure can produce corner-cutting.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "builder": "Potential liability for negligent installation; risk of professional sanction",
    "city": "Ordinance\u0027s safety intent undermined by non-compliant implementation",
    "future_occupants": "Life-safety risk if pipes freeze and system fails during a fire",
    "homeowner": "Unknowingly occupying a home with a defective fire suppression system"
  },
  "proeth:activatesConstraint": [
    "Public_Safety_Hazard_Constraint",
    "Freeze_Risk_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/59#Action_Hazardous_Sprinkler_Pipe_Routing",
  "proeth:causesStateChange": "A latent but serious safety hazard now exists in the residence; the sprinkler system is installed but is vulnerable to freezing failure, which could render it inoperable precisely when needed in a fire",
  "proeth:description": "As a direct result of the retroactive ordinance, the builder installs a sprinkler system throughout the residence, including routing pipes through an unheated garage, creating a freezing hazard.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After ordinance enactment; before occupancy permit issuance; before Engineer A\u0027s site visit",
  "proeth:temporalSequence": 8,
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Sprinkler System Installed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Event_Pipes_Exposed_to_Freeze_Risk",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the latent nature of this hazard (it may never manifest if winters are mild) affect the ethical urgency of disclosure?",
    "Who is morally responsible for the ongoing risk: the builder who created it, the inspector who may have missed it, or the engineer who later discovers it?",
    "Does the severity of the potential consequence (fire suppression failure during a house fire) change the ethical calculus compared to a less catastrophic latent defect?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "The hazard exists silently, no one in the home feels the danger; the emotional weight falls on Engineer A once discovered, and on the homeowner once informed; there is a quiet but serious menace to this event",
  "proeth-scenario:ethicalImplications": "Reveals how technical decisions have moral consequences that persist over time; raises questions about the relationship between probability of harm and duty to act; illustrates that a low-probability, high-severity risk carries significant ethical weight in engineering practice",
  "proeth-scenario:learningMoment": "Illustrates the concept of a latent defect, a hazard that exists independently of anyone\u0027s awareness of it; teaches students that engineering failures are often silent until triggered, and that the gap between installation and failure can be long, obscuring accountability.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "builder": "Ongoing liability exposure; professional and legal risk accumulates silently",
    "city": "Ordinance\u0027s fire-safety purpose is being actively undermined by non-compliant implementation",
    "future_occupants": "Face same risk without any awareness",
    "homeowner": "Living with an unknown risk; fire suppression system may fail in a fire, potentially resulting in property loss or death"
  },
  "proeth:activatesConstraint": [
    "Latent_Safety_Hazard_Constraint",
    "Fire_Suppression_System_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/59#Action_Hazardous_Sprinkler_Pipe_Routing",
  "proeth:causesStateChange": "The residence now contains a fire suppression system that is structurally vulnerable to failure at the moment of greatest need; the hazard is latent (not immediately apparent) but physically real and worsening with seasonal temperature drops",
  "proeth:description": "With the completion of the sprinkler installation routing pipes through the unheated garage, those pipes become continuously exposed to ambient temperatures that may drop below freezing, creating an ongoing and latent threat to the integrity of the fire suppression system.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Immediately upon completion of sprinkler installation; ongoing until remediation",
  "proeth:temporalSequence": 9,
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Pipes Exposed to Freeze Risk"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Event_Freeze_Hazard_Exposed_to_Engineer_A",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does an engineer\u0027s duty to protect public safety apply even when the hazard is entirely outside the scope of their contracted work? Why or why not?",
    "At what threshold of certainty about a hazard is an engineer obligated to act: must they be certain, or is reasonable suspicion sufficient?",
    "How does Engineer A\u0027s situation differ from that of a random passerby who notices the same pipes? What does professional licensure add to the moral equation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences surprise, concern, and perhaps discomfort at being drawn into a situation outside his contracted scope; internal conflict between \u0027not my job\u0027 instinct and professional duty; homeowner remains unaware and unaffected at this moment",
  "proeth-scenario:ethicalImplications": "Reveals the core tension between contractual scope and professional duty; demonstrates that licensure creates obligations that transcend client agreements; raises questions about the boundaries of professional responsibility and the moral weight of specialized knowledge",
  "proeth-scenario:learningMoment": "This is the pivotal moment illustrating that an engineer\u0027s ethical obligations are not bounded by the scope of their contract, knowledge of a safety hazard triggers duties regardless of the engineer\u0027s original assignment.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "builder": "Potential exposure increases as a third-party professional has now identified the defect",
    "engineer_a": "Now carries professional and ethical obligation to act; inaction would constitute an ethics violation; potential personal liability if harm results from silence",
    "future_occupants": "Safety outcome contingent on whether Engineer A acts",
    "homeowner": "Remains at risk but unaware; outcome depends on Engineer A\u0027s response"
  },
  "proeth:activatesConstraint": [
    "NSPE_Code_Section_III_1_Constraint",
    "Public_Safety_Paramount_Constraint",
    "Duty_To_Warn_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/59#Action_Engineer_A_Observes_Hazardous_Routing",
  "proeth:causesStateChange": "Engineer A transitions from uninformed bystander to a professional with actual knowledge of a public safety hazard; ethical obligations are now triggered regardless of scope of original engagement",
  "proeth:createsObligation": [
    "Engineer_A_Must_Notify_Homeowner",
    "Engineer_A_Must_Document_Observation_In_Writing"
  ],
  "proeth:description": "While storing equipment in the homeowner\u0027s garage in the course of his retaining wall work, Engineer A incidentally observes the sprinkler pipes routed through the unheated space, recognizing the freezing risk.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "During Engineer A\u0027s site work for retaining wall; after sprinkler installation",
  "proeth:temporalSequence": 12,
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Freeze Hazard Exposed to Engineer A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#Event_Homeowner_Receives_Safety_Warning",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer A\u0027s ethical obligation end with written notification to the homeowner, or does it extend further: for example, to notifying the city or building inspector?",
    "How should Engineer A communicate the hazard in writing: what level of technical detail, urgency, and recommended action is appropriate?",
    "If the homeowner dismisses or ignores the warning, what further obligations, if any, does Engineer A have?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Homeowner likely experiences alarm, anxiety, and possibly anger toward the builder; Engineer A may feel relief at having fulfilled duty but also discomfort about potential conflict with the builder or homeowner\u0027s reaction; builder faces potential confrontation",
  "proeth-scenario:ethicalImplications": "Demonstrates the principle that informed consent and knowledge transfer are central to engineering ethics; raises questions about the limits of professional duty and whether notification alone is sufficient when life safety is at stake; highlights the engineer\u0027s role as protector of public welfare even within private client relationships",
  "proeth-scenario:learningMoment": "Illustrates that an engineer\u0027s duty to warn is fulfilled by providing clear, written notification: the engineer is not responsible for ensuring remediation occurs, but must ensure the responsible party has the information needed to act.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "builder": "Exposed to homeowner complaint, potential regulatory action, and liability",
    "city": "Ordinance\u0027s safety intent can now be realized if homeowner acts on the warning",
    "engineer_a": "Ethical obligation discharged; professional integrity maintained; potential for strained relationship with homeowner if message is unwelcome",
    "future_occupants": "Safety outcome now depends on homeowner\u0027s response rather than remaining purely at risk",
    "homeowner": "Now empowered to demand remediation; may have legal recourse against builder; faces cost and disruption of repair"
  },
  "proeth:activatesConstraint": [
    "Homeowner_Duty_To_Remediate_Constraint",
    "Informed_Consent_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/59#Action_Engineer_A_Notifies_Homeowner_in_Writing",
  "proeth:causesStateChange": "Homeowner transitions from unknowing victim to informed party with ability and responsibility to act; Engineer A\u0027s ethical obligation is discharged upon written notification; the hazard itself persists until remediated",
  "proeth:createsObligation": [
    "Homeowner_Must_Investigate_And_Remediate",
    "Homeowner_May_Seek_Recourse_From_Builder"
  ],
  "proeth:description": "As the outcome of Engineer A\u0027s written notification, the homeowner becomes aware of the freeze risk in the sprinkler system, shifting from a state of ignorance to informed awareness of a life-safety hazard in their home.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A Notifies Homeowner in Writing; prior to occupancy or during early occupancy",
  "proeth:temporalSequence": 14,
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Homeowner Receives Safety Warning"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#CausalChain_b7d0463d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct result of the retroactive ordinance, the builder installs a sprinkler system throughout",
  "proeth:causalSequence": [
    {
      "proeth:description": "City deliberately extends sprinkler requirement to all residential projects not yet receiving final approval",
      "proeth:element": "Retroactive Ordinance Enactment (Action 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Ordinance becomes legally binding, creating mandatory compliance obligation for the builder",
      "proeth:element": "Sprinkler Ordinance Takes Effect (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Builder installs sprinkler system throughout the residence to satisfy the new legal requirement",
      "proeth:element": "Sprinkler System Installed (Event 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Builder routes retrofitted piping through unheated garage, creating freeze exposure risk",
      "proeth:element": "Hazardous Sprinkler Pipe Routing (Action 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Completed installation leaves pipes vulnerable to freezing temperatures in unheated garage",
      "proeth:element": "Pipes Exposed to Freeze Risk (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Retroactive Ordinance Enactment (Action 1)",
  "proeth:counterfactual": "Without the retroactive ordinance, no sprinkler system would have been required or installed in this residential project; the hazardous routing situation would never have arisen",
  "proeth:effect": "Sprinkler System Installed (Event 2)",
  "proeth:necessaryFactors": [
    "City\u0027s legal authority to enact retroactive ordinance",
    "Project not yet having received final approval at time of enactment",
    "Builder\u0027s legal obligation to comply with municipal code"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "City Government",
  "proeth:sufficientFactors": [
    "Retroactive ordinance legally binding + project within scope of ordinance + builder compliance obligation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#CausalChain_143ec503",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "With the completion of the sprinkler installation routing pipes through the unheated garage, those pipes are exposed to freeze risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Builder chooses to route retrofitted sprinkler piping through the unheated garage",
      "proeth:element": "Hazardous Sprinkler Pipe Routing (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Installation is completed with the deficient routing incorporated into the finished system",
      "proeth:element": "Sprinkler System Installed (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Water-filled pipes in unheated garage become vulnerable to freezing, risking pipe burst and system failure",
      "proeth:element": "Pipes Exposed to Freeze Risk (Event 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A discovers the hazardous routing while accessing the garage for authorized retaining wall work",
      "proeth:element": "Freeze Hazard Exposed to Engineer A (Event 3)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s written notification brings the latent hazard to the homeowner\u0027s attention",
      "proeth:element": "Homeowner Receives Safety Warning (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Hazardous Sprinkler Pipe Routing (Action 2)",
  "proeth:counterfactual": "Had the builder routed pipes through heated interior spaces or applied adequate freeze protection, the pipes would not have been exposed to freeze risk regardless of ambient temperatures",
  "proeth:effect": "Pipes Exposed to Freeze Risk (Event 6)",
  "proeth:necessaryFactors": [
    "Decision to route pipes through unheated garage space",
    "Absence of freeze-protection measures such as insulation or heat tracing",
    "Garage remaining unheated during cold weather periods"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Builder",
  "proeth:sufficientFactors": [
    "Unprotected pipe routing through unheated space + ambient freezing temperatures = realized freeze hazard"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#CausalChain_16e6bcd5",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "While storing equipment in the homeowner\u0027s garage in the course of his retaining wall work, Engineer A observes the hazardous routing",
  "proeth:causalSequence": [
    {
      "proeth:description": "Homeowner hires Engineer A specifically for retaining wall design, granting site access",
      "proeth:element": "Homeowner Engages Engineer A (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A enters the garage within authorized scope to store retaining wall project equipment",
      "proeth:element": "Engineer A Accesses Garage (implied by Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A observes sprinkler pipes routed through the unheated garage and recognizes the freeze risk",
      "proeth:element": "Freeze Hazard Exposed to Engineer A (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A exercises professional judgment to advise the homeowner in writing of the out-of-scope hazard",
      "proeth:element": "Engineer A Notifies Homeowner in Writing (Action 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Homeowner becomes aware of the freeze risk and can take corrective action",
      "proeth:element": "Homeowner Receives Safety Warning (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Homeowner Engages Engineer A (Action 3)",
  "proeth:counterfactual": "Without the engagement of Engineer A for retaining wall work, no qualified engineer would have had occasion to access the garage and observe the deficient routing; the hazard would have remained latent until a freeze event caused pipe failure",
  "proeth:effect": "Freeze Hazard Exposed to Engineer A (Event 3)",
  "proeth:necessaryFactors": [
    "Homeowner\u0027s decision to hire Engineer A for retaining wall work",
    "Engineer A\u0027s authorized access to the garage for equipment storage",
    "Pipes being visibly routed through the garage in an observable manner",
    "Engineer A\u0027s professional competence to recognize the freeze hazard"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Homeowner",
  "proeth:sufficientFactors": [
    "Authorized garage access + visible hazardous routing + Engineer A\u0027s professional knowledge = hazard discovery"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#CausalChain_38ae25ca",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As the outcome of Engineer A\u0027s written notification, the homeowner becomes aware of the freeze risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A observes the hazardous pipe routing during authorized garage access",
      "proeth:element": "Freeze Hazard Exposed to Engineer A (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Existing BER cases 76-4, 90-5, and 17-3 provide ethical framework obligating disclosure of observed hazards",
      "proeth:element": "BER Precedent Body Established (Event 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A makes professional decision to advise homeowner in writing of the freeze-exposure risk",
      "proeth:element": "Engineer A Notifies Homeowner in Writing (Action 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Homeowner becomes aware of the freeze risk through Engineer A\u0027s written notification",
      "proeth:element": "Homeowner Receives Safety Warning (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Homeowner is now positioned to engage the builder or a plumbing engineer to correct the deficient routing before a freeze event",
      "proeth:element": "Potential Remediation (implied outcome)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Notifies Homeowner in Writing (Action 5)",
  "proeth:counterfactual": "Had Engineer A remained silent about the out-of-scope hazard, the homeowner would have remained unaware until a freeze event caused pipe rupture, potential property damage, or fire suppression system failure",
  "proeth:effect": "Homeowner Receives Safety Warning (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s professional decision to act on the observed hazard despite it being outside the retaining wall scope",
    "Engineer A\u0027s recognition that the freeze hazard posed a risk to public safety",
    "Written form of notification creating a documented record",
    "BER precedent body supporting the ethical obligation to disclose"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Engineer A\u0027s professional ethics obligation + observed hazard + written notification = homeowner awareness and documented warning"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/59#",
    "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/59#CausalChain_c76ab318",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Through three prior BER cases (1976, 1990, 2017), a body of precedent was established holding that engineers must disclose observed safety hazards",
  "proeth:causalSequence": [
    {
      "proeth:description": "1976 BER precedent establishes that engineers must document and report hazards in writing even against client wishes",
      "proeth:element": "BER Case 76-4 Engineer Files Written Report (Action 6)",
      "proeth:step": 1
    },
    {
      "proeth:description": "1990 BER precedent reinforces disclosure obligation, extending it to situations where attorneys instruct confidentiality",
      "proeth:element": "BER Case 90-5 Engineer Discloses Structural Defects (Action 7)",
      "proeth:step": 2
    },
    {
      "proeth:description": "2017 BER precedent establishes that engineers may and must expand scope to address discovered safety hazards",
      "proeth:element": "BER Case 17-3 Forensic Engineer Expands Report Scope (Action 8)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Three-decade body of consistent precedent creates clear ethical mandate for disclosure of observed hazards regardless of engagement scope",
      "proeth:element": "BER Precedent Body Established (Event 5)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A applies the precedent body to the observed freeze hazard, issuing written notification to the homeowner",
      "proeth:element": "Engineer A Notifies Homeowner in Writing (Action 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "BER Precedent Body Established (Event 5)",
  "proeth:counterfactual": "Without the established BER precedent body, Engineer A might have rationalized silence on the grounds that the hazard was outside the retaining wall engagement scope; the precedents remove that ethical escape route and affirmatively require disclosure",
  "proeth:effect": "Engineer A Notifies Homeowner in Writing (Action 5)",
  "proeth:necessaryFactors": [
    "BER Case 76-4 establishing that engineers must file written reports of hazards even against client instruction",
    "BER Case 90-5 establishing that engineers must disclose structural defects despite attorney instruction to maintain confidentiality",
    "BER Case 17-3 establishing that forensic engineers may expand report scope to include discovered safety hazards",
    "Engineer A\u0027s awareness of or access to these precedents through professional education and NSPE membership"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "NSPE Board of Ethical Review (collective institutional responsibility)",
  "proeth:sufficientFactors": [
    "Consistent BER precedent across three decades + Engineer A\u0027s professional obligation to know applicable ethics standards = ethical mandate to disclose the freeze hazard in writing"
  ],
  "proeth:withinAgentControl": true
}