Doc Structure

Arnold organizes documentation by feature, not by document type.

Feature-based organization

Instead of a single specification file or a collection of docs by type (PRD, tech spec, API docs), Arnold creates a folder per feature:

docs/
├── auth/
│   ├── auth-overview.md
│   ├── auth-flows.md
│   ├── auth-edge-cases.md
│   └── auth-criteria.md
├── booking/
│   ├── booking-overview.md
│   ├── booking-flows.md
│   └── booking-criteria.md
├── payments/
│   └── payments-overview.md
├── decisions/
│   ├── DEC-001-stripe-payments.md
│   └── DEC-002-no-overbooking.md
└── specification.md

Doc types within a feature

Why this structure?

Feature-based organization has three advantages:

1. Navigable - Find everything about a feature in one folder
2. Checkable - Arnold can compare each feature's docs to the corresponding code
3. Scalable - Add features without reorganizing existing docs