Research briefs

A close reading of the source. A practical question for the product team. Explore the collection by subject.

6 briefs · Individual source-review dates shown below

Licensing

What does a licence actually cover?

A jurisdiction is a starting point. The useful question is which activity, entity and market an authorisation covers.

Last checked · 6 min

Technical operations

Build a record you can explain

Connect a customer event to its source, decision and version. Keep access-to-history rules separate from retention policy.

Last checked · 6 min

Software provenance

Trace the software. Keep the evidence.

Follow the documents that connect a software release to its origin, test scope and accountable parties.

Last checked · 7 min

Reading regulatory sources

A document is not a duty

The publisher’s name is only the first check. Document type, legal status and a precise scope determine what a statement can support.

Last checked · 8 min

Document control

Read the change, not just the date

An announcement date, a version label and an effective date answer different questions. Keep the trail and record the gaps.

Last checked · 8 min

Read with the right expectations

These are research briefs, not breaking news or a legal checklist. The date beside each entry is the date its cited sources were read for this edition. It does not mean every related instrument was checked, or that the wording will remain unchanged.

For a specific passage, follow the source notes at the end of the brief. The document matrix records a narrower set of source-backed statements and distinguishes requirements from context. Our methodology describes how missing effective dates, version uncertainty and corrections are handled.