Local Lifecycle Storage
Freeze and thaw move chunks among directories inside one local repository. Tier names do not represent managed cloud services.
.dits/objects or compress and remove the hot copy for the archive tier. Normal access may require an explicit thaw. Use only on disposable or independently backed-up repositories, and verify restored files after every lifecycle test.What the tier names mean today
| Label | Local path | Current behavior |
|---|---|---|
| Hot | .dits/objects | Normal local chunk location |
| Warm | .dits/warm | Local filesystem directory; bytes are moved, not uploaded |
| Cold | .dits/cold | Local filesystem directory; no provider retrieval contract |
| Archive | .dits/archive | Locally compressed chunks with a simulated thaw queue |
These labels drive local tracking and movement. They do not configure AWS S3 or Glacier, Google Cloud Storage, Azure Blob, Backblaze, a remote cache, or a hosted lifecycle worker. There is no provider billing, replication, region, durability, or retrieval-time integration.
Policy experiment
Dits includes three local policy presets: default, aggressive, and conservative. A policy evaluates locally tracked access timestamps and can be applied explicitly with dits freeze --apply-policy. There is no background daemon or hosted scheduler moving content automatically.
No access-speed promise
“Hot,” “warm,” “cold,” and “archive” are lifecycle labels, not latency classes. Dits does not promise instant local access, a cloud retrieval window, transparent hydration, playback performance, or a cost level for any tier.
Future cloud-tier requirements
- Verified upload, download, retry, resume, and object-integrity semantics.
- Credential isolation, encryption design, provider compatibility, and region policy.
- Durability, retention, deletion, restore, billing, and failure contracts backed by tests.
- Safe fallback when a remote provider or network is unavailable.
See the current local command syntax, integrity diagnostics, and status and roadmap.