The model registry starts as a source-backed template system. It should not publish broad comparative claims until source trails, update dates, and reviewer status are clear.
| Field | Purpose |
|---|---|
| Model identity | Name, publisher, release date, license, source links, and version notes. |
| Modalities | Text, image, video, audio, document, UI, spatial, temporal, or other supported inputs and outputs. |
| Architecture | High-level design, training approach, context handling, mixture-of-experts notes, OCR strategy, or memory design. |
| Evidence | Benchmarks, papers, repositories, demos, contamination notes, and last-reviewed date. |
| Deployment | Hardware, latency, memory, API availability, edge/cloud fit, and operational limits. |
| Interop readiness | Known tool calling, structured output, protocol, schema, UAI-1, or MCP notes. |
Model page template
Overview
Provider, model family, release date, license/access, context, modalities, and deployment options.
Capability profile
Reasoning, coding, math, multimodal, tool use, latency, cost, and known limits.
Evidence trail
Benchmarks, sources, reviewer status, and freshness notes so readers know what can be trusted.