Decisions
The rules and conventions your AI tools follow.
A decision is a rule, convention, or architectural choice your team has agreed on. Decisions are what your AI tools read before writing code.
Anatomy of a decision
Each decision has:
| Field | Description |
|---|---|
| Title | Short summary of the decision |
| Content | Full reasoning and constraints |
| Version | Increments when the decision is updated |
| Cluster | Where it belongs in your tree |
Examples
| Cluster | Title | Content |
|---|---|---|
auth.tokens | Single-use refresh tokens | Refresh tokens are single-use. Store in httpOnly cookies. Rotate on every use. |
infra.deploy | CI-only deployments | All deployments go through CI. Never deploy from local machines. |
api.errors | Structured error responses | Return structured error responses with a code, message, and optional details field. |
Versioning
Decisions are versioned. When you update a decision, a new version is created. The previous version is preserved.
This means your AI tools always get the latest version, and you can see what changed over time.
Creating decisions
Decisions are created in two ways:
- Manually in the CLI under Decisions. Select a cluster and add a decision.
- Automatically via GitHub integration. Extracted from merged pull requests.