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

ID	Verdict	Basis	What that means
`NEVER-06`	BUILD	research	All of it, confirmed by OQ-47: patient data EFEVRE processes on behalf of a hospital never reaches this product or the signal layer. EFEVRE is a processor for that data and a controller only for the consented signal layer, and Article 28(10) is the reason the distinction has teeth: a processor that sets its own purposes becomes a controller. Still held. Nothing. Released by OQ-47.
`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.
`XFER-15`	BUILD	research	All of it, and it is a prohibition rather than a feature: patient data EFEVRE processes for a hospital is never used for this product or for the signal layer. OQ-47 gives it its legal footing, since a processor that sets its own purposes becomes a controller for that processing. Still held. Nothing. The architecture is what enforces it: this product cannot reach a clinical store, and the boundary refuses at startup a configuration that would let it try. Released by OQ-47.

Requirements