Chapter 4 — Public Finance with 100% Accountability: Outcome Budgeting, Open Ledger, Open Contracting, and Cryptographically Anchored Auditability

Public Finance with 100% Accountability: Outcome Budgeting, Open Ledger, Open Contracting, and Cryptographically Anchored Auditability

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 4

Public Finance with 100% Accountability: Outcome Budgeting, Open Ledger, Open Contracting, and Cryptographically Anchored Auditability

Where this chapter sits

Chapter 2 named the operating spine. Chapter 3 named the runtime that operates it. This chapter is the financial discipline that flows through both: how Karnataka’s budget is built, how every rupee is tagged to an outcome, how every contract is published, and how every payment is tied to evidence. The Open Ledger and the OCDS-aligned contracting feed every dashboard in every subsequent chapter.

4.1 Problem Snapshot

Karnataka’s governance failure is not, primarily, an absence of money. It is the absence of measurable outcomes per rupee, the absence of full-cycle contract transparency, the absence of payment discipline, and the absence of timely audit. When citizens cannot see where money goes, trust collapses — and politics becomes a fight over contracts rather than a contest over results.

Today, a resident of Karnataka cannot easily answer four basic questions about the public finance that shapes their daily life: How much of my district’s budget went to my pothole-prone road this year? Which contractor built it, at what unit cost, on what timeline, with what milestone evidence? When was the contractor last paid, and against what verified work? When was the road last audited, and what did the audit say?

These are not exotic questions. In a state with the data infrastructure Karnataka already has, they are answerable today; they are simply not answered. The People’s Model treats this gap as a public-finance design failure, not an information-technology one.

In a transparent state, the answer to “where did my taxes go?” takes one tap on a phone, not one RTI request to a district office.

4.2 People’s Model Blueprint

Chapter 4 commits to a Public Finance Operating System with five disciplines. Together they make every rupee traceable and every promise measurable.

Discipline 1 — Outcome Budget and Program Ledger

Every budget line is tied to a measurable outcome, an implementing unit, and a milestone trajectory. Every spend is tagged: scheme → district → asset or beneficiary → contract → invoice → payment. The Program Ledger replaces line-item accounting as the operative view; the line-item view continues for statutory compliance but is no longer the working artefact of public finance.

Discipline 2 — Open Contracting by Default

Every contract is published on the Open Ledger across the full contracting cycle — planning, tender, award, execution, payments, completion, defect-liability, maintenance — in machine-readable form aligned to the Open Contracting Data Standard (OCDS) v1.1.5. Karnataka’s existing legal base is strong: the KTPP Act, 1999 and the KPPP e-procurement portal already cover tender and award. The Model extends this to true end-to-end contract execution management.

KSSL cryptographic anchoring — the audit floor

The Open Ledger is the financial transparency spine. The Karnataka State Service Log (KSSL, Vol I Ch 2) is the broader cryptographic audit spine — it carries every inter-system interaction across state services, not only the financial ones. Every entry in the Open Ledger is anchored to KSSL: a contract published on the Open Ledger gets a KSSL inclusion proof, and any party can independently verify that the contract record exists exactly as published and has not been altered. Periodic anchors are published using open public-verification protocols, so the integrity guarantee extends beyond state control — a successor government cannot quietly rewrite an Open Ledger entry without leaving a mathematically detectable trace.

Every payment also returns a citizen-verifiable receipt: the payee — and any auditor — can confirm against the published KSSL anchor that the payment entry exists and has not been altered. Receipts work offline: a printed or SMS receipt carries the same verifiable reference.

This is what ’one hundred percent accountability’ means in practice. Not state-assured transparency — independently verifiable transparency.

What lives where

The Open Ledger holds: contracts, payments, milestone evidence, outcome-budget tagging, party-side financial accounts, sanctions register, aggregate audit findings, and aggregate summaries from other publishing surfaces. Not on the Open Ledger: per-citizen personal records (those live in Citizen Data Trust, Vol I Ch 6); time-series sensor + forecast data (Karnataka Open Data Portal); AI deployment metadata (AI-Use Register); geospatial raw data (Karnataka Digital Twin raw store); department-internal operational records (Sector operational systems). Citizens navigate all of this through JANATA without needing to know which surface holds which record.

Discipline 3 — Payment Discipline

Milestone-only payments, with milestone evidence — geo-tagged photographs, measurement-book data, inspection reports, third-party verification where applicable. No ad-hoc advances except in pre-disclosed categories with a published cap and a recovery schedule.

Discipline 4 — Independent + Citizen Audit

A professional internal audit unit runs continuous audit on the Program Ledger. The Comptroller and Auditor General continues its statutory audit. Social audits are mandatory for high-impact welfare and works programmes. A Public Red-Flags dashboard surfaces single-bid tenders, repeated change orders, delayed projects, and abnormal unit costs to citizens, journalists, and oversight bodies in real time.

Discipline 5 — Fiscal Prudence with Transparency

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 commits to fiscal responsibility within statutory limits and to publishing every contingent liability and guarantee in the budget book and on the Open Ledger. Maintenance gets a ring-fenced allocation as a structural matter; deferred maintenance is itself a fiscal shock waiting to happen.

4.3 How it Works (Operational Flow)

The budget cycle

• Pre-budget — publish prior-year outcomes and baseline metrics for the top 100 programmes; invite citizen and civil-society inputs through a structured consultation that produces a published response document.
• Budget day — publish, alongside the budget, the programme objectives, the unit costs, the district-wise allocations, and the outcome tags.
• During the year — monthly Open Ledger updates of financial flows (spending, contract execution, payment milestones); project progress and outcome dashboards on the Karnataka Open Data Portal updated at the same cadence; quarterly published exception reports on red items. Both surfaces are anchored to the Karnataka State Service Log so the monthly updates carry cryptographic proofs of authenticity.
• Year-end — publish what worked, what failed, and why, in the same Outcome Budget format as the budget itself, so any reader can compare promise to delivery.

Procurement and execution

• All eligible purchases on KPPP e-procurement; no manual tenders above the KTPP threshold.
• Standardised bid documents and item schedules across the state to reduce discretionary variations.
• Contract execution tracked as a workflow on the runtime engine (Chapter 3): Mobilisation → Measurement → Inspection → Payment → Defect-liability → Maintenance.
• Every workflow stage publishes its evidence on the Open Ledger within the publication window.

The citizen interface

• My Tax, My State — a dashboard showing where state revenue came from in the resident’s district, what it funded, and at what outcome.
• Track My Project — a public page for every public work in the state showing cost, contractor, milestones, geo-tagged photographs, payments, defects raised, and grievances filed.
• Compare Districts — a benchmarking view that lets any resident see how their district’s unit costs and SLAs compare to neighbours.

The OCDS-alignment annex

The Open Ledger publishes contracting data in OCDS v1.1.5 form. The mapping between Karnataka’s legacy data fields and OCDS fields is published in Vol III Appendix D as the Open Ledger Data Dictionary. The mapping is the contract between the state’s internal systems and the public dashboards; an unmapped field is by definition not published.

The annex specifies four publication-window commitments. Planning data publishes at budget tabling. Tender data publishes within 24 hours of issue. Award data publishes within 7 days of award. Execution and payment data publishes within 30 days of the underlying event. Implementation publishes against these commitments as KPIs on the Public Red-Flags dashboard.

4.4 Finance & Accountability

Public finance is a full system: Revenue → Allocation → Procurement → Delivery → Audit → Learning. Each stage carries its own disciplines.

Revenue principles

• Stable tax base, supported by simpler compliance — fewer forms, fewer touchpoints, fewer rates.
• Non-tax revenue from public services where appropriate, with full carve-outs to protect access for residents below the poverty line.
• Profits and dividends from public manufacturing units (Chapter 5) are visible on the Open Ledger and reinvested into named public-good funds — Road Safety & Trauma Care, School Infrastructure, Emergency Response — not the general consolidated fund.

Spending principles

• Maintenance-first — every department with built assets sets a defined minimum percentage for maintenance, ring-fenced from re-appropriation.
• Capital expenditure with a published business case — life-cycle cost, alternative-options analysis, and risk register accompany every capital sanction above a threshold.
• Targeted subsidies with data-linked verification — to reduce both leakage and exclusion errors.

Value-for-money tools

• Standard unit-cost benchmarks, published district by district; cost variations beyond a band require a written reason on the contract record.
• Life-cycle costing — build plus operate plus maintain — replaces lowest-bid as the default award criterion for asset-creating works.
• Stop-the-line — when milestone evidence is missing on a payment request, the payment pauses automatically and the case appears in the L2 queue (Chapter 3).

4.4a Consistency principle — free for survival essentials, paid for infrastructure use

A unifying principle runs through every basic-amenity and entitlement commitment in the manifesto. Free, at no charge to the citizen, is reserved for survival essentials — twenty litres of drinking water per person per day (Vol II Ch 9 Sec. 9.6.10), free trauma care under the Road Safety Programme (Vol II Ch 9 Sec. 9.6.7), free use of the Public Toilet Network (Vol II Ch 9 Sec. 9.6.9), free public education and the broader Learning State (Vol II Ch 7 Sec. 7.4). Everything else is paid use. Electricity is paid at all volumes including lifeline (Vol II Ch 9 Sec. 9.6.10). Public transport is paid fare. Digital connectivity is paid bandwidth.

Health-care follows the same rule on a phased path. Primary and secondary care is free at the point of care for every Karnataka resident from Year 1 under the Karnataka Universal Health Entitlement (Vol II Ch 8). Catastrophic, rare-disease, and unforeseen-serious-illness care is covered by Year 5 through the Catastrophic Care Fund. By Year 10, every Karnataka-domiciled resident has free access to the full diagnostic-and-treatment stack — every district hospital and tertiary hub equipped — for all unforeseen and serious medical conditions, with no means test. Elective and lifestyle health consumption remains paid. What a citizen cannot predict and cannot bear alone is the state’s burden; what a citizen chooses to consume is paid.

Why this rule

Blanket free quotas to all households are politically attractive but fiscally corrosive — they crowd out the capital investment needed to actually build and maintain the underlying infrastructure. A guaranteed entitlement to survival essentials plus paid use of infrastructure is fiscally sustainable across ten years and beyond, which is what the public actually needs. Subsidies for households below the poverty line go via targeted means-tested mechanisms — a transport pass, scheme-based assistance, the Public Distribution System — not via blanket free quotas that benefit all consumers including high-income ones.

Application across the manifesto

Every sector chapter that establishes a basic-amenity commitment follows this principle. The principle is the dividing line that distinguishes entitlement (free for survival) from infrastructure (paid for use). When in doubt, the question is: is this what a citizen needs to survive, or is this consumption of a public asset? Survival = free. Consumption = paid.

4.5 KPIs & Public Dashboards

Six headline KPIs for the Public Finance Operating System, all measurable from the Open Ledger.

• Outcome-tagged capital-works share (% of capex tagged to measurable outcomes) — baseline: low; Year 1 pilot; Year 3 ≥50%; Year 5 100%.
• Milestone-paid disbursement share (% of state works paid against anchored milestone evidence) — baseline: low; Year 1 pilot; Year 3 ≥50%; Year 5 100%.
• Contract-award-to-publication lag (median days from award to OCDS publication) — baseline: variable; Year 1 ≤7 days; Year 3 ≤24 hours; Year 5 same-day.
• Anomaly-detection precision (% of automated flags validated as real issues) — baseline: (new); Year 3 ≥70%; Year 5 ≥85%.
• Public-audit participation (social audits filed per year, statewide) — baseline: low; Year 3 ≥1,000; Year 5 ≥5,000.
• Outcome-miss → corrective-action cycle time (median days from miss detection to corrective action on dashboard) — baseline: (new); Year 3 ≤30 days; Year 5 ≤14 days.

Two further indicators are tracked but framed as trust outcomes rather than financial KPIs: citizen audit participation (number of social audits convened per district per year) and RTI request volume, which the Model expects to decline as the Open Ledger publishes by default what RTI requests currently extract case by case.

4.6 Implementation Roadmap

Foundations — 0 to 100 days

• Publish the Spend Wisely Charter — the full list of what data the state will publish by default, in what format, and within what window.
• Launch the Open Ledger pilot for all capital works in 5 departments and 5 districts, and for 3 flagship welfare schemes. In parallel, bring the Karnataka State Service Log (KSSL, Vol I Ch 2) online for the first cohort of financial systems so every Open Ledger entry is anchored to a publicly verifiable structure from the pilot stage.
• Publish the Public Red-Flags dashboard (single bids, time overruns, change orders, abnormal unit costs) for the pilot scope.
• Publish the OCDS-alignment annex and the first version of the Open Ledger Data Dictionary (Vol III App D).

Foundations — Year 1

• Apply the Outcome Budget framework across all departments in the next state budget.
• Integrate KPPP tender data with execution and payment data on the Open Ledger end-to-end.
• Bind the maintenance-first allocation rule into the budget.
• Stand up the Public Finance Audit Cell that runs continuous audit on the Program Ledger.

Build-out — Years 2 to 5

• Full-cycle open contracting across all contracting departments, aligned to OCDS.
• Automated anomaly detection on the Open Ledger feeding Mission Control queues (Chapter 3). Automated cryptographic-anchor verification by the Karnataka State Audit Office, with discrepancy alerts to the Civil-society Independent Audit Board (Vol I Ch 6).
• Move all subsidy disbursement to data-linked verification on the spine.
• Publish the My Tax, My State and Track My Project interfaces statewide.

Consolidation — Years 5 to 10

• Audit in near-real-time. Near-zero dark spending. Faster correction. Higher value per rupee.
• Karnataka’s Open Ledger and the Karnataka State Service Log architecture published under open licence as a reference for other states. The cryptographic-anchoring approach is documented as an open national / international standard.

4.7 Anti-capture Safeguards

The eight named safeguards from Chapter 1 apply to public finance. Three carry finance-specific operative rules; three additional finance-specific safeguards apply.

Finance-specific rules for Chapter 1 safeguards

• Open Ledger publication — within the publication windows defined in the OCDS-alignment annex. Missed windows are auditable events.
• Milestone-only payment — Stop-the-line is the default; exceptions are pre-disclosed and capped.
• Bidder-competition floor — single-bid tenders flagged in real time on the Red-Flags dashboard; awards reviewed by the Procurement Audit Cell.

Finance-specific additional safeguards

• Hard-limit discretion. Any exception — nomination, emergency purchase, price variation, extra item — triggers automatic disclosure, senior approval, and post-facto audit within 30 days. Three exceptions of the same kind from the same officer within 12 months triggers an investigation.
• Inspectors rotate. Inspection assignments rotate on a published schedule; no inspector is assigned to the same contractor on consecutive cycles.
• Third-party financial audit. A defined percentage of payment-release decisions is independently audited every quarter by a panel of empanelled chartered-accountant firms chosen by lot, not by appointment.

Major capital programmes — including The Learning State build (Vol II Ch 7 Sec. 7.4: DHEC network, Karnataka Apex Institute, district + taluk museum network, KPB, library upgrades) — are funded through 5-year capital tranches locked by legislative appropriation per the durability discipline in Vol II Ch 7 Sec. 7.4. Capital tranches cannot be re-purposed without legislative amendment; this protects multi-year build commitments across electoral cycles. Full fiscal framework in Vol III Appendix J.

• KSSL cryptographic anchoring of every financial event. Every Open Ledger entry is anchored through the Karnataka State Service Log into a publicly verifiable structure. Independent civil-society verifier nodes re-check the anchors continuously. A future government cannot quietly rewrite the record of a contract award, a milestone payment, or an outcome miss — tampering is mathematically detectable.
• Threshold-cryptography quorum on high-value disbursements. Contract awards above the published threshold and bulk disbursements require a multi-signer quorum encoded in Hardware Security Modules — no single Finance officer, however senior, can sign alone. The quorum membership is public and rotates.
• Civil-society Independent Audit Board oversight. The Board’s annual audit of public finance is published, with statutory powers to compel disclosure of contract documentation, payment records, and Open Ledger anchoring proofs.

4.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 1, Chapter 2, Chapter 3, Chapter 5.
• Volume II — every sector chapter uses the Open Ledger and Outcome Budget frame from this chapter; Vol II Ch 11 (Environment) uses life-cycle costing explicitly.
• Volume III — Appendix B (Public Project Lifecycle SOP), Appendix C (Procurement & Works Red-Flag Catalog), Appendix D (Open Ledger Data Dictionary).

---

← Chapter 3 — The 24/7 Governance Engine: Mission Control, Workflows, and Reliable Delivery · Chapter 5 — From Contractor Raj to State Capacity: Government Works & Manufacturing Ecosystem →

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