Portal — System B · restricted · no model, no inference
Specialist queue
Sorted urgent, then oldest. Nothing in this queue was drafted, classified or summarised by software — the intake answers are the summary.
Q1 · Access
Sign-in and MFA are not commissioned yet
The console needs authenticated, role-restricted, India-hosted access with MFA and an append-only audit log. Until that server exists this console reads the threads held on this device only, so the workflow can be reviewed end to end. Named responders: to be filled by the CoE. Published response time: measure, then publish.
Q2 · Queue — 0 threads
no-match backlog: 0Nothing waiting. Complete an intake at /ask/new to see a thread arrive here.
Q3 · Retention job
Identified content is kept 12 months, audit 24. The job is verifiable: it logs every run, including runs where nothing was due.
Q4 · Decisions still open
Who staffs the queue, and what is the honest response time?
With no drafting, every non-library question is human work from the first second. This is the binding constraint on the whole design.
Who owns the library?
A named clinician must read the no-match log monthly and write entries. Without that the automated share never grows.
Does intake link to the tracker?
Per-row opt-in keeps the instruments' local-only promise intact. Recommended.
Is the ten-cluster self-report at n11 acceptable clinically?
Families answering screening questions about their own child is a different act from a trained worker doing it.