# Documentation index

## Reading order

1. [Product specification](product-specification.md)
2. [Architecture](architecture.md)
3. [Security and privacy](security.md)
4. [Data model](data-model.md)
5. [Synchronization and integrations](synchronization.md)
6. [Media and measurements](media-and-measurements.md)
7. [Deployment and operations](deployment.md)
8. [API contract](api.md)
9. [Development plan](development-plan.md)

## Architecture decisions

- [ADR-001: Go application facade with private PocketBase](adr/ADR-001-private-pocketbase.md)
- [ADR-002: Application encryption and key lifecycle](adr/ADR-002-encryption.md)
- [ADR-003: Offline-first synchronization](adr/ADR-003-offline-sync.md)

## Authority

When documents overlap, the more specific document governs. Security invariants always take precedence over implementation convenience. A later explicit product decision should be recorded by changing the relevant document and, when architectural, adding or superseding an ADR.