Integrations and event ownership

• Event source. Agree which sender provides an external event identity and how its provider name appears on a receipt.
• Identity source. Map named people to app users so assignments and authored updates point to the right person.
• Equipment inventory. If another system owns asset tags or serial numbers, agree a stable import mapping before loading assets.

For each sender, agree the event identifier, received date, payload hash and meaning of each receipt state. A repeated event should be reconciled against its original identity before the team applies it again. Rejected and failed receipts need a named reviewer and a correction path. Test a normal delivery, an invalid record and a repeated identity with the source owner before relying on the connection. Plan the first operating cycle.