Architecture
Magistr is a Rust workspace with one project authority and several clients. The public product model is deliberately small:
- Native state stores roadmap chunks, ship tasks, reasoning steps, checks, and artifacts.
- Application services coordinate a use case and own completion semantics.
- Clients present the shared model. The terminal cockpit owns terminal input and rendering; the desktop client has its own renderer.
- Protocols stay at their boundary. Terminal byte protocols belong to
magistr-tui; the cockpit remains independent of them.
Workspace map
| Crate | Responsibility |
|---|---|
magistr-domain | Project concepts and invariants |
magistr-application | Use cases and ports |
magistr-engine | Native persistence and workflow execution |
magistr-cockpit | Shared interface model and updates |
magistr-tui | Terminal input, graphics, and runtime |
magistr-mcp | In-process MCP tool definitions |
magistr-cli | The magistr command |
Read the architecture overview and owned subsystems in the repository for the complete boundary map.
A useful mental model
The user steers a roadmap. A ready chunk becomes a ship objective. The active client records actions and checks against that objective. A later session reads the same native state and can continue without guessing what happened.