Requirements

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.

All 122 BUILD 104 PARTIAL 15 BLOCKED 0 DROPPED 3

Showing the 2 requirements that NP-04 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
`NEVER-07`	BUILD	inference	All of it, confirmed by OQ-38: the clinician's own words never enter the signal layer. What is stored is coded labels and a machine-written summary built from those labels and the topic of the answer, generated inside the institution boundary, with the inputs to each summary logged (NP-04). Still held. Nothing. The log is what makes this checkable rather than promised: a summary whose inputs are recorded can be shown to contain nothing a clinician typed. Released by OQ-38, NP-04.
`XFER-06`	BUILD	inference	All of it, confirmed by OQ-38 and OQ-44: the signal carries coded items in the stated vocabularies, with the code list version recorded, plus a one-line machine summary written from the coded fields and the topic of the answer returned to the clinician, never from words a clinician typed (NP-04). The summary is generated inside the institution boundary and the inputs used for each one are logged. Still held. Nothing. Released by OQ-38, OQ-44, NP-04.