# AquaArchive Design Brief Document (DBD)
**Version:** 1.0 Draft | **Date:** 2026-10-28

## 1. Design objective
Create a calm, precise, trustworthy field tool for archaeological documentation. Prioritize evidence integrity and field usability over decorative complexity.

## 2. Principles
- Mobile-first, touch-friendly, readable in sunlight and low light.
- Make offline, pending, syncing, synced, and failed states explicit.
- Keep exact coordinates restricted by role.
- Preserve drafts through interruptions and explain destructive actions.
- Distinguish temporary field tag, client UUID, permanent artifact code, original photo, derivative, draft report, and official report.
- Meet accessibility expectations and do not use color alone to convey status.

## 3. Visual direction
Suggested tone: scientific, maritime, restrained, contemporary. Suggested palette: deep navy, ocean blue/teal, neutral slate; limited amber/red for warnings. Use legible sans-serif type and tabular numerals for identifiers and measurements. These are recommendations, not an approved brand system; confirm logo, palette, fonts, and design tokens with the owner.

## 4. Primary screens
### Project dashboard
Current project, general site zone, recent records, pending sync count, last sync, storage warnings. No exact coordinates in general dashboard.

### Artifact list
Search by permitted permanent code, temporary tag, and descriptive metadata. Filters by project, zone, date, and status. Include loading, empty, offline, and error states.

### Artifact capture
Group fields into Identification, Description, Context, Photos, and Review. Show identifiers distinctly. Include Save Draft and Sync actions with truthful results and inline validation.

### Photo evidence
Show view category, byte size, checksum status, upload status, and original/derivative label. No ordinary overwrite control for original evidence.

### Sync queue
Show pending records/photos, last error, retry action, and status. Local save must not be described as server backup.

### Reports
Select type/date range, show draft/official status, source period, project, generation status, and access restrictions.

### Restricted site details
Keep exact coordinates out of standard cards. Gate access by role and avoid caching restricted values.

## 5. Reusable component candidates
`StatusPill`, `OfflineBanner`, `SyncQueueItem`, `ArtifactIdentityBlock`, `PhotoEvidenceCard`, `ChecksumStatus`, `FieldInput`, `ConfirmActionDialog`, `EmptyState`, `LoadingState`, `ErrorState`, `RoleRestrictedNotice`. Check existing components before creating duplicates.

## 6. Interaction/content rules
Use clear labels such as “Save draft”, “Retry upload”, “Synced”, and “Needs attention”. Explain errors and next steps without exposing raw SQL or secrets. Do not display success while a request is pending. Keep technical IDs copyable. Distinguish local save from server acknowledgment.

## 7. Responsive and accessibility
Mobile: single-column forms and safe sticky actions. Tablet: two-column layouts where readable. Desktop: tables and side-by-side details. Provide keyboard navigation, visible focus, semantic labels, associated validation errors, sufficient contrast, screen-reader announcements, reduced-motion support, and zoom testing.

## 8. Acceptance criteria
- A field user can create and save a draft offline.
- All three identifiers are distinguishable.
- Sync failure is recoverable and understandable.
- Original evidence is distinct from previews.
- Exact coordinates are absent from standard screens and caches.
- Draft and official reports cannot be confused.
- Critical actions do not depend on color or hover.

## 9. Owner decisions
Final brand assets; bilingual glossary; supported devices/browsers; role-based screen visibility; coordinate reveal controls; approved wireframes and usability test.