.tine Format Policy
Portable run graphs, integrity and signature boundaries, and v1 compatibility.
Run.save("result.tine") still writes v2. Version 0.1 artifacts can migrate in memory and be deliberately re-saved as v2.
Protocols
opentine 0.7.0 deliberately has two compatibility surfaces: portable .tine files stay on format v2, while initialized .tine/ repositories use the verified v3 object model.
v2
Repository Object Model
Typed objects, refs, packs, semantic history, and synchronization.
Repository v3 stores blobs, events, runs, attestations, and annotations. It supplements portable files; it does not rename them “.tine v3.”
Read the repository protocol →