A consistency level describes what a read can promise about writes. Elm Catalog uses Session consistency so its client flow can rely on the documented session behavior without pretending every unrelated reader always sees the latest global write. That distinction matters when requests move between application instances.
The session token is part of the application's consistency context. Preserve it appropriately when the flow crosses clients or service instances, and choose a stronger or different contract only after reviewing the supported account configuration and workload constraints. The local account stores the declared setting but does not replicate documents, issue session tokens, or simulate stale reads. You will configure accounts and make checked decisions about those limits. A successful local account creation must not be described as proof of real read-after-write or regional failure behavior.
Choose and carry a consistency contract deliberately.