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 3 requirements that NP-11 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-INT-01`	BUILD	inference	All of it, confirmed by the answer that names the formats: CSV and Excel for lists and tables, PDF for profiles and evidence answers, and JSON through the API (OQ-25). The export action exists on expert lists, profiles and trend views. Still held. Nothing, and one rule is part of the requirement rather than a caveat: every one of the four paths applies the suppression the views apply, and the differencing check of NP-10 refuses an export whose comparison could reveal a hidden count. A commercial user's export carries public-source fields only, never signals, fit scores or evidence answers, and every export is logged with user, time and content (NP-11). Released by OQ-25, NP-10, NP-11.
`ACC-02`	BUILD	research	All of it. Commercial users may hold logins, in a separate view that keeps consented signals and medical content out (OQ-35). Every user carries a role, and the filter is applied to the data rather than to the screen: a commercial role sees no signal- derived field, no fit score and no evidence answer, anywhere, including through the API. Still held. Nothing. The same rule governs export: a commercial user exports fields built from public sources only, such as papers, trials, congress roles and affiliations, and every export is logged with user, time and content (NP-11). Released by OQ-35, NP-11.
`ACC-04`	BUILD	inference	All of it, confirmed by NP-11, which names what it must cover: every export is logged with the user, the time and the content, and a commercial user's exports are filtered to public-source fields before that log is written. Still held. Nothing by a question. One value stays unstated and unneeded: no log retention period or review cadence is invented here, because none is stated and the audit log's own retention is a deployment decision recorded elsewhere. Released by NP-11.

Requirements