# Reconcile a metric that two dashboards report differently

One metric, two dashboards, two numbers, resolved to a single definition both read from.

Category: Pipelines and warehouse
Source: https://letsship.ai/use-cases/reconcile-a-disputed-metric
Published: 2026-08-25

## Goal

Reconcile a metric that two dashboards report differently and give both one definition.

## Acceptance criteria

- The cause of the difference is identified and written down
- One definition is agreed and implemented once
- Both dashboards read from that definition
- The historical difference is explained for anybody who saw both

## What lands as proof

A written explanation of the discrepancy plus both dashboards reading a single implementation.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Reconcile {metric} across dashboards

Description: Reconcile a metric that two dashboards report differently and give both one definition.

Acceptance criteria:
- The cause of the difference is identified and written down
- One definition is agreed and implemented once
- Both dashboards read from that definition
- The historical difference is explained for anybody who saw both

Before you create the issue, find two dashboards in this repository's stack reporting the same metric differently and replace {metric}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: reconcile a metric that two dashboards report differently and give both one definition. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means one definition, both dashboards reading it, the difference explained, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.