Develop without a physical railway
Use isolated transport fixtures and the repository fake bridge for the behaviours each can actually establish.
Source 0.1.0 Private source package
Begin with a local transport fixture
The downloadable read-layout-state example has an automated fixture check against the real SDK. It verifies request scope, decoding and error propagation without starting services or touching saved railway records.
When you need bridge behaviour
Authorised repository contributors can use the maintained fake-bridge harness with disposable development records. Its protected setup stays in the repository guide. It establishes software protocol behaviour, not electrical DCC behaviour or physical speed matching.
Describe what the check proves
Keep transport, simulator and hardware evidence separate. A simulated acknowledgement establishes only its tested software behaviour. Hardware compatibility and physical results need their own reviewed evidence.