Appendices · The People's Model — Manifesto v2026

Manifesto_Vol3_AppD_OpenLedgerDataDict_v1.0_c0626.docx

This Appendix is the canonical field-level definition of every record published on the Open Ledger (Vol I Ch 4). It is the contract between Karnataka’s…

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

The People’s Model

Manifesto v2026

Volume III — Implementation Handbook

Appendix D

Open Ledger Data Dictionary

The contract between Karnataka’s internal systems and the public dashboards.

D.1 Purpose

This Appendix is the canonical field-level definition of every record published on the Open Ledger (Vol I Ch 4). It is the contract between Karnataka’s internal procurement, finance, and case-management systems and the public dashboards that residents, journalists, auditors, and oversight bodies use to verify state spending.

An unmapped field is by definition not published. A mapped field is published according to the publication-window commitments in Vol I Ch 4’s OCDS-alignment annex. Every change to this dictionary is a versioned, dated, published amendment with an effective-from date.

v1.0 of this Dictionary covers contracts, payments, milestones, and inspections. v2.0 (per the editorial-review process in Vol 0c MethodNote) extends to programme-tagged spending across all departments.

D.2 Standards alignment

OCDS — Open Contracting Data Standard v1.1.5. Every field in Sec. D.4 carries its OCDS identifier where one exists.
Karnataka Transparency in Public Procurements (KTPP) Act, 1999 and KTPP Rules, 2000 — the legal basis for the data publication.
e-Procurement — Karnataka Public Procurement Portal (KPPP). All eligible procurements pass through KPPP; KPPP records are the upstream source for the Open Ledger publisher.
Karnataka Sakala Services Act, 2011 — service-charter SLA data referenced from the spine (Vol I Ch 2 — Service Registry subsystem).

D.3 Publication-window commitments (from Vol I Ch 4 annex)

D.4 Field definitions (canonical)

D.4.1 Contract record

D.4.2 Milestone record

D.4.3 Payment record

D.4.4 Inspection record

D.5 Redaction & privacy

Personal data is never published at the resident level. Aggregation rules per Vol I Ch 6 (Citizen Data Trust) apply throughout this Dictionary.

Welfare disbursement to a named individual: published as district × scheme × month aggregate. Individual level visible only to the resident on their own case file.
Vendor contract data: fully public including vendor name, value, and milestone evidence — but redacted of any incidental personal data in attached documents.
Inspector identity: published as officer ID and role, not as personal name, in the public Open Ledger view. Names are visible to authorised oversight only.
Citizen ratings: published in aggregate per service × district. Individual ratings never linked back to the rating resident.

D.6 Versioning of this Dictionary

Every change to this Dictionary is a versioned amendment with an effective-from date. Field additions are MINOR; structural changes (field removal, type change, OCDS-mapping change) are MAJOR. Every amendment publishes on the Open Ledger Bulletin so downstream systems and dashboards can adapt.

Current version: v1.0. Next planned: v2.0 expanding to programme-tagged spending across all departments, per the editorial-review process in Vol 0c MethodNote.

D.7 Cross-references

Volume I Chapter 2 (operating spine) — the source of identity and case-file fields.
Volume I Chapter 3 (24/7 governance engine) — the source of workflow, SLA, and escalation fields.
Volume I Chapter 4 (Public Finance with 100% Accountability) — the OCDS-alignment annex this Dictionary operationalises.
Volume III Appendix C (Procurement & Works Red-Flag Catalog) — the detection rules that consume this Dictionary’s published data.

Architecture scope clarification

Architecture clarification — scope of the Open Ledger Data Dictionary

Under the operating architecture (Vol I Ch 2 Sec 2.2), the state’s publication surfaces are six: Open Ledger for financial flows; AI-Use Register; Karnataka Open Data Portal for time-series and dataset content; Citizen Data Trust for personal records; Karnataka Digital Twin raw store for de-identified historical content; sector operational systems. This Data Dictionary defines the schema for the Open Ledger — the financial-spine surface specifically, aligned with the international Open Contracting Data Standard (OCDS). Time-series and dataset schemas live on the Karnataka Open Data Portal under separate documentation (see App H sheet H.233). Personal-data schemas live with the Citizen Data Trust under the Citizen Consent Ledger (App H sheet H.232). The Open Ledger Data Dictionary stays the OCDS-aligned spec for financial publication.

KSSL anchoring of Open Ledger entries

Every Open Ledger entry is anchored through the Karnataka State Service Log (KSSL, App H sheet H.230). The anchoring chain ensures that a published Open Ledger entry can be independently verified for integrity by any external party. This Data Dictionary defines the data fields; KSSL provides the integrity floor.

Cross-references

Schema for financial flows — this dictionary. Schema for time-series and dataset content — separate, on the Karnataka Open Data Portal. Schema for personal-data flows — separate, through the Citizen Data Trust under citizen consent. All three surfaces anchored through KSSL.

Data category — Publication window — Trigger event

Planning data — At budget tabling — Budget tabled in Karnataka Legislature

Tender data — ≤ 24 hours from issue — KPPP tender publication

Award data — ≤ 7 days from award — Letter of Award issued

Execution data (milestones, evidence) — ≤ 30 days from event — Milestone certification / inspection

Payment data (release, invoice) — ≤ 30 days from event — Payment release authorisation

Defect-liability and maintenance records — ≤ 30 days from event — Defect raised / maintenance work-order

Field — OCDS path — Definition / source

contract_id — release.id — Globally unique identifier across Karnataka state contracting. KSC-<dept>-<year>-<seq>.

scheme_id — — — Outcome-tagged programme/scheme this contract belongs to. Cross-references the Outcome Budget.

dept_id — buyer.id — Owning department identifier. Karnataka State department reference list.

title — release.tag, contracts.title — Plain-language contract title. ≤ 200 chars.

procedure — tender.procurementMethod — open / limited / single-source. KTPP allowed values only.

bidders_count — tender.numberOfTenderers — Number of qualified bidders. <3 triggers Procurement Audit Cell review (Vol I Sec. 1.7 safeguard 6).

awarded_value_inr — awards.value.amount — Award value in INR. Currency code INR.

awarded_to_id — awards.suppliers.id — Awardee unique ID. Cross-references the Karnataka Supplier Registry.

start_date — contracts.period.startDate — ISO-8601 date. Contract commencement.

end_date — contracts.period.endDate — ISO-8601 date. Contract completion target.

officer_id — — — Karnataka officer ID of the contract owner (Vol I Sec. 1.7 safeguard 2).

Field — OCDS path — Definition / source

milestone_id — milestones.id — Globally unique milestone identifier within the contract.

contract_id — — — FK to contract record.

milestone_title — milestones.title — Plain-language description.

due_date — milestones.dueDate — ISO-8601. SLA clock anchor.

status — milestones.status — scheduled / met / notMet / partiallyMet.

evidence_uri — documents.url — Link to geo-tagged photo, measurement book, inspection report, or third-party verification.

inspector_id — — — Officer who certified the milestone. Rotation enforced (Vol I Sec. 3.7 safeguard 5).

citizen_visible — — — boolean. False only where the citizen-data redaction rule applies.

Field — OCDS path — Definition / source

payment_id — transactions.id — Globally unique within the Open Ledger.

contract_id — — — FK to contract record.

milestone_id — — — FK to milestone. NULL only for pre-disclosed advance categories.

amount_inr — transactions.value.amount — Payment amount in INR.

payment_date — transactions.date — ISO-8601. Authorisation date.

payer_id — transactions.payer.id — Drawing & Disbursing Officer ID.

payee_id — transactions.payee.id — Beneficiary / contractor ID.

evidence_ref — — — Cross-reference to the milestone evidence_uri. Stop-the-line enforces this for non-exception payments (Vol I Sec. 3.7 safeguard 2).

exception_code — — — Enum: NONE / ADVANCE / EMERGENCY / VARIATION / EXTRA_ITEM. Non-NONE triggers Vol I Sec. 1.7 safeguard 6 audit pathway.

Field — OCDS path — Definition / source

inspection_id — — — Globally unique within the inspection registry.

contract_id / asset_id — — — FK to contract or asset record.

inspector_id — — — Karnataka officer ID; rotation rules apply.

inspection_date — — — ISO-8601.

finding_code — — — Enum: PASS / DEFECT / REWORK / FAIL / WITHHELD.

evidence_uri — — — Inspection report, photographs, lab results.

geo_tag — — — Lat/long, ISO-6709.

← Manifesto_Vol3_AppC_RedFlagCatalog_v1.0_c0626.docx · Manifesto_Vol3_AppE_HelmetUnitEconomics_v1.0_c0626.docx →

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