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 3 requirements that OQ-19 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 |
|---|---|---|---|
FR-PROF-04 | BUILD | research | All of it. Trend data and the API data set refresh daily, expert profiles weekly, and every profile shows its last-updated time (OQ-19). The cadences are settings rather than literals, because the answer is a deployment decision and a site that needs a different one should not need a release. Still held. Nothing. Released by OQ-19. |
FR-INT-02 | BUILD | research | All of it. The API data set refreshes daily, which is the cadence OQ-19 states, and the cadence is configuration rather than a literal. Every requirement group is in the first release (OQ-01). Still held. Nothing. An API answer is subject to the differencing check like an export: it is refused when a comparison could reveal a count the minimums hide (NP-10). |
NFR-01 | BUILD | research | All of it. The intervals are stated: trend data and the API data set refresh daily, expert profiles weekly (OQ-19), and both are settings rather than literals so a deployment can differ without a release. Still held. Nothing. Released by OQ-19. |