21 lines
1.1 KiB
Markdown
21 lines
1.1 KiB
Markdown
# 06 — Model Artifact manifest and Shard advertisement
|
|
|
|
Status: ready-for-agent
|
|
|
|
## What to build
|
|
|
|
Introduce a Model Artifact manifest that separates storage distribution from route execution. A node should be able to verify local model files, determine which Shards it can serve, and advertise artifact/layer availability to the Tracker without contacting Hugging Face at request time.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] Manifest records model preset, upstream revision, license, backend support, quantization, context cap, tokenizer artifacts, file hashes, piece hashes, and tensor/layer mapping where available.
|
|
- [ ] A node can verify local artifacts against the manifest and reject corrupt or incomplete artifacts.
|
|
- [ ] A node can derive advertised Shard ranges from the manifest and local files.
|
|
- [ ] Tracker registration can include artifact id, backend id, Shard range, and verification status.
|
|
- [ ] Tracker coverage can distinguish model-layer coverage from artifact availability.
|
|
- [ ] Tests cover valid manifest registration, corrupt artifact rejection, and missing layer/tensor metadata.
|
|
|
|
## Blocked by
|
|
|
|
- 01 — Route Session lifecycle.
|