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 12 requirements that the confirmation of 18/09/2026 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-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.
`FR-MEAS-02`	BUILD	inference	All of it, confirmed on 18/09/2026: per customer, the lead time between the date this product flagged an expert on a topic and the date of that expert's first indexed publication on it. The flag date is already recorded and the publication date comes from the indexed literature, so the measurement needs no new source. Still held. Nothing. Two honesty constraints belong to the number rather than beside it: a lead time exists only for an expert who did publish, so the report says how many flagged experts have not, and a median over a survivor set is a different claim from a median over the cohort. This is the same measurement the OQ-27 study formalises, and it is the number that evidences the product's central claim. Released by the confirmation of 18/09/2026.
`FR-MEAS-04`	BUILD	inference	All of it, confirmed on 18/09/2026: per expert, the scientific topics on which company engagement took place. The engagement records come from the customer's own uploaded file (OQ-23) and the topics from this product's coded vocabulary, so nothing here needs a source it does not have. Still held. Nothing, and the requirement's own exclusion stands as written: no prescribing data and no sales data, which OQ-28 makes a product-wide rule rather than a local one. Released by the confirmation of 18/09/2026, OQ-23, OQ-28.
`X-02`	BUILD	inference	The gene named in a question, as an HGNC symbol (OQ-44), confirmed on 18/09/2026. 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-44.
`X-08`	BUILD	inference	The contributing clinician's professional role, from the list OQ-10 states, confirmed on 18/09/2026. 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-10, OQ-14, OQ-40.
`X-09`	BUILD	inference	The evidence status of the answer, as contested evidence or thin evidence, confirmed on 18/09/2026. These two flags are what the research-gap view is built from (NP-07), which is why the field exists at all. 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, NP-07.
`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.
`XFER-05`	BUILD	inference	All of it, confirmed on 18/09/2026 and narrowed to the structured fields. OQ-39 removed the free-text question box from OncoSkepsis, so there is no prose to scan: what remains is a check on the coded fields before a signal is created. Still held. Nothing. The narrowing matters: a free-text scanner in a product with no free text would be security theatre, and would imply a protection that nothing exercises. Released by the confirmation of 18/09/2026, OQ-39.
`XFER-13`	BUILD	inference	All of it, confirmed on 18/09/2026, and it is the load-bearing one. The signal layer delivers to this product through a one-way interface, and this product's services have no read access to the stored coded OncoSkepsis signals. ADR 0002 records the shape that implements it: a signal service that neither product owns, which OncoSkepsis writes to and this product reads from, holding no credential for any clinical store. Still held. Nothing. Until the confirmation this was an inference the architecture already relied on, which is the uncomfortable kind: a design resting on a requirement nobody had agreed. Released by the confirmation of 18/09/2026, OQ-47.
`ACC-03`	BUILD	inference	All of it, confirmed on 18/09/2026: a customer administrator adds users, removes users and assigns roles. The role vocabulary it assigns is this product's own five, which the answers settle: KOL lead, field medical lead, Medical Science Liaison, commercial and administrator (OQ-03, OQ-35). Still held. Nothing. An administrator's reach stops at their own account, and inside an agency account at the workspaces they administer (OQ-04, ACC-01). Released by the confirmation of 18/09/2026, OQ-03, OQ-35.
`COMP-04`	BUILD	inference	All of it, confirmed on 18/09/2026 with one thing settled that the requirement left open: the customer enters the fair market value. This product calculates none, proposes none and holds no rate table. The documented need and the selection criteria already exist as append-only revisions under FR-PLAN-02, so this requirement ties those two and the customer's own fair market value record to a planned engagement. Still held. Nothing. The narrowing is the substance: a product that proposed a payment amount would be making a recommendation about a transfer of value, which is the customer's decision and their record to defend to a code reviewer. Released by the confirmation of 18/09/2026.
`NFR-02`	BUILD	inference	All of it, confirmed on 18/09/2026: every expert signal and every field trend carries the type of evidence behind it, whether publications, trials, congress abstracts or aggregated query signals. The types are ones this product already holds, so the requirement is a field and a display rather than a new source. Still held. Nothing. This is the requirement that stops a question-derived signal reading like a publication record, which is the single most misreadable thing the product shows. Released by the confirmation of 18/09/2026.

Requirements