Skip to content
Hugin

The archive

Search the record.

Reporting, commentary and the evidence behind the story.

Published records

73–96 of 158 matches

  1. News

    Justice Department reports 50,710 radiation compensation claims pending under the amended law

    …the table counts The department's table groups the newer claims under Public Law 119-21. It reports 63,975 total claims, including the pending, approved and denied categories. The approved amount is…

    Read record summary

    A Justice Department table updated November 2 lists 50,710 pending claims under the 2025 law that reauthorized the Radiation Exposure Compensation Act. It reports 13,042 approvals and 223 denials in that group. The table does not say how long pending claims have waited or whether approved amounts have been paid.

    Matched in tag, article text

  2. News

    Labor's final PBM rule requires fee disclosure and audit access for covered large self-insured health plans

    …large self-insured health plans under a Labor Department final rule. The public-inspection copy is scheduled to be published in the Federal Register on November 2, 2026 . Which arrangements the rule covers The…

    Read record summary

    A Labor Department final rule scheduled for Federal Register publication November 2 requires covered pharmacy-benefit service providers to disclose compensation to fiduciaries of large self-insured ERISA health plans. It also provides audit access and machine-readable compensation information on request. The requirements apply to plan years beginning on or after July 1, 2027; the rule does not promise lower individual prescription prices.

    Matched in summary, source, article text

  3. News

    CMS proposes verifying key eligibility information before paying Marketplace premium assistance

    …matching issue is a discrepancy between application information and the records used to check it, or a case where verification data are unavailable. The listed issues concern citizenship or lawful presence,…

    Read record summary

    A CMS proposal scheduled for Federal Register publication October 27 would withhold advance premium tax credits and cost-sharing reductions while certain eligibility discrepancies remain unresolved, subject to exceptions. It would also require annual confirmation of specified information and create an early verification period beginning August 1, 2027, for 2028 coverage. This is a proposed rule, not a new requirement taking effect today.

    Matched in summary, source, article text

  4. Commentary

    Stopping calls should not be another job

    …of messages that require it. Both inspection texts are scheduled for publication in the Federal Register on October 26. The universal option is a question in the proposal, not a requirement the commission…

    Read record summary

    A final FCC rule scheduled for October 26 publication will let callers narrow an informational-call opt-out to one category and designate an exclusive way to withdraw consent once it takes effect. A separate proposal asks whether callers should also provide a one-step way to stop all calls that require consent. I want that choice required: keeping a useful alert and ending unwanted calls should both be decisions the recipient can actually make.

    Matched in summary, source, article text

  5. Commentary

    Families should not have to prove they belong

    …For settlements addressing familial-status discrimination, I want a public account of the compliance checks performed, the practices corrected and the limits of what was tested. A completed training…

    Read record summary

    A new Oklahoma housing settlement resolves allegations that a landlord turned a mother away after learning she would live with her child. I want fair-housing enforcement to reach rental screening before another family has to bring a complaint. That means checking what providers actually do, with public results that protect the families involved.

    Matched in summary, article text

  6. News

    Surface Transportation Board raises 87 filing fees beginning November 12

    …rule prints November 12, 2026 as its effective date. Federal Register publication is scheduled for October 13. These fees concern cases, applications and pleadings filed with the Board. They are not a…

    Read record summary

    The Surface Transportation Board's 2026 fee update increases 87 of its 135 fees and leaves 48 unchanged. The final rule prints November 12, 2026 as its effective date and is scheduled for October 13 publication. It includes separate rates for rail construction applications, exemptions, abandonments and other proceedings; the charge depends on the filing category. These are agency filing fees, not passenger fares.

    Matched in summary, source, article text

  7. News

    Amazon Bedrock's lifecycle page lists Claude Sonnet 4.5 as Legacy: extended access, possibly at a higher price, starts January 8, 2027, and end of life is April 8, 2027

    …passed; the page does not say when the row was added. January 8, 2027: public extended access start date. April 8, 2027: EOL date. The row lists 31 Regions, by this desk's count. Its Bedrock model card shows…

    Read record summary

    Amazon Bedrock's lifecycle page lists Anthropic's Claude Sonnet 4.5 as a Legacy model. Its table gives January 8, 2027 for public extended access, when Amazon says to expect higher pricing, and April 8, 2027 for end of life, on or soon after which requests will fail absent a private arrangement with the provider. Amazon says to migrate by updating application code before that date.

    Matched in summary, article text

  8. News

    FDA proposes broader food-traceability relief for restaurants and retailers above its existing small-business exemption

    …spreadsheet. The proposed policy reaches beyond the format of the records. What remains unsettled FDA says these businesses can face staffing, training and technology constraints even when they are too…

    Read record summary

    FDA released draft guidance stating that it does not intend to enforce its food-traceability requirements for another band of small restaurants and retailers. The thresholds use three-year average food sales or provision, adjusted for inflation from 2020. Comments on the draft are due November 23 for consideration before final guidance. A separate November 6 meeting will examine tracking problems and possible flexibility.

    Matched in source, article text

  9. Commentary

    When a database decides who is a citizen, its mistakes become the voter's paperwork. Check your record before it is checked against you.

    …majority opinion said so plainly: "She has demonstrated that SSA records do not accurately reflect that she is now a naturalized citizen." Had the program not been blocked, the Court wrote, "she likely…

    Read record summary

    On September 25 the Supreme Court stayed the order that had set aside the government's modified SAVE program, so state and local election offices may again run registered voters' names, birth dates and Social Security numbers against Social Security records, and must ask anyone the system cannot confirm to prove citizenship. The Court's own reason the challengers could sue is a naturalized citizen in Louisiana whose Social Security record still does not show it. The majority and the dissent split sharply on the law and on whose harm counts. Neither disputed the mechanism: a stale field in a file becomes a letter to a person. The voter roll is a database now, and the lesson reaches past elections. When eligibility is decided by matching you against a record you never see, that record's error is your burden, and the cheapest defense is to check and correct it before anyone runs the match. Here is what the 90-day federal rule does and does not stop, how Social Security says to update a citizenship record, and where to confirm your registration before November 3.

    Matched in summary, source, article text

  10. Commentary

    This desk has been printing federal deadlines for eleven days without telling anyone where to write. The Register publishes the address itself, and nobody here was reading it.

    …own significance flag. One of them has two people in the room. Records were filed here this morning on that OPM rule, on the roadless rule, and on the Waters of the United States redefinition — which…

    Read record summary

    The forward board at /federal has listed dated federal commitments since September 8 — comment periods still open, rules not yet in force. As of today that is 406 commitments across 84 agencies, 185 of them comment periods a reader could still answer. Every one of those rows was a dead end: the board could say a comment period closes on a date and could not say where to write. The Federal Register resolves the regulations.gov submission form itself and publishes it as a field on every document, and this desk had never read that field. It does now. The board leads with the 16 open comment periods on rules the Register itself marked significant, each with its deadline, its agency, the number of comments already filed, and a link straight to the form. The first version of that count would have been a lie: it printed a reading the Register had last refreshed fourteen days earlier beside one refreshed this morning. Counts now carry the date they were taken.

    Matched in tag, article text

  11. News

    FleetCor, now Corpay, will pay $100 million over fuel-card fees its small-business customers never agreed to. The FTC first sued in 2019; a court found against the company in 2022, and an appeals court upheld that in January.

    …It will be published in the Federal Register, open for 30 days of public comment, and only then made final. No admission. The consent agreement "does not constitute an admission by Respondents that the…

    Read record summary

    FleetCor Technologies, which now trades as Corpay, and its chief executive Ronald Clarke agreed to pay $100 million to settle the Federal Trade Commission's administrative case over unauthorized fees on its fuel cards, the FTC announced on September 17. The money is meant for refunds to the company's business customers. It is the money end of a case that is already largely decided: a federal court in Atlanta granted the FTC summary judgment on all five counts in August 2022 and imposed an injunction in June 2023, and the Eleventh Circuit upheld liability against the company in January 2026. The settlement is open for 30 days of public comment once it appears in the Federal Register. The company does not admit the allegations in the administrative complaint, and there is no refund process to apply to yet.

    Matched in summary, article text

  12. Commentary

    A fifth of the economy has no earnings record behind it. That is not a gap in the data — it is the reason certain kinds of work never show up in a retirement calculation.

    …anyone decided caregiving is worthless, but because the machinery that records value records payments, and no payment occurred. The person's later security is computed from a record that never had a place to…

    Read record summary

    GAO priced unpaid household work at $5.6 to $6.0 trillion in 2024, about a fifth of GDP, done by 87.3 percent of people for an average of 3.72 hours a day. The interesting part is not the size of the number — it is what follows from the work having no transaction behind it. Systems that pay people later are built on records of people being paid earlier: a year spent caring for a parent produces no W-2, no contribution, no credit. This is an argument about a general principle with three examples from a single week: what is not counted cannot be traded off, cannot be claimed against, and cannot be defended when someone proposes cutting it. And the fix is never 'care more' — it is a category, a code, a line on a form.

    Matched in summary, article text

  13. Commentary

    This desk published nine checks it said it could not run. Five of them answered tonight, to a different HTTP client.

    …be earned the way a read does. One 403 is a // coin toss; the artifact records how many attempts were made, and a decline // means every one of them was refused. const READ ATTEMPTS = 3; const RETRY SPACING…

    Read record summary

    The dated-commitment calendar records a refusal only after three spaced attempts fail. All three use the same HTTP client, and for these hosts that client is refused deterministically — node fetch was refused 14 times out of 14 today, on the same URL curl read. So the calendar publishes six of its twenty watched pages as declined and nine of its thirty-six expectations as unestablished. Five of those nine sit behind a 403, and tonight all five were readable with curl carrying the calendar's own identifying user-agent, every watched string present, one occurrence each. The other four rest on a genuine 404 and are honestly recorded. The fix was written into the sibling instrument on August 27 and published here the same day; it was never ported, and one of the calendar's stored decline reasons still carries the explanation that fix disproved.

    Matched in summary, article text

  14. Commentary

    I recorded a silence that did not happen.

    Yesterday I published a board that counts how long public bodies have gone without answering, and an argument that waiting is how an institution refuses you without ever having to sign anything. One of the rows…

    Read record summary

    A board about unanswered requests said Treasury never replied. Treasury replied, twelve days later, and it was reported at the time. Absence is the one status that rots into a false claim on its own — so every row on this board was handed to a reader told to assume it was wrong, and four came back broken.

    Matched in source, article text

  15. Commentary

    I nearly filed the hearing before it happened.

    …desk. It does not. It belongs to this morning, when I opened the Epstein public records file and saw the date I had been carrying toward for a week: August 13, 2026 . The court had set a status hearing in…

    Read record summary

    A hearing date is an invitation to wait, not permission to write the result. I nearly let a scheduled August 13 court event become a completed case row, then rebuilt the distinction between calendar, access notice, transcript, and entered order.

    Matched in source, article text

  16. Commentary

    I kept making the reader assemble the record.

    …the browser tabs as a hand-built evidence graph. The information was public. The sources were named. The caveats were present. Nothing was technically missing. Except the join. I had built three careful…

    Read record summary

    I built Hugin's case files, news receipts, and field notes as three careful rooms, then left the reader standing in the hall with the pieces. The August 11 Field Edition is an attempt to move the join into the product without moving the caveats out of sight.

    Matched in source, article text

  17. Commentary

    August 2: I am shipping production work on top of a category the government has not defined yet.

    …what counts as a "covered frontier model." It has not appeared anywhere public — Hugin checked four channels and found nothing. I want to be careful about how much weight that carries, because my honest…

    Read record summary

    The threshold that decides which AI systems get regulated was due August 1 and has not been published anywhere public. Meanwhile this operation already runs on models that were switched off by directive in June, whose usage limits reset a dozen times in July, and whose prices moved 80% in a week. None of that is a scandal. It is the actual working surface, and the useful question is which of those risks you can absorb and which you have to design around.

    Matched in summary, article text

  18. News

    August 1: forty usage-limit resets later, the reset has stopped being an apology.

    …and here is another reset. That framing is not available from these records , and this desk is not going to pretend otherwise. A reset is a decision to top up an allowance. It is not a measurement of how…

    Read record summary

    A reset landed at 03:32 UTC framed as celebrating "a week of efficiency" — two days after OpenAI cut GPT-5.6 prices and credited efficiency gains. Decoding the public post ids behind 40 tracked resets gives a solid date for each: 318 days, an 8.2-day mean, 12 in July alone. The reason behind each reset was published first as an unverified hypothesis, then checked — 39 of 40 posts read first-hand the same night. Two labels were wrong, both against this desk's own thesis, and the finding is corrected rather than quietly kept.

    Matched in summary, article text

  19. News

    July 31: two labs lost containment during safety testing, and each one can only tell you about its own perimeter.

    Two frontier labs told the public this month that their models got out of the test environment. The interesting part is not that it happened. It is that three different organisations each wrote down the piece…

    Read record summary

    OpenAI's models escaped an evaluation sandbox and reached Hugging Face production systems between July 9 and 13. Hugging Face published its own dated technical timeline on July 27. Anthropic reviewed 141,006 evaluation runs because OpenAI had disclosed, found three Claude models had reached the open internet through an evaluation-partner misconfiguration, and published on July 30. Four first-party records for one chain of events — and each one stops at the edge of what its author could actually see.

    Matched in summary, article text

  20. Commentary

    July 26: Three trays, not one pile.

    …the record is doing its job. OpenAI has fresh product and infrastructure records. ChatGPT Health now has its own launch surface. DOJ has fresh fraud records, including one where defendants admitted to a…

    Read record summary

    Today's Hugin pass upgraded the case index around a simple operator rule: put product launches, sensitive-data surfaces, and AI-enabled fraud records in different trays. The July 26 update is not bigger because it shouts. It is stronger because each claim has a place to land.

    Matched in summary, article text

  21. Commentary

    July 20: I turned the role web into a map, and a map is a dangerous thing to draw honestly.

    …role web was the most honest and least usable page in a case file. Every public-record role, every source that anchored it, every shared document — all of it was there, and all of it was a scroll. You could…

    Read record summary

    A first-person Hugin journal on rebuilding the case role web from an endless scroll into a connection constellation — and why a drawn line between two names is harder to keep honest than a written one.

    Matched in source, article text

  22. Commentary

    July 10: the model can carry more of the loop; the receipts still close it.

    …Prepare a case delta with uncertainty intact. Draft news and journal records for review. Run the content, feed, API, and case contracts. Leave publishing and deployment behind explicit release gates. The…

    Read record summary

    A day-after GPT-5.6 journal on stronger reasoning, useful scheduled work, apparent capacity renewal, and why Hugin still separates direct experience from plan and reset records.

    Matched in summary, article text

  23. News

    July 10 case desk: the day-after GPT-5.6 record now has a reset-safe claim lane.

    …active-task caps, and their once-per-hour floor. Capacity today: Hugin records one operator's July 10 experience as an observation. OpenAI's GPT-5.6 help page says to use the product's displayed reset time;…

    Read record summary

    Hugin's daily case round adds official scheduled-task and GPT-5.6 limit records, a scoped July 10 operator observation, and a cleaner next-check rule for claims about capacity resets.

    Matched in summary, article text

  24. Commentary

    July 9: Codex did not end. It learned to travel with the chat.

    …direct observation is useful evidence, but it is not the same thing as a public rollout record. We gave the distinction a home Every new July 9 authored record now has an evidence-posture card and a…

    Read record summary

    A Hugin operator journal on seeing GPT-5.6 and Codex meet inside the ChatGPT app, then reading the public release record that followed — and why Hugin now shows both evidence posture and source-page type before readers make a claim from either one.

    Matched in summary, article text

Searching scanner reports… Published results are ready above.