Publication method · version 2 · reviewed September 19, 2026
Methodology
Millatu separates what a public source recorded from when Millatu captured and processed it. The checker presents dated observations and their origin. It does not decide legal or business status.
Current editorial method
A reviewed date means the Millatu project checked that page's explanatory text and destination links on that date. It does not indicate continuous monitoring, certify a current source record, or establish an agency record date.
A correction to Millatu copy, a source link, or presentation is recorded as a Millatu correction. It does not amend an agency record. Questions about Millatu copy can be sent to data@millatu.com; questions about an agency record or service belong with that agency.
How the ABC checker compares records
The checker accepts exact ABC file numbers and selects rows from the retained statewide export. It displays the file number, license type, master indicator, license/application indicator, recorded status, issue date and expiration date. Names, addresses and contact details are excluded.
A component is identified by file number, license type, master indicator and license/application indicator together. Identical repeats are deduplicated. Conflicting values for that same identity make the affected number unavailable for comparison; they do not invalidate unrelated usable numbers.
A first observation is a baseline. Changes require two accepted, dated observations with comparable components. Missing components or records are reported separately; they do not establish closure, revocation or another business event. After a conflicting observation, a recovered record begins a new baseline.
Every response is checked against the expected source refresh date. Stale, rejected or unavailable source evidence suppresses current values and change claims. A result shows the source date, capture context and comparison dates when available. The downloaded JSON report contains the same source evidence for the selected numbers.
Inputs are processed for the request and are not saved as a watchlist. The Privacy page describes the separate aggregate usage counts. For a current authoritative record, use California ABC License Lookup.
Future data publication protocol — not active
The following requirements concern planned county aggregates, bulk listings and public record-history pages beyond the request-only checker. They do not mean those features are approved, scheduled, complete, or active.
1. Source first
Every future observation must identify the source, source URL, source-data date when supplied, Millatu capture time, recorded value, and parser version. A link back to the official source stays next to any data-bearing display.
For the currently documented California ABC source, use California ABC License Lookup for a specific lookup, California ABC Licensing Reports for published reports and broader files, and the California ABC glossary for field definitions.
2. Scope is explicit
The first planned source is California ABC licensing material. The planned Alameda County selection uses the recorded source field Prem County with the value ALAMEDA, as described in the California ABC source and coverage guide.
Coverage means only the source, files, fields, dates, and selection rule stated on the page. It does not imply completeness outside that boundary.
3. Rows are not silently redefined
A source row is counted as a source row. It is not silently converted into one business, one location, or one license. Duplicate and secondary license types can appear separately in California ABC Licensing Reports.
4. Dates describe different moments
- Source data date
- The date stated by the source, when available.
- Captured at
- When Millatu retrieved the source material.
- Accepted at
- When Millatu's checks accepted that capture for possible publication.
- Detected at
- When two accepted captures were compared.
None of these Millatu timestamps is presented as the legal or operational effective time of a source event.
5. Differences stay descriptive
A future comparison may state that a row appeared, was absent in a later capture, or contained a different recorded value. Millatu does not turn that difference alone into a conclusion about business activity or the reason the source changed.
6. Parsing and acceptance are versioned
A parser version identifies the rules used to read a source file. Captures that fail source, schema, or quality checks are not treated as new observations. Comparisons across changed parsing rules require a documented replay or remain unpublished.
7. Corrections are not silent
A later accepted source capture may supersede an earlier display. A Millatu processing correction is identified separately from a change observed in the source. Earlier observations are not silently rewritten to resemble later data.
Questions about a Millatu display can be sent to data@millatu.com. Only the source agency can amend its own record.
8. Publication gates
This protocol describes gates for a possible future release. It does not promise publication, indicate that a gate has passed, or authorize registry data to open.
- Informational pages can be published without registry rows.
- Aggregate displays require accepted captures, source permission review, provenance, freshness, privacy, accessibility, and rollback checks.
- Record and history pages require an additional identity and public-field review.
Any future data-bearing release requires a separate project review, explicit release decision, and its own rollback evidence. The current holding section remains closed and publishes no records.