decision-watcher

When to invoke

Only when the project has a .harness/ folder (otherwise stay silent — this is not a bencium-loop project).

Trigger when the current conversation involves any of:

• Library/framework choice: "should we use X or Y?", "let's go with Z"
• Data model decisions: schema design, field naming conventions, normalization choices
• Architecture splits: monolith vs services, sync vs async, client vs server rendering
• Policy choices: auth model, caching strategy, error handling approach, naming conventions
• Tradeoffs: explicit "X over Y because Z" statements from the user or you

Do NOT trigger on:

• Implementation details that are obvious from the code (variable names, file layout)
• Choices already documented in .harness/archive/ (check first via context-loader)
• Trivial decisions that have no downstream consequences (e.g., "let's use 2-space indent")