Public Transit

An agency answers to riders, regulators and a control center at the same time. Model help with notices and reports is attractive, and operational detail must not ride along with it. A fixed set of checks sits between the two.

Control center staff and planners ask about a service change, an incident note or a passenger announcement. The starter checks each prompt and each reply. It has no tool permission and no link to signaling, ticketing or vehicle systems. A service decision stays with the controller on duty.

Passenger information is not what the masking patterns look for. They hide operator and badge numbers, maintenance or on-call phone numbers, and roster references. If your staff paste rider complaints or accessibility case detail, add patterns for that data yourself.

Requests that name a facility blueprint, a safety interlock or a control system password are refused. A second screen uses built-in wording and refuses explosives, weapons and attacks. Security awareness material uses all three of those words, so review the list before a security team adopts the starter.

Injection wording is screened first, and then a verified user and organization is required. The reply must reach a combined 0.87, with 0.78 for relevance and 0.80 for accuracy weighted evenly. Short replies fail at 120 characters or one sentence. A failing reply is refused, and the gate does not apply to streamed output.

Public transit safety duties, NIS2 and ISO 27001 form the reference set. Accessibility obligations, safety management and emergency planning remain your programs. Human review sits in the chain with nothing configured, so no reply is held for approval until you set it. The audit marker never blocks a request and never stores one.