# Project — website
> The "why". Rarely changes.
## What
Read-only web UI for the devist worker's `worker_events` log. Lives
inside the main devist repo at `website/`, ships with the same release
cadence.
## Why
The Rust worker collects file events and AI-generated advice into
SQLite locally + Supabase remotely. CLI access (`devist worker watch`,
`devist worker advice`) is fine for one machine but breaks down for:
- multi-device review (laptop pushes events, you triage from desktop)
- async review (advice queue you can come back to)
- visual scan of trends (which projects get the most warns?)
A web UI gives all of that for free, since the data is already in
Supabase.
## Constraints
- **Read-mostly.** The only client write is `acked_at` (column-level
GRANT enforced server-side).
- **Single repo.** Ships inside devist, not a sibling project.
- **Single user / single tenant** for now. Multi-tenant lives in a
future migration if it becomes a need.
## Non-goals
- Editing worker config from the UI (CLI-only).
- Triggering `claude` runs from the UI.
- Replacing the CLI for power users — the CLI stays canonical.
## Stakeholders
- Owner: WebchemistCorp
- Reviewers: same