Describe
Use model.yaml to define the model’s structure, runtime requirements, artifacts, interface, and entrypoint.
Developer infrastructure for AI systems
modelc is a CLI and specification for packaging AI models as portable, inspectable units with declared artifacts, defined interfaces, and reproducible execution.
pip install modelc
.modelc.tar.gz archivesPackage models as self-contained artifacts instead of loose collections of files and assumptions.
Read the structure, runtime requirements, and interface before you run anything.
Use declared interfaces as a foundation for evaluation, contracts, and larger systems.
The gap
Even when a model is available publicly, using it often requires reconstructing an environment, identifying the right artifacts, and interpreting informal assumptions about input shape, output structure, and execution flow.
In software, containers created a cleaner boundary between code and runtime. In AI, that boundary is still weak. modelc is an attempt to define a small but useful primitive at that layer.
The manifest
modelc uses a developer-friendly manifest that keeps the important parts visible: metadata, runtime, artifacts, interface schema, and entrypoint.
apiVersionapiVersion: modelc.dev/v0
kind: ModelContainer
metadata:
name: sentiment-basic
version: 0.1.0
runtime:
type: python
version: "3.11"
artifacts:
weights:
path: ./model/
format: pytorch
tokenizer:
path: ./tokenizer/
format: huggingface
interface:
input:
type: text
schema:
text: string
output:
type: classification
schema:
label: string
confidence: float
entrypoint:
command: python run.py
Workflow
Use model.yaml to define the model’s structure, runtime requirements, artifacts, interface, and entrypoint.
Package the project into a portable archive with a resolved manifest and a predictable internal layout.
Read model metadata, artifacts, and schemas without executing the model first.
Pass JSON through stdin, execute the entrypoint, and validate output against the declared schema.
Positioning
modelc is meant to be a systems primitive. It defines a unit of packaging and execution that can support future layers such as evaluation, contracts, signing, provenance, and registry workflows.
The emphasis is on a disciplined v0: keep the boundary small, useful, and easy to reason about.
Roadmap