Appearance
Regulatory Changes
Where to find it: Regulatory Compliance, then Regulatory Changes (/reg-intel/changes).
The change feed is where detection becomes decision. Every event in it is waiting for a person to say what it means.
What an event contains
| Element | Description |
|---|---|
| Source | Which registered source produced it |
| Authority | The publishing body |
| Detected at | When the sweep found it |
| Summary | An AI-generated description of what appears to have changed |
| Classification | An AI-suggested category for the update |
| Triage state | Untriaged, accepted or dismissed |
| Triage record | Who triaged it, when, and with what reason |
The summary is advisory
The AI summary describes what the model read. It is a reading aid for prioritising a queue, not a legal analysis, and it has no authority over what you decide. Always open the underlying publication before accepting or dismissing anything material.
The triage decision
You are answering one question: does this change our obligations?
| Decision | When | What happens |
|---|---|---|
| Accept | The change is in perimeter and creates, amends or clarifies obligations | The event can be sent to Smart Extract to produce candidate requirements |
| Dismiss | The change is out of perimeter, purely administrative, or already covered | The event is retained with your reason recorded |
Dismissal is not deletion. A dismissed event with a clear reason is a durable record that your function considered a publication and consciously concluded it did not apply — which is exactly what a supervisor asks for when testing horizon-scanning.
How to triage an event
- Open Regulatory Changes. Untriaged events appear first.
- Read the summary, then open the source publication and read the relevant part.
- Decide whether obligations are affected.
- Select Accept or Dismiss and record your reason. Be specific: "Applies only to insurance undertakings; the group holds no insurance licence" is useful in a year's time. "Not relevant" is not.
- For accepted events, choose Send to Extract to move the text into Smart Extract.
Requires reg_intel.triage.
What happens after acceptance
Accepting an event does not create requirements. It moves the material into extraction, where:
- AI proposes candidate requirements with the source text each came from.
- A person reviews every candidate.
- The person publishes, edits, merges or rejects each one.
- Published candidates become requirements in the library.
Only at step 4 does anything enter your obligation set. See The Requirement Pipeline.
Good triage practice
Triage on a rhythm, not on impulse. A short daily or twice-weekly pass keeps the queue honest. A monthly binge produces shallow reasons.
Write reasons for your successor. The person reading your dismissal reason will not have the context you have today.
Escalate genuine ambiguity. If it is unclear whether a change binds you, that uncertainty is itself worth recording — dismiss with a reason that names the ambiguity, or accept and let the requirement's applicability decision carry the judgement with its own approval trail.
Do not use dismissal to manage volume. If the queue is unmanageable, the problem is source selection, not triage.
Permissions
| Action | Permission |
|---|---|
| View the change feed | reg_intel.read |
| Accept or dismiss an event | reg_intel.triage |
| Send an accepted event to extraction | reg_intel.triage plus library.smart_extract |
Example
A sweep detects an updated outsourcing circular. The AI summary reads: "Appears to amend notification thresholds for material outsourcing arrangements and introduces a 30-day pre-notification requirement."
The Compliance Analyst opens the circular. The summary is broadly right, but the analyst also notices a transitional provision the summary did not mention, giving existing arrangements six months to comply.
The analyst accepts the event with the reason: "Amends material outsourcing notification thresholds and adds 30-day pre-notification. Transitional provision gives existing arrangements until the stated date. Sending to extraction; transitional deadline to be captured as a requirement deadline."
That reason does three things: it justifies acceptance, it records a fact the AI missed, and it tells the next person what to look for.
Troubleshooting
"An event has no summary." AI classification is advisory and can be unavailable — for example when the AI entitlement is off, or the publication could not be read. The event is still fully triageable; you simply read the source yourself.
"Send to Extract is unavailable." You need library.smart_extract in addition to triage rights, and the compliance core entitlement must be enabled.
"I want to see dismissed events." Use the include-dismissed option in the feed. Nothing is removed.