Question prompt
One short, scoped question per issue. Reply if it intersects your work; ignore if it does not. Replies are anonymized and reviewed.
DueCare deliberately has no community account system. Engagement is by email: subscribe, receive periodic question prompts and reviewed digests, reply when a question intersects your work. Replies pass through a server-side PII detector before any structured fields are stored or reviewed.
Double opt-in. Topic preferences are stored at the email provider, not on the hub. Unsubscribe is one click in every email.
No automated drafts go out. A curator approves every issue before it sends.
One short, scoped question per issue. Reply if it intersects your work; ignore if it does not. Replies are anonymized and reviewed.
A short summary of what changed in packs, tools, and the research monitor since the last digest. Always citation-linked.
Sent only when a corridor pack ships a material change (e.g. a fee cap moves). Few and far between by design.
No human or model sees a reply’s structured form until the server-side PII detector clears it.
Email provider posts the reply to the hub’s inbound webhook. Raw email is held in the provider, not the hub.
The server-side PII detector scans the reply. Anything resembling a case narrative is dropped and the submitter is told why.
The harness extracts a structured object that matches one of the safe submission types (URL update, observation, ranking, etc.).
A human curator reviews the structured object. Approve, edit, reject, or hold for more info.
Approved objects become pack diffs, contact updates, or eval candidates. The submitter receives a structured receipt.