What it means for an assistant to know you best
Knowing you is not storing everything you said. It is a memory you can read, correct and delete, kept where you hold the keys. Here is how to test yours.
- memory
- personal assistant
- privacy
Pre-launch · chapter 2/5 · trust
kyber bot --remember meYour SI should work only for you
KyberBot is the personal assistant that knows you best. Its memory is yours: kept on your own devices, encrypted, readable by nobody else. It lives in every KyberDeck form, from a card on a lanyard to a robot in the hallway, hands the heavy work to KyberAgent swarms, and asks you before anything sensitive.
- Memory on your devices, encrypted
- One person to answer to: you
- Asks before anything sensitive
- One assistant, from a card to a robot
The problem
The assistants you can rent today work for someone else
Three reasons an assistant that knows you well is, today, hard to trust.
err 01
It has a second customer
A rented assistant serves you and the company whose business is your data and your attention. When those two interests pull apart, you are not the one it was built to side with.
err 02
Your memory lives on their servers
To know you, an assistant has to remember you. Today that memory sits in someone else's data centre, under their retention policy, one breach or one change of terms away from being somebody else's.
err 03
It cannot act, or it acts without asking
Either it is a chat window that can do nothing, or it is handed your accounts and acts on them with no moment where it stops to ask, and no record of what it did.
How it works
Remember, ask, hand off
Three habits that make an assistant worth trusting with your day.
- 01
Remember
KyberBot builds its memory of you from what you choose to share: people, plans, preferences, the way you like things done. That memory lives on your devices and your home node, encrypted with keys you hold.
- 02
Ask
Before anything sensitive, such as money, a message in your name, someone else's details or a motion in the physical world, it stops and asks. What counts as sensitive is a policy you can read and change.
- 03
Hand off
Work bigger than a conversation goes to a KyberAgent swarm, each agent in its own KyberCell. KyberBot writes the brief, keeps your memory out of their reach, checks what comes back and gives you the answer.
What it does
An assistant, documented like a terminal
Each line is a promise about how KyberBot behaves, written the way we intend to document it.
| command | what it does |
|---|---|
| kyber memory show | Lists what KyberBot remembers about you, where each item is stored, when it learned it and why it kept it. |
| kyber forget | Removes a fact, a person or a whole week from what it knows, on every device you own. Forgetting is a command, not a support ticket. |
| kyber policy edit | Opens the rules for what KyberBot may do without asking: spend, send, share, move. Plain text, versioned, yours. |
| kyber delegate | Hands a task to a KyberAgent swarm with a brief, a budget and a deadline, and reports back with what was done and what it cost. |
| kyber log | Every action taken in your name: who asked, which rule allowed it, what happened. Readable without us. |
| kyber memory export | Writes the whole memory out in an open format, so leaving is a file copy rather than a negotiation. |
Illustrative: the commands describe behaviour. They are not a released CLI.
What is inside
Six reasons to trust it, all of them checkable
Trust here is not a feeling. Each of these is a property you will be able to inspect.
01
Your memory, your keys
The memory is encrypted with keys that live on your hardware, such as a security key on your keyring. Without them it is noise, to us and to anyone else.
02
Works only for you
No advertiser, no data broker, no second customer behind the conversation. KyberBot answers to one identity, and it is yours.
03
Asks before it acts
Payments, messages in your name, other people's details and motion in the physical world wait for your yes. The list is a readable policy, not a mood.
04
It runs the rest
KyberBot plans the work, hands it to KyberAgent swarms, chooses where it runs (on the device, on your node or in KyberFusion) and checks the result before you see it.
05
A harness when it has mass
In a robot, KyberBot carries a declared safety envelope below the planner, a homeostat that pulls autonomy back when the world stops matching the map, and a record of every motion.
06
Readable, top to bottom
Open source is the intent for the assistant, the policy language and the record format. Every action carries who asked and which rule allowed it, so you audit your own assistant instead of taking its word.
The system
KyberBot is the second chapter of KyberFusion
The deck is where you touch the system; KyberBot is who you talk to. Everything behind it, the swarms, the system and the cloud, answers to it, and it answers to you.
kyber stack --from you
01KyberDeck · bodyHardware around you, to buy or to build
02KyberBot · trust← you are hereThe assistant that knows you and runs the rest
03KyberAgent · handsSwarms of agents doing the work, each in its own cell
04KyberLinux · groundAn ultralight, secure, open system for SI
05KyberFusion · networkA sovereign cloud owned by the people who use it
↳KYBERIOS · businessThe Kyber stack as one operating system for a small business — built on all five layers, for one job
↳KYBERTIS · servicesThe company that deploys, hardens and supports Kyber, with an SLA — built on all five layers, for one job
One request, end to end
- you speak
- KyberDeck hears
- KyberBot decides, and asks when it matters
- KyberAgent swarms do the work
- KyberLinux keeps each agent in its cell
- KyberFusion lends power, paid in tokens
- the answer comes back to you
KyberBot is the step where trust is decided: what leaves your devices, which agent sees what, and what waits for your yes. Your data stays yours at every step.
Memory you own
The memory is yours, and so are the keys
An assistant that knows you best has to remember a lot. KyberBot keeps that memory on your own devices, the deck you carry and the node at home, encrypted with keys you hold, like a hardware security key on your keyring. It is designed so that we never hold a copy, which leaves us nothing to sell, leak or hand over.
- On your hardware: the long memory on your home node, recent context on what you carry.
- Under your keys: no key, no memory, for us or for anyone who takes the device.
- Yours to take away: export it in an open format, or delete it, with one command.
In a robot
An assistant with mass needs a harness
When KyberBot runs a robot, a wrong answer can become a wrong motion. So in a robot it carries the physical safety envelope: a harness that bounds what the machine may attempt, a homeostat that slows or stops it when the world stops matching the map, and a record of every motion it makes.
- Below the planner: a plan that breaks the envelope never becomes motion.
- Fail-closed: a policy that cannot be read stops the machine rather than being ignored.
- Every motion recorded, with what the robot believed and which rule applied.
- Above certified safety, never instead of it: emergency stops stay hard-wired.
Limits
What KyberBot does not do
An assistant earns trust by saying plainly where it stops.
- It is not available yet. Nothing to install, nothing for sale, no prices and no account to create.
- It does not sell, rent or share your data. There is no advertising business behind it and no second customer in the conversation.
- It does not act on sensitive things without asking. Money, messages in your name, other people's details and motion in the physical world wait for your yes.
- It does not replace certified safety in a robot. Emergency stops, safety-rated controllers and the standards behind them stay where they are; KyberBot sits above them.
- It is not a super intelligence. SI is what the system is built to carry. KyberBot is the part that makes sure it works for you when it arrives.
Where we are
Nothing to install yet, so here is the honest state of the work
KyberBot is pre-launch. Anything else on this page would be a promise rather than a status.
- Now
Memory, policy and the ask-first loop
The encrypted memory store, the policy language for what needs your yes, and the record format, on prototype KyberDeck hardware. In robots, the harness and policy layer on machines that actually move.
- Next
Closed pilots across the forms
A small number of people living with KyberBot on a card, a pocket deck and a home node, and one robot class running the harness in observe-only mode first.
- Later
Open release
Source, the policy specification and the record format published together, so the assistant you are asked to trust can be read by people who do not have to take our word for it.
FAQ
Frequently asked questions
What is KyberBot in one sentence?
KyberBot is a personal SI assistant that knows you best, works only for you, keeps its memory encrypted on your own devices, and runs the rest of the Kyber system on your behalf, asking you before anything sensitive.
What does SI mean here?
Super Intelligence, the name we use for the field as a whole. We use it because of what is coming, the most capable tool people have ever had, and because of who we think it should belong to: the people who use it, not the companies that rent it out.
Where does my data go?
Nowhere, by default. The memory stays on your devices, encrypted with your keys. When a task needs more power, KyberBot sends only what that task needs to a KyberAgent cell or a KyberFusion node built to keep it unlinked from you, and records that it did.
What counts as sensitive?
By default: spending money, sending anything in your name, sharing details about other people, signing you up for things and any motion in the physical world. You can tighten the list at any time; loosening it is a deliberate change that goes on the record.
Is it the same KyberBot in a robot?
Yes: the same identity and the same memory, with one addition. In a robot it carries a safety envelope (a harness below the planner, a homeostat and a record of every motion), and it sits above certified safety hardware, never instead of it.
How does it fit with the other Kyber projects?
KyberDeck is the body it lives in. KyberBot is the assistant you talk to and trust. KyberAgent is the swarm it hands work to, each agent in its own KyberCell. KyberLinux is the system underneath all of them, and KyberFusion is the sovereign cloud that lends power when your own devices are not enough.
Is there a KyberBot for work?
Yes, through KYBERIOS, the branch of the Kyber stack for small businesses: every employee gets their own KyberBot at work, with the company's memory kept apart from their private one.
Chapter 2/5 · Trust
Chapter two: trust
An assistant is useful in proportion to what it knows about you: your people, your plans, your habits, the things you would rather nobody knew. That is exactly why the assistants on offer today are hard to trust. They know you on behalf of someone else, and their memory of you is an asset on another company's books.
Ours is built the other way round. KyberBot remembers you on hardware you own, under keys you hold, and answers to one person. It says what it is about to do, stops before anything that matters, and keeps a record you can read. Trust is not a promise we make about it; it is a set of properties you can check.
An assistant that only talks is not much help, though. The work itself is done by many hands, each kept in its own cell, and that is the next chapter: the swarm.
Blog
All articlesNotes on memory, trust and machines that move
One assistant, many bodies
A card, a band, a pocket deck, a home node and a robot should not be five assistants. What changes between bodies, what must not, and how to tell which you have.
- identity
- memory
- devices
Your data is not the product
If the business behind an assistant is attention or data, the better it knows you, the more it is worth to someone else. Why KyberBot is built the other way round.
- privacy
- business model
- data
Be in the first cohort
The waitlist goes live soon. Until then, the blog is where the assistant's rules get argued.
No form yet, no data collected — just come back.