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>
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>
Stéphane Tailland