How asav-mx/j-tel works
JTEL is a multi-account platform for verifying employee transportation services. Client organizations configure sites, contracts, geofences, routes, shifts and services; carriers manage vehicles and contribute operational evidence; platform staff administer circuits and investigate exceptions. GPS ingestion and scheduled verification feed compliance results, which users monitor and receive as alerts. A separate public app exposes live transit information and ticket-validation workflows. The supplied excerpts show selected API and service calls; several broader subsystem connections are documented or suggested by the tree but are left unwired where implementation evidence is missing.
Main entry points: services Verification and ingestion · cron Verification jobs API · app Rider app · cliente Client configuration API
Components 25
Client setup
- Client configuration API
apps/web/src/app/api/cliente - Client configuration data
packages/db
Fleet operations
- Carrier operations API
apps/web/src/app/api/carrier - Fleet and service data
packages/db - GPS integration
packages/gps-umbrella
Verification
- Verification jobs API
apps/web/src/app/api/cron - Verification and ingestion
packages/services - Decision engine
packages/verification - Compliance records
packages/db - Alerting
apps/web/src/lib/alertas - Health endpoint
apps/web/src/app/api/salud/route.ts
User experiences
- Client workspace
apps/web/src/app/cliente - Carrier workspace
apps/web/src/app/carrier - J-Staff workspace
apps/web/src/app/jstaff
Public transit
- Rider app
apps/publico/src/app - Transit and ticket API
apps/publico/src/app/api - Ticket reader
apps/publico/src/lib/validador
Other components
- Client operators
- Carrier operators
- J-Staff operators
- Scheduled jobs
- GPS provider
- Alert channel
- Transit riders
- PostgreSQL
Connections 22
- Client operators → Client workspace: uses
- Client workspace → Client configuration API: submits configuration
- Client configuration API → Client configuration data: reads and writes
- Client configuration data → PostgreSQL: persists
- Carrier operators → Carrier workspace: uses
- Carrier workspace → Carrier operations API: submits operations
- Carrier operations API → Fleet and service data: reads and writes
- Fleet and service data → PostgreSQL: persists
- GPS integration → GPS provider: fetches GPS data
- Scheduled jobs → Verification jobs API: invokes
- Verification jobs API → Verification and ingestion: orchestrates
- Verification and ingestion → Decision engine: requests decisions
- Verification and ingestion → Compliance records: records outcomes
- Compliance records → PostgreSQL: persists
- J-Staff operators → J-Staff workspace: uses
- Verification jobs API → Alerting: builds alerts
- Alerting → Alert channel: sends notifications
- Health endpoint → Verification and ingestion: gets diagnosis
- Transit riders → Rider app: uses
- Rider app → Transit and ticket API: requests transit data
- Rider app → Ticket reader: scans tickets
- Ticket reader → Transit and ticket API: synchronizes scans