Acceptance and operational handoff
Confirm the contract, data, exceptions, evidence and support ownership before operational handoff.
Conditions before deployment
Confirm contract/path/encoding/auth, state mappings, publication rights and deployment configuration. Documentation, fixture or offline website checks do not replace production API, Gateway, Agent or validation tests.
Settle RSS/SIC deployment conditions
Before go-live confirm namespace/base URL, authentication, provider/package, mode-specific schemas, callbacks, reconciliation and validation. Documentation UI tests do not replace API or native Agent acceptance.
Handoff requirements
- Contract and version
Confirm endpoints, schemas, authentication, states, errors and change control.
- Access and secrets
Test least privilege, rotation, revocation and environment separation.
- Exceptions
Test cancellation, expiry, outages, lost responses, duplicate and unordered events.
- Outcome and evidence
Agree verification, acceptance and evidence retention.
- Operations
Assign monitoring, alerts, reconciliation, support and recovery.
Acceptance evidence
- Approved success and failure test results.
- Operational contacts and ownership.
- Change, revocation and service-exit procedures.
Integration acceptance gates
| Item | Check |
|---|---|
| Contract | Agree URL/encoding/authentication, version and operations actually used. |
| Provider | Confirm mapping, eligible certificates and RAR/RS-HUB or SIC scope. |
| Unknown outcome | Test response loss, duplicate/out-of-order callbacks and UI disconnection. |
| Final document | Verify finalization and validation reports; retain evidence under approved policy. |
| SSO and data | Agree account/session, sharing consent, signing authority and demo disclosure. |