enriquelop
Joined 7 months ago
Joined 7 months ago
Many of you asked if the code is shared. It is now: https://github.com/legalize-dev
The pipeline is multi-country by design. France already works as a second country (Légifrance data). Adding a new country means implementing 4 Python interfaces for your national gazette. The rest (markdown, git, web, API) is generic.
I wrote a guide for contributors who want to add their country: https://github.com/legalize-dev/legalize-pipeline/blob/main/...
From this thread alone, people asked about Germany, Portugal, Sweden, Finland, Netherlands, and Brazil. If you know your country's open data source for legislation, a PR is the best way to help.
I'll be honest — I don't know how much time I'll be able to dedicate to this, but I'd love to build something big. Legislation is massive and scaling to more countries takes real infrastructure. I'm setting up an Open Collective to fund hosting and development: https://opencollective.com/legalize
Live site with browsable laws + diffs: https://legalize.dev
Everything is still very precarious, time to time.
Thank you
The idea: legislation is just patches on patches on patches. Git already solves this. Instead of reading "strike paragraph 3 and replace with...", you get an actual diff.
The repo is the product. Browse any law, git log to see its full reform history, git diff to see exactly what changed.
Built the pipeline in ~4 hours with Claude Code. Source is BOE (Spain's official gazette) consolidated legislation API.
Exploring whether there's a business here — structured legislation API for legaltech/compliance, or just a useful open dataset. Curious what HN would build with this data.
The new AI policy says:
"It is not allowed to use generative AI for producing artefacts of any kind, including code, design, and documentation."
I get the point about not filling the proposals with AI to force us to at least write them ourselves, but is there anyone nowadays who doesn't use AI for programming?
Weird, isn't it?