Competence Boundary Principle

@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:CompetenceBoundaryPrinciple a owl:Class ; rdfs:label "Competence Boundary Principle" ; proeth:abstractNature "Open-textured standard requiring case-by-case assessment of what constitutes adequate competence for a given domain, and whether available tools can bridge a competence gap or merely mask it." ; proeth:confidence "0.88" ; proeth:derivedObligations "Decline to offer services in domains where the engineer lacks substantive training and experience", "Disclose competence limitations to prospective clients before accepting engagements", "Recognize that software tools do not confer professional competence", "Seek collaboration with or referral to engineers who possess the requisite domain expertise" ; proeth:extensionalExamples "A chemical engineer using a CD-ROM design tool to offer facilities design services without relevant training", "A structural engineer offering geotechnical design services after completing an online course", "An electrical engineer offering civil highway design based solely on software-generated outputs" ; proeth:operationalization "Requires engineers to assess their own competence before accepting engagements, to decline work outside their domain, and to resist commercial incentives that encourage overreach beyond established expertise." ; proeth:potentialConflicts "Client demand for one-stop engineering services", "Commercial pressure to expand service offerings", "Employer directives to take on unfamiliar project types" ; proeth:principleCategory "professional_virtue" ; proeth:textReferences "Engineer A orders the CD-ROM and begins to offer facilities design and construction services.", "Engineer A, a chemical engineer with no facilities design and construction experience, receives a solicitation in the mail", "never designed a highway before? No problem. Just point to the 'Highways' window and click." ; proeth:valueBasis "Public safety and trust in the profession depend on engineers practicing only within domains where they can exercise genuine, substantive professional judgment rather than nominal approval of automated outputs." ; proeth-prov:discoveredInCase 121 ; proeth-prov:discoveredInPass 2 ; proeth-prov:discoveredInSection "facts" ; proeth-prov:firstDiscoveredAt "2026-06-04T18:45:01.804237+00:00"^^xsd:dateTime ; proeth-prov:firstDiscoveredInCase 121 ; proeth-prov:matchConfidence 0.75 ; proeth-prov:matchReasoning "The existing Competence Principle addresses balancing professional autonomy with recognition of limitations and need for collaboration. The concept extracted here is a more specific instantiation of that principle, focused on the prohibition against offering services outside one's domain and the inadequacy of software tools as a substitute for genuine competence. The existing class is the appropriate parent, but the case raises a distinct emphasis on domain-boundary overreach enabled by commercial tools that the existing class does not fully capture. Confidence is set at 0.75 as a variant rather than a direct match." ; proeth-prov:matchedOntologyClass proeth:CompetencePrinciple ; proeth-prov:matchedOntologyLabel "Competence Principle" ; proeth-prov:matchesExisting true ; proeth-prov:sourceText "Engineer A, a chemical engineer with no facilities design and construction experience, receives a solicitation in the mail" ; rdfs:comment "Professional principle prohibiting engineers from offering or undertaking engineering services in technical domains for which they lack the requisite education, training, or experience, regardless of the availability of software tools, templates, or other aids that may simulate competence. The use of automated design tools does not substitute for the foundational knowledge required to exercise independent professional judgment over the outputs of those tools." ; rdfs:subClassOf proeth:ProfessionalVirtuePrinciple ; skos:definition "Professional principle prohibiting engineers from offering or undertaking engineering services in technical domains for which they lack the requisite education, training, or experience, regardless of the availability of software tools, templates, or other aids that may simulate competence. The use of automated design tools does not substitute for the foundational knowledge required to exercise independent professional judgment over the outputs of those tools." ; skos:scopeNote "[CompetencePrinciple] Balances professional autonomy with recognition of limitations and need for collaboration." ; prov:generatedAtTime "2026-06-04T18:45:01.804237+00:00"^^xsd:dateTime ; prov:wasAttributedTo "Case 121 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 .