Skip to content

Mission metrics

A mission can keep metrics: numbers Cora records each time she does a piece of work, so you can see how they move. A weekly check might record a score, a number of issues found and a rate, every week.

The examples on this page follow an invented bike shop, Kestrel Cycles, and its mission “Website refresh”.

Each metric has (D0772):

Part Example
A name Checkout errors
A unit errors
What it means Errors shown to people at checkout in the week
Better when lower
Where it comes from The weekly site check

Then it has values: a number and the date and time it applies to. The names come from your mission and its skills, never from Cora AI itself.

Cora records a value with record_metric when someone in the mission asks her to (“Cora, track the checkout errors each week”) or when a skill says to, for example on a weekly schedule.

The first value makes the metric, so Cora gives its unit, what it means, whether higher or lower is better and where it comes from. After that she adds values. A value in another unit is refused, so a chart never mixes units.

Cora reads the values with read_metrics, newest first, with the change from the value before. So a report can say “checkout errors fell from 14 to 9 this week, which is better”.

For a report, Cora can also ask for a chart: a small line chart of the values as a picture she puts into the report document. It is drawn by Cora AI from the values themselves, so it shows exactly what was recorded.

  • 20 metrics in a mission.
  • 500 values for each metric. At the limit, the oldest value goes when a new one comes.

Open Mission details and choose Overview. The Metrics section shows, for each metric:

  • its latest value and unit;
  • how it changed from the value before, in words, and whether that is better or worse;
  • what it means and where it comes from;
  • a small trend chart of the last 30 values, with a description for screen readers;
  • a Values list of each date and value.
Who What they can do
Any member of the mission See the metrics and their values. Ask Cora to record or report one.
Mission admins, and org admins who are in the mission Delete a whole metric, or one wrong value, in Mission details. Each asks first.

Nobody types a value into the console: values come from Cora’s work. To fix a wrong value, delete it and ask Cora to record the right one.

Cora’s helpers cannot record or read metrics. A hero that another mission has called in records and reads its own mission’s metrics, as in its own work.

Decisions: D0772.