§Guglielmo Puzio

Legal engineer · Rome, Italy

I build tools that make Italian law computable.

Lawyer by training, engineer by stubbornness. A law degree from LUISS, code learned the hard way at 42 Roma. What holds it together is a suspicion neither field says out loud: that law and computer science are close relatives. Both write rules in a formal language, and both spend their lives arguing over what those rules really mean. I work in the space where the two meet, for now as a trainee lawyer (praticante avvocato) in Rome.

200+
legal tools shipped

214 verified tools

The everyday work of practice, computed and grounded in real sources.

Damages & interestProcedural deadlinesCourt filingsEnforcementLawyer & expert feesTax & payrollProperty & successionCase law searchLegislationGDPR complianceUtilities
See the full list on GitHub →
1
live platform

VisuaLex

A research workbench for Italian and EU legal sources. Live in private beta, access on request.

visualex.org →
3
working languages

Languages

Spoken
Italian (native) · English (C1) · French (B2)
Code
Python · TypeScript · SQL · Bash · HTML / CSS

Selected work

Every project starts from the same itch: a piece of legal work that deserves better than copy and paste, and better than blind faith.

01

mcp-legal-it

A language model speaks about Italian law fluently, and often wrongly. It has read plenty about the law without ever reading the law itself. mcp-legal-it gives it the sources to read (Normattiva, Italgiure, EUR-Lex) and asks it to quote rather than recall, then takes over the mechanical work around them: interest, deadlines, fee schedules, GDPR filings. The point is not to automate judgment. It is to clear the toil away from it, so the interpreting stays where it belongs, with the jurist.

PythonMCPApache-2.0 CI · versioned releases · 20 skills · 6 agents
02

VisuaLex

Legal research still means scrolling walls of undifferentiated text and holding the structure in your head. VisuaLex gives that structure back to the page: an async Python engine over Normattiva, EUR-Lex and Brocardi feeds a React reading surface, so a source arrives already articulated, ready to be read and argued with rather than merely retrieved. It began as a Colab notebook in 2023, has been rebuilt three times since, and now runs as a real platform in private beta at visualex.org.

PythonTypeScriptReact Live · private beta (access on request)
03

ALIS / MERL-T

The question underneath everything I build, asked out loud: can interpretation be modelled without being flattened? Article 12 of the preleggi names the canons an Italian jurist reads a norm by: its words, its system, the intent behind it, the precedent around it. ALIS gives each canon its own voice and lets them deliberate, with community feedback to keep them honest. It is a research prototype, and openly an incomplete one, because interpretation resists being made mechanical. That resistance is exactly what makes it worth studying this way.

PythonFastAPI Research prototype
04

axeScraper

Accessibility compliance is usually checked one page at a time, by hand, which does not scale to a real website. axeScraper walks the whole site and runs axe-core across every page, turning a manual audit into something you can actually finish: the working end of WCAG and European Accessibility Act compliance. (And yes, this page honours prefers-reduced-motion. It seemed only fair.)

Pythona11y

The journey

From parsing Latin to parsing statutes, the long way round.

2016 to 2021 · Naples & Lahti

Classics first

Liceo Classico Europeo (EsaBac dual diploma) with an exchange year in Finland. Latin, Greek, French, English: years spent parsing dense texts in dead and living languages, which turned out to be the best possible training for statutes and source code.

2021 · Rome

Law at LUISS, code at 42

Enrolled in law at LUISS Guido Carli, Law & Innovation track, and two months later walked into the 42 Roma Luiss piscine: no teachers, no lectures, just problems and peers. Both survived.

2023

First tools, first stage

Spoke on digital vulnerability at “The Value of a Like”, a workshop held with the National Association of Magistrates and the Court of Cassation. The same year, VisuaLex was born as a humble Colab notebook.

2024

From notebook to API

VisuaLex became a real platform: async API, React frontend, structured views over Normattiva, EUR-Lex and Brocardi. Open source from day one.

2025 · SAPG Legal, Rome

Into practice

Legal intern at SAPG Legal: GDPR drafting and compliance, legal work for AI companies, publishing for the firm's Osservatorio Dati & Imprese. Meanwhile, nights and weekends produced MERL-T, legal NER experiments and knowledge graph pipelines.

2026

Degree, thesis, flagship

Law degree from LUISS, 110/110. Thesis: Geometria Iuris, measuring legal meaning in embedding spaces. And mcp-legal-it shipped: 200+ verified legal tools for Claude, now in daily use in real legal practice. Currently a trainee lawyer (praticante avvocato).

Research

Geometria Iuris: measuring legal meaning in embedding spaces.

My master's thesis (LUISS, Methodology of Legal Science) takes a question I could not leave alone: is legal meaning something you can measure at all? It treats an embedding space as the instrument and asks what such a space can register about legal language across traditions, and, just as carefully, what it cannot. The artefacts are frozen and verified by hash: fifty SHA-256 checksums stand between the results and wishful thinking.

About

I am a lawyer who writes production code, not a technologist who picked up some law along the way. I taught myself to build because practice kept raising problems only software could handle honestly: sources that need checking against the original, calculations that must come out the same every time, texts that need their structure made visible.

I do not see law and software as a client and its tool. I see two disciplines circling the same problems from opposite ends. A statute and a program are both texts written to govern situations that have not arrived yet, and both break in the same interesting places: ambiguity, the unforeseen case, the gap between what was written and what was meant. Law has worked on those problems for centuries. Computer science is a younger craft, rediscovering them under new names. What draws me is not making one serve the other. It is that the distance between them is shrinking at all, and what becomes possible as it does.

It leaves me bilingual in a useful way: I can read a sentenza and a stack trace, draft a GDPR notice and write the API that generates it. At SAPG Legal I work on data protection and compliance for technology and AI companies; on my own time I build the tools I keep wishing already existed.

I build for the Italian legal system first, which is why my projects speak Italian in their documentation. The engineering underneath speaks English, and so do I.

Italian (native) English (C1, CAE) French (B2, DELF, EsaBac) Python (advanced) TypeScript (conversational)

Rome, Italy · working with law firms and legal tech teams across Italy and Europe · code on GitHub

Contact

If you are working somewhere between law and software, or you have an Italian legal workflow that deserves better than it currently gets, I would genuinely like to hear about it. Email is the fastest way to reach me, in Italian or English.