Metrics and insights

Skopo derives metrics from immutable events rather than from point-in-time scans of the database. This makes metric values reproducible and auditable. The Insights view presents the active project's metric bundle — the set of metrics defined by the active methodology — with filters, freshness indicators, and drill-down into the contributing items and events.

Metric events

A metric event is an immutable record of something that happened: a work item moved to a terminal state, a sprint ended, a ritual was completed, a policy check was satisfied or failed, a release was published. Each event carries a timestamp and enough context to be used in multiple metric calculations.

Because events are immutable and append-only, Skopo can recompute any metric for any historical period from the same underlying data. If a methodology upgrade changes how a metric is defined, the new definition can be applied to the existing event history.

Snapshots and freshness

Computing a metric from raw events on every page load would be slow for large projects. Skopo caches results as filter-keyed snapshots. Each snapshot stores the computed value, the filter set used (date range, status filter, type filter), the sample size, and the time it was computed.

The Insights view shows whether a metric value is Fresh or Cached. A fresh value was computed recently; a cached value may be slightly behind the current state. The compute timestamp and sample size are visible in the metric detail panel so you can judge how current the data is.

If a project has too few events to compute a metric meaningfully, Skopo shows an insufficient-data state explaining what events are needed to build the metric.

Drill-down

Each metric card in Insights is expandable. Selecting a metric reveals:

• the contributing items — the specific work items counted or measured by this metric;
• the contributing events — the metric events that fed into the calculation;
• a status distribution and work type mix for the contributing items;
• a workload by assignee breakdown.

You can also filter the Insights view by date range, status, and work-item type. Each filter change produces a distinct snapshot keyed to that filter set, so Skopo can cache results per filter combination rather than recomputing everything on each visit.

No individual rankings

Skopo does not surface individual performance rankings or per-person throughput scores. Metrics measure the delivery system — flow, quality, goal achievement — not the people working in it. Velocity is available as planning context for sprint capacity conversations, not as a productivity measurement.

The workload-by-assignee breakdown in drill-down shows estimated effort distribution across the contributing items, not output per person.