Architecture Decision Record Template

# [NNNN] [Decision in active voice]

Date: [YYYY-MM-DD]
Status: Proposed | Accepted | Rejected | Deprecated | Superseded by [link]

## Context
[The forces, constraints, and problem that make a decision necessary.]

## Decision drivers
- [Quality, constraint, or requirement that changes the choice]

## Considered options
1. [Option]
2. [Option]

## Decision
We will [specific choice].

## Consequences
- [Positive or enabling consequence]
- [Cost, limitation, or new responsibility]

## Confirmation
[How implementation or operation will prove the decision is being followed.]

# 0012 Store job leases in the database

Status: Accepted

## Context
Two workers can claim the same queued job after a process restart. In-memory locks do not survive or coordinate across processes.

## Decision
We will acquire a time-bounded lease with one conditional database update before work begins.

## Consequences
- Workers can recover abandoned jobs after the lease expires.
- Lease duration and renewal become operational settings that require monitoring.

## Confirmation
An integration test starts two workers against one database and proves only one performs the job.