GUIDE
How DWERK Works
DWERK operates as three distinct layers. Each layer has a clear role. Together they form a system where physical work is captured, stored, and made visible — without ambiguity.
Three layers
Mobile app — proof capture layer
Staff check in, record tasks, and upload evidence using the DWERK mobile app. Each action creates an immutable event — GPS coordinates, timestamp, photo, and device identity are captured at the moment of work. The app works offline. Evidence is stored locally and syncs when connectivity is restored.
Backend — canonical truth layer
All events are append-only. Nothing is overwritten or deleted through the application. The backend is the source of truth. Every operational question — who was present, when they arrived, what evidence exists — is answered from this layer.
Console — projection and control layer
Managers and admins see derived views from the truth layer. Attendance summaries, exception feeds, coverage reports, and continuity dashboards are all projections — computed from source events, never stored independently. The console controls configuration but never modifies the operational record.
Why this matters
When a dispute arises — billing, coverage, incident — the operational record is the answer. Not memory. Not a spreadsheet. Not a supervisor's word. The record. Because it is append-only and evidence-linked, it can be reviewed by any authorized party and trusted as a faithful account of what actually happened.