Skip to main content

​
What the storage layer does

Storage connects:
  • local translation files,
  • sidecar provenance metadata,
  • remote adapter APIs.

​
Supported adapters

​
Entry identity

Each translation entry is identified by:
  • key
  • context
  • locale

​
Why sidecar metadata exists

Your user-facing text stays in normal translation files. Operational metadata (for example draft vs curated state) stays in sidecar metadata files so translation content remains clean.

​
Pull and push lifecycle

  1. run generates local drafts (origin=llm, state=draft).
  2. sync push sends local changes to remote storage.
  3. Human translators curate values in remote TMS.
  4. sync pull applies curated changes locally.

​
Conflict rules

  • Pull can auto-apply curated-over-draft when enabled.
  • Push protects curated remote values by default.
  • --fail-on-conflict prevents silent drift.
  • --force-conflicts is opt-in for risky overwrite paths.
For specific conflict decisions, see conflicts.