Pehchan

By 2 June 2026, the Labour Department had registered 12,545 service providers in Ganderbal for an Amarnath Yatra that went on to serve more than 4.8 lakh pilgrims. Ponywallas, porters, drivers, guides, and camp staff work across a wide mountain corridor. Telling a registered provider from someone who simply turned up meant trusting a paper list held somewhere else — no help to an officer at a checkpoint or a family hiring a pony at Baltal.

Seasonal operations bring a large, changing workforce into sensitive ground. Manual lists go stale. Physical credentials are slow to validate. A delayed check creates a queue at precisely the wrong place. The system had to be fast enough for a queue and accountable enough for a corridor.

Police teams gained one corridor-wide verification workflow. Legitimate providers gained a recognisable identity. Pilgrims gained a direct way to check the people serving them.

Identity moved from a distant list into the field operation — across a registration context of 12,545 people on a corridor serving more than 4.8 lakh pilgrims.

We are taking Pehchan as the identity pattern for other seasonal and corridor workforces: the same QR loop, the same AEGIS controls, configured to the register a department already runs.

Next on our side: closer binding of a verified provider into Trinetra field posts and Sentinel command views, so a checkpoint decision is visible to the rest of the corridor operation.