Why MegaTensors uses one explicit format contract

Model formats become expensive when producers and consumers make different assumptions. MegaTensors keeps the contract deliberately small and explicit.

Indexes are executable context#

The shard index says where every tensor lives and records the metadata a loader needs before opening large files. This makes partial inspection possible and prevents filename conventions from becoming an undocumented API.

Compatibility is directional#

Writers declare the format version they produce. Readers advertise the versions they understand and reject incompatible releases with actionable errors instead of attempting a best-effort load.

Fewer paths, better tests#

Supporting one documented path lets the project test conversion, publication, verification, and loading as a single contract.