Project Status

Executive summary

This repository is an active NISC-specific Pareto Anywhere monorepo. The Nuxt application, Azure Functions API, database migrations, docs site, and Windows desktop gateway are current delivery targets. Legacy static-web-app frontend and root-level Functions artifacts remain in the repo for historical context only.

Delivery status by surface

Surface	Evidence in repo	Status
Web application	nuxt-frontend/pages, layouts, components/mobile/views	Active
API backend	static-web-app/api/src/functions/index.js + route modules	Active
Database	database/migrations/001 through 061	Active
Docs publishing	docs-site/.vitepress/config.ts, root docs:build	Active
Azure deployment	.github/workflows/azure-swa-nuxt.yml, deployments/main.bicep	Active
Desktop gateway	windows-desktop-gateway/, desktop workflow, MSI project	Active
Android packaging	nuxt-frontend/capacitor.config.ts, mobile-build.yml, APKs in releases/	Active but debug-oriented
iOS packaging	Capacitor scripts exist; workflow release text requires Xcode/manual signing	Present, manual
ESP32 BLE gateway	esp32-gateway/ PlatformIO + Azure IoT code	Supporting utility
Node BLE scanner	ble-scanner/scanner.js	Supporting utility
Legacy vanilla app	archived/static-web-app-frontend/	Archived
Legacy root Azure Functions	static-web-app/negotiateConnection, processIoTHubMessages, archived/api	Archived/legacy

Current feature posture

Strongly represented in code

• RTLS and floor-plan visualization
• Personnel and asset registries
• Emergency trigger, muster, contacts, notifications, and escalation
• Gateway health and diagnostics
• Weather, analytics, activity, ambient monitoring
• Desktop gateway onboarding and runtime management
• Phone badge onboarding, station, and enrollment flows

Transitional or incomplete areas

Area	Current state in code
Auth provider migration	Complete — Okta SSO active via nuxt-oidc-auth; Auth0 removed
PWA	Explicitly disabled in nuxt.config.ts because stale service workers caused deploy issues
Mobile distribution	Android workflow builds debug APKs; phone enrollment page shows disabled App Store / Google Play buttons
Docs maturity	Operator docs exist; this developer handbook fills the handoff gap

Platform status notes that matter during handoff

• Local ports differ by mode: direct Nuxt dev uses 3006, Docker exposes the frontend on 3005, and nginx exposes a combined origin on 8090.
• Docs are shipped with the app: VitePress output goes to nuxt-frontend/public/docs.
• Root validation is orchestration only: root npm run lint and npm run test delegate into subprojects and require those subproject dependencies to already be installed.
• Protected edit zones exist: .claude/LOCKS.md guards floorplan, admin personnel/gateways, CSS branding, and some ingestion files.

Pareto Anywhere references in the repo

Reference	Meaning
Root package name pareto-anywhere-azure	Upstream lineage and package identity
Root package homepage reelyactive.com/pareto/anywhere/integrations/azure/	External Pareto Anywhere reference embedded in repo metadata
BLE RTLS Positioning System.md	In-repo RTLS investigation and architecture reference
ble-scanner/	Utility that posts to the same Pareto ingestion path as physical gateways
docs-site/reference/beacon-payloads.md and iot-transport-profiles.md	Product/reference docs aligned to the Pareto-style telemetry pipeline

Recommended ownership split

• Frontend/UI: nuxt-frontend/
• Backend/API and integrations: static-web-app/api/
• Data model: database/
• Docs and handoff: docs-site/
• Windows gateway: windows-desktop-gateway/
• Hardware utilities: esp32-gateway/, ble-scanner/