This page shows the pre-commit working store (the raw extraction under review). This case was committed to OntServe on 2026-07-25 14:27; the committed record differs by design (deduplication, typing, and agent binding are applied at commit). View the committed record
Overview
Provenance Draft

PASS 3: Temporal Dynamics

Case 88: Public Health, Safety, and Welfare–Climate Change Induced Conditions

32 entities 8 actions 3 events 8 causal chains 12 temporal relations
Timeline Overview
Action Event 11 sequenced markers
Development Project Initiation Before case events, project inception
Specialized Analysis Proposal During design, before public hearings
Ongoing Climate Change Ongoing, before and during the project
Conference Procedure Presentation Recent transportation agency conference, before Engineer A's judgment
Project Scope Acceptance Project inception
Flood Risk Judgment During design phase, after attending the conference
Client Directive Issuance Immediately after Engineer A's proposal
Client Discussion Engagement Recommended next step, after Client B's directive
Concern Documentation Proposal Conditional future step, if Client B remains unconvinced after discussion
Project Withdrawal Conditional final step, if Client B refuses both courses of action
Historical Dataset Shift Recent decades, ongoing
OWL-Time Temporal Structure 12 relations time: = w3.org/2006/time
transportation agency conference (presentation of hydraulic evaluation procedures) time:intervalBefore Engineer A's judgment about accelerated flooding
Client B engaging Engineer A time:intervalBefore Engineer A's design and permitting work
Engineer A's application of current local regulations (25-year storm) time:intervalDuring project design phase
Engineer A's proposal of the specialized hydrologic/hydraulic analysis time:intervalBefore project public hearings
Engineer A's proposal of the specialized analysis time:intervalBefore Client B's directive to proceed without the analysis
proposed project (upgraded tidal crossing) time:intervalBefore potential flood damage to twenty upstream homes
potential flood damage to upstream homes time:intervalDuring future high tides and storm surges
updating of local regulations and national codes for climate change time:intervalAfter current project design and permitting
engineers' assumption of stationary historical climate data time:intervalOverlaps recent decades of changing climate and weather patterns
Engineer A's discussion with Client B about the need for detailed evaluation time:intervalBefore Engineer A's proposal to document concerns in an engineering report
Client B's refusal of both proposed courses of action time:intervalBefore Engineer A's withdrawal from the project
specialized detailed analysis (if performed) time:intervalAfter regulatory authorities' request for the analysis
Extracted Actions (8)
Volitional professional decisions with intentions and ethical context

Description: Client B, a developer, decides to propose development of a health care facility requiring a significant upgrade of the access road crossing a tidal saltmarsh.

Temporal Marker: Before case events, project inception instant

Fluent Transitions:
Initiates (1)
  • Project Underway

Mental State: deliberate

Intended Outcome: Develop a health care facility with adequate access

Required Capabilities:
Development planning
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Development planning
  • initiates: Project Underway
Literal extractions (kept for synthesis)
  • description content: Client B, a developer, decides to propose development of a health care facility requiring a significant upgrade of the access road crossing a tidal saltmarsh.
  • hasAgent content: Client B
  • temporalMarker content: Before case events, project inception
  • eventRoleContext content: Developer
  • hasMentalState content: deliberate
  • intendedOutcome content: Develop a health care facility with adequate access
  • textReferences content: a developer who is proposing to develop a health care facility that requires a significant upgrade to the property’s access road that crosses a tidal saltmarsh
  • temporalExtent content: instant
  • temporalSequence content: 3
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Development_Project_Initiation",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.091019+00:00",
  "proeth:description": "Client B, a developer, decides to propose development of a health care facility requiring a significant upgrade of the access road crossing a tidal saltmarsh.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Developer",
  "proeth:hasAgent": "Client B",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Project Underway"
  ],
  "proeth:intendedOutcome": "Develop a health care facility with adequate access",
  "proeth:requiresCapability": [
    "Development planning"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Before case events, project inception",
  "proeth:temporalSequence": 3,
  "proeth:textReferences": [
    "a developer who is proposing to develop a health care facility that requires a significant upgrade to the property\u2019s access road that crosses a tidal saltmarsh"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Development Project Initiation"
}

Description: Engineer A accepts an engagement representing Client B covering design and local permitting of the roadway, including upgrading the tidal crossing from a small culvert to a small bridge.

Temporal Marker: Project inception instant

Fluent Transitions:
Initiates (1)
  • Engineer-Client Engagement

Mental State: deliberate

Intended Outcome: Provide design and permitting services for the roadway and tidal crossing upgrade

Obligation Engagement:
Fulfills (1)
  • Perform Services Within Scope for Client
Required Capabilities:
Roadway design Hydraulic design Local permitting
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Perform Services Within Scope for Client
  • requiresCapability: Roadway design; Hydraulic design; Local permitting
  • initiates: Engineer-Client Engagement
Literal extractions (kept for synthesis)
  • description content: Engineer A accepts an engagement representing Client B covering design and local permitting of the roadway, including upgrading the tidal crossing from a small culvert to a small bridge.
  • hasAgent content: Engineer A
  • temporalMarker content: Project inception
  • eventRoleContext content: Consulting Engineer
  • hasMentalState content: deliberate
  • intendedOutcome content: Provide design and permitting services for the roadway and tidal crossing upgrade
  • textReferences content: Engineer A’s scope includes design and local permitting of the roadway, including an upgrade of the tidal crossing from a small culvert to a small bridge, increasing its hydraulic capacity.
  • temporalExtent content: instant
  • temporalSequence content: 4
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Project_Scope_Acceptance",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.091176+00:00",
  "proeth:description": "Engineer A accepts an engagement representing Client B covering design and local permitting of the roadway, including upgrading the tidal crossing from a small culvert to a small bridge.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Consulting Engineer",
  "proeth:fulfillsObligation": [
    "Perform Services Within Scope for Client"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Engineer-Client Engagement"
  ],
  "proeth:intendedOutcome": "Provide design and permitting services for the roadway and tidal crossing upgrade",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Roadway design",
    "Hydraulic design",
    "Local permitting"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Project inception",
  "proeth:temporalSequence": 4,
  "proeth:textReferences": [
    "Engineer A\u2019s scope includes design and local permitting of the roadway, including an upgrade of the tidal crossing from a small culvert to a small bridge, increasing its hydraulic capacity."
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Project Scope Acceptance"
}

Description: Engineer A forms a professional judgment, based on hydraulic evaluation procedures from a recent transportation agency conference, that the project may cause some upstream homes to become uninhabitable a decade or more earlier than otherwise.

Temporal Marker: During design phase, after attending the conference instant

Fluent Transitions:
Initiates (1)
  • Identified Upstream Flood Risk

Mental State: deliberate professional judgment

Intended Outcome: Assess potential public impacts of the increased hydraulic capacity under changing climate conditions

Foreseen Unintended Effects:

  • Difficult questions at the project's public hearings
Obligation Engagement:
At stake (1)
  • Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Guided By Principles:
  • Hold Paramount Public Health, Safety, and Welfare
Required Capabilities:
Understanding of hydrology, hydraulics, and coastal modeling Engineering judgment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Hold Paramount Public Health, Safety, and Welfare
  • requiresCapability: Understanding of hydrology, hydraulics, and coastal modeling; Engineering judgment
  • initiates: Identified Upstream Flood Risk
  • raisesObligation: Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Literal extractions (kept for synthesis)
  • description content: Engineer A forms a professional judgment, based on hydraulic evaluation procedures from a recent transportation agency conference, that the project may cause some upstream homes to become uninhabitable a decade or more earlier than otherwise.
  • hasAgent content: Engineer A
  • temporalMarker content: During design phase, after attending the conference
  • eventRoleContext content: Consulting Engineer
  • hasMentalState content: deliberate professional judgment
  • intendedOutcome content: Assess potential public impacts of the increased hydraulic capacity under changing climate conditions
  • foreseenUnintendedEffects content: Difficult questions at the project's public hearings
  • textReferences content: It is Engineer A’s judgment, based on hydraulic evaluation procedures presented at a recent transportation agency conference, that the proposed project may result in some upstream homes becoming uninhabitable a decade or more earlier than would otherwise be the case.
  • temporalExtent content: instant
  • temporalSequence content: 6
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Flood_Risk_Judgment",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.091218+00:00",
  "proeth:description": "Engineer A forms a professional judgment, based on hydraulic evaluation procedures from a recent transportation agency conference, that the project may cause some upstream homes to become uninhabitable a decade or more earlier than otherwise.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Consulting Engineer",
  "proeth:foreseenUnintendedEffects": [
    "Difficult questions at the project\u0027s public hearings"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:guidedByPrinciple": [
    "Hold Paramount Public Health, Safety, and Welfare"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate professional judgment",
  "proeth:initiates": [
    "Identified Upstream Flood Risk"
  ],
  "proeth:intendedOutcome": "Assess potential public impacts of the increased hydraulic capacity under changing climate conditions",
  "proeth:raisesObligation": [
    "Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare"
  ],
  "proeth:requiresCapability": [
    "Understanding of hydrology, hydraulics, and coastal modeling",
    "Engineering judgment"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "During design phase, after attending the conference",
  "proeth:temporalSequence": 6,
  "proeth:textReferences": [
    "It is Engineer A\u2019s judgment, based on hydraulic evaluation procedures presented at a recent transportation agency conference, that the proposed project may result in some upstream homes becoming uninhabitable a decade or more earlier than would otherwise be the case."
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Flood Risk Judgment"
}

Description: Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict flood damage to twenty upstream homes from sea level rise and the increased hydraulic capacity of the crossing.

Temporal Marker: During design, before public hearings instant

Fluent Transitions:
Initiates (1)
  • Analysis Proposal Pending Client Decision

Mental State: deliberate

Intended Outcome: Quantify the extent of future flood damage to the upstream neighborhood and prepare for public hearing questions

Foreseen Unintended Effects:

  • Added cost and complexity to the project
Obligation Engagement:
At stake (1)
  • Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Guided By Principles:
  • Hold Paramount Public Health, Safety, and Welfare
Required Capabilities:
Sufficient understanding of hydrology, hydraulics, and coastal modeling Judgment on when specialized evaluation is needed
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Hold Paramount Public Health, Safety, and Welfare
  • requiresCapability: Sufficient understanding of hydrology, hydraulics, and coastal modeling; Judgment on when specialized evaluation is needed
  • initiates: Analysis Proposal Pending Client Decision
  • raisesObligation: Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Literal extractions (kept for synthesis)
  • description content: Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict flood damage to twenty upstream homes from sea level rise and the increased hydraulic capacity of the crossing.
  • hasAgent content: Engineer A
  • temporalMarker content: During design, before public hearings
  • eventRoleContext content: Consulting Engineer
  • hasMentalState content: deliberate
  • intendedOutcome content: Quantify the extent of future flood damage to the upstream neighborhood and prepare for public hearing questions
  • foreseenUnintendedEffects content: Added cost and complexity to the project
  • textReferences content: Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict the extent to which sea level rise and the increased hydraulic capacity of the tidal crossing will result in flood damage to a neighborhood of twenty upstream homes during future high tides and storm surges
  • temporalExtent content: instant
  • temporalSequence content: 7
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Specialized_Analysis_Proposal",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.091251+00:00",
  "proeth:description": "Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict flood damage to twenty upstream homes from sea level rise and the increased hydraulic capacity of the crossing.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Consulting Engineer",
  "proeth:foreseenUnintendedEffects": [
    "Added cost and complexity to the project"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:guidedByPrinciple": [
    "Hold Paramount Public Health, Safety, and Welfare"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Analysis Proposal Pending Client Decision"
  ],
  "proeth:intendedOutcome": "Quantify the extent of future flood damage to the upstream neighborhood and prepare for public hearing questions",
  "proeth:raisesObligation": [
    "Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare"
  ],
  "proeth:requiresCapability": [
    "Sufficient understanding of hydrology, hydraulics, and coastal modeling",
    "Judgment on when specialized evaluation is needed"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "During design, before public hearings",
  "proeth:temporalSequence": 7,
  "proeth:textReferences": [
    "Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict the extent to which sea level rise and the increased hydraulic capacity of the tidal crossing will result in flood damage to a neighborhood of twenty upstream homes during future high tides and storm surges"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Specialized Analysis Proposal"
}

Description: Client B directs Engineer A to proceed with the project without the costly analysis unless and until regulatory authorities request such an analysis.

Temporal Marker: Immediately after Engineer A's proposal instant

Fluent Transitions:
Initiates (2)
  • Directive to Proceed Without Analysis
  • Ethical Conflict Between Client Directive and Public Welfare
Terminates (1)
  • Analysis Proposal Pending Client Decision

Mental State: deliberate

Intended Outcome: Avoid the cost of the specialized analysis and keep the project moving

Foreseen Unintended Effects:

  • Potential flood impacts to upstream homes remain unevaluated
Required Capabilities:
Project cost and schedule management
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Project cost and schedule management
  • initiates: Directive to Proceed Without Analysis; Ethical Conflict Between Client Directive and Public Welfare
  • terminates: Analysis Proposal Pending Client Decision
Literal extractions (kept for synthesis)
  • description content: Client B directs Engineer A to proceed with the project without the costly analysis unless and until regulatory authorities request such an analysis.
  • hasAgent content: Client B
  • temporalMarker content: Immediately after Engineer A's proposal
  • eventRoleContext content: Developer
  • hasMentalState content: deliberate
  • intendedOutcome content: Avoid the cost of the specialized analysis and keep the project moving
  • foreseenUnintendedEffects content: Potential flood impacts to upstream homes remain unevaluated
  • textReferences content: Client B directs Engineer A to proceed without the costly analysis unless and until such an analysis is requested by the applicable regulatory authorities.
  • temporalExtent content: instant
  • temporalSequence content: 8
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Client_Directive_Issuance",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.091954+00:00",
  "proeth:description": "Client B directs Engineer A to proceed with the project without the costly analysis unless and until regulatory authorities request such an analysis.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Developer",
  "proeth:foreseenUnintendedEffects": [
    "Potential flood impacts to upstream homes remain unevaluated"
  ],
  "proeth:hasAgent": "Client B",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Directive to Proceed Without Analysis",
    "Ethical Conflict Between Client Directive and Public Welfare"
  ],
  "proeth:intendedOutcome": "Avoid the cost of the specialized analysis and keep the project moving",
  "proeth:requiresCapability": [
    "Project cost and schedule management"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Immediately after Engineer A\u0027s proposal",
  "proeth:temporalSequence": 8,
  "proeth:terminates": [
    "Analysis Proposal Pending Client Decision"
  ],
  "proeth:textReferences": [
    "Client B directs Engineer A to proceed without the costly analysis unless and until such an analysis is requested by the applicable regulatory authorities."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Client Directive Issuance"
}

Description: Prescribed next step in which Engineer A engages Client B in discussions about the need for the detailed evaluation, disclosure of potential impacts on the public, mitigation alternatives, and the risk to Client B of not evaluating the impacts.

Temporal Marker: Recommended next step, after Client B's directive interval

Fluent Transitions:
Initiates (1)
  • Client Deliberation on Evaluation and Disclosure

Mental State: deliberate

Intended Outcome: Persuade Client B of the need for the detailed evaluation and disclosure of potential impacts

Foreseen Unintended Effects:

  • Possible strain on the client relationship
Obligation Engagement:
At stake (1)
  • Hold Paramount the Protection of Public Health, Safety, and Welfare
Fulfills (1)
  • Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Guided By Principles:
  • Hold Paramount Public Health, Safety, and Welfare
Required Capabilities:
Client communication Understanding of hydrology, hydraulics, and coastal modeling
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
  • guidedByPrinciple: Hold Paramount Public Health, Safety, and Welfare
  • requiresCapability: Client communication; Understanding of hydrology, hydraulics, and coastal modeling
  • initiates: Client Deliberation on Evaluation and Disclosure
  • raisesObligation: Hold Paramount the Protection of Public Health, Safety, and Welfare
Literal extractions (kept for synthesis)
  • description content: Prescribed next step in which Engineer A engages Client B in discussions about the need for the detailed evaluation, disclosure of potential impacts on the public, mitigation alternatives, and the risk to Client B of not evaluating the impacts.
  • hasAgent content: Engineer A
  • temporalMarker content: Recommended next step, after Client B's directive
  • eventRoleContext content: Consulting Engineer
  • hasMentalState content: deliberate
  • intendedOutcome content: Persuade Client B of the need for the detailed evaluation and disclosure of potential impacts
  • foreseenUnintendedEffects content: Possible strain on the client relationship
  • textReferences content: Engineer A should engage Client B in discussions about the need for the detailed evaluation and disclosure of the potential impacts on the public and alternatives for the project to mitigate those impacts, and the potential risk to Client B of not evaluating the potential impacts.
  • temporalExtent content: interval
  • temporalSequence content: 9
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Client_Discussion_Engagement",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.092014+00:00",
  "proeth:description": "Prescribed next step in which Engineer A engages Client B in discussions about the need for the detailed evaluation, disclosure of potential impacts on the public, mitigation alternatives, and the risk to Client B of not evaluating the impacts.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Consulting Engineer",
  "proeth:foreseenUnintendedEffects": [
    "Possible strain on the client relationship"
  ],
  "proeth:fulfillsObligation": [
    "Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare"
  ],
  "proeth:guidedByPrinciple": [
    "Hold Paramount Public Health, Safety, and Welfare"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Client Deliberation on Evaluation and Disclosure"
  ],
  "proeth:intendedOutcome": "Persuade Client B of the need for the detailed evaluation and disclosure of potential impacts",
  "proeth:raisesObligation": [
    "Hold Paramount the Protection of Public Health, Safety, and Welfare"
  ],
  "proeth:requiresCapability": [
    "Client communication",
    "Understanding of hydrology, hydraulics, and coastal modeling"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "Recommended next step, after Client B\u0027s directive",
  "proeth:temporalSequence": 9,
  "proeth:textReferences": [
    "Engineer A should engage Client B in discussions about the need for the detailed evaluation and disclosure of the potential impacts on the public and alternatives for the project to mitigate those impacts, and the potential risk to Client B of not evaluating the potential impacts."
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Client Discussion Engagement"
}

Description: Prescribed fallback in which Engineer A proposes to Client B that the potential concern needing more detailed evaluation be provided in an engineering report for consideration by regulatory agencies and the public.

Temporal Marker: Conditional future step, if Client B remains unconvinced after discussion instant

Fluent Transitions:
Initiates (1)
  • Public Safety Concern Disclosed for Regulatory Consideration

Mental State: deliberate

Intended Outcome: Disclose the potential flood concern to regulators and the public through an engineering report

Foreseen Unintended Effects:

  • Public and regulatory scrutiny of the project
Obligation Engagement:
At stake (1)
  • Hold Paramount the Protection of Public Health, Safety, and Welfare
Guided By Principles:
  • Hold Paramount Public Health, Safety, and Welfare
Required Capabilities:
Engineering report preparation Regulatory communication
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Hold Paramount Public Health, Safety, and Welfare
  • requiresCapability: Engineering report preparation; Regulatory communication
  • initiates: Public Safety Concern Disclosed for Regulatory Consideration
  • raisesObligation: Hold Paramount the Protection of Public Health, Safety, and Welfare
Literal extractions (kept for synthesis)
  • description content: Prescribed fallback in which Engineer A proposes to Client B that the potential concern needing more detailed evaluation be provided in an engineering report for consideration by regulatory agencies and the public.
  • hasAgent content: Engineer A
  • temporalMarker content: Conditional future step, if Client B remains unconvinced after discussion
  • eventRoleContext content: Consulting Engineer
  • hasMentalState content: deliberate
  • intendedOutcome content: Disclose the potential flood concern to regulators and the public through an engineering report
  • foreseenUnintendedEffects content: Public and regulatory scrutiny of the project
  • textReferences content: Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public
  • temporalExtent content: instant
  • temporalSequence content: 10
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Concern_Documentation_Proposal",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.092045+00:00",
  "proeth:description": "Prescribed fallback in which Engineer A proposes to Client B that the potential concern needing more detailed evaluation be provided in an engineering report for consideration by regulatory agencies and the public.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Consulting Engineer",
  "proeth:foreseenUnintendedEffects": [
    "Public and regulatory scrutiny of the project"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:guidedByPrinciple": [
    "Hold Paramount Public Health, Safety, and Welfare"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Public Safety Concern Disclosed for Regulatory Consideration"
  ],
  "proeth:intendedOutcome": "Disclose the potential flood concern to regulators and the public through an engineering report",
  "proeth:raisesObligation": [
    "Hold Paramount the Protection of Public Health, Safety, and Welfare"
  ],
  "proeth:requiresCapability": [
    "Engineering report preparation",
    "Regulatory communication"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Conditional future step, if Client B remains unconvinced after discussion",
  "proeth:temporalSequence": 10,
  "proeth:textReferences": [
    "Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Concern Documentation Proposal"
}

Description: Prescribed final step in which Engineer A withdraws from the project if Client B refuses both the detailed evaluation and the disclosure of concerns in an engineering report.

Temporal Marker: Conditional final step, if Client B refuses both courses of action instant

Fluent Transitions:
Initiates (1)
  • Engineer Disengaged from Project
Terminates (2)
  • Engineer-Client Engagement
  • Ethical Conflict Between Client Directive and Public Welfare

Mental State: deliberate

Intended Outcome: Avoid participating in a project that proceeds without evaluation or disclosure of potential public impacts

Foreseen Unintended Effects:

  • Loss of the engagement with Client B
  • Project may continue with another engineer
Obligation Engagement:
Fulfills (1)
  • Hold Paramount the Protection of Public Health, Safety, and Welfare
Guided By Principles:
  • Hold Paramount Public Health, Safety, and Welfare
Required Capabilities:
Professional judgment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Hold Paramount the Protection of Public Health, Safety, and Welfare
  • guidedByPrinciple: Hold Paramount Public Health, Safety, and Welfare
  • requiresCapability: Professional judgment
  • initiates: Engineer Disengaged from Project
  • terminates: Engineer-Client Engagement; Ethical Conflict Between Client Directive and Public Welfare
Literal extractions (kept for synthesis)
  • description content: Prescribed final step in which Engineer A withdraws from the project if Client B refuses both the detailed evaluation and the disclosure of concerns in an engineering report.
  • hasAgent content: Engineer A
  • temporalMarker content: Conditional final step, if Client B refuses both courses of action
  • eventRoleContext content: Consulting Engineer
  • hasMentalState content: deliberate
  • intendedOutcome content: Avoid participating in a project that proceeds without evaluation or disclosure of potential public impacts
  • foreseenUnintendedEffects content: Loss of the engagement with Client B; Project may continue with another engineer
  • textReferences content: Failing agreement by Client B to t either of these courses of action the BER believes that Engineer A should withdraw from the project.
  • temporalExtent content: instant
  • temporalSequence content: 11
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Action_Project_Withdrawal",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T16:18:09.092070+00:00",
  "proeth:description": "Prescribed final step in which Engineer A withdraws from the project if Client B refuses both the detailed evaluation and the disclosure of concerns in an engineering report.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "Consulting Engineer",
  "proeth:foreseenUnintendedEffects": [
    "Loss of the engagement with Client B",
    "Project may continue with another engineer"
  ],
  "proeth:fulfillsObligation": [
    "Hold Paramount the Protection of Public Health, Safety, and Welfare"
  ],
  "proeth:guidedByPrinciple": [
    "Hold Paramount Public Health, Safety, and Welfare"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Engineer Disengaged from Project"
  ],
  "proeth:intendedOutcome": "Avoid participating in a project that proceeds without evaluation or disclosure of potential public impacts",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Professional judgment"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Conditional final step, if Client B refuses both courses of action",
  "proeth:temporalSequence": 11,
  "proeth:terminates": [
    "Engineer-Client Engagement",
    "Ethical Conflict Between Client Directive and Public Welfare"
  ],
  "proeth:textReferences": [
    "Failing agreement by Client B to t either of these courses of action the BER believes that Engineer A should withdraw from the project."
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Project Withdrawal"
}
Extracted Events (3)
Occurrences that trigger ethical considerations and state changes

Description: Continuing changes in climate and weather patterns, including sea level rise and changes in precipitation intensities and recurrence intervals, form the background occurrence affecting the tidal crossing design.

Temporal Marker: Ongoing, before and during the project interval

Fluent Transitions:
Initiates (2)
  • Changing Climate and Weather Conditions
  • Sea Level Rise Condition
Terminates (1)
  • Reliability of Historical Climate Assumptions
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Changing Climate and Weather Conditions; Sea Level Rise Condition
  • terminates: Reliability of Historical Climate Assumptions
Literal extractions (kept for synthesis)
  • description content: Continuing changes in climate and weather patterns, including sea level rise and changes in precipitation intensities and recurrence intervals, form the background occurrence affecting the tidal crossing design.
  • temporalMarker content: Ongoing, before and during the project
  • textReferences content: effects of sea level rise and changes in precipitation intensities and recurrence intervals effected by on-going climate change; In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change.
  • eventType content: exogenous
  • temporalExtent content: interval
  • temporalSequence content: 1
  • confidence assessment: 0.9
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Event_Ongoing_Climate_Change",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T16:18:09.092175+00:00",
  "proeth:confidence": "0.9",
  "proeth:description": "Continuing changes in climate and weather patterns, including sea level rise and changes in precipitation intensities and recurrence intervals, form the background occurrence affecting the tidal crossing design.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "exogenous",
  "proeth:initiates": [
    "Changing Climate and Weather Conditions",
    "Sea Level Rise Condition"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "Ongoing, before and during the project",
  "proeth:temporalSequence": 1,
  "proeth:terminates": [
    "Reliability of Historical Climate Assumptions"
  ],
  "proeth:textReferences": [
    "effects of sea level rise and changes in precipitation intensities and recurrence intervals effected by on-going climate change",
    "In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change."
  ],
  "rdfs:label": "Ongoing Climate Change"
}

Description: As climate and weather data are updated in recent decades, the historical dataset itself changes, making climate and weather patterns a moving target for design assumptions rather than a fixed baseline.

Temporal Marker: Recent decades, ongoing interval

Fluent Transitions:
Initiates (1)
  • Climate Data Moving Target Condition
Terminates (1)
  • Fixed Historical Baseline Condition
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Climate Data Moving Target Condition
  • terminates: Fixed Historical Baseline Condition
Literal extractions (kept for synthesis)
  • description content: As climate and weather data are updated in recent decades, the historical dataset itself changes, making climate and weather patterns a moving target for design assumptions rather than a fixed baseline.
  • temporalMarker content: Recent decades, ongoing
  • textReferences content: In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change.; This necessitates that climate and weather patterns be addressed not as fixed by historical patterns but rather recognized as a “moving target.”
  • eventType content: automatic
  • temporalExtent content: interval
  • temporalSequence content: 2
  • confidence assessment: 0.8
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Event_Historical_Dataset_Shift",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T16:18:09.092235+00:00",
  "proeth:confidence": "0.8",
  "proeth:description": "As climate and weather data are updated in recent decades, the historical dataset itself changes, making climate and weather patterns a moving target for design assumptions rather than a fixed baseline.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventType": "automatic",
  "proeth:initiates": [
    "Climate Data Moving Target Condition"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "Recent decades, ongoing",
  "proeth:temporalSequence": 2,
  "proeth:terminates": [
    "Fixed Historical Baseline Condition"
  ],
  "proeth:textReferences": [
    "In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change.",
    "This necessitates that climate and weather patterns be addressed not as fixed by historical patterns but rather recognized as a \u201cmoving target.\u201d"
  ],
  "rdfs:label": "Historical Dataset Shift"
}

Description: Hydraulic evaluation procedures were presented at a recent transportation agency conference, providing the technical basis for Engineer A's later judgment about accelerated flooding of upstream homes.

Temporal Marker: Recent transportation agency conference, before Engineer A's judgment instant

Fluent Transitions:
Initiates (1)
  • Engineer Awareness of Advanced Hydraulic Evaluation Procedures
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Engineer Awareness of Advanced Hydraulic Evaluation Procedures
Literal extractions (kept for synthesis)
  • description content: Hydraulic evaluation procedures were presented at a recent transportation agency conference, providing the technical basis for Engineer A's later judgment about accelerated flooding of upstream homes.
  • temporalMarker content: Recent transportation agency conference, before Engineer A's judgment
  • textReferences content: based on hydraulic evaluation procedures presented at a recent transportation agency conference
  • eventType content: exogenous
  • temporalExtent content: instant
  • temporalSequence content: 5
  • confidence assessment: 0.85
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "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/ontology/case/88#Event_Conference_Procedure_Presentation",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T16:18:09.092211+00:00",
  "proeth:confidence": "0.85",
  "proeth:description": "Hydraulic evaluation procedures were presented at a recent transportation agency conference, providing the technical basis for Engineer A\u0027s later judgment about accelerated flooding of upstream homes.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "exogenous",
  "proeth:initiates": [
    "Engineer Awareness of Advanced Hydraulic Evaluation Procedures"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Recent transportation agency conference, before Engineer A\u0027s judgment",
  "proeth:temporalSequence": 5,
  "proeth:textReferences": [
    "based on hydraulic evaluation procedures presented at a recent transportation agency conference"
  ],
  "rdfs:label": "Conference Procedure Presentation"
}
Causal Chains (8)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: Engineer A is a consulting engineer representing Client B, a developer who is proposing to develop a health care facility that requires a significant upgrade to the property’s access road that crosses a tidal saltmarsh.

Necessary Factors (NESS):
  • Client B's decision to propose the health care facility development
  • Need for a significant access road upgrade crossing a tidal saltmarsh
  • Availability of Engineer A as a consulting engineer willing to take the engagement
Sufficient Factors:
  • Client B's project proposal requiring design and permitting services combined with Engineer A's agreement to represent Client B
Counterfactual Test: Without Client B's decision to propose the development, there would have been no roadway/tidal crossing engagement for Engineer A to accept
Responsibility Attribution:

Agent: Client B (developer)
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Development Project Initiation
    Client B proposes a health care facility requiring a significant access road upgrade across a tidal saltmarsh
  2. Engagement of Consulting Engineer
    Client B retains Engineer A to represent the project
  3. Project Scope Acceptance
    Engineer A accepts scope covering design and local permitting of the roadway, including upgrading the culvert to a bridge with increased hydraulic capacity
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Development Project Initiation
  • effect: Project Scope Acceptance
  • responsibleAgent: Client B (developer)
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer A is a consulting engineer representing Client B, a developer who is proposing to develop a health care facility that requires a significant upgrade to the property’s access road that crosses a tidal saltmarsh.
  • necessaryFactors content: Client B's decision to propose the health care facility development; Need for a significant access road upgrade crossing a tidal saltmarsh; Availability of Engineer A as a consulting engineer willing to take the engagement
  • sufficientFactors content: Client B's project proposal requiring design and permitting services combined with Engineer A's agreement to represent Client B
  • counterfactual content: Without Client B's decision to propose the development, there would have been no roadway/tidal crossing engagement for Engineer A to accept
  • agentKnowledge content: Client B knew the property access required crossing a tidal saltmarsh and would need a significant road upgrade
  • interveningFactors content: Local development regulations requiring design for a 25-year fresh-water storm
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Development Project Initiation', 'proeth:description': 'Client B proposes a health care facility requiring a significant access road upgrade across a tidal saltmarsh'}; {'proeth:step': 2, 'proeth:element': 'Engagement of Consulting Engineer', 'proeth:description': 'Client B retains Engineer A to represent the project'}; {'proeth:step': 3, 'proeth:element': 'Project Scope Acceptance', 'proeth:description': 'Engineer A accepts scope covering design and local permitting of the roadway, including upgrading the culvert to a bridge with increased hydraulic capacity'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_1",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092288+00:00",
  "proeth:agentKnowledge": "Client B knew the property access required crossing a tidal saltmarsh and would need a significant road upgrade",
  "proeth:causalLanguage": "Engineer A is a consulting engineer representing Client B, a developer who is proposing to develop a health care facility that requires a significant upgrade to the property\u2019s access road that crosses a tidal saltmarsh.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client B proposes a health care facility requiring a significant access road upgrade across a tidal saltmarsh",
      "proeth:element": "Development Project Initiation",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client B retains Engineer A to represent the project",
      "proeth:element": "Engagement of Consulting Engineer",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A accepts scope covering design and local permitting of the roadway, including upgrading the culvert to a bridge with increased hydraulic capacity",
      "proeth:element": "Project Scope Acceptance",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Development Project Initiation",
  "proeth:counterfactual": "Without Client B\u0027s decision to propose the development, there would have been no roadway/tidal crossing engagement for Engineer A to accept",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Project Scope Acceptance",
  "proeth:interveningFactors": [
    "Local development regulations requiring design for a 25-year fresh-water storm"
  ],
  "proeth:necessaryFactors": [
    "Client B\u0027s decision to propose the health care facility development",
    "Need for a significant access road upgrade crossing a tidal saltmarsh",
    "Availability of Engineer A as a consulting engineer willing to take the engagement"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Client B (developer)",
  "proeth:sufficientFactors": [
    "Client B\u0027s project proposal requiring design and permitting services combined with Engineer A\u0027s agreement to represent Client B"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change. This necessitates that climate and weather patterns be addressed not as fixed by historical patterns but rather recognized as a “moving target.”

Necessary Factors (NESS):
  • Continuing changes in climate and weather patterns including sea level rise
  • Ongoing collection and updating of climate and weather data
Sufficient Factors:
  • Persistent climate change combined with periodic dataset updates renders the historical record a moving target
Counterfactual Test: Without ongoing climate change, updated historical data would remain consistent with prior data and the dataset would not shift
Responsibility Attribution:

Agent: No individual agent (natural/systemic phenomenon)
Type: indirect
Within Agent Control: No

Causal Sequence:
  1. Ongoing Climate Change
    Sea level rise and changes in precipitation intensities and recurrence intervals continue
  2. Data Updates
    Climate and weather data are updated in recent decades
  3. Historical Dataset Shift
    The historical dataset itself changes, making it a 'moving target' rather than a fixed baseline
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Ongoing Climate Change
  • effect: Historical Dataset Shift
  • responsibleAgent: No individual agent (natural/systemic phenomenon)
Literal extractions (kept for synthesis)
  • causalLanguage content: In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change. This necessitates that climate and weather patterns be addressed not as fixed by historical patterns but rather recognized as a “moving target.”
  • necessaryFactors content: Continuing changes in climate and weather patterns including sea level rise; Ongoing collection and updating of climate and weather data
  • sufficientFactors content: Persistent climate change combined with periodic dataset updates renders the historical record a moving target
  • counterfactual content: Without ongoing climate change, updated historical data would remain consistent with prior data and the dataset would not shift
  • agentKnowledge content: The engineering profession is increasingly aware that historical climate assumptions no longer hold
  • interveningFactors content: Lag in updating national design codes and local development regulations
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Ongoing Climate Change', 'proeth:description': 'Sea level rise and changes in precipitation intensities and recurrence intervals continue'}; {'proeth:step': 2, 'proeth:element': 'Data Updates', 'proeth:description': 'Climate and weather data are updated in recent decades'}; {'proeth:step': 3, 'proeth:element': 'Historical Dataset Shift', 'proeth:description': "The historical dataset itself changes, making it a 'moving target' rather than a fixed baseline"}
  • responsibilityType assessment: indirect
  • withinAgentControl assessment: False
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_2",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092320+00:00",
  "proeth:agentKnowledge": "The engineering profession is increasingly aware that historical climate assumptions no longer hold",
  "proeth:causalLanguage": "In recent decades, as climate and weather data are updated, the historical dataset changes as climate and weather patterns continue to change. This necessitates that climate and weather patterns be addressed not as fixed by historical patterns but rather recognized as a \u201cmoving target.\u201d",
  "proeth:causalSequence": [
    {
      "proeth:description": "Sea level rise and changes in precipitation intensities and recurrence intervals continue",
      "proeth:element": "Ongoing Climate Change",
      "proeth:step": 1
    },
    {
      "proeth:description": "Climate and weather data are updated in recent decades",
      "proeth:element": "Data Updates",
      "proeth:step": 2
    },
    {
      "proeth:description": "The historical dataset itself changes, making it a \u0027moving target\u0027 rather than a fixed baseline",
      "proeth:element": "Historical Dataset Shift",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Ongoing Climate Change",
  "proeth:counterfactual": "Without ongoing climate change, updated historical data would remain consistent with prior data and the dataset would not shift",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Historical Dataset Shift",
  "proeth:interveningFactors": [
    "Lag in updating national design codes and local development regulations"
  ],
  "proeth:necessaryFactors": [
    "Continuing changes in climate and weather patterns including sea level rise",
    "Ongoing collection and updating of climate and weather data"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "No individual agent (natural/systemic phenomenon)",
  "proeth:sufficientFactors": [
    "Persistent climate change combined with periodic dataset updates renders the historical record a moving target"
  ],
  "proeth:withinAgentControl": false
}

Causal Language: It is Engineer A’s judgment, based on hydraulic evaluation procedures presented at a recent transportation agency conference, that the proposed project may result in some upstream homes becoming uninhabitable a decade or more earlier than would otherwise be the case.

Necessary Factors (NESS):
  • Presentation of hydraulic evaluation procedures at the transportation agency conference
  • Engineer A's sufficient understanding of hydrology, hydraulics, and coastal issues to apply the procedures
  • The project's proposed increase in hydraulic capacity of the tidal crossing
Sufficient Factors:
  • Exposure to the new evaluation procedures combined with Engineer A's technical competence and knowledge of the project's tidal crossing upgrade
Counterfactual Test: Without the conference procedures, Engineer A may not have possessed the analytical basis to judge that upstream homes could become uninhabitable a decade or more earlier
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Conference Procedure Presentation
    Hydraulic evaluation procedures presented at a recent transportation agency conference
  2. Application to Project Conditions
    Engineer A applies the procedures to the tidal crossing upgrade with increased hydraulic capacity under sea level rise
  3. Flood Risk Judgment
    Engineer A judges that upstream homes may become uninhabitable a decade or more earlier than otherwise
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Conference Procedure Presentation
  • effect: Flood Risk Judgment
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: It is Engineer A’s judgment, based on hydraulic evaluation procedures presented at a recent transportation agency conference, that the proposed project may result in some upstream homes becoming uninhabitable a decade or more earlier than would otherwise be the case.
  • necessaryFactors content: Presentation of hydraulic evaluation procedures at the transportation agency conference; Engineer A's sufficient understanding of hydrology, hydraulics, and coastal issues to apply the procedures; The project's proposed increase in hydraulic capacity of the tidal crossing
  • sufficientFactors content: Exposure to the new evaluation procedures combined with Engineer A's technical competence and knowledge of the project's tidal crossing upgrade
  • counterfactual content: Without the conference procedures, Engineer A may not have possessed the analytical basis to judge that upstream homes could become uninhabitable a decade or more earlier
  • agentKnowledge content: Engineer A had sufficient understanding of hydrology, hydraulics, and coastal modeling to form a reasonable judgment about flooding potential
  • interveningFactors content: Ongoing climate change and sea level rise; Regulations not yet updated to reflect changing conditions
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Conference Procedure Presentation', 'proeth:description': 'Hydraulic evaluation procedures presented at a recent transportation agency conference'}; {'proeth:step': 2, 'proeth:element': 'Application to Project Conditions', 'proeth:description': 'Engineer A applies the procedures to the tidal crossing upgrade with increased hydraulic capacity under sea level rise'}; {'proeth:step': 3, 'proeth:element': 'Flood Risk Judgment', 'proeth:description': 'Engineer A judges that upstream homes may become uninhabitable a decade or more earlier than otherwise'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_3",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092344+00:00",
  "proeth:agentKnowledge": "Engineer A had sufficient understanding of hydrology, hydraulics, and coastal modeling to form a reasonable judgment about flooding potential",
  "proeth:causalLanguage": "It is Engineer A\u2019s judgment, based on hydraulic evaluation procedures presented at a recent transportation agency conference, that the proposed project may result in some upstream homes becoming uninhabitable a decade or more earlier than would otherwise be the case.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Hydraulic evaluation procedures presented at a recent transportation agency conference",
      "proeth:element": "Conference Procedure Presentation",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A applies the procedures to the tidal crossing upgrade with increased hydraulic capacity under sea level rise",
      "proeth:element": "Application to Project Conditions",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A judges that upstream homes may become uninhabitable a decade or more earlier than otherwise",
      "proeth:element": "Flood Risk Judgment",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Conference Procedure Presentation",
  "proeth:counterfactual": "Without the conference procedures, Engineer A may not have possessed the analytical basis to judge that upstream homes could become uninhabitable a decade or more earlier",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Flood Risk Judgment",
  "proeth:interveningFactors": [
    "Ongoing climate change and sea level rise",
    "Regulations not yet updated to reflect changing conditions"
  ],
  "proeth:necessaryFactors": [
    "Presentation of hydraulic evaluation procedures at the transportation agency conference",
    "Engineer A\u0027s sufficient understanding of hydrology, hydraulics, and coastal issues to apply the procedures",
    "The project\u0027s proposed increase in hydraulic capacity of the tidal crossing"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Exposure to the new evaluation procedures combined with Engineer A\u0027s technical competence and knowledge of the project\u0027s tidal crossing upgrade"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict the extent to which sea level rise and the increased hydraulic capacity of the tidal crossing will result in flood damage to a neighborhood of twenty upstream homes during future high tides and storm surges, anticipating this to be a difficult question to answer in the project’s public hearings.

Necessary Factors (NESS):
  • Engineer A's judgment that the project may accelerate uninhabitability of upstream homes
  • Engineer A's recognition that specialized expertise beyond his own is needed
  • Anticipation of difficult questions at public hearings
Sufficient Factors:
  • Professional judgment of significant potential public impact combined with the ethical obligation to hold public safety paramount
Counterfactual Test: Had Engineer A been comfortable predicting significant impacts were unlikely, no complex specialized analysis would have been proposed; the case discussion confirms the outcome 'might have been different'
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Flood Risk Judgment
    Engineer A judges the project may render upstream homes uninhabitable a decade or more earlier
  2. Recognition of Analytical Limits
    Engineer A determines a specialized subconsultant is needed to predict flood damage extent
  3. Specialized Analysis Proposal
    Engineer A proposes the complex and costly hydrologic and hydraulic analysis to Client B
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Flood Risk Judgment
  • effect: Specialized Analysis Proposal
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict the extent to which sea level rise and the increased hydraulic capacity of the tidal crossing will result in flood damage to a neighborhood of twenty upstream homes during future high tides and storm surges, anticipating this to be a difficult question to answer in the project’s public hearings.
  • necessaryFactors content: Engineer A's judgment that the project may accelerate uninhabitability of upstream homes; Engineer A's recognition that specialized expertise beyond his own is needed; Anticipation of difficult questions at public hearings
  • sufficientFactors content: Professional judgment of significant potential public impact combined with the ethical obligation to hold public safety paramount
  • counterfactual content: Had Engineer A been comfortable predicting significant impacts were unlikely, no complex specialized analysis would have been proposed; the case discussion confirms the outcome 'might have been different'
  • agentKnowledge content: Engineer A understood there was sufficient potential for flooding of other properties to merit a detailed, complex evaluation of future conditions
  • interveningFactors content: Regulations requiring only a 25-year fresh-water storm design; Codes not yet updated for climate change
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Flood Risk Judgment', 'proeth:description': 'Engineer A judges the project may render upstream homes uninhabitable a decade or more earlier'}; {'proeth:step': 2, 'proeth:element': 'Recognition of Analytical Limits', 'proeth:description': 'Engineer A determines a specialized subconsultant is needed to predict flood damage extent'}; {'proeth:step': 3, 'proeth:element': 'Specialized Analysis Proposal', 'proeth:description': 'Engineer A proposes the complex and costly hydrologic and hydraulic analysis to Client B'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_4",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092370+00:00",
  "proeth:agentKnowledge": "Engineer A understood there was sufficient potential for flooding of other properties to merit a detailed, complex evaluation of future conditions",
  "proeth:causalLanguage": "Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict the extent to which sea level rise and the increased hydraulic capacity of the tidal crossing will result in flood damage to a neighborhood of twenty upstream homes during future high tides and storm surges, anticipating this to be a difficult question to answer in the project\u2019s public hearings.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A judges the project may render upstream homes uninhabitable a decade or more earlier",
      "proeth:element": "Flood Risk Judgment",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A determines a specialized subconsultant is needed to predict flood damage extent",
      "proeth:element": "Recognition of Analytical Limits",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A proposes the complex and costly hydrologic and hydraulic analysis to Client B",
      "proeth:element": "Specialized Analysis Proposal",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Flood Risk Judgment",
  "proeth:counterfactual": "Had Engineer A been comfortable predicting significant impacts were unlikely, no complex specialized analysis would have been proposed; the case discussion confirms the outcome \u0027might have been different\u0027",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Specialized Analysis Proposal",
  "proeth:interveningFactors": [
    "Regulations requiring only a 25-year fresh-water storm design",
    "Codes not yet updated for climate change"
  ],
  "proeth:necessaryFactors": [
    "Engineer A\u0027s judgment that the project may accelerate uninhabitability of upstream homes",
    "Engineer A\u0027s recognition that specialized expertise beyond his own is needed",
    "Anticipation of difficult questions at public hearings"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Professional judgment of significant potential public impact combined with the ethical obligation to hold public safety paramount"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Client B directs Engineer A to proceed without the costly analysis unless and until such an analysis is requested by the applicable regulatory authorities.

Necessary Factors (NESS):
  • Engineer A's proposal of a complex and costly analysis
  • Client B's cost sensitivity and preference to defer to regulatory demands
  • Absence of regulatory requirement for such an analysis
Sufficient Factors:
  • The proposal of a costly, non-mandatory analysis combined with regulations that do not require climate-informed evaluation
Counterfactual Test: Without the proposal, Client B would have had nothing to reject; had regulations required the analysis, Client B's directive would not have been available
Responsibility Attribution:

Agent: Client B
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Specialized Analysis Proposal
    Engineer A proposes a costly hydrologic and hydraulic analysis by a specialized subconsultant
  2. Client Cost/Regulatory Assessment
    Client B weighs the analysis cost against the absence of any regulatory demand
  3. Client Directive Issuance
    Client B directs Engineer A to proceed without the analysis unless regulators request it
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Specialized Analysis Proposal
  • effect: Client Directive Issuance
  • responsibleAgent: Client B
Literal extractions (kept for synthesis)
  • causalLanguage content: Client B directs Engineer A to proceed without the costly analysis unless and until such an analysis is requested by the applicable regulatory authorities.
  • necessaryFactors content: Engineer A's proposal of a complex and costly analysis; Client B's cost sensitivity and preference to defer to regulatory demands; Absence of regulatory requirement for such an analysis
  • sufficientFactors content: The proposal of a costly, non-mandatory analysis combined with regulations that do not require climate-informed evaluation
  • counterfactual content: Without the proposal, Client B would have had nothing to reject; had regulations required the analysis, Client B's directive would not have been available
  • agentKnowledge content: Client B was informed of Engineer A's concern about flood damage to twenty upstream homes and the recommended analysis
  • interveningFactors content: Local regulations and national codes not yet updated to require climate-change-informed design
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Specialized Analysis Proposal', 'proeth:description': 'Engineer A proposes a costly hydrologic and hydraulic analysis by a specialized subconsultant'}; {'proeth:step': 2, 'proeth:element': 'Client Cost/Regulatory Assessment', 'proeth:description': 'Client B weighs the analysis cost against the absence of any regulatory demand'}; {'proeth:step': 3, 'proeth:element': 'Client Directive Issuance', 'proeth:description': 'Client B directs Engineer A to proceed without the analysis unless regulators request it'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_5",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092388+00:00",
  "proeth:agentKnowledge": "Client B was informed of Engineer A\u0027s concern about flood damage to twenty upstream homes and the recommended analysis",
  "proeth:causalLanguage": "Client B directs Engineer A to proceed without the costly analysis unless and until such an analysis is requested by the applicable regulatory authorities.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A proposes a costly hydrologic and hydraulic analysis by a specialized subconsultant",
      "proeth:element": "Specialized Analysis Proposal",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client B weighs the analysis cost against the absence of any regulatory demand",
      "proeth:element": "Client Cost/Regulatory Assessment",
      "proeth:step": 2
    },
    {
      "proeth:description": "Client B directs Engineer A to proceed without the analysis unless regulators request it",
      "proeth:element": "Client Directive Issuance",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Specialized Analysis Proposal",
  "proeth:counterfactual": "Without the proposal, Client B would have had nothing to reject; had regulations required the analysis, Client B\u0027s directive would not have been available",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Client Directive Issuance",
  "proeth:interveningFactors": [
    "Local regulations and national codes not yet updated to require climate-change-informed design"
  ],
  "proeth:necessaryFactors": [
    "Engineer A\u0027s proposal of a complex and costly analysis",
    "Client B\u0027s cost sensitivity and preference to defer to regulatory demands",
    "Absence of regulatory requirement for such an analysis"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Client B",
  "proeth:sufficientFactors": [
    "The proposal of a costly, non-mandatory analysis combined with regulations that do not require climate-informed evaluation"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: However, with the facts as presented, Engineer A should engage Client B in discussions about the need for the detailed evaluation and disclosure of the potential impacts on the public and alternatives for the project to mitigate those impacts, and the potential risk to Client B of not evaluating the potential impacts.

Necessary Factors (NESS):
  • Client B's directive to proceed without the analysis
  • Engineer A's standing judgment of reasonably likely and significant public impacts
  • Engineer A's paramount ethical obligation to public health, safety, and welfare
Sufficient Factors:
  • A client directive that conflicts with the engineer's judgment of significant public risk, triggering the ethical duty to engage the client
Counterfactual Test: Had Client B accepted the analysis proposal, no corrective discussion would be ethically required
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Client Directive Issuance
    Client B directs proceeding without the costly analysis
  2. Ethical Conflict Recognition
    Engineer A recognizes the directive conflicts with the paramount duty to protect public health, safety, and welfare
  3. Client Discussion Engagement
    Engineer A engages Client B on the need for detailed evaluation, disclosure, mitigation alternatives, and risks to Client B
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Client Directive Issuance
  • effect: Client Discussion Engagement
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: However, with the facts as presented, Engineer A should engage Client B in discussions about the need for the detailed evaluation and disclosure of the potential impacts on the public and alternatives for the project to mitigate those impacts, and the potential risk to Client B of not evaluating the potential impacts.
  • necessaryFactors content: Client B's directive to proceed without the analysis; Engineer A's standing judgment of reasonably likely and significant public impacts; Engineer A's paramount ethical obligation to public health, safety, and welfare
  • sufficientFactors content: A client directive that conflicts with the engineer's judgment of significant public risk, triggering the ethical duty to engage the client
  • counterfactual content: Had Client B accepted the analysis proposal, no corrective discussion would be ethically required
  • agentKnowledge content: Engineer A knows the obligation to public safety is not bounded by what is required by law or regulations
  • interveningFactors content: Client B's economic interest in avoiding the costly analysis
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Client Directive Issuance', 'proeth:description': 'Client B directs proceeding without the costly analysis'}; {'proeth:step': 2, 'proeth:element': 'Ethical Conflict Recognition', 'proeth:description': 'Engineer A recognizes the directive conflicts with the paramount duty to protect public health, safety, and welfare'}; {'proeth:step': 3, 'proeth:element': 'Client Discussion Engagement', 'proeth:description': 'Engineer A engages Client B on the need for detailed evaluation, disclosure, mitigation alternatives, and risks to Client B'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_6",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092407+00:00",
  "proeth:agentKnowledge": "Engineer A knows the obligation to public safety is not bounded by what is required by law or regulations",
  "proeth:causalLanguage": "However, with the facts as presented, Engineer A should engage Client B in discussions about the need for the detailed evaluation and disclosure of the potential impacts on the public and alternatives for the project to mitigate those impacts, and the potential risk to Client B of not evaluating the potential impacts.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client B directs proceeding without the costly analysis",
      "proeth:element": "Client Directive Issuance",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A recognizes the directive conflicts with the paramount duty to protect public health, safety, and welfare",
      "proeth:element": "Ethical Conflict Recognition",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A engages Client B on the need for detailed evaluation, disclosure, mitigation alternatives, and risks to Client B",
      "proeth:element": "Client Discussion Engagement",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Client Directive Issuance",
  "proeth:counterfactual": "Had Client B accepted the analysis proposal, no corrective discussion would be ethically required",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Client Discussion Engagement",
  "proeth:interveningFactors": [
    "Client B\u0027s economic interest in avoiding the costly analysis"
  ],
  "proeth:necessaryFactors": [
    "Client B\u0027s directive to proceed without the analysis",
    "Engineer A\u0027s standing judgment of reasonably likely and significant public impacts",
    "Engineer A\u0027s paramount ethical obligation to public health, safety, and welfare"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "A client directive that conflicts with the engineer\u0027s judgment of significant public risk, triggering the ethical duty to engage the client"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public.

Necessary Factors (NESS):
  • Engineer A's discussion with Client B about the need for the detailed evaluation
  • Client B remaining unconvinced after the discussion
  • Engineer A's continuing obligation to disclose the potential public impacts
Sufficient Factors:
  • Client refusal of the detailed evaluation combined with the engineer's duty of disclosure produces the fallback of documenting the concern in an engineering report
Counterfactual Test: If Client B were convinced by the discussion to fund the analysis, the fallback documentation proposal would be unnecessary
Responsibility Attribution:

Agent: Engineer A (with Client B sharing responsibility through refusal)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Client Discussion Engagement
    Engineer A discusses the need for detailed evaluation and disclosure with Client B
  2. Client Remains Unconvinced
    Client B declines to authorize the detailed evaluation
  3. Concern Documentation Proposal
    Engineer A proposes documenting the potential concern in an engineering report for regulatory agencies and the public
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Client Discussion Engagement
  • effect: Concern Documentation Proposal
  • responsibleAgent: Engineer A (with Client B sharing responsibility through refusal)
Literal extractions (kept for synthesis)
  • causalLanguage content: If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public.
  • necessaryFactors content: Engineer A's discussion with Client B about the need for the detailed evaluation; Client B remaining unconvinced after the discussion; Engineer A's continuing obligation to disclose the potential public impacts
  • sufficientFactors content: Client refusal of the detailed evaluation combined with the engineer's duty of disclosure produces the fallback of documenting the concern in an engineering report
  • counterfactual content: If Client B were convinced by the discussion to fund the analysis, the fallback documentation proposal would be unnecessary
  • agentKnowledge content: Engineer A knows regulatory agencies and the public will consider the project at public hearings and that this is a difficult question to answer
  • interveningFactors content: Client B's continued resistance after discussion
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Client Discussion Engagement', 'proeth:description': 'Engineer A discusses the need for detailed evaluation and disclosure with Client B'}; {'proeth:step': 2, 'proeth:element': 'Client Remains Unconvinced', 'proeth:description': 'Client B declines to authorize the detailed evaluation'}; {'proeth:step': 3, 'proeth:element': 'Concern Documentation Proposal', 'proeth:description': 'Engineer A proposes documenting the potential concern in an engineering report for regulatory agencies and the public'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_7",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092425+00:00",
  "proeth:agentKnowledge": "Engineer A knows regulatory agencies and the public will consider the project at public hearings and that this is a difficult question to answer",
  "proeth:causalLanguage": "If Client B remains unconvinced, Engineer A should propose to Client B that engineer a provides the potential concern that may necessitate more detailed evaluation in an engineering report for consideration by regulatory agencies and the public.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A discusses the need for detailed evaluation and disclosure with Client B",
      "proeth:element": "Client Discussion Engagement",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client B declines to authorize the detailed evaluation",
      "proeth:element": "Client Remains Unconvinced",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A proposes documenting the potential concern in an engineering report for regulatory agencies and the public",
      "proeth:element": "Concern Documentation Proposal",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Client Discussion Engagement",
  "proeth:counterfactual": "If Client B were convinced by the discussion to fund the analysis, the fallback documentation proposal would be unnecessary",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Concern Documentation Proposal",
  "proeth:interveningFactors": [
    "Client B\u0027s continued resistance after discussion"
  ],
  "proeth:necessaryFactors": [
    "Engineer A\u0027s discussion with Client B about the need for the detailed evaluation",
    "Client B remaining unconvinced after the discussion",
    "Engineer A\u0027s continuing obligation to disclose the potential public impacts"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (with Client B sharing responsibility through refusal)",
  "proeth:sufficientFactors": [
    "Client refusal of the detailed evaluation combined with the engineer\u0027s duty of disclosure produces the fallback of documenting the concern in an engineering report"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Failing agreement by Client B to t either of these courses of action the BER believes that Engineer A should withdraw from the project.

Necessary Factors (NESS):
  • Client B's refusal of both the detailed evaluation and the documentation/disclosure proposal
  • Engineer A's paramount obligation to public health, safety, and welfare
  • No remaining ethically acceptable path to continue on the project
Sufficient Factors:
  • Client refusal of both ethical courses of action combined with the engineer's unresolvable judgment of significant public risk
Counterfactual Test: If Client B agreed to either the detailed evaluation or disclosure in an engineering report, withdrawal would not be required
Responsibility Attribution:

Agent: Client B (refusals) and Engineer A (duty to withdraw)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Concern Documentation Proposal
    Engineer A proposes including the potential concern in an engineering report for regulators and the public
  2. Client Refusal of Both Options
    Client B fails to agree to either the detailed evaluation or the disclosure report
  3. Project Withdrawal
    Engineer A withdraws from the project as the ethically required final step
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Concern Documentation Proposal
  • effect: Project Withdrawal
  • responsibleAgent: Client B (refusals) and Engineer A (duty to withdraw)
Literal extractions (kept for synthesis)
  • causalLanguage content: Failing agreement by Client B to t either of these courses of action the BER believes that Engineer A should withdraw from the project.
  • necessaryFactors content: Client B's refusal of both the detailed evaluation and the documentation/disclosure proposal; Engineer A's paramount obligation to public health, safety, and welfare; No remaining ethically acceptable path to continue on the project
  • sufficientFactors content: Client refusal of both ethical courses of action combined with the engineer's unresolvable judgment of significant public risk
  • counterfactual content: If Client B agreed to either the detailed evaluation or disclosure in an engineering report, withdrawal would not be required
  • agentKnowledge content: Engineer A knows continuing without evaluation or disclosure would fail the paramount duty to the public; Client B knows the engineer's stated concerns
  • interveningFactors content: Client B's refusal of both proposed courses of action
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Concern Documentation Proposal', 'proeth:description': 'Engineer A proposes including the potential concern in an engineering report for regulators and the public'}; {'proeth:step': 2, 'proeth:element': 'Client Refusal of Both Options', 'proeth:description': 'Client B fails to agree to either the detailed evaluation or the disclosure report'}; {'proeth:step': 3, 'proeth:element': 'Project Withdrawal', 'proeth:description': 'Engineer A withdraws from the project as the ethically required final step'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/88#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/88#CausalChain_8",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T16:18:09.092442+00:00",
  "proeth:agentKnowledge": "Engineer A knows continuing without evaluation or disclosure would fail the paramount duty to the public; Client B knows the engineer\u0027s stated concerns",
  "proeth:causalLanguage": "Failing agreement by Client B to t either of these courses of action the BER believes that Engineer A should withdraw from the project.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A proposes including the potential concern in an engineering report for regulators and the public",
      "proeth:element": "Concern Documentation Proposal",
      "proeth:step": 1
    },
    {
      "proeth:description": "Client B fails to agree to either the detailed evaluation or the disclosure report",
      "proeth:element": "Client Refusal of Both Options",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A withdraws from the project as the ethically required final step",
      "proeth:element": "Project Withdrawal",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Concern Documentation Proposal",
  "proeth:counterfactual": "If Client B agreed to either the detailed evaluation or disclosure in an engineering report, withdrawal would not be required",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Project Withdrawal",
  "proeth:interveningFactors": [
    "Client B\u0027s refusal of both proposed courses of action"
  ],
  "proeth:necessaryFactors": [
    "Client B\u0027s refusal of both the detailed evaluation and the documentation/disclosure proposal",
    "Engineer A\u0027s paramount obligation to public health, safety, and welfare",
    "No remaining ethically acceptable path to continue on the project"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Client B (refusals) and Engineer A (duty to withdraw)",
  "proeth:sufficientFactors": [
    "Client refusal of both ethical courses of action combined with the engineer\u0027s unresolvable judgment of significant public risk"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (12)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
transportation agency conference (presentation of hydraulic evaluation procedures) before
Entity1 is before Entity2 		Engineer A's judgment about accelerated flooding time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		It is Engineer A's judgment, based on hydraulic evaluation procedures presented at a recent transpor... [more]
Client B engaging Engineer A before
Entity1 is before Entity2 		Engineer A's design and permitting work time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A is a consulting engineer representing Client B... Engineer A's scope includes design and ... [more]
Engineer A's application of current local regulations (25-year storm) during
Entity1 occurs entirely within the duration of Entity2 		project design phase time:intervalDuring
http://www.w3.org/2006/time#intervalDuring 		Local development regulations require designing for a 25-year fresh-water storm... Engineer A's scop... [more]
Engineer A's proposal of the specialized hydrologic/hydraulic analysis before
Entity1 is before Entity2 		project public hearings time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A proposes a complex and costly hydrologic and hydraulic analysis... anticipating this to b... [more]
Engineer A's proposal of the specialized analysis before
Entity1 is before Entity2 		Client B's directive to proceed without the analysis time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsu... [more]
proposed project (upgraded tidal crossing) before
Entity1 is before Entity2 		potential flood damage to twenty upstream homes time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		the proposed project may result in some upstream homes becoming uninhabitable a decade or more earli... [more]
potential flood damage to upstream homes during
Entity1 occurs entirely within the duration of Entity2 		future high tides and storm surges time:intervalDuring
http://www.w3.org/2006/time#intervalDuring 		will result in flood damage to a neighborhood of twenty upstream homes during future high tides and ... [more]
updating of local regulations and national codes for climate change after
Entity1 is after Entity2 		current project design and permitting time:intervalAfter
http://www.w3.org/2006/time#intervalAfter 		The local development regulations and national design codes and standards have not yet been updated ... [more]
engineers' assumption of stationary historical climate data overlaps
Entity1 starts before Entity2 and ends during Entity2 		recent decades of changing climate and weather patterns time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps 		For more than a century, engineers have assumed that future climate and weather conditions will be c... [more]
Engineer A's discussion with Client B about the need for detailed evaluation before
Entity1 is before Entity2 		Engineer A's proposal to document concerns in an engineering report time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A should engage Client B in discussions about the need for the detailed evaluation... If Cl... [more]
Client B's refusal of both proposed courses of action before
Entity1 is before Entity2 		Engineer A's withdrawal from the project time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Failing agreement by Client B to either of these courses of action the BER believes that Engineer A ... [more]
specialized detailed analysis (if performed) after
Entity1 is after Entity2 		regulatory authorities' request for the analysis time:intervalAfter
http://www.w3.org/2006/time#intervalAfter 		Client B directs Engineer A to proceed without the costly analysis unless and until such an analysis... [more]
About Allen Relations & OWL-Time

Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.

Each relation includes both a ProEthica custom property and a time:* OWL-Time property for maximum compatibility.

Back to Extraction Continue to Step 4

© Licensed under the GNU GPL v3