Mapping
The source object is transformed into the destination fields explicitly rather than hidden behind a screenshot.
Reliability evidence
Successful sync is not enough. The failure path has to be inspectable too.
The Integration demo exposes explicit field mapping, a simulated transient failure, controlled retry and replay protection. These are representative mechanism checks, not production customer metrics.
What to inspect
A reliable integration needs behavior around the happy path.
Transient failure
The demo can inject one failure and expose whether the controlled retry subsequently commits the event.
Idempotency
Replaying the same event should be blocked from producing a second side effect.
Audit state
The event payload and log remain visible so the operator can understand what happened and why.
Why it matters
Invisible integration failures become manual reconciliation work.
A connector that works only when every dependency responds perfectly is not enough for an operating process. The package scope therefore includes testing, retry/error handling, idempotency protection where applicable and a written runbook.