Provenance & lineage
Every commit records exactly what it was derived from. The provenance view walks that ancestry and — for model images — shows how much storage is shared with the parent.
Early preview
Weight-sharing metrics require storage tracking and are in early preview — contact support@briefcaseai.org for access.
Derivation tree
When you push an image, oci-bai compares its layers against existing commits and writes a derivation link automatically if there's a shared base. Explicit parents can be declared in a cohort push.
bash
oci-bai --repo my-repo provenance fine-tune-v1
Weight sharing
When an image has a parent, oci-bai counts how many storage segments are shared between the two. This tells you whether you're looking at a re-tag, a partial fine-tune, or a completely retrained model.
Reading the weight-sharing panel
| Shared % | Meaning |
|---|---|
| ≥ 90% | Same checkpoint — re-uploaded or tag change |
| 50 – 90% | Partial fine-tune — adapter or head-only update |
| 5 – 50% | Significant retraining |
| < 5% | Full fine-tune — all weights retrained |
Lineage commands
bash
oci-bai --repo my-repo provenance v2 oci-bai --repo my-repo lineage diff v1 v2
Impact — who depends on this?
Find every version that descends from a given base.
bash
oci-bai --repo my-repo whodepends base-v4