Commissioning documentation
Collect commissioning acceptance evidence
Keep receipts for each published acceptance gate instead of relying on a self-reported readiness score.
Check the core functions
The published gates include identity and memory, two model routes, voice, an approved computer action and an approved connector. Test the actual configured paths and keep evidence tied to the commissioned machine and configuration.
Check ongoing operation
The gates also cover a recurring task receipt, sponsor policy block, backup and restore, a configured revenue workflow and final evidence. A revenue workflow being configured does not establish a sale or collected revenue.
Record open items
For every gate, record the input, observed output, time and remaining limitations. Keep failed or unrun checks open until they are demonstrated. Acceptance should reflect the agreed scope and actual result.
Continue
Reviewed September 17, 2026. Current product terms and availability are listed on the product site.