Release-wide Progress Overview

Important

Data collected on: 2026-10-29

This page shows how the S-CORE platform grew across releases. Each chart aggregates one metric over all tracked modules; every bar is split into colour slots, one slot per contributing module.

The last column, marked (forecast) and named after the next release milestone, is not a released state — it is today’s state of the modules pinned in known_good.json, shown as the projection for the next release.

For the current state — per-module and per-component requirements, architecture, traceability, coverage and work-product status — use the verification reports, which are generated from the needs data of this documentation build:

• Platform Verification Report — feature-level requirements, architecture and inspection statistics.

• Module Verification Reports — per module: components, component requirements, architectural elements, requirements traceability, test coverage and verification work products.

Note

All columns are recounted from the module sources pinned by each release, so the series is internally comparable. The counts are source-derived and therefore differ from CI figures — test counts are test definitions, not parameterised CI runs. Treat the numbers as indicative; the verification reports are the authoritative source.

Requirements

Fig. 1 Feature and component requirements across the tracked modules per release.

Architecture

Fig. 2 Feature and component architecture elements across the tracked modules per release.

Implementation

Fig. 3 Lines of code across the tracked modules per release, excluding documentation and third-party sources.

Verification

Fig. 4 Unit test definitions across the tracked modules per release.

Fig. 5 Component and feature integration test definitions per release. Alongside the integration tests kept in the module repositories this includes the feature tests hosted in reference_integration itself, attributed to the module under test.