Skip to content

White Paper

github-actions[bot] edited this page Nov 6, 2026 · 2 revisions

White paper

The OpenBridge white paper explains the problem, how OpenBridge works, where it falls short today, and what it will take to launch. This page summarizes each section and lists every version.

The white paper describes a prototype. Its figures come from draft reference data and must be checked against current agency sources before public use.

Versions

The latest version is always OpenBridge_White_Paper.pdf.

Version Date Download What changed
1.1 November 2026 v1.1 Precise privacy wording; organizational footing and liability and distribution added as blockers; immigration wording held for counsel; depth-first referrals; 90-day plan; expert reviewers still needed
1.0 November 2026 v1.0 First edition

What each section covers

This summary follows version 1.1 (15 pages).

  1. Executive summary. People qualify for help they never get because the path in is hard. OpenBridge checks several programs from one set of answers, with no account. It collects, stores, and sends no personal data. It is a working prototype that is not ready for the public.
  2. The problem. The safety net is dozens of programs with different rules. People fall through because of fragmentation, complex rules, fear (especially in mixed-status families), and practical barriers like shared computers and reading level. The paper notes that its scale figures come from different years and methods.
  3. What OpenBridge does. A session in five steps: welcome, household, income, results, act. Answer once, see reasons for every result, get per-person results for Medicaid and WIC, cautious outcomes, paperwork help, no dead ends, and navigator mode. It also lists what OpenBridge is not.
  4. Who it serves. Benefit seekers, community navigators, community organizations, and contributors.
  5. How it works. A Progressive Web App with no backend in Phase 1. A pure, testable engine. States stored as data files with cited sources. Privacy built into the design, stated precisely: a host's web server may keep standard connection logs (time, file, network address) but never anything a person types, and the provided setups turn access logs off. Made for older browsers and low-cost phones.
  6. Current status. What is built, what is a draft, and what has not started (expert review, legal review, a live site).
  7. Limitations and known gaps. Limits chosen on purpose (it screens and does not decide), rules not yet covered, accuracy concerns (draft rules, 2024 figures, few test cases), and product gaps.
  8. Hurdles to overcome. Blockers: finding expert reviewers (none yet), getting the rules right, legal review (with immigration wording on hold until counsel approves it), organizational footing and liability (nonprofit or fiscal sponsor, insurance, who is responsible), earning trust, and distribution. Major hurdles: growing to fifty states, showing impact without tracking, and long-term upkeep. Then minor ones.
  9. Roadmap. Phases 1 through 4.
  10. Risks and mitigations. Each main risk and how the project handles it.
  11. How to help. Expertise and partnership the project needs, and a 90-day plan: recruit reviewers, settle footing, legal review, navigator quick-start materials, pilot partners, and a complete referral directory for one pilot county first.
  12. Conclusion. The technical groundwork is done. What is left is human work: experts, lawyers, real users, and a community to keep the rules current.

Newer than the paper

The paper is a snapshot. For the current plan and status, the ROADMAP is the source of truth. See Roadmap and status.

How new versions are added

  1. Save the new PDF as docs/whitepaper/OpenBridge_White_Paper_vX.Y.pdf, where X.Y is the version number. Earlier versions stay in place.
  2. Copy it over docs/whitepaper/OpenBridge_White_Paper.pdf, so that link always opens the latest.
  3. Add a row at the top of the Versions table above with the version, month and year, a link to the new file, and a one-line note on what changed.
  4. Run npm run check:wiki to make sure the new links work, then open a pull request.

Related pages

Clone this wiki locally