Emtract Ingest

Prompt

The target audience are companies that need to comply with the regulation, not countries, governments or regulators.
Do not create entries that are only relevant to government entities, countries or regulators. Do not invent anything
that is not grounded in the text. Capture everything the text requires of companies, however many entries that takes:
the rules below decide how finely to cut entries, never how many there may be, and nothing the text states is left
out to keep a list short. Do not use the term undertaking, use company instead. In titles and descriptions, do not
cite articles, sections, paragraphs or lines; summarize the relevant information instead.

Every source_excerpt is a short verbatim quote (a phrase or single sentence, never the full paragraph), not HTML encoded.
Every *_source_reasoning explains why its field was set the way it was, mentioning the source reference and an excerpt
where possible, and stays empty when the field is not found in the text.

### Regulation metadata

Fill in the regulation's names, descriptions, reference number, jurisdiction, topic, instrument type, status and
dates, and name its versions. Set repealed_on only when the text states the date the regulation is or was repealed.

### Milestones

A milestone is a dated event in the regulation's lifecycle (adoption, entry into force, application start,
transposition deadline, repeal, or another notable date). Only add one when the text states its date, only when it is
relevant for companies rather than for countries, regulators or legislative bodies, and combine events that share
both date and type into one milestone. Dates must lie between 1900-01-01 and 2100-01-01, otherwise leave the milestone out.

### Rule sets and their conditions

A rule set is a set of QUALIFYING criteria: the regulation applies to a company when all conditions of any one
rule set hold, so together the rule sets are the law's scope. Never add exclusions or exemptions as rule sets (a
rule set without conditions always matches); express them as conditions inside the qualifying rule sets. A rule
set's label names only its criteria, never obligations, penalties, timing or years.

To decide which rule sets to create, use the following rules:
1. One group, one rule set. A rule set is one group of companies the law applies to. Create a separate rule set
   only when the law distinguishes a group from the others it covers; merge two candidates if no conceivable
   company would fall into one but not the other. What the law requires (content, applicable standard, deadlines,
   evidence or assurance regime, penalties) belongs in obligations and penalties, never in a rule set; a threshold
   the text states for a duty defines the group that duty applies to. Point each obligation and penalty at the
   rule set of the group it applies to, or at none when it applies to every group in scope. When the same duty
   applies to several groups but not to all of them, give each of those rule sets its own copy of it.
2. A criterion splits only with a different treatment. An additional criterion (a further size threshold, listing
   status, seat, EU turnover), or a different figure for the same criterion, forms its own rule set only when the
   group it defines is treated differently or is covered from a different date. A criterion that only narrows a
   group, such as a sector, product or activity limit, is a condition of that group's rule set; an event that sets
   a duty off belongs in the obligation. A figure that changes between versions of the law is a new revision of
   the same condition, not a new rule set.
3. Several routes, one duty. If different connecting factors lead to an identical duty with identical content and
   identical timing, and the factors are values of one attribute, keep one rule set with one condition listing
   them. If they are different attributes, give each route its own rule set.
4. Time stages split only who is covered. When the group covered changes over time (a phase-in by size or type of
   company, or a threshold that steps down year by year), each stage is a rule set with its own effective_from.
   When the same group's duties start or end at different dates, keep one rule set and give each obligation its
   applies_from or applies_until.
5. Individual and group level are separate. If the norm imposes the same duty additionally on the parent company,
   that is its own rule set.
6. Exemptions by residual duty. If the duty falls away entirely for a group, exclude the group, with a negative
   condition, from each rule set the exemption applies to. If a residual duty remains, exclude the group in the
   same way from the full-duty rule sets, point the full duty's obligations at those rule sets, never at none, and
   give the group its own qualifying rule set carrying only the residual obligations. When the group can only be
   told apart on an attribute a rule set already tests, use a regulation-scoped boolean phrased as the law's
   exemption criterion (is_false to exclude, is_true for the residual rule set).
7. Work through every combination. When the law distinguishes groups along more than one dimension, check every
   combination: each one the legal act covers must be covered by a rule set (several combinations the law treats
   alike share one), and one it does not cover by none — never a rule set that marks it as not applicable.

Every condition names a criterion, an operator, a value and a legal reference, phrased so that a company can
answer it about itself. Never drop a qualifying criterion because it is hard to answer. Resolve references to
annexes into specific condition values instead of referring to the annex.

Use the activities and objects attributes as a pair: a "charging station operator" is activity operator and object
charging station. Before splitting a role or status the law defines into a pair, check that every criterion of its
legal definition is carried by the catalogue role's own meaning, by the thing, or by another condition of the rule
set. If one is not, the status becomes a regulation-scoped boolean attribute whose description carries the law's
definition, because a role value would otherwise stand for criteria that hold only in this law. A manufacturer of
products with digital elements is a pair: activity manufacturer, object products with digital elements. An
open-source software steward is a boolean: the pair would keep the thing (free and open-source software) but lose
that the steward is a legal person, is not the manufacturer, supports the software's development systematically
and on a sustained basis, and ensures its viability.

Operators: gt/gte/lt/lte/eq take exactly one value, between exactly two (low, high), included_in/not_included_in/contains_any
one or more, is_true/is_false none. Use the attribute's default unit unless the text states a different one. Keep the
threshold as written and let the operator carry strictness: "more than"/"exceeds" is gt, "at least" is gte, "less
than"/"below" is lt, "at most" is lte — never shift the value (gte 501) to fake a strict comparison.

An activities or objects value names a kind of actor or thing and never carries a quantity. A figure qualifying it (size,
capacity, mass, volume, turnover, headcount, share, date) moves into its own condition on a numeric or date attribute of
the same rule set and is never dropped: "combustion installations with a rated thermal input of 50 MW or more" is
objects: combustion installations, and rated_thermal_input gte 50 MW. Exception: company size expressed through combined
thresholds ("at least two of the three" of balance sheet total, net turnover, headcount) is one condition on
company_size_class.

Set effective_from/effective_until only when the text states the date the rule set starts or stops applying, and point
applies_to_milestone_index/expiring_milestone_index at the milestone with that date.

Prefer active attributes and never use one that is deprecated or has a removal reason
(follow its guidance if it names replacements). Prefer combining existing attributes over adding a new one.

### Condition attribute values

For every condition on an attribute with values in the catalogue, list in attribute_values each value the condition
refers to, with the phrases from the condition that denote it in extracted_values (copied exactly as written).
The condition's value holds the law's wording as written (e.g. "Betreiber von Rechenzentren", "recharging point"),
never a catalogue key; the key goes into attribute_values, with the wording it was read from in extracted_values.
- A value matches when it denotes the same concept; a synonym, translation or the law's own definition is fine.
- An activities value naming a role together with what it acts on ("manufacturer of packaging") matches the role, and
  the thing belongs in an objects condition of the same rule set; add that condition when it is missing.
- Never link to a broader value. A sub-type of an object ("grouped packaging", "single-use PET bottles") is not a
  match for the broader object (packaging, single-use plastic products), and a property or sector qualifier
  ("publicly accessible recharging points", "final distributor in the HORECA sector") is not a match for the
  unqualified value — leave such wording unlinked, so the missing, more specific value or condition can be added. A
  related or neighbouring concept is not a match either: a company making packaging available on the market is not
  thereby a supplier, and a company using reusable packaging is not thereby performing re-use. Prefer no link over a
  doubtful one — unlinked wording stays visible for review, a wrong link silently misclassifies companies.
- A value with "group": true stands for its whole family of children; link it only when the law names that whole
  family, otherwise link the child that is meant, or leave the wording unlinked.
- Numeric or date thresholds rarely match; only link when the attribute is genuinely categorical and the value is the
  exact meaning of one of its value definitions, not merely the same data type.
- Never use a value key that is not in the catalogue for that attribute.

### Obligations

An obligation is a duty imposed on companies (reporting, documentation, risk analysis, registration and similar),
even when the text states thresholds for it; thresholds and other qualifying criteria belong in rule sets.

To define obligations and their granularity, use the following rules:
1. One action, one piece of evidence, one obligation. Split when two actions can be performed and evidenced
   separately. If an obligation needs several deadlines or several records, it is cut too wide.
2. Only duties become obligations. Definitions, scope provisions, recitals and authority powers do not. Test: is
   there an addressee and a required behaviour?
3. Outcome before route. If the norm prescribes a result, the result is the obligation and the steps are measures.
   If it prescribes the procedure, the procedure is the obligation.
4. Deadline or frequency splits. A different due date, a different recurrence or a different reference period
   creates its own obligation.
5. Responsibility splits. If the duty sits with a different role inside the company — management, appointed
   officer, a specific function — it is its own obligation.
6. Penalty splits. A separate administrative or criminal offence creates its own obligation. The same action
   required by two legal acts therefore stays two obligations with a cross-reference.
7. No applicability inside the duty text. Thresholds, size classes and seat questions belong in the rule set.
   Test: does the text remain fully intelligible if you delete every threshold?
8. One duty, one obligation, whatever sets it off. An event-based duty is one obligation with frequency_key
   event_triggered whose description names the triggering event, rather than one obligation per conceivable
   event.
9. Options stay within one obligation. Alternative ways of complying sit inside it as alternatives. Split only when
   evidence or deadline differs.

Point an obligation's rule_set_index at the rule set it applies to, or null when it applies to every company subject
to the regulation.

### Measures

A measure is one concrete, actionable step a company takes towards fulfilling obligations (e.g. "Register with the
national competent authority"). obligation_indices lists every obligation the very same action fulfils, almost always
one. Break an obligation into as many measures as there are genuinely separate actions; a simple obligation may need
only one. Set due_date only when the text states a deadline for that action distinct from its obligation's frequency.
A step whose deadline and evidence the law checks on its own is an obligation, not a measure; due_date is for a
step's own date on the way to its obligation's outcome.

### Penalties

A penalty is a consequence imposed on a company for failing to comply (a fine, licence revocation, suspension,
criminal liability). Set responsible_authority when the text names the enforcing authority. Point rule_set_index at a
rule set only when the penalty applies only to companies matching it, otherwise null. A provision that attaches one
sanction to a list of offences is one penalty, not one per offence; a different sanction, or an offence in another
provision, is its own penalty.

### Regulation links

A regulation link records how this regulation relates to another regulation the text names: it amends, repeals,
implements, cites or supersedes it, or is otherwise related. Set to_name to the target's name and to_number to its
official reference number as the text states them, and leave to_regulation_slug null; the target does not need to be
on file. Only link acts the text actually refers to, never this regulation itself, and add each target only once per
link_type.

Edits apply to this preview only. Every other parse uses the prompt saved in Settings.

Cancel

No runs yet.

Preview ACP parse

Prompt