Ordinary Git blobs
Binary files are stored as regular repository objects — immutable, addressable and versioned like any other file.
Version binaries and code as one.
Images, models, archives and other binary files are ordinary versioned objects in Strata — stored immutably, streamed on demand, and tracked for the tasks that depend on them. Git LFS compatibility is under evaluation.
Binary files are first-class repository objects.
Streaming storage
Large binaries stream to and from S3-compatible object storage, with reads bounded and deduplicated rather than fetched whole.
Git LFS adapter
A Git LFS transfer path is implemented and round-trip tested against real clients. Qualification is pending.
Binary conflicts
When two tasks change the same asset, both versions are preserved as a conflict candidate instead of one silently overwriting the other.
Bounded previews
Image previews are bounded in size and format. Previewing is safety-tested; it never attempts arbitrary rendering.
Immutable asset dependencies
Tasks record which asset revision they depend on, so a change to an asset can be traced to every dependent task.
02 — Git LFS compatibility
Real clients, qualified scope.
Strata implements a Git LFS transfer path that has been round-trip tested against real Git LFS clients, with shared publication validation so transfers are verified against the authoritative repository state before they are acknowledged.
That implementation is under evaluation. It is not yet declared generally available, and the supported operation set has not been fully qualified against every Git LFS client behaviour.
| transfer | Real-client round-trip tested |
|---|---|
| validation | Shared LFS publication validation |
| status | UNDER EVALUATION · NOT GENERALLY AVAILABLE |
Never overwrite a competing change silently.
Binary files cannot be merged line by line, so Strata does not pretend they can. When two concurrent tasks edit the same asset, Strata returns a structured conflict that identifies the file, the overlapping revisions and both competing versions. Nothing is published until the conflict is resolved explicitly — the same integration discipline as code, applied to assets.
Bounded previews, not arbitrary rendering.
Strata renders bounded image previews for supported formats only. Previewing is capped in size and covered by a safety test; it does not attempt to render unknown or unsafe content. Large or unsupported files stay stored and retrievable, without being forced into a previewer.
Know what depends on which asset revision.
Asset revisions are immutable, and tasks record their dependency on specific asset revisions. When an asset moves forward, dependent tasks are flagged so agents re-check their work against the current revision instead of silently carrying a stale asset. Retrieval is available through the CLI, the API and MCP.
Binary assets today.
| Capability | Status |
|---|---|
| Ordinary binary blobs · streaming storage | Implemented |
| Binary conflict preservation | Implemented |
| Bounded image previews | Implemented · safety-tested |
| Immutable asset dependencies | Implemented |
| Git LFS adapter (real-client transfer) | Qualification pending |
| API / CLI / MCP retrieval | Implemented |
Implementation does not equal availability. Binary asset capabilities are implemented and being qualified; they are not yet declared generally available.