mirror of
https://github.com/basicmachines-co/basic-memory
synced 2026-06-21 13:47:35 +00:00
5458c35b35
Signed-off-by: phernandez <paul@basicmachines.co> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.7 KiB
1.7 KiB
title, type, entity, version, schema, settings
| title | type | entity | version | schema | settings | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Decision | schema | Decision | 1 |
|
|
Decision
A DecisionNote is a durable record of a real choice — one with alternatives
and a rationale, not a passing preference. The Basic Memory plugin's output-style
prompts Claude to capture these inline as decisions are made, and the future
/basic-memory:bm-decide command captures them explicitly.
Decisions are found by structured recall:
search_notes(metadata_filters={"type": "decision", "status": "open"}).
What makes a good DecisionNote
- decision — state the choice plainly.
- rationale + alternative — why this, and what was rejected. This is the part that saves a future session from relitigating the same ground.
- consequence — what the choice commits the work to.
- affects / supersedes — relations that wire the decision into the graph.
Frontmatter
type: decision plus status make decisions queryable. Capture decisions
sparingly — one note per genuine decision, not per opinion. Validation is warn,
never blocking.