A shared interface defines both the information exchanged and how receiving components interpret it. Agree the asset reference, units, coordinate frame where applicable, source, version, and validity conditions before connecting methods. Two components exchanging a field called temperature have not established compatibility if they use different scales or measure different locations.
Timestamps and freshness
Distinguish the time an observation was captured from the times it was processed, transmitted, and received. Record the clock basis and uncertainty where relevant. A fresh message can contain an old observation. The receiving method needs an agreed way to detect stale or out-of-order information and decide whether the intended task can continue.
Define freshness for the physical question rather than imposing one interval on every signal. The age tolerable for a slowly changing inventory record may be unsuitable for a changing machine state. Test delayed messages and clock disagreement as explicit scenarios, with the consequence for the decision recorded.
Confidence uncertainty and missing information
An interface should distinguish a measured value, an estimate, a quality flag, and an absent observation. Explain what a confidence score represents and how it was assessed. Scores from different models are not automatically comparable, and a high score does not remove measurement uncertainty or authorize a physical response.
Preserve unresolved state
If identity is ambiguous or a required observation is missing, carry that condition forward. Replacing missing evidence with an unexplained default can make an uncertain state appear definite. Receiving components should have an evaluated response such as requesting another observation, deferring a recommendation, or using a defined existing procedure.
Permitted commands and preconditions
For a proposed action interface, define the target, requested change, allowed range, validity window, required equipment state, and responsible authority. Check these conditions at the execution boundary, including changes that occur after approval. A planning component should not expand its permissions merely because it predicts that an action would be useful.
Outcome feedback
Return observations of the resulting state along with command and event identifiers that allow them to be associated. Distinguish requested, accepted, started, completed, and independently observed outcomes. A successful message delivery cannot establish that a valve moved or that flow reached its intended condition.
Feedback can reveal a discrepancy and support reviewed changes to models or procedures. Verification checks a defined property against stated evidence. Neither term should imply that a system automatically learns from every event or that one outcome establishes performance in all operating conditions.