1. Different material has different terms
Public access to the Benefit Bridge Alpha does not make every component subject to the same license. The project distinguishes:
- Benefit Bridge-created Alpha material that has not yet been released under an open-source license;
- third-party and open-source components governed by their own licenses; and
- Benefit Bridge material intentionally released later under a clearly stated open-source license.
Benefit Bridge does not claim ownership of third-party/open-source software or take away rights its license grants. Publicly visible information is not confidential merely because it appears in an Alpha.
2. PolicyEngine US
The Python comparison and validation code is pinned to PolicyEngine US 2.38.19. PolicyEngine US is a separate project distributed under the GNU Affero General Public License, version 3 (AGPL-3.0).
The current static browser Alpha does not intentionally bundle the PolicyEngine US Python package into its browser JavaScript. PolicyEngine is used in the repository’s Python comparison, validation, and test path and may be used by a separately deployed comparison service.
Benefit Bridge and PolicyEngine calculations are identified separately. Reference to PolicyEngine does not imply endorsement, certification, or affiliation.
3. Other dependencies
PolicyEngine US has its own dependencies, and the development environment also uses testing and build tools. Each dependency remains governed by its applicable license and notice. A source or binary distribution must preserve notices and provide source or offers when its licenses require them.
This page is not intended to replace the complete notices contained in dependency packages or their source repositories.
4. Government rules and reference material
Benefit Bridge may describe public benefit rules or link to government material. That does not make Benefit Bridge a government service and does not imply agency approval. Government seals, names, publications, data, and other materials remain subject to any applicable law, attribution requirement, or usage restriction.
5. Benefit Bridge’s future open-source core
The product direction calls for a permanently open-source core, but this notice does not pretend that a future license choice has already been completed. Benefit Bridge-created material will be open source only when the current rights holder intentionally publishes it with a specific license and the required notices.
Until that happens, do not assume that a publicly reachable Alpha grants permission to copy proprietary components, redistribute them, create a commercial derivative product, or obtain non-public source or technical material. These restrictions do not override any permission granted by an applicable open-source license.
Confirm ownership of every Benefit Bridge contribution, select a project license, inventory direct and transitive dependencies, preserve all required notices, evaluate AGPL-3.0 network-use and source-availability obligations, and make sure the Alpha-use restrictions do not conflict with open-source rights.
6. Corrections
License information can change when dependencies change. If you believe a required notice or attribution is missing, use the contact method that accompanied the Alpha invitation and do not include sensitive household information.