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-22 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-ALERT-01 | BUILD | research | All of it, on the channels the answer names: a weekly email digest per user, and alerts written into the customer's CRM as tasks, for Veeva Vault CRM, Salesforce Life Sciences Cloud and IQVIA OCE (OQ-22, OQ-26). Subscriptions were already buildable; what was missing was where an alert goes and how often, and both are now stated rather than chosen here. Still held. Nothing. Every alert carries the same suppression as the view it came from: the 8-person minimum, the 3-institution minimum with the dominance check, counts rounded to 5, and nobody named without an accepted contact request (OQ-14, OQ-40, OQ-05). An alert is a delivery channel, not an exemption. |
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. |
FR-INT-03 | BUILD | research | All of it, against the three systems the answer names: Veeva Vault CRM, Salesforce Life Sciences Cloud and IQVIA OCE, all in the first release (OQ-26, OQ-01). Read access serves expert matching; write access delivers the alert tasks of OQ-22. Still held. Nothing. What crosses into a customer's CRM obeys the same suppression as everything else, and an alert task naming an expert requires the same accepted contact request a screen does. |