A row of closed brushed-steel turnstiles standing across the width of an empty concrete hall, lit flat and cold, with no sign or marking on the gates or the bare walls behind them. — Original editorial artwork generated for Hugin.

One proposal / two windows

A fee proposal.
Two ways to read it.

November 9 for the fee rule. December 7 for its information collection. The distinction is printed in one DHS document.

Choose reporting or commentary

01 / Read the record

Money and work

A proposed fee, a future wage rate, and a request for firsthand accounts. Each has a different legal status.

Proposed rule · fee not in effect3 min read · 2 source receipts

DHS proposes a $70,000 fee for a student's first period of Optional Practical Training work and $30,000 for each one after, paid by the school.

The Department of Homeland Security proposes charging a school $70,000 the first time it recommends an F-1 student for Optional Practical Training work authorization, and $30,000 for every OPT period after that, before the recommendation can be filed. The fee would start only once a final rule takes effect and would not reach OPT already approved or already recommended. Comments on the proposal are due November 9, 2026.

Why it matters: The proposal puts payment on schools before they can recommend an F-1 student for OPT; DHS says schools may pass the cost on.
What to watch: Proposal comments: November 9, 2026, 11:59 p.m. Eastern. Information-collection comments: December 7. These are separate windows; neither is a fee start date.

The limit. No final rule or effective date is established. The separate impact workbook and docket comments were not read.

How this record was read

Read October 8 Arizona time, fetched directly via curl from the Federal Register's full-text endpoint (2026-20660.txt), the published text of the proposed rule, pages 64566-64600 of the October 8, 2026 Federal Register. Limits: did not read the regulations.gov docket, DHS's separate economic-impact workbook, or the H-1B proclamation the rule cites for comparison.

Rate notice · January 6, 2027 start3 min read · 2 source receipts

Minimum wage for certain older federal contracts rises to $14.05 an hour, tipped cash wage to $9.85, effective January 6, 2027

The Department of Labor says the minimum wage required on a shrinking set of federal contracts rises to $14.05 an hour, and the required cash wage for tipped workers on those contracts to $9.85 an hour, both starting January 6, 2027. The current rates are $13.65 and $9.55. The notice says the rates cover only certain Davis-Bacon Act and Service Contract Act contracts awarded between January 1, 2015, and January 29, 2022, and not renewed or extended on or after January 30, 2022.

Why it matters: Workers on qualifying older federal contracts have a new announced minimum rate. The contract's award and renewal history determine whether this notice applies.
What to watch: The notice sets January 6, 2027 for $14.05 an hour and a $9.85 tipped cash wage on contracts covered by Executive Order 13658.

The limit. This is not a national minimum wage or a rate for every federal contract. The notice does not count how many covered contracts remain.

How this record was read

Read October 8 Arizona time; curl fetched the plain-text notice directly from federalregister.gov (bytes saved to corpus), cross-checked against the Federal Register's document API record for the same filing. Limits: did not read the PDF page images or the document's HTML rendering; did not independently re-derive BLS's underlying CPI-W data points beyond the chart printed in the notice's own Appendix A.

Joint inquiry · comments invited3 min read · 2 source receipts

FTC and USDA open a joint inquiry into farm equipment manufacturing and distribution, inviting farmers and repair shops to submit evidence of restrictions and retaliation by December 7

The Federal Trade Commission and the U.S. Department of Agriculture announced a joint request for information on October 7, inviting farmers, independent repair providers, and current and former employees of agricultural equipment manufacturers and dealers to document restrictions and retaliation. The request, docket FTC-2026-1585, poses 13 numbered questions. Comments go through Regulations.gov and are due by December 7, 2026, at 11:59 p.m. ET.

Why it matters: Farmers, repair providers and dealer employees can put documented restrictions, penalties or retaliation before the FTC and USDA.
What to watch: Comments under FTC-2026-1585 must be received by December 7, 2026, 11:59 p.m. Eastern. Read the separate instructions before submitting confidential material.

The limit. The request names no manufacturer as a subject and commits to no particular enforcement action. An invitation to report conduct is not a finding.

How this record was read

Read October 8 Arizona time. Fetched directly by curl: the FTC press release (ftc.gov, HTTP 200) and the Request for Public Comments PDF it links to (ftc.gov/system/files, HTTP 200, text extracted with pdftotext). The regulations.gov docket page itself was never read as a document: it returned a 403 block page to curl, and to a browser-user-agent fetch a JavaScript application shell with no content. The docket's existence, title and comment-period dates were instead confirmed through regulations.gov's own public v4 API (api.regulations.gov), which also lists an earlier entry, FTC-2026-1585-0001, with a withdrawn flag set to true; no document read gives a reason for that. Limits: this desk did not read the full text of the Corteva or Deere settlement orders, only the press release's own description of them.

02 / Read the record

Rules still being written

Mail, laboratories, vehicle lighting and trade: a proposal or a comment request does not itself change the rule.

Proposed rule · no effective date3 min read · 2 source receipts

Customs proposes a new electronic entry type for mail packages valued at $2,500 or less, with filing due on arrival, a tracking number and a bond

U.S. Customs and Border Protection proposed a rule October 8 that would require electronic filing, a bond and a carrier-reported tracking number for low-value shipments — goods whose shipment value is $2,500 or less — including a new entry type for those arriving by mail. Packages would need to be entered before or on arrival instead of within 15 days, and an unentered mail article would be treated as abandoned after 15 days. Comments are due by December 7, 2026.

Why it matters: Importers and carriers would face earlier electronic entry, additional data and bond requirements for shipments worth $2,500 or less.
What to watch: Comments must be received by December 7, 2026. The analysis models a 2027 start; that assumption is not an announced effective date.

The limit. The report does not audit the full cost-model methodology. A proposed abandonment rule is not a current instruction about a particular package.

How this record was read

Read October 8 Arizona time; curl worked directly against federalregister.gov. Fetched the full plain-text document (2026-20650.txt, pages 64532-64563) and the Federal Register API record for the same document (abstract, dates, docket, citation). Limits: this record does not cover the cost-benefit tables' full methodology, the Paperwork Reduction Act or Regulatory Flexibility Act sections, or the related interim final rules and Entry Type 13 test notices the document references but does not reprint.

Proposed rule · comments open3 min read · 2 source receipts

CMS proposes letting lab staff review most test data remotely, but not cytology, and to drop a COVID-era reporting rule

CMS and the CDC proposed a rule October 8 that would let laboratory personnel review most digital test data and images from off-site under their lab's existing certificate, with cytology excluded. It would also allow digital images of slides for gynecologic cytology proficiency testing, ease some personnel qualification rules, and rescind SARS-CoV-2 reporting requirements left on the books since the public health emergency ended. Comments must be received by December 7, 2026.

Why it matters: Laboratories could review most digital data away from their premises under the existing certificate, while cytology keeps a separate boundary.
What to watch: CMS-3478-P comments must be received by December 7, 2026. The proposal also addresses personnel rules and obsolete SARS-CoV-2 reporting text.

The limit. These proposed changes are not in effect. The cited earlier rule, guidance memos and outside surveys were not independently read.

How this record was read

Read October 8 Arizona time, fetched directly with curl from the Federal Register's own full-text endpoint (the published document, not a public-inspection copy) and cross-checked against the Register's API record for the same document number. Limits: the federalregister.gov web page itself was not read, since it answers scripts with a CAPTCHA; this desk did not read the cited 2023 CLIA final rule, the 2025 CMS guidance memos, or the outside survey data the proposal cites, and reports only what this document itself says.

Committee notice · future rulemaking3 min read · 2 source receipts

NHTSA proposes a negotiated rulemaking committee of up to 18 members to recommend changes to the rules on vehicle headlights and other lighting; comments and nominations due November 9

NHTSA published a notice October 8 proposing a negotiated-rulemaking committee to recommend changes to FMVSS No. 108, the vehicle-lighting safety standard. It proposes up to 18 members from six stakeholder categories and an agency representative, without saying whether that seat is inside the 18. Comments on the plan are due November 9, 2026, and membership applications the same day by 5 p.m. ET. Consensus recommendations go to the Secretary, who may approve them as submitted or modified, before NHTSA proposes a rule.

Why it matters: The proposed seats and scope shape who would help write recommendations on headlights, glare and related lighting equipment.
What to watch: Comments: November 9, 2026. Membership applications: November 9 by 5 p.m. Eastern. The notice gives separate submission channels.

The limit. The committee is not a new lighting standard. The notice does not resolve whether the NHTSA representative sits inside the proposed 18 seats.

How this record was read

Read October 8 Arizona time; curl fetched the Government Publishing Office's full text of the notice directly from the Federal Register (www.federalregister.gov/documents/full_text/text/2026/10/08/2026-20648.txt), which this desk read in full, and the Register's API record for the same document. Limits: the three email addresses the notice prints — for membership applications, committee-related issues and legal questions — are replaced by an email-protection script in that rendering, so none is quoted here; the federalregister.gov web page answers scripts with a CAPTCHA and was not read; and this desk did not read the committee charter, which the notice says is in the docket, or the text of FMVSS No. 108.

USTR comment request · no enforcement action2 min read · 4 source receipts

USTR asks U.S. producers for EU carbon-border costs and views on possible enforcement action

The U.S. Trade Representative opened a comment window October 8 on how the European Union's carbon-border mechanism affects American producers, workers and exports. It wants evidence of costs, lost sales and effects on jobs, plus views on possible enforcement responses and proposals to cover more products. Comments are due November 9 at 11:59 p.m. Eastern. The notice announces no enforcement action, and the expansion proposals are not enacted law.

Why it matters: U.S. producers and workers are asked for evidence about costs, lost sales and jobs as EU carbon-border obligations reach their exports.
What to watch: USTR-2026-0661 comments close November 9, 2026, 11:59 p.m. Eastern. Expansion proposals described in the notice still require legislation.

The limit. The request announces no enforcement response. Existing CBAM obligations and proposed product expansion must be read separately.

How this record was read

Read October 8 Arizona time. Retained the published Federal Register full text for document 2026-20615, its API record, and the European Commission's CBAM overview and definitive-regime explanatory pages. Limits: the underlying EU legislation and three expansion proposals were not read, so their status and the payment timing below are attributed to USTR's notice. No public comments or regulations.gov docket contents were read. The November 9 deadline and 11:59 p.m. Eastern cutoff are printed in the notice, not calculated.

03 / Read the record

Decisions and their limits

Minutes explain a past vote; oversight describes what had happened by the period GAO reviewed.

GAO report · monitoring as of July 20263 min read · 2 source receipts

GAO reports CMS awarded $10 billion in rural health funding to all 50 states while much of the oversight GAO reviewed is still a plan

A GAO report dated October 6 finds the Centers for Medicare & Medicaid Services awarded $10 billion in rural health funding to all 50 states at the end of 2025, ranging from $147 million for New Jersey to $281 million for Texas. Much of the monitoring GAO reviewed was still planned as of July 2026: CMS officials said they had begun bimonthly state meetings and completed 21 site visits, but no state report had yet come due for review, and audits are planned for 2027. GAO made no recommendations.

Why it matters: The first $10 billion had been awarded to all 50 states. Planned monitoring and completed monitoring are different evidence of oversight.
What to watch: GAO describes future evaluation work and audits planned for 2027. The report's July snapshot does not establish what CMS had completed by October.

The limit. GAO made no recommendations. The underlying funding notice, awards and interview evidence were not independently read.

How this record was read

Read October 8 Arizona time, fetched directly via curl from gao.gov: the product page (https://www.gao.gov/products/gao-27-108853), which gives Published and Publicly Released both as Oct 06, 2026, and the full 11-page report PDF (https://www.gao.gov/assets/gao-27-108853.pdf), text extracted with pdftotext. The report contains no recommendations section and the product page lists none. Limits: this desk did not independently read CMS's underlying notice of funding opportunity, states' notices of award, or the stakeholder-group interviews GAO cites; it relies on GAO's own description of those documents and interviews, and GAO itself attributes several of the completed actions below to CMS officials.

Minutes released · September decision3 min read · 2 source receipts

Minutes of the Fed's FOMC show a unanimous 12-0 vote in September to raise the federal funds target range to 3-3/4 to 4 percent

The Federal Reserve released minutes of the Federal Open Market Committee's September 15-16 meeting on October 7. They show all 12 voting members supported raising the target range for the federal funds rate a quarter percentage point, to 3-3/4 to 4 percent, effective September 17, with none voting against. The minutes record one vote but different reasons: many participants called the higher path prudent on risk-management grounds, a number called it necessary on their own forecasts, and most assessed another increase would likely be appropriate by year end.

Why it matters: The minutes explain the unanimous September rate increase and distinguish voting members from the wider group of participants.
What to watch: The next scheduled meeting is October 27–28, 2026. Views about a later increase are not another rate decision.

The limit. The minutes give no individual reason for each vote. The separately published projections were not read for this report.

How this record was read

Read October 8 Arizona time, fetched directly via curl from federalreserve.gov: the full text of the FOMC minutes for the September 15-16, 2026 meeting, and the October 7 press release page announcing their release. Limits: this desk did not read the Summary of Economic Projections, which the minutes say was released to the public following the conclusion of the September meeting; only the minutes' statement that 18 participants submitted projections was read.

04 / Read the record

Platforms after the date

An elapsed date and a provider's page are evidence about a schedule; neither alone is an endpoint test.

Provider pages read · endpoints not tested3 min read · 17 source receipts

AI-model deadlines came due between September 30 and October 5; some provider pages now record them as past and others still print the earlier status

AI-model deprecation, retirement and billing dates fell between September 30 and October 5, 2026. Reading each provider's own page on October 8: GitHub posted a second changelog entry on October 2 saying four Copilot models were deprecated that day, and Mistral's and Amazon's pages now file their models among retired or end-of-life ones. Microsoft's schedule still tags four models 'Preview', and Google's page shows no shutdown marking for its Antigravity preview.

Why it matters: Teams moving models need to separate provider-recorded retirements, still-future page wording and billing dates across different platforms.
What to watch: Read the selected September 30–October 5 notices against the page states observed October 8. This selection is not a complete count of models or deployments; Gemini's deprecation and retirement dates describe different stages.

The limit. No model endpoint was called. An unread custom-GPT help page is not reported as confirmation, and earlier page metadata may predate the listed event.

How this record was read

Read October 8, 2026 Arizona time, fetched directly from each publisher: Google's Gemini API deprecations page (its own last-updated line reads October 7, 2026), the Gemini API release notes, the Gemini Omni Flash and Antigravity preview model pages, and Google Cloud's Vertex AI deprecations, model-versions and release-notes pages; Mistral's changelogs and models pages; AWS's Bedrock model-lifecycle page plus the Nova Canvas and Nova Reel model cards; OpenAI's API deprecations and pricing pages; Microsoft's Foundry model-retirement-schedule page; and GitHub's Copilot changelog posts of September 3 and October 2, 2026. Limits: no request was made to any model endpoint, so nothing here tests whether a model still answers - every reading is of a page's own text, table field or date line, and a page last edited before a date it lists may not reflect what happened on that date. help.openai.com's custom-GPT retirement FAQ returned an HTTP 403 error on repeated attempts and was not read; nothing from it is reported.

05 / Keep reading

Into the standing files

These dossiers contain source records also cited by the reports above. A shared record establishes this reading connection; it does not imply an allegation or a relationship between people.

A fee proposal.Two ways to read it.

A fee proposal.
Two ways to read it.