Stéphane Tailland 95b6e3a1c9 docs: the events are emitted by the API, and what that implies
Recording where the work lands and the two facts about that codebase that
shape it: every write passes through one BaseModelViewSet, so one hook covers
every domain; and the models are managed = False, so a transactional outbox
introduces the estate's first Django-managed table beside the pre-existing
schema.

Emission belongs in the API rather than a database CDC or a gateway plugin,
because only the API knows which change is a business event and only it holds
the sub/azp that the event must carry for a downstream agent to act under the
same authority.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-29 13:49:18 +02:00
S
Description
No description provided
266 KiB
Languages
Python 91.4%
Dockerfile 8.6%