Reproducible query — Product (shared drive)

HELP FILES

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.

FILES

What this covers: querying the FILES entity (20 rows; label field NAME).

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

Syntax:

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

2. COUNT FILES BY IS_FOLDER then LIST FILES WHERE IS_FOLDER IS "no" LIMIT 10 - segment, then drill in.

3. SUM FILES DEPTH BY IS_FOLDER - aggregate by segment.

4. RESOLVE FILES "<fuzzy name>" then GET FILES "<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 (e.g. IS_FOLDER: no, yes).
Default LIMIT is 100; count in a LIST response is not the true total.

epoch 1source generated-context

Raw envelope — what an app or agent receives

{
  "ok": true,
  "query": "HELP FILES",
  "verb": "HELP",
  "subject": "FILES",
  "data": {
    "topic": "FILES",
    "content": "# FILES\n\nWhat this covers: querying the FILES entity (20 rows; label field `NAME`).\n\nWhy you need it: list, fetch, count, and aggregate files; answer \"which/how many/how much\" questions.\n\nSyntax:\n- `LIST FILES [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]`\n- `GET FILES \"<name>\"`\n- `COUNT FILES [BY <FIELD>] [WHERE ...]`\n- `SUM FILES <NUMERIC FIELD> [BY <FIELD>] [WHERE ...]`\n- `RESOLVE FILES \"<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 FILES` - size the data before listing.\n2. `COUNT FILES BY IS_FOLDER` then `LIST FILES WHERE IS_FOLDER IS \"no\" LIMIT 10` - segment, then drill in.\n3. `SUM FILES DEPTH BY IS_FOLDER` - aggregate by segment.\n4. `RESOLVE FILES \"<fuzzy name>\"` then `GET FILES \"<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 (e.g. IS_FOLDER: no, yes).\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"
    }
  }
}

Certificate · Playground · What you can ask