# RECYNEX integration and handover checklist

Use this checklist to define an interface discussion. The signed project event contract and security specification govern implementation.

## System boundary

- List supported equipment models, firmware versions and site identifiers.
- Name the sending and receiving systems and their technical owners.
- Distinguish classification, physical acceptance, reward eligibility and material handover.
- Define event IDs, schema versions, timestamps, units and data retention.
- Agree authentication, authorization, credential rotation and test environments.

## Failure and recovery

- Test rejection, duplicate delivery and acknowledgement loss.
- Test disconnection before and after physical acceptance.
- Define local queue limits, replay order, retry policy and permanent failures.
- Reconcile equipment events with the receiving system and any reward ledger.
- Make participant messages accurate when a connected service is pending or unavailable.

## Operational handover

- Identify who monitors integration errors and how incidents are escalated.
- Record acceptance tests, unresolved issues and sign-off owners.
- Assign collection and downstream material reconciliation separately.
- Confirm that no browser state alone issues a real reward or bypasses equipment safety controls.

Bring a sample event or API description to an integration discussion with RECYNEX at support@recynex.com.