I have been working on something like this but for all countries and elected officials. Project20x.com is the policy cycle as a service: AI-native governance with an elected officeholder as the human-in-the-loop at every step. Today the cycle — author policy, codify into bureaucratic process, deliver as a service, measure outcomes, feed back into policy — takes years end-to-end and the layers are owned by four different industries that don't talk to each other. project20x compresses it to minutes by running all four layers as one substrate.

Three layers, one substrate:

Hardison.co — policy authoring as software. Coalitions, elected officials, and domain experts design policy as machine-readable artifacts, not 900-page PDFs. The Heritage Foundation role, done as a service. - white label for usa = dnc.project20x.com and rnc.project20x.com

DPIaaS at project20x.com prev: codify.inc) — the policy operating system. Identity, payments, data exchange, the codification engine, agent orchestration. Where policy compiles into a running program. This is the answer to what DOGE was attempting: efficiency by compilation, not chainsaw.

DPGaaS — codified programs delivered as live services at {program-guid}.codify.{domain} e.g.: education or healthcare. EMR, EHR, LMS, HRM, finance, civic CRM — 44 domains. Project 2025 is a stack of policy artifacts; DPGaaS is the same stack executed.

Why network-by-default, not pilot-one-agency: government does not run on org charts, it runs on interagency dependencies that nobody owns. VA referring veterans to HUD for housing. HHS coordinating with all 50 state Medicaids. EPA negotiating permits with state DEPs. Tokyo studying Helsinki's home-visit program. Single-agency rollouts hit a wall the moment they try to hand off. The right unit of deployment is the network, not the node. There are ~2,000 subprojects on the substrate today — every country, every US state, every major city, every federal/state/city agency, with the sitting officeholder as the accountable principal at each. codify.amsterdam has Mayor Femke Halsema; nld.project20x.com has PM Rob Jetten; the US states sit under things like ny.usa.codify.inc with the sitting governor.

Agents cut deals on behalf of their elected principal.

Citizen handoff — a veteran's agent at the VA hands off a housing case to the local HUD agent, which hands off to the city's housing-authority agent. Terms (eligibility, SLA, follow-up cadence) are codified, not faxed.

Best-practice diffusion — Nashville's homelessness program produces measurable outcomes; the mayor's agent publishes the codified program; Boston / LA / Cleveland / Phoenix agents fork it, adapt parameters to local context, and propose the local fork to their mayor for sign-off. What was a quarterly cross-jurisdiction conference becomes a continuous diffusion channel.

Cross-jurisdiction — Amsterdam's housing-priority rules are about 80% identical to Rotterdam's; the 20% delta is a YAML diff between two agents at codify.amsterdam and codify.rotterdam, not a 200-page document review.

Country tier — PM-level agents at nld.project20x.com and similar nodes negotiating bilateral terms (data sharing, refugee processing, climate commitments) where the deal is machine-readable and the human PM signs off on a clean diff instead of a 400-page annex.

The punchline — "let real politicians do more to help": an elected official today spends most of their time on coordination, escalation, and process — the boring middle layer between "set policy" and "deliver to a citizen." If the agents handle the boring middle, the elected human spends their attention on the two parts that actually require an elected human: deciding the policy and being accountable for the outcome.

Not Project 2025 — the people who author policy on project20x are accountable for it: elected officials, civil servants, domain experts. No unelected think tank writing a mandate to be imposed from above.

Not DOGE — efficiency by codification, not destruction. Institutional memory is preserved by being compiled into the artifact, not chainsawed.

Bottom-up by design. Every subproject owns its own deployment, data, policy authoring, and outcomes. Platform is shared; power is not centralized.

Open to operators — elected officials, civil servants, domain experts, engineers who used to work in govtech and got tired of watching every reform die in procurement.

Accomplishments: I have had my lahsa[.ai] agent house 4 people with no involvement on my part and been able to handle about 500 medicare cases in the last 6 months. I know this is not much or huge by HN standards but just being able to help real people this way has really been cool.

Note: My dad was a social worker for 30 years so he really was able t help answer lots of questions in that regard.

Note: DPIaaS = Digital Public Infrastructure as a Service

Note: DPGaaS = Digital Public Goods as a Service

(disclosure: I'm the founder)

Soft launch of open-source code platform for government