Reproducible query — Product (shared drive)
HELP LABELS
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.
LABELS
What this covers: querying the LABELS entity (4 rows; label field FILE_ID).
Why you need it: list, fetch, count, and aggregate labels; answer "which/how many/how much" questions.
Syntax:
LIST LABELS [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]GET LABELS "<file_id>"COUNT LABELS [BY <FIELD>] [WHERE ...]RESOLVE LABELS "<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 LABELS - size the data before listing.
2. RESOLVE LABELS "<fuzzy name>" then GET LABELS "<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 LABELS",
"verb": "HELP",
"subject": "LABELS",
"data": {
"topic": "LABELS",
"content": "# LABELS\n\nWhat this covers: querying the LABELS entity (4 rows; label field `FILE_ID`).\n\nWhy you need it: list, fetch, count, and aggregate labels; answer \"which/how many/how much\" questions.\n\nSyntax:\n- `LIST LABELS [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]`\n- `GET LABELS \"<file_id>\"`\n- `COUNT LABELS [BY <FIELD>] [WHERE ...]`\n- `RESOLVE LABELS \"<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 LABELS` - size the data before listing.\n2. `RESOLVE LABELS \"<fuzzy name>\"` then `GET LABELS \"<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"
}
}
}