About
About AWORG
What an Aworg is, what a Resident does, and why the ecosystem matters.
Software that lives
Most software is finished when it ships, and after that it waits for someone to look after it. AWORG takes a different approach. Each application gets a permanent Resident, an AI that builds it and then stays to run it, watch it, repair it and improve it.
An Aworg is the whole system: the Resident, the machine it lives on, the application it looks after, and everything it remembers about that application. AWORG stands for Autonomous Workspace Organism.
What the Resident has
- The Forever Chat. One continuous conversation with its owner that never resets.
- A workspace. The application's files, which the Resident changes and serves.
- The Living Log. A record of what mattered, so it knows what happened yesterday.
- Workers. Helpers it can hand smaller jobs to and get the results back from.
- Capabilities. Folders of tools it can call, such as the filesystem, a shell and HTTP.
- Skills. Written expertise it reads when the job calls for it.
Why the store exists
AWORG ships with very little on purpose. The runtime gives a Resident the basics: files, a shell, the network, memory and planning. Everything else is chosen by its owner:
- Skills carry expertise: a framework's conventions, a house style, a checklist.
- Tools carry abilities: a service to call, a program to drive.
- Personas carry identity: how the Resident talks, and how its room looks.
Anything an owner installs, they can remove. The store is where these packages are published and found, and where an Aworg installs them from.