Environmental Justice as Engineering Design Obligation Invoked by Engineer K
P · Principle
Individual
http://proethica.org/ontology/case/4#Environmental_Justice_as_Engineering_Design_Obligation_Invoked_by_Engineer_K
Properties
Instance of
EnvironmentalJusticeasEngineeringDesignObligation
http://proethica.org/ontology/intermediate#EnvironmentalJusticeasEngineeringDesignObligation
Applied to
City Municipal Infrastructure Client with Environmental Justice Obligations
Nearby Underserved Community Flood Risk Stakeholder
Traditional Approach design evaluation
Balancing with
Client Loyalty
Cost-Preference Community Stakeholder priorities
Faithful Agent Obligation Within Ethical Limits
Concrete expression
Engineer K identified that the Traditional Approach would disproportionately burden a nearby underserved community with flood risk under high-volume conditions, treated this distributional inequity as a material factor in the design evaluation, and disclosed it to City leadership as part of the comparative analysis
Confidence
0.9
Importance
high
Interpretation
In this context, environmental justice as an engineering design obligation required Engineer K to extend the public welfare analysis beyond aggregate flood protection to consider who bears the residual flood risk under the Traditional Approach, and to treat the disproportionate burden on the underserved community as a material design factor requiring disclosure and advocacy for mitigation
Invoked by
Engineer K Flood Control Design Engineer
Tension resolution
Engineer K fulfilled the identification and disclosure dimensions of the obligation; the City's rejection of mitigation raises the unresolved question of whether further escalation or community notification is required
Source Evidence
Source text
Engineer K discovers that the Traditional Approach could disproportionately impact a nearby underserved community by diverting floodwaters to their neighborhood under low-probability but high-volume conditions—particularly if the design capacity of the Traditional Approach is breached.
Text references
Engineer K discovers that the Traditional Approach could disproportionately impact a nearby underserved community by diverting floodwaters to their neighborhood under low-probability but high-volume conditions—particularly if the design capacity of the Traditional Approach is breached.
The City's leadership decides not to address the identified floodwater issue with the Traditional Approach, ultimately concluding that any action to mitigate the impact on this community would delay the project further and reinforcing the low probability of such conditions occurring.
TTL
@prefix case4: <http://proethica.org/ontology/case/4#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
case4:Environmental_Justice_as_Engineering_Design_Obligation_Invoked_by_Engineer_K a proeth:EnvironmentalJusticeasEngineeringDesignObligation,
owl:NamedIndividual ;
rdfs:label "Environmental Justice as Engineering Design Obligation Invoked by Engineer K" ;
proeth:appliedto "City Municipal Infrastructure Client with Environmental Justice Obligations",
"Nearby Underserved Community Flood Risk Stakeholder",
"Traditional Approach design evaluation" ;
proeth:balancingwith "Client Loyalty",
"Cost-Preference Community Stakeholder priorities",
"Faithful Agent Obligation Within Ethical Limits" ;
proeth:conceptCategory "Principle" ;
proeth:concreteexpression "Engineer K identified that the Traditional Approach would disproportionately burden a nearby underserved community with flood risk under high-volume conditions, treated this distributional inequity as a material factor in the design evaluation, and disclosed it to City leadership as part of the comparative analysis" ;
proeth:confidence "0.9" ;
proeth:discoveredincase "4" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "facts" ;
proeth:firstdiscoveredat "2026-02-26T16:32:57.409598+00:00" ;
proeth:firstdiscoveredincase "4" ;
proeth:generatedattime "2026-02-26T16:32:57.409598+00:00" ;
proeth:importance "high" ;
proeth:interpretation "In this context, environmental justice as an engineering design obligation required Engineer K to extend the public welfare analysis beyond aggregate flood protection to consider who bears the residual flood risk under the Traditional Approach, and to treat the disproportionate burden on the underserved community as a material design factor requiring disclosure and advocacy for mitigation" ;
proeth:invokedby "Engineer K Flood Control Design Engineer" ;
proeth:principleclass "Environmental Justice as Engineering Design Obligation" ;
proeth:sourcetext "Engineer K discovers that the Traditional Approach could disproportionately impact a nearby underserved community by diverting floodwaters to their neighborhood under low-probability but high-volume conditions—particularly if the design capacity of the Traditional Approach is breached." ;
proeth:tensionresolution "Engineer K fulfilled the identification and disclosure dimensions of the obligation; the City's rejection of mitigation raises the unresolved question of whether further escalation or community notification is required" ;
proeth:textreferences "Engineer K discovers that the Traditional Approach could disproportionately impact a nearby underserved community by diverting floodwaters to their neighborhood under low-probability but high-volume conditions—particularly if the design capacity of the Traditional Approach is breached.",
"The City's leadership decides not to address the identified floodwater issue with the Traditional Approach, ultimately concluding that any action to mitigate the impact on this community would delay the project further and reinforcing the low probability of such conditions occurring." ;
proeth:wasattributedto "Case 4 Extraction" ;
prov:generatedAtTime "2026-02-26T17:17:00.272413"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 4 Extraction" .
Metadata
Extraction details
Discovered in case
4
Discovered in pass
2
Discovered in section
facts
First discovered
2026-02-26T16:32:57.409598+00:00
First case
4
Generated
2026-02-26T16:32:57.409598+00:00
Attributed to
Case 4 Extraction
Generated
2026-02-26T17:17:00.272413
Generated by
ProEthica Case 4 Extraction