Chat

Chat is where SEMANTIX answers questions. You ask in ordinary language; the agent works from your scope’s governed context and runs validated read-only queries to answer.

Scoped and open conversations

A conversation is either governed or open, and the difference is what it can see.

A governed conversation works inside a scope: its entities, metrics, and business rules, and nothing beyond them. This is the mode you want for questions about your data. See context scopes.

An open conversation has no scope, and works from whatever tools the attached agent has. That is open mode, and it is deliberately unguarded.

What the agent works from

• The entities reachable from your scope’s metrics, with their full column lists as registered in the Registry.
• Your scope’s certified metrics and their definitions.
• Your scope’s certified business rules — instructions it is expected to honour.

It is not the entire warehouse schema, and it does not preload sample rows. When it needs a literal for a filter, it can look up the distinct values of a specific column on request.

Validated execution

Generated SQL passes an AST validator and a dry-run gate before it runs. Anything that is not read-only, or that fails validation, is refused with a reason rather than attempted. Executed queries are visible in the thread, so you can read what was actually run.

Only SELECT, WITH, EXPLAIN, SHOW, TABLE, and VALUES are permitted, and results are row-limited. See read-only by design.

What a conversation keeps

Each successful answer is saved with your question, the validated SQL, and a bounded sample of the result — so you can check the work without rerunning it.

Two limits, stated plainly: a turn that failed is not kept, and results are stored as a sample rather than in full. The history is a record of what worked, not a complete transcript of every attempt. See grounding in practice.

Conversations

Conversations are scoped and private to you — a thread belongs to the person who started it. You can start new ones, and switch between them.

Getting better answers

• Ask about certified things. Questions about a certified metric get its definition; questions about an uncertified one rely on inference.
• Be explicit about grain. “Revenue by region by month” and “revenue this quarter” can legitimately differ; say which you mean.
• Check the SQL. It is in the thread, and reading it is the fastest way to catch a wrong assumption.
• State your business rules. If a rule matters and is not certified on the scope, say it — or ask an owner to add it so everyone gets it.