Public Welfare Paramountcy Principle

Class
http://proethica.org/ontology/intermediate#PublicWelfareParamountcyPrinciple
Class Hierarchy
Definition

Fundamental principle requiring engineers to hold paramount the safety, health, and welfare of the public above all competing professional obligations, including duties of loyalty to clients and employers. This principle is the highest-order canon in engineering ethics and cannot be overridden by client economic concerns, contractual relationships, or instructions to suppress findings.

Inherited from PublicWelfarePrinciple

Requires contextual interpretation to balance against client confidentiality and employer loyalty when public safety is at risk.

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
Open-textured value requiring case-by-case interpretation of what constitutes a sufficient threat to public welfare to trigger disclosure or refusal obligations, and how to balance against competing duties of loyalty and confidentiality.
Confidence
0.97
Derived Obligations
Disclose identified safety and environmental risks to affected parties and authorities
Prioritize public health over client economic concerns when the two conflict
Refuse to continue work when client declines to implement necessary protective measures
Extensional Examples
BER Case 22-5 and BER Case 20-4: emphasis on safe drinking water as public welfare concern
BER Case 76-4: Engineer Doe obligated to report discharge findings to Pollution Control Authority despite client instruction to suppress written report
BER Case 84-5: Engineer A violated Code by continuing project after client refused safety representative, subordinating public welfare to client economic concerns
Operationalization
Requires engineers to disclose known safety risks to appropriate authorities, refuse to continue work that creates unmitigated public risk, and resist client pressure to suppress or ignore safety findings.
Potential Conflicts
Client Loyalty Limits
Confidentiality Principle
Faithful Agent Duty Principle
Principle Category
fundamental_ethical
Value Basis
The foundational justification for professional licensure and regulation is protection of the public, who cannot independently assess the safety of engineered works and must rely on professional integrity.
Property Structure
1 · Object and Data Properties rdfs:domain on this class or ancestor
PropertyRangeDescription
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
AttributeProperty (sh:path)Description
principle kindprincipleCategoryThe 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 casesextensionalCasesClass-level prior cases that instantiate the principle (McLaren extensional grounding); an optional class-mint field.
3 · Bearer Attributes SHACL property shape individual data
AttributeProperty (sh:path)Description
interpretationinterpretationPer-case reading of what the principle requires in this situation (a defeasibility-pipeline source field).
concrete expressionconcreteExpressionHow the principle is concretely expressed in the case (a defeasibility-pipeline source field).
applied toappliedToWhat the principle is applied to in the case (the situation or party it bears on).
balancing withbalancingWithThe 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 resolutiontensionResolutionHow the case resolves the tension involving this principle (a defeasibility-pipeline source field).
invoked byinvokedByThe 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
FromPropertyDescription
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 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.
Section 2(a) requires that his duty to the public be paramount.
a code of ethics is of course a statement of commitment from a particular profession to assist its members in the protection of the public health and safety
it is basic to the entire concept of a profession that its members will devote their interests to the public welfare

Source text
Section 2(a) requires that his duty to the public be paramount.
Used in cases 3

Case ontologies that instantiate this class or one of its base-ontology descendants. Computed from each individual's type, so the list stays current as cases are extracted. The originating case is shown under Extraction details.

Case 76 Case 85 Case 86
@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:PublicWelfareParamountcyPrinciple a owl:Class ; rdfs:label "Public Welfare Paramountcy Principle" ; proeth:abstractNature "Open-textured value requiring case-by-case interpretation of what constitutes a sufficient threat to public welfare to trigger disclosure or refusal obligations, and how to balance against competing duties of loyalty and confidentiality." ; proeth:confidence "0.97" ; proeth:derivedObligations "Disclose identified safety and environmental risks to affected parties and authorities", "Prioritize public health over client economic concerns when the two conflict", "Refuse to continue work when client declines to implement necessary protective measures" ; proeth:extensionalExamples "BER Case 22-5 and BER Case 20-4: emphasis on safe drinking water as public welfare concern", "BER Case 76-4: Engineer Doe obligated to report discharge findings to Pollution Control Authority despite client instruction to suppress written report", "BER Case 84-5: Engineer A violated Code by continuing project after client refused safety representative, subordinating public welfare to client economic concerns" ; proeth:operationalization "Requires engineers to disclose known safety risks to appropriate authorities, refuse to continue work that creates unmitigated public risk, and resist client pressure to suppress or ignore safety findings." ; proeth:potentialConflicts "Client Loyalty Limits", "Confidentiality Principle", "Faithful Agent Duty Principle" ; proeth:principleCategory "fundamental_ethical" ; proeth:textReferences "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.", "Section 2(a) requires that his duty to the public be paramount.", "a code of ethics is of course a statement of commitment from a particular profession to assist its members in the protection of the public health and safety", "it is basic to the entire concept of a profession that its members will devote their interests to the public welfare" ; proeth:valueBasis "The foundational justification for professional licensure and regulation is protection of the public, who cannot independently assess the safety of engineered works and must rely on professional integrity." ; proeth-prov:discoveredInCase 8, 76 ; 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.93 ; proeth-prov:matchReasoning "This principle maps directly to the existing Public Welfare Principle and Public Welfare Paramount classes in the ontology. The case text explicitly invokes NSPE Canon I.1 and the paramountcy formulation. The existing Public Welfare Principle class covers this concept; the individual record captures the case-specific application." ; proeth-prov:matchedOntologyClass proeth:PublicWelfarePrinciple ; proeth-prov:matchedOntologyLabel "Public Welfare Principle" ; proeth-prov:matchesExisting true ; proeth-prov:sourceText "Section 2(a) requires that his duty to the public be paramount." ; rdfs:comment "Fundamental principle requiring engineers to hold paramount the safety, health, and welfare of the public above all competing professional obligations, including duties of loyalty to clients and employers. This principle is the highest-order canon in engineering ethics and cannot be overridden by client economic concerns, contractual relationships, or instructions to suppress findings." ; rdfs:subClassOf proeth:FundamentalEthicalPrinciple ; skos:definition "Fundamental principle requiring engineers to hold paramount the safety, health, and welfare of the public above all competing professional obligations, including duties of loyalty to clients and employers. This principle is the highest-order canon in engineering ethics and cannot be overridden by client economic concerns, contractual relationships, or instructions to suppress findings." ; skos:scopeNote "[PublicWelfarePrinciple] Requires contextual interpretation to balance against client confidentiality and employer loyalty when public safety is at risk." ; 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
Type
Class
Last Updated
2026-07-05 15:17
Discovered in case
['8', '76']
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-06-04T10:05:37.970804+00:00
First case
8
Match Confidence
0.93
Match Reasoning
This principle maps directly to the existing Public Welfare Principle and Public Welfare Paramount classes in the ontology. The case text explicitly invokes NSPE Canon I.1 and the paramountcy formulation. The existing Public Welfare Principle class covers this concept; the individual record captures the case-specific application.
Matched Ontology Label
Public Welfare Principle
Matches Existing
true
Generated
2026-06-04T10:05:37.970804+00:00
Attributed to
['Case 8 Extraction', 'claude-sonnet-4-6']