How fieldmid is built

PowerSync

Core requirement

Sync engine that bridges SQLite on every client with PostgreSQL in the cloud.

• 9 Sync Streams scoped by role — workers see their own incidents, supervisors see their site, admins see everything, and edge devices receive a parameterized critical feed.
• Mobile app writes incidents to local OP-SQLite; PowerSync reconciles them with Supabase Postgres when connectivity returns.
• Rust edge daemon uses the PowerSync Rust SDK (pre-alpha) to sync a read-only SQLite on rugged Linux devices with a TUI dashboard.
• The web dashboard can subscribe to PowerSync for optional real-time reads alongside Supabase Realtime.

Supabase

Best Submission Using Supabase

PostgreSQL backend with Auth, Edge Functions, Realtime subscriptions, and Row Level Security.

• 10 SQL migrations define the full schema: organizations, sites, workers, incidents, escalations, compliance rules, audit reports, notifications, push tokens, and CLI auth sessions.
• 5 Edge Functions handle signup gating, admin role management, PowerSync write ingestion (with Mastra triage), push notifications, and CLI browser-based auth.
• Supabase Auth manages email/password and OAuth (Google, GitHub) across web and mobile.
• Row Level Security enforces per-org, per-role data isolation throughout.

Mastra

Best Submission Using Mastra

AI agent framework powering incident triage, escalation workflows, compliance audits, and shift summaries.

• Triage Agent classifies incidents by severity (LOW through CRITICAL) with risk scoring, critical keyword detection, and tag extraction.
• Escalation Workflow is a two-step orchestration: prepare an escalation message, then conditionally dispatch to supervisors via email, Slack, or push.
• Compliance Agent audits incidents against organization rules and generates flagged-pattern reports.
• Summary Agent produces end-of-shift reports with incident counts, resolution rates, and management-ready narratives.