Policy Framework · Public Accountability

Governance & Accountability

Demand-management programmes must meet high standards of transparency and fairness. This page answers the governance question before it is asked.

MTSAi is designed so the public authority retains control of policy, data, and review processes while the operational infrastructure executes the authorised rules.

The city owns the policy. The city owns the data. The city controls the deployment.

Governance Principles

How Control is Structured

Principle 01

Government Defines Policy

All pricing, incentive, and eligibility parameters are set by the city or state authority. MTSAi executes — it does not decide.

Principle 02

Audit Trails Are Non-Negotiable

Every policy change, every charge, and every incentive calculation produces a traceable, timestamped, retrievable record.

Principle 03

Commuters Have Due Process

No commuter is penalised. Opt-in participation. Every calculation can be inspected and appealed through a formal process.

City Authority Retains Full Control

MTSAi is operational infrastructure, not a policy authority. The city or state government defines which corridors are included, which behaviours are rewarded, at what levels, and for how long.

  • Geographic scope is defined by the authority.
  • Incentive parameters are set and adjusted by the authority.
  • Operational data remains under city control throughout.
  • Vendor exit and data portability are defined in contract.
Key Commitment

No policy parameter changes without government authorisation. MTSAi cannot unilaterally alter pricing, incentives, or eligibility conditions.

Auditable Policy Rules

Every policy rule is versioned and documented. Changes to incentive parameters, eligibility conditions, or corridor coverage are recorded with a timestamp and authorisation trail. Audit-ready exports are available to the city authority at any time.

Policy rules are separated from code so governance decisions remain visible and modifiable without requiring technical intervention.

Key Commitment

Audit logs are available to the city authority at any time, without restriction, in exportable formats suitable for government review and CAG scrutiny.

Commuter Due Process

Commuters who dispute an incentive decision are given a defined appeal pathway. Every incentive calculation is logged. Every appeal is tracked. The system is designed so a commuter can understand why a decision was made and challenge it through a formal process.

No commuter is penalised under the system. Participation is opt-in. Incentives are earned, not imposed.

Compliance Alignment

The architecture is designed to align with:

Digital Personal Data Protection Act (DPDP) CERT-In Cybersecurity Guidelines Government of India Cloud & Hosting Standards Public Procurement Transparency Principles

These references describe design intent and readiness posture. Final compliance is verified through government audit per contract scope.

Governance at a Glance

Accountability is Structural

100% Government-controlled policy — every parameter requires authority authorisation
4+ Audit control areas with retrievable, timestamped records for every action
0 Silent policy changes — every change is authorised, logged, and reversible

Accountability is not a feature. It is a structural requirement. MTSAi is designed so that every policy decision is visible, traceable, and adjustable.

Platform Status Disclosure

Pre-Deployment Status (Jan 2026)

No live city implementations are currently operational. All deployment, outcome, and operational capability references are design specifications subject to government procurement, contract execution, and implementation.

Compliance Status

All references to regulatory frameworks represent design intent and readiness posture. Final compliance is verified through government audit per contract scope.

International References

Case study outcomes cited from London, Singapore, Stockholm, and other cities are external examples from independent transportation authorities, not MTSAi deployments.