Queries that write themselves, and stay in their lane
A written requirement becomes a database query. Every generated query runs read-only, against an allow-list of tables, scoped to one workspace.
Generated expressions
The foundation under evaluated attributes, segments and workflow conditions.
- A requirement written in plain words becomes a query, stored beside a plain-English description of what it does. The expression itself stays on the server.
- Generated queries run through a sandbox before execution: SELECT statements only, an allow-list of tables, and a blocked list of functions.
- Execution happens on a read-only connection under row-level security, scoped to a single workspace per transaction.
Data in and out
- Records read back with their stored attributes, plus whichever evaluated attributes the caller asks to expand.
- Record inputs and outputs now share one definition, so an API call, an import and a workflow step all validate the same way.
maxinja
- The assistant data model was rebuilt around exchanges and typed interactions, which is what later made streamed, step-by-step responses possible.