Start a controlled pilot
Begin with one critical operation, one isolated test environment, and agreed acceptance criteria.
Review an example first
Follow the receive-configuration walkthrough from a 20-to-32 confirmation change through approvals, authorization, scheduling, execution and evidence. Open the interactive demo or read the selected source and recorded contract checks directly on GitHub.
Use Release evidence to identify the dates, code revisions and environments behind each result. The public sample's evaluation terms apply to copying and running it; the private core is a separate component.
1. Choose the operation
Describe the exact change your team needs to authorize: for example, a protocol upgrade or a risk-parameter update. Identify the current approval process, who controls execution, and whether any alternative route can bypass the proposed control.
See Protected operations and Protocol upgrade. Check integration status in the compatibility matrix.
2. Agree on the scope
Before implementation, both teams confirm:
- the test environment, operation and permitted values;
- the technical and acceptance contacts on each side;
- which integration work and dependencies are included;
- the expected effort and responsibilities; and
- what constitutes a pass, a failure, or an unresolved result.
Use synthetic data or test assets. Do not send private keys, production credentials or identifiable customer records.
3. Receive the scoped integration material
Approved participants receive version-matched interface details, synthetic examples and acceptance instructions through an agreed access-controlled channel. Environment-specific setup and operational guidance are provided only to the relevant technical reviewers.
For integration materials and source review, see Source and documentation access.
4. Validate the workflow
The acceptance plan should cover an approved request, a changed or out-of-policy request, expiry or replay where applicable, and evidence inspection. Simulation, authorization, transaction handoff and confirmed execution must remain distinct results.
5. Review the evidence together
Record what passed, what did not, and which assumptions remain unverified. A completed controlled pilot does not establish production readiness, independent node operation, external audit or protection of real assets.