For teams
Not yet. Here is how it keeps AI agents inside the limits you set.
Consensus Logic is a single-user, local-first Windows product today. No SSO, no team administration, no cloud. This page exists so an engineering lead can see how authority, budget and evidence are handled, and leave a name for when that changes.
The problem this solves
Agents that cannot grant themselves scope.
The leads who ask about teams do not want agents that are smarter. They want spend that cannot surprise them, a Stop that works, and an audit trail per task that nobody had to build by hand. That is the architecture below. It is described as an architecture, not a promise: each row has an acceptance scenario, and the Proof page shows its status.
Two authorities, two records
Review authority and execution authority are separate. Planning cannot change a project. Running must be authorised separately, after the plain-English summary for that exact plan revision has been shown.
Allowances at every level
Calls, time and repairs are budgeted at account, project, task and step level. Every call is reserved before launch and settled after. Splits and retries never reset the budget. No model can grant itself scope.
Stop that works
Stop starts nothing new immediately and reports whether the work actually stopped, or says plainly that it cannot tell. An unconfirmed stop blocks the next action.
A record of every step
What changed, what passed, what failed, what remains unknown, and what to do next. Evidence is labelled product or mechanism and never mixed.
Project boundaries in trusted code
One project's context is never presented in another's task. The boundary is enforced by the controller, not by a filter on the screen.
One executing task at a time
No unattended scheduler. Automatic supervision runs inside explicit authority and finite allowances, then stops.
What does not exist
All true today. Stated so nobody plans around it.
| Capability | Status |
|---|---|
| Single sign-on | Not implemented |
| Team administration, seats, roles | Not implemented |
| Shared or cloud-hosted records | Not implemented |
| Audit export | Not implemented Studio report export arrives in the full workflow version, per machine |
| macOS and Linux | Not implemented |
| Licensing beyond Studio's three machines | Not implemented |
Teams waitlist
Two questions and an email.
The answers decide whether team features are built and what shape they take. You will hear once, when there is a decision.
Draft: waitlist endpoint not wired yet