Left · the labs.llc tool
Rules, side by side
The Federal Register, read live: the labs.llc desk against the Register's own website and the federal portal for comments.
Right · set against
- FederalRegister.gov
The Office of the Federal Register's web edition: current issue, public inspection, search, reader aids and My FR accounts.
page checked 2026-09-27 20:03 UTC - Regulations.gov
The federal site for dockets and public comments on proposed rules and other documents.
page checked 2026-09-27 20:04 UTC
1 · The tool
What it is, and who it is for
The Federal Register is the daily journal of the United States government: rules, proposed rules, notices and presidential documents, one issue every working day. The labs.llc Rules desk reads it live and arranges it for people who have to keep up: the day's issue counted by type and listed in full, what agencies filed today for publication tomorrow, and every comment period that closes in the next thirty days, with the days left.
It is for lawyers, compliance staff, reporters, advocates and anyone who wants to comment on a proposed rule before the window shuts.
2 · The workings
How it works
There is no labs.llc server in the path. The page's script calls the Federal Register's public API directly from your browser; the API needs no key and allows cross-site reads. It uses four endpoints: documents, per-type facets, current public-inspection documents and agencies. Every request names the fields it wants, and the same list drives the parser, so the page asks for exactly what it draws. Titles, counts and dates are printed as the API returned them; the only two things the page works out itself, the days remaining and summed facet totals, are named as such.
- www.federalregister.gov/api/v1: documents, facets, public inspection and agencies (Office of the Federal Register, NARA)
Where the work happens: Your browserNo relay: the page talks to the Register's API directly.
3 · The test
What we ran, and what came back
Run against a local copy of labs.llc build 537, byte-identical to the live site. Times are UTC.
| What we did | When (UTC) | What came back |
|---|---|---|
| Count for the 25 September issue | 2026-09-27 19:58:22 | Through the same endpoint the page uses: HTTP 200 in 0.14 s, 80 notices, 16 rules, 8 proposed rules. |
| Today's public-inspection list | 2026-09-27 19:58:22 | HTTP 200 in 0.06 s, 168,493 bytes, 106 documents on file. |
| Can the browser read it directly? | 2026-09-27 19:58:22 | Yes: the agencies endpoint answered with access-control-allow-origin: *. |
4 · Side by side
Row by row against FederalRegister.gov, Regulations.gov
2 to labs.llc3 elsewhere1 level
01Today's issue
Counted by type from the API's facets, then listed in full with titles and agencies as returned.
Evidence: rules/assets/js/app.js lines 355-381FederalRegister.gov shows the current issue on its home page; when we looked it read 101 documents from 33 agencies, 179 pages: 83 notices, 5 proposed rules, 13 rules.
Same publisher, same data. FederalRegister.gov is the source and links the official legal edition on govinfo.gov; labs.llc is a faithful reading of it.
02Comment periods about to close
Every period closing within 30 days on one list, sorted by closing date, with days left counted to your own midnight.
Evidence: app.js lines 70, 583-616, 634Regulations.gov shows “Comments Due Soon” for periods closing today or within a few days, has a filter for documents open for comment, and gives due dates in Eastern Time, per its FAQ.
labs.llc gives the longer look-ahead in one sorted list; Regulations.gov is where you then go to comment.
03Three views on one page
Today's issue, tomorrow's public-inspection filings and the closing comment periods, together, from the same API.
Evidence: app.js lines 1-11FederalRegister.gov keeps Current Issue, Public Inspection and Document Search as separate sections.
One page instead of three is the labs.llc desk's main contribution.
04Taking part
A reader only: it cannot submit a comment or open a docket.
Regulations.gov accepts comments on notices, requests for information and proposed rules while a period is open, and its dockets hold supporting documents and other people's comments.
Regulations.gov does the thing the reading is for.
05Keeping track
No accounts, subscriptions or alerts, and no refresh timer: it reads when you ask.
Evidence: rules/WIRING.json method.refreshFederalRegister.gov offers My FR, with a clipboard, saved comments and subscriptions.
If you follow an agency week after week, the official site will remember it for you.
06Searching the whole Register
Term and agency search, but it inherits the API's limits, which it labels: paging stops at 50 pages and counting at 10,000.
Evidence: app.js lines 60-61FederalRegister.gov has advanced document search, public-inspection search and a library of reader aids.
For research, the official search is fuller; labs.llc is at least open about where its own stops.
5 · The shortcomings
Where it falls short
- A reader only: no accounts, subscriptions or alerts, and no way to comment from the page.
- It inherits the API's caps of 50 pages of results and counts up to 10,000.
- No automatic refresh; the page reads when you load or ask.
6 · The verdict
Which side, for which job
Left: labs.llc Rules
Pick the labs.llc desk for a morning read: what was published, what lands tomorrow, and which comment windows are closing, on one page with nothing between you and the publisher.
Right: elsewhere
Pick FederalRegister.gov to search deeply or subscribe, and Regulations.gov to read a docket or file a comment.
A clean, faithful reading of the Register that joins three official views; for acting on what you read, the government's own sites.
Try Rules on labs.llc