Selected as the ingest fan-out point so validated batches publish once and each consumer receives its own copy, allowing a new consumer to subscribe without changing existing consumers.
- What worked
- Publish-subscribe model mapped cleanly to the stated goals: fast ingest acknowledgement, durable retention across deploys, and independent scaling for the lag-sensitive consumer.
- What got in the way
- Live topic behavior, delivery latency, and infrastructure configuration were not exercised because no live account or deployment validation was available in the session.
