01
The registry should stay open.
manifesto
The definitions, examples, hierarchy, and releases should be inspectable and editable by the community, not trapped inside a private orchestration layer.
Mission
Mission
A community-built open-source tool embedding set that keeps moving.
The mission is not to publish one static model and stop. The mission is to keep building a public tool embedding layer that grows with open-source tooling, public submissions, explicit hierarchy, and public releases.
Why This Exists
Closed tool layers go stale.
New open-source tools appear constantly, interfaces shift, categories blur, and useful training examples accumulate over time. A private or static tool set cannot represent that reality. An open registry can.
02
The hierarchy should stay explicit.
manifesto
A tool embedding project needs parent ids and broader families of behavior, not only flat labels with no structure for the model to exploit.
03
The dataset should stay alive.
manifesto
Open-source tooling changes too quickly for a frozen benchmark to remain relevant. The set has to keep evolving through new submissions and new snapshots.
04
The releases should stay public.
manifesto
Builders should not have to guess where the latest checkpoints live. The Hugging Face organization should be the obvious download destination.
Commitment
The community should be able to shape the ontology itself.
That means adding tools, improving examples, refining parent ids, challenging categories, and releasing better checkpoints over time. The registry should behave like living infrastructure.
Directive
Keep the tool layer public, inspectable, and reproducible.
registry on github
models on hugging face
parent_id required for hierarchy