Loading workspace…
signed outSign in
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 2 requirements that OQ-28 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-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. |
COMP-01 | BUILD | research | All of it, as a deny-by-default rule with nothing left to decide. No payment data, no claims data and no prescribing data enters this product, so US Open Payments, European payment registers, insurance claims and prescribing feeds are excluded from every profile, score and export (OQ-28). Still held. Nothing. The rule is easier to keep than it was to write: there is no ingestion path to guard, because none is built. Released by OQ-28. |