OSC Contract
The OSC Contract defines how control values enter the instrument layer.
The runtime remains transport-agnostic.
Control Flow
- Receive OSC externally
- Parse address/value
- Map to parameters
- Update
NodeProps
Guarantees
- No protocol dependency in core engine
- Latest value wins
- No implicit interpolation
Responsibility Boundary
Application layer handles:
- Socket lifecycle
- Message parsing
- Validation
- Value mapping
Runtime handles:
- Reading updated parameters
Recommended Practices
- Clamp values explicitly
- Log parameter updates
- Avoid blocking in control handlers