# Decision Log

Structured, append-only decision records for `tegwick-control`.

## Purpose

Decisions that affect activation levels, commitments, governance, or landscape
priority belong here — not only as inbox notes or task bullets.

## Layout

```text
decisions/
├── README.md                    this file
├── DEC-NNN-<slug>.md            individual decision records
└── archive/                     superseded records (optional)
```

## Naming

```text
DEC-NNN-<slug>.md
```

- `NNN` — three-digit sequence (`001`, `002`, …)
- `slug` — short kebab-case topic (`activation-levels`, `root-control-repo`)

## Registry

`DECISIONS.md` at the repo root is the **index**: open decisions, resolved
decisions, and pointers to full records in this folder.

When creating a new decision:

1. Allocate the next `DEC-NNN` id from `DECISIONS.md`.
2. Copy `templates/decision-record.md` into `decisions/DEC-NNN-<slug>.md`.
3. Add a summary entry to `DECISIONS.md` under Open or Resolved.

## Status values

| Status | Meaning |
|---|---|
| Open | Under consideration; no choice yet |
| Accepted | Decision made and in effect |
| Rejected | Option explicitly declined |
| Superseded | Replaced by a later decision |

Update both the record file and `DECISIONS.md` when status changes.

## Intake path

```text
inbox/ or area card → triage → decisions/DEC-NNN-<slug>.md → DECISIONS.md index
```

Agents may draft decision records but must not mark `Accepted` without human
approval per `AGENT_RULES.md`.