The catalogue

The catalogue is served by a portal, not by this site. It is where contracts are searched, compared and resolved by the CLI — see The portal.

Why it is not here

A catalogue belongs to whoever publishes it. Listing one organisation’s contracts as a section of Oren’s documentation would say they are part of Oren — and they are not. They are one organisation’s tasks, with the same standing as anyone else’s.

That matters more than it looks. The whole model rests on implementations being compared by the privilege they require, and on being official carrying no weight in that ranking. Documentation that features one organisation’s contracts puts a thumb on exactly that scale.

The reference workers

The contracts used as examples throughout this documentation are published by techlite, and their source lives in the workers repository — one directory per task, each with a generated README covering inputs, outputs, dependencies and implementations.

They exist to prove the contracts are implementable and to give a starting point. A third-party implementation asking for less privilege is objectively better.

Browsing a catalogue

export OREN_REGISTRY=https://your-portal
oren add techlite/analyze-commits

oren add shows what a task requires from your environment, and the cost of each available implementation, before you use it. The portal’s web interface shows the same thing, side by side.