Platform
What an inspector would be shown
Written from primary sources and checked against them. As of 2026-09-06. How that is done.
Short answer
How does Bloom prove it enforced the right rule?
Every decision records which version of which rule made it, so a sale from three months ago is explained with the rule as it stood that day rather than with today's. A published rule is never edited; a change supersedes it and both stay. Rules that cannot be evaluated are quarantined and counted as enforcement gaps rather than dropped quietly, because a dropped block rule means the state says stop and the software does not.
Append only means append only
The evidence tables carry no update or delete grant. A correction is a new row that supersedes an old one, and the old one stays. That is the difference between a log and a record, and it is the reason a decision from a previous quarter can still be explained.
Publishing gaps rather than hiding them
When thirteen states were read against their own statutes, four faults in the rule engine surfaced that a single state had hidden. Three rules had been written with a qualifier nothing implemented, so they sold failed and recalled product while appearing to block it. Five rules across four states recorded closed trading hours as the permitted window, which blocks the lawful day and permits every overnight sale. Both are fixed, and both are the reason the gap count is published.
The state pages show what is verified and what is not, per state, with the date of each read.
What it does not do
Bloom is not a validated track and trace integrator in any state, so reports are generated and queued rather than posted to a live regulator system. It is compliance software and sourced reference information, not legal advice, and the licensee remains responsible for what is filed.
Questions people ask next
- What does the evidence log actually contain?
- Every decision the engine made, the version of each rule that made it, a hash of the context those rules saw, and the outcome. It is append only and monthly partitioned. A sale from three months ago is explained with the rule as it stood that day, because a published rule is superseded rather than edited.
- What happens when a rule cannot be evaluated?
- It is quarantined and reported rather than silently dropped or silently enforced backwards. A dropped block rule means the state says stop and the software does not, so a rule that fails to load is counted as an enforcement gap and surfaced, not hidden.
- Are all your published rules enforced?
- No, and the exact number is published. Across the states read so far, most published rules enforce at the till, some are requirements no register can check such as keeping records for three years, and a small number genuinely fail to load and are visible as gaps. Claiming otherwise would be the easiest lie on this site to tell and the easiest to catch.
- Can I export everything for an inspection?
- The inspection packet exports a period, a licence, an employee or a package as signed files with a summary. It is built from the same records the software runs on rather than assembled for the occasion.
- How do I know a fact is current?
- Every published fact carries the date its source was last verified, shown next to the fact. Bloom watches for regulatory change, and a fact stays live until a real change replaces it on the day that change takes effect.