UI Window Into Operations

Summary

The UI is a window into operational reality. It should show current state, evidence, decisions, and repair affordances rather than acting as a thin CRUD skin over tables.

Problem

CRUD pages make it easy to expose raw records and hard to explain operational meaning. Operators need queues, cases, artifact viewers, timelines, and actions.

Principle

Build UI around work to be understood and acted on, not around database table ownership.

Platform Shape

The web app has route groups for jobs, DAGs, geo analysis, marketing, payroll, POA, and precon. Those surfaces should read service-built projections and call API routes that adapt requests into domain services.

Source Evidence

• docs/reference/architecture.md
• app/web/app
• app/api
• services/workflow/read_models

Related Reading

• docs/engineering/concepts/review-queues.md
• docs/engineering/architecture/serving-snapshots.md