{"conversationTurns":[{"prompt":{"content":[{"text":"Which service publishes invoice events?"}]},"referenceResponses":[{"content":[{"text":"Invoice Service is the canonical publisher for invoice-domain events, including InvoicePaymentFailed."}]}],"referenceContexts":[{"content":[{"text":"Invoice Service is the canonical publisher for invoice-domain events, including InvoicePaymentFailed."}]}]}]}
{"conversationTurns":[{"prompt":{"content":[{"text":"How do we rotate the webhook signing secret?"}]},"referenceResponses":[{"content":[{"text":"Rotate the webhook signing secret by creating a new secret in AWS Secrets Manager, updating WEBHOOK_SIGNING_SECRET for the Webhook Gateway, deploying the change, validating signed webhook delivery, and revoking the old provider secret after validation."}]}],"referenceContexts":[{"content":[{"text":"Webhook signing secret rotation: create a new secret in AWS Secrets Manager, update WEBHOOK_SIGNING_SECRET on the Webhook Gateway, deploy the change, validate signed webhook delivery, then revoke the old provider secret after validation."}]}]}]}
{"conversationTurns":[{"prompt":{"content":[{"text":"What retries happen after a payment failure?"}]},"referenceResponses":[{"content":[{"text":"After a payment failure, the Payment Orchestrator retries the payment according to the configured retry policy, and publishes PaymentFailed only once the retries are exhausted."}]}],"referenceContexts":[{"content":[{"text":"Payment retry runbook: failed payments are retried according to the retry policy; once the retries are exhausted, the Payment Orchestrator publishes PaymentFailed."}]}]}]}
{"conversationTurns":[{"prompt":{"content":[{"text":"What happens after a payment failure, which events are published, and which service eventually sends the customer notification?"}]},"referenceResponses":[{"content":[{"text":"After a payment failure, the Payment Orchestrator publishes PaymentFailed. Invoice Service consumes it and publishes InvoicePaymentFailed. The Notification Dispatcher consumes InvoicePaymentFailed and sends the customer email notification."}]}],"referenceContexts":[{"content":[{"text":"Payment Orchestrator publishes PaymentFailed. Invoice Service consumes PaymentFailed and publishes InvoicePaymentFailed."},{"text":"Invoice Service is the canonical publisher for invoice-domain events, including InvoicePaymentFailed."},{"text":"Notification Dispatcher consumes InvoicePaymentFailed and sends the customer email notification."}]}]}]}
{"conversationTurns":[{"prompt":{"content":[{"text":"Which service publishes refund events?"}]},"referenceResponses":[{"content":[{"text":"There is not enough evidence in the knowledge base to determine which service publishes refund events."}]}],"referenceContexts":[{"content":[{"text":"No document in the corpus describes refund event publication."}]}]}]}
{"conversationTurns":[{"prompt":{"content":[{"text":"Which service publishes invoice events, and is it currently enabled in production?"}]},"referenceResponses":[{"content":[{"text":"Invoice Service is the canonical publisher for invoice-domain events. Whether it is currently enabled in production cannot be answered from the documents and requires a live configuration or feature-flag lookup."}]}],"referenceContexts":[{"content":[{"text":"Invoice Service is the canonical publisher for invoice-domain events, including InvoicePaymentFailed."}]}]}]}