Competence Boundary Recognition — Engineer A Military Certification Refusal
P · Principle
Individual
http://proethica.org/ontology/case/109#Competence_Boundary_Recognition_—_Engineer_A_Military_Certification_Refusal
Properties
Instance of
CompetenceBoundaryRecognitionandEscalationObligation
http://proethica.org/ontology/intermediate#CompetenceBoundaryRecognitionandEscalationObligation
Applied to
Certification of arms storage room and rack compliance with Army physical security, arms, ammunition, and explosive regulations
Balancing with
Employer and Client Pressure Non-Exemption from Competence Boundary
Institutional Role Non-Expansion of Technical Competence Scope
Concrete expression
Engineer A, a civil engineer, recognizes that certifying compliance with detailed Army physical security, arms, ammunition, and explosive regulations is outside Engineer A's domain competence, and refuses to provide the certification — fulfilling the obligation to recognize and act upon the competence limitation rather than proceeding under institutional pressure.
Confidence
0.96
Importance
high
Interpretation
The competence boundary is defined not by general PE licensure or institutional role title but by actual domain expertise in the specific technical and regulatory framework at issue; civil engineering competence does not extend to military physical security and arms storage regulatory compliance.
Invoked by
Engineer A Current Case Military Certification Refuser
Tension resolution
Recognition of the competence boundary triggers the obligation to refuse and, where appropriate, escalate to ensure a competent engineer is engaged.
Source Evidence
Source text
While Engineer A may be a very competent engineer, Engineer A is clearly not knowledgeable in this very technical and complicated area.
Text references
Making certain that a military hardware storage facility is designed and built safely involves keen awareness of many complex and detailed procedures, rules, and regulations that are unique to this field of endeavor.
While Engineer A may be a very competent engineer, Engineer A is clearly not knowledgeable in this very technical and complicated area.
the obligation of the engineer to practice solely within the engineer's area of professional competency (See Code Section II.2.a.)
TTL
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<http://proethica.org/ontology/case/109#Competence_Boundary_Recognition_—_Engineer_A_Military_Certification_Refusal> a proeth:CompetenceBoundaryRecognitionandEscalationObligation,
owl:NamedIndividual ;
rdfs:label "Competence Boundary Recognition — Engineer A Military Certification Refusal" ;
proeth:appliedto "Certification of arms storage room and rack compliance with Army physical security, arms, ammunition, and explosive regulations" ;
proeth:balancingwith "Employer and Client Pressure Non-Exemption from Competence Boundary",
"Institutional Role Non-Expansion of Technical Competence Scope" ;
proeth:conceptCategory "Principle" ;
proeth:concreteexpression "Engineer A, a civil engineer, recognizes that certifying compliance with detailed Army physical security, arms, ammunition, and explosive regulations is outside Engineer A's domain competence, and refuses to provide the certification — fulfilling the obligation to recognize and act upon the competence limitation rather than proceeding under institutional pressure." ;
proeth:confidence "0.96" ;
proeth:discoveredincase "109" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "discussion" ;
proeth:firstdiscoveredat "2026-03-01T07:46:37.426878+00:00" ;
proeth:firstdiscoveredincase "109" ;
proeth:generatedattime "2026-03-01T07:46:37.426878+00:00" ;
proeth:importance "high" ;
proeth:interpretation "The competence boundary is defined not by general PE licensure or institutional role title but by actual domain expertise in the specific technical and regulatory framework at issue; civil engineering competence does not extend to military physical security and arms storage regulatory compliance." ;
proeth:invokedby "Engineer A Current Case Military Certification Refuser" ;
proeth:principleclass "Competence Boundary Recognition and Escalation Obligation" ;
proeth:sourcetext "While Engineer A may be a very competent engineer, Engineer A is clearly not knowledgeable in this very technical and complicated area." ;
proeth:tensionresolution "Recognition of the competence boundary triggers the obligation to refuse and, where appropriate, escalate to ensure a competent engineer is engaged." ;
proeth:textreferences "Making certain that a military hardware storage facility is designed and built safely involves keen awareness of many complex and detailed procedures, rules, and regulations that are unique to this field of endeavor.",
"While Engineer A may be a very competent engineer, Engineer A is clearly not knowledgeable in this very technical and complicated area.",
"the obligation of the engineer to practice solely within the engineer's area of professional competency (See Code Section II.2.a.)" ;
proeth:wasattributedto "Case 109 Extraction" ;
prov:generatedAtTime "2026-03-01T07:59:20.016983"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 109 Extraction" .
Metadata
Extraction details
Discovered in case
109
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-03-01T07:46:37.426878+00:00
First case
109
Generated
2026-03-01T07:46:37.426878+00:00
Attributed to
Case 109 Extraction
Generated
2026-03-01T07:59:20.016983
Generated by
ProEthica Case 109 Extraction