# ADR 001 — Browser-First User Interface

**Status:** Accepted

## Decision

The primary user interface will be browser-based.

## Context

The application must support persistent interactive storytelling, campaign management, branch/checkpoint navigation, state inspection, imported knowledge management, and future images/video. These requirements are substantially better suited to a graphical browser interface than a terminal-only interface.

## Alternatives Considered

- terminal-only UI,
- Open WebUI as the primary product UI,
- native desktop application,
- browser-based application.

## Reason

A browser interface provides the best path for:

- transcript interaction,
- story-tree visualization,
- state/library panels,
- streaming text,
- local deployment,
- future generated graphics/video,
- cross-platform use without separate native clients.

## Consequences

- terminal-first candidate projects will require a browser layer if selected,
- runtime browser dependencies must remain local/offline-capable,
- remote CDN assets should not be required in production.