How srihariakula/apexarc2026 works
Von Digitalis Estates is an estate-operations platform for visitor analytics, animal monitoring, ticketing/loyalty, and AI oversight. Its clearest implemented workflow is popularity measurement: gateways or ticket scans submit events, the API stores them, scheduled rollups produce analytics, and staff review recommendations. Animal alerts and population counts follow a separate keeper-review path; visitor identity and ticketing support the customer-facing path. The graph combines sampled server code with README-documented capabilities; cloud MQTT, inference, and production OAuth details are architectural intentions rather than inspected integrations.
Main entry points: app.js Express API · db.js PostgreSQL · animal-monitoring/routes.js Animal monitoring · ingestion/routes.js Event ingestion
Components 18
Visitor experience
- Web interfaces
implementation/webapp - Tickets and loyalty
implementation/server/src/services/ticketing-integration/routes.js
Estate operations
- Event ingestion
implementation/server/src/services/ingestion/routes.js - Animal monitoring
implementation/server/src/services/animal-monitoring/routes.js - Alert tiering
implementation/server/src/services/animal-monitoring/alertTiering.js
Analytics and AI
- Popularity analytics
implementation/server/src/services/popularity-analytics/routes.js - Hourly and daily rollups
implementation/server/src/services/popularity-analytics/aggregation.js - Forecasts and recommendations
implementation/server/src/services/popularity-analytics/routes.js - AI governance
implementation/server/src/services/ai-governance/routes.js
Application platform
- Identity and access
implementation/server/src/services/identity-access/routes.js - Authentication middleware
implementation/server/src/middleware/auth.js - Express API
implementation/server/src/app.js - PostgreSQL
implementation/server/src/db.js
Other components
- Visitor
- Keeper and staff
- Sensors and gateways
- MQTT and cloud inference
- OAuth/OIDC provider
Connections 30
- Visitor → Web interfaces: uses
README.md - Keeper and staff → Web interfaces: uses
README.md - Web interfaces → Express API: requests APIs
implementation/server/src/app.js - Express API → Identity and access: mounts routes
implementation/server/src/app.js - Express API → Tickets and loyalty: mounts routes
implementation/server/src/app.js - Express API → Event ingestion: mounts routes
implementation/server/src/app.js - Express API → Popularity analytics: mounts routes
implementation/server/src/app.js - Express API → Animal monitoring: mounts routes
implementation/server/src/app.js - Express API → AI governance: mounts routes
implementation/server/src/app.js - Express API → Authentication middleware: attaches user
implementation/server/src/app.js - Identity and access → Authentication middleware: issues tokens
implementation/server/src/services/identity-access/routes.js - Authentication middleware → PostgreSQL: loads user and roles
implementation/server/src/middleware/auth.js - Identity and access → PostgreSQL: reads and writes accounts
implementation/server/src/services/identity-access/routes.js - Tickets and loyalty → PostgreSQL: stores ticket and loyalty data
implementation/server/src/services/ticketing-integration/routes.js - Event ingestion → PostgreSQL: stores incoming events
implementation/server/src/services/ingestion/routes.js - Sensors and gateways → Event ingestion: submits readings
implementation/server/src/services/ingestion/routes.js - Event ingestion → MQTT and cloud inference: stands in for MQTT path
implementation/server/src/services/ingestion/routes.js - Event ingestion → Hourly and daily rollups: events feed rollups
README.md - Popularity analytics → Hourly and daily rollups: calls rollups
implementation/server/src/services/popularity-analytics/routes.js - Hourly and daily rollups → PostgreSQL: reads and writes aggregates
implementation/server/src/services/popularity-analytics/aggregation.js - Popularity analytics → PostgreSQL: reads analytics; records approvals
implementation/server/src/services/popularity-analytics/routes.js - Keeper and staff → Forecasts and recommendations: reviews recommendations
README.md - Animal monitoring → Alert tiering: tiers alert severity
implementation/server/src/services/animal-monitoring/routes.js - Animal monitoring → PostgreSQL: stores alerts and counts
implementation/server/src/services/animal-monitoring/routes.js - Keeper and staff → Animal monitoring: confirms or reviews
README.md - MQTT and cloud inference → Animal monitoring: provides sensor signals
README.md - Animal monitoring → MQTT and cloud inference: uses vision inference
README.md - AI governance → PostgreSQL: records evaluations and promotions
implementation/server/src/services/ai-governance/routes.js - Tickets and loyalty → Popularity analytics: reads current popularity
implementation/server/src/services/ticketing-integration/routes.js - Tickets and loyalty → OAuth/OIDC provider: production sign-in