Architecture Decision Records

Architecture Decision Records (ADRs) document significant design decisions in SlicerMouseMaster.

ADR Index

ADR	Title	Status
ADR-001: Event Interception Strategy	Event Interception Strategy	Accepted
ADR-002: Preset File Format	Preset File Format	Accepted
ADR-003: Button Detection Mechanism	Button Detection Mechanism	Accepted
ADR-004: Platform Differences	Platform Differences	Accepted
ADR-005: Persistence Strategy	Persistence Strategy	Accepted
ADR-006: UI Framework Choices	UI Framework Choices	Accepted
ADR-007: Preset Sharing Mechanism	Preset Sharing Mechanism	Accepted
ADR-008: Testing Strategy	Testing Strategy	Accepted
ADR-009: Slicer Action Mapping	Slicer Action Mapping	Accepted
ADR-010: Context-Sensitive Bindings	Context-Sensitive Bindings	Accepted
ADR-011: Documentation Infrastructure	Documentation Infrastructure	Accepted
ADR-012: Living Documentation	Living Documentation	Accepted

What is an ADR?

An Architecture Decision Record captures a significant architectural decision along with its context and consequences.

Each ADR includes:

• Title: Brief description of the decision

• Status: Proposed, Accepted, Deprecated, or Superseded

• Context: The situation that led to this decision

• Decision: What we decided to do

• Consequences: The results of this decision

Creating a New ADR

1. Copy the template from docs/adr/README.md

2. Name it ADR-XXX-short-title.md where XXX is the next number

3. Fill in all sections

4. Submit for review via pull request

5. Add to this index once accepted