18a8bf38a724c8caa4f6edcb836ab3cbd6e321cd
An earlier revision collapsed detection and ordering into one nightly run. They are not the same job: detecting a coming stock-out depends on something happening and should be woken by it, while proposing a purchase order is genuinely periodic — grouped by supplier lead time, not by unit sold. Recorded because it changes what has to be built: the autonomous mandate is a cost of choosing a clock, not of the business need. Kafka is the target for the reactive half. Nothing in the estate emits a domain event today, which is what made a nightly sweep look inevitable. Detection stays unbuilt until then rather than being approximated by a periodic scan — a batch pretending to be reactive is worse than an absent feature, because it looks finished. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
No description provided
Languages
Python
91.4%
Dockerfile
8.6%