Open Commons ObservatoryEnglish·Русский

When your program uses someone else's code, you do not really have that code. You have a promise that a registry will hand you something by that name - and a hope that nobody changes what the name means.

Borrowed, not owned

A dependency you cannot change is a risk you cannot manage. Find a bug in it and you have two bad choices: wait for a stranger to fix it, or copy the code into your own project and look after that private copy for ever, as it drifts further from the original every month.

And a fix you do make is trapped where you made it. Getting it back to the people who could use it means untangling it from everything else you changed.

A cutting, not a copy

Rhizoid makes each dependency a real fork that you own - a rhizoid-cutting, or rhizcut. It is pinned to an exact state, so nothing moves under you. It follows the original when you choose, not when someone else decides. You can patch it today, without anyone's permission. And when your patch is good, it goes home as one clean change, with none of your local history attached.

Like a gardener's cutting

A cutting is a living piece of the parent plant. It grows in your soil and you prune it as you need - and it is still the same plant, so what you learn from it can go back to the garden it came from.

Nothing hidden

There is no central list to trust and no lock file only a tool can read. Each cutting carries its own small note saying where it came from and what state it holds. And the tool tells you when a cutting has drifted from what you declared - it does not merely repeat the declaration back to you.

What it does not fix

Rhizoid works in the world as it is: files, git, forks. It does not cure the deeper trouble - that software is identified by name. That is Rhizome's work, and a much longer road. Rhizoid is what can be used while that road is walked.

Where it stands

Its commands are settled and the layer that reads its declarations is built and tested. The commands themselves are being written.