How Exojuris works.
Layers, kept separate
- Source documents. Each official document is captured with its identifiers, URLs and capture time. When a source changes a document, a new immutable version is stored; earlier versions are kept.
- Evidence. Every value Exojuris shows (a date, a status, a docket number, an applicant) is stored as a claim pointing to the exact source location: an API field, a table cell, or a quoted sentence. The “evidence” link beside each fact shows it.
- Proceedings. Documents are linked into proceedings (FCC dockets, FAA rulemaking dockets, ISED notice numbers, Canadian satellite applications). Each proceeding has an append-only chronology.
- Published items. Briefing items are generated from those records. They never replace the evidence.
Dates
Exojuris keeps the difference between the date a source says something happened, the date a document was published, an effective date, a deadline, and the time Exojuris first recorded it. A date without a time is shown as a date. Deadlines are shown only when an official source states them. Exojuris never calculates a legal filing deadline. Relative periods (“within 30 days of publication”) are quoted, not converted into dates.
Each proceeding page has an “as known on” view that hides events recorded after the chosen date. Records imported from the historical archive are labelled; a capture made today cannot show what a page looked like years ago.
Statuses
A status on Exojuris is the documented procedural stage shown by the latest covered document (for example, “proposed rule published” or “listed: Accepted”). It is not a statement of legal effect. A rule may be stayed, challenged or delayed by documents Exojuris does not cover. On ISED’s satellite application list, “Accepted” does not by itself establish that every necessary authorization was granted, and the list does not say when a status changed.
Automation and AI
Collection, extraction and publication of factual items are automated and rule-based. No language model writes or checks the published items today. A fixed publication controller publishes an item only if its document class is approved, its source is in live mode, and every fact shown has supported evidence. Conflicting values (for example, an API date that disagrees with the document’s own text) are published only with a visible warning, and never become deadlines. Analysis or commentary, if added later, will be labelled and held for review by a competent reviewer before publication.
Insights
Counts on insight pages are computed in code from a complete, defined set of records, never from search rankings. Each run stores its definition version, dataset fingerprint, denominator, unresolved records and the exact record list, which you can download.
Corrections
When a source changes or an error is found, the item is updated as a new version with a stated reason, listed on the corrections page. Readers who received the item by email are sent a correction notice once email delivery is configured. Withdrawn items stay visible as withdrawn.
Untrusted content
Text retrieved from sources is treated as data. It cannot change how Exojuris behaves, publish anything by itself, or reach private account data.