add_decision
Record an architectural decision or tech choice linked to code symbols and files for context-aware memory. Decisions support temporal validity and can be invalidated when outdated.
Instructions
Manually record an architectural decision, tech choice, preference, or convention. Links to code symbols/files and optionally to a specific subproject for code-aware memory. Decisions have temporal validity — they can be invalidated later when they become outdated. Mutates the decision store (creates a new record). For automated extraction from session logs use mine_sessions instead. Returns JSON: { added: { id, title, type } }.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags for categorization (e.g., ["auth", "security"]) | |
| type | Yes | Decision type | |
| title | Yes | Short summary of the decision | |
| content | Yes | Full decision text — reasoning, context, tradeoffs | |
| file_path | Yes | File path this decision is about | |
| symbol_id | No | Symbol FQN this decision is about (e.g., "src/auth/provider.ts::AuthProvider#class") | |
| git_branch | No | Git branch this decision belongs to. Omit to auto-detect from the project root, or pass null to make the decision branch-agnostic (visible from every branch). | |
| service_name | No | Subproject name this decision is about (e.g., "auth-api", "user-service") |