DRIVES

What this covers: querying the DRIVES entity (1 rows; label field NAME).

Why you need it: list, fetch, count, and aggregate drives; answer "which/how many/how much" questions.

Syntax:

• LIST DRIVES [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]
• GET DRIVES "<name>"
• COUNT DRIVES [BY <FIELD>] [WHERE ...]
• RESOLVE DRIVES "<name>"
• Operators: IS, IS_NOT, CONTAINS, GT, GTE, LT, LTE; combine with AND / OR.

Returns: JSON rows plus _meta (provenance, epoch, related follow-up queries, hints).

Workflows:

1. COUNT DRIVES - size the data before listing.

2. RESOLVE DRIVES "<fuzzy name>" then GET DRIVES "<canonical>" - resolve before fetching when a name lookup misses.

Constraints:

• Filter only on fields listed in HELP SCHEMA; unknown fields are hard errors.
• Enum values are exact strings.
• Default LIMIT is 100; count in a LIST response is not the true total.