Querying

Current Behavior

Squire currently supports lexical querying via Discord commands:

!find <query>: runs SQLite FTS search over canonical object title/body and returns numbered results.
!show <number>: expands one row from the latest numbered cursor (!recent, !active, !find, !status, or !weekly).
!detail <number>: shows the full raw note object for one row from the latest numbered cursor.
!active [number] [category]: lists active notes grouped by type with numbered rows.

This path is deterministic and local-first:

User runs !find <query>.
Query terms are normalized and executed against local SQLite FTS.
Matching canonical objects are formatted into numbered rows.
!show <number> uses the active cursor to display details for one result.
!detail <number> uses the same active cursor to show the full raw note object for one result.

There is no separate LLM query-to-JSON translation layer in current runtime querying behavior.

Squire does use LLMs for capture interpretation and update/append decision routing. That retrieve-then-decide pipeline is documented in: