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

Architecture Decision Records

Significant architectural decisions made during development

Danvas maintains Architecture Decision Records (ADRs) for durable architecture and product-domain decisions. ADRs live in the repository with the code so implementation changes and decision changes can be reviewed together.

Documentation tiers

TierLocationPurpose
Tier 1 — ADRsdocs/adr/Architecture, domain, security, tenancy, integration, data-sync, and package-boundary decisions.
Tier 2 — Engineering standardsdocs/engineering/standards/React/Next conventions, form UX standards, tooling usage, and repeatable implementation guidance.
Tier 3 — Feature specs / implementation notesdocs/features/, docs/engineering/implementation-notes/, docs/runbooks/Feature behavior, runbooks, current implementation notes, and narrow optimization history.

Active ADR index

The canonical index is maintained in docs/adr/README.md.

That index includes the full active Tier 1 list, superseded records, and moved records. The most frequently referenced active domains are:

DomainKey ADRs
Auth, tenancy, permissionsADR-0003, ADR-0004, ADR-0018, ADR-0024
Database, schema, auditADR-0001, ADR-0033, ADR-0035, ADR-0047
Server actions and API boundariesADR-0015, ADR-0019, ADR-0025, ADR-0032, ADR-0081
Package boundariesADR-0026, ADR-0039, ADR-0081
Data fetchingADR-0005, ADR-0041, ADR-0051
Compliance and service dayADR-0054, ADR-0070, ADR-0071, ADR-0077, ADR-0080
Lineup and daypart readinessADR-0071, ADR-0072, ADR-0073, ADR-0074
Data sync and integrationsADR-0017, ADR-0020, ADR-0053, ADR-0057, ADR-0058, ADR-0062, ADR-0063, ADR-0064, ADR-0068, ADR-0069, ADR-0078, ADR-0079, ADR-0108
Coupons and versioned NPSADR-0091, ADR-0096
Operations workflowADR-0055, ADR-0056, ADR-0075, ADR-0076
Tooling, vendor, infraADR-0002, ADR-0012, ADR-0013, ADR-0042, ADR-0043, ADR-0044, ADR-0045, ADR-0065, ADR-0067

Coupon runtime details live in Coupons and Guest NPS and its canonical feature contract. The 2026-10-07 release receipt records the completed reliability migration/deployments. It does not supersede ADR-0091/0096 admission, privacy, retry, or pilot decisions.

Moved out of ADRs

Several low-confidence ADRs were intentionally moved to more appropriate documentation tiers:

Former ADRNew location
ADR-0029 and ADR-0030docs/features/guest-coupon-experience.md
ADR-0031docs/engineering/standards/form-submission-ux.md
ADR-0037, ADR-0040, ADR-0049, ADR-0050docs/engineering/standards/react-and-next-patterns.md
ADR-0066docs/engineering/implementation-notes/role-map-query-caching.md

The original ADR files remain as moved/superseded stubs so historical links still resolve. In particular, ADR-0027 and ADR-0048 are historical references; use the accepted replacement ADRs in the active routing table above.

ADR format

New ADRs should include context, decision, considered options, consequences, and compliance/review guidance. Do not create a new ADR for a coding-style preference, one-off config migration, feature screen spec, or narrow performance note.

Data Flow

How data moves through Danvas

Core Domain

Technical architecture and data models for Danvas domains

On this page

Documentation tiersActive ADR indexMoved out of ADRsADR format