The cleanup is a commons. सञ्चित कार्मिक ऋणस्य परिमार्जनम्

India is doing its own administrative archaeology.

The Jan Vishwas (Amendment of Provisions) Act 2023 — and its 2025 amendment, with a 2026 Bill in active drafting — is the Indian state's own admission that decades of accumulated rules, licence requirements, criminal clauses for paperwork errors, defunct agencies, and forms nobody has looked at since 1974 need to go. Hundreds of provisions, dozens of Acts, an active cleanup cycle with at least another decade of work in the pipeline. Sanjeev Sanyal at the EAC-PM, Manish Sabharwal in the Mint columns, Karthik Muralidharan in Accelerating India's Development have each, in their own register, named this as the central governance lever of the decade.

The state is doing its part. The backlog is vastly larger than what any central team can handle from the inside. That is not a complaint about the state — it is a description of the gap. Every administrative cleanup at civilisational scale needs an external research surface wider than the institution doing the cleaning. The Indian Law Commission once played a version of this role for primary legislation; Vidhi, PRS, Takshashila, NIPFP, CEGIS each play a fragment of it today, with limited bench depth and overflowing pipelines. The research surface that is structurally required is much larger than what these institutions can absorb on their own.

Something else has changed at the same time. A research workflow that would have taken a five-person think-tank team three months — primary-source review, regulatory archaeology, structured comparative analysis, drafting a proposed change — now takes one capable person with the right tools a focused weekend. The capability gap between trained researchers and motivated generalists has narrowed by an order of magnitude in eighteen months. The next institution that absorbs this delta well will run circles around the ones that don't.

One sentence.

The Jan Vishwas Commons (JVC) is a federated, commons-licensed civic-research repository where contributors claim specific frictions in the Indian state, research them, and ship structured proposals — under their own names, in a record that does not depreciate.

Mechanically it borrows from open-source software: a hosted Forgejo (open-source git) instance at forge.intercamp.in, an issue tracker that is also a problem catalogue, pull requests as the contribution mechanism, reviews as the sharpening loop, and a verifiable record on each contributor's profile. The unit of work is a bounty — not a competition prize, but in the open-source sense: a scoped problem with an explicit destination.

Philosophically it sits on three load-bearing claims this paper will work through, in order. First, that what the cleanup is cleaning is best named as Conway Debt — and that naming it precisely changes what one prioritises. Second, that the proper accounting unit for civic work is not metric-optimisation but Pañca Ṛṇa — the five civilisational obligations a polity carries. Third, that the substrate on which the commons lives has to be a commons, not a platform any later actor can enclose. The Techno-Memetic Commons licence is the legal instrument for that third claim.

What we are cleaning is Conway Debt.

Two ideas from two unrelated Conways combine into the diagnosis. Melvin Conway, 1968: any organisation that designs a system will produce a design whose structure is a copy of the organisation's communication structure. John Conway, 1970, Game of Life: simple rules produce persistent emergent patterns; once a glider is moving, it does not stop. Combine the two. Every organisation a civilisation has ever built leaves a structural fingerprint on the artefacts it produces. The artefacts outlast the organisation. New organisations inherit the artefacts and rebuild around them. The pattern propagates. The compounding skeuomorph is what we now wake up inside.

India's administrative substrate carries Conway Debt from at least four overlapping organisational topologies that no longer hold: the colonial extractive-administrative apparatus (1858–1947); the post-independence command-economy planning bureaucracy (1947–1991); the partially-liberalised licence-and-permission regime (1991–2014); and the digital-public-infrastructure overlay now being applied to all three substrates underneath. Each layer added rules without dismantling the previous; each new institution rebuilt around the existing artefacts. The current compliance surface is a topographic record of these strata, with sediment from each still computing in the present.

Naming it precisely matters because it changes the prioritisation. The Sanyal taxonomy of process reform — seven types from revisiting default lists to merging defunct agencies — describes the shapes the cleanup takes. Conway Debt describes why each shape exists. A list is frozen because it was generated under conditions that no longer hold and no organisation took ownership of refreshing it. A licence requirement is cosmetic because the threat it was designed against is gone. A grievance channel templates its closures because the organisational structure rewards closure rates, not resolution quality. Each is a glider from a previous era still running on the present grid.

A clean-up is therefore not simplification for its own sake. It is a deliberate refactoring of substrate against an updated ledger of what the polity owes — to its citizens, its ecology, its lineage, its knowledge commons, and its governance integrity. That ledger has a name.

Five debts, not one metric.

Western policy work optimises against metrics: GDP growth, compliance costs, EoDB rank, fiscal deficit. Each is useful; none is sufficient; many produce the very Goodhart pathology the cleanup is trying to undo. The Indic civilisational frame offers a different accounting unit. Pañca Ṛṇa — the five debts every generation owes and discharges. They are not optional, they are not tradeable against each other, and they cannot be cleared by monetary settlement. They are structural.

The structural advantage of the Pañca-Ṛṇa frame over single-metric optimisation is that it is Goodhart-resistant by construction. Each Ṛṇa holds the others in tension. You cannot optimise Manuṣya Ṛṇa by paying out cash transfers if Bhūta Ṛṇa has been defaulted on through the substrate the transfer is drawn against. You cannot discharge Dev Ṛṇa by automating grievance closures if Manuṣya Ṛṇa says the resolution had no substance. The four hold each other in a tensioned fourfold; no single one becomes the optimisable target. The bounties JVC catalogues are problem statements whose proposed unfreezes can be evaluated against this richer ledger, rather than against any single number whose movement was the explicit goal.

Problem statements, organised by debt.

What follows is a sample — not exhaustive, not final — organised by which Ṛṇa the proposed unfreeze principally discharges. Most real bounties touch two or three. The point of the organisation is to keep the work honest about what is being repaid. Each card lists the friction, the proposed shape of unfreeze, the natural destination, and the Sanyal-type tag where it fits cleanly.

Bhūta Ṛṇa — ecological substrate

Manuṣya Ṛṇa — citizen-facing friction

Pitra Ṛṇa — household, lineage, succession

Ṛṣi Ṛṇa — knowledge commons

Dev Ṛṇa — governance integrity

Each of these is a public-source bounty with a known destination that exists today. The aim of the Pañca-Ṛṇa grouping is to make visible what the cleanup is discharging, not just what it is removing. The next contributor who comes along and asks "which axis is undersupplied?" gets a usable answer.

What the commons can become.

The previous section is the catalogue at v0. What follows are directions the commons can grow in — fresh takes that draw on the philosophical substrate and would not be obvious from a compliance-cleanup framing alone. Each is a track that could eventually carry its own contributor cohort.

Why a commons, and why this commons.

The single most consequential decision the JVC will make is the substrate it lives on. Three available defaults: hosted on a US platform (GitHub / GitLab.com), hosted on a sovereign-but-private stack (a single Indian foundation or consultancy), or hosted on a self-owned federated open-source instance (Forgejo, on Intercamp infrastructure). The default many would reach for is GitHub; the right answer is Forgejo. The reasoning is structural.

A research substrate that catalogues frictions in the Indian state, written by Indian contributors, indexed and embedded into other surfaces — should not be silently learnable by the training corpora of platforms whose business model is to enclose and re-monetise the analysis. The Techno-Memetic Commons licence the Codex carries is the explicit instrument: contributors grant permissive use to all reciprocity-honouring consumers; closed-source enclosure with no commons obligation back is structurally disallowed under the terms. The substrate is open by default and protected against the specific surveillance-capitalist business model that would otherwise capture it.

Forgejo (a community-owned fork of Gitea) on Intercamp infrastructure gives us the operational ground for this. Federated identity, no platform dependency, full export, content-addressed attribution. The repository can be mirrored at any time to any destination by any reader. The commons is not "trusting" any single hosting decision; the design assumes hostility from any platform layer and is robust to that hostility.

How the commons stays itself.

Six commitments the founding cohort signs into. Each is a structural choice with a known failure mode if violated.

1. Contribution is the credential.

No selective admissions, no résumé filter, no application gate. A first bounty enters the queue from anyone; it is sharpened or merged on the merits of the work. Reviewers sharpen, they do not fail. Failure mode if violated: the commons becomes a credentialing institution, and the contribution stops mattering more than the contributor's prior.

2. The destination is part of the bounty.

Every bounty names a real downstream destination — a regulator, a committee, a state cell, a journalism pipeline, a think tank gap-fill, or the commons-as-its-own-destination. No abstract policy essays. Failure mode if violated: the commons accumulates well-written analysis that goes nowhere.

3. The commit is permanent.

Verifiable record of contribution, timestamped, citable, with a clear authorship trail. No retroactive deletion, no closed-source forks. Failure mode if violated: the commons becomes a portfolio showcase rather than a substrate.

4. The substrate cannot be enclosed.

The Techno-Memetic Commons licence on every accepted commit; Forgejo as the host; full mirrorability. No single later actor — even Intercamp / 2014P_ themselves — can take the commons private. Failure mode if violated: a platform play emerges on top of the commons and the contributors' work becomes extractable surplus.

5. Reviewers are stewards, not gatekeepers.

The review function exists to sharpen, to teach the format, to raise the floor. Not to defend a taste, not to filter for pedigree, not to reject as the default move. The first-bounty experience is what determines whether a contributor returns. Failure mode if violated: the commons attracts only the already-credentialed.

6. The commons audits itself, against Pañca Ṛṇa.

An annual cycle: which axes is the commons over- or under- supplying? Where are the cold sectors? Whose Ṛṇa is being systematically defaulted on? The diagnostic is reflexive. The commons is a member of the substrate it is auditing. Failure mode if violated: the commons starts measuring itself by output count alone, optimises against that, and reproduces Goodhart within its own walls.

What this draft is asking for.

This document is being shared with a small group: people who operate in policy think tanks, in civil service, in serious journalism, in founder networks, in research institutions, in university policy clubs. The aim is not consensus. The aim is sharp pushback on the parts that are wrong, so v4 can be tighter.

Five questions worth a response — even a one-line one:

1. Is the Conway Debt framing useful, or is it ornament on what is essentially a deregulation cleanup?
2. Does Pañca Ṛṇa as the accounting unit make this a richer commons, or does it narrow the audience prematurely?
3. If your institution were to use the commons (cite it, fund it, sponsor a track, sit on a review queue), what would the first concrete step be?
4. Is the substrate decision — Forgejo + TMC licence vs. GitHub default — load-bearing the way this draft claims, or is it premature optimisation?
5. What problem statement is missing from the sample that should be in the founding catalogue?

Write back to hello@2014p.com. Replies will be aggregated and a v4 will incorporate the load-bearing pushback. If you would rather speak than write, the same address. The platform begins seeding work in monsoon 2026; the founding bounties go into a record that does not depreciate.

The cleanup is not, finally, an efficiency project. It is a civilisation paying down debt that has been compounding for decades — to its citizens, its ecology, its lineages, its knowledge commons, its governance. The commons exists because no single institution can do this work alone, and because the substrate the work happens on shapes what the work can become. The choice of substrate is the choice of the next thirty years.