An interface contract explains what each record means and when a receiving component may rely on it. Agree asset references, timestamps, units, frames, uncertainty, versions, and validity conditions. At the action boundary, add authority, preconditions, request identifiers, and outcome associations.
Test these meanings across components. A source can use unknown to mean no observation while a receiver treats it as normal. Two systems can call a task complete at different events. Successful data exchange does not establish that the parties share the same interpretation.