Key concepts
Projects, agents, jobs, workbooks, pages, actions and credits — every word you will meet, defined once.
Every word you will meet in the product, defined once. Come back to it whenever a screen uses a term you do not recognise.
The building blocks
| Term | What it means |
|---|---|
| Project | The container for one operation. It holds everything: the data, the agents, the automation and the screens. Nothing crosses from one Project into another. |
| Super Agent | The AI builder. You describe what you need and it plans and builds the Project for you. It does not run your day to day work. |
| K-Agent | An agent that lives inside your Project and works for you continuously: answering customers, deciding what happens next, calling other parts of the system. |
| Skill | A focused piece of know-how a K-Agent can load when it needs it, so one agent can cover several tasks without losing the thread. |
| Job | Automation with no AI in the loop: a fixed set of steps that runs on a schedule, or when something happens. Reliable and repeatable. |
| Action | A short request put to a person: confirm this, fill this in, choose one. It arrives in their inbox or as a form on screen. |
| Task | Tracked work assigned to a person, moving from open to in progress to done. It can carry stops, photos, scans and signatures. |
| Widget | A live panel on a screen. Some present information (a list, a chart, a number). Others collect information (a form, an editable grid). |
| Page | A named screen in your team's side menu, made of Widgets. Pages are how your team uses the system day to day. |
| Report | A branded, paged, printable document built from your data, ready to send or save as a PDF. |
| Document | A written artifact an agent produces for a person to read: a policy, a summary, a runbook. |
| Live Workbook | Your data, organised like a workbook. A Sheet is one table (Customers, Jobs, Vehicles). A Column is one field. A Row is one record. |
| Data Adaptor | A read-only connection to a system you already run, so its data appears as a Sheet. Kareenos reads from it and never writes back into it. |
| Event | A note that something happened (a message arrived, a row changed, a vehicle left a zone). Agents and Jobs subscribe to events and react. |
| Tool | One specific capability an agent is granted, such as sending a message or adding a row. Nothing is granted by default: an agent can only do what it was given. |
| Team | A group of people with the same access. Putting someone in the right Team is how you decide what they can see and do. |
| Marketplace | A catalogue of complete Projects published by others that you can import into your own account. |
| MyKareenos | The mobile app your team uses in the field for their Tasks, Actions, photos and location. |
Credits
Two balances are shown in the top bar. Super Agent credits are spent when the AI builder designs and builds for you. K-Agent credits are spent when your own agents run: answering customers, thinking, taking decisions. Automation Jobs and screens do not consume agent credits.
A rule of thumb for screens
Tip
Pages present, dialogs edit, actions ask. If your team is reading, that belongs on a Page. If they are entering or changing records, that belongs in a dialog opened from a Page. If an agent needs an answer from a person, that is an Action.