Reproducible query — Product (shared drive)
HELP SECTIONS
Anyone opening this link re-runs the same query against epoch 1, so it returns the same answer — that is what makes a number in a report checkable later.
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;
countin a LIST response is not the true total.
epoch 1source generated-context
Raw envelope — what an app or agent receives
{
"ok": true,
"query": "HELP SECTIONS",
"verb": "HELP",
"subject": "SECTIONS",
"data": {
"topic": "SECTIONS",
"content": "# SECTIONS\n\nWhat this covers: querying the SECTIONS entity (36 rows; label field `ID`).\n\nWhy you need it: list, fetch, count, and aggregate sections; answer \"which/how many/how much\" questions.\n\nSyntax:\n- `LIST SECTIONS [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]`\n- `GET SECTIONS \"<id>\"`\n- `COUNT SECTIONS [BY <FIELD>] [WHERE ...]`\n- `SUM SECTIONS <NUMERIC FIELD> [BY <FIELD>] [WHERE ...]`\n- `RESOLVE SECTIONS \"<name>\"`\n- Operators: IS, IS_NOT, CONTAINS, GT, GTE, LT, LTE; combine with AND / OR.\n\nReturns: JSON rows plus `_meta` (provenance, epoch, related follow-up queries, hints).\n\nWorkflows:\n1. `COUNT SECTIONS` - size the data before listing.\n2. `RESOLVE SECTIONS \"<fuzzy name>\"` then `GET SECTIONS \"<canonical>\"` - resolve before fetching when a name lookup misses.\n\nConstraints:\n- Filter only on fields listed in HELP SCHEMA; unknown fields are hard errors.\n- Enum values are exact strings.\n- Default LIMIT is 100; `count` in a LIST response is not the true total.\n"
},
"_meta": {
"epoch": 1,
"provenance": {
"source": "generated-context",
"stage": "P4"
}
}
}