Hub
The Hub at hub.biosimulant.com is the public catalog. Published labs live here, this is what you pin a version from, and anyone can look at what a lab is made of without signing in.
There is no login on the Hub. Browsing is open, and fork, edit, run and account actions hand off to Studio.
What a published lab is
A published release is immutable. namespace/name@version always resolves to the same bytes, so a run recorded against it can be reproduced later. Publishing a change means cutting a new version. You never edit an old one.
A lab page shows what the lab simulates, which models it contains, how they are wired together, and the exact version you are looking at.
Working with the Hub
| If you want to… | Go to |
|---|---|
| Put a lab on the Hub from your machine or CI | Package and publish |
| Publish automatically on every push to a branch | Deployments |
| Change who can see a lab you own | Visibility and sharing |
| Pin a Hub lab and run it beside your own code | Compose Hub labs locally |
| Search and inspect the Hub from an agent | Agent tool reference |
Pinning
Anything that consumes a Hub lab should name an exact version. The Developer API takes a pinned lab reference, HubComposition resolves one locally, and the CLI pulls one into a local tree. A floating reference is convenient right up until the day it changes underneath a result you already reported.
What the Hub does not judge
Publishing says a lab builds and its manifests validate. It says nothing about whether the science is right. Compatibility profiles check that two ports describe the same information in the same form; they don’t judge model quality or fitness for use. See Model compatibility and Passports and evidence.
Next steps
- Package and publish: declare, validate, build, publish
- Compose Hub labs locally: pinned Hub labs beside local modules
- Studio: fork a Hub lab and run it in the browser