SECTIONS

What this covers: querying the SECTIONS entity (36 rows; label field ID).

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

Syntax:

• LIST SECTIONS [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]
• GET SECTIONS "<id>"
• COUNT SECTIONS [BY <FIELD>] [WHERE ...]
• SUM SECTIONS <NUMERIC FIELD> [BY <FIELD>] [WHERE ...]
• RESOLVE SECTIONS "<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 SECTIONS - size the data before listing.

2. RESOLVE SECTIONS "<fuzzy name>" then GET SECTIONS "<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.