Why GitTrix
Why agent workflows need ephemeral-first storage and explicit promotion gates.
AI coding agents generate massive amounts of speculative code, and most of it should never touch durable history.
GitTrix exists to enforce a simple rule: agents work in ephemeral storage; humans promote accepted changes to durable storage.
Core thesis:
- Agents get no durable-write path.
- Backends are swappable runtime choices, not hardcoded destinations.
- Promotion is content-level curation, not replaying messy agent commit history.
This keeps real history clean without blocking fast agent iteration.