xarmian 378dec5244 docs(idspace): name the assumption the incarnation bound rests on (BUG-2736) ...

Codex round 8, on a fresh angle. The invariant was stated in terms of publish
RATE -- an id can repeat across incarnations only if the earlier process
published more than 2^20 events per millisecond of its life -- and quietly
assumed the other half: that the next start lands in a LATER millisecond.

The bases are separated by the clock at millisecond resolution, and the CAS
separates only buses built inside one process. A second process starting
inside the same millisecond as the first would take the same base and reissue
its ids.

Not closed, and the reason it is acceptable is physical rather than hopeful:
reaching the constructor means the OS reaped the old process and the new one
bound its listener, opened its database and ran migrations. Closing it for
real needs persistence, which BUG-2736's body rules out for a separate and
stronger reason. So it is accepted and NAMED -- in the package comment and in
deployment.md -- rather than left for the next reader to find during an
incident.

Claude-Session: https://claude.ai/code/session_01JVDBKbgn3Xt7ndW1YoYd8X

2026-08-22 19:54:19 +00:00

..

idspace_test.go

fix(events): give each in-memory bus incarnation its own ID space (BUG-2736)

2026-08-22 18:14:45 +00:00

idspace.go

docs(idspace): name the assumption the incarnation bound rests on (BUG-2736)

2026-08-22 19:54:19 +00:00