Background ingest and curate

The daemon loop runs ingest (hot path) and curate (cold path) on independent schedules. It is not a separate CLI command: it runs inside lerim serve (and therefore inside lerim up / Docker).

Intervals

Configure in ~/.lerim/config.toml (or via an explicit LERIM_CONFIG override) under [server]:

Setting	Typical default	Description
ingest_interval_minutes	30	How often the daemon runs ingest
curate_interval_minutes	60	How often the daemon runs curate

Normal backlog ingest claims the newest available session per project first so recent corrections are extracted quickly on first run. Historical replay paths can still request oldest-first catalog ordering when chronological reconstruction is required.

What to run

lerim serve          # JSON API + background loop
lerim up             # Docker: same combined process

Use lerim ingest / lerim curate for one-shot runs via the API, or rely on the background loop when the server is up.

Related

• lerim serve — combined server entrypoint
• lerim ingest — one-shot hot path
• lerim curate — one-shot cold path
• lerim status — queue and last-run info