Client Loyalty Bounded by Public Welfare Invoked Against Client B Cost Directives
P · Principle
Individual
http://proethica.org/ontology/case/88#Client_Loyalty_Bounded_by_Public_Welfare_Invoked_Against_Client_B_Cost_Directives
Properties
Instance of
Applied to
Client B Cost-Directing Developer
Balancing with
Non-Acquiescence to Client Directive Suppressing Safety Analysis
Public Welfare Paramount
Concrete expression
Engineer A must serve Client B's interests faithfully — including respecting cost management concerns and contractual scope — but only within the bounds of the public welfare obligation, which requires that Engineer A not subordinate the upstream community's flood safety to Client B's financial preferences
Confidence
0.88
Importance
high
Interpretation
Client loyalty is a genuine and weighty obligation, but it is bounded by the primacy of public welfare; Engineer A's graduated escalation sequence reflects the attempt to serve both obligations before the conflict becomes irresolvable
Invoked by
Engineer A Tidal Crossing Infrastructure Design Engineer
Tension resolution
Client loyalty yields to public welfare when the client's cost management directives would result in suppression of safety-relevant analysis affecting identifiable third parties
Source Evidence
Source text
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.
Text references
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.
TTL
@prefix case88: <http://proethica.org/ontology/case/88#> .
@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#> .
case88:Client_Loyalty_Bounded_by_Public_Welfare_Invoked_Against_Client_B_Cost_Directives a proeth:ClientLoyalty,
owl:NamedIndividual ;
rdfs:label "Client Loyalty Bounded by Public Welfare Invoked Against Client B Cost Directives" ;
proeth:appliedto "Client B Cost-Directing Developer" ;
proeth:balancingwith "Non-Acquiescence to Client Directive Suppressing Safety Analysis",
"Public Welfare Paramount" ;
proeth:conceptCategory "Principle" ;
proeth:concreteexpression "Engineer A must serve Client B's interests faithfully — including respecting cost management concerns and contractual scope — but only within the bounds of the public welfare obligation, which requires that Engineer A not subordinate the upstream community's flood safety to Client B's financial preferences" ;
proeth:confidence "0.88" ;
proeth:discoveredincase "88" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "discussion" ;
proeth:firstdiscoveredat "2026-02-26T00:19:27.254437+00:00" ;
proeth:firstdiscoveredincase "88" ;
proeth:generatedattime "2026-02-26T00:19:27.254437+00:00" ;
proeth:importance "high" ;
proeth:interpretation "Client loyalty is a genuine and weighty obligation, but it is bounded by the primacy of public welfare; Engineer A's graduated escalation sequence reflects the attempt to serve both obligations before the conflict becomes irresolvable" ;
proeth:invokedby "Engineer A Tidal Crossing Infrastructure Design Engineer" ;
proeth:principleclass "Client Loyalty" ;
proeth:sourcetext "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:tensionresolution "Client loyalty yields to public welfare when the client's cost management directives would result in suppression of safety-relevant analysis affecting identifiable third parties" ;
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:wasattributedto "Case 88 Extraction" ;
prov:generatedAtTime "2026-02-26T00:31:11.071704"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 88 Extraction" .
Metadata
Extraction details
Discovered in case
88
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-02-26T00:19:27.254437+00:00
First case
88
Generated
2026-02-26T00:19:27.254437+00:00
Attributed to
Case 88 Extraction
Generated
2026-02-26T00:31:11.071704
Generated by
ProEthica Case 88 Extraction