General-purpose model without downstream documentation

Maintain versioned model documentation for each general-purpose model covering intended uses, training, and limitations, and publish it where downstream providers get the model.

Model documentation for each general-purpose model version (a model card or documentation page, such as model_card.md or the Hugging Face model card README) written for downstream integrators: intended and out-of-scope uses, architecture and technical specifications, how and on what data the model was trained, evaluation results, and known limitations. The provider's documentation owner revises it with each released version and keeps earlier versions retrievable. The repository holds its source, and the release pipeline publishes it alongside the weights or API so integrators receive it at the point of integration.

Where it goes: 12 repository artifacts, 14 user-facing text, 11 CI/CD pipeline.

What reviewers look for: a model card or documentation page per released model version with sections on intended uses, technical specifications, training data, and limitations, published where integrators obtain the model (model hub, API docs, download page), and a release step that ships it with the version rather than documentation that trails the release.

Organizational control: the evidence is a kept record, its owner and its upkeep, not code.

from huggingface_hub import HfApi
HfApi().upload_folder(folder_path='out/', repo_id='org/base-7b')

from huggingface_hub import HfApi, ModelCard
card = ModelCard.load('out/README.md')
required = ['## Uses', '## Training Details', '## Bias, Risks, and Limitations', '## Technical Specifications']
missing = [s for s in required if s not in card.text]
if missing:
    raise SystemExit(f'model card incomplete: {missing}')
HfApi().upload_folder(folder_path='out/', repo_id='org/base-7b')

Engineering guidance, not legal advice. Each provision below may add its own details (a cadence, a deadline, a required notice element): open it for those.