Infrastructure Layer

Compliance Infrastructure for Regulated Industries.

Southeast Asia's financial system is growing faster than its compliance infrastructure. We are building the structured regulatory backbone. The layer that every bank, fintech, and regulated enterprise in the region can operate on.

11
In scope for future expansion

MAS, BSP, OJK, BOT, BNM, SBV,NBC, RMA, MMA, AMBD, CBSL

6,000+
Regulated institutions

Banks, fintechs, insurance, and other regulated entitiesare all starting from scratch over and over.

Evidence-Grade
From day one

Every obligation verbatim, traceable, and reproducible.Built to withstand examination.

How It's Built

Four Layers. One Unified Regulatory Data Model.

Most compliance tools sit on top of unstructured documents. We start at the data layer by modeling regulatory obligations into a machine-readable format that our AI systems can use.

Active layerRegulatory Obligation Mapping
ObligationsStructured
Layer01 / 04

The Evidence Standard

Why General-Purpose AI Cannot Produce Audit-Grade Compliance Evidence.

A technical breakdown of why systems like Copilot fail compliance examination standards - and how this infrastructure is designed differently.

Neuro-Symbolic Architecture

Provable Obligation Extraction.

A neuro-symbolic extraction process where neural inference proposes candidates, deterministic verification proves provenance, and BAF adjudication formally accepts every regulatory obligation.

Regulatory Source
MORB / AMLC / GoTRACS / MAS / Others

Regulatory PDFs enter our intelligent document pipeline. Deterministic parsing and configuration-driven processing produce framework-specific extraction recipes.

Neural Inference
Schema-Constrained Inference

Schema-constrained LLM inference, restricted to judgment-requiring fields. The model is never trusted for source location, which is recovered deterministically by the verifier.

Deterministic Verifier
Byte-Exact Source Alignment

Byte-exact alignment to the parsed source. Source location metadata is recovered independently, never claimed by the model. Ungrounded quotes are rejected (hallucination guard).

Integrity Gate Suite
Falsifiable Build Contracts

A suite of falsifiable contracts spans structural, semantic, and accuracy dimensions. Strict invariants gate the build; quality heuristics gate against calibrated thresholds.

BAF Adjudication
Defender, Prosecutor, Judge

Three agents reason under formal, qualitative bipolar argumentation. The Judge returns a verdict plus a structured, self-healing, machine-actionable remediation directive from a closed action set.

Compliance Ground Truth
Audit-Ready Records

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

Examiner-Ready Output
Inline Forensics Objects
Highlighted Regulator Pages
Append-Only Evidence Ledger
Advanced Gap Analysis

BAF Adversarial Reasoning Agents for Defensible Gap Analysis.

ProfytAI’s Bipolar Argumentation Framework (BAF) applies structured, qualitative challenge-and-defense reasoning to regulatory analysis. Every obligation is contested, defended, and adjudicated.

Regulation

MORB Part IX §931

Required obligation text

Bank Document

MTPP

Parsed to machine-readable data

Defender

Coverage Ledger

+Satisfies
~Partial Coverage

Prosecutor

Gap Ledger

Missing Requirement
Scope Gap

Judge

Reconciles the Ledgers

Reasons only from the structured findings, never the raw corpus.

Verdict
1 of 4

Two Inputs

The regulation (MORB) and the bank's document (MTPP), parsed to machine-readable data.

Adversarial Reasoning

A Defender's coverage ledger (green) weighed against a Prosecutor's gap ledger (red).

One Traceable Verdict

The Judge reasons only from the structured findings, reconciling one of four statuses.

The Same Flow, Stage by Stage

The diagram above, expanded into its four pipeline stages, from raw documents to a cited, defensible decision.

1. Documents

Regulations, policies, procedures, controls, and legal documents are ingested into our intelligent document processing pipeline.

  • Regulatory Source
  • Bank Documents
  • Legal Documents / Control Evidence

2. Evidence Map

Verbatim quotes and source anchors tie every obligation to its supporting evidence in the bank's documents, building an auditable cross-reference per record.

verbatim anchors, not summaries

3. BAF Reasoning

Defense/Support and Challenge/Attack arguments are weighed together.

Judge resolves both sides

4. Decision Output

Coverage status, rationale, and cited evidence trail.

Covered
Partially covered
Gap / missing evidence
Requires review

Evidence trail + rationale

Every finding links back to source clauses and the argument path.

What Is a BAF?

A structured reasoning approach where every claim is contested by an attacking agent, defended by a supporting agent, and adjudicated through structured, qualitative reasoning, so the path from evidence to verdict stays visible end-to-end.

How ProfytAI Uses It: ProfytAI implements the BAF pattern with 3 specialist LLM agents: a Prosecutor Agent, a Defender Agent, and an Orchestrator/Judge Agent that reconciles their structured findings into one verdict.

The Result

Defensible gap analysis where every conclusion can be opened, examined, and explained back to the source evidence, not a black-box AI verdict.

Every score traces back to the exact evidence and reasoning that produced it.

How Agents Share Context

One agent cannot hold your full policy library and its own reasoning without degrading. The context window fills, attention dilutes, and earlier context gets dropped (context rot).

ProfytAI Separates Reading from Adjudication

  • Worker agents carry the bank corpus and do the data-heavy reading across your policy library.
  • The orchestrator never ingests that corpus. It reasons from a compact structural index of each document plus the structured findings workers return, so its working memory stays lean at any library size.

Heavy Context Is Paid for Once per Run

  • The corpus is a stable, cacheable prefix on every worker call: processed once, then reused for each obligation instead of re-sent every time.
  • Reasoning context never bloats as the run progresses.
  • Every obligation gets the same depth of scrutiny, first to last.
AI Surface
Coming Soon

Structured Data That AI Can Actually Reason Over.

Most compliance data is locked in PDFs and spreadsheets. Ours is structured, modeled, and exposed via APIs and MCP servers, so AI can query, validate, and generate against it.

profytai · mcp200 OK
get_obligation("MAS TRM 8.4.1")
{
id: "MAS-TRM-8.4.1",
deontic: "SHALL",
controls: ["CTL-14", "CTL-22"],
evidence: ["EVD-08", "EVD-09"],
citation: { page: 42, section: "8.4.1" }
}

One Call · Obligation, Controls, Evidence, Citation

Claude & LLM IntegrationsAI-01

MCP Server + API Surface

AI coding agents can call structured obligations, controls, and evidence requirements on-demand, generating 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
Knowledge GraphAI-02

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
How Teams Use It

Keep Work Grounded in One Source of Truth.

Pull the obligation register for any MAS or BSP regulation. Map controls. Collect evidence. Export the audit trail. All structured. All machine-ready.

(a)

Dashboard view

Map controls, track evidence, monitor gaps across your program

(b)

Register export

Obligation registers, structured and ready for export into your own systems

(c)

API access

Coming Soon

Pull any obligation by jurisdiction, framework, or risk domain

Obligation Register - MAS TRM
MAS TRM § 4.2.1Controls3 mappedEvidence2 / 3StatusAudit-ready
BSP MORB § 148Controls5 mappedEvidence4 / 5StatusIn progress
OJK POJK 11/2022Controls4 mappedEvidence4 / 4StatusRoadmap
BNM RMiT § 10.3Controls6 mappedEvidence2 / 6StatusRoadmap
11 jurisdictions · 6,000+ institutions

Start here

The Infrastructure Is Live. The Packs Are Coming Soon.

The structured regulatory data model is live today. The obligation register packs and data licensing ship Q3 2026. Reach out to see what infrastructure-grade compliance documentation actually looks like.