Teams

People and Dus, on one team.

Duscode starts with one person and one engineer called Dus. Teams are the next step. Here is what works today, what is in beta and what is still coming, straight from the evidence.

What is ready, from the evidence.

The stages come from the same record as Capabilities.

Seats and roles

On the Team plan you invite people to your team by email. Each person gets a seat, and owners decide who manages the team. Each person runs Duscode on their own computer, with their own sessions, budgets and a Proof of Work for every task.

A shared workspace

Coming, not built yet: one place where you see each other’s work, decisions and budgets from any computer, with shared budgets and permissions per role.

Rooms

Coming, not built yet: a room where your people and AI specialists work a problem together. Anyone can raise a hand. When the room wraps up, the outcome becomes decisions, each credited to whoever made it, and nothing ships until it has passed two approval gates. AI specialists are always labelled as AI.

Clients and collaborators

  • A view for your clients (coming): show a client the progress and proof of their project without giving them your workspace. Today you can export a task’s Proof of Work as Markdown or a single HTML report and send it.
  • Collaborators abroad (coming): work with people outside the UK, with the UK International Data Transfer Agreement (IDTA) built into how access is given.
For engineers

Within one project today, several sessions already coordinate on one machine: each works in its own git worktree, claims files before editing, reserves ports and migration numbers, and waits for another session’s merge when their work overlaps. The Team view in the app lists them. Details: Sessions working together.

Running an agency? See For agencies.