ProfytAI
Log In
The Regulation Intelligence Engine

The Engine Behind
Every Product We Ship.

Regulation is written for people. We built the engine that lets software and AI act on it, and prove every step.

Request a WalkthroughSee the Proof
Three Layers

One Engine. Three Layers.

Each layer has one job and hands verified output to the next. Regulation goes in. Proof comes out.

Layer 01 · Regulation Compiler

One Rule, Compiled in Front of You.

A real MAS rule, split into its words, mapped to who must act and what they must do, then compiled into one record that carries the page it came from. Every quote is located in the regulator's own text, or it never ships.

Source · MAS TRM Guidelines 2021 · §4.3.1 · Page 13 · Verbatim

The FIshouldtake into considerationfinancial, operational, legal, reputational and regulatory factorsin assessing technology risks.

Parsed
ACTOR
The FI
MODAL
should
ACTION
take into consideration
OBJECT
financial, operational, legal, reputational and regulatory factors
CONDITION
in assessing technology risks.
Compiled

Compiled Record

Verified

ID
MAS.TRM.2021.Sec4.3.1.p13.OBL2
ACTOR
The FI
MODAL
should
ACTION
take into consideration factors
SOURCE
§4.3.1 · p.13

Record MAS.TRM.2021.Sec4.3.1.p13.OBL2, quoted verbatim from the public MAS text.

Compiler · How a Record Is Made

Provable Obligation Extraction.

AI suggests each record, the regulator's own text decides what stays, and every record is argued for and against before it is sealed.

Regulatory Source
MORB / AMLC / GoTRACS / MAS / Others

Regulatory PDFs enter the compiler, which reads each rulebook in its own structure, section by section.

AI Reading
Suggests Each Record

AI reads each rule and suggests the record: who must act, what they must do, and under which conditions.

Source Check
Checked Against the Source

Every record is checked against the regulator's own words before it moves on. Anything that cannot be found in the source is rejected.

Integrity Gates
Checked Before Release

Automated integrity checks must pass before any build is released. A failed check stops the release.

Adversarial Review
Argued Before It Is Accepted

Each record is argued for and against, and a verdict is reached before it is accepted. Every step is traced.

Compliance Ground Truth
Audit-Ready Records

Each obligation ships as a structured, self-contained record. Audit-defensible ground truth our applications build on.

Examiner-Ready Output
Inline Forensics Objects
Highlighted Regulator Pages
Append-Only Evidence Ledger
Layer 02 · Ontology · Live in Atlas

Every Rule, Linked to What It Governs.

Links each duty to the entities it binds, the circulars that touch it and the sanctions that enforce it. Every link carries the quote that proves it, or waits for a named reviewer.

One Rule, Traced

Regulator

  • The authority
  • that issues the rules
Publishes

Rulebook

  • A rulebook, act
  • or regulation,
  • tied to its issuer
  • and its source
Includes

Obligation

  • One obligation, in the regulator's words
  • With its citation and page
  • And whether it is proven

e.g. PH.KP.IRR.2025.RULE-III.2(b)(i).p11.OBL1

Konektadong Pinoy Act IRR · p.11

Depends On

What Applies to You

  • Which rules apply
  • to which part of
  • your organization,
  • and why
Applies To

Your Company

  • The legal entities
  • your rules apply to,
  • with their names
  • as regulators know them
Cited On

The Source Page

  • The exact words
  • on the exact page
  • of the source,
  • behind every
  • record

Everything It Connects

Your Organization

Your CompanyWho Owns WhatWhat You HoldWhat You File

When Rules Apply

The ConditionsWhat Applies to YouWhat-If Cases

The Rules

RegulatorRulebookObligation

What Changes

New CircularsDoes It Change AnythingWhat It Touches

The Proof

The Source PageWho Checked ItWhat to Do Next

How a Rule Connects · Conceptual View

Ontology · What It Opens Up

One Model, Read by People and Agents.

For People

A Dynamic, Interconnected Obligation Model

A graph of a jurisdiction's obligations and how they interconnect, so a change to one rule surfaces every obligation, control and evidence item it touches.

  • Obligation crosswalks within a jurisdiction
  • Links from obligation to control to evidence
  • Change-impact tracing across related obligations
  • Machine-readable output formats
For AgentsAPI and MCP · Q4 2026
Illustrative Call

agent needs the alerting duty for this service

→ tools/call obligation.get

{ "id": "MAS.TRM.2021.Sec7.7.4.p26.OBL1" }

← result

"modal": "SHOULD",

"verbatim": "The FI should configure system events or alerts…",

"citation": "MAS TRM Guidelines, Sec. 7.7.4, p. 26 (2021)"

MCP Server and API Surface

AI coding agents will call structured obligations, controls and evidence requirements on demand, and build regulation-compliant implementations with traceability.

  • MCP tools for obligations, controls and evidence schemas
  • API calls from coding agents during build and review
  • Compliance by construction, with citations
  • Guardrails constrained to known regulatory requirements
Layer 03 · Integrity Ledger · Live in All Products

Every Decision, Sealed with Its Evidence.

The Integrity Ledger seals each decision with its evidence and the rule it was made under, in a hash-chained, append-only record an auditor can check.

  • Hash-Chained, so a Changed or Removed Decision Breaks the Chain
  • The Evidence and the Rule Travel with Every Decision
  • The Regulator's Page, Highlighted, Ships with the Record
See the Evidence Standard
The Integrity Ledger in AssessrLog, with demo data. A decision chain by day, the sealed events register with hashes and statuses, and one decision event with its notes and basis.
The Engine at Work · Gap Analysis in the Compliance Platform

The Engine, Applied to Your Policies.

The same adversarial review that checks every compiled record also checks your policies against the compiled rules, with every verdict traced to its source.

Regulation

MORB Part IX §931

Required obligation text

Bank Document

MTPP

Money Laundering and Terrorist Financing Prevention Program

Case For

What Holds

+Satisfies
~Partial Coverage

Case Against

What Is Missing

−Missing Requirement
−Scope Gap

Decision

Weighs Both Sides

Returns one traced verdict for each obligation.

Verdict
1 of 4
See Gap Analysis
Gap Analysis · How a Run Works

Four Stages, One Verdict per Obligation.

  1. STAGE 01

    Documents

    Regulations, policies, procedures, controls and legal documents are ingested.

  2. STAGE 02

    Evidence Map

    Verbatim quotes and source anchors tie every obligation to its evidence.

  3. STAGE 03

    Adversarial Reasoning

    Support and attack arguments for each obligation are weighed together.

  4. STAGE 04

    Decision Output

    Coverage status, rationale and the cited evidence trail, for every obligation.

Both Sides, Every Time

Every Finding Is Argued

Each obligation is argued for and against before a verdict, so no finding rests on a single reading.

Same Depth, First to Last

Every Obligation, Equal Scrutiny

The last obligation in a run gets the same depth of review as the first.

Tell Us Your Use Case.
We'll Show You the Engine on It.

Request a WalkthroughLicense the Data