Obligation-Conflict Resolution

Case 88-6 (1988) · Whistleblowing - City Engineer

Professional obligations conflict, and the board applies no fixed rule for which one wins. Each resolution is recorded as three edges: competesWith (the tension), prevailsOver (the obligation the board allowed to win in this case), and defeasibleUnder (the situation under which the yielding obligation gives way). The same tension is then traced across comparable cases, where its resolution shifts with context. Hover any obligation or state to see its definition; click to open it in OntServe.
How this case resolved it competition structure in OntServe
Engineer A Project Withdrawal Duty prevails over Engineer A Faithful Agent Duty
the two obligations are in tension (competesWith)
the yielding obligation gives way only under (defeasibleUnder):
  • Loyalty Versus Public Protection Conflict
Featured
Engineer A Proper Authority Reporting Duty prevails over Engineer A Faithful Agent Duty
the two obligations are in tension (competesWith)
the yielding obligation gives way only under (defeasibleUnder):
  • Loyalty Versus Public Protection Conflict
Open tensions recorded without a resolution: Engineer A Faithful Agent Duty vs Engineer A Public Safety Duty
What the board concluded
  • Engineer A did not fulfill her ethical obligations by informing the City Administrator and certain members of the city council of her concerns.
Recorded violations: Covert Advisory Continuation violates Engineer A Project Withdrawal Duty Failure to Report Externally violates Engineer A Public Safety Duty Covert Advisory Continuation violates Engineer A Authority Circumvention Reporting Duty Failure to Report Externally violates Engineer A Proper Authority Reporting Duty
How comparable cases resolved this and related tensions

Read at the type level, this resolution is: Faithful Agent Obligation yields to Safety Withdrawaland Notification Obligation. Comparison across cases happens at this level; the duty types recur while each case's obligations instantiate them. Cases below are grouped by how much of that pairing they share. A duty type that yields here may prevail elsewhere, which is the context-dependence itself, not an inconsistency.

Same tension: both duty types match, so the board ruled on this exact pairing. Related tension: only one duty type matches; the other duty differs, so these show how a type behaves elsewhere rather than a ruling on this pairing.

Case Prevailing type Yielding type Relation to this case
Related tension: one duty type matches (14)

Closest instance-level matches, ranked on the specific obligations and contexts of this case:

Case Obligation that prevailed Yielding obligation Context (defeasibleUnder)
89-7
Duty To Report Safety Violations
Engineer A Authority Notification Duty Engineer A Faithful Agent Duty Code Exception Disclosure Release
24-1
Balancing Client Directives and Public...
Engineer L Watershed Safety Duty Engineer L Faithful Agent Duty Public Safety Faithful Agent Conflict
76-4
Public Welfare - Knowledge of Information...
Engineer Doe Authority Reporting Duty Engineer Doe Faithful Agent Duty No Written Report Directive
82-2
Confidentiality of Engineering Report
Engineer A Client Confidentiality Duty Engineer A Faithful Agent Duty Engineer A Good Faith Assumption; Report Copy Sent to Realty Firm
96-8
Peer Review - Confidentiality Agreements
Engineer A Authority Cooperation Duty Engineer A Confidentiality Duty Confidentiality Versus Cooperation Dilemma