← Back to the chapter · Previous detail
Technical detail · Protocol Bridging Fundamentals
Maintain versions and reconcile the evidence
When firmware alters a register or a cloud team renames a field, change the mapping version with the contracts. Store that version beside a sample trace so a reviewer can distinguish a sensor fault, an old mapping and the current target schema.
Schema compatibility is directional. Adding an optional target field may leave an old consumer working; renaming a required field can stop it. Changing a unit without changing the field name can leave a consumer running with a believable wrong value. Use fixtures from the current and previous protocol contracts during upgrades, and verify which side can be rolled back.
Observability means being able to tell what the bridge did from recorded signals. Treat those signals as outputs: count source reads, accepted translations, rejected mappings, target acknowledgements, retries, stale records and denied commands. For 100 source samples, accepted plus rejected must equal 100. Every accepted sample must reach a named target result or a visible pending state.
Approve the bridge only when fixtures for both protocol contracts produce expected records and named errors after a clean restart. The record should let a second reviewer retrace one reading from source to target and locate failures without reconstructing undocumented defaults.