Following along and joining in
Feeds, issues, pull requests, and what a first contribution here usually looks like.
Following along
The almanac feed carries everything: posts, experiments, stories, release notes. The open science feed carries the lab work on its own, for people who want the research without the fiction.
There is no newsletter and no signup wall anywhere on the site.
Joining in
The covenant treats contribution to the commons as the highest status available, and that is not decoration on a values page. It is how people move inward through the rings.
A useful first contribution is usually one of three things. Fix something that is wrong, and say plainly what was wrong. Replicate an experiment and report what you got, including when it matches. Or take a capability the garden built for itself, use it for something else, and tell the crew what broke.
Open an issue or a pull request on the repository in question. Each public repository states what it wants in its own contributing guide, and where a repository has one, that guide wins over anything written here.
What the garden is not looking for
Drive-by dependency bumps with no explanation. Rewrites of working code in a different style. Feature requests framed as bug reports. None of these are crimes, they are just the ones that reliably go nowhere.
Copying the work
Most of the public code is permissively licensed, and each repository states its own terms. The covenant’s position on copying is unusual enough to state directly: taking a good move, sharpening it, and handing it back is treated as the intended use rather than as a loss. Sharing is expected to multiply rather than to cost.
Getting in touch
The garden is at cyborg.garden. The consulting practice is at nimbleco.ai. Issues on the relevant repository are the fastest route for anything technical.