lemma

space · bots

Agents and flows

The mechanics: what happens after the click.

what it is assembled from

  1. a message in the channel the person is already in
  2. a flow a graph with state, not a long conversation
  3. an agent one step of the flow, not the whole program
  4. data a knowledge base, a spreadsheet, somebody’s API
  5. a person when the machine has nothing to answer
the same skeleton under every bot we build

A bot is not a window with messages in it. It is state: where the person arrived, what they have already chosen and what the system has to do next.

work

2026

Grant Invest

siteinterfacebot

A site for a company that helps industry get state support, and a Telegram bot that answers the same questions in words.

see the work
  1. page or bot two surfaces, one conversation
  2. the request a name and a phone — a chat needs no more
  3. a service on the server, reachable only from inside
  4. telegram where the request is actually read
a request takes one path, wherever it came from

2026

Neznaika on Phuket

botflowsrequests

An island’s Telegram bot: housing, transport, visas, currency exchange, help when something goes sideways. Six buttons that turned out to be an operating system.

see the work
  1. a person
  2. a flow
  3. a request
  4. a table
  5. a manager
  6. a status
a request comes back to the person who sent it

infrastructure

Agents are assembled on our own platform, iisy: graph flows, an agent as a single step, knowledge bases, external calls, channels and conversation analytics. The client sees only a working bot — and an invoice with no line for a platform licence.

Mechanics need a surface.

sites
ask