Glossary
Definitions of important terms used across the site and API.
A runnable prediction service or model. Each source has a unique name (for example, `mildew-predictor`). A source describes the algorithm and how it should be executed, but not the tenant-specific configuration.
An immutable release or snapshot of a Source (for example, a git SHA, a semantic version like `v1.0.0`). Jobs are pinned to a specific Source Version to ensure reproducible results. Note: A source version corresponds directly to a **Service** in the Management backend. The `source_version.id` is the `service_id` used for authentication along with the service password.
The normal interval, in minutes, between runs of a model. An expected interval of 15 means the model is expected to run every 15 minutes.
How long, in hours, a prediction may be kept after its measured time (`datetime_measure`). A prediction for 25 August 2026 at 06:00 with 24-hour retention becomes eligible for deletion from 26 August 2026 at 06:00, and is deleted when a cleanup job next runs.
The logical name for a required input a Source needs to run (for example, `ambient_temp`). Defines the expected data contract (type/metric) but not which physical sensor provides the data.
The logical name for a prediction result produced by a Source (for example, `disease_index`). Similar to input roles, these are decoupled from concrete storage until a Job is configured.
A organisation-specific configuration that tells the system to run a particular `source_version` with concrete bindings and schedules.
The mapping between a Source's `input_roles` and concrete data providers (for example linking the `ambient_temp` role to sensor `abc-123`).
A system-level representation of a prediction output. When a Job runs, its results are assigned to a "Virtual Sensor" so they can be treated as first-class data streams for visualization and alerts.
A standardized unit or category of measurement (like `celsius`, `mm`, or `lux`). Both Roles and Sensors are associated with Metrics to ensure data compatibility.
A time-based scheduling expression used to run periodic jobs. especify minutes/hours/day-of-month/etc.
A way for the service to send an HTTP POST to an external URL when a specific event occurs (for example, job completion).
Application Programming Interface — the set of HTTP endpoints used to interact with the platform programmatically.
The data sent in a request or event (for example, prediction inputs or webhook bodies).
A group of jobs or predictions processed together (often used for bulk workflows).