undefined

**Examples:**
```nix

```typescript
// Parsing date strings manually because date-fns adds 70KB
// Alternative: date-fns (rejected: bundle size for 3 date operations)
const parseDate = (str: string): Date => { ... };

undefined

undefined

todos_oneshot(
  title: "ADR: [Decision Title]",
  description: "**Date**: YYYY-MM-DD | **Status**: Accepted\n**Context**: [1-2 sentences]\n**Decision**: [What was chosen]\n**Rationale**: [Why]\n**Alternatives Rejected**: [What wasn't chosen and why]",
  tags: "decision",
  type: "task"
)

todos_oneshot(
  title: "ADR: Use Zustand for Client State Management",
  description: "**Date**: 2024-01-15 | **Status**: Accepted\n**Context**: Need lightweight state management for React app without Redux boilerplate.\n**Decision**: Use Zustand with immer middleware.\n**Rationale**: Minimal API, TypeScript-first, no providers, works with React concurrent features.\n**Alternatives Rejected**: Redux Toolkit (too heavy), Jotai (atom model less intuitive for team), Context (prop drilling at scale).",
  tags: "decision",
  type: "task"
)

undefined

**Compact form for simple decisions:**

undefined

**Date**: YYYY-MM-DD | **Status**: [Proposed|Accepted|Deprecated|Superseded by <ticket-id>]
**Context**: [The situation requiring a decision, 1-2 sentences]
**Decision**: [What was decided, in active voice: "Use X for Y"]
**Rationale**: [Why this option was chosen, primary reasons]
**Alternatives Rejected**:
- [Option A]: [Why rejected]
- [Option B]: [Why rejected]
**Consequences**: [Expected outcomes, both positive and negative]

undefined

undefined

**In the context of** [situation/requirement],
**facing** [concern/quality attribute],
**we decided** [decision outcome]
**and neglected** [alternatives],
**to achieve** [benefits],
**accepting that** [trade-offs/consequences].

**In the context of** user session management,
**facing** the need for horizontal scalability,
**we decided** to use Redis for session storage
**and neglected** in-memory sessions and database sessions,
**to achieve** stateless application servers and sub-millisecond session lookups,
**accepting that** we add operational complexity and a failure dependency.

Is this a local, easily-reversible choice?
├─ YES → Tier 1 (Inline comment)
└─ NO
   └─ Does this affect multiple files or modules?
      ├─ YES → Is this architecturally significant or hard to reverse?
      │        ├─ YES → Tier 3 (Full ADR)
      │        └─ NO → Tier 2 (Brief ADR in DECISIONS.md)
      └─ NO → Tier 1 (Inline comment)

// See decision ticket for state management decision
import { useStore } from './store';

undefined

undefined

Missing decision documentation:
- Line 45: Why PostgreSQL instead of existing MongoDB?
  → Needs ADR or brief explanation
- Line 123: Why custom retry logic vs axios-retry?
  → Needs inline comment with rationale

undefined

undefined

undefined

undefined

undefined

undefined

undefined

*Fix: Explain WHY it's best and compared to WHAT*

**Missing Alternatives:**

*Fix: List what else was considered and why rejected*

**Pure Description:**

*Fix: Explain why this sorting approach over alternatives*

**Retroactive Rationalization:**
Writing ADRs after the fact to justify decisions already made without genuine consideration.
*Fix: Document during decision-making, not after*

┌─────────────────────────────────────────────────────────────────┐
│                    THE ARCHIVIST QUICK REFERENCE                │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  BEFORE WRITING CODE, ASK:                                      │
│  • Would another engineer question this choice?                 │
│  • Are there reasonable alternatives?                           │
│  • Will forgetting this cause problems?                         │
│                                                                 │
│  DOCUMENTATION TIERS:                                           │
│  ┌─────────┬──────────────────┬─────────────────────────────┐  │
│  │ Tier 1  │ Inline comment   │ Local, reversible choices   │  │
│  │ Tier 2  │ DECISIONS.md     │ Multi-file, moderate impact │  │
│  │ Tier 3  │ Full ADR         │ Architectural, hard to undo │  │
│  └─────────┴──────────────────┴─────────────────────────────┘  │
│                                                                 │
│  MINIMUM VIABLE DECISION COMMENT:                               │
│  # Uses [X] because [reason] (vs [Y]: [why not])                │
│                                                                 │
│  MINIMUM VIABLE ADR ENTRY:                                      │
│  ## [NNNN] Title                                                │
│  **Date**: | **Status**: Accepted                               │
│  **Decision**: [What]                                           │
│  **Rationale**: [Why]                                           │
│  **Alternatives Rejected**: [What wasn't chosen]                │
│                                                                 │
│  DOCUMENT BEFORE IMPLEMENTING - NOT AFTER                       │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

// Job queue implementation: see decision ticket
import Queue from 'bull';