Transport
Can the producer and consumer exchange bytes over an available path?
Semantic and policy gates
A link becomes a usable mission path only when schema, meaning, time, provenance, confidence, security, authority, units, and deadline requirements align.
Research basis KW-RPT-002 KW-RPT-008 KW-RPT-013
Can the producer and consumer exchange bytes over an available path?
Do they agree on schema, identity, units, time, uncertainty, and transformations?
Can this data be released, trusted, and used by this consumer for this function?
Pathway verdict
Choose a producer and consumer to inspect every gate.
Protocol translation can connect systems that were never designed together, but it cannot automatically prove semantic equivalence, data integrity, releasability, or authority.
Minimum operational object
| Field | Why it exists |
|---|---|
| Global identity and correlation history | Prevents duplicate or merged objects from silently becoming one track. |
| Observation and update time | Allows age-of-information checks and deadline enforcement. |
| Reference frame, units, and uncertainty | Makes position and motion meaningful to the consumer. |
| Source and transformation provenance | Shows who produced or changed the data and how confidence was derived. |
| Classification and releasability | Allows data-level policy rather than network-location assumptions. |
| Validity period and schema version | Prevents stale or incompatible objects from being treated as current. |
| Authority and permitted use | Separates observation, recommendation, authorization, and execution roles. |
Answer-ready summary
A physical link can exist while the data remains unusable because meaning, units, time, identity, provenance, classification, or authority do not align.
Read the supporting pageIt compares abstract message contracts and exposes which technical, trust, and authority gates pass or fail.
Read the supporting page