ScopeOfPracticeCompetenceConstraint

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

A boundary on an agent's authority to make a determination that belongs to another party or process, here the limit that the determination of whether a design error was made is not up to the engineer but is for the legal process to determine, so the engineer should not voluntarily characterize the work as an error.

Inherited from Case 121

A boundary statement limiting the permissible action space by reference to the agent's competence: an engineer must not offer or perform professional services in areas outside their demonstrated competence.

Inherited from JurisdictionalConstraint

Boundaries of authority and geographical or organizational scope (Dennis et al. 2016)

Case Provenance
Discovered in
This class was discovered during extraction of the case(s) above; the supporting verbatim quotes are in Source Evidence.
Properties
Confidence
0.85
Constraint Type
jurisdictional
Property Structure
1 · Object and Data Properties rdfs:domain on this class or ancestor
PropertyRangeDescription
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
AttributeProperty (sh:path)Description
boundary typeboundaryTypeThe 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 byestablishedByThe 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
AttributeProperty (sh:path)Description
severityseverityThe 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 conditionapplicabilityConditionThe situational TRIGGER: the circumstances under which the prohibition applies in this case (the Dennis specification-by-context condition); temporalScope carries the durational window.
constrained entityconstrainedEntityThe agent whose conduct the constraint limits, via the outgoing constrainedEntity edge. Range: Agent.
temporal scopetemporalScopeThe 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.
sourcesourceThe 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 statementconstraintStatementThe 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
FromPropertyDescription
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
Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error
whether an error was made was not up to Engineer T and was not clear in this set of circumstances

Source text
They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error.
Used in cases 2

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 9 Case 57
@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:ScopeOfPracticeCompetenceConstraint a owl:Class ; rdfs:label "ScopeOfPracticeCompetenceConstraint" ; proeth:confidence "0.85" ; proeth:constraintType "jurisdictional" ; proeth:textReferences "Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error", "whether an error was made was not up to Engineer T and was not clear in this set of circumstances" ; proeth-prov:discoveredInCase 9, 121 ; proeth-prov:discoveredInPass 2 ; proeth-prov:discoveredInSection "facts" ; proeth-prov:firstDiscoveredAt "2026-07-05T05:17:43.973597+00:00"^^xsd:dateTime ; proeth-prov:firstDiscoveredInCase 9 ; proeth-prov:matchConfidence 0.88 ; proeth-prov:matchReasoning "This is a boundary of authority: the determination of error is assigned to the legal process, not to Engineer T. It fits the canonical Jurisdictional Constraint (boundaries of authority and scope); the deposition-specific detail is carried on the individual as literals rather than in a new compound class." ; proeth-prov:matchedOntologyClass proeth:JurisdictionalConstraint ; proeth-prov:matchedOntologyLabel "Jurisdictional Constraint" ; proeth-prov:matchesExisting true ; proeth-prov:sourceText "They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error." ; rdfs:comment "A boundary on an agent's authority to make a determination that belongs to another party or process, here the limit that the determination of whether a design error was made is not up to the engineer but is for the legal process to determine, so the engineer should not voluntarily characterize the work as an error." ; rdfs:subClassOf proeth:CompetenceConstraint, proeth:JurisdictionalConstraint ; skos:definition "A boundary on an agent's authority to make a determination that belongs to another party or process, here the limit that the determination of whether a design error was made is not up to the engineer but is for the legal process to determine, so the engineer should not voluntarily characterize the work as an error." ; skos:scopeNote "[Case 121] A boundary statement limiting the permissible action space by reference to the agent's competence: an engineer must not offer or perform professional services in areas outside their demonstrated competence.", "[JurisdictionalConstraint] Boundaries of authority and geographical or organizational scope (Dennis et al. 2016)" ; prov:generatedAtTime "2026-07-05T05:17:43.973597+00:00"^^xsd:dateTime ; prov:wasAttributedTo "Case 9 Extraction", "claude-fable-5" . 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
Type
Class
Last Updated
2026-07-05 15:17
Discovered in case
['9', '121']
Discovered in pass
2
Discovered in section
facts
First discovered
2026-07-05T05:17:43.973597+00:00
First case
9
Match Confidence
0.88
Match Reasoning
This is a boundary of authority: the determination of error is assigned to the legal process, not to Engineer T. It fits the canonical Jurisdictional Constraint (boundaries of authority and scope); the deposition-specific detail is carried on the individual as literals rather than in a new compound class.
Matched Ontology Label
Jurisdictional Constraint
Matches Existing
true
Generated
2026-07-05T05:17:43.973597+00:00
Attributed to
['Case 9 Extraction', 'claude-fable-5']