Skip to main content
The Compliance Physical

We do not just prepare your filings.
We find what is wrong first.

The Compliance Physical reconstructs your complete public filing history, reconciles it against the obligations of your actual disclosure regime, and flags every gap with a rule citation and the accession numbers that evidence it. It runs automatically at onboarding and re-reconciles every six hours after that.

The Problem

Issuers inherit messy histories.

The record outlives the people who made it.

Prior management filed what it filed. An offering was opened and quietly abandoned. The company moved between reporting regimes and the cadence never caught up. None of that is visible from inside the company today, but all of it sits on the public record, and the public record is what a regulator, an exchange, or an acquirer reads.

Cleanup has meant counsel, by hand.

The conventional remedy is a law firm reconstructing years of filings manually: pulling EDGAR one document at a time, mapping each against the rules in force when it was filed, and writing up the gaps. It is slow, it is billed by the hour, and it usually happens only after something has already surfaced.

How It Works

State machines and citations. The AI explains; it does not detect.

01

The timeline walk

The engine reconstructs the complete EDGAR filing history of the issuer, including archives and former names, into a single ordered timeline. That timeline, not a questionnaire, is the input.

02

Concurrent regime threads

Exchange Act reporting, Regulation A, OTC alternative reporting, and foreign-private-issuer status each run as their own lifecycle thread over the same timeline. Mixed and transitioning regimes are thread combinations, not special cases.

03

Deterministic detection

Detection is a state-machine diff of what the rules required against what was filed. Not an AI guess. Every finding carries its rule citation and the accession numbers of the evidence.

04

The AI layer explains

Rules detect; the AI interprets. It writes the plain-English narrative of each finding, asks the issuer what the record cannot show, and drafts the remediation paperwork for counsel review.

Five Anomaly Classes

Every finding belongs to one of five classes.

Each finding carries the rule citation that creates the obligation and the accession numbers of the filings that evidence it. Nothing is asserted that the record cannot show.

Missing filings
An obligation came due under the issuer regime in force and no filing on the record answers it. The finding cites the rule that created the obligation and the period it covers.
Wrong-vehicle filings
A disclosure was made, but on the wrong form for the regime in force at the time. The finding names the form filed, the form the rule calls for, and the citation.
Late filings
The filing exists but landed outside its window. Borderline timing is never asserted as fact; it is classified counsel judgment and routed as a question.
Contradictory filings
Two filings on the public record assert facts that cannot both hold. Each side of the contradiction is evidenced by its accession number.
Dangling lifecycles
An offering or reporting thread was opened on the record and never closed. The finding shows the opening event, the expected exit, and the silence in between.
The Decision Model

Every gap becomes a decision, not an alert.

A finding that only generates anxiety is noise. The Compliance Physical turns each finding into a documented decision with a recorded owner, a recorded rationale, and a recorded outcome.

Branched paths

Each finding proposes its decision paths: remediate now, take it to counsel, or defer with a recorded reason. Deferral is a logged decision with an owner, not a dismissed notification.

Prepared drafts

Where remediation means a filing, the platform proposes the remediation plan and can begin preparing the drafts, grounded in the certified Vault, queued for counsel review before anything moves.

The governance trail

Identified, decided, acted. Each step is timestamped and attributed in the audit ledger, so the company can show not only that a gap was found, but how it was handled and by whom.

At Onboarding

A quiet scan. A calm debrief.

During setup

The Compliance Physical runs automatically while the Vault is being built. No alarms fire mid-onboarding; the record is examined in full before anything is said about it.

After setup

The debrief presents what the record shows, finding by finding, with the evidence attached and the decision paths laid out. From then on, the platform re-reconciles the full record every six hours.

The Discipline

Market Fortress is not your counsel.

The Compliance Physical is recommendation-free by design. It does not advise the company to file or not to file; it states what the public record shows, cites the rule, and attaches the evidence.

Every finding is classified at the source as objective fact or counsel judgment. A missing annual report against an active reporting obligation is a fact. Whether a borderline filing window was breached, or whether an event was material, is counsel judgment, and the platform renders those findings as questions for counsel rather than conclusions. Judgment findings gate the related drafting until counsel has weighed in.

The line is structural, not stylistic: counsel sign-off gates are built into the remediation workflow, and nothing the engine produces is legal advice. Market Fortress flags. Counsel decides.

Proof Discipline

The detection layer is deterministic and regression-locked against real public filing histories: the same record always produces the same findings, and the test suite holds it there. Every finding and every decision lands in a tamper-evident audit ledger, and Market Fortress signatures can be checked against a public verification endpoint without trusting Market Fortress.

See what your record shows.

Early-access program by invitation. The Compliance Physical runs in your first onboarding session, against your actual filing history.

Platform | Market Fortress