BUNDLE
A local-first financial utility organized around provenance, stale-data handling, deterministic projections, and inspectable connector boundaries.
Commitment: local use, portable records, and explicit connector limits.
Open Canopy program
Software should remain useful without captivity.
Open Canopy is the public commitment to standalone usefulness, understandable boundaries, portable data, and honest release language. It is a program and contract, not a claim that every Hidden Canopy system is open.
The commitment
Local-first where practical, portable by design, explicit about what is not included. Public availability, Open Canopy status, product role, and hosted Hub access are separate dimensions.
Qualifying software
Start with the surfaces that carry an explicit public commitment.
The current directory names qualifying software conservatively. A repository can be public-source or source-available without being part of Open Canopy until its boundary is reviewed.
Camera-Location
A discovery utility that keeps observation, verification, authorization, and stale state distinct while remaining useful as a local tool.
Commitment: inspectable evidence paths and no implied authorization from discovery.
Boundary note. Other public-facing products may be useful without carrying an Open Canopy designation. Check the portfolio metadata and each product page instead of inferring status from a repository URL.
Portability and trust
Leave with the useful parts.
Data portability Exportable, documented records should not require an active Hub session to remain readable.
Interoperability Neutral formats and typed boundaries are preferred where they preserve meaning and provenance.
Licensing clarity A license is stated at the repository boundary; source visibility is not treated as a license grant.
Forking A fork may preserve the public core while removing optional hosted or proprietary integrations.
Local operation Network, AI, login, and Hub access are optional for the core paths described as standalone.
Contributing
Contribute to the boundary you can inspect.
Contribution begins with a reproducible issue, a clear source boundary, and an honest description of what was tested. It does not require access to private services or imply entitlement to them.
Start with the source
Read the repository README, license, status notes, and local verification instructions before extending a claim.
Make the change legible
Describe the capability gained, boundary improved, tests run, and evidence that remains unavailable.
Keep authority explicit
Do not add credentials, private adapters, silent network requirements, or mutation paths hidden behind a model response.
What Open Canopy does not mean
It does not mean every product is open-source, every interface is hosted, every roadmap item is implemented, or every public repository is a promise of support. Those claims require their own evidence.