Skip to content

Aspiration and Roadmap

David Condrey edited this page Aug 8, 2026 · 1 revision

Aspiration and roadmap

The aspiration is a governed, interoperable service layer that helps people living outdoors move through document replacement, transportation, hygiene, mutual aid, and provider follow-up without duplicating HMIS or coordinated entry.

What success would look like

  • A paper-and-kiosk path works for someone without a stable device.
  • Public information is useful but cannot identify or locate a person.
  • Providers have secure, role-limited workflows and auditable commitments.
  • Response visibility includes capacity and eligibility context rather than punitive rankings.
  • A person can correct, withdraw, or recover a request without surrendering dignity.
  • Independent audits and lived-experience feedback can stop harmful features.

Gates

  1. Prototype: synthetic data, static viewer, signed fixtures, explicit limitations.
  2. Governed pilot: advisory group, one narrow use case, privacy/consent, moderation, paper and accessibility testing, no HMIS imports.
  3. Private service layer: encrypted API/database, workforce identity, MFA, least privilege, audit, recovery, incident response, and deletion.
  4. Controlled interoperability: data-sharing agreements, current HUD mapping, separate sensitive workflows, freshness/provenance, and rollback.
  5. Measured expansion: aggregate outcomes and independent review; stop or narrow harmful features.

No gate is passed because the previous gate merely works technically. It is passed only when people, providers, privacy reviewers, and maintainers can show evidence that it is safe enough for the next step.

Clone this wiki locally