Open the README on what a Bot is, and mark the project alpha

The opening described a workspace for agents that operate a browser, which
reads as the whole of it. Lead instead with the teammate you hand work to,
then the three things that distinguish this one: a computer per Bot rather
than one per account, every action decided beforehand and recorded after,
and answers drawn as components.

Also say plainly that this is alpha and moving, so nobody arrives expecting
otherwise.

Author: davidmckayv

README.md

@@ -1,12 +1,16 @@
 # OpenBot
 
-OpenBot gives an agent a computer of its own and puts boundaries around what it does with it.
+Bots are teammates you hand real work to. They sign in to apps and websites and use them the way you do, on a computer that stays theirs between sessions. Name one, give it a role, grant it access as it earns it, and talk to it in a channel.
 
-Bring any AG-UI agent, written on a framework or by hand, and it arrives as a teammate with a container to itself: a live Chromium session that keeps its logins between sessions, a filesystem, and only the tools you have granted it. One Bot cannot read another's files or use another's sign-ins.
+OpenBot is the open one. It runs on your own machine, it takes any AG-UI agent you bring, and it puts the boundaries where they belong.
 
-Everything it then does is decided before it happens and recorded after. Every page opened, file written, MCP tool called and component drawn passes the boundary you set, and the trail holds what was allowed and what was refused, each refusal naming the rule that refused it. When it reaches something it should not do alone, it stops and asks, and you take the wheel in its browser and hand it back.
+**Every Bot gets a computer of its own.** Not one machine per account that everything you have made shares. Each Bot gets a container to itself: its own Chromium holding its own logins, its own filesystem, and only the tools you granted it. No Bot can read another's files or reuse another's sign-ins, so separate Bots really are separate boundaries.
 
-It answers in components rather than only prose, and you can write a new one in the browser and publish it without a rebuild. Conversations, memory and threads are durable through CopilotKit Intelligence.
+**Every action is decided before it happens and recorded after.** Each page opened, file written, MCP tool called and component drawn goes past a policy you write, and into a trail that keeps what was allowed and what was refused, every refusal naming the rule that refused it. When a Bot reaches something it should not do alone it stops and asks, and you can take the wheel in its browser and hand it back.
+
+**It answers in components, not only prose.** Charts, tables and forms are drawn into the conversation, and you can write a new component in the browser and publish it without a rebuild. Threads and memory are durable through CopilotKit Intelligence.
+
+> **Alpha, and under active development.** OpenBot is early. Expect rough edges and bugs, and expect things to move. Issues and pull requests are welcome.
 
 > **Runs on your machine.** Everything below is written for a laptop. Out of the box OpenBot runs with `OPENBOT_DEV_NO_AUTH`, which skips signing in and admits every request as one administrator; [Google sign-in](#sign-in-with-google) can be wired up instead.