Client Economic Pressure Resistance Principle
Class
http://proethica.org/ontology/intermediate#ClientEconomicPressureResistancePrinciple
Class Hierarchy
- Thing
- ↳ entity (bfo)
- ↳ continuant (bfo)
- ↳ generically dependent continuant (bfo)
- ↳ information content entity (iao)
- ↳ directive information entity (iao)
- ↳ Principle (proethica-core)
- ↳ Professional Virtue Principle (proethica-intermediate)
- ↳ Client Economic Pressure Resistance Principle
Definition
Professional virtue principle prohibiting engineers from abandoning their ethical duties to the public by yielding to client economic concerns or cost-based objections to necessary safety measures. When a client refuses to fund protective measures that the engineer has identified as necessary for public safety, the engineer must not continue work in a manner that perpetuates the identified risk, regardless of the financial consequences to the client or the professional relationship.
Inherited from PublicSafetyParamount
Fundamental principle requiring engineers to prioritize public safety above client instructions, employer directives, or collegial relationships when significant design errors create risk to persons who will occupy or use engineered structures.
Case Provenance
Discovered in
This class was discovered during extraction of the case(s) above; the supporting verbatim quotes are in Source Evidence.
Properties
Abstract Nature
The principle requires engineers to distinguish between legitimate client cost management decisions and client refusals that cross the threshold of creating unacceptable public risk. This distinction requires professional judgment about the severity of the risk and the adequacy of proposed alternatives.
Confidence
0.92
Derived Obligations
Document the client's refusal and the engineer's response
Refuse to continue work when client declines necessary safety measures on cost grounds
Treat client refusal of safety measures as a trigger for withdrawal or escalation, not accommodation
Extensional Examples
BER Case 84-5: Engineer A violated Code by continuing project after client refused to hire safety representative on cost grounds, abandoning ethical duty to public
Present case: Engineer L cannot continue work after Client X refuses to implement protective stormwater measures
Operationalization
Requires engineers to refuse to continue work when client cost objections result in removal of safety measures the engineer has identified as necessary, and to treat such refusals as triggering the obligation to withdraw or escalate rather than to proceed.
Potential Conflicts
Contractual obligations to complete work
Faithful Agent Duty Principle
Principle Category
professional_virtue
Value Basis
The integrity of the engineering profession depends on engineers maintaining their ethical obligations even under financial and relational pressure. Yielding to client economic concerns when public safety is at stake signals that professional duties are negotiable, undermining public trust in the profession.
Property Structure
1 · Object and Data Properties
rdfs:domain on this class or ancestor
| Property | Range | Description |
|---|---|---|
| establishedBy inherited | CodeProvision | Indicates which code provision establishes this ethical concept. |
| invokedBy inherited | Agent | Relates a Principle to the Agent(s) that invoke it in the case scenario (the parties who appeal to the principle to justify or evaluate conduct). May name several agents. |
2 · Definitional Attributes
SHACL definitional shape
| Attribute | Property (sh:path) | Description |
|---|---|---|
| principle kind | principleCategory | The controlled principle kind, which drives the four-kind subClassOf typing: FundamentalEthicalPrinciple, ProfessionalVirtuePrinciple, RelationalPrinciple, DomainSpecificPrinciple. The canonical leaf label becomes the rdf:type; the category is a routing input, not stored as a literal. |
| extensional cases | extensionalCases | Class-level prior cases that instantiate the principle (McLaren extensional grounding); an optional class-mint field. |
3 · Bearer Attributes
SHACL property shape
individual data
| Attribute | Property (sh:path) | Description |
|---|---|---|
| interpretation | interpretation | Per-case reading of what the principle requires in this situation (a defeasibility-pipeline source field). |
| concrete expression | concreteExpression | How the principle is concretely expressed in the case (a defeasibility-pipeline source field). |
| applied to | appliedTo | What the principle is applied to in the case (the situation or party it bears on). |
| balancing with | balancingWith | The competing principle or value this principle is balanced against in the case, recorded as a literal; extraction records the tension but asserts no defeat or precedence, and the defeasibility edges are materialized by a separate pass from this field. |
| tension resolution | tensionResolution | How the case resolves the tension involving this principle (a defeasibility-pipeline source field). |
| invoked by | invokedBy | The agent who invokes the principle, via the P->Agent invokedBy edge (resolved to a case Agent by embedding shortlist + LLM select; a Board-pattern invoking party resolves deterministically to the case-scoped NSPE Board of Ethical Review Agent). Range: Agent. |
4 · Referenced By
rdfs:range on this class or ancestor
| From | Property | Description |
|---|---|---|
| Action | guidedByPrinciple inherited | Relates an action to a principle that directs it. The principle supplies the value the action is taken to serve. |
| Code Provision | establishes inherited | Relates a code provision to the ethical concepts (principles, obligations, constraints) it establishes or defines. |
| Obligation | derivedFromPrinciple inherited | Relates an obligation to the principle or principles it operationalizes. The obligation gives concrete directive force to the more abstract value the principle expresses (Dennis et al. 2016). |
| Role | adheresToPrinciple inherited | Relates a role to principles that guide its conduct; the role-relative applicability edge of the R->P->O chain (the role determines which principles apply to conduct in that standing). |
Source Evidence
Text references
Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.
Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A abandoned the ethical duty [to the public] and proceeded to work on the project.
We note a direct parallel between the 1984 case and the facts under consideration.
Source text
The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A abandoned the ethical duty [to the public] and proceeded to work on the project.
@prefix core: <http://proethica.org/ontology/core#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix pcsh: <http://proethica.org/shapes/core#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix proeth-prov: <http://proethica.org/provenance#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
proeth:ClientEconomicPressureResistancePrinciple a owl:Class ;
rdfs:label "Client Economic Pressure Resistance Principle" ;
proeth:abstractNature "The principle requires engineers to distinguish between legitimate client cost management decisions and client refusals that cross the threshold of creating unacceptable public risk. This distinction requires professional judgment about the severity of the risk and the adequacy of proposed alternatives." ;
proeth:confidence "0.92" ;
proeth:derivedObligations "Document the client's refusal and the engineer's response",
"Refuse to continue work when client declines necessary safety measures on cost grounds",
"Treat client refusal of safety measures as a trigger for withdrawal or escalation, not accommodation" ;
proeth:extensionalExamples "BER Case 84-5: Engineer A violated Code by continuing project after client refused to hire safety representative on cost grounds, abandoning ethical duty to public",
"Present case: Engineer L cannot continue work after Client X refuses to implement protective stormwater measures" ;
proeth:operationalization "Requires engineers to refuse to continue work when client cost objections result in removal of safety measures the engineer has identified as necessary, and to treat such refusals as triggering the obligation to withdraw or escalate rather than to proceed." ;
proeth:potentialConflicts "Contractual obligations to complete work",
"Faithful Agent Duty Principle" ;
proeth:principleCategory "professional_virtue" ;
proeth:textReferences "Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.",
"Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.",
"The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A abandoned the ethical duty [to the public] and proceeded to work on the project.",
"We note a direct parallel between the 1984 case and the facts under consideration." ;
proeth:valueBasis "The integrity of the engineering profession depends on engineers maintaining their ethical obligations even under financial and relational pressure. Yielding to client economic concerns when public safety is at stake signals that professional duties are negotiable, undermining public trust in the profession." ;
proeth-prov:discoveredInCase 8 ;
proeth-prov:discoveredInPass 2 ;
proeth-prov:discoveredInSection "discussion" ;
proeth-prov:firstDiscoveredAt "2026-06-04T10:05:37.970804+00:00"^^xsd:dateTime ;
proeth-prov:firstDiscoveredInCase 8 ;
proeth-prov:matchConfidence 0.78 ;
proeth-prov:matchReasoning "The Client Economic Pressure Resistance Principle is a specific application of the Public Safety Paramount class already in the ontology, focusing on the scenario where client cost objections are the mechanism by which public safety is threatened. The existing class captures the general obligation to prioritize public safety over competing pressures. The present principle adds specificity about the economic pressure vector, making it a variant rather than an exact match. The individual record will capture the case-specific application." ;
proeth-prov:matchedOntologyClass proeth:PublicSafetyParamount ;
proeth-prov:matchedOntologyLabel "Public Safety Paramount" ;
proeth-prov:matchesExisting true ;
proeth-prov:sourceText "The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A abandoned the ethical duty [to the public] and proceeded to work on the project." ;
rdfs:comment "Professional virtue principle prohibiting engineers from abandoning their ethical duties to the public by yielding to client economic concerns or cost-based objections to necessary safety measures. When a client refuses to fund protective measures that the engineer has identified as necessary for public safety, the engineer must not continue work in a manner that perpetuates the identified risk, regardless of the financial consequences to the client or the professional relationship." ;
rdfs:subClassOf proeth:ProfessionalVirtuePrinciple ;
skos:definition "Professional virtue principle prohibiting engineers from abandoning their ethical duties to the public by yielding to client economic concerns or cost-based objections to necessary safety measures. When a client refuses to fund protective measures that the engineer has identified as necessary for public safety, the engineer must not continue work in a manner that perpetuates the identified risk, regardless of the financial consequences to the client or the professional relationship." ;
skos:scopeNote "[PublicSafetyParamount] Fundamental principle requiring engineers to prioritize public safety above client instructions, employer directives, or collegial relationships when significant design errors create risk to persons who will occupy or use engineered structures." ;
prov:generatedAtTime "2026-06-04T10:05:37.970804+00:00"^^xsd:dateTime ;
prov:wasAttributedTo "Case 8 Extraction",
"claude-sonnet-4-6" .
pcsh:CaseAnnotationShape a sh:NodeShape ;
rdfs:label "Shared per-case annotation schema (all nine components)"@en ;
rdfs:comment "The cross-component annotation fields on committed case individuals: proeth:confidence (extraction confidence, decimal; all components except Action, whose Step-3 contract carries no confidence field), proeth:textReferences (verbatim supporting quotes, universal), proeth-prov sourceText (the source snippet, on the Step-1/2 provenance layers; Step-3 A/E individuals ground via textReferences only), and the involvement gloss (proeth:caseInvolvement on role individuals, proeth:caseContext on obligation, capability, and constraint individuals). Values are per-individual; the fields do not individuate any type."@en ;
sh:property [ sh:description "Extraction confidence for this individual (0 to 1)." ;
sh:name "confidence" ;
sh:order 1 ;
sh:path proeth:confidence ],
[ sh:description "Verbatim case quotes supporting this individual." ;
sh:name "text references" ;
sh:order 2 ;
sh:path proeth:textReferences ],
[ sh:description "How this individual figures in the case narrative (role individuals; the same text is routed into rdfs:comment)." ;
sh:name "case involvement" ;
sh:order 3 ;
sh:path proeth:caseInvolvement ],
[ sh:description "Grounding context in this case (obligation, capability, and constraint individuals)." ;
sh:name "case context" ;
sh:order 4 ;
sh:path proeth:caseContext ] ;
sh:targetClass core:Action,
core:Capability,
core:Constraint,
core:Event,
core:Obligation,
core:Principle,
core:Resource,
core:Role,
core:State .
pcsh:PrincipleDefinitionShape a sh:NodeShape ;
rdfs:label "Principle definition schema (type-level, descriptive, field contract)"@en ;
rdfs:comment "What individuates a principle TYPE: its canonical kind (drives the four-kind subClassOf typing; the canonical leaf becomes the rdf:type) and the extensional cases that ground it (McLaren). The five per-case narrative literals and the invokedBy edge are per-individual and now declared on PrinciplePropertyShape, mirroring the RoleDefinitionShape/ProfessionalRolePropertyShape split so the {{ principle_schema }} prompt separates the type judgment from what the case supplies. Descriptive only (no validation result); principle_category is a routing input, not stored as a literal."@en ;
sh:property [ sh:description "The controlled principle kind, which drives the four-kind subClassOf typing: FundamentalEthicalPrinciple, ProfessionalVirtuePrinciple, RelationalPrinciple, DomainSpecificPrinciple. The canonical leaf label becomes the rdf:type; the category is a routing input, not stored as a literal." ;
sh:name "principle kind" ;
sh:order 1 ;
sh:path proeth:principleCategory ],
[ sh:description "Class-level prior cases that instantiate the principle (McLaren extensional grounding); an optional class-mint field." ;
sh:name "extensional cases" ;
sh:order 2 ;
sh:path proeth:extensionalCases ] ;
sh:targetClass core:Principle .
pcsh:PrinciplePropertyShape a sh:NodeShape ;
rdfs:label "Principle per-case schema (individual data, non-definitional)"@en ;
rdfs:comment "What a principle INDIVIDUAL is described by in a specific case: the five narrative literals the defeasibility pipeline consumes and the agent that invokes it. These do NOT individuate the principle TYPE (that is PrincipleDefinitionShape); their values are per-case, asserted on the individual. Descriptive only."@en ;
sh:property [ sh:description "Per-case reading of what the principle requires in this situation (a defeasibility-pipeline source field)." ;
sh:name "interpretation" ;
sh:order 1 ;
sh:path proeth:interpretation ],
[ sh:description "How the principle is concretely expressed in the case (a defeasibility-pipeline source field)." ;
sh:name "concrete expression" ;
sh:order 2 ;
sh:path proeth:concreteExpression ],
[ sh:description "What the principle is applied to in the case (the situation or party it bears on)." ;
sh:name "applied to" ;
sh:order 3 ;
sh:path proeth:appliedTo ],
[ sh:description "The competing principle or value this principle is balanced against in the case, recorded as a literal; extraction records the tension but asserts no defeat or precedence, and the defeasibility edges are materialized by a separate pass from this field." ;
sh:name "balancing with" ;
sh:order 4 ;
sh:path proeth:balancingWith ],
[ sh:description "How the case resolves the tension involving this principle (a defeasibility-pipeline source field)." ;
sh:name "tension resolution" ;
sh:order 5 ;
sh:path proeth:tensionResolution ],
[ sh:description "The agent who invokes the principle, via the P->Agent invokedBy edge (resolved to a case Agent by embedding shortlist + LLM select; a Board-pattern invoking party resolves deterministically to the case-scoped NSPE Board of Ethical Review Agent). Range: Agent." ;
sh:name "invoked by" ;
sh:order 6 ;
sh:path core:invokedBy ] ;
sh:targetClass core:Principle .
Metadata
Extraction details
Discovered in case
8
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-06-04T10:05:37.970804+00:00
First case
8
Match Confidence
0.78
Match Reasoning
The Client Economic Pressure Resistance Principle is a specific application of the Public Safety Paramount class already in the ontology, focusing on the scenario where client cost objections are the mechanism by which public safety is threatened. The existing class captures the general obligation to prioritize public safety over competing pressures. The present principle adds specificity about the economic pressure vector, making it a variant rather than an exact match. The individual record will capture the case-specific application.
Matched Ontology Label
Public Safety Paramount
Matches Existing
true
Generated
2026-06-04T10:05:37.970804+00:00
Attributed to
['Case 8 Extraction', 'claude-sonnet-4-6']