Adapters
An adapter extends ZAITRACK. Each one belongs to a family:
| Family | Does |
|---|---|
codec | decodes a device protocol into positions and events, and encodes commands |
connector | sends platform data to another system (an export, a regulator) |
datasource | brings outside data in (toll and fine files, fuel statements) |
action | does something when a rule fires |
ai | an AI capability |
Some codecs are built in; others require a marketplace installation. See Codecs. The catalogue has a page for every adapter ZAITRACK publishes — whether it works today, how to use it, its settings, credentials and limits, and what to check when it does not work. Anyone can browse them in the marketplace.
When ZAITRACK publishes one of its adapters in the registry, it signs it with its platform key (ECDSA P-256), the only key its organisation may sign with there. Its codecs are published that way, each version approved on two conformance runs (the crate's own tests and codec-runtime's golden frames); the catalogue lists them.
Publishing your own
Publishers work in Adapter Studio, signed in with their ZAITRACK account. An organisation's owners and admins make changes; its other members can read.
- Register a signing key: an ECDSA P-256 public key.
- Create a project: its slug, family, name, licence and visibility.
- Submit a version: the manifest, its signature and the artifact.
- Review: ZAITRACK staff record a conformance run and approve or reject.
- Installations: organisations install approved versions and give the settings the manifest declares.
Publish an adapter walks through each step with the exact commands.
What is not there yet
- An approved version and an active installation do not prove that a device can connect or that a deployment has prepared its runtime. Marketplace codecs run in codec-runtime's WASM sandbox; built-in codecs use the platform's built-in implementation. TCP and UDP adapter routes need a port allocated by ZAITRACK. Codec readiness explains the separate checks and the current preparation limits.
- Connectors and data sources run on connector-host, which links ZAITRACK's own; a third party's connector does not run on the platform. None is published as working yet: each is proven against its provider's sandbox first. The catalogue says which adapters work today.
- A project's marketplace listing is curated by ZAITRACK, not created from the project.
- Partners cannot yet publish for the organisations under them.
- Adapter Studio has no public API: the registry is reached through the studio only.