The QRRegistry compliance library exists for one kind of reader: an EU manufacturer or procurement reviewer who has decided that the regulation applies to them and now needs a plain answer to a specific question. It is not a feed, a newsletter, or a stream of opinion. Every entry is anchored to a published regulation, dated to its last review, and indexed by the sector and regulation it actually concerns.
What you’ll find here
Articles in this library answer questions of the shape “how does regulation X apply to product class Y?” — the kind of question a manufacturer types into a search bar after the first procurement reviewer asks for the digital product passport, not before. We organise entries by regulation (ESPR, the Construction Products Regulation, the Battery Regulation, the Tyre Labelling Regulation) and cross-list them by sector. The index does not order entries by date because a knowledge base is not a chronology — the date that matters is the last-reviewed date inside each article, which tells a reader whether the answer is current.
The editorial standards
Every article in this library passes the same gates before it ships:
- Anchored. The article cites the specific article and paragraph of the regulation, with a permalink to the EUR-Lex source text. A reader who disagrees with our reading can check ours against the source in one click.
- Dated. The frontmatter carries a
last_revieweddate that surfaces inside the article. When the regulation changes — a delegated act drops, a guidance note is published, a court reads a clause differently — the affected articles are revisited, the date is bumped, and the change is visible in the git history. - Sectoral. Each article names the product sector it applies to, and the call-to-action at the bottom links to the workspace for exactly that sector. A textile manufacturer reading a textile article does not get pushed into a battery workflow.
- Bylined. The author’s name appears inside the article. The byline is the part of the article that stakes a reputation on the analysis. Anonymous reference notes invite low-quality writing; bylines anchor it.
- Editorially gated. Every article must clear a minimum word count, a minimum title length, a minimum summary length, and a strict frontmatter schema before it loads at all. A malformed article fails app boot, not just CI. This sounds rigid; it is. A knowledge base with one weak entry degrades the whole archive in a way a blog never does.
What you won’t find here
We don’t run a comments section. We don’t show a “related posts” sidebar — the regulation grouping in the index does that work without chrome. We don’t track engagement past the analytics already published on /privacy (a coarse country code and device class, no cookies, no fingerprinting). We don’t sell a newsletter. We don’t add posts to maintain a posting cadence; we add articles when the regulation gives us something honest to say. Above all, we don’t translate the prose with a language model. Compliance writing has too narrow a margin for translation error — when an article ships in German, French, or Italian, a human translator was paid to produce it.
How the library evolves
Articles ship one at a time, each as its own commit, each reviewed by the author whose byline it carries. When a regulation moves — a CIRPASS-2 working document lands a new mapping, the Commission publishes a delegated act, a national authority issues guidance — the affected articles are revisited and the last_reviewed date is bumped. The git history of app/content/library/ is the long-term record of what changed when, which is the same standard the underlying regulations themselves are held to.
Who writes here
For now the library is small and the bylines are few. Each contributor brings a load-bearing competence to the topic they cover — not a generalist take, not a rephrasing of someone else’s analysis. Where a contributor’s background bears on credibility (an aviation-industry track record on permanent record retention, for example), the byline notes it inline. Where it doesn’t, the byline keeps to the name and the article does the work.
How to use this library
If you arrived here from a search engine, the article you landed on is the one we wrote for the question you asked. If you arrived from the footer link, the index page groups every article by regulation — start with the regulation that governs your product. Either path leads to the same answer. The CTA at the bottom of every article points to the workspace for the sector the article concerns; you can ignore it and still take the analysis with you.
If you have a question we haven’t written about, the contact form on every page is the right place. We track the questions that come up more than once, and the ones that come up most become the next articles.