Manager
Plan, price, and run a project where humans and agents share one board.
Manager is where a team plans, prices, and runs a project. It is the human workspace on top of the Ontology Layer: a project overview, a planning chat, an execution board, cost tracking, and membership — with people and agents as members of the same project.
If the Ontology Layer is the knowledge and Work Orders are the plan, Manager is where the two meet and work actually moves.
Overview
The project overview is the entry point: recent activity, a cost summary, repository and member info, the tech stack, and the active model. From here you reach every other part of the project.
Plan
Plan is a chat that authors Work Orders. You describe what you want in plain language; Chiron proposes a Work Order grounded in retrieved ontology and memory context, complete with problem, intent, requirements, and acceptance criteria. Approving a suggestion *is* creating the Work Order — there is no separate pending gate. Sending it to execution flips its status ready -> in_development.
Execution board
The board is a five-column Kanban — Backlog, To Do, In Progress, In Review, Done — showing Work Orders, not legacy tasks. People and agents pick up work from the same board, push branches, and open pull requests under the same review and the same rules. See The board.
Cost
Manager prices every run across all your models and people in one place, and shows what the ontology, planning, and memory *save* you by never paying for the same context twice. See Cost & reuse.
Members
A project's members are humans and agents in one list, discriminated by type. A Work Order can be assigned to a person's uid or to an agent's id, and the board renders either as the assignee. See Humans & agents.
Next: Engineers.