4 Commits

Author	SHA1	Message	Date
Stéphane Tailland	b62b92fe1a	Add the procurement topic and Supply's write access to it ... reorder.requested and its answer (confirmed/rejected) share the topic, keyed by the reorder id, so ordering between the ask and the answer holds the way it does for a product's own facts on classic-models.catalog. Supply both writes and reads this topic — one service, two capacities, not a separate procurement identity, per the 2026-08-31 decision. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-31 16:17:05 +02:00
Stéphane Tailland	d633d409fc	Drop the old Kafka account now the consumer has moved ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-31 14:57:53 +02:00
Stéphane Tailland	f5484dd67f	Add the supply account beside the one it replaces ... Two at once so the consumer can move without a gap; the old one goes as soon as it has. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-31 14:56:06 +02:00
Stéphane Tailland	f0ec5c47e2	Administer the Kafka topology centrally ... Topics and accounts on the shared cluster belong to the platform team, for the same reason the gateway defaults do: an ACL is not a team's decision to make about itself, and a partition count is not a team's decision to make about the cluster. They had been pushed into the application repos on the argument that ownership follows use. That argument holds for a contract, not for a grant. Self-service is a different thing and does not come from moving these files: it comes from an event gateway that virtualises topics and a developer portal that socialises them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-31 08:50:54 +02:00