Skip to main content

The application chat

Every generated application includes a chat (<project>/chat/) in which people work with the application in plain language: find records, run the business's reports, and open the application's own screens inside the conversation to create, edit and approve.

Narrow by construction​

  • The assistant has four read tools (search records, summarise a record, search reports, run an approved report) and four screen openers (open a record, a create form, an update form, an approval).
  • It never writes a record. The person saves in the embedded screen, under optimistic locking and every access check, and the save comes back to the conversation only after it has been read back.
  • It never sees a credential, a cookie, a raw URL or SQL. Records are opaque references issued per person, and screens are view ids that expire.
  • Filesystem, shell, browser and plugin capabilities are disabled, and a test fails if one is turned back on.

Sign-in​

People sign in once with their application account. The chat stores its own sessions in a separate database, never in the application's.