Projection Queries | Cessy Builder Docs

Projection queries read current runtime state. They should be narrow, predictable, and tied to the projection’s published schema.

Common controls

Control	Purpose
`limit`	Maximum number of rows to return.
`offset`	Pagination offset.
`sort`	Sort field and direction when supported by the projection.
`filter`	JSON filter expression over projection fields.

Exact query parameters come from the generated OpenAPI contract for the app.

Filter shape

Use structured filters instead of string-built query fragments. Supported operators depend on the projection query contract and can include equality, containment, prefix matching, and case-insensitive matching.

Avoid unbounded text search unless the projection is designed for it.

Output shaping

Projection tools and APIs can support output controls to reduce payload size. Use them for agent workflows so the model receives only the fields needed for the task.

Builder guidance

Design projections around real read questions. If every client has to fetch a large projection and filter locally, the projection shape is probably wrong.