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 requirements whose account names OQ-06. Of the 3 shown, its answer released 3.
| ID | Verdict | Basis | What that means |
|---|---|---|---|
FR-DISC-02 | BUILD | stated | All of it, in the shape the answers of 17/09/2026 gave it. The expert a pharma user meets is an anonymous card carrying profession, country and topic, and no name, no employer and no question text (OQ-05). A contact request is recorded, passed to the expert, and the identity is revealed only on acceptance, with the acceptance stored as a consent record naming the company and the wording shown (OQ-42). The link between a card and a person stays inside the signal layer, which no service outside it may read. 'Sustained and specific enquiry' is the topic score of OQ-06, built from the number, recency and specificity of questions, with the top 1.4 percent of a disease area flagged until the validation study replaces the cut-off (NP-15). Research Workspace questions feed anonymous trends only, and reach a named card solely for an academic who switched on 'contactable by pharma' (OQ-07, NP-03, FD-02). The 12 researchers of the August 2026 note are excluded from every list, card and profile (OQ-33). The negative-publication verification this build already had is unchanged and is what evidences the claim. Still held. Nothing is held by a question. One operational bound stands and is not a gate: OncoSkepsis signals are shown only once a third hospital joins (NP-01, OQ-40), so a view with nothing releasable says so, naming the minimum, rather than showing an empty result. |
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-ALERT-02 | BUILD | stated | All of it. The trigger is the OQ-06 topic score crossing the NP-15 cut-off, the top 1.4 percent within a disease area, rather than a question count nobody stated. Delivery is the weekly digest and the CRM task of OQ-22. What the alert may say is bounded by the same minimums as any other view, and it names no expert who has not accepted a contact request (OQ-05, OQ-14, OQ-42). Still held. Nothing. The cut-off is configuration, because the validation study of OQ-27 replaces it with a measured one, and an alert threshold that needed a release to change is a threshold nobody will tune. |