# metric

Docs for TrueQuery 0.1.6. Define a metric once, then find the places that compute it differently.

**For BI and analytics engineers.** In Claude Code this is a `/truequery` slash command. In Muse Code, describe the task in your own words, or load the skill with `/skill truequery`. In Codex the skill isn't here yet, only the checks.

## Define it

```
/truequery metric "active customer"
```

It looks for an existing definition first, instead of inventing a new one. If there isn't one, it asks for the meaning, formula, grain, filters, unit and time zone, then writes it into `DATA.md`, and into your semantic layer if you have one.

An existing computation that differs is named as a conflict, not silently replaced.

## Find the drift

```
/truequery metric check active customer
```

It reads each place that computes the metric and reports it as matching, differing in a named clause, or impossible to tell. This is judgment, not one of the checker's checks, and it never claims a match it didn't read.

TrueQuery doesn't pick a winner: you decide, and the decision goes into `DATA.md`.