Source and contracts
The public repository, documentation, format, tests, or interface described by the page can be inspected at the linked source revision.
Open Canopy contract
Public enough to inspect. Bounded enough to trust.
This is the plain-language contract for the public Hub. It explains what a public page or repository link means, what it deliberately does not mean, and where private authority, data, and operational detail remain.
The short version
Public source is evidence of a reviewed release boundary—not a grant of access, trust, authority, funding, endorsement, or production readiness.
What public means
A source and explanation people can inspect.
Public pages should help a reader understand the released surface without making them reconstruct the company's private workspace.
Capability with non-claims
Each overview names what the source does and what remains unverified, simulated, private, experimental, or outside the release.
Source receipts
Portfolio entries point to a reviewed revision or publication source. A receipt records lineage; it does not turn a source snapshot into a live guarantee.
What public does not mean
No silent expansion of authority.
Readers, investors, operators, and integrators should not infer more than the evidence supports.
A repository is not a service.
A public source link does not grant access to private Hub routes, customer data, private models, protected workflows, hosted credentials, or deployment infrastructure.
Source is not acceptance.
Code presence, a simulator, a fixture, or a unit test is not by itself proof of hardware support, production readiness, live provider behavior, or universal performance.
Research interest is not an award.
Department-level or public-sector research language is not evidence of a signed contract, committed revenue, solicitation status, proposal outcome, endorsement, or partnership.
AI output is not permission.
Proposals, recommendations, model responses, and external integrations must pass the local or governed authority path before a consequential change can occur.
Boundary map
Keep the core useful without publishing the private layer.
Public foundation Formats, geometry, generic backends, local workflows, public CLI paths, evaluation contracts, and reviewed documentation.
Private Hub Identity, entitlement, organization scope, private providers, model routing, protected telemetry, customer data, hosted workflow state, and authority.
Local operator Filesystem paths, credentials, devices, datasets, checkpoints, private runtime bindings, and final local execution decisions.
Held-out material
Some work remains unnamed on purpose.
The public boundary is stronger when it does not turn internal visibility into a product directory.
Federal, defense, SBIR, and STTR work
The Hub does not enumerate repository functions, solicitations, technical approaches, submissions, award status, or contract status.
Unpublished simulation and integration material
Uncleared adapters, private catalogs, anatomy material, and hosted integrations stay outside the public library until their boundary is reviewed.
Source visibility is not release approval.
A local checkout, branch, document, or repository name does not automatically become a public claim.
Use the contract
Read the page, then follow the source.
If a public page and a repository disagree, the source revision and its explicit evidence boundary require review. If a detail is not published here, do not infer it from a neighboring private system.