Danvas
Danvas
DashboardSupportWelcome

👤 USER DOCS

User Guides

Getting Started

Getting StartedDashboard & OnboardingApp Settings

Tutorials

Tutorial: Setting Up Shift Tasks & ClosersTutorial: Managing Incidents in the InboxTutorial: Tracking Compliance & Sync StatusTutorial: Operational Workflows with the AI AssistantTutorial: Building & Deploying Custom Checklists

Daily Operations (Staff)

Shift Workspace & TasksService Day SetupDaily Line-UpStaff Service Day ReportsForms

Communication & Chat

Messages & AnnouncementsUnified Operations InboxAI Assistant

Manager & Admin Guides

Daily Line-Up SetupStaff SchedulingManaging LocationsNPS and Guest FeedbackCouponsContacts and Guest HistoryManager CloseoutsDaily Line-Up & ComplianceAnalyticsIncident ReportingWhistleblower Concerns & FeedbackAdmin Tools

⚙️ DEVELOPER DOCS

Getting Started

Getting StartedDevelopmentDeployment Guide

Architecture

Architecture OverviewExplanation: AI Integration & Tenant SecurityExplanation: Dynamic Forms Engine DesignExplanation: Compliance Ledger DesignExplanation: Live Sync & Data FreshnessData FlowArchitecture Decision Records

Core Domain

Core DomainDatabase ReferenceLocations DomainAuth & RBACScheduling DomainReports DomainIncidents DomainUnified Operations InboxLive Sync Data FreshnessToast Sync PipelineNotifications DomainCoupons and Guest NPSAudit Log & Compliance ArchitectureDesign Audit FindingsAI Chat IntegrationAnalytics & Tips Integration

Frontend

Frontend ArchitectureFormsLoading SkeletonsComponentsPWA & Offline ShellScreenshots

API Reference

API Reference

Endpoints

POS Sales APIOptimization Data APISchedule Shifts APIEmployee Export APIReports APIIncidents APIAI Chat APIPush Notifications APIWebhooks APICron API

Contributing

ContributingCode Examples

Security

Security & Compliance

Release Notes

What's New

Unified Operations Inbox

Technical architecture of the Master-Detail operations inbox and messaging feed

The Operations Inbox v2 (governed by ADR-0075) serves as the unified operational command feed for restaurant managers and staff. It consolidates incidents, announcements, staff messages, and workflow notifications into a single triaged inbox.


Architectural Overview

The inbox is located at /inbox and is designed around a responsive Master-Detail layout with structured triage states:

Primary Views

  1. Attention: Urgent, unassigned, or aging items requiring immediate manager action.
  2. Mine: Items claimed by or explicitly assigned to the signed-in user.
  3. Active: All open, in-progress, or escalated operational items across the team.
  4. History: Completed, closed, or dismissed items with full audit history.

Canonical Lifecycle State Machine

All operational items progress through deterministic lifecycle states with optimistic concurrency control (revision checks):

stateDiagram-v2
    [*] --> unclaimed: Created
    unclaimed --> in_progress: Claim / Assign
    in_progress --> waiting: Awaiting Vendor / Info
    waiting --> in_progress: Update Received
    in_progress --> completed: Resolve / Sign-off
    unclaimed --> dismissed: Dismiss Noise
    in_progress --> dismissed: Dismiss
    completed --> [*]
    dismissed --> [*]

State Transitions & Ownership

  • Claiming: Sets ownerId to the current user and moves state to in_progress.
  • Unclaiming: Releases item back to unclaimed state for team pickup.
  • Escalation: Bumps urgency tier (low → medium → high → critical) and alerts managers via Slack.
  • Resolution: Requires resolution notes and logs an immutable audit event.

Keyboard Navigation & Shortcuts

To maximize manager speed during busy service shifts:

  • J / K or ↓ / ↑ — Navigate feed items
  • C — Claim selected item
  • U — Unclaim selected item
  • E — Escalate urgency
  • R — Focus reply / response input
  • Esc — Deselect / close detail drawer

Mobile Experience

On viewports < 768px, the inbox collapses into a high-density list with 48px touch targets. Selecting an item opens a slide-over sheet preserving full thread history and action buttons without losing feed context.

Incidents Domain

Technical lifecycle, ownership, and audit trail of operational incidents

Live Sync Data Freshness

Technical architecture of the data freshness engine and sync status monitoring

On this page

Architectural OverviewPrimary ViewsCanonical Lifecycle State MachineState Transitions & OwnershipKeyboard Navigation & ShortcutsMobile Experience