For · Regulatory & Compliance Research

Binding law. Guidance. Draft.
Enforcement position.
These are not the same.

Regulatory research fails when authority, applicability and effective state are flattened into one summary. A real document can still be non-binding. An official source can still be inapplicable to the jurisdiction or date that matters. Commentary can be useful without being authority.

Epistamate is designed to preserve those distinctions at the claim and evidence level, together with the audit trail of how the view was formed.

See the regulatory experiment →The authority model →

Source authority is a property to evaluate,
not a score to infer from a domain name.

Binding instruments

Primary law, regulations, directives, decisions and other binding instruments have a different evidentiary function from interpretive guidance or commentary.

Official guidance

Regulator guidance, Q&A, supervisory statements and official communications may be highly relevant while remaining non-binding. The distinction should stay visible.

Proposals and drafts

Draft rules, consultations and legislative proposals are evidence about direction, not current obligations. Future-state and current-state claims should not silently merge.

Commentary and analysis

Expert and industry analysis can orient research or identify contested interpretations, but it does not inherit the authority of the instrument it discusses.

Regulatory intelligence that preserves
authority, scope and uncertainty.

01

Authority and applicability at claim level

Regulatory propositions can carry jurisdiction, authority class, binding status, affected actors, effective dates and applicability boundaries rather than losing those distinctions in synthesis.

Core principle: source trust is not truth, and official status alone does not establish that a proposition applies to the present question.
02

Contradictions and overlaps remain explicit

Different instruments, regulators or jurisdictions can create genuinely conflicting or overlapping obligations. The product is designed to surface that state rather than forcing a false single answer.

Reviewer value: a conflict that remains unresolved is a research object, not a synthesis failure to hide.
03

Audit trail without legal overclaim

Epistamate records research state and researcher decisions so a later reviewer can reconstruct what evidence and uncertainty were visible at the time. That can support governance and auditability; it is not a legal certification of compliance with any statute.

Important: legal applicability and regulatory compliance require qualified professional judgment outside the software.
04

Regulatory knowledge that can be updated

The long-term Knowledge layer is intended to preserve prior interpretations and evidence while re-evaluating them when an instrument changes, an effective date passes, or a new jurisdictional source appears.

Current boundary: RegWatch pack infrastructure exists, but live vertical calibration and durable cross-topic Knowledge are still development milestones.

Use models to search and interpret.
Do not let them collapse the legal hierarchy.

Planning

Frontier models can identify missing jurisdictions, likely primary instruments, interpretive disputes and useful acquisition lanes faster than a rigid planner.

Interpretation

Models can help extract candidate obligations and relationships from long instruments, but candidate interpretation remains separate from evidence and legal authority.

Challenge

Models can generate alternative readings, conflicting authorities and implementation edge cases. Those suggestions should drive evidence checks rather than become conclusions by agreement.

Product doctrine: multiple model agreement is process robustness, not independent legal or evidentiary corroboration.

If your regulatory research needs a defensible trail from proposition to authority,

We are looking for bounded regulatory workflows where authority class, applicability and reviewer provenance are consequential.

Start a conversation →