BayanLink

Implemented Platform vs. Planned Roadmap

Municipal Incident Triage Friction

Municipal governance often relies on fragmented communication channels: citizen complaints submitted via social media comments, phone calls, and walk-in paper affidavits. This causes duplicate dispatch of municipal work crews, lack of verification on fraudulent reports, zero accountability for response times, and zero transparency for reporting citizens.

BayanLink was architected to replace this chaos with a structured, auditable incident lifecycle pipeline.

The Incident Verification & Dispatch Pipeline

When a citizen logs an infrastructure hazard or municipal issue, NestJS validates the report, checks for geospatial proximity to open tickets to prevent duplicate spam, and streams the event to verified agency operators over WebSockets:

@WebSocketGateway({ cors: { origin: '*' }, namespace: '/events' })
export class DispatchGateway implements OnGatewayConnection {
  @WebSocketServer()
  server: Server;

  // Broadcasts newly verified citizen incidents to authorized department rooms
  async broadcastIncident(incident: IncidentReportDto): Promise {
    const room = `department_${incident.departmentId}`;
    
    this.server.to(room).emit('incident:new', {
      id: incident.id,
      category: incident.category,
      severity: incident.urgencyLevel,
      coordinates: incident.coordinates,
      timestamp: new Date().toISOString(),
    });
  }
}