Skip to content

Say which serialization boundary a claimed read model crosses - #2534

Merged
woksin merged 1 commit into
mainfrom
docs/imp-18-serialization-boundary-by-ownership
Aug 12, 2026
Merged

Say which serialization boundary a claimed read model crosses#2534
woksin merged 1 commit into
mainfrom
docs/imp-18-serialization-boundary-by-ownership

Conversation

@woksin

@woksin woksin commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Changed

The page explained which provider wins and why compliance makes Chronicle the
one that has to, but not the consequence that costs people time: the winner
also decides how the injected instance is materialized, and the three providers
cross entirely different boundaries.

A consumer whose MongoDB convention, element rename or custom serializer does
not apply to a command-side read model had no way to learn why from the
documentation, and the failure is quiet and directional - the customization
works plainly on the query side, which is the surface anybody checks first, so
it looks discovered and correct while reaching nothing on the command path.

The API's own remarks already say this. The page a consumer reads did not.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: 49eab3a7-0743-4895-8303-bf5632b6a992
@woksin
woksin merged commit 1fbe732 into main Aug 12, 2026
7 of 8 checks passed
@woksin
woksin deleted the docs/imp-18-serialization-boundary-by-ownership branch August 12, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant