Requester: Copper Returns integration lead. Done: one event delivered to two subscriptions, independently inspected and acknowledged, with the production proof boundary stated.
Copper Returns needs independent ledger and audit consumers. You will create a topic and two subscriptions, publish one original event, then inspect and complete each subscription separately. Every accepted step remains part of the carried local account.
The exercise deliberately separates delivery from the fictional completion notice before acknowledgment. The browser does not execute a ledger transaction, call an audit service, or run real lease clocks. Use the returned acknowledgment handle for settlement and retain the event reference as the business identity. The final handoff must say exactly what the local pipeline demonstrated and which real consumer, retry and recovery behavior still needs testing.