Engineer A Advisory Completeness
Cs · Constraint
Individual
http://proethica.org/ontology/case/14#Engineer_A_Advisory_Completeness
Definition
Engineer A was prohibited from presenting only a subset of the four funding-agency-approved delivery methods in the advisory memo to City B Administrator. The advisory role required presenting all four approved options so that City B could make an informed selection.
Properties
Instance of
AdvisoryScopeCompletenessConstraint
http://proethica.org/ontology/intermediate#AdvisoryScopeCompletenessConstraint
Case context
Engineer A, with no existing contract with City B, was asked by the City Administrator (a non-engineer) to advise on project delivery methods for a wastewater improvement project under a specific funding source. Four methods were approved by the funding agency. Engineer A's memo identified only two, omitting Construction-Manager-at-Risk and Fixed-Price-Design-Build, and recommended Progressive-Design-Build, a method under which Engineer A is qualified to provide services.
Confidence
0.9
Constraint statement
Engineer A was prohibited from presenting only a subset of the four funding-agency-approved delivery methods in the advisory memo to City B Administrator. The advisory role required presenting all four approved options so that City B could make an informed selection.
Severity
high
Source
NSPE Code of Ethics, Section II.2 (Engineers shall perform services only in areas of their competence) and Section III.2 (Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession)
Temporal scope
At the time Engineer A prepared and submitted the advisory memo to City B Administrator
Match Confidence
0.72
Match Reasoning
Via class 'Advisory Scope Completeness Constraint': The selective omission of options is driven by a conflict of interest and partially maps to Conflict of Interest Avoidance. However, the specific mechanism here is the completeness of advisory disclosure rather than merely the existence of a conflict, making this a variant that warrants a distinct class. The closest existing class is Conflict of Interest Avoidance but it does not capture the affirmative duty to present all options.
Matched Ontology Label
Conflict of Interest Avoidance (Constraint)
Matches Existing
true
Synthesis Literal
caseContext
confidence
constraintClass
constraintStatement
severity
source
temporalScope
textReferences
Relationships
constrainedEntity
Agent Engineer A
Source Evidence
Text references
Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
Source text
Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
TTL
@prefix case14: <http://proethica.org/ontology/case/14#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix proeth-core: <http://proethica.org/ontology/core#> .
@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 skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
case14:Engineer_A_Advisory_Completeness a proeth:AdvisoryScopeCompletenessConstraint,
owl:NamedIndividual ;
rdfs:label "Engineer A Advisory Completeness" ;
proeth-core:constrainedEntity case14:Agent_Engineer_A ;
proeth:caseContext "Engineer A, with no existing contract with City B, was asked by the City Administrator (a non-engineer) to advise on project delivery methods for a wastewater improvement project under a specific funding source. Four methods were approved by the funding agency. Engineer A's memo identified only two, omitting Construction-Manager-at-Risk and Fixed-Price-Design-Build, and recommended Progressive-Design-Build, a method under which Engineer A is qualified to provide services." ;
proeth:conceptCategory "Constraint" ;
proeth:confidence "0.9" ;
proeth:constrainedEntity "Engineer A" ;
proeth:constraintClass "Advisory Scope Completeness Constraint" ;
proeth:constraintStatement "Engineer A was prohibited from presenting only a subset of the four funding-agency-approved delivery methods in the advisory memo to City B Administrator. The advisory role required presenting all four approved options so that City B could make an informed selection." ;
proeth:severity "high" ;
proeth:source "NSPE Code of Ethics, Section II.2 (Engineers shall perform services only in areas of their competence) and Section III.2 (Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession)" ;
proeth:temporalScope "At the time Engineer A prepared and submitted the advisory memo to City B Administrator" ;
proeth:textReferences "Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.",
"Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build." ;
proeth-prov:discoveredInCase 14 ;
proeth-prov:discoveredInPass 2 ;
proeth-prov:discoveredInSection "facts" ;
proeth-prov:firstDiscoveredAt "2026-06-04T08:45:47.831992+00:00"^^xsd:dateTime ;
proeth-prov:firstDiscoveredInCase 14 ;
proeth-prov:matchConfidence 0.72 ;
proeth-prov:matchReasoning "Via class 'Advisory Scope Completeness Constraint': The selective omission of options is driven by a conflict of interest and partially maps to Conflict of Interest Avoidance. However, the specific mechanism here is the completeness of advisory disclosure rather than merely the existence of a conflict, making this a variant that warrants a distinct class. The closest existing class is Conflict of Interest Avoidance but it does not capture the affirmative duty to present all options." ;
proeth-prov:matchedOntologyClass <http://proethica.org/ontology/concepts#Conflict_of_Interest_Avoidance> ;
proeth-prov:matchedOntologyLabel "Conflict of Interest Avoidance (Constraint)" ;
proeth-prov:matchesExisting true ;
proeth-prov:sourceText "Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options." ;
proeth-prov:synthesisLiteral "caseContext",
"confidence",
"constraintClass",
"constraintStatement",
"severity",
"source",
"temporalScope",
"textReferences" ;
rdfs:comment "Engineer A was prohibited from presenting only a subset of the four funding-agency-approved delivery methods in the advisory memo to City B Administrator. The advisory role required presenting all four approved options so that City B could make an informed selection." ;
skos:definition "Engineer A was prohibited from presenting only a subset of the four funding-agency-approved delivery methods in the advisory memo to City B Administrator. The advisory role required presenting all four approved options so that City B could make an informed selection." ;
prov:generatedAtTime "2026-06-04T08:45:47.831992+00:00"^^xsd:dateTime ;
prov:wasAttributedTo "Case 14 Extraction",
"claude-sonnet-4-6" ;
prov:wasGeneratedBy "ProEthica Case 14 Extraction" .
Metadata
Extraction details
Discovered in case
14
Discovered in pass
2
Discovered in section
facts
First discovered
2026-06-04T08:45:47.831992+00:00
First case
14
Generated
2026-06-04T08:45:47.831992+00:00
Attributed to
['Case 14 Extraction', 'claude-sonnet-4-6']
Generated by
ProEthica Case 14 Extraction