Claros v0.2.2
v0.2.2 — Engine Core
The lifecycle engine now runs end to end.
- Segment-compatible event ingestion (track and identify) with API key auth,
server-side deduplication, and partitioned event storage - Contact model with trait merging, conflict recording, and a unified lifecycle
state machine covering seven states - Flows defined in plain language and compiled once by an LLM into a
deterministic execution plan, with a bring-your-own key - Flow execution: enrollment with priority and re-entry rules, step advancement,
exit conditions, and engagement depth from incremental counters - Throttle gate with suppression, frequency caps, and timezone-aware send windows
- Drain and reap workers with crash recovery
Not yet functional: email content generation and actual sending. Messages are
created, throttled, and queued, but no transport exists yet, so nothing leaves
the system.