PUBLICATION BLOCKED — 2026-08-23, certifier round-13 findings R13-9 and R13-10. This article states a docket comment count ("eight"), and the filing checklist forbids that in any article until the filing-day preempt re-run is done and its line (d) is written: "Until (d) is written, the preempt finding is UNVERIFIED and no comment count may be stated in the filing, in any article, or in any external record." The last real count is 2026-08-21 and the box is deliberately unchecked. It also said the comment asks that two provisions be conformed — false since FR-20 withdrew Recommendation 2 on 8/22; corrected above, and it was committed wrong earlier the same day, which is the correction-reaches-the-draft-not-the-derived-artifact pattern again. Now mechanical, not just a note (2026-08-23). scripts/ledger_predicates.py article-census-current used to compare the article's count against _comment_archive.jsonl and pass. Matching a snapshot is not currency, so the check now also bounds the archive's age (STALE_CENSUS_DAYS = 3, the watch runs daily). It is currently RED: the archive's newest read_on is 2026-08-11, twelve days old. Mutation-tested — relaxing the limit turns it green and nothing else changes.

Provenance discrepancy found while wiring that up, recorded rather than smoothed: the draft's own header comment says "re-read 2026-08-20 (8 unique documents)", and no row in the archive carries a read_on later than 2026-08-11 (distribution: 07-30 ×6, 08-09 ×6, 08-11 ×2, 08-08 ×1). Comment metadata may have been re-checked on 8/20 without the full re-read the line claims. Treat the 8/20 re-read as UNVERIFIED until the filing-day re-pull, which supersedes it anyway.

Do not publish until: the preempt re-run is done on filing day, the counts are re-verified against what the docket actually holds that morning, and the filing itself has been submitted (FR-28: file first, then publish).

We Filed on the C-UAS Rule. Here Is What We Said — and Why the Agency Column Is Still Empty.

The federal docket that will shape state and local counter-drone operations for a decade closes September 4. We filed. Almost nobody else has, and no law enforcement agency has at all.

By Brian Rutherford | (publish date set at publish — do not fill by hand)

Bottom Line Up Front: The interim final rule implementing the SAFER SKIES Act (Docket FBI-2026-0001) closes for public comment on September 4, 2026. It decides how state, local, tribal, and territorial agencies get trained, certified, audited, and equipped to counter drones. We filed a comment on it. We also read every other comment on the docket, in full, including attachments — there are eight, and zero come from a police department, sheriff's office, corrections agency, or law enforcement association. The people this rule was written for are not in the room, and we would rather tell you that having taken our own advice than before.

What we filed, and what we deliberately did not

Our comment is narrow and technical. It asks that one provision be conformed to a duty the rule already imposes elsewhere in its own text — a drafting inconsistency, not a policy disagreement. We filed it because it is the thing we could speak to with evidence, and because a comment that argues past what its author actually knows is worth less than no comment at all.

It is not the comment this docket is missing. Ours says nothing about staffing a night shift, about what a two-tier certification does to a department with one qualified operator, or about what an audit costs an agency that has never been audited on this. Those are the operator's-side facts, and they cannot come from us. They have to come from an agency, and as of this writing not one has filed.

That is the honest shape of it: we are not observing the silence from outside. We are in the record, and the column that matters is still blank.

What the docket actually contains

I read all eight comments, and every attachment. Here is the full census:

• One vendor selling 12-gauge anti-drone tangler rounds, who filed a spec sheet.
• Five individuals: two with oversight questions (Fourth Amendment concerns, delegation safeguards), one man asking the most practical question on the record — who do I call when there's a drone incursion? — one supporting the rule and asking that it be extended to airport approach and departure paths and to energy infrastructure, and one opposing it as too open-ended to be safe for ordinary citizens.
• One security practitioner with thirty years of critical infrastructure assessment experience, who supports the rule but argues its centralized structure (national schoolhouse, interagency technology lists, layered approvals) is too slow for a threat that iterates in weeks.
• One tribal government (the Habematolel Pomo of Upper Lake), the only governmental commenter of any kind, arguing the rule's "covered facility or asset" scope is too narrow and framing counter-UAS within data sovereignty.

That's it. That's the record, with the clock running to September 4.

Two of those eight arrived on August 10, more than a month after the rule took effect. So the docket is still moving — it is just not moving in the direction you would expect. Every new filing since July has come from an individual. The agency column is still empty.

Why the silence matters

An interim final rule is already in effect. But the comment record shapes the final rule, and agencies that stay silent inherit whatever the record produces. Three ways to read the quiet:

1. The lawyers are still writing. Institutional commenters routinely file in the last two weeks. If the associations (IACP, the sheriffs' associations, the corrections community) are coming, they arrive late. That is the normal pattern.
2. Agencies assume someone else is handling it. Associations file so departments don't have to. Maybe. But on the parallel FAA drone rulemaking, nearly 3,929 comments got filed and individual sheriff's offices and fire districts showed up in person. They know how to comment when they're paying attention.
3. Agencies don't know this rule exists. The uncomfortable reading, and the one my time in this space keeps confirming. The SAFER SKIES Act passed inside a 1,000-page defense bill in December. The implementing rule dropped July 1. Most departments are absorbing it (if at all) through vendor marketing, not through the Federal Register.

Whichever reading is right, the outcome is the same. The rule that governs your training pipeline, your operations plan requirements, your audit obligations, and your technology options is being finalized on a record you didn't touch.

What agencies give up by not filing

The comments already on the docket press hard in one direction: more oversight, more safeguards, more judicial process around delegated authority. Those are legitimate concerns and some belong in the final rule. But nobody is filing the operator's side of the ledger. Nobody has told DOJ and DHS, on the record, what a 40-officer department can realistically staff. Nobody has said whether the certification structure works for a rural sheriff who shares a region with three other agencies. Nobody has flagged what mutual aid actually looks like at 2 a.m. when the drone is over the jail now.

Regulators cannot weigh input they never receive. A docket full of oversight concerns and empty of operational reality produces a final rule tilted exactly the way you'd expect.

What to do before September 4

If you run or advise an agency with counter-UAS exposure (corrections, stadium venues, critical infrastructure response, border-adjacent jurisdictions), three moves before September 4:

1. Read the rule itself, not a summary. It's 6 CFR Part 124, and the two-tier structure (detection versus mitigation certification) is the piece most coverage gets wrong.
2. File a comment, even a short one. A two-paragraph comment from a working sheriff describing staffing reality carries more weight in this record than anything a consultant writes. The docket takes submissions at regulations.gov until September 4.
3. If you can't file, get your association to. Ask your state chiefs' or sheriffs' association whether they're commenting. The question itself moves the system.

We watch this docket daily and read every comment in full, including attachments. When the first agency or association files, that changes the record's character, and we'll report it.

(Where DELALLi sits in this: we educate and prepare agencies for what the rule requires. We do not certify anyone. Certification of mitigation authority runs through the FBI's National Counter-UAS Training Center (NCUTC), and nowhere else.)