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 6 requirements that OQ-01 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-NET-01`	BUILD	research	All of it that this document supports: co-authorship and shared-affiliation edges over the indexed literature, with the trial record now source-agnostic and each fact carrying the source that supplied it (OQ-11). Every requirement group is in the first release (OQ-01), so nothing waits on sequencing. Still held. Shared-trial edges remain unbuilt, and not because of a question: no requirement in this document names a trial data source for FR-NET. Inventing one would be a source decision nobody has taken. Released by OQ-01, OQ-11.
`FR-PLAN-04`	BUILD	research	All of it. Insights are captured through one fixed category list, the same for every customer: evidence gap, guideline or practice change, clinical-trial interest, safety question, access or reimbursement issue, and other (NP-08). There is no free-text box anywhere in insight capture (OQ-24), and an agency account keeps each client's notes inside that client's workspace (OQ-04). Still held. Nothing. The safety category opens the customer's own safety reporting page, whose link is held in their account settings, and no side-effect content is stored here (NP-08). That is the whole of this product's role in pharmacovigilance, deliberately. Released by OQ-01, OQ-04, OQ-24, NP-08.
`FR-PLAN-05`	BUILD	research	All of it. A short checklist can be shown at the point of insight capture, with items taken from the stated source definition rather than invented: R23 defines an insight as a deeper understanding of the reason behind a trend that shows whether action is warranted, which yields the two checklist... Still held. No functional part. OQ-01 is the only listed open question and governs release order, not content. Three constraints: 0.5 - no score, weight or pass threshold may be invented, so nothing like 'three of four boxes means actionable' and the checklist must not gate saving; the exact checklist wording... Released by OQ-01.
`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). Released by OQ-01, OQ-19, NP-10.
`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. Released by OQ-26, OQ-22, OQ-01.
`FR-INT-04`	BUILD	inference	All of it, confirmed on 18/09/2026: single sign-on through SAML 2.0 or OpenID Connect, with identity-provider metadata configured per customer. This product's own identity instance already speaks OpenID Connect, so a customer's provider is a configuration of that rather than a second authentication path in this codebase. Still held. Nothing. Just-in-time provisioning stays bounded by ACC-01: a user arriving through a customer's provider joins that customer's account and no other. Released by OQ-01, the confirmation of 18/09/2026.

Requirements