Circles & Governance
Understand the current organization model through circles, governance dashboards, roles, and tasks.
The organizational center of gravity in the live app is /circles, not the older /holacracy naming.
Current Route Model
| Route | Role |
|---|---|
/circles | organization center and circle navigation |
/circles/[circleId] | circle detail |
/governance | governance dashboard |
/governance/constitution | constitution view |
/governance/tensions | tension workflow |
/governance/proposals | proposal workflow |
/governance/meetings | meeting workflow |
/tasks | work/task surface |
/legal-entities | registry and entity context |
What Changed
Several older organizational routes now redirect:
/holacracy->/circles/holacracy/tasks->/tasks/governance/dao->/governance
That means current docs should explain governance through the circles + governance + tasks trio, not through older route names.
Circles
Use /circles and its detail routes to describe:
- circle structure
- members
- roles
- finance views by circle
- graph-linked organizational context
Governance
Use /governance to describe:
- tensions
- proposals
- meetings
- governance-health metrics
This page is a governance dashboard, not just a static concept page.
Tasks
/tasks is a first-class route and should be documented as part of the organization workflow, not as a side note.
Documentation Rule
When updating docs:
- prefer
/circlesover/holacracy - treat
/governanceas a dashboarded workflow surface - include
/tasksand/legal-entitiesin organization docs, not only in architecture docs
The app navigation config is the best source for live organizational IA. Historical Holacracy pages remain useful for concept and philosophy, but not for current route structure.