Building auditable regulatory reference data: from legal text to versioned CSV
Regulatory information becomes hard to use the moment it is reduced to an isolated answer. A date, threshold, or obligation may be technically correct today, yet unusable tomorrow if nobody can see its source, scope, or update rule.
A more reliable approach is to treat regulatory guidance as small, maintained reference data. The goal is not to automate legal judgment. It is to make the underlying rules inspectable, versioned, and easy to reuse.
Start with a decision, not a document
The first useful question is rarely “what does the law say?” It is usually “what action must happen, for whom, and when?”
