The Periodic Table of Regulatory Obligations

In most organisations, regulation is treated as text. It arrives in the form of PDFs, guidance documents, memos, checklists, and policy templates.

Compliance teams and advisors then do something difficult. They translate prose into operational requirements.

But there’s a hidden limitation. Without a stable model of regulatory units, the system never becomes coherent. It becomes a collection of interpretations.

The pre-structure era of compliance

Think of chemistry before the periodic table.

The raw material existed. Scientists knew the elements and could describe their properties. What was missing was the organizing structure.

Progress was slow and comparisons were manual.

Regulation today looks similar. Obligations are real, patterns exist, but we still lack a universal coordinate system.

Crosswalks are built by hand. Comparisons are narrative. “Coverage” is often asserted rather than measured.

What Mandatry is actually doing

Mandatry converts regulatory frameworks into

→ atomic obligations, the smallest enforceable units
→ a canonical concept layer, which creates jurisdiction-neutral meaning
→ a governed structure with integrity controls and version discipline

This turns “regulation as prose” into “regulation as computable structure.”

Or more bluntly, most tools index documents. Mandatry indexes regulatory physics.

Why this changes what becomes possible

Once regulation becomes atomic and canonical,

→ overlap is visible, not guessed
→ gaps are computable, not debated
→ drift is measurable, not discovered during audit pain
→ new frameworks can map into existing meaning, reducing reinvention

This is the point where compliance stops scaling linearly with portfolio size.

Why this layer is defensible (and rare)

This part of the market isn’t crowded because structural regulatory modeling is much harder than monitoring.

Monitoring is a data ingestion and NLP problem.

Structural modelling requires

→ atomic decomposition logic
→ deterministic classification rules
→ ontology governance
→ version discipline
→ integrity validation and audit reproducibility

It demands engineering and doctrine simultaneously.

And that creates a compounding moat. Canonical maturity grows over time as duplicates are prevented and mappings are governed.

The point of the “periodic table” metaphor

The metaphor is not hype. It is a statement of category.

Mandatry is not trying to become another compliance workflow product. It is trying to establish a structural reference layer beneath the ecosystem.

The objective is that, in ten years, organisations do not ask, “Which spreadsheet is the latest crosswalk?”

They ask, “Which canonical regulatory layer are we standardised on?”

That is what infrastructure adoption looks like.