{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Action_Proceed_Without_Literature_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct a targeted literature review of current severe weather design standards before beginning design work",
    "Consult with a specialist or colleague with recent expertise in severe weather structural design",
    "Pause project initiation to formally assess whether existing knowledge is current and sufficient for this specific regional context"
  ],
  "proeth-scenario:characterMotivation": "Engineer A likely believed his existing knowledge and general awareness of design trends were sufficient for the project, possibly combined with time constraints, budget pressures, or an overconfidence in his accumulated regional experience. He may not have recognized that a literature review was a professional obligation rather than an optional enhancement.",
  "proeth-scenario:consequencesIfAlternative": [
    "A targeted literature review would have surfaced the newly published severe weather design parameters, enabling their incorporation from the outset and likely preventing the subsequent structural failure",
    "Consulting a specialist would have introduced updated knowledge into the design process, potentially identifying critical gaps in Engineer A\u0027s awareness and satisfying the professional duty of competence through collaborative practice",
    "A formal sufficiency assessment would have created a documented record of due diligence and may have flagged the need for additional research or expertise, redirecting the project toward a safer design trajectory before any design work commenced"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that the obligation to remain current with technical literature is not merely aspirational but constitutes a baseline professional competency standard. Engineers cannot substitute familiarity with past practice for awareness of newly published standards, particularly in high-risk design contexts such as severe weather regions.",
  "proeth-scenario:ethicalTension": "Efficiency and confidence in established expertise vs. the professional duty to maintain current competency; self-assessed sufficiency vs. the evolving standard of care; practical project momentum vs. diligent pre-design due diligence.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public safety in a severe weather region, structural integrity of the completed building, Engineer A\u0027s professional licensure and reputation, potential civil and ethical liability, and the broader standard of care expected across the profession.",
  "proeth:description": "Engineer A decided to proceed with the structural design project without first conducting a comprehensive review of the most recent technical literature on severe weather design standards, relying instead on existing knowledge and general awareness of design trends.",
  "proeth:foreseenUnintendedEffects": [
    "Potential gap in awareness of emerging design parameters not yet identified as a risk by Engineer A"
  ],
  "proeth:fulfillsObligation": [
    "General duty to apply established structural engineering principles",
    "Duty to leverage region-specific experience"
  ],
  "proeth:guidedByPrinciple": [
    "Competence in professional practice",
    "Protection of public health, safety, and welfare"
  ],
  "proeth:hasAgent": "Engineer A (Structural Engineer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Currency of knowledge vs. practical limits of continuous literature monitoring",
    "proeth:resolutionReasoning": "Engineer A implicitly prioritized reliance on established experience over exhaustive pre-design literature review; the BER found this insufficient to constitute unethical conduct because the new parameters had not yet achieved the status of generally accepted standards"
  },
  "proeth:hasMentalState": "deliberate but uninformed",
  "proeth:intendedOutcome": "Efficiently begin design work using established competence and experience in the region",
  "proeth:requiresCapability": [
    "Awareness of current and emerging severe weather structural design standards",
    "Systematic review of recent technical literature relevant to practice region",
    "Critical evaluation of whether existing knowledge base is sufficient for the specific project context"
  ],
  "proeth:temporalMarker": "Pre-design phase, prior to commencement of structural system design",
  "proeth:violatesObligation": [
    "Duty to maintain current knowledge of evolving design standards relevant to the specific practice context (NSPE Code Section II.2.b)",
    "Duty to perform services only within areas of competence, which implicitly includes awareness of current standards"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Proceed Without Literature Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Action_Design_Using_Established_Principles",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Pause mid-design upon recognizing uncertainty about severe weather parameters and conduct a targeted literature search before finalizing structural calculations",
    "Explicitly flag the severe weather design assumptions in design documentation and seek peer review from an engineer with current knowledge of applicable standards",
    "Reach out to the relevant professional society, building authority, or technical working group to verify whether updated severe weather design guidance exists for the region"
  ],
  "proeth-scenario:characterMotivation": "Engineer A was confident that the structural principles he applied were sound and reflected competent engineering practice as he understood it. He likely acted in good faith, drawing on regional experience and established methodologies, without awareness that his knowledge base was materially incomplete relative to newly published standards applicable to the project context.",
  "proeth-scenario:consequencesIfAlternative": [
    "Pausing mid-design to review literature would have interrupted momentum but would likely have surfaced the new standards in time to incorporate them, preserving structural safety without requiring a full redesign after construction",
    "Flagging assumptions and seeking peer review would have introduced a check on Engineer A\u0027s knowledge gap, distributing responsibility appropriately and creating a documented quality control step that could have caught the deficiency before the design was finalized",
    "Consulting a professional society or building authority would have provided authoritative confirmation of the current standard of care, giving Engineer A both the technical information needed and a defensible record of diligent inquiry"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that good intentions and genuine technical skill do not substitute for currency of knowledge. Ethics education should emphasize that the standard of care is externally defined by what a competent, reasonably diligent engineer would know and apply\u2014not by what an individual engineer subjectively believes is sufficient. This action also highlights the compounding risk of proceeding through design phases once an early knowledge gap goes unaddressed.",
  "proeth-scenario:ethicalTension": "Good-faith application of known principles vs. the objective standard of care that requires awareness of current published standards; personal confidence in professional judgment vs. the public\u0027s reliance on engineers to proactively incorporate the best available technical knowledge; completing a deliverable vs. ensuring that deliverable meets the evolving threshold of competent practice.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The structural safety of the building under foreseeable severe weather loading, the lives and property of future occupants and neighbors, Engineer A\u0027s professional and legal accountability, and the integrity of the engineering process as a public safety mechanism.",
  "proeth:description": "Engineer A completed the structural system design based on what he believed constituted sound structural engineering principles, without incorporating the newly published severe weather design parameters, relying on his existing knowledge and regional experience.",
  "proeth:foreseenUnintendedEffects": [
    "None identified by Engineer A at the time; Engineer A believed the design was sound"
  ],
  "proeth:fulfillsObligation": [
    "Duty to apply professional engineering judgment and established structural engineering principles",
    "Duty to leverage region-specific experience in designing for severe weather conditions",
    "Duty to complete contracted professional services"
  ],
  "proeth:guidedByPrinciple": [
    "Competence and soundness of engineering judgment",
    "Public safety paramount",
    "Professional integrity in design execution"
  ],
  "proeth:hasAgent": "Engineer A (Structural Engineer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Obligation to use most current design methods vs. reasonable reliance on established and proven engineering principles",
    "proeth:resolutionReasoning": "Engineer A resolved the tension by relying on established engineering principles, which the BER found did not constitute unethical conduct because the new parameters had not yet been peer-reviewed or incorporated into generally accepted practice as formal standards, and because Engineer A\u0027s conduct lacked the intentional, reckless, or malicious character required for an ethical violation"
  },
  "proeth:hasMentalState": "deliberate and good faith",
  "proeth:intendedOutcome": "Produce a structurally sound building design that meets engineering standards as understood by Engineer A at the time of design",
  "proeth:requiresCapability": [
    "Awareness of newly published severe weather design parameters specific to the practice region",
    "Integration of emerging design methods into structural system design",
    "Critical assessment of whether existing design approaches are sufficient given evolving knowledge in the field"
  ],
  "proeth:temporalMarker": "Design phase, during preparation of structural system design",
  "proeth:violatesObligation": [
    "Duty to incorporate current and relevant design standards into professional practice (NSPE Code Section II.2.b)",
    "Duty to hold paramount the safety, health, and welfare of the public (NSPE Code Section I.1), to the extent that awareness of new parameters was reasonably attainable"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Design Using Established Principles"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Action_Release_Design_for_Construction",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct a pre-release design review specifically focused on verifying that the design addresses current severe weather requirements for the region before signing and sealing the documents",
    "Require an independent technical review or peer check of the structural design by a second qualified engineer before releasing for construction",
    "Voluntarily delay release of the design pending confirmation from the local building authority or a current code reference that the severe weather design parameters used are up to date"
  ],
  "proeth-scenario:characterMotivation": "Engineer A likely considered the design complete and technically sound based on his own assessment, and proceeded to release it for construction in the ordinary course of project delivery. Without awareness of the knowledge gap established in prior actions, he had no subjective reason to revisit or update the design before construction commenced. Project schedule, client expectations, and professional confidence in his completed work all reinforced forward momentum.",
  "proeth-scenario:consequencesIfAlternative": [
    "A pre-release design review focused on severe weather adequacy would have been the final safeguard in the engineering process; even at this late stage, discovering the new standards would have allowed redesign before construction began, preventing the failure at the cost of schedule delay",
    "An independent peer review would have introduced a second professional with potentially more current knowledge, creating a quality control mechanism capable of identifying the knowledge gap and triggering necessary design revisions before construction locked in the deficient parameters",
    "Delaying release pending code verification would have been the most conservative and defensible course of action; confirmation from the building authority would have either validated the design or surfaced the new standards, and the temporary schedule impact would have been far less costly than the post-construction failure and its consequences"
  ],
  "proeth-scenario:decisionSignificance": "Represents the last clear opportunity in the engineering process to intercept and correct the knowledge gap before it becomes embedded in physical construction. Ethics education should use this action to emphasize that design release is not merely an administrative act\u2014it is a professional certification that the design meets the applicable standard of care. It also illustrates the concept of compounding ethical omissions: each prior failure to act narrowed the window for correction, making this final decision point the most consequential.",
  "proeth-scenario:ethicalTension": "Fulfilling contractual and schedule obligations to the client vs. the overriding duty to public safety; treating design completion as a procedural milestone vs. treating it as a final opportunity to verify adequacy; deference to one\u0027s own prior work product vs. professional responsibility to subject that work to scrutiny before it becomes permanent.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Irreversible commitment of a deficient design to physical construction; the safety of building occupants and the public during the building\u0027s operational life; the professional, legal, and reputational consequences for Engineer A upon post-failure analysis; the potential for catastrophic structural failure under foreseeable severe weather conditions\u2014ultimately realized within one year of construction.",
  "proeth:description": "Engineer A allowed his completed structural design to be incorporated into the plans and specifications for the building without revisiting or updating the design before construction commenced, resulting in the building being constructed without the newly published severe weather design parameters.",
  "proeth:foreseenUnintendedEffects": [
    "None identified by Engineer A; no indication that Engineer A had any reason at this stage to question the adequacy of the design"
  ],
  "proeth:fulfillsObligation": [
    "Duty to deliver professional engineering services and completed design documents",
    "Duty to ensure design was based on sound engineering principles as understood at the time"
  ],
  "proeth:guidedByPrinciple": [
    "Professional responsibility for design documents released for construction",
    "Continuity of competence obligation through the project lifecycle",
    "Public safety as paramount concern"
  ],
  "proeth:hasAgent": "Engineer A (Structural Engineer of Record)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Project delivery obligations vs. ongoing duty to verify currency of design standards before construction",
    "proeth:resolutionReasoning": "Engineer A resolved the tension by proceeding with construction release based on good-faith reliance on established engineering principles; the BER\u0027s analysis suggests that without awareness of the new parameters and absent reckless conduct, this decision did not constitute an ethical violation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Advance the project to construction in accordance with the completed design, which Engineer A believed was sound",
  "proeth:requiresCapability": [
    "Pre-release review of design against current technical literature",
    "Ongoing professional development monitoring to identify newly published standards relevant to active projects",
    "Judgment to determine when emerging literature warrants design revision before construction"
  ],
  "proeth:temporalMarker": "Post-design phase, prior to and during construction",
  "proeth:violatesObligation": [
    "Ongoing duty to monitor and incorporate current design standards before finalizing documents for construction (NSPE Code Section II.2.b)",
    "Duty to hold paramount public safety, particularly in a severe weather region with known structural risk implications"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Release Design for Construction"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Event_New_Standards_Published",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what point does a newly published standard become part of the minimum standard of care \u2014 upon publication, upon wide dissemination, or upon some other threshold?",
    "Is it ethically sufficient for an engineer to rely on established principles if they have not actively monitored recent technical literature? Why or why not?",
    "What systemic responsibilities do professional societies, employers, and licensing boards have to ensure engineers are aware of newly published standards?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Neutral at time of occurrence \u2014 Engineer A is unaware, so no immediate emotional response; retrospectively, this event becomes a source of regret and professional self-scrutiny; professional community may feel urgency to disseminate standards more effectively",
  "proeth-scenario:ethicalImplications": "Reveals tension between the practical limits of individual knowledge-keeping and the profession\u0027s expectation of continuous competency; raises questions about whether the duty to know is absolute or contextually bounded; highlights the collective responsibility of the profession to disseminate critical safety-related standards effectively",
  "proeth-scenario:learningMoment": "The publication of new standards creates an objective professional duty to know, regardless of subjective awareness. Engineers must maintain active engagement with technical literature \u2014 passive familiarity with established knowledge is insufficient in a rapidly evolving field. This event illustrates that the standard of care is dynamic, not static.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "building_owner_client": "Exposed to structural risk without knowledge; relying on engineer\u0027s competency to incorporate current standards",
    "engineer_a": "Unknowingly enters a state of professional non-compliance; future conduct will be judged against these standards regardless of awareness",
    "future_occupants_public": "Safety implicitly dependent on engineer\u0027s currency with published standards",
    "professional_community": "Obligation to disseminate new standards effectively; publication alone may be insufficient without active outreach"
  },
  "proeth:activatesConstraint": [
    "Competency_Currency_Constraint",
    "Continuing_Education_Obligation",
    "Literature_Awareness_Standard"
  ],
  "proeth:causesStateChange": "The professional standard of care is elevated; engineers practicing in severe weather regions are now expected to be aware of and apply updated parameters; ignorance of the published standards does not negate the obligation to know them.",
  "proeth:createsObligation": [
    "Monitor_Technical_Literature",
    "Update_Design_Knowledge",
    "Apply_Current_Standards_When_Known"
  ],
  "proeth:description": "Newly developed severe weather design standards are published in technical literature, establishing updated parameters for structural design in severe weather regions. These standards represent a meaningful advancement beyond previously established design knowledge.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to or concurrent with Engineer A\u0027s design phase (exact timing unspecified, but before design completion)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "New Standards Published"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Event_Design_Incorporated_Into_Plans",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What does an engineer\u0027s professional seal ethically certify, and does that certification extend to currency with recently published standards?",
    "At this stage, what options remain available to prevent the eventual failure, and who bears responsibility for exercising them?",
    "How should the design review and approval process be structured to catch deficiencies arising from knowledge gaps rather than calculation errors?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences professional satisfaction at project milestone completion; no awareness of deficiency creates false confidence; client and project team feel progress and forward momentum; retrospectively, this moment is recognized as the point at which the deficiency became structurally embedded in the project",
  "proeth-scenario:ethicalImplications": "Highlights the ethical weight of professional certification; illustrates how procedural compliance (completing and releasing a design) can mask substantive non-compliance (failure to apply current standards); raises questions about the adequacy of self-certification models in engineering practice",
  "proeth-scenario:learningMoment": "The act of sealing and releasing plans is not merely administrative \u2014 it is a formal professional certification of competence. Students should understand that the engineer of record\u0027s signature represents an affirmation that the design meets current standards, making pre-release review obligations ethically and legally critical.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "building_owner_client": "Receives plans believed to represent competent, current engineering practice; unaware of latent deficiency",
    "contractor": "Will build in strict conformance with deficient plans, having no independent obligation to verify structural adequacy against current standards",
    "engineer_a": "Professional seal now attached to deficient design; accountability is formally established; window for low-cost correction is closing",
    "future_occupants_public": "Safety trajectory is now set toward eventual failure absent intervention"
  },
  "proeth:activatesConstraint": [
    "Construction_Fidelity_To_Design_Constraint",
    "Sealed_Document_Responsibility_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/74#Action_Release_Design_for_Construction",
  "proeth:causesStateChange": "Design is locked into official documents; Engineer A\u0027s professional seal implies certification of competent design; the substandard design parameters are now embedded in the construction pathway with no corrective mechanism triggered.",
  "proeth:createsObligation": [
    "Monitor_Construction_For_Design_Conformance",
    "Remain_Available_For_Design_Clarification",
    "Flag_Any_Discovered_Design_Deficiencies_Before_Construction_Proceeds"
  ],
  "proeth:description": "Engineer A\u0027s completed structural design \u2014 developed without awareness of the new severe weather standards \u2014 is formally incorporated into construction plans and specifications, committing the design to physical realization. This event marks the transition from design phase to construction-ready documentation.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "End of design phase, prior to construction commencement",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Design Incorporated Into Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Event_Building_Constructed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the completion of construction without incident (yet) suggest the design was acceptable, or does it simply reflect that the triggering weather event has not yet occurred?",
    "What role should building inspectors and permitting authorities play in verifying that designs conform to current published standards?",
    "How does the concept of \u0027latent defect\u0027 apply to engineering designs that do not conform to current standards but have not yet caused failure?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Project stakeholders experience completion satisfaction; Engineer A\u0027s professional role concludes with apparent success; building owner takes possession with confidence; no visible indicator of latent structural risk; retrospectively, this moment represents the full materialization of the ethical failure",
  "proeth-scenario:ethicalImplications": "Illustrates the temporal disconnect between ethical failure and visible consequence; demonstrates how systemic gaps in review processes allow deficient designs to reach completion; raises questions about the distribution of safety responsibility across the design-build-permit ecosystem",
  "proeth-scenario:learningMoment": "The completion of construction represents the point of no return for low-cost remediation. Students should recognize that ethical failures in the design phase compound through subsequent project phases, and that the cost \u2014 financial, human, and professional \u2014 of correction escalates dramatically once construction is complete.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "building_owner_client": "Takes ownership of asset with hidden structural vulnerability; financial and safety exposure now fully assumed",
    "contractor": "Construction obligations fulfilled; no ongoing liability absent design deficiency discovery",
    "engineer_a": "Professional involvement concludes; accountability for design is now fixed and permanent",
    "occupants_public": "Now inhabiting or using a structure with inadequate severe weather resistance; safety directly at risk"
  },
  "proeth:activatesConstraint": [
    "Occupant_Safety_Baseline_Constraint",
    "Post_Construction_Inspection_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/74#Action_Release_Design_for_Construction",
  "proeth:causesStateChange": "Deficient design is now physically instantiated; building enters service in a severe weather region without adequate structural parameters; the latent risk is now fully embedded in the built environment and will be triggered by the next severe weather event.",
  "proeth:createsObligation": [
    "Post_Construction_Inspection",
    "Ongoing_Monitoring_In_Severe_Weather_Region"
  ],
  "proeth:description": "The building is physically constructed in accordance with Engineer A\u0027s plans and specifications, materializing the structurally deficient design into a permanent built structure. Construction proceeds without identification of the design\u0027s non-conformance with current severe weather standards.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Post-design phase; construction period concluding prior to occupancy",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Building Constructed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Event_Severe_Weather_Event_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is the severe weather event a defense for Engineer A \u2014 i.e., can the damage be attributed to an \u0027act of nature\u0027 rather than professional negligence? Why or why not?",
    "How does the foreseeability of severe weather in the building\u0027s region affect the ethical analysis of Engineer A\u0027s design decisions?",
    "What is the difference between a proximate cause and a root cause in engineering failure analysis, and why does this distinction matter ethically?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Terror and danger for occupants during the event; shock and trauma for survivors; grief if casualties occur; alarm and urgency for emergency responders; dawning horror for Engineer A upon learning of the event; distress for building owner",
  "proeth-scenario:ethicalImplications": "Forces confrontation with the real-world consequences of abstract professional obligations; illustrates that the duty to apply current standards is not bureaucratic formalism but a direct mechanism for protecting human life; highlights the foreseeable harm doctrine in professional ethics",
  "proeth-scenario:learningMoment": "The severe weather event is the proximate cause of damage but not the root cause \u2014 the root cause is the design deficiency. Students must distinguish between the triggering event and the underlying ethical failure, and recognize that foreseeable environmental conditions in a known severe weather region are precisely what engineering standards are designed to address.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "building_owner_client": "Property damage, financial loss, potential liability to occupants, loss of use of asset",
    "emergency_responders": "Called to respond to structural emergency; their safety also at risk in unstable structure",
    "engineer_a": "The professional and ethical consequences of the design decision are now imminent; potential legal liability, license investigation, and reputational damage are triggered",
    "occupants_public": "Direct physical danger; potential injury, death, or displacement; psychological trauma",
    "professional_community": "Event will prompt scrutiny of design standards compliance and professional accountability"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Emergency_Response_Constraint",
    "Life_Safety_Immediate_Action"
  ],
  "proeth:causesStateChange": "Latent structural deficiency is activated; the building is subjected to loads exceeding its design capacity under current standards; the gap between designed performance and required performance is physically tested; conditions for structural damage are now fully present.",
  "proeth:createsObligation": [
    "Emergency_Evacuation_If_Occupied",
    "Immediate_Structural_Assessment",
    "Notify_Relevant_Authorities",
    "Preserve_Evidence_For_Investigation"
  ],
  "proeth:description": "A severe weather event strikes the building\u0027s location within one year of construction completion, subjecting the structure to the environmental loads for which it was inadequately designed. This exogenous event is the proximate trigger that converts the latent structural deficiency into active failure.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Within one year post-construction",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Severe Weather Event Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Event_Structural_Damage_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How does the post-failure confirmation that current standards would have prevented the damage affect the ethical evaluation of Engineer A\u0027s conduct during the design phase?",
    "Should Engineer A have anticipated that severe weather would occur within the building\u0027s service life, and how does this foreseeability affect ethical culpability?",
    "What obligations does Engineer A have now that damage has occurred \u2014 to the building owner, to affected occupants, to the profession, and to the public?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Shock, fear, and physical danger for occupants; grief and trauma for those injured or displaced; anger and betrayal felt by building owner toward engineering team; professional dread and guilt for Engineer A; public alarm about engineering accountability; media and regulatory scrutiny intensifies",
  "proeth-scenario:ethicalImplications": "The damage event is the ethical reckoning point \u2014 it transforms a potential violation (inadequate design) into an actual harm with real victims; it forces engagement with the consequentialist dimension of engineering ethics alongside duty-based obligations; it raises questions of proportional accountability when multiple parties (engineer, permitting authority, professional societies) contributed to conditions enabling the failure",
  "proeth-scenario:learningMoment": "Structural damage is the visible, undeniable consequence of the ethical failure that began with the decision not to review current technical literature. Students should trace the full causal chain from professional omission to human harm, understanding that engineering ethics is not abstract \u2014 it has direct, measurable consequences for real people.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "building_owner_client": "Significant financial loss from property damage; potential liability to occupants; loss of use; possible litigation against Engineer A",
    "engineer_a": "Faces potential loss of professional license, civil liability, disciplinary proceedings before engineering board, and lasting reputational damage; professional identity fundamentally challenged",
    "insurers": "Claims triggered; investigation into design adequacy and professional liability",
    "occupants_public": "Physical harm, displacement, psychological trauma, financial loss; trust in built environment shaken",
    "professional_community": "Case becomes a reference point for professional competency standards; heightened scrutiny of literature review practices; potential regulatory response"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Immediate_Structural_Assessment_Required",
    "Occupant_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/74#Action_Proceed_Without_Literature_Review__Design_Using_Es",
  "proeth:causesStateChange": "Building transitions from \u0027in service\u0027 to \u0027structurally compromised\u0027; human safety is immediately at risk; legal, regulatory, and professional accountability mechanisms are activated; post-failure investigation is now mandated.",
  "proeth:createsObligation": [
    "Immediate_Structural_Safety_Assessment",
    "Occupant_Evacuation_And_Safety",
    "Notify_Building_Official_And_Authorities",
    "Initiate_Failure_Investigation",
    "Preserve_Physical_Evidence"
  ],
  "proeth:description": "The building sustains significant structural damage as a direct result of the severe weather event acting upon an inadequately designed structural system. The damage is the materialized consequence of the design\u0027s non-conformance with current severe weather standards.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During or immediately following the severe weather event, within one year post-construction",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Structural Damage Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#Event_Post-Failure_Analysis_Completed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "The analysis finds that compliance with new standards would have prevented the failure. Does this conclusively establish that Engineer A acted unethically, or are there additional factors to consider?",
    "How should the engineering profession use post-failure analyses to improve both technical standards and ethical practice going forward?",
    "What weight should be given to the fact that Engineer A was unaware of the new standards \u2014 does subjective ignorance mitigate objective professional responsibility?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Forensic confirmation brings clarity but also finality to Engineer A\u0027s culpability; Engineer A may experience shame, regret, defensiveness, or a combination; building owner shifts from uncertainty to justified anger; affected occupants gain validation of their harm; professional community confronts a documented case of standards non-compliance with fatal consequences",
  "proeth-scenario:ethicalImplications": "The post-failure analysis transforms the ethical question from hypothetical to concrete; it establishes the counterfactual basis for culpability; it raises deep questions about the relationship between knowledge, foreseeability, and responsibility in professional practice; it also highlights the retrospective nature of ethical evaluation and the tension between judging conduct by standards known at the time versus standards that were available but unknown to the actor",
  "proeth-scenario:learningMoment": "The post-failure analysis is the evidentiary foundation of the ethical case. Students should understand that the counterfactual \u2014 \u0027would compliance have prevented the harm?\u0027 \u2014 is central to both legal liability and ethical culpability. The finding that compliance would have prevented the failure is not merely technical; it is the ethical verdict on the adequacy of Engineer A\u0027s professional practice.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "building_owner_client": "Has actionable basis for legal claims against Engineer A and potentially others in the design-build chain",
    "engineer_a": "Professional culpability is now formally documented; license revocation, civil liability, and professional censure become concrete rather than speculative; personal and professional identity crisis",
    "licensing_board": "Obligated to act on findings; professional disciplinary proceedings likely initiated",
    "occupants_public": "Findings provide basis for compensation claims; public trust in engineering accountability mechanisms either reinforced or undermined depending on subsequent professional response",
    "professional_community": "Case enters the body of professional ethics precedent; likely to be cited in future BER cases and educational contexts"
  },
  "proeth:activatesConstraint": [
    "Professional_Accountability_Constraint",
    "Regulatory_Reporting_Obligation",
    "Public_Disclosure_Constraint"
  ],
  "proeth:causesStateChange": "Causal chain from design omission to structural damage is formally established; Engineer A\u0027s professional conduct is now subject to definitive retrospective ethical and legal evaluation; the findings become the evidentiary basis for any disciplinary, legal, or professional proceedings.",
  "proeth:createsObligation": [
    "Report_Findings_To_Licensing_Authority",
    "Notify_Affected_Parties_Of_Findings",
    "Remediate_Or_Demolish_Damaged_Structure",
    "Engineer_A_Respond_To_Professional_Inquiry"
  ],
  "proeth:description": "A post-failure investigation and analysis determines that the structural damage was caused by the design\u0027s non-conformance with newly published severe weather design parameters, and further concludes that adherence to those parameters would have prevented the failure. This finding formally establishes the causal link between Engineer A\u0027s design decisions and the structural damage.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After structural damage event; prior to ethical discussion and retrospective evaluation",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Post-Failure Analysis Completed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#CausalChain_6c24f73e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A decided to proceed with the structural design project without first conducting a comprehensive literature review, resulting in a design developed without awareness of the new severe weather standards",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A decides to begin structural design without reviewing current technical literature, bypassing discovery of newly published severe weather standards",
      "proeth:element": "Proceed Without Literature Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A completes structural design based on previously known principles, unknowingly omitting compliance with new severe weather design requirements",
      "proeth:element": "Design Using Established Principles",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A releases the non-compliant design for incorporation into construction plans and specifications without identifying the gap in standards compliance",
      "proeth:element": "Release Design for Construction",
      "proeth:step": 3
    },
    {
      "proeth:description": "Building is physically constructed according to the deficient design, materializing the standards gap into the built structure",
      "proeth:element": "Building Constructed",
      "proeth:step": 4
    },
    {
      "proeth:description": "Severe weather event exposes the design deficiency, causing significant structural damage confirmed by post-failure analysis to result from the inadequate design",
      "proeth:element": "Structural Damage Occurs",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Proceed Without Literature Review",
  "proeth:counterfactual": "Had Engineer A conducted a literature review, the new severe weather standards would likely have been discovered and incorporated, potentially preventing or reducing structural damage when the weather event occurred",
  "proeth:effect": "Structural Damage Occurs",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s decision to skip literature review",
    "Existence of newly published severe weather standards",
    "Design proceeding without incorporation of current standards",
    "Severe weather event occurring within building\u0027s service life"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of skipped literature review + outdated design basis + severe weather event striking the structure"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#CausalChain_f8cb78fd",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Newly developed severe weather design standards are published in technical literature, establishing requirements that Engineer A\u0027s design \u2014 completed without awareness of these standards \u2014 failed to meet, contributing to structural damage when a severe weather event occurred",
  "proeth:causalSequence": [
    {
      "proeth:description": "Severe weather design standards are published, raising the threshold for compliant structural design before Engineer A begins work",
      "proeth:element": "New Standards Published",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A proceeds without discovering the new standards, creating a knowledge gap that propagates into the design",
      "proeth:element": "Proceed Without Literature Review",
      "proeth:step": 2
    },
    {
      "proeth:description": "Non-compliant design is embedded into construction documents, locking the deficiency into the project",
      "proeth:element": "Design Incorporated Into Plans",
      "proeth:step": 3
    },
    {
      "proeth:description": "A severe weather event strikes the building, applying loads that the new standards were specifically designed to address",
      "proeth:element": "Severe Weather Event Occurs",
      "proeth:step": 4
    },
    {
      "proeth:description": "The building sustains significant structural damage because its design did not account for the severe weather loads now required by current standards",
      "proeth:element": "Structural Damage Occurs",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "New Standards Published",
  "proeth:counterfactual": "If new standards had not been published prior to design commencement, Engineer A\u0027s design would have been consistent with prevailing standards and may not have been deficient; alternatively, if the severe weather event had not occurred, the deficiency may never have been exposed",
  "proeth:effect": "Structural Damage Occurs",
  "proeth:necessaryFactors": [
    "Publication of new standards establishing higher severe weather design thresholds",
    "Engineer A\u0027s failure to discover and apply those standards",
    "Severe weather event meeting or exceeding the threshold addressed by new standards",
    "Building constructed to the deficient design"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); standards-publishing body (contextual)",
  "proeth:sufficientFactors": [
    "New standards published but not consulted + design finalized and built + severe weather event occurring = structural inadequacy exposed and damage realized"
  ],
  "proeth:withinAgentControl": false
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#CausalChain_32498c32",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A allowed his completed structural design to be incorporated into the plans and specifications, which were then used to physically construct the building in accordance with those plans, materializing the design deficiency into the built environment",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A releases the structurally deficient design, authorizing its use in construction documents",
      "proeth:element": "Release Design for Construction",
      "proeth:step": 1
    },
    {
      "proeth:description": "The deficient design becomes the binding basis for construction, with no further engineering review",
      "proeth:element": "Design Incorporated Into Plans",
      "proeth:step": 2
    },
    {
      "proeth:description": "Contractors build the structure exactly as designed, embedding the severe weather design deficiency into the physical building",
      "proeth:element": "Building Constructed",
      "proeth:step": 3
    },
    {
      "proeth:description": "Severe weather applies loads the structure was not designed to withstand under current standards",
      "proeth:element": "Severe Weather Event Occurs",
      "proeth:step": 4
    },
    {
      "proeth:description": "The physically constructed deficiency is exposed, resulting in significant structural damage confirmed by post-failure analysis",
      "proeth:element": "Structural Damage Occurs",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Release Design for Construction",
  "proeth:counterfactual": "Had Engineer A withheld the design pending a standards compliance review, or had a reviewing authority rejected the design, the deficient building would not have been constructed and subsequent structural damage would not have occurred",
  "proeth:effect": "Building Constructed",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s affirmative decision to release the design",
    "Design containing deficiencies relative to current severe weather standards",
    "Absence of intervening review that would have caught the deficiency before construction",
    "Construction proceeding in accordance with released plans"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Release of deficient design + no corrective review + construction executed as designed = deficient building realized"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/74#",
    "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/74#CausalChain_163a08e3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A post-failure investigation and analysis determines that the structural damage was caused by the design\u0027s failure to meet the newly published severe weather standards, establishing a direct causal link between Engineer A\u0027s design decisions and the resulting harm",
  "proeth:causalSequence": [
    {
      "proeth:description": "Root volitional decision that initiated the causal chain by omitting discovery of current standards",
      "proeth:element": "Proceed Without Literature Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "Severe weather event causes damage to the deficiently designed and constructed building",
      "proeth:element": "Structural Damage Occurs",
      "proeth:step": 2
    },
    {
      "proeth:description": "Forensic investigation traces structural damage to design deficiency relative to published severe weather standards",
      "proeth:element": "Post-Failure Analysis Completed",
      "proeth:step": 3
    },
    {
      "proeth:description": "Analysis formally links Engineer A\u0027s failure to conduct literature review to the realized harm, establishing professional responsibility",
      "proeth:element": "Causal Attribution Established",
      "proeth:step": 4
    },
    {
      "proeth:description": "Attribution of responsibility triggers potential professional discipline, liability, and remediation obligations for Engineer A",
      "proeth:element": "Professional and Legal Consequences",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Post-Failure Analysis Completed",
  "proeth:counterfactual": "Without the post-failure analysis, the causal link between Engineer A\u0027s decision to skip the literature review and the structural damage would remain unconfirmed, potentially obscuring professional and legal responsibility",
  "proeth:effect": "Responsibility Attribution to Engineer A\u0027s Design Deficiency",
  "proeth:necessaryFactors": [
    "Structural damage event providing the subject of investigation",
    "Post-failure analysis methodology capable of identifying design deficiency as root cause",
    "Existence of published standards against which the design could be measured",
    "Documentation of Engineer A\u0027s design decisions and their basis"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineer A (underlying cause); investigating body (analysis execution)",
  "proeth:sufficientFactors": [
    "Occurrence of damage + forensic investigation + comparison against published standards = confirmed causal attribution of design deficiency to Engineer A\u0027s omission"
  ],
  "proeth:withinAgentControl": false
}