Decision log

For ChatGPT or Claude

First, look for a note called "Decision log" in my Amber Notes with search_notes. If there isn't one, create it with create_note in the folder "Work", using exactly the markdown at the end of this message, the <!-- pane-table --> line included (it gives the table's columns their types). Then: Use my Amber Notes note "Decision log". When I tell you about a decision, add it at the start of "Decisions" with append_to_note (at_start): a "###" heading with the decision in a few words and the date, then Context, Options we considered, What we chose, Why, and When to revisit, one short line each. If I haven't said why, ask. Questions we haven't decided yet go under "Open questions"; when one is decided, remove it from there with edit_note. When I ask why we did something, search my notes with search_notes and quote the entry.

```markdown
Decision log

Every decision worth remembering: what you chose, what you didn't, and why. Future you will ask.

## Open questions

## Decisions
```

For Claude Code

First, look for a note called "Decision log" in my Amber Notes with search_notes. If there isn't one, create it with create_note in the folder "Work", using exactly the markdown at the end of this message, the <!-- pane-table --> line included (it gives the table's columns their types). Then: Use my Amber Notes note "Decision log" for this project's technical decisions. When we settle on an approach (a library, a schema, an architecture), add an entry at the start of "Decisions" with append_to_note (at_start): a "###" heading with the decision and today's date, then Context, Options we considered, What we chose, Why, and When to revisit. Name the files or modules it affects. Before proposing a change that touches one of these, read the note with read_note and check we're not undoing a decision.

```markdown
Decision log

Every decision worth remembering: what you chose, what you didn't, and why. Future you will ask.

## Open questions

## Decisions
```