UI Consistency

The workflow selector SHALL display all authorized workflows returned from the backend discovery endpoint. The menu SHALL include built-in options for automatic selection and disabling workflow routing.

The application SHALL support light and dark themes with a user-accessible toggle. Theme preference SHALL be persisted across sessions. The default theme SHALL be light.

The sidebar logo and alt text SHALL be determined by the deployment hostname, not hardcoded. White-label deployments SHALL display their own branding instead of the default logo. Unknown hostnames SHALL fall back to default branding. Adding a new white-label brand SHALL require only a configuration entry and a logo asset, not component changes.

Chat conversations, messages, and the active conversation SHALL be persisted with backend synchronization when chat persistence is enabled, falling back to local cache for fast startup. The backend SHALL be the source of truth on startup for persistence-enabled domains. Messages SHALL be limited per conversation to prevent storage overflow. Transient state such as processing indicators SHALL NOT be persisted, and processing status SHALL reset on restore to prevent stuck states.

The application SHALL present a confirmation dialog before executing destructive or significant actions. The dialog SHALL support customizable title, message, and button text. The dialog SHALL close on backdrop click and Escape key.

The chat interface SHALL provide modals for attaching context such as contracts, deals, and property profiles to conversations. Each modal SHALL fetch and display available items from the backend. Selecting an item SHALL add it to pending attachments for the current message.

The contract analysis view SHALL provide a detail view for viewing paragraph citations in context. The view SHALL display the full paragraph text from the contract and highlight the cited section where applicable.

The Suggested Edits column in the review workbench SHALL display an animated loading indicator while edits are being generated. The static placeholder SHALL only appear when processing is complete with no suggested edit. The loading indicator SHALL communicate active processing to reduce user uncertainty.

The sidebar SHALL support tenant-based configuration for section labels and visibility so tenant deployments can hide or rename navigation sections.

The workflow selector SHALL filter available workflows based on tenant configuration. Tenant priority settings SHALL influence workflow display order.

Contract analysis actions that trigger long-running backend work SHALL show visible loading feedback and disable repeat actions while pending. Actions include sync, import, add column, delete column, delete contract, and regeneration. Loading feedback SHALL clear on both success and error.

Playbook upload interactions SHALL display a visible loading indicator while the upload request or subsequent list refresh is in progress. Loading feedback SHALL clear on both success and error.

The contract analysis feature SHALL provide a button that allows users to create an empty grid by entering a name. After successful creation, the view SHALL navigate into the newly created grid. If the user cancels or enters an empty name, no grid SHALL be created.

When a user imports a shared folder in the contract analysis view, the system SHALL auto-create a grid from the folder contents. The system SHALL auto-detect the cloud storage provider from the URL. After a successful folder sync, the grid list SHALL be refreshed.

Chat context attachments SHALL remain visible and active across follow-up messages until the user explicitly removes them.

User messages that include uploaded files SHALL display an attachment summary in the chat history. Messages without attachments SHALL omit the summary.

Assistant messages with output attachments SHALL provide working download links. Download links SHALL use token-based authentication for secure file retrieval.

When review edits are applied, the workbench SHALL immediately reflect applied status so users can navigate edits and download revised documents. Applied rows SHALL display applied-state indicators instead of action buttons. When all edits are resolved, batch-apply actions SHALL be disabled. After one or more edits are applied, the download revised action SHALL be enabled.

When a user edits the recommended response, the response cell SHALL display the edited text with an explicit "(edited)" indicator. The edited text SHALL reflect the user-provided content, not the pre-edit suggestion.

When a user edits the recommended response and then applies the edit, the edit genealogy SHALL display provenance indicating the response was user-edited. The provenance label SHALL appear alongside other source metadata.

Edit genealogy SHALL render consistently regardless of whether edits are applied individually or in batch. The user SHALL NOT experience missing genealogy details when applying a single row versus batch apply.