Public software
The nine-entry public repository directory, source revisions, categories, and non-claims.
Open the public directory →Public library
Find the shelf that matches the question.
The public Hub is a library, not a single product page. Each shelf keeps its own use case, source boundary, and evidence language so a repository or research note does not imply hosted access, private authority, or a claim the source does not support.
Start here
Choose a shelf, then follow its source receipt. The detailed pages are intentionally separate so a household tool, authoring foundation, evaluation harness, and native research runtime are not collapsed into one generic “AI” claim.
Library shelves
Six public paths through the work.
Each page is a stable overview with links to the relevant repository, research surface, and boundary statement.
Local tools for people
IDA CLI, Camera-Location, HAVEN, and BUNDLE keep useful capability close to the person using it.
Open consumer software →Game engine & development
Open World Model Harness and OMNI-Q cover engine-neutral evaluation, simulation, routing, replay, and development evidence.
Open game development →Cartographer
A standalone spatial-authoring foundation with geometry, revisions, validation, interchange, and bounded proposal workflows.
Open Cartographer →Research library
Model releases, research areas, public articles, SSRN overviews, and adjacent writing with explicit attribution.
Open research →Open Canopy contract
The public/private split: what a public page may say, what source visibility does not authorize, and what remains held out.
Read the contract →Honest gap: a missing shelf is not a claim about existence. This library lists reviewed public surfaces, not every internal project.
Research and writing
A library of questions, not a pile of claims.
Research pages preserve the difference between a publication, a model release, a source receipt, a simulation, and a hardware observation. The research index groups the material by question; individual pages carry the details and original links.
Held-out boundary
Public visibility is not authority.
Private runtime packages, protected data, internal governance, proposal repositories, federal and defense work, unpublished simulation material, and hosted integration surfaces are not silently promoted into this library. The public contract explains why.