CLHEAR Open source
Turns raw regulatory text into compliance blueprints, each item traced to its clause. Help make it the industry standard.
CLHEAR on GitHubThe program your firm needs, the program you already run, and a plan to close the gap. Every item traced to the clause it comes from.
One system, three parts
Turns raw regulatory text into compliance blueprints, each item traced to its clause. Help make it the industry standard.
CLHEAR on GitHubRuns CLHEAR in your own cloud account, on your firm's data, and adds what a program needs day to day: feeds, tasks, evidence, apps and agents.
See Reg42 OSThe AI model inside Reg42 OS, hosted next to your data. It answers from your firm's blueprint and shows the trail behind every answer.
Ask SolonExample Markets · a fictional US broker-dealer
What would you like to know about FINRA 2210?
Ask Solon about the example firm…Follow Example Markets, a fictional US broker-dealer, from the text of one rule to a plan that closes the gap. Switch the rule at any time.
Pick one rule, describe your firm, and get the program you need.
Pick the regulation or licence that matters now. CLHEAR keeps its original text, clause by clause, with the source and date.
2210(d)(1)(B)“No member may make any false, exaggerated, unwarranted, promissory or misleading statement or claim in any communication.”
Picture: a shelf of the three starting regulations with the selected one pulled out, showing its official reference, its date and the verbatim text of one clause.
Countries, licences, products, clients and channels. These facts decide which obligations apply. Controls, owners and evidence stay in your own systems.
jurisdictionsauthorisationsproductscustomer_basechannelsOnly these facts go to CLHEAR. Controls, owners and evidence stay in your systems.
Picture: the example firm's profile, with its countries, licences, products, clients and channels lighting up as they are chosen.
CLHEAR lists what your firm must have: policies, roles, committees, systems and processes. This is your reference blueprint, and every item links back to its clause.
Picture: the reference blueprint. Each required item is drawn with a dashed periwinkle outline and linked to the clause it comes from.
Start with one regulation. We map it with you.
Scope a conformance projectMap what you run today and see the gap, item by item.
Your documents, systems, people and data feeds form the actual blueprint. It uses the same shapes, so the two can be compared item by item.
Picture: the actual blueprint. The firm's documents, systems and data feeds fill the same slots in solid turquoise. Empty slots show what is missing, and one extra item is marked as surplus.
The two blueprints overlay. Covered items fill in, gaps stay open, and mismatches and extras are marked.
Picture: the two blueprints overlaid. Covered items are filled, gaps stay empty, and the mismatch and the surplus item are marked, each with its reason.
Start with one regulation. Compare it on your own firm.
Scope a conformance projectPlan the work, prove it with evidence, and stay current.
Each gap becomes a task with an owner across the three lines of defence: generate a document, assign a role, install an app or run a workflow.
Scope a conformance projectPicture: the action plan. Each gap becomes a task with an action type, an owner and a line of defence.
Evidence flows back from production onto the item it proves. The audit trail records who did what, and why.
Picture: evidence arriving from production onto one item, which turns covered, while its task moves to done and the audit trail records who approved it and why.
A complete, traced blueprint makes precise answers possible. Solon is the AI model inside Reg42 OS. It answers from the firm’s own blueprint graph and shows the trail behind every answer.
Posts that influencers make for Example Markets count as its retail communications under Rule 2210. A registered principal must approve each one before use, the content must be fair and balanced, testimonials must carry the required disclosures, and each post must be kept with its dates of use. Rule 3110 asks for written procedures that cover all of this.
A replay on a fictional firm with simulated data. It is an example, not a live client.
A changed clause travels up through the blueprint to the one task it affects, with a named owner.
OBL:finra-2210#d-6-bPicture: a change feed. A clause change updates an obligation, flags one blueprint item, and creates one task for a named owner.
Each regulation adds its blueprint, and the blueprints join into one program. An item that serves more than one rule appears once.
Start with one regulation. Grow from there.
Scope a conformance projectCLHEAR is an open standard and an open-source engine. It reads the texts you choose, finds the duties in them, and returns the smallest set of measures that covers them. Each measure points back to its clause. Help make it the industry standard.
An example from the story, traced from a blueprint item to the words of the law. The digest lets anyone check the clause text.
BLK-PRINCIPAL-APPROVALOBL:finra-2210#b-1-aAn 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").
Published. The specification, the schemas and the engine code are public, under AGPL-3.0.
Runnable. Anyone can run it on their own sources, on a laptop or in a private network.
Reviewed in public. Changes arrive as pull requests anyone can read.
Reg42 OS runs CLHEAR natively in your own cloud account and adds what a program needs to run day to day. Client data stays in your account.
Only official sources and signed releases come in. Your data stays inside.
BETABuild: a design partner can assemble an app from the blueprint.
Examples on the fictional firm.
The feeds in the example firm.
Eight layers of open records, from the verbatim clause to the leanest program.
Items, obligations, clauses and evidence for one firm, linked in one graph.
The platform runs in your own cloud account, so your data stays there.
Agents act only after a named person approves, and the record keeps the name.
A conformance project, scoped and priced per regulation. Reg42 people run it with your team, and the same path works for the next rule.
Choose the regulation or licence to start with.
Reg42 maps your firm and builds the reference and the actual blueprint in your instance.
You get the gap analysis and the plan, and you keep the platform running.
Communications with the public, including social media and influencer posts, for a US broker-dealer.
Scope a conformance projectBest execution for a US broker-dealer, including the quarterly review of execution quality.
Scope a conformance projectRisk management and human oversight for a high-risk AI system, such as credit scoring.
Scope a conformance projectFour gates on every app and agent, and a hard boundary around your data.
Limits on what a model can access and change, set in the architecture.
Each action records what was done, on what data, and why.
Checked against evaluation sets before anything is trusted in production.
The model drafts. A named person decides, and every change carries that name.
Your data stays in your cloud account. Only official sources and signed CLHEAR releases come in.
Tell us the regulation. We reply about fit and the first step.
Regulators didn’t raise the barrier for us. They raised it for everyone who treats AI as a demo.
Pick the regulation. We reply about fit and the first step.