Clusters
How decisions are organized into a hierarchical tree.
Clusters group related decisions. They map to areas of your codebase, team conventions, or any structure that makes sense for your organization.
Structure
Clusters are hierarchical, using dot notation:
auth
auth.tokens
auth.sessions
payments
payments.webhooks
infra
infra.deployRequesting context for auth returns decisions from auth, auth.tokens, and auth.sessions. This lets AI tools pull in broad or narrow context depending on the task.
Naming patterns
There's no required naming convention. Some common patterns:
| Pattern | Examples |
|---|---|
| By domain | auth, payments, notifications |
| By layer | api, database, infra |
| By service | user-service, billing-service |
| By concern | testing, logging, error-handling |
Creating clusters
Clusters are created in the CLI under Decisions. You can create top-level clusters or nest them under existing ones.
When using GitHub integration, Lithium creates clusters automatically based on the content of merged pull requests.