# Records

A record is one recording: a single patient trace, one machine run, or one market window. A record
bundles three things. To open a page, click its box.

```mermaid
flowchart TB
    Record["<b>Record</b><br/>one recording"]
    TS["Time series<br/><i>one or more signals</i>"]
    AN["Annotations<br/><i>static · point · interval</i>"]
    TK["Tasks<br/><i>training targets</i>"]
    Record --> TS
    Record --> AN
    Record --> TK
    click TS "time-series.html" _self
    click AN "annotations.html" _self
    click TK "tasks.html" _self
```

- **[Time series](time-series.md)** are the raw signal: a record has one or more signals, such as the
  vibration and temperature signals of a machine.
- **[Annotations](annotations.md)** are scoped side-information: a label, an event, or a full reading.
- **[Tasks](tasks.md)** are the labeled training targets built from the record.

A record has no metadata slot. Record-level context, such as a subject's age, the device, or the
split, is an [annotation](annotations.md) with no span.

## Modalities and units

A typed [spec](../types.md) declares each modality once: a name and the unit of its values. TimeF
carries the unit as a [pint](https://pint.readthedocs.io) unit. The unit is part of the type. So
different signals read through the same API. Examples are an accelerometer trace in g, a temperature
signal in °C, and a market series in a currency. The spec declares no unit for time. Time offsets are
whole microseconds by construction. So a caller cannot state another unit.