Loading workspace…
signed outSign in
Every requirement in bioskepsis-insights-user-requirements-v1.1.md, with the verdict the document’s own rules force. No requirement now carries the verdict BLOCKED. Each row carries both halves of its account, what is buildable and what is still held, and names the decisions that released it. A requirement answered the other way is DROPPED, and that is the one verdict nobody can go and change.
Showing the 2 requirements that OQ-30 released. A requirement that the document alone would have held is here because a decision with a date let it through.
| ID | Verdict | Basis | What that means |
|---|---|---|---|
SEC-05 | BUILD | inference | All of it, confirmed by OQ-30, which fixes the territory: EU data centres. A deployment names its own region within that, the status route reports what it names, and the availability target is 99.5 percent per calendar quarter. Still held. Nothing. A deployment may still be misconfigured, which is why the region is reported rather than assumed: a residency claim nobody can check is worth nothing to a procurement reader. Released by OQ-30. |
NFR-04 | BUILD | inference | All of it, confirmed by OQ-30, which states both targets: 99.5 percent availability per calendar quarter, and the page-speed thresholds of main content within 2.5 seconds and input response within 200 milliseconds, measured at the 75th percentile of page loads. Still held. Nothing. The targets are measured rather than asserted, and the percentile matters: a mean would hide exactly the slow quarter of loads the threshold exists to catch. Released by OQ-30. |