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 4 requirements that OQ-39 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
`XFER-03`	BUILD	stated	All of it. The consent screen can now say what it has to, because the answers fix what is recorded: coded labels plus a machine-written topic summary, never a clinician's typed words (OQ-38); no free-text question box exists at all (OQ-39); the ISO week and no timestamp (OQ-43); and a name reaching a pharma user only through the clinician's own acceptance of a contact request (OQ-05, OQ-42). Still held. Nothing. A consent screen is only as honest as the list behind it, which is why this requirement could not be built while any of those four answers was missing. Released by OQ-05, OQ-38, OQ-39, OQ-42, OQ-43.
`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-07`	BUILD	inference	All of it, confirmed by OQ-39 and OQ-47. OncoSkepsis runs in EFEVRE's cloud under the institutional licence, and clinicians enter only structured fields, so no patient details reach it. EFEVRE is a processor for that clinical use and a controller only for the signal layer, which is where the institution boundary sits. Still held. Nothing. The boundary is a legal shape the architecture has to match: separate stores, separate access control, a processor contract per hospital and a consent record per clinician. Released by OQ-39, OQ-47.
`DATA-05`	BUILD	stated	All of it. The signal layer records the scientific question and its field, and nothing else: coded items in stated vocabularies, a machine summary built only from those and the answer's topic, and an ISO week (OQ-38, OQ-43, OQ-44). OncoSkepsis has no free-text question box for patient detail to arrive in (OQ-39), and the identifier check runs over the structured fields before a signal is created (XFER-05). Still held. Nothing. This requirement used to be blocked by the absence of a stated content list, which is exactly what made it unenforceable: a prohibition with no inventory behind it is a sentence rather than a control. Released by OQ-38, OQ-39, OQ-43, OQ-44.

Requirements