# What is a regulatory digital twin?

> A regulatory digital twin is a continuously maintained, computable representation of a regulatory environment: the legislation, guidance, standards and organisational policies that apply, the concepts they share, the systems and evidence they govern, and the rules that connect them. It can be queried, tested against scenarios and updated when regulation changes, so the downstream impact of a change becomes discoverable rather than discovered.

Canonical: https://sireto.com/regulatory-digital-twins

## What a regulatory digital twin connects

- Legislation and regulation, with versions and dates of application.
- Regulatory guidance and standards that interpret or operationalise them.
- Organisational policies, procedures and controls.
- Domain concepts shared across all of the above.
- Operational systems and the data they hold.
- Compliance evidence and its provenance.
- Software agents and the constraints they must respect.

## What you can do with one

Because the twin is computable, questions that used to take weeks of analysis become queries.

- Impact analysis: when an article changes, which rules, policies, controls and systems are affected?
- Scenario testing: does this planned process or product satisfy the applicable requirements?
- Coverage: which obligations have no corresponding control or evidence?
- Regulatory change management: track amendments and re-evaluate automatically.
- Decision support: answer with a reasoning path back to the source provision.

## How regulatory digital twins relate to NormLogic

NormLogic builds the layers a regulatory digital twin needs: structured sources, regulatory knowledge graphs, formal rules and provenance. Connecting those layers to an organisation’s policies, systems and evidence produces a twin of its regulatory environment that can be kept current as regulation evolves.

## Frequently asked questions

### How is a regulatory digital twin different from a compliance management system?

A compliance management system tracks tasks, documents and attestations. A regulatory digital twin models the regulation itself as computable knowledge, connected to those documents and systems, so it can answer what applies, what changed and what is affected.

### Does a regulatory digital twin need all regulation modelled before it is useful?

No. Twins are built incrementally, usually starting with one regulation and the policies and controls it governs. Each addition increases the questions the twin can answer.

### Who maintains a regulatory digital twin?

Compliance and legal teams own the interpretations; engineering owns the integration; the platform tracks regulatory change and flags what needs review. The provenance layer records who decided what, and on which basis.

## Related

- [What is machine-executable regulation?](https://sireto.com/machine-executable-regulation)
- [What is automated regulatory compliance?](https://sireto.com/automated-regulatory-compliance)
- [What is Regulatory Engineering?](https://sireto.com/regulatory-engineering)
- [NormLogic](https://sireto.com/normlogic)
