# 03-Decisions — Schema

This folder holds significant decisions that span multiple projects or represent major directional choices. For project-specific decisions, use `01-Projects/[name]/decisions.md` instead.

## When to use 03-Decisions/ (vs project decisions.md)

Use this folder for:
- Technology or tool choices that apply across everything you do
- Business or life decisions you want a permanent record of
- Choices you'd want to audit in 12 months and understand the reasoning

Use the project's own `decisions.md` for:
- Architecture decisions specific to one project
- Scope or feature choices within a project
- Client-specific calls

## File naming

`YYYY-MM-DD-kebab-topic.md`

Examples:
- `2026-01-15-switched-to-tailwind-across-all-projects.md`
- `2026-03-01-dropped-typescript-for-personal-projects.md`

## File format

```
---
type: decision
date: YYYY-MM-DD
status: active | superseded | archived
tags: [keyword]
---

# [Decision title]

## Decision
[What was decided, clearly stated.]

## Context
[Why this decision came up. What prompted it.]

## Reasoning
[Why this option over the alternatives. What was weighed.]

## Alternatives considered
- [Alternative 1] — rejected because [reason]
- [Alternative 2] — rejected because [reason]

## Trade-offs accepted
[What you're giving up or accepting by making this choice.]

## Revisit condition
[What would cause you to reconsider? Or: "No planned revisit — treat as stable."]
```