Volume I — Core Architecture · The People's Model — Manifesto v2026

Chapter 5 — From Contractor Raj to State Capacity: Government Works & Manufacturing Ecosystem

Today, the bulk of Karnataka’s public works and essential supplies are executed through layers of contractors. This creates a predictable failure pattern.…

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 5

From Contractor Raj to State Capacity: Government Works & Manufacturing Ecosystem

Where this chapter sits

Chapters 2, 3, and 4 build the digital, operational, and financial layers of capable government. This chapter builds the human and physical capacity layer — the engineers, project managers, manufacturing units, and quality systems that let the state actually deliver works and goods rather than outsource them to a contractor chain. The Project Delivery Cadre introduced here recurs in every chapter that follows; the helmet programme used as the worked example is also the unit-economics study in Vol III Appendix E.

5.1 Problem Snapshot

Today, the bulk of Karnataka’s public works and essential supplies are executed through layers of contractors. This creates a predictable failure pattern. Incentives reward low bids, change orders, and delays. Quality suffers because the owner — the state — lacks the technical capacity to supervise the work it commissioned. Public money leaks through inflated rates and commission chains. Long-term maintenance is ignored, because no one in the chain is paid to think about year 7.

The result is a state that pays without building capability. The chain is renewed at every project; the state learns nothing across projects. A new road needs a new tender, a new contractor, a new round of supervision, a new round of disputes, and a new round of maintenance that nobody owns.

A state that only purchases is a state that always pays more — and always for the same lesson.

5.2 People’s Model Blueprint

Chapter 5 commits to a Government Delivery Ecosystem with five components. Together they give the state the capability to execute core work in-house and to use contractors only where contracting clearly adds value.

Component A — Karnataka State Works Corps (KSWC)

District-level engineering units for roads, drains, public buildings, water assets, and routine maintenance. Each district unit carries its own survey teams, design and estimation cell, quality lab, and inspection corps. Rapid-repair teams handle potholes, streetlights, minor bridges, and school repairs as a standing capability rather than as one-off contracts.

Component B — State Project Delivery Cadre

A professional cadre — recruited, trained, certified — in modern project-delivery competencies. Roles are defined and standardised: sponsor, project manager, commercial manager, risk manager, planner, quantity surveyor, quality lead. The cadre rotates across districts and across asset classes so the state learns project-by-project. The full Roles & Competencies dictionary lives in Vol III Appendix F.

Component C — State Manufacturing Network

Public Production Units operated by the state — small at first, scaling with proven performance — that manufacture high-volume, high-leakage, essential goods. The starter portfolio:

ISI-certified helmets and safety gear.
School furniture, uniforms, and textbooks.
Basic medical consumables and emergency kits.
Water meters, LED streetlights, solar components.

Two principles govern the Network. First, start where the state already spends large amounts on items with predictable demand and significant leakage. Second, profits are not retained in a general fund — they are visibly reinvested in named public-good funds (Road Safety & Trauma Care, School Infrastructure, Emergency Response).

Component D — Entrepreneurial SOE Model

Where in-house operation needs more commercial flexibility than a standard department can provide, the Model uses State-Owned Enterprises with hard performance discipline: transparent annual targets, audited accounts, public dashboards, and dividend or reinvestment commitments published in advance. The international evidence base for SOEs is clear: they work where performance discipline is real and fail where it is not. Karnataka’s SOEs operate inside the discipline; the discipline is non-negotiable.

Component E — Where Private Contracting Remains

Mega projects, specialised systems, and capacity-peak work still require specialised contractors. The Model becomes an intelligent client: strong in-house designs, rigorous supervision, milestone evidence on the Open Ledger, and full-cycle OCDS disclosure. Contracting is a tool, not a default.

Architecture integration — human capacity for the cryptographic floor

The operating architecture creates new statutory bodies and operational roles that need real human capacity. Chapter 5’s State Project Delivery Cadre and Karnataka State Works Corps frame the model; this section names the architecture-specific capacity additions.

Karnataka Cyber Security Operations Centre (CSOC) staffing

CSOC is a statutory body (App I) with compel-patching authority across every state system. It needs trained incident responders, malware analysts, threat-intelligence analysts, vulnerability researchers, red-team operators, and forensic specialists. Staffing target: a defined core team of full-time employees in Year 1 scaling to operational maturity by Year 3, plus an open bug-bounty pool of accredited external researchers. Recruitment pipeline runs through state-run cyber programmes (Ch 5 — Government Works frame) and partnerships with state universities; salaries are benchmarked against industry comparables to avoid hollow-shell staffing.

Karnataka State Service Log (KSSL) operations team

KSSL is a runtime system. It needs a 24/7 operations team — site reliability engineers, cryptography engineers, infrastructure engineers — to keep the anchoring pipeline healthy, handle log-rotation cycles, manage the Hardware Security Module fleet, and keep every new system quantum-safe from inception while retiring legacy cryptography within the fifteen-year outer bound. Capacity target: a defined core SRE roster with a clear succession plan; documented runbooks; open-source operational tooling.

Threshold-cryptography quorum holders

Operations that touch more than 1 lakh personal records at once require a threshold-cryptography quorum. Quorum members are drawn from defined roles — never from a single department — and must hold their key material on Hardware Security Modules. Quorum members receive training on the operational responsibility, the legal weight of their signing role, and the audit standard they answer to. Quorum lists are public; quorum signing events are anchored on KSSL.

Civil-society Independent Audit Board secretariat

The Audit Board (Vol I Ch 6) is statutory, with funding ring-fenced from departmental control (App I). It needs an independent secretariat — auditors, data scientists, legal staff, communications staff. The secretariat capacity is built in Years 1-2; by Year 3 it conducts continuous independent audits across the six publishing surfaces.

Open-source maintenance capacity

The open-source mandate (App I) means the state’s code is publicly readable. It also means the state’s code is publicly maintained — there must be a continuous-engineering capacity that accepts, reviews, and integrates external contributions, ships releases, manages security advisories, and runs the public-development repositories. This is engineering work; Chapter 5’s Project Delivery Cadre is the home cadre.

Civic and officer literacy for the new architecture

Officers across every department need working literacy on the four front doors, the six publishing surfaces, KSSL, and the Citizen Consent Ledger. This is not specialist training — it is the basic operating literacy of working in the state. Curriculum is built into induction and continuing-education programmes for all state staff. Citizens receive a parallel literacy track through Vol III Ch 21 (Civic Literacy) on what their rights are, what JANATA shows them, and how to query the publishing surfaces.

5.3 How it Works (Operational Flow)

The transition pathway

The shift to in-house capability is staged, not overnight. Five sequential moves:

Map the top 20 works categories in Karnataka by spend and failure rate (roads, buildings, water systems, school infrastructure, hospital civil works, and so on).
Year 1 — bring design, estimation, and inspection in-house first across all 20 categories. The state becomes an intelligent client even while contractors continue to execute.
Years 1–2 — bring maintenance and small works in-house. These are the most leak-prone categories and the highest-frequency learning loop.
Years 2–5 — stand up in-house execution units for repetitive work in the highest-volume categories.
Years 5–10 — contractors retained only for specialised, high-tech, or capacity-peak projects, with the state as intelligent client throughout.

Worked example — the Helmet Programme (cross-reference: Vol III App E)

The Helmet Programme is a small example with the right shape: a state need, a manufacturing capability, a redistribution mechanism, and a published unit economics. Illustrative figures below; canonical model in Vol III Appendix E.

The point of the worked example is not that the state should be a helmet manufacturer in perpetuity. The point is that the state has been paying contractors and middlemen for items like this for decades, and that the same money, organised inside a Public Production Unit with published economics, funds road safety as a by-product. The same logic applies to school furniture, basic medical consumables, and LED streetlights.

Helmet Programme — Phase-0 launch (first 100 days)

Among all initiatives in this chapter, the Helmet Programme is uniquely positioned to land in Phase 0 because every input it depends on already exists at state level: BIS testing capacity, existing public-sector manufacturing facilities suitable for retro-fit, road-safety baseline data, and a clear distribution channel through state-run traffic outposts. Pulling it into Phase 0 turns it from a ’good idea in the manifesto’ into a visible, falsifiable proof that the State Manufacturing thesis works.

Day 0–30 — Facility selection. One existing state-owned facility identified, audited, retro-fit plan published with line-item costs. Selection criteria published in advance; selection score-sheet published with the selection.

Day 30–60 — Line installation and BIS certification. Production line installed; first 1,000-unit test batch produced; BIS certification applied. Independent inspector report on the Open Ledger.

Day 60–90 — First commercial batch. 50,000 units manufactured at the published unit cost; margin transferred to the Road Safety and Trauma Care Fund in real time, ledger entry visible.

Day 90–100 — Distribution. First commercial batch distributed to traffic outposts state-wide for first-time-rider subsidised sale. Programme runs continuously thereafter.

Falsification criteria — when the Phase-0 commitment is closed

The Phase-0 launch carries explicit fail conditions, all reversal of the standing programme is permitted: (a) cost overrun ≥ 25% on the published unit cost at the Day-90 audit point; (b) BIS certification not granted within 90 days; (c) margin transfer to the Road Safety and Trauma Care Fund delayed by more than seven days against the production ledger; (d) independent quality audit at Day 90 flags failure rates above the BIS test threshold. On any of these, the Phase-0 commitment is closed with a public after-action report. The standing Helmet Programme (Vol III App E) continues on its original timeline.

Mega-infrastructure pacing

Years 0–2 — build state-side planning capacity, DPRs, land and utility mapping, intelligent-client capability.
Years 2–5 — upgrade buses, commuter rail and district mobility hubs (fast impact, proven economics).
Years 5–10+ — evaluate regional rapid transit and inter-district corridors based on demonstrated ridership and fiscal capacity, executed through public delivery models with full transparency.

5.4 Finance & Accountability

Building state capability is a capital investment in long-term saving. The Model is explicit about both sides.

Capital needs

Tools, plants, labs, and depots for the Works Corps.
A training academy for the Project Delivery Cadre.
Initial manufacturing plants and quality certification infrastructure.

Savings and income channels

Less leakage from inflated rates and change orders, measurable as unit-cost-benchmark variation closing over time.
Lower life-cycle cost because quality and maintenance improve; the Defect-liability and Maintain stages now have real owners.
Manufacturing income — visible, capped, audited — funding named public-good funds rather than the general fund.

Fiscal posture

Start with categories where in-house delivery is demonstrably cheaper and repeatable.
Scale only after performance proves value; the Model does not commit to in-house delivery as an article of faith.
Publish the year-on-year cost-per-unit for every Works Corps category and every Manufacturing Network item, with district-wise variation.

5.5 KPIs & Public Dashboards

Six headline KPIs for the Government Delivery Ecosystem, each measurable from procurement records, cadre data, and works-completion evidence on the spine. Each KPI’s definition, unit, source dataset, and audit frequency is published in Vol III Appendix A (Sector KPI Dictionary).

Karnataka State Works Corps district coverage (% of districts with operational corps) — baseline: 0%; Year 1 maintenance corps in 2 divisions; Year 3 ≥50% districts; Year 5 100% districts.
Project Delivery Cadre members certified vs target — baseline: 0; Year 1 design issued + first cohort recruited; Year 3 ≥50% of target; Year 5 100% of target.
In-house works share (% of state works executed in-house, not contracted out) — baseline: low (~10-15% by category); Year 3 ≥40%; Year 5 ≥60%.
State manufacturing-line revenue from State Manufacturing Catalog products (₹ / year) — baseline: 0; Year 3 ≥₹500 crore / year; Year 5 ≥₹1,500 crore / year.
Critical-product fault rate from State Manufacturing — baseline: (new); Year 1 first lines live; Year 3 ≤1%; Year 5 ≤0.5%.
Cryptography-engineering cadre headcount (KSSL operations + threshold-crypto quorum holders + open-source maintenance) — baseline: 0; Year 1 core team; Year 3 operational maturity; Year 5 sustained roster with succession plan.

5.6 Implementation Roadmap

Foundations — 0 to 100 days

Publish the transition plan: which works categories move in-house first, and on what timeline.
Stand up the State Project Delivery Cadre design (Vol III App F) and begin recruitment for the first cohort.
Establish state-level quality labs and the first set of unit-cost benchmarks.
Commence helmet manufacturing feasibility and ISI certification pipeline.
Open the cryptography-engineering cadre under the State Project Delivery Cadre — recruitment pipeline for the engineers who keep every new build quantum-safe-by-default and who staff the KSSL operations team.
Stand up the cryptography-engineering bench inside the Project Delivery Cadre — small core team responsible for the KSSL anchoring pipeline, the HSM fleet, and threshold-cryptography quorum operations. Capacity target ramps over Years 1-3.

Foundations — Year 1

In-house design, estimation, and inspection units operational in every district.
Rapid-repair teams launched in the pilot districts.
First Manufacturing Network units commissioned — helmets and one or two other starter-portfolio items.
Open Ledger publication of unit costs and manufacturing economics for all Network items.
CSOC staffing reaches operational maturity — incident responders, malware analysts, threat-intelligence analysts, red-team operators, forensic specialists all in place; bug-bounty pool of accredited external researchers active.
Open-source maintenance capacity built into the Project Delivery Cadre — the engineers who accept, review, and ship updates against the state’s publicly-readable code base; the open-source mandate creates a real career track.

Build-out — Years 2 to 5

In-house execution capacity scaled for repetitive works in the top categories.
District production clusters and supply chains for the Network items.
State-level intelligent-client capability for mega-projects, run through the Cadre.
Civic + officer literacy on the four front doors, six publishing surfaces, KSSL, and Citizen Consent Ledger is induction-standard for every state employee; assisted-access counter staff trained to walk residents through receipt verification.

Consolidation — Years 5 to 10

Mature ecosystem: high-quality assets, reliable maintenance, large skilled job creation, reduced corruption space.
Network items either at sustained in-house production or, where market dynamics warrant, transitioned to a regulated open market — with the decision criteria published.

5.7 Anti-capture Safeguards

Bringing capability in-house carries its own capture risks. The eight Chapter 1 safeguards apply; four additional safeguards apply specifically to the Government Delivery Ecosystem.

Rotation of inspectors and project managers across districts and contractors on a published schedule.
Independent quality labs not under the operational control of the units they test.
Whistleblower protection with statutory backing for officers and citizens reporting irregularities in works or production.
Published unit costs — district-wise and over time — so a contractor or a unit cannot quietly inflate.
Mandatory third-party tests for critical works (structural, safety, public-health-sensitive).
Zero tolerance for unexplained cost variations; variations beyond a defined band require a written reason and trigger automatic audit.
Vendor capture of the engineering bench. The open-source mandate keeps the state’s code base public — civil-society can audit it, fork it, run their own verifier nodes. Combined with the SBOM mandate and the vendor-diversity ceiling, no single vendor can hide a black box inside state infrastructure.
Capture of the cryptographic floor itself. KSSL signing keys are held under threshold cryptography in Hardware Security Modules; no single administrator can sign anchor batches alone. The quorum membership is public and rotates; key rotation runs on a published schedule with a pre-published compromise-recovery protocol.
Cadre-pipeline capture. Recruitment, promotion, and discipline of the State Project Delivery Cadre — including the cryptography-engineering bench and CSOC staff — are overseen by the Civil-society Independent Audit Board with statutory budget protection.

5.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 — Chapters 1–4 (commitments, spine, runtime, finance).
Volume II — Chapter 8 (Health: pooled supply chain), Chapter 9 (Cities: works and maintenance), Chapter 12 (Justice: court-system delivery).
Volume III — Appendix B (Public Project Lifecycle SOP), Appendix E (Helmet Programme Unit Economics — canonical), Appendix F (Project Delivery Cadre — Roles & Competencies).

Line — Illustrative figure (canonical in Vol III App E)

ISI-certified helmet — manufacturing cost (state production unit) — Around ₹450 per unit at scale.

Transparent margin (~30%) — Around ₹135 per unit. Cap and method published.

Kiosk sale price — single fixed price for all purchasers — Around ₹585 per unit.

Margin destination — Ring-fenced Road Safety & Trauma Care Fund. Visible on Open Ledger.

Year-1 production target — 5 lakh units.

Year-5 production target — Scaling toward 20 lakh units annually.

Net contribution to Road Safety & Trauma Care by Year 3 — Estimated ₹50–100 crore range; published on Open Ledger as actuals.

← Chapter 4 — Public Finance with 100% Accountability: Outcome Budgeting, Open Ledger, Open Contracting, and Cryptographically Anchored Auditability · Chapter 6 — Ethics, Oversight, Digital Rights, and Citizen-controlled Data: AI that Serves People →

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].