Chapter 1 — Why Government Must Change: From Schemes to Systems

Every chapter of The People’s Model follows the same eight-section template, so a reader can move from “what is broken” to “how we fix it” to “how we will…

Read this chapter in the interactive reader, or download the full 601-page manifesto (PDF).

---

The People’s Model

Manifesto v2026

Volume I — Core Architecture

Chapter 1

Why Government Must Change: From Schemes to Systems

Working chapter — canonical source; master volume compiled from chapters at publication

How to read this chapter

Every chapter of The People’s Model follows the same eight-section template, so a reader can move from “what is broken” to “how we fix it” to “how we will know it worked” without slogans. The sections are: Problem Snapshot, People’s Model Blueprint, How it Works (Operational Flow), Finance & Accountability, KPIs & Public Dashboards, Implementation Roadmap, Anti-capture Safeguards, and Citations & Further Reading.

This chapter is the entry point. It states the problem the rest of Volume I solves. The five non-negotiable commitments introduced here recur in every chapter that follows. The eight named anti-capture safeguards at the end are referenced by name throughout Volumes II and III.

1.1 Problem Snapshot

Karnataka is not short of laws. It is not short of schemes, missions, or announcements. The state runs hundreds of welfare programmes, has constituted dozens of expert committees, and publishes thousands of pages of budget documents every year. And yet the daily experience of a resident in Karnataka — whether in Bengaluru or Bidar — is shaped by the same five frustrations:

• A routine service takes weeks instead of the legally notified days, and the officer cannot tell you why. You filed the application — for a caste certificate, a mutation, a driving licence — that the Sakala Act says is yours by right within a fixed number of days. You came back, and came back again. The receipt in your file is real; the breach is real and quarterly published. What no dashboard records is the day you took off work, the parent you brought along to wait, the small humiliation of being told to come back next Tuesday. The right lives on paper. The discretion lives at the counter.
• A bribe is the quickest path to a routine document. Everyone knows the rate — for the birth certificate that should be free, for the property registration that already has an official fee, for the building permission, for the vehicle transfer. The rate is informal, but it is published — by uncle, by neighbour, by the agent who ’helps’ with the form. Honest citizens pay it because they cannot afford to lose another week. Honest officers learn early which colleagues are running the side business and which complaints will be punished. The state loses revenue, and worse, loses the citizen’s belief that following the rule is rewarded.
• The road outside your house is rebuilt every monsoon and broken every monsoon. You watch the trucks arrive in October, fix in November, fail in June. You watch the same patch the following October. The contractor has been paid; the engineer’s signature is in the file; the officer who signed is rotated by the time the surface gives way. Bengaluru’s pothole budget grows every year and the roads do not get better. You begin to understand that the system is not failing — it is succeeding at something other than the road you walk on.
• The government school three streets away has fewer enrolments than it had a decade ago. The teacher shortages have lasted years. The Grade 3 child who cannot read at grade level today will not read at grade level next year. The parents you know — the auto driver, the domestic worker, the small-shop owner — are pulling their children out and putting them in unregulated private schools whose only advantage is that the gate opens on time. The state is constitutionally obliged to educate every child. Every empty seat in the government school is a piece of that promise quietly walked back.
• The nearest government hospital ran out of essential medicines last week, and no one was held responsible. The shortages, the broken equipment, the drug stock-outs, the long queues, the buildings that have not been painted in a decade — these are not surprises. Everyone in the catchment knows. Across town, the private hospital insists on a deposit before treating an emergency, bills for procedures the patient did not need, and treats illness as a commercial opportunity. The citizen is caught between a public system that has been allowed to decay and a private system that has been allowed to predate. Either way, the bill comes due.

This is not a policy gap. It is an execution gap.

The pattern beneath every one of those frustrations is the same. Government has stopped being a producer of services and become a fund-distributor. The actual work — building, repairing, teaching, treating, inspecting — is contracted out to a chain of vendors, sub-vendors, and middlemen. When the chain delivers badly, the responsibility for the failure is distributed so thinly across files, agencies, and contractors that no single person can be held to account.

There is a deeper failure beneath every example above. Party and government have collapsed into one. The winning party’s office, staff, money flow, and loyalty become functionally indistinguishable from the state apparatus that should belong to every resident. Civil servants serve party priorities, not citizen rights. Transfers and postings become tools of political reward. Citizens who did not vote for the winning party are effectively second-class for the term. This collapse is the structural failure that produces the procedural failures above — and it is what the People’s Model exists to undo (Vol III Ch 19 + Ch 20).

The result is a loop that punishes everyone who is honest. Citizens pay through taxes and bribes, but cannot see what the money bought. Honest officers get blocked by processes that reward delay and punish initiative. Politics becomes a fight for contracts, because contracts are where the money actually flows.

The People’s Model begins from a refusal to accept this loop as inevitable. It is not.

1.2 People’s Model Blueprint

Founding principle — We do not believe in power. We believe in responsibilities. Every party position is a responsibility owed to citizens, not a possession (Party Operating Principles addendum, P.0).

The People’s Model treats government like an operating system, not a speech.

Government, in this manifesto, means the state apparatus — courts, civil service, police, schools, hospitals, the Election Commission, the entire delivery machinery — that owes equal service to every resident of Karnataka, regardless of vote, caste, religion, language, or party affiliation. The party that won the last election does not own this apparatus. The party sets policy direction through the manifesto and remains accountable to citizens through elections and recall. The state apparatus then executes — for every resident, on the same terms, with the same dignity. This distinction is the foundation; everything that follows operationalises it.

Government exists for three reasons: to protect life, to enable livelihood, and to uplift living standards. Everything else — technology, finance, law, even the manifesto you are reading — is a means to those three ends. We call this orientation Seva Sarkara: government as service, not government as rule.

The five non-negotiable commitments

For Karnataka, Seva Sarkara translates into five commitments. These are the spine of Volume I; every chapter that follows is the detail of one of them.

• A single state operating spine. One identity, one service registry, one citizen case file, one financial Open Ledger, one grievance system — all anchored through the Karnataka State Service Log (KSSL). Every interaction with the state is traceable from request to resolution.
• Outcome budgeting and open contracting. Every rupee is tagged to a measurable outcome. Every contract is published on the Open Contracting Data Standard. Every payment is tied to milestone evidence that any resident can inspect.
• State capacity over contractor dependency. A Project Delivery Cadre and a Government Works & Manufacturing Ecosystem bring core engineering, maintenance, and essential manufacturing back in-house where markets demonstrably fail.
• A 24/7 governance engine. Mission-control workflows. Service-level commitments published for the top 100 citizen services. Automatic escalation when deadlines slip. Citizen ratings that trigger audits rather than vanity dashboards.
• Digital rights as default. A Citizen Data Trust that gives residents ownership of their data. A published AI-use register for every government system. A Grievance Justice Authority with statutory teeth.

What this is not

This is not “big government”. It is capable government — small where markets work, strong where markets fail. The argument that follows in the rest of Volume I shows what that distinction means in practice: who builds the capacity (Chapter 5), how the money flows (Chapter 4), what the workflows look like (Chapters 2 and 3), and what rights the resident has against the machine (Chapter 6).

It is also not a critique of officers. The vast majority of officers in Karnataka work inside processes designed for a different century. The Model is the redesign. Officers are not the failure mode; the process is.

1.3 How it Works (Operational Flow)

Three perspectives let us show what the Model looks like once it is running: the resident’s, the officer’s, and the grievance pathway.

A resident’s day

You apply for an income certificate — once, on the People’s App or at the assisted service centre in your panchayat. The application generates a unique case number. The case carries with it the Service Charter for income certificates: who decides, in how many days, with what evidence, and what happens if those days slip. You can see, on your phone, exactly where the file is and which officer is acting on it. If the deadline slips, the case escalates automatically — first to that officer’s supervisor, then to a District Service Officer, then to the Mission Control room for that department. At no point are you asked to call, follow up, or pay a facilitator.

An officer’s day

You log in to a workflow that lists every case you own, sorted by SLA risk. Decisions you make create an auditable digital trail: timestamp, your officer ID, the supporting documents you cited, and the reasons you wrote. Approvals and rejections both require a reason — short, structured, in plain language — that the resident will see. If you need to consult a sister department, the case moves laterally inside the system; no one is sent to “go and get a clearance.” Your performance is measured on SLA adherence, decision quality (sampled by audit), and citizen rating — not on file movement.

A grievance

If something is wrong, the resident files once, against the case ID. The grievance triggers a parallel workflow with its own SLA and its own escalation ladder. Patterns across grievances — a particular taluk where a particular service always slips, a particular officer with disproportionate adverse decisions — surface automatically on the Mission Control dashboard and trigger audits, retraining, or process redesign.

The point is not that the Model removes officers. It is that the Model removes the structural reasons honest officers cannot perform.

1.4 Finance & Accountability

“Spend wisely” is not a slogan. It is a system. The People’s Model commits to three financial disciplines and one published constraint.

Outcome-based budgeting

Every budget line is tagged to a measurable outcome. A line that cannot be tagged either gets a tag or gets cut. The Karnataka budget will, by Year 2, publish an outcome-tagged share of total expenditure that increases year on year toward 100% of programmatic spend.

Open ledger spending

Program-wise, district-wise, and vendor-wise data on contracts, payments, milestones, and inspections is published on the Open Ledger portal in machine-readable form, aligned to the Open Contracting Data Standard (OCDS). The Karnataka Transparency in Public Procurements Act, 1999 already gives the legal basis; the Model puts the technical and operational infrastructure behind it.

Budget honesty

No off-book spending. All contingent liabilities and guarantees are disclosed in the budget book and reconciled against the Open Ledger.

The constraint

Karnataka’s 2025–26 budget targets a fiscal deficit of approximately 2.9% of GSDP and a revenue deficit of approximately 0.6% of GSDP (PRS, 2025). The People’s Model does not promise the impossible. We will not run the state into unsustainable deficit, and we will not pretend that reform is free. The headroom for reform comes from three places: leakage that becomes saving when payments move to milestone-evidence; competitive procurement that drops costs when single-bid tenders give way to multi-bid; and value-for-money that improves when outcomes — not line items — drive allocation. Every figure in this manifesto is checked against these constraints before publication.

1.5 KPIs & Public Dashboards

We commit to six headline KPIs for the state operating spine, each measurable from the Open Ledger or the case-file system. Each KPI has a Karnataka baseline (where data exists for 2025–26) and a target trajectory across the three phases set in Volume 0 Sec. 4.2: Foundations (Year 1), Build-out (Years 2–5), Consolidation (Years 5–10).

• Citizen-trust score (independent annual survey) — baseline: (new state metric); Year 1 baseline measured; Year 3 +10 points over baseline; Year 5 +20 points; Year 10 sustained top-quartile-in-India.
• Top-100 service SLA adherence (% within statutory timeline) — baseline: Sakala 2025–26 high breach; Year 1 dashboard live; Year 3 ≥80%; Year 5 ≥95%; Year 10 ≥99%.
• Open Ledger publication coverage (% of state spend above the KTPP threshold on OCDS within publication window) — baseline: low / sample-based; Year 1 pilot 5 departments + 5 districts; Year 3 ≥50%; Year 5 100% statewide.
• Grievance resolution within statutory SLA — baseline: high pendency; Year 1 GJA notified; Year 3 median ≤ statutory SLA; Year 5 ≥95% closed within SLA.
• Citizen audit participation (social audits filed per year, statewide) — baseline: low; Year 3 ≥1,000 / year; Year 5 ≥5,000 / year; Year 10 sustained citizen-driven oversight loop.
• Citizen receipt-verification rate — baseline: 0%; Year 1 100% of state transactions issue verifiable receipts; Year 5 ≥30% of citizens have verified at least one; Year 10 ≥60%.
• In-house works share (% of public-works rupee value executed in-house by Karnataka State Works Corps + state cadres rather than tendered to private contractors) — baseline: low; Year 3 ≥40%; Year 5 ≥60% (cross-ref Vol I Sec 5.5).

Each KPI’s definition, unit, source dataset, and audit frequency is published in Volume III Appendix A (Sector KPI Dictionary). KPIs that cannot be measured from open data are not eligible for commitment — a discipline enforced across every chapter of this manifesto.

1.6 Implementation Roadmap

The Model rolls out across the three phases set in Volume 0 Sec. 4.2. The roadmap below names the Foundations-phase actions that the first administration owns end-to-end.

Foundations — 0 to 100 days

• Publish the People’s Model Service Charter for the top 100 citizen services: each charter lists eligibility, documents, fees, timeline, decision authority, and escalation path.
• Launch the Open Ledger pilot in 5 departments and 5 districts. All new contracts above the KTPP threshold publish on OCDS from day one of the pilot.
• Issue the Project Delivery Cadre design — roles, competencies, training pathway, certification — as a public draft for review (see Vol III Appendix F).
• Establish a Mission Control room in the Chief Secretary’s office to track service-charter SLAs and Open-Ledger compliance.
• Stand up the Citizen Data Trust governing council (full legal entity follows in Year 1).
• Stand up the Karnataka State Service Log (KSSL) pilot — the cryptographic anchoring layer — alongside the Open Ledger pilot, with civil-society verifiers invited from Day 1 (see Vol I Ch 2 Sec. 2.2; Vol II Ch 15).
• Publish the four-front-doors and six-publishing-surfaces specification for public review (see Vol I Ch 2 Sec. 2.2).
• Publish the Quantum-Safe-by-Default Procurement Standard — every new build hybrid PQC from Day 1, inherited world on its own digitalisation clock (see Vol II Ch 15; Foundation Design A.5).

Foundations — Year 1

• Scale the case-file workflow to all departments touching citizen services.
• Introduce outcome budgeting across all capital works in the next state budget.
• Begin the Government Works & Manufacturing Ecosystem rollout, starting with the maintenance corps in two divisions (see Chapter 5).
• Notify the Grievance Justice Authority with statutory powers (see Chapter 6).
• Notify the Karnataka Cyber Security Operations Centre (CSOC) as a statutory body with compel-patching authority, reporting to the Civil-society Independent Audit Board (see Vol I Ch 6 Sec. 6.2 Institution 6; Vol II Ch 15; App I Sec. I.4.15).
• Notify the Civil-society Independent Audit Board with statutory ring-fenced budget; first annual public report scheduled (see Vol I Ch 6 Sec. 6.2 Institution 5; App I Sec. I.4.15).
• Bring KSSL online for the first cohort of state systems; Open Ledger and AI-Use Register publish through KSSL anchors from this point forward (see Vol I Ch 2 Sec. 2.2; Ch 4 Sec. 4.2).
• Launch JANATA + the Officer Console; the first tier of assisted-access points operational — Gram Panchayat Service Centres across the rural network, ward kiosks across the urban network (see Vol III Ch 22; Vol I Ch 2 Sec. 2.2).
• Stand up the Citizen Consent Ledger gateway — first personal-data flows carry citizen-issued tokens, visible on JANATA (see Vol I Ch 6 Sec. 6.2 Institution 4; App H sheet H.232).

Build-out — Years 2 to 5

• Replace paper-driven approval chains with digital-first workflows across all departments.
• Convert high-leakage spending categories — works, supplies, contracted services — to milestone-paid, evidence-based spending.
• Build district-level delivery units for maintenance and rapid repair.
• Publish the second-edition Open Ledger Data Dictionary (Vol III App D v2.0) covering all departments.
• Citizen Consent Ledger live across every personal-data flow in the state (see Vol I Ch 6 Sec. 6.2 Institution 4).
• Karnataka Open Data Portal expanded — sector outcome time-series with anchored cadences; civil-society standing on non-publication (see Vol I Ch 2 Sec. 2.2; App H sheet H.233; App I Sec. I.4.14).
• AI-Use Register populated with every state-operated AI system, with annual independent algorithmic audit (see Vol I Ch 6 Sec. 6.2 Institution 2).
• Open-source mandate enforced — public repositories, reproducible builds, SBOM mandatory, vendor-diversity ceiling for critical components (see Vol I Ch 6 Sec. 6.2 supporting rules; App I Sec. I.4.14).
• Business Portal + Civil Society Interface fully operational alongside JANATA and Officer Console (see Vol I Ch 2 Sec. 2.2; Vol III Ch 22).
• Long-secret data on hybrid PQC by Year 4, closing the harvest-now-decrypt-later window (see Vol II Ch 15; Foundation Design A.5).
• Village digital centre within walking distance of every household — small, staffed at scheduled hours, integrated with the Panchayat Service Centre and ward-kiosk network so every resident has an in-person assisted-access option by Year 5, regardless of smartphone or connectivity (see Vol II Ch 13; Vol III Ch 22; Vol III App H sheet H.236).

Consolidation — Years 5 to 10

• Karnataka measurably high-trust: fast services, low leakage, predictable delivery, and continuous published performance across every department.
• Citizen Data Trust fully operational with binding consent infrastructure.
• AI-use register binding on all government systems (see Chapter 6).
• KSSL anchoring across every state digital interaction; civil-society verifier infrastructure live; annual cryptographic audit published (see Vol I Ch 2 Sec. 2.2; Foundation Design A.7).
• Karnataka State Digital Infrastructure Act + Karnataka Cyber Security and Citizen Consent Act fully operational — architecture locked into statute (see App I Sec. I.4.14, I.4.15).
• Threshold cryptography enforced for sensitive operations — no single officer signs alone (see Vol I Ch 6 Sec. 6.2 supporting rules; App I Sec. I.4.15).
• Inherited-world cryptography migration on track within its fifteen-year outer bound; progress published annually (see Vol II Ch 15; Foundation Design A.5).

Every Foundations action above maps to at least one Volume III program design sheet, so the rollout can begin from day one rather than starting from a blank page.

1.7 Anti-capture Safeguards

The People’s Model separates money, power, and execution by design. Eight named safeguards make the separation enforceable. None of them is novel in isolation; what is new is that all eight run together, automatically, by default, from day one of the Model.

• Published workflow. Every service has its workflow published; deviation requires a written, public exception.
• Single accountable owner. One named officer per outcome, with a named backup. No diffuse responsibility.
• Automatic SLA escalation. Built into the workflow engine, not dependent on a complaining resident.
• Open Ledger publication. Every contract, payment, and milestone published in OCDS, in machine-readable form.
• Milestone-only payment. No advance against unmet milestones except in pre-disclosed categories with a cap.
• Bidder-competition floor. Tenders with fewer than three qualified bidders are reviewed by the Procurement Audit Cell before award.
• Conflict-of-interest register. Every officer above a defined grade declares assets, affiliations, and family-business interests. Mismatches with contract awards trigger automatic audit.
• Citizen-rating triggered audit. When ratings on a service category drop below a defined threshold in a district, an audit is automatically commissioned. The audit and its remedies are published.

Vol II uses these eight safeguards by name. Vol III Appendix C (Procurement & Works Red-Flag Catalog) operationalises items 4–6 as detection rules; Vol III Appendix H (Program Atlas) cites the relevant safeguards in the Standard Risk Controls section of every program design sheet.

Architecture note — the digital-state floor

The five non-negotiable commitments introduced in this chapter are now backed by a single cryptographic floor running underneath every state digital service. This floor — the Karnataka State Service Log (KSSL, Vol I Ch 2) — anchors every inter-system interaction into a publicly verifiable structure. Six publishing surfaces sit above it: the Open Ledger for financial flows; the AI-Use Register; the Karnataka Open Data Portal for time-series and dataset content; the Citizen Data Trust for personal records under citizen consent; the Karnataka Digital Twin raw store; sector operational systems. Four citizen-facing front doors — JANATA (residents), the Officer Console (state employees), the Business Portal (enterprises), and the Civil Society Interface (journalists, researchers, audit bodies) — talk to all of this through standard interfaces. The Karnataka Cyber Security Operations Centre (CSOC) and the Civil-society Independent Audit Board (Vol I Ch 6) keep watch.

Why this matters for the five commitments

Each of the five non-negotiable commitments depends on the floor below it. Time-bound delivery requires KSSL to anchor service-clock starts and stops. Open finance requires the Open Ledger anchored to KSSL so monthly publications carry cryptographic proofs of authenticity. Outcome accountability requires the Karnataka Open Data Portal for time-series outcome data, again anchored. Anti-corruption requires the cryptographic floor to make tampering mathematically detectable. Citizen rights against the state require the Citizen Consent Ledger and the Independent Audit Board to be real institutions with statutory teeth (App I). The five commitments were always the goal; this chapter’s role is to declare the problem, and the architecture across Ch 2-6 is how it is fixed.

1.8 Citations & Further Reading

Full bibliography for this chapter and the wider manifesto is in Vol III Appendix G (Research References).

Cross-references inside this manifesto

• Volume I — Chapter 2: Operating System components in detail.
• Volume I — Chapter 3: Mission Control room and workflow engine.
• Volume I — Chapter 4: Open Ledger, outcome budgeting and open contracting in depth.
• Volume I — Chapter 5: Government Works & Manufacturing Ecosystem; Project Delivery Cadre.
• Volume I — Chapter 6: Digital rights principles, Citizen Data Trust, AI-use register, Grievance Justice Authority.
• Volume III — Appendix A: Sector KPI Dictionary (definitions for every KPI above).
• Volume III — Appendix C: Procurement & Works Red-Flag Catalog.
• Volume III — Appendix D: Open Ledger Data Dictionary.
• Volume III — Appendix F: Project Delivery Cadre — Roles & Competencies.

---

← Method Note · Chapter 2 — The People’s Model Operating System: Identity, Services, Case Files, Four Front Doors, Six Publishing Surfaces, and the Karnataka State Service Log →

This is a chapter of The People's Model manifesto for Karnataka — published in full for public review. Every claim may be challenged: write to [email protected].