Skepsis Insights

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-43. Of the 4 shown, its answer released 4.

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. Released by OQ-06, OQ-07, OQ-14, OQ-43, OQ-44, NP-10.
`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. Released by OQ-05, OQ-14, OQ-22, OQ-26, OQ-33, OQ-40, OQ-43.
`X-07`	BUILD	inference	The time of a question as an ISO week, and no exact timestamp anywhere in the signal layer (OQ-43). A week is the finest granularity this product will ever hold. 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). Released by OQ-43.
`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). Released by the confirmation of 18/09/2026, OQ-14, OQ-40, OQ-43, NP-10.

Requirements