Total.js Totem: design
Totem is an AI coding environment written as a Total.js 5 application. You open a project, talk to an agent that reads the code, edits files and runs commands, and review what changed. The same application runs from a terminal, in a Docker container and inside a native window.
These pages describe what Totem does and why. They are the contract for the code: when the code and a page disagree, one of them is a bug. The README of the repository is the way in; the roadmap says what is built and what is next.
| Page | What it answers |
|---|---|
| Vision | What Totem is, who it is for, what it will not do |
| Architecture | Folders, processes, the request path, how Total.js features are used |
| Agent loop and tools | How a prompt becomes edits; tools as actions |
| Data model | Projects, sessions, messages, parts, snapshots and where they live |
| Protocol | REST endpoints and the WebSocket events the interface speaks |
| Permissions and security | What the agent may do, what it asks for, how the server is protected |
| Interface | Screens and the jComponent components they use |
| Capabilities | The list of features, each with its phase |
| Knowledge | How the agent knows Total.js (recipes, Forge, checks) and how to measure it with any model |
| Delivery | Command line, Docker image and native windows |
| Roadmap | Phases, each with the condition that closes it |
| Decisions | Decisions taken and the ones still open |
How to read the status of a statement#
- Verified statements about Total.js name the file of the framework that supports them.
- A statement that says done is built and has a test; one that says simulators only has not been tried with the real service.
- Open questions live only in decisions.