Connections

• External effect source. When an operation receipt carries an external reference, connect the authoritative system that can confirm the effect before closing that receipt.
• Evidence files. Attach the file your team uses as delivery proof to the parent package and choose its visibility for review.
• Platform identities. Link each team members entry to its User so ownership and reviewer decisions have a named actor.

Agree who can configure an external source, which reference identifies an effect and how reviewers compare expected results. Keep the operation key and expected revision on the receipt. If the source and local record disagree, leave the exception open for review and attach the comparison to the package. Use the completion reconciliation path to test this before the first live event.