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

ID	Verdict	Basis	What that means
`FR-PLAN-03`	BUILD	research	All of it, on the mechanism the answer chose: the customer uploads a file of engaged- expert IDs and meeting dates whenever they choose, and those experts are marked as already engaged in their lists (OQ-23). Matching uses the open identifiers and the per-customer CRM mapping table of OQ-20. A live CRM import is ruled out rather than postponed, so no read connection to a customer system is built for this. Still held. Nothing. The engagement status stays something the customer's own users set or upload, which keeps the record theirs: this product never infers that a meeting happened. Released by OQ-20, OQ-23, OQ-26.
`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.

Requirements