# ADR-0001: Record architecture decisions

- **Status:** Accepted
- **Date:** 2026-07-30

## Context

Flying Jib combines Minecraft server embedding, Holepunch P2P, Electron, and mesh federation. Without a durable decision log, agents and humans will re-litigate stack choices and silently diverge from mesh-native constraints.

## Decision

Use Architecture Decision Records in `agent/ADRs/`:

- Sequential numbering (`0001`, `0002`, …)
- Template at `0000-template.md`
- Required before architecture, protocol, process-model, or security-model changes land
- Status: Proposed → Accepted (or Deprecated/Superseded)

## Consequences

### Positive

- Traceable “why” for every major choice
- Onboarding and AI agents share the same decision surface

### Negative / tradeoffs

- Small process overhead per change

### Follow-ups

- [x] Template and first ADRs for Phase 0
- [ ] Keep index via directory listing / ROADMAP links