Scope
What it does, and what it refuses to do.
A boundary you can read before you talk to us. Everything on the second list is permanently out of scope — decisions, not roadmap items phrased politely.
In scope
The authorization register,
and the findings it produces.
The product answers one question: can this entity perform this activity in this state today, and where is the proof? Everything in scope exists either to answer it or to evidence the answer.
Authorization register
Licences, locations, products and activities — each date-ranged, with authorized agents modelled as first-class rather than bolted on afterwards.
The authorization matrix
The join between one location, one product, and the licence that permits it. A gap exists only in that join, which is why we model authorizations rather than licences.
Deterministic gap detection
The same register against the same rule pack produces the same findings on every run, and the run is reproducible.
Versioned, cited rule packs
Every entry carries a version, an effective date, a source citation, and whether a person has verified it against the statute.
Renewal and obligation dates
Dated instances generated from the rules rather than typed into a calendar and maintained by hand.
Permanently out of scope
The refusals matter
more than the feature list.
None of these is a gap waiting to be filled. They are someone else’s product, and you should find them here rather than in month three of an engagement.
Licence applications and filing submission
We manage what a company already holds. Obtaining licences is someone else’s business, and a good one.
AML transaction monitoring and SAR filing
A different product for a different buyer. Adjacency is not a reason to build something.
Any legal conclusion
The system reports evidenced conditions. It does not interpret a statute for your situation, and it will never tell you that you are compliant.
Automated NMLS submission
There is no public write API. A vendor implying that sync exists is describing something else.
Operational analytics
No branch performance, no throughput findings. That was the discontinued predecessor’s product and it is not coming back.
Fifty states before they are verified
Coverage is a claim that a person read the statute. We ship the states our design partners actually hold, and we name them.
Coverage, stated from the rule pack
What the engine
can currently reason about.
These numbers are read from the shipped rule pack at build time, not written into this page. If an entry is added or removed, this paragraph changes with it — copy cannot drift ahead of the engine.
Rule pack 2026.08.1-draft · 13 entries · 13 drafted
No rule here is human-verified
Every entry in the pack is drafted. No person has yet read the statutes behind these citations and signed off on them. Verification of the rules an engagement can reach happens before any customer sees a finding — a finding drawn from an unverified rule is worse than no finding at all, and we would rather say so on this page than in a footnote later.
Outside the pack is silence, not a clean bill
An activity the pack does not cover reports as no_rule — an open research task — never as an absence of gaps. Widening declared coverage is a claim that somebody looked, so it does not happen to make a demo read better.
Who it is for
A narrow buyer,
named honestly.
Multi-location check-cashing and money services operators of roughly 20 to 300 branches, and money transmitters holding somewhere between 5 and 30 state licences. The person using it is a licensing or compliance manager; the person signing is a CCO or COO.
Not the first version
Crypto and digital-asset licensing, fintechs seeking a first licence, single-state operators, and banks. Not because those problems are uninteresting — because the authorization model is shaped around multi-state, multi-location footprints with agent networks, and it would fit worse than it appears to.
What it will never tell you
It will never tell you that you are compliant. The system states facts it can evidence — this licence expires on this date; no licence in the register covers this activity at this location — and leaves the judgment with a person who can be accountable for it.
If this is your problem
Tell us where the register stops matching the floor.
What states you hold, what your locations actually do, and which licences you would check by hand before an exam.