Developer Preview 0.3.0.dev2: This page documents the unchanged SDK 0.2.0 base contract. For the unified adapter, optional simulated motion and current installation commands, use the current quickstart and bundled docs. No real hardware or production integration is enabled.

Manufacturer visit and integration checklist

Bring a filled templates/manufacturer-checklist.json. Leave unknown facts unknown; attach evidence rather than promises.

1. Manufacturer/legal contact (business identity only), product/model/SKU, hardware revision, exact firmware/version/update/rollback method, expected support lifetime and secure update/boot evidence.
2. Choose software, device or hybrid. Identify every dependency: manufacturer app/service, native library, OS/build/CPU, signed driver/source/version, install privilege and license. Can each declared capability operate without the manufacturer app? Without internet? Record each separately.
3. List USB classes/vendor protocols, Bluetooth classic/BLE profiles, Wi-Fi protocols/ports and physical interfaces. Document API/SDK availability, versioning, download/redistribution rights, sample code provenance, supported languages, support contact and end-of-life plan.
4. For microphone and speaker: codecs, PCM byte order, sample rates, channels, chunk sizes, simultaneous input/output, latency, volume/control limits, resource ownership and interruption behavior. For camera: formats, dimensions, conversion, frame delivery, privacy indicator and permission behavior. Protocol acknowledgement is not physical proof.
5. For each capability: route, exact recipient, transport, required native permission/consent, retention, unsupported behavior and offline/cloud dependency. The initial public contract supports nine capabilities only; extra device functions do not become generic commands.
6. For cloud dependencies: operator/domain/region, data categories, purpose, transfer authorization, authentication method (never provide secrets in the checklist), mandatory account/subscription, fees, rate limits, retention/deletion, availability and applicable terms. This kit makes no cloud calls and supplies no credentials.
7. Security: identity proof/attestation, signed updates, device reset/revocation, lost-device response, malicious adapter containment, vulnerability reporting, secret handling and audit evidence. Same-user subprocess isolation is insufficient proof.
8. Physical matrix: exact model × firmware × OS/driver × transport × capability. Mark declared/simulated/observed separately. Provide evidence for failure paths and revoke/reconnect/no-replay, not only a demonstration video.
9. Licensing and certification: the supplied LICENSE_PT.txt and any separately required redistribution approval, third-party inventory, source/binary availability for review, privacy/security obligations and approved review recipient. No official certification is available from a local pass.
10. Next step: prepare the offline review packet. No purchase, factory commitment, credential enrollment or live integration is authorized by this checklist.