Limits & scope

What the language does not do, and what the engine is not — stated plainly so there are no surprises.

Language limits

· No OFFSET — paginate with an opaque CURSOR.
· No HAVING, no subqueries, no LIKE/regex.
· ORDER BY is single-field and requires LIMIT.
· count() only — no count(field) or DISTINCT.
· CONTAINS works on lists only.
· Ghost routing covers flat AND filters; OR/NOT scan the primary.
· Max response frame 256 MB.

Engine scope

Single-node by design: no replication, no encryption at rest, no cross-lobe transactions (each write is atomic via its WAL batch). Optional TLS 1.3 and a bearer token (--tls-cert / --auth-token) cover transport and access; deploy on an encrypted volume.

No SQL/Cypher shim, no UDFs, no per-record access control. The WHERE grammar is closed; access control is delegated to your network layer.