cratis-chronicle-client-elixir

The Chronicle client for Elixir

cratis_chronicle is a standalone client SDK. It is a library, not a framework: it starts no supervision tree of its own, you add Chronicle.Client to yours, and everything after that is ordinary OTP.

Verified product sources

This skill is verified against Cratis/Chronicle.Elixir at tag v2.2.0, which is the version actually published on Hex.

Fact	Value	Source
OTP app / Hex package	:cratis_chronicle	Source/chronicle/mix.exs:14
Published version	2.2.0	hex.pm
Elixir requirement	~> 1.14	Source/chronicle/mix.exs:16
Contracts dependency	cratis_chronicle_contracts resolved to 16.13.4	Source/chronicle/mix.lock

The v2.3.0 git tag was never published to Hex. mix deps.get cannot fetch it. Anything introduced there — notably the Chronicle.Concept macro, which does not exist at v2.2.0 — must not be documented as available.

The repository's VERSION file says 0.0.5 and is a build-time placeholder overwritten by the publish workflow. Never quote it.

Do not copy from the repository's root README.md. At v2.2.0 it uses module names that do not exist — use Chronicle.EventType, use Chronicle.ReadModel, use Chronicle.Reactor, use Chronicle.Reducer, use Chronicle.Seeder (README.md:9-13, :49, :54). The real modules are namespaced: Chronicle.Events.EventType, Chronicle.ReadModels.ReadModel, Chronicle.Reactors.Reactor, Chronicle.Reducers.Reducer, Chronicle.Seeding.Seeder. Copy from Documentation/client-snippets/ instead — those are CI-validated and correct at every version.

Documentation/get-started.md:12 pins {:cratis_chronicle, "~> 0.1"}, which does not match the published 2.2.0. Use a 2.x requirement.

Adding it

# mix.exs
defp deps do
  [
    {:cratis_chronicle, "~> 2.2"}
  ]
end

The library declares extra_applications: [:logger, :inets, :ssl] and no mod: (Source/chronicle/mix.exs), so nothing starts on its own. :inets and :ssl back the least-connections load balancer's HTTP probes.