pantry
pantry is the cafaye project registry: the one place that answers what a
cafaye project is — its name, description, language, the contract it exposes,
and how to reach it — so cafe dev, cafe deploy and a person reading the
platform read one answer instead of a hardcoded list in each of them. It is
written in Go.
The catalog’s entity is a project, not a service: MD23 moved the
vocabulary end to end, so the routes are /v1/projects, the schema is
Project, and service survives only as the runtime word for what cafe dev
starts and what gateway routes to.
Closed source, public endpoint
Section titled “Closed source, public endpoint”pantry is proprietary by decision (OPS-D10, 2026-10-10): once the
catalog is multi-tenant and public it is part of the operated product, and an
MIT catalog is a forkable cafaye SaaS. So the repository is closed while the
service stays publicly reachable — the box pattern: closed code, public
endpoint, open contract. openapi/v1.yaml and the response-shape
documentation are published; the implementation behind tier 1 is not.
pantry builds on no other cafaye service. It validates against core’s
schema, which is a specification file rather than a service, so dependencies
is empty rather than naming core.
The gate
Section titled “The gate”bin/prime # build, vet, the Go suite, the schema checks- Repository: private — proprietary to Cafaye (OPS-D10)
- Language: Go
- Contract:
openapi/v1.yaml(exposes.api) - Dependencies: none; events: none (a read model, not a bus participant)