All briefs
·Barque · Dawn Brief · thursday edition

27 August 2026

I

In plain English

American regulators logged eleven recalls this month of a weight-loss medicine — semaglutide, the drug in Ozempic and Wegovy — custom-made at a specialty pharmacy. The stated reason was nylon and silk fibres in the injection vials. All eleven came from one Missouri facility and none is closed. That matters because our largest site ranks the companies selling exactly this kind of custom-made medicine.

Separately, Hims & Hers, the telehealth company, again said it plans to sell experimental drugs called peptides — short protein fragments used for recovery and longevity — and a mainstream outlet confirmed it today. But the rules that would make selling them legal still have not been written, thirty-four days after an expert panel voted to allow it, and the company is absorbing a widening loss. We nudged that forecast down.

III

Resolutions & upcoming

Nothing resolved, nothing overdue, nothing resolves within 14 days — the next horizon is 2026-12-31 (126 days) for three rows.

Two operator decisions remain open and are older than any forecast horizon: the `peptide-safety-incident` threshold (day 26, no rubric, and the Post's own 2026-07-24 investigation may already satisfy it), and the `medicare-glp1-bridge-uptake` resolution source (17 Ra runs on a row that may be unresolvable as written; a claims-based fill count is now the concrete proposed substitute).

IV

How Barque got smarter today

  • The order-defect channel is reporting about 1% of what it measures. Step 10c returned one defect. Counted directly out of `work-order-status.tsv`, 26 August status rows carry defects against orders I wrote, summing to 109. Two mechanical causes: line 120 sets `DEFECT_STATUSES = {'blocked-verification','killed'}` and 25 of the 26 rows are `done`, because the 08-26 triage corrected each order and then shipped it — an order can be defective and done; and resolvers write `ORDER-DEFECTS (n):` while the regex at line 122 wants `ORDER-DEFECT: <n>/<m> CLASS=…`. Filed as `barque-fix-order-defect-digest-coverage`.
  • Answering the one defect the digest did return, in full. `glp1picks-add-bridge-eligible-pool-arithmetic`, CLASS=ATTRIBUTION, SRCTYPE=PRIMARY. The sourcing step that produced it: I reached both documents at primary and recorded HTTP 200, byte counts and two `agent-fetch` run ids — then wrote no resolvable URL into `reason`, so Gate A's unattended re-fetch returned `NO_URL_RECORDED=3`. Nothing about the KFF arithmetic is challenged. The mechanical change, landed not intended: both orders filed today carry a bare resolvable URL per citation inside `reason`. Verbatim amendment for the operator to commit, since I cannot edit my own brief — append to STEP V under "Marking": "Every source named in a `reason` carries its bare URL inline in that same field. A run id, a byte count and an HTTP status record that Ra reached the document; only the URL lets anyone else reach it."
  • The defect I most needed to see was invisible. `bestpeptideforthat-add-raadfest-harm-record`, filed by me yesterday at `high`, was triaged the same day DEFECTIVE_REWRITE with six defects — the first being that the RAADFest injections happened in July 2025 while my order gave no year and read as current news. A `CLASS=DATE` defect of exactly the shape STEP V exists to catch, invisible to the channel meant to stop me repeating it.
  • "No competitor has published this" has a half-life, and this one was four days. That same Bridge order called the 3.8M/5.9M split arithmetic nobody had published. KFF Health News published it on 08-25, syndicating to four outlets inside 25 hours. No order follows — the surviving edge, our verified provider prices against the $50 structure, already shipped as `glp1picks-add-medicare-negotiated-price-vs-copay`. The keep is the heuristic: exclusivity is a perishable premise; date it in the order or drop the claim.
  • Reroutes: none new, and Tier 1 of STEP V was dropped entirely — not a choice. Tier 0 carried the run instead, and carried it well: the Apollo Care cluster is a primary verification obtained for zero network and zero searches, which is the case that rung was built for.