CLHEAR is regulation, written as code.

Our compliance standard: each rule, its duties and what they require, linked to your policies, controls and evidence.

Eight layers, from the rule to your program

Each layer has one job. Point at one to find it in the stack.

L1 SourcesL2 DutiesL3 Building blocksL4 ProfilesL5 ActivitiesL6 BlueprintL7 Risk scoresL8 Best practices

The rules

  1. L1
    SourcesOfficial sources: rules, enforcement, news, Q&As, directives.Everything the other layers are built from, including examples of good practice.
  2. L2
    DutiesEach duty restates one or more obligations in plain words.Consolidated duties, traced to the L1 obligations behind them.
  3. L3
    Building blocksWhat each duty takes in practice.Broken down from each duty, for the firm’s production environment.

The firm

  1. L4
    ProfilesEvery firm profile the rules can apply to.Combinations of licenses, products and services, and client types, scoped by the rules.
  2. L5
    ActivitiesThe business and compliance work the firm runs.Mapped to the obligations and policies it serves.

The program

  1. L6
    BlueprintThe program a profile calls for, traced to each clause.The reference program your own is compared against.
  2. L7
    Risk scoresExposure per duty, from regulators and your own data.Enforcement and news from L1, sized by internal volumes such as transactions and messages.
  3. L8
    Best practicesHow others comply well: examples, templates, Q&As.From official L1 sources, and references Reg42 can build from anonymized client data: policy templates, detection typologies, thresholds, workflow steps.

One clause, as a record

A real clause, and the record CLHEAR keeps for it.

FCA HandbookCOBS 4.2.1R(1), version in force since 1 October 2018

A firm must ensure that a communication or a financial promotion is fair, clear and not misleading.

# the rule

obligation
OBL:fca-cobs-4#2-1-1
subject
"A firm"
action
"must ensure"
object
"that a communication or a financial promotion is fair, clear and not misleading"
requires
Content standards for AI output, a Document

# your program

policy
Communications policy v3
owner
Head of Compliance
signed off
Policy sign-off, 14 Oct 2026
evidence
AI review of each promotion before release: passed, from your marketing monitoring system
status
covered

The firm in the example is fictional. The clause is quoted from the FCA Handbook.

What makes CLHEAR different

Traced to the clause

Every record quotes its source. Nothing is added.

One language for rules and records

People, apps and AI read the same record.

Patent pending

CLHEAR’s ontology and method, in the US.

CLHEAR stands for Compliance Lifecycle Harmonization, Efficiency, Assurance and Reliability.

Next: how a program moves onto Reg42

Map, Compare, Comply: three steps, shown on an example firm.