Founder letterDon’t Panic. Regulation is Cool.

Vertical AI for financial compliance

Know what you owe.Prove what you do.

Reg42 is building the compliance context graph: the rules you owe, joined to the records of what you do, inside your own cloud, so every answer comes with its source, owner and evidence.

What we are building

The data layer

Context graph

What you owe, joined to what you do: Reg42’s encoded rules, written in CLHEAR, an open language, designed to link to your policies, controls, owners and evidence.

See the graph
The AI interface

Solon

Equips frontier models, Claude included, with your firm’s context graph. Designed to run in your own cloud account, with the trail behind every answer.

Ask Solon
The vision

Reg42 OS

A vertical AI operating system designed to run the whole compliance program on the graph, with guardrails and an audit trail, in your cloud.

See Reg42 OS
Reg42 OS · your cloud account SIMULATED

Example Markets · a fictional global broker

What would you like to know about AI conformance in the US?

Ask Solon about the example firm…
Blueprint · US · FINRARequiredIn place
2210(b)(1)(A)2210(d)(1)(A)3110(b)(4)17a-4(b)(4)3110(b)(1)
Principal approval of AI-drafted postsMismatch
Content standards for AI outputCovered
Review of chatbot answersGap
Chatbot transcript recordsCovered
Procedures for AI toolsGap
The story

One firm. One domain. Nine steps.

How Reg42 is designed to work. Follow Example Markets, a fictional global broker, from its own records to a plan that closes each gap in AI conformance. Switch between the US, UK and EU at any time.

Example Markets · AI conformance in the US
Act I · Chapters 1 and 2

Map.

Connect the records you own, and ask what happens today.

01Where do I start?

Start with your own records.

Connect the records compliance already owns: policies, controls, committee minutes, owners and evidence. Inside your cloud account, they become the first layer of your context graph.

Your records · Example MarketsContext graph
DocumentsDocument store
SystemsSupport platform
Data feedsTeam chat archive
DocumentsShared drive
Communications standards v5Document · Head of Compliance
Chat transcripts, archived dailySystem · Head of Client Services
Approvals in team chatProcess · Head of Marketing
Legacy prompt spreadsheetAsset · Marketing team

Connected inside your cloud account, each record with its owner. No rules are applied yet.

Picture: the example firm's systems, such as its document store and support platform, connected to the records compliance owns, each with its kind and owner.

02What happens today?

Ask what happens today, and see the source.

Solon is designed to answer from your connected records, with the source, owner and evidence behind each answer. Gaps and tasks come next, once the rules are added.

Solon · Example MarketsYour records
Which controls cover our AI use cases today?

Three records cover them today. The communications standards v5 cover AI-drafted posts and chatbot answers, the support platform archives every chatbot conversation each day, and the Head of Marketing approves each post in team chat before it goes out.

SourceCommunications standards v5 · Document storeChat transcripts · Support platformApprovals · Team chat archive
OwnerHead of ComplianceHead of Client ServicesHead of Marketing
EvidenceArchive capture, 19 Oct 2026Approval message, 16 Oct 2026
GapsTasksNext, once the rules are added

Picture: a question to Solon about which controls cover the firm's AI use cases today, answered with its sources, owners and evidence.

Act II · Chapters 3 to 6

Compare.

Add the rules, describe your firm, and see each gap.

03Which rules apply?

Add the rules, clause by clause.

Reg42’s encoded rules are designed to keep each official text verbatim, clause by clause, with its source and date. Start with one jurisdiction.

SourcesL1
FINRA Rule 2210

Communications with the Public

FINRA Rules · Version in force since 16 August 2019
2210(d)(1)(B), first sentence

“No member may make any false, exaggerated, unwarranted, promissory or misleading statement or claim in any communication.”

Kept verbatim, with a copy stored for citation

Picture: a shelf of the three jurisdictions in the story with the selected one pulled out, showing its official reference, its date and the verbatim text of one clause.

04What makes them apply to us?

Describe your firm in CLHEAR.

Countries, licenses, products, clients, channels and AI use cases. These facts decide which obligations apply.

Profile · Example MarketsL4
Countriesjurisdictions
United States
Licensesauthorisations
FINRA member broker-dealer
Productsproducts
StocksETFs
Clientscustomer_base
Retail
Channelschannels
Mobile appSocial media
AI use casesai_use_cases
In-house support chatbotAI-drafted marketing posts

Only these facts decide which obligations apply. Controls, owners and evidence stay in your systems.

Picture: the example firm's profile, with its countries, licenses, products, clients, channels and AI use cases lighting up as they are chosen.

05What do the rules require of us?

The program you should have, traced to each clause.

Reg42 lists what your firm must have, written in CLHEAR: policies, roles, systems and processes. This is your reference blueprint, and every item links back to its clause.

Reference blueprint · US · FINRAL6
2210(b)(1)(A)A principal approves each retail communication before use
2210(d)(1)(A)Keep communications fair and balanced
3110(b)(4)Review correspondence with customers
17a-4(b)(4)Keep the communications sent and received
3110(b)(1)Keep written supervisory procedures
Principal approval of AI-drafted postsProcess · 2210(b)(1)(A)
Content standards for AI outputDocument · 2210(d)(1)(A)
Review of chatbot answersProcess · 3110(b)(4)
Chatbot transcript recordsSystem · 17a-4(b)(4)
Procedures for AI toolsDocument · 3110(b)(1)
What the rule requires

Picture: the reference blueprint. Each required item is drawn with a dashed periwinkle outline and linked to the clause it comes from.

06Where are we short?

Each gap, item by item, with the reason.

Your records are matched against the reference blueprint. Covered items fill in, gaps stay open, and mismatches and extras are marked.

Gap analysis · US · FINRARules × your records
2 covered2 gaps1 mismatch1 surplus
Principal approval of AI-drafted posts2210(b)(1)(A) · Approved in chat by marketing, not by a registered principalMismatch
Content standards for AI output2210(d)(1)(A) · Cover AI-drafted posts and chatbot answersCovered
Review of chatbot answers3110(b)(4) · No one reviews what the chatbot sendsGap
Chatbot transcript records17a-4(b)(4) · Every conversation keptCovered
Procedures for AI tools3110(b)(1) · Procedures do not cover AI toolsGap
Legacy prompt spreadsheetNot traced to any clauseSurplus

Picture: the firm's records matched against the reference blueprint. Covered items are filled, gaps stay empty, and the mismatch and the surplus item are marked, each with its reason.

Act III · Chapters 7 to 9

Comply.

Close each gap, keep the decision trace, and stay current.

07What do we do next?

A plan to close each gap, with your tools or Reg42 OS.

Each gap becomes a task with an owner across the three lines of defense: use an existing tool, generate a document, assign a role, install an app or run a workflow.

Action plan · US · FINRA4 tasks
1st line · the business2nd line · compliance3rd line · independent review
Generate a documentAdd AI tools to the supervisory proceduresGapProcedures for AI tools · 3110(b)(1)HCHead of Compliance2nd line
Install an appRoute every AI-drafted post to a registered principalMismatchPrincipal approval of AI-drafted posts · 2210(b)(1)(A)HMHead of Marketing1st line
Install an appInstall a daily review of chatbot answersGapReview of chatbot answers · 3110(b)(4)CSHead of Client Services1st line
Assign a roleName an independent reviewerGapProcedures for AI tools · 3110(b)(1)IAInternal Audit3rd line

Picture: the action plan. Each gap becomes a task with an action type, an owner and a line of defense.

08How do we show it’s done?

Every approval, kept as a decision trace.

Evidence flows back onto the item it proves. Each approval is kept as a decision trace: who decided, on what, and why.

Evidence · Principal approval of AI-drafted postsDecision trace
Principal approval of AI-drafted postsProcess · 2210(b)(1)(A)MismatchCovered
From production
  • Post approved before useAI post review app · 22 Oct 2026
  • Approver and date archivedSocial media archive · 22 Oct 2026
  • Next procedures review bookedWorkflow · Jan 2027
Route every AI-drafted post to a registered principalDoneHMHead of Marketing
  1. Solon checked the draftWhy: against 2210(d)(1)(A)
  2. Registered principal approved itWhy: fair and balanced, before first use

Picture: evidence arriving onto one item, which turns covered, while its task moves to done and the decision trace records who approved it and why.

Interlude · Solon

Ask the example firm.

Frontier models, equipped with context. Ask the example firm a question, and the answer arrives with the obligations, items, evidence and clauses behind it.

  • In your cloud. Solon is designed to run in your cloud account, next to your data, and to use frontier models, Claude included, through your own cloud provider.
  • Grounded in your graph. Obligations, blueprint items, evidence and clauses, all linked.
  • Built to be measured. The goals, against the same model without the graph: more accurate, lower cost, with history, every action traced and linked to evidence. Each goal will be measured by evals on the firm’s own tasks.
Solon · Example MarketsSIMULATED
What do FINRA and SEC rules require of our AI tools?
  1. Reading the firm profile
  2. Resolving the obligations that apply
  3. Walking the blueprint graph
  4. Checking evidence and clauses

FINRA’s rules apply to AI-drafted posts and chatbot answers as they do to any communication, and the firm is responsible for their content. A registered principal must approve each marketing post before use, every communication must be fair and balanced, and the chatbot’s answers must be supervised like other communications. SEC rules require every conversation to be kept, and written procedures must cover the AI tools.

ObligationsApprove each retail communication before useKeep communications fair and balancedReview correspondence with customersKeep the communications sent and receivedKeep written supervisory procedures
Blueprint itemsPrincipal approval of AI-drafted posts MismatchContent standards for AI output CoveredReview of chatbot answers GapChatbot transcript records CoveredProcedures for AI tools Gap
EvidenceNone yet
ClausesFINRA Rule 2210(b)(1)(A)FINRA Rule 2210(d)(1)(A)FINRA Rule 3110(b)(4)SEA Rule 17a-4(b)(4)FINRA Rule 3110(b)(1)Rule 2210 FAQs B.4 and D.8

A replay on a fictional firm with simulated data. It is an example, not a live client.

09What happens when the rule changes?

When the rule changes, see exactly what changes for you.

A changed clause travels up through the blueprint to the one task it affects, with a named owner.

Change feed · US · FINRAWatched
  1. 1Clause changes SIMULATEDFINRA Rule 2210(d)(1)(A)Amendment published
  2. 2Obligation updatesKeep communications fair and balancedOBL:finra-2210#d-1-a
  3. 3Item flaggedContent standards for AI outputNeeds new wording
  4. 4Task createdUpdate the content standardsHCHead of Compliance

Picture: a change feed. A clause change updates an obligation, flags one blueprint item, and creates one task for a named owner.

Zoom out

Start with one. Add the next on the same path.

Each jurisdiction adds its blueprint, and the blueprints join into one AI conformance program. An item that serves more than one rule appears once.

One program, one domain at a time.

Become a design partner
The data layer

The compliance context graph.

What you owe, joined to what you do. Point solutions cover a few tasks, AI knowledge tools search files, and none joins the whole program. The context graph is designed to link each rule to the policies, controls, owners and evidence that meet it.

Inside your cloud account
What you owe Reg42’s encoded rules, in CLHEAR
  • Laws
  • Regulations
  • Standards
  • Guidance
  • Official Q&As
  • Historical enforcement
  • News
What you do Your records
  • Policies
  • Controls
  • Committee minutes
  • Issues and findings
  • Roles and owners
  • Pending tasks
  • Evidence
Compliance context graphSolon answers and acts on it

Designed so every answer comes with its source, owner and evidence.

CLHEAR · an open language for Regulation as Code

One open language for compliance data.

CLHEAR is an open language for writing regulations as code: the exact words of the rules, the duties inside them, and the roles, documents, systems and processes each duty requires, every line traced to its clause. We will publish it as a spec anyone can read and implement. Reg42 encodes the rules and keeps them current, and Reg42 OS is designed to run them inside your cloud.

L1 SourcesL2 ObligationsL3 Building blocksL4 ProfilesL5 ActivitiesL6 BlueprintL7 PrioritiesL8 Benchmarks
  1. L1SourcesOfficial texts, split into clauses and kept verbatim with their date.
  2. L2ObligationsWho must do what, pinned to the clause it comes from.
  3. L3Building blocksWhat a firm must have: documents, roles, committees, systems, processes, workflows and assets.
  4. L4ProfilesCountries, licenses, products, clients and channels, and which obligations reach each profile.
  5. L5ActivitiesWhat the firm does, linked to the obligations that govern it.
  6. L6BlueprintThe leanest complete program for one profile, with an evidence chain for each item.
  7. L7PrioritiesEach obligation scored by how often and how hard regulators act on it.
  8. L8BenchmarksHow a program compares with what regulators found in examinations.

One evidence chain, end to end.

An example from the story, traced from a blueprint item to the words of the law. The digest lets anyone check the clause text.

Blueprint itemPrincipal approval of AI-drafted postsProcess · owned by the Head of MarketingBLK-PRINCIPAL-APPROVAL
ObligationApprove each retail communication before useApplies to members that use retail communicationsOBL:finra-2210#b-1-a
ClauseFINRA Rule 2210(b)(1)(A)An appropriately qualified registered principal of the member must approve each retail communication before the earlier of its use or filing with FINRA's Advertising Regulation Department ("Department").
SourceFINRA Rule 2210FINRA Rules · Version in force since 16 August 2019
sha256 3abfe13f6421…a98ede1f

Open language. To be published as a spec, free to use.

Reg42 content. Rules encoded, kept current and reviewed.

Your graph, your data. Designed to be exported in CLHEAR at any time.

Reg42 OS · the vision

A vertical AI operating system to run the whole compliance program.

Reg42 OS is designed to run the program on the context graph, with guardrails and an audit trail, in your own cloud: Reg42’s encoded rules, your data, your existing tools and your people, in one place.

Official regulatory sourcesLaws, regulations and standards
Signed Reg42 rule releasesVerified before they go live
Your cloud account
Reg42 OSYour program, gaps, plans, workflows and evidence.
Reg42 engineEncodes the rules in CLHEAR and builds the reference blueprint.
Your data feedsOrders, documents, people and communications.
SolonEquips frontier models with your context, from your environment.
Apps and agentsJobs that read the blueprint and write evidence back.

Only official sources and signed releases come in. Your data stays inside.

Actual blueprintBuilt from your data feeds and what people enter.
Gap analysisWritten in CLHEAR, item by item.
Action plansEach gap becomes work with an owner.
WorkflowsProcesses across the three lines of defense.
Apps and agents storeInstall the jobs your plan calls for.
Document generationDrafts that start from the items you are missing.
Evidence and audit trailWhat ran, who approved it, and why.
Engine updatesVerified, tested and approved before they go live.

PLANNEDBuild: design partners will be able to assemble an app from the blueprint.

Apps and agents, working on the blueprint.

Examples on the fictional firm, once its plan is in place.

App
AI post review
WATCHES
New AI-drafted posts
RUNS
On each new draft
READS
Marketing standards
SERVES
FINRA Rule 2210(b)(1)(A), 2210(d)(1)(A)
Agent
Chatbot transcript review
WATCHES
Chatbot conversations
RUNS
Each day
READS
Support platform
SERVES
FINRA Rule 3110(b)(4), PRIN 2A.5.10R
Agent
Clause watcher
WATCHES
Official sources
RUNS
When a signed release arrives
READS
Source texts and their versions
SERVES
Every obligation from that source
Agent
AI notice check
WATCHES
Chatbot releases
RUNS
On each release
READS
The chatbot greeting
SERVES
EU AI Act Art. 50(1)

Your operations, connected.

The feeds in the example firm.

Document store Support platform Team chat archive Social media archive Compliance library HR system Shared drive
Start

Start with a map.

A paid design partnership, one domain at a time: first a map of the records your compliance team owns, then the rules, then the gaps.

01

Your records

Connect the records compliance owns: policies, controls, committee minutes, owners and evidence.

02

The rules

Add Reg42’s encoded rules to see each gap. First package: AI conformance.

03

The gaps

Close each gap with your existing tools or with Reg42 OS, with every approval recorded.

Accountability and security

Accountable by design.

Four gates on every app and agent, and a hard boundary around your data.

Security guardrails

Limits on what a model can access and change, set in the architecture.

An audit trail

Each action records what was done, on what data, and why.

Accuracy, evidenced

Checked against evaluation sets before anything is trusted in production.

A named person decides

The model drafts. A named person decides, and every change carries that name.

By design, your data stays in your cloud account. Only official sources and signed Reg42 rule releases come in, and your graph is designed to export in CLHEAR.

Why Reg42

Built from inside the problem.

Rules, policies, controls, owners and evidence sit in scattered records and people’s heads. Reg42 is built to join them.

From practice

Designed from 10+ years of running compliance technology, with auditors, regulators and C-levels in the room.

The whole program

Built for compliance across all the business activities of a global financial firm, in multiple jurisdictions with leading regulators.

An open language

Built on CLHEAR, an open language for Regulation as Code. Reg42 has a US patent application pending.

The team

A domain expert and a deep technologist. One ran compliance technology from the inside. The other builds mission-critical systems.

Avner Yoffe, Co-founder and CEO

10+ years in compliance technology: 7 at eToro, where he led the creation of the regtech department from scratch, and 3 at Cappitech, now part of S&P Global. Author of CLHEAR.

LinkedIn
Eitan Ezra, Co-founder and CTO

6 years in intelligence technology: Unit 8200 software team lead for mission-critical systems, on projects that won the Israel Defense Prize. Worked with Avner at eToro.

We’re building the system I looked for as a buyer and couldn’t find.Avner Yoffe

Contact

See it on your firm.

Tell us the domain. We reply about fit and the first step.

A paid design partnership, one domain at a time, starting with a map of your own records.

We reply by email.