Integrations and source ownership

• Kubernetes API. Agree how cluster identity, version, namespace and workload readiness are read into the operating records.
• Telemetry provider. Agree how readings enter workload observations and how the team identifies the affected service during incident review. Retain external event identifiers in integration receipts for reconciliation.
• Deployment pipeline. Let the operator compare execution results with an approved change and later workload observations. Keep the plan and status outcome in the change record.
• Identity provider. Map authorized users to People so ownership and attributed incident updates use the intended accounts.

Agree which system owns each field, the source event identifier and the treatment of retries before enabling routine intake. Store credentials in the approved secret store. Compare received, applied, rejected and failed receipt outcomes with source events so an intake failure remains visible. A provider event does not decide incident priority, approve a change or close a service issue. Named team members make those decisions using the linked records and their access rights.

Prepare the implementation with a sample source event and an exception case.