Seeds
Defined data. Compact changes. Shared understanding.
Compatibility & Interoperability
Keep the Definition Across Platforms
Data seeds carry the values. A transport binding supplies the definition, delivery identity, and acknowledgement contract.
HTTP · Available
The Trie-Trunk logger negotiates definitions and delivers batches to ingress. A successful call requires a staging acknowledgement. See the Logger integration.
Brokers · Proposed Bindings
Kafka, AMQP, and JMS are candidates for adapters that carry seed payloads and definition references. Each binding must specify partition or ordering keys, retries, acknowledgements, and replay behavior; these adapters are not implemented yet.
Existing JSON Producers
A bridge can map source fields into an accepted data definition before encoding. Mapping and validation must be explicit; a binary payload alone does not make mismatched schemas compatible.
A Shared Codec Boundary
Pill Packer provides the portable PIL and PAC implementation for Rust, with initial JavaScript/WASM and Go reader bindings. Transport and delivery policy remain with the integration.