The requirements this system answers
The ISC published its requirements in two documents and one annex. Everything in this evaluation build traces back to a numbered line in one of them, and the numbering is the ISC's own, including the section numbers that appear twice in the source.
Baseline 2026-09-04, agreed 2026-09-04. It is frozen: a change to it after this point goes through a change request with a written impact assessment, rather than being absorbed silently.
What the baseline was taken from
| Document | Version | Dated |
|---|---|---|
| Bid to Bulletin Functional Requirements Specification | v1.2 | 2026-07-15 |
| Annex to the Bid to Bulletin FRS | 15 July 2026 annex | 2026-07-15 |
| Registration and Reporting Functional Requirements Specification | v3.0 | 2026-07-06 |
How to read the two measures
The submission publishes two separate things about every line, and they are never added together.
Requirements disposition
Whether the line has a defensible answer: how the system meets it, or why it does not apply, or what it depends on. This is a statement about the design.
Implementation readiness
What exists today. Implemented and working in this build, demonstrated only, designed but not yet built, an external dependency, or an optional module. This is a statement about the software you are looking at.
The line-by-line statement of both, with the route each observation was made on, is file 04 of the submission, the requirements traceability matrix. Nothing in this build is in production, and the matrix says so on its first tab.