The hub asks the people who already know.
Civil society won't learn another login. So the hub inverts the model: it detects where its knowledge needs verifying, drafts a specific question for the experts best placed to answer (caseworkers, lawyers, hotline volunteers), and gives a curator a reviewable dispatch plan. Human-sent, vetted observations can then feed prioritized context and candidate grading dimensions. This page shows the live planning and intake boundary.
The loop
Loading live outreach state…
Context gaps the hub wants verified
Each is a concrete, field-answerable question. Priority rises as observations corroborate it. Draft campaign previews the solicitation and the number of matching opted-in profiles. The hub never stores raw recipient addresses and cannot send; a curator needs a separate consented address book to resolve hashes before dispatching through an organization-owned mailer.
Loading gaps…
Prioritized context from observations
Ranked by how strongly civil-society replies corroborate each gap. Each carries a candidate grading dimension, so outreach feeds the evaluation rubric, not just the document corpus.
No observations yet. As replies arrive, prioritized context appears here.
Register an outreach topic profile
Submitting records only a sha256 address hash + your topics. It does not create a contactable mailing-list entry: the hub cannot recover your address or email you. Contact is possible only if an authorized curator already holds the same address in a separate consented address book. Unsubscribe by submitting the same address through the unsubscribe route.