Skip to content
Back to resources

2026-10-14 · 3 min read

Understanding SDK Contract Boundaries

Understand the shared contract source and compatibility workflow.

A shared contract source

The SDK defines the public data contracts used across VISIONGO applications. C++ DTO headers are generated from JSON schemas. Applications consume the generated headers and do not edit them directly.

Keep application boundaries

Applications communicate through public contracts and formal transports. They do not import each other's private source directories, headers or internal symbols.

Change contracts first

Update the contract source, regenerate the bindings and run compatibility checks before updating producers and consumers. Prefer optional additions. Breaking changes require a protocol version change.

Check consumers

Validate all affected producers and consumers, including error paths and older peers. A successful build alone does not prove wire compatibility.