This week on the floor
Example figures from a demonstration week. Real figures, reviewed before publishing, take their place once a floor is published.
- Fires423 −40%
- Completion rate94% ±0%
- Stopped for a person12
- Spend$2.07 −67%
- Incidents85 −73%
Hire by job description
You do not configure a platform. You write a job description, choose what the colleague may reach, set a monthly budget and working hours, and decide what they must stop and ask about. These are example roles.
-
IN
Inbox Manager
Ivy · weekdays 08:00–17:00 SAST- Does
- Reads incoming mail, labels and prioritises it, drafts replies to routine messages, and escalates anything unusual.
- Reaches
- Shared mailbox (read, draft) · Calendar (read)
- Stops for
- Sending to a new external address · anything about money or terms
typical month$3–6 -
AW
AWS Monitor
Neo · on shift 24/7 · manager of the Environments Team- Does
- Watches EC2, alarms and health events; reads live state before answering; raises a Floor incident on a silent stall.
- Reaches
- AWS (describe, alarms; no writes without approval)
- Stops for
- Any change to a running instance · spend above the envelope
typical month$1–2 -
MU
Murex Analyst
Nayla · weekdays 07:00–18:00 SAST- Does
- Answers questions about trades, positions and processing scripts from the MX.3 estate; compares extracts line by line.
- Reaches
- Murex MX.3 (read, via the connector) · the extracts you hand it
- Stops for
- Any post-trade action · anything leaving the estate
typical month$8–15
Every run leaves a receipt
This is what a colleague hands back. Not a chat transcript: the brief, each step with what it touched and how long it took, the point where it stopped for a person, the result, and the price.
- READLive state, not memory. Colleagues are made to look before they answer. A monitor may not describe your estate from yesterday's notes.
- STOPApproval is a pause, not a dialog. The run is frozen in the database, survives restarts, and resumes when a person decides. From the app, Teams or WhatsApp.
- COSTPriced per run, capped per month. Each colleague has a budget envelope. When it is spent, they stop and tell you.
- KEEPKept on the record. Steps, approvals and who decided them are retained under the periods in the privacy policy.
- briefQuery live EC2 state across all regions and list what is running. Promised to Neo.
- 1aws_ec2list_instances · af-south-1, eu-west-1, us-east-13.1 s
- 2aws_cloudwatchdescribe_alarms · 2 in ALARM1.2 s
- 3reason17 stopped, 3 running, 1 alarm on a production disk2.4 s
- ■stopaws_ec2 · reboot_instance — declined by Neo after 12 mperson
- 4replytable of running instances, alarm noted, no action taken0.9 s
Where it runs, and what it may see
Kion Assistant runs in Kion Consulting's own cloud tenancy or inside your estate. You choose the AI providers. Nothing you do is used to train models, and nothing is sold or used for advertising.
- Your systems, your keys. Each connection is granted separately, scoped, and can be withdrawn. Credentials are injected after the policy decision, never shown to the model.
- Your choice of model. Anthropic, OpenAI, Azure OpenAI, DeepSeek, Mistral, xAI, Moonshot, Z.ai or a model you host yourself. Per colleague, per duty.
- Your channels. The browser, Microsoft Teams, WhatsApp, email, and a desktop agent for the machines a colleague may use.
- Your rules. Read-only by default; approval before writes; budgets that halt; an audit trail you can export.
| What we ask for | Why, and when |
|---|---|
| Your name, email address and profile picture | To create and identify your account, show who is who inside a shared workspace, and send you the notifications you ask for. Requested when you choose to sign in with Google or Microsoft. |
| Your mailbox, if you connect it | So a colleague can read the threads you point it at and draft or send replies on your instruction. Requested only when you add a mail connection, and never at sign-in. |
| Your calendar, if you connect it | So a colleague can answer questions about your schedule and arrange the meetings you ask it to arrange. |
| Your files, if you connect storage | So a colleague can open the documents and spreadsheets you name, and write back results where you tell it to. |
| Your contacts, if you connect them | So a colleague can address a message to the person you name rather than asking you for an address every time. |
| Your Microsoft Teams chats, if you connect Teams | So a colleague can read the messages you send it in Teams and reply in the same chat or channel. Requested only when you connect Teams, and never at sign-in. |