Unfamiliar Tool Competence Constraint
Class
http://proethica.org/ontology/intermediate#UnfamiliarToolCompetenceConstraint
Class Hierarchy
- Thing
- ↳ entity (bfo)
- ↳ continuant (bfo)
- ↳ generically dependent continuant (bfo)
- ↳ information content entity (iao)
- ↳ directive information entity (iao)
- ↳ Constraint (proethica-core)
- ↳ Competence Constraint (proethica-intermediate)
- ↳ UnfamiliarToolCompetenceConstraint
Definition
Competence constraint limiting an engineer's permissible use of a tool, technology, or method with which they lack sufficient experience or understanding, requiring that the engineer either acquire adequate competence before use, limit reliance on the tool's outputs, or obtain qualified assistance, so that professional work products meet required standards.
Inherited from CompetenceConstraint
Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022)
Case Provenance
Discovered in
This class was discovered during extraction of the case(s) above; the supporting verbatim quotes are in Source Evidence.
Properties
Affected Stakeholders
Client
Engineer
Public
Confidence
0.84
Constraint Type
competence
Flexibility
soft
Mitigation Strategies
Disclose tool limitations and unfamiliarity to the client and seek consent before proceeding
Engage a colleague with relevant tool expertise to review outputs
Limit use of unfamiliar tools to non-critical or supplementary tasks until competence is established
Obtain training or experience with a new tool before using it for client deliverables
Violation Impact
Deficient work products, public safety risk, regulatory non-compliance, and professional liability arising from reliance on tool outputs the engineer cannot adequately evaluate.
Property Structure
1 · Object and Data Properties
rdfs:domain on this class or ancestor
| Property | Range | Description |
|---|---|---|
| constrainedEntity inherited | Agent | Relates a Constraint to the Agent whose conduct it limits in the case scenario. Distinct from constrainedBy (Action -> Constraint), which records that an action is subject to a constraint. |
| establishedBy inherited | CodeProvision | Indicates which code provision establishes this ethical concept. |
2 · Definitional Attributes
SHACL definitional shape
| Attribute | Property (sh:path) | Description |
|---|---|---|
| boundary type | boundaryType | The controlled boundary type, which drives the subClassOf typing into one of the ten closed boundary-type classes: LegalConstraint, RegulatoryConstraint, ResourceConstraint, CompetenceConstraint, JurisdictionalConstraint, ProceduralConstraint, EthicalConstraint, SafetyConstraint, ConfidentialityConstraint, TemporalConstraint. The prohibition/boundary content that individuates the type. A routing input, not stored as a literal. |
| established by | establishedBy | The source CodeProvision that establishes the constraint, via the establishedBy edge. The second type-individuating coordinate: per the scopeNote a constraint type is the boundary it states plus its source provision. Range: CodeProvision. |
3 · Bearer Attributes
SHACL property shape
individual data
| Attribute | Property (sh:path) | Description |
|---|---|---|
| severity | severity | The severity of the constraint in this case (critical, high, medium, low); a per-occasion assessment (Dennis severity ordering) that can differ across cases sharing the same boundary. |
| applicability condition | applicabilityCondition | The situational TRIGGER: the circumstances under which the prohibition applies in this case (the Dennis specification-by-context condition); temporalScope carries the durational window. |
| constrained entity | constrainedEntity | The agent whose conduct the constraint limits, via the outgoing constrainedEntity edge. Range: Agent. |
| temporal scope | temporalScope | The durational WINDOW during which the boundary is in force in this case (e.g. for the duration of the engagement); applicabilityCondition carries the situational trigger under which it applies. |
| source | source | The provision or authority string as extracted, kept verbatim on the individual; each dotted NSPE designation that resolves against the provision registry is also materialized as the establishedBy edge (a non-code source survives only in this literal). |
| constraint statement | constraintStatement | The operative must-not clause, kept verbatim; mirrors skos:definition and is one of the narrative source fields the defeasibility harvest reads from committed TTLs. |
4 · Referenced By
rdfs:range on this class or ancestor
| From | Property | Description |
|---|---|---|
| Action | constrainedBy inherited | Relates an action to constraints that limit or restrict it. The ratified D1 producer (an Action-pass action_constraints field resolved to this edge) shipped without its emitter; the edge is reserved with the Action-side enrichment family (usesResource pattern) and the producer lands with the Step-4 enrichment or the 119 rebuild. Do not deprecate on the zero-use test. |
| Code Provision | establishes inherited | Relates a code provision to the ethical concepts (principles, obligations, constraints) it establishes or defines. |
| State | activatesConstraint inherited | Relates a State to a Constraint that the obtaining of the State activates, bounding the actions available to the role-bearers the state concerns (the S->Cs linkage). |
Source Evidence
Text references
Not being familiar with the full functionality of the AI software, including the accuracy and originality of AI-generated text
The AI drafting software was new to the market and Engineer A had no previous experience with the tool.
Source text
The AI drafting software was new to the market and Engineer A had no previous experience with the tool.
Used in cases 1
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 120@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:UnfamiliarToolCompetenceConstraint a owl:Class ;
rdfs:label "Unfamiliar Tool Competence Constraint" ;
proeth:affectedStakeholders "Client",
"Engineer",
"Public" ;
proeth:confidence "0.84" ;
proeth:constraintType "competence" ;
proeth:flexibility "soft" ;
proeth:mitigationStrategies "Disclose tool limitations and unfamiliarity to the client and seek consent before proceeding",
"Engage a colleague with relevant tool expertise to review outputs",
"Limit use of unfamiliar tools to non-critical or supplementary tasks until competence is established",
"Obtain training or experience with a new tool before using it for client deliverables" ;
proeth:textReferences "Not being familiar with the full functionality of the AI software, including the accuracy and originality of AI-generated text",
"The AI drafting software was new to the market and Engineer A had no previous experience with the tool." ;
proeth:violationImpact "Deficient work products, public safety risk, regulatory non-compliance, and professional liability arising from reliance on tool outputs the engineer cannot adequately evaluate." ;
proeth-prov:discoveredInCase 7 ;
proeth-prov:discoveredInPass 2 ;
proeth-prov:discoveredInSection "facts" ;
proeth-prov:firstDiscoveredAt "2026-06-03T14:06:33.588436+00:00"^^xsd:dateTime ;
proeth-prov:firstDiscoveredInCase 7 ;
proeth-prov:matchConfidence 0.78 ;
proeth-prov:matchReasoning "The existing Competence Constraint class covers boundaries defined by agent capabilities and technical limitations, which encompasses this scenario. The unfamiliar tool variant is a specific application of that general class. Matching as a variant at medium confidence while defining a more specific reusable subtype for unfamiliar tool deployment contexts." ;
proeth-prov:matchedOntologyClass proeth:CompetenceConstraint ;
proeth-prov:matchedOntologyLabel "Competence Constraint" ;
proeth-prov:matchesExisting true ;
proeth-prov:sourceText "The AI drafting software was new to the market and Engineer A had no previous experience with the tool." ;
rdfs:comment "Competence constraint limiting an engineer's permissible use of a tool, technology, or method with which they lack sufficient experience or understanding, requiring that the engineer either acquire adequate competence before use, limit reliance on the tool's outputs, or obtain qualified assistance, so that professional work products meet required standards." ;
rdfs:subClassOf proeth:CompetenceConstraint,
proeth:DefeasibleConstraint ;
skos:definition "Competence constraint limiting an engineer's permissible use of a tool, technology, or method with which they lack sufficient experience or understanding, requiring that the engineer either acquire adequate competence before use, limit reliance on the tool's outputs, or obtain qualified assistance, so that professional work products meet required standards." ;
skos:scopeNote "[CompetenceConstraint] Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022)" ;
prov:generatedAtTime "2026-06-03T14:06:33.588436+00:00"^^xsd:dateTime ;
prov:wasAttributedTo "Case 7 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:ConstraintDefinitionShape a sh:NodeShape ;
rdfs:label "Constraint definition schema (type-level, descriptive, field contract)"@en ;
rdfs:comment "What individuates a constraint TYPE: the boundary it states (boundary_type, which drives the subClassOf typing into one of the ten closed boundary-type classes) and the source provision that establishes it. The per-case severity and applicability, the agent it limits, and the action it bounds are per-individual and declared on ConstraintPropertyShape, mirroring the R/P/O/S/Rs/Ca Definition/Property split and the constraint scopeNote (the TYPE is the prohibition plus its source provision; the constrained party, per-occasion applicability, and any exception attach to the case individual). Descriptive only (no validation result); the routing input is the constraint_type schema field (the boundaryType property is its shape-path anchor), not stored as a literal."@en ;
sh:property [ sh:description "The controlled boundary type, which drives the subClassOf typing into one of the ten closed boundary-type classes: LegalConstraint, RegulatoryConstraint, ResourceConstraint, CompetenceConstraint, JurisdictionalConstraint, ProceduralConstraint, EthicalConstraint, SafetyConstraint, ConfidentialityConstraint, TemporalConstraint. The prohibition/boundary content that individuates the type. A routing input, not stored as a literal." ;
sh:name "boundary type" ;
sh:order 1 ;
sh:path proeth:boundaryType ],
[ pcsh:informationalOnly true ;
sh:description "The source CodeProvision that establishes the constraint, via the establishedBy edge. The second type-individuating coordinate: per the scopeNote a constraint type is the boundary it states plus its source provision. Range: CodeProvision." ;
sh:name "established by" ;
sh:order 2 ;
sh:path core:establishedBy ] ;
sh:targetClass core:Constraint .
pcsh:ConstraintPropertyShape a sh:NodeShape ;
rdfs:label "Constraint per-case schema (individual data, non-definitional)"@en ;
rdfs:comment "What a given constraint INDIVIDUAL is described by in a specific case: its per-occasion severity and applicability window, the agent whose conduct it limits, and the action it bounds. These do NOT individuate the constraint TYPE (that is ConstraintDefinitionShape, keyed on the boundary it states and its source provision); their values are per-case, asserted on the individual. Descriptive only."@en ;
sh:property [ sh:description "The severity of the constraint in this case (critical, high, medium, low); a per-occasion assessment (Dennis severity ordering) that can differ across cases sharing the same boundary." ;
sh:name "severity" ;
sh:order 1 ;
sh:path proeth:severity ],
[ sh:description "The situational TRIGGER: the circumstances under which the prohibition applies in this case (the Dennis specification-by-context condition); temporalScope carries the durational window." ;
sh:name "applicability condition" ;
sh:order 2 ;
sh:path proeth:applicabilityCondition ],
[ sh:description "The agent whose conduct the constraint limits, via the outgoing constrainedEntity edge. Range: Agent." ;
sh:name "constrained entity" ;
sh:order 3 ;
sh:path core:constrainedEntity ],
[ sh:description "The durational WINDOW during which the boundary is in force in this case (e.g. for the duration of the engagement); applicabilityCondition carries the situational trigger under which it applies." ;
sh:name "temporal scope" ;
sh:order 4 ;
sh:path proeth:temporalScope ],
[ sh:description "The provision or authority string as extracted, kept verbatim on the individual; each dotted NSPE designation that resolves against the provision registry is also materialized as the establishedBy edge (a non-code source survives only in this literal)." ;
sh:name "source" ;
sh:order 5 ;
sh:path proeth:source ],
[ sh:description "The operative must-not clause, kept verbatim; mirrors skos:definition and is one of the narrative source fields the defeasibility harvest reads from committed TTLs." ;
sh:name "constraint statement" ;
sh:order 6 ;
sh:path proeth:constraintStatement ] ;
sh:targetClass core:Constraint .
Metadata
Extraction details
Discovered in case
7
Discovered in pass
2
Discovered in section
facts
First discovered
2026-06-03T14:06:33.588436+00:00
First case
7
Match Confidence
0.78
Match Reasoning
The existing Competence Constraint class covers boundaries defined by agent capabilities and technical limitations, which encompasses this scenario. The unfamiliar tool variant is a specific application of that general class. Matching as a variant at medium confidence while defining a more specific reusable subtype for unfamiliar tool deployment contexts.
Matched Ontology Label
Competence Constraint
Matches Existing
true
Generated
2026-06-03T14:06:33.588436+00:00
Attributed to
['Case 7 Extraction', 'claude-sonnet-4-6']