Define the decision
State the useful outcome of the proposed connection. A courier update, publication feed and factor source have different records, risks and authority needs. Name the external service, operator and exact data exchanged. Separate a read-only discovery link from an authenticated integration capable of creating or changing commitments.
Build a usable record
Check access terms, licensed fields, authentication scope, secrets handling, recipient permissions and data retention. Identify who can activate, pause and revoke the connection. Define how records will retain source, version and timestamps. For write actions, specify the authorised trigger and how duplicate attempts will be prevented or recognised.
Check the evidence boundary
Test normal, unavailable, stale and conflicting responses in an authorised environment. An adapter should not convert an empty response into a favourable result or treat an unconfirmed dispatch as success. Provide a manual recovery route and a visible pending state. Agree support responsibility and change-review triggers before relying on it in a customer journey.
Worked example — illustrative
In a fictional factor connection, a source changes its unit label while keeping a similar numeric value. The adapter rejects the unexpected schema and leaves calculations incomplete rather than applying the factor as kilograms automatically. A reviewer resolves the version and unit issue before approved use resumes.
Put the method into practice
Use the permission register to document the proposed scope, then attach test evidence and activation authority. A listed source on Leaf is not an active connection. Actual integrations require the shared engine, commissioned external production services and the responsible operator’s verified setup.
- Define data and operations.
- Check rights and credential scope.
- Test stale and failed responses.
- Record activation and revocation authority.