Skip to main content

0.9.4 — Metrics & Receipts

Released 2026-10-05.

A new metrics layer: declare the measurements your organisation cares about, let REQQA collect and check them automatically, and get a receipt when a release depends on one.

What's new​

Required-series declarations. Declare that a named metric series must exist, must meet a value target, or must cover every member of a named population, before a specific change can proceed. A declaration can combine existence, value-target and coverage conditions in one record. Authored from a new Required-Series Declarations screen (System Administrator only), with a status view showing whether a declaration is currently Satisfied, Blocked, Lapsed, or Waived.

Threshold and coverage gates. Two new gate shapes beyond plain existence: a value condition checks an observation against a numeric target; a coverage condition checks that every member of a named population has a qualifying observation, and reports which members are missing.

Metrics reporting. A new reporting view and CSV export surface the metric series your organisation is tracking, including a set of built-in informative metrics (repo line counts, dependency-vulnerability counts, documentation hygiene findings, backlog composition) that are never gating — information only, for anyone.

Classification codebook registry. For any metric that classifies something subjectively (a defect severity, a finding category), upload a named, versioned codebook of key-to-definition pairs. Old classifications stay attached to the codebook version that was current when they were made, so comparisons across time never silently mix definitions.

Bug fixes​

  • None specific to existing functionality — this release is new capability, not a fix to prior behaviour.

Behind the scenes​

  • A generic, organisation-scoped time-series store underlies all of the above, with an ingestion/query API and both a build-process producer (repo stats, SBOM scans, documentation health) and an in-app producer (wired into analysis and release lifecycle events).
  • 491 new automated scenarios across the metrics, declarations, gates, reporting and codebook features.

Upgrade notes​

No action needed. Declarations and codebooks are opt-in — nothing is required until an organisation chooses to declare a series or upload a codebook.