Bind robot configuration to the policy release.
The same policy bytes can have different consequences under different sensors, actuators, controller gains, frames, or runtime versions. Release identity should include the configuration assumptions that matter at dispatch.
Request a Shadow AuditChoose the configuration boundary
List the inputs that change the policy-to-controller contract: device identity, controller package and parameters, model preprocessing, observation and action schemas, coordinate frames, and relevant runtime versions.
Create a stable digest
- Normalize the selected configuration into a canonical manifest.
- Reference immutable artifacts rather than deployment filenames.
- Hash the manifest and include the digest in the policy release.
- Make the gateway compare the observed trusted digest before dispatch.
Change workflow
A configuration change that affects the declared boundary creates a new release or requires new approval. Do not silently update a configuration object behind an existing approved digest.
Limitations
A digest proves equality to declared configuration, not that the configuration is safe or complete. Teams must decide the boundary through engineering analysis and retain independent protective controls.
Continue the architecture review
Ready to map the release path? Request a Shadow Audit.