Key concepts
Levels, projects, agents, data sheets, automations, actions, connections and credits: every word you will meet, defined once.
Every word you will meet in the product, defined once. The sidebar uses plain business words (AI Agents, Data Sheets, Automations); some pages and older screens still use the platform's own names (K-Agent, Live Workbook, Job). Both are listed here.
Where you work
| Term | What it means |
|---|---|
| Level | One of the three parts of Kareenos, chosen from the level menu at the top of the sidebar: 1 · Kareenos runs your operation, 2 · Workspace shows it, 3 · K-Apps ships your own apps. |
| Advanced | The builders' area beside the levels: editors, monitoring and system pages. Not a level you climb. |
| Project | The container for one operation. It holds the data, the agents, the automations and the screens. Nothing crosses from one project into another. The current project is shown in the top bar. |
| New Task | The first row of every level: where you ask the Super Agent for something in your own words. |
| Super Agent | Your building assistant behind New Task. Describe what you need and it plans and builds it: projects, agents, automations, widgets and pages. It does not run your day to day work. |
| Inbox | Everything your agents need from a person: approvals, short forms and tracked tasks. The home page of every team member, on the web and in the myKareenos app. |
| myKareenos | The phone app your team uses for the Inbox, tasks, photos and location in the field. |
What gets built
| Term | What it means |
|---|---|
| AI Agent (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 an agent can load when it needs it, so one agent can cover several tasks without losing the thread. |
| Data Sheet (Live Workbook) | Your data, organised like a workbook. A Sheet is one table (Customers, Jobs, Vehicles), a Column one field, a Row one record. A workbook groups the sheets of one operation. |
| Automation (Job) | Work 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. |
| Document | A written piece an agent produces for a person to read: a policy, a summary, a runbook. |
| Connection | Anything outside Kareenos your project uses: a WhatsApp number, a mailbox, a calendar, a database, a tool server. Set up from Connections. |
| Event | A note that something happened (a message arrived, a row changed, a vehicle left a zone). Agents and automations 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. |
| 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. |
| Team | A group of people with the same access. Putting someone in the right Team decides what they can see and do. |
| Marketplace | A catalogue of complete projects, published by others or by you, that can be imported into an account. |
At levels 2 and 3
| Term | What it means |
|---|---|
| Dashboard | The first screen of the Workspace: live tiles that sum up the project at a glance. |
| Page | A named screen your team opens every day, made of widgets and listed under Pages in the Workspace. |
| Widget | A live tile on a page or dashboard. Some present information (a list, a chart, a number), others collect it (a form, an editable grid). |
| Report | A branded, paged, printable document built from your data, ready to send or save as a PDF. |
| App | An application of your own, outside the Kareenos screens, built with Claude Code and hosted by Kareenos at its own address. |
| K-API | One route of an app: something the app's screens can ask Kareenos to do, served by an automation you own. |
| Embed | One of your agents published as a public link or a chat on your website, for people without a login. |
Credits
Two balances pay for what Kareenos does. SC (Super Agent credits) are spent when the Super Agent designs and builds for you. KC (K-Agent credits) are spent when your own agents run: answering customers, thinking, taking decisions. Automations and screens do not spend agent credits. The SC balance sits in the top bar; both balances are in the account menu. See Subscription and 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 in their Inbox.