Rhizoid
fork, own and sync git dependencies instead of relying on a package manager
✓ Why it exists✓ What it must reach○ How each step is delivered and proven✓ What is happening now
Why it exists
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.
What it must reach
Working
0/1The command line, implemented
0/1The consumption side, designed
Perfection
0/1A TUI
Ongoing perfection
0/1ocoeco travels as a rhizcut
Readinesslevel 0 of 9
0 / 4 milestones done
How each step is delivered and proven
The command line, implementednot started
The declarations layer and its testscheck
The part that reads a cutting's own note is built and tested first.
Every command trusts what it reads.
The consumption side, designednot started
The design logpractice
Each question is settled as a decision, with what was rejected, before any code depends on it.
A dependency tool's mistakes are expensive to undo once others rely on them.
A TUInot started
Nothing delivers this step yet.
ocoeco travels as a rhizcutnot started
Nothing delivers this step yet.
What is happening now
Made by work
35 commits in the last 90 days latest release v1.0.0 · 2026-09-22