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 11 requirements that NP-10 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-TREND-01 | BUILD | stated | All of it. Every input it needed is now stated. The accelerating designation reads the OQ-06 topic score rather than a raw question count, so 'asked more and more often' is a movement in that score. A trend is shown only when at least 8 different people stand behind it, and every displayed count is rounded to the nearest 5 (OQ-14). Time is the ISO week of a question and nothing finer (OQ-43). Topics are coded with OncoTree, HGNC, HGVS with ClinGen Allele Registry IDs, and ChEMBL, with the code list version stored on every signal (OQ-44). Research Workspace questions feed these aggregates and never a named expert (OQ-07). Still held. Nothing. Two bounds travel with it rather than holding it: the 8-person minimum and the rounding apply in every view, export, alert and API answer, not only on screen, and the differencing check of NP-10 refuses an export or an API answer whose comparison could reveal a count the minimum was meant to hide. |
FR-INT-01 | BUILD | inference | All of it, confirmed by the answer that names the formats: CSV and Excel for lists and tables, PDF for profiles and evidence answers, and JSON through the API (OQ-25). The export action exists on expert lists, profiles and trend views. Still held. Nothing, and one rule is part of the requirement rather than a caveat: every one of the four paths applies the suppression the views apply, and the differencing check of NP-10 refuses an export whose comparison could reveal a hidden count. A commercial user's export carries public-source fields only, never signals, fit scores or evidence answers, and every export is logged with user, time and content (NP-11). |
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). |
X-01 | BUILD | inference | The cancer type named in a question, coded with OncoTree, whose code list version is stored on every signal (OQ-44). Still held. Nothing. Shown only above both minimums: 8 distinct contributing people (OQ-14) and 3 distinct institutions with the 5 percent dominance check (OQ-40, NP-12), with counts rounded to the nearest 5 and the differencing check refusing an export or API answer whose comparison could reveal a hidden count (NP-10). |
X-03 | BUILD | inference | The tumour variant named in a question, in HGVS notation with a ClinGen Allele Registry ID (OQ-44). A variant-level signal is shown only above both minimums and rolls up to the gene otherwise (OQ-41), which is the whole of the re-identification control here. Still held. Nothing. Shown only above both minimums: 8 distinct contributing people (OQ-14) and 3 distinct institutions with the 5 percent dominance check (OQ-40, NP-12), with counts rounded to the nearest 5 and the differencing check refusing an export or API answer whose comparison could reveal a hidden count (NP-10). |
X-04 | BUILD | inference | The drug, drug class or mechanism named in a question, coded with ChEMBL (OQ-44). ChEMBL is CC BY-SA 3.0, so anything derived from it that this product shares travels under the same licence. Still held. Nothing. Shown only above both minimums: 8 distinct contributing people (OQ-14) and 3 distinct institutions with the 5 percent dominance check (OQ-40, NP-12), with counts rounded to the nearest 5 and the differencing check refusing an export or API answer whose comparison could reveal a hidden count (NP-10). |
X-06 | BUILD | inference | The country of the contributing clinician, which is what makes a country facet possible without a named person behind it. Still held. Nothing. Shown only above both minimums: 8 distinct contributing people (OQ-14) and 3 distinct institutions with the 5 percent dominance check (OQ-40, NP-12), with counts rounded to the nearest 5 and the differencing check refusing an export or API answer whose comparison could reveal a hidden count (NP-10). |
X-10 | BUILD | inference | The counts themselves: questions, distinct contributing clinicians and distinct contributing institutions, which are what the two minimums are measured against. Still held. Nothing. Shown only above both minimums: 8 distinct contributing people (OQ-14) and 3 distinct institutions with the 5 percent dominance check (OQ-40, NP-12), with counts rounded to the nearest 5 and the differencing check refusing an export or API answer whose comparison could reveal a hidden count (NP-10). |
X-11 | BUILD | inference | The change in question counts between two periods, confirmed on 18/09/2026 and governed by NP-10. Comparing two tables can reveal a small number even when each table separately meets the threshold, so the differencing check stands in front of every export and API answer, and an in-app view shows a warning instead. Still held. Nothing. Shown only above both minimums: 8 distinct contributing people (OQ-14) and 3 distinct institutions with the 5 percent dominance check (OQ-40, NP-12), with counts rounded to the nearest 5 and the differencing check refusing an export or API answer whose comparison could reveal a hidden count (NP-10). |
XFER-10 | BUILD | research | All of it, on the strength NP-10 chose: a comparison that could reveal a hidden count blocks the export or the API answer outright, and an in-app view shows a warning instead. The check runs before every export and every API answer rather than at the point the data is stored. Still held. Nothing. The asymmetry is deliberate: an export leaves the building and cannot be recalled, while an in-app view is read by a signed-in user whose access is logged. |
DATA-03 | BUILD | stated | All of it. The dashboard receives aggregated signals, and the two numbers that define 'aggregated' are now stated: at least 8 distinct people behind anything shown, with displayed counts rounded to the nearest 5 (OQ-14), and at least 3 distinct institutions with the 5 percent dominance check for anything from OncoSkepsis (OQ-40, NP-12). The thresholds apply in every view, export, alert and API answer, and the differencing check refuses an output whose comparison could reveal a count they hide (NP-10). Still held. Nothing. Individual-level data does not cross at all, which OQ-05 settles: the anonymous card is what a pharma user sees, and a name arrives only through the expert's own acceptance. |