Storage Model

Where eve records live and what should be committed.

eve stores product history inside the repository.

.eve/
  config.json
  snapshots/*.json
  artifacts/<snapshot-id>/*
  cache/

Canonical files

The canonical product records are snapshot JSON files under .eve/snapshots/.

These files should be committed to Git. They are the durable product history.

Artifacts

Artifacts are supporting evidence for snapshots. They can be repository paths, local files, URLs, screenshots, videos, logs, notes, or conversation records.

Artifacts should be safe to commit. Do not store credentials, private customer data, or machine-local secrets in .eve/.

Cache

.eve/cache/ is rebuildable. It exists to make local browsing and indexing fast.

Cache files should not be treated as the source of truth.

Drafts

The CLI stages a draft before committing it as a canonical snapshot. Drafts are useful when product meaning is assembled while implementation and verification are still in progress.

After eve commit, the draft is validated, Git facts are derived, and a canonical file is written under .eve/snapshots/.

On this page