Engineer M Graduated Escalation City After Firm DBA Non-Compliance
O · Obligation
Individual
http://proethica.org/ontology/case/5#Engineer_M_Graduated_Escalation_City_After_Firm_DBA_Non-Compliance
Properties
Instance of
GraduatedEscalationtoClientAfterSubcontractorNon-ComplianceObligation
http://proethica.org/ontology/intermediate#GraduatedEscalationtoClientAfterSubcontractorNon-ComplianceObligation
Case context
Firm DBA may take the position that it performed work under City direction and refuse to make corrections; Engineer M must then escalate to the City before reporting to the licensure board.
Compliance status
unclear
Confidence
0.85
Importance
high
Obligated party
Engineer M (Lead Infrastructure Project Engineer)
Obligation statement
If Firm DBA refused to correct the discrepancies in its public engagement report, Engineer M was obligated to escalate the matter to the City — with the knowledge and potential presence of Firm DBA — and to present the ethical obligations of all parties before proceeding to external regulatory reporting.
Temporal scope
After Firm DBA's refusal to correct discrepancies, and before or in conjunction with external reporting
Relationships
competesWith
Engineer M Licensure Board Reporting Firm DBA After City Inaction, Engineer M Subcontract or Ethical Compliance Oversight Firm DBA
defeasibleUnder
Engineer M Subconsultant Ethical Non-Compliance with Firm DBA, Internal Escalation Exhausted — Engineer M Post-City Meeting
derivedFromPrinciple
Escalating Confrontation Obligation - Engineer M Escalation Sequence
Source Evidence
Source text
Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved.
Text references
A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections.
Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved.
TTL
@prefix case5: <http://proethica.org/ontology/case/5#> .
@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#> .
case5:Engineer_M_Graduated_Escalation_City_After_Firm_DBA_Non-Compliance a proeth:GraduatedEscalationtoClientAfterSubcontractorNon-ComplianceObligation,
owl:NamedIndividual ;
rdfs:label "Engineer M Graduated Escalation City After Firm DBA Non-Compliance" ;
proeth-core:competesWith case5:Engineer_M_Licensure_Board_Reporting_Firm_DBA_After_City_Inaction,
case5:Engineer_M_Subcontractor_Ethical_Compliance_Oversight_Firm_DBA ;
proeth-core:defeasibleUnder case5:Engineer_M_Subconsultant_Ethical_Non-Compliance_with_Firm_DBA,
<http://proethica.org/ontology/case/5#Internal_Escalation_Exhausted_—_Engineer_M_Post-City_Meeting> ;
proeth:casecontext "Firm DBA may take the position that it performed work under City direction and refuse to make corrections; Engineer M must then escalate to the City before reporting to the licensure board." ;
proeth:compliancestatus "unclear" ;
proeth:conceptCategory "Obligation" ;
proeth:confidence "0.85" ;
proeth:derivedFromPrinciple case5:Escalating_Confrontation_Obligation_-_Engineer_M_Escalation_Sequence ;
proeth:discoveredincase "5" ;
proeth:discoveredinpass "2" ;
proeth:discoveredinsection "discussion" ;
proeth:firstdiscoveredat "2026-02-24T13:58:20.317156+00:00" ;
proeth:firstdiscoveredincase "5" ;
proeth:generatedattime "2026-02-24T13:58:20.317156+00:00" ;
proeth:importance "high" ;
proeth:obligatedparty "Engineer M (Lead Infrastructure Project Engineer)" ;
proeth:obligationclass "Graduated Escalation to Client After Subcontractor Non-Compliance Obligation" ;
proeth:obligationstatement "If Firm DBA refused to correct the discrepancies in its public engagement report, Engineer M was obligated to escalate the matter to the City — with the knowledge and potential presence of Firm DBA — and to present the ethical obligations of all parties before proceeding to external regulatory reporting." ;
proeth:sourcetext "Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved." ;
proeth:temporalscope "After Firm DBA's refusal to correct discrepancies, and before or in conjunction with external reporting" ;
proeth:textreferences "A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections.",
"Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved." ;
proeth:wasattributedto "Case 5 Extraction" ;
prov:generatedAtTime "2026-02-24T14:07:05.451383"^^xsd:dateTime ;
prov:wasGeneratedBy "ProEthica Case 5 Extraction" .
Metadata
Extraction details
Discovered in case
5
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-02-24T13:58:20.317156+00:00
First case
5
Generated
2026-02-24T13:58:20.317156+00:00
Attributed to
Case 5 Extraction
Generated
2026-02-24T14:07:05.451383
Generated by
ProEthica Case 5 Extraction