Show SQL & feedback

STYD is built to be transparent: for many answers you can see the logic and the query behind the result, and you can give feedback when something is off.

When the SQL is visible

For answers produced from your database, STYD can show a “How I found this” panel. The generated SQL and a technical trace are available there, collapsed under technical details so non-technical users are not forced to read them.

Showing the query supports transparency, debugging, and audits, you can confirm exactly what was run against your data. On Odoo there is no SQL: the panel shows which Odoo records were read and the filters and period applied.

What non-technical users should look for

You do not need to read SQL to trust an answer. The panel also explains, in plain language:

  • a short summary of what STYD did
  • the business logic used
  • the filters applied (such as dates, status, or company)
  • the data used to answer
  • any assumptions, for example when no date range was given

Giving feedback

Each answer can be rated:

Helpful (thumbs up)
Marks the answer as helpful.
Not helpful (thumbs down)
Opens a short form to explain what went wrong.

The “Not helpful” form lets you pick the closest reason (for example wrong number, wrong period, missing data or wrong language) and optionally describe the answer you expected. There is no field for SQL.

What feedback is used for

Feedback helps STYD’s team review answers, build evaluation cases, and improve the product over time. It is not a guarantee of instant correction, flagging one answer does not immediately retrain the system. Improvements are reviewed before they take effect (see Brief your assistant).