Regingada
Playbooks

Three playbooks, fully readable

Deliverable · Source: Funk corpus (CELEX/ELI-anchored) · Status: 2026-08

Every playbook here is a working document from the deliverables pipeline: the same machinery the suite uses to assemble a memo, laid out on a page and readable from first line to last. No form in front of it, no gate, no teaser extract — the whole document is on the page.

Curated for orientation. Not legal advice, not a legal assessment of your case.

Everything is readable right here — no email required. Use Save as PDF on each playbook to take it with you.

The playbooks

One corpus, three questions people actually ask

The three playbooks answer the three questions that arrive first: who has to be appointed where, where the acts rub against each other, and which role a company is even in. Each one is drawn from the same anchored corpus, and each one names its sources.

  • Appointment duties · non-EU providers

    EU Representative Compass

    Which appointment duty a non-EU provider triggers in which regime — five functions that do not substitute for one another. The compass sets them side by side: legal basis, addressee, seat requirement, and what the appointed person actually has to be able to do.

    • GDPR Art. 27 · DSA Art. 13
    • AI Act Art. 22/54
    • NIS2 · Data Act
    Read the playbook →
  • Seams · seven legal acts

    Cross-Regulation Collision Map

    Eight seams at which EU digital acts meet — including the three unrelated Articles 22. Each entry names the two provisions, what actually collides, and which reading order keeps two workstreams from collapsing into one wrong one.

    • 8 collisions
    • 7 legal acts
    Read the playbook →
  • Roles · AI Act

    AI Act Role Quick-Check

    Provider, deployer, importer, distributor, authorised representative: five questions that settle the role before anyone starts counting obligations. Plus Art. 25 — the reversal that turns a deployer into a provider without a single line of code changing hands.

    • 5 roles
    • Art. 25 trap
    Read the playbook →
Provenance

Where the playbooks come from

A playbook is not an essay. It is generated from the same corpus the suite works on, and it keeps the document ledger that every deliverable carries: source, coverage, method, status, review, distribution.

Document ledger

Field Entry
SourceFunk corpus — obligation and definition nodes anchored to CELEX and ELI identifiers, so every statement can be read back to a norm text.
CoverageThe EU digital-law acts carried in the corpus, among them the GDPR, the DSA, the AI Act, the DMA, NIS2, the Data Act and the Data Governance Act.
MethodAssembled with the Regingada deliverables pipeline and then curated by hand — the machine proposes the structure, a human decides what stays.
Status2026-08. A playbook carries no signature and no individual assessment; it is a structured starting point.
DistributionReadable on the page. A print stylesheet turns each playbook into a paper or PDF document via the browser; no download and no email are required.

Articles appear in these playbooks because a fact pattern of that shape reaches them — not because a lawyer has found that they apply to you. Which of them actually bite in a concrete company is an assessment, and an assessment is a mandate.

How to read them

What a playbook is — and what it is not

What it is

An orientation document: a map of what a question of that shape reaches in EU digital law, with the provisions named and the traps marked. It is meant to be read before the first meeting, so that the meeting can start one level higher.

What it is not

Not legal advice, not a finding, not a statement about your company. There are no client names, no figures on results and no claim that following a playbook settles anything. Individual-case advice comes from the law firm Theo Funk under a separate mandate.

Next step

From a general playbook to your own footprint

A playbook is written for a shape of question, not for your company. When you want your own footprint instead of a general one, the pre-wizard takes five questions and the suite builds the map from your answers. Everything it then produces is orientation — the legal assessment of it stays with the firm, in a mandate.

Estimate the coordination load of your footprint →
What shipped behind these playbooks → Changelog

Worked profiles: the five model cases. Non-EU providers should also read the overview of EU representation.

Disclaimer

Orientation, not legal advice

These playbooks and the suite provide orientation and information only. They are not legal advice. Individual-case advice is provided exclusively by the law firm Theo Funk under a separate mandate. Regingada UG (haftungsbeschränkt) — the software company and appointed EU representative — and the law firm are strictly separated.