AI Modelreg — Model Registry

• Area: Intelligence
• Path: services/ai/modelreg
• Kind: Curated catalog of AI models (metadata, versions, benchmarks, curation tags)
• Status: v0.0.1 — schema + storage + CRUDsearch API (MODELREG-001002, 2026-05-28) + benchmark ingestionquery (MODELREG-004, 2026-06-01, consumed by `servicesai/curator` Loop A) landed; PGStore persistence, OpenAPI emission, live Koder ID auth pending.

Role in the stack

modelreg is the Koder-side answer to "what models can we choose from, and what do we know about each?". It owns model metadata: identity, version, license, weights URL, benchmark scores, capability tags. It is the missing trust layer that lets runtime/, gateway/, and product UIs pick models with full information instead of falling back blindly on whatever Ollama happens to have cached.

It is the Koder analog of HuggingFace Hub and MLflow Model Registry — scoped to Koder needs (curation + benchmarks + product-facing tags) and explicitly separated from runtime (executor) and kdb-blob (weight storage).

Boundary vs neighbors

• services/ai/runtime consumes slug → weights URL + min-VRAM; modelreg never serves weights.
• services/ai/eval produces benchmark rows; modelreg surfaces them per (model, version).
• services/ai/training registers fine-tunes as new versions but does not store weights here.
• infra/data/kdb-blob is the weight storage layer modelreg refers to.

Features (v1 target)

• CRUD API with multi-axis search (tag, license, family, modality, maxvram, mincontext)
• Model + version + tag entities backed by kdb-doc
• Curation flow: 2-curator approval + benchmark gate for koder-curated
• Eval integration: ingest benchmark rows, query cross-model
• SDK helper engines/sdk/go/modelreg for runtime + gateway
• Cache invalidation via SSE event stream
• Web catalog UI at modelreg.koder.dev (deferred to v0.2)

Primary couplings

RFC and bootstrap

• RFC: modelreg-RFC-001-foundations.kmd — accepted 2026-05-09
• Bootstrap ticket: services/ai/backlog/done/128-modelreg-bootstrap.md
• Implementation tickets: 001 schema+storage — DONE 2026-05-28 (docs/schema-v1.md + backend/internal/types entitiesenumsvalidation + backend/internal/store Store iface + MemStore: unique-id, multi-tenant visibility cross-tenant→404, idempotent versionstags, soft-delete, multi-axis filter + cursor pagination), 002 CRUD API + multi-axis search — DONE 2026-05-28 (`backendinternalapi + cmdkoder-modelreg :9460: POST/GET/DELETE models + versions/tags, filter by family/tag/license/modality/max_vram/min_context/q + cursor pagination, RoleChecker write-gating curator/admin reused from workflow#018, MODELREG-* error IDs, 24 -race scenarios; residual = OpenAPI openapi.json emission + live Koder ID auth (blocked on ID-162) + PGStore persistence). Pending: 003` curationapproval, 004 eval integration, 005 runtime resolver SDK.

Self-hosted-first analysis (5 gates)