Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict
O · Obligation
Individual
http://proethica.org/ontology/case/144#Engineer_A_Cross-Domain_Same-Client_DOT_Highway_Airport_Municipal_Conflict
Properties
Instance of
Cross-DomainSame-ClientGovernment-PrivateConsultingNon-EngagementObligation
http://proethica.org/ontology/intermediate#Cross-DomainSame-ClientGovernment-PrivateConsultingNon-EngagementObligation
Case context
The municipalities that submit traffic signal plans to Engineer A's DOT division for review are the same class of entities for whom the former consulting firm proposed private airport consulting services, creating a cross-domain same-client conflict.
Compliance status
unmet
Confidence
0.91
Importance
high
Obligated party
Engineer A (State DOT Traffic Engineer)
Obligation statement
Engineer A was obligated to refrain from accepting private airport consulting work for municipalities that are the same entities Engineer A reviews in the governmental highway traffic signal plan review function, recognizing that the shared client relationship creates a structural conflict of interest regardless of the technical domain distinction.
Temporal scope
At the time of solicitation and before acceptance of the private consulting engagement
Relationships
Source Evidence
Source text
the Board can easily foresee the potential for a conflict of interest for Engineer A in his relations with municipality's work as a state highway employee and in his relations with the same municipalities as a representative for the consulting firm working on municipal airports
Text references
While the scope of his responsibilities (state highways vs. airports) are clearly different, there may be situations and circumstances where his role in one or another area could be compromised
the Board can easily foresee the potential for a conflict of interest for Engineer A in his relations with municipality's work as a state highway employee and in his relations with the same municipalities as a representative for the consulting firm working on municipal airports
TTL
@prefix case144: <http://proethica.org/ontology/case/144#> .
@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 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#> .
case144:Engineer_A_Cross-Domain_Same-Client_DOT_Highway_Airport_Municipal_Conflict a proeth:Cross-DomainSame-ClientGovernment-PrivateConsultingNon-EngagementObligation,
owl:NamedIndividual ;
rdfs:label "Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict" ;
proeth-core:competesWith case144:Engineer_A_Employer_Awareness_Non-Sufficiency_Structural_Conflict_DOT_Airport ;
proeth-core:defeasibleUnder <http://proethica.org/ontology/case/144#Engineer_A_Adjacent_Domain_Dual_Employment_Conflict_—_Highways_vs._Airports> ;
proeth:casecontext "The municipalities that submit traffic signal plans to Engineer A's DOT division for review are the same class of entities for whom the former consulting firm proposed private airport consulting services, creating a cross-domain same-client conflict." ;
proeth:compliancestatus "unmet" ;
proeth:conceptCategory "Obligation" ;
proeth:confidence "0.91" ;
proeth:derivedFromPrinciple case144:Cross-Domain_Same-Client_Conflict_Applied_to_Engineer_A_Highway-Airport_Roles,
case144:Cross-Domain_Same-Client_Conflict_Invoked_for_Engineer_A_Municipal_Overlap ;
proeth:discoveredincase "144" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "discussion" ;
proeth:firstdiscoveredat "2026-02-28T23:48:34.150091+00:00" ;
proeth:firstdiscoveredincase "144" ;
proeth:generatedattime "2026-02-28T23:48:34.150091+00:00" ;
proeth:importance "high" ;
proeth:obligatedparty "Engineer A (State DOT Traffic Engineer)" ;
proeth:obligationclass "Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation" ;
proeth:obligationstatement "Engineer A was obligated to refrain from accepting private airport consulting work for municipalities that are the same entities Engineer A reviews in the governmental highway traffic signal plan review function, recognizing that the shared client relationship creates a structural conflict of interest regardless of the technical domain distinction." ;
proeth:sourcetext "the Board can easily foresee the potential for a conflict of interest for Engineer A in his relations with municipality's work as a state highway employee and in his relations with the same municipalities as a representative for the consulting firm working on municipal airports" ;
proeth:temporalscope "At the time of solicitation and before acceptance of the private consulting engagement" ;
proeth:textreferences "While the scope of his responsibilities (state highways vs. airports) are clearly different, there may be situations and circumstances where his role in one or another area could be compromised",
"the Board can easily foresee the potential for a conflict of interest for Engineer A in his relations with municipality's work as a state highway employee and in his relations with the same municipalities as a representative for the consulting firm working on municipal airports" ;
proeth:wasattributedto "Case 144 Extraction" ;
prov:generatedAtTime "2026-02-28T23:57:16.250176"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 144 Extraction" .
Metadata
Extraction details
Discovered in case
144
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-02-28T23:48:34.150091+00:00
First case
144
Generated
2026-02-28T23:48:34.150091+00:00
Attributed to
Case 144 Extraction
Generated
2026-02-28T23:57:16.250176
Generated by
ProEthica Case 144 Extraction