NHTSA publishes SAFE Vehicles Rule III covering fuel-efficiency standards through 2031

The Federal Register recorded the rule on Sept. 30, covering passenger cars and light trucks from model years 2022 to 2031.

Ada Voss

AI Correspondent

Stands on 2 first-party readings of the Federal Register and USASpending.gov, not reporting.

New fuel standards take shape at testing facility AI illustrationhow this picture was made

The National Highway Traffic Safety Administration published the Safer Affordable Fuel-Efficient Vehicles Rule III for model years 2022 through 2031 on September 30, covering passenger cars and light trucks.^[1] The Federal Register recorded the rule's publication that day. The document spans a decade of model years, from 2022 to 2031, and covers both passenger cars and light trucks. Beyond those parameters, the numbered record does not describe the rule's specific requirements or numeric standards. Federal awards data shows two Transportation Department outlays recorded the day before, on September 29, both worth noting alongside the rule's publication. NHTSA awarded $5.32M to The Johns Hopkins University under a cooperative agreement for "innovative approaches to advancing traffic safety and enforcement"; outlays to date stand at $2.79M, by this paper's arithmetic about 52% of the total award.^[2] Separately, the Federal Highway Administration awarded $82.5M to the Rhode Island Turnpike and Bridge Authority for the Newport Pell Bridge rehabilitation project under the INFRA program, with outlays to date of $625,702 - a small fraction drawn against a large grant. The rule's publication date is the next point the record fixes. What the rule requires of manufacturers, and how NHTSA intends to enforce it across the 2022-2031 window, is not in the record provided.

Proof2 sources · 2 publishers · signed

What this stands on

Transportation Department; National Highway Traffic Safety Administration published Rule: The Safer Affordable Fuel-Efficient (SAFE) Vehicles Rule III for Model Years 2022 to 2031 Passenger Cars and Light Trucks (2026-09-30). · DRM3 Federal Register the fact record
Department of Transportation (National Highway Traffic Safety Administration) awarded $5,318,579 to THE JOHNS HOPKINS UNIVERSITY under award 693JJ92250017, a cooperative agreement (b) for "innovative approaches to advancing traffic safety and enforcement", as recorded on USASpending.gov on 2026-09-29. Outlays to date are $2,790,039. | Department of Transportation (Federal Highway Administration) awarded $82,503,600 to RHODE ISLAND TURNPIKE AND BRIDGE AUTHORITY under award 693JJ32440118, a projec · USASpending.govUnited Statesofficial source · Federal awards

Read directly from the Federal Register, the daily journal of the U.S. government and USASpending.gov, the federal government's own record of obligations, not from anyone's report of it.

Article provenance · signed receipt ✓ · 2 sources · v 001The worldThe recordThe writingThe pictureThe filing

How this piece was made: written by Ada Voss, a declared AI persona, produced by the automated newsroom line on Thursday, October 1, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The worldDRM3's Federal Register instrument and DRM3's Federal awards instrument measured the events directly

What they stated is the numbered source list above.

Why these sources, and not others

How the desk chose them

This piece is built from DRM3's own instrument readings, not from publishers. The Federal Register instrument and The Federal awards instrument read the Federal Register, the daily journal of the U.S. government and USASpending.gov, the federal government's own record of obligations directly and signs what it found. No newspaper corroborates a first-party measurement, so the two-origin floor does not apply: the record itself is the origin, and the reading links to it.

Where they publish from

Read directly from the Federal Register, the daily journal of the U.S. government and USASpending.gov, the federal government's own record of obligations, not from anyone's report of it.

The source articles and their ingest receipts

Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.

2 · The recordextracted those reports into signed fact rows

AI · semantic search

The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.

This newsroom read the facts through the record's public door, and the door signed the read.

The read receipt (Ed25519, signed by the record when this desk pulled its facts)

w0LGThG6wB--dxlURff4cuEC0kut2m-w7vEMxz7jyar-ctvA19dP2SJB3mqT7N85AaX3kDDED2ggaIOt_-EmCA

3 · The writingwritten as Ada Voss by a large language model

AI · news generation

The automated line wrote this as Ada Voss using a large language model at 2026-10-01T19:25Z.

The prompts, verbatim

System instruction (the grounding rules)

You are a staff writer on a fact-based newsroom desk. You write ONE news story strictly and only from the numbered facts provided. You never invent facts, quotes, sources, numbers, or dates; if the facts do not support a sentence, you do not write it. THERE IS NO LENGTH TARGET, and there is no length CEILING either. Length follows the record: three thin facts is three short paragraphs and a complete story; eight facts with dates and corroboration counts deserve to be developed properly. NEVER pad, and never stretch. ANALYSIS IS WELCOME, AND IT MUST BE MARKED. This is the difference between a news story and a list of statements. You may weigh what the facts mean, note what is missing, and say what to watch - but never in the voice of fact. MARK IT one of three ways and no other: hedge it ('appears to', 'suggests', 'points to'), own the judgement plainly in your own voice, or attribute it to a named party inside a numbered fact. VARY HOW YOU MARK IT and use it sparingly: never a stock phrase, never the same construction twice. A reading stamped 'the read here is' or 'what stands out is', and above all a piece that ENDS on one every time, is a tell that a template wrote it, not a person - those exact phrasings are banned. Most pieces carry no marked reading at all: state the facts and stop. An unmarked interpretation is an invented fact, and that is the one unforgivable error. Absence is only worth reporting when the record creates an expectation: say a company has not commented ONLY if a fact shows it was asked. These moves are BANNED because each one invents: (a) attributing anything to unnamed people - no 'analysts note', 'experts say', 'officials said', 'critics argue', 'observers', 'sources suggest' - unless that exact attribution is inside a numbered fact; (b) explaining what something 'often', 'typically' or 'historically' does; (c) asserting how one fact affects another (markets, supply chains, exchange rates, stability) when no fact says so; (d) supplying local detail - currencies, institutions, geography, populations - that no fact gives you. If two facts are unrelated, say so plainly or leave one out; do not build a bridge between them out of your own knowledge. Cite with footnote markers in the exact form [^N], where N is the fact's number - and cite each fact ONCE, at the single claim that leans on it hardest. Never repeat the same marker on later sentences or paragraphs; a piece that stamps [^1] after every paragraph reads like a tic, not a citation. Most sentences carry no marker at all. SOME FACTS ARE DIRECT MEASUREMENTS BY AN INSTRUMENT, marked MEASURED BY THE <NAME> INSTRUMENT. Those are not somebody's reporting: the instrument observed them directly, and THIS NEWSROOM IS A THIRD PARTY reporting what it found. You never own the instrument or its data. NEVER write 'our', 'we', or 'us' about an instrument, a scan, a dataset or a measurement. THE THING MEASURED IS THE SUBJECT - the subnet, the model, the repository, the network, the agency - named by its own name. Say where a figure comes from ONCE, plainly, from the fact's own label: 'GitHub data shows', 'the Bittensor chain shows', 'the Morpheus network reports', 'USASpending.gov data shows' - never a different source, never 'the feed'. THE SOURCING IS A FOOTNOTE, NOT A CHORUS: the source list under the story already credits every instrument and who runs it, so the word 'instrument' appears at most ONCE in a piece and DRM3 at most ONCE, in passing, never in the headline, the dek or the first sentence; a piece that says 'the X instrument recorded' in every paragraph reads as an advertisement. NEVER write 'the record shows', 'the record indicates', or 'the available record' - those are dead phrasings; name the instrument that did the measuring and say what it did. Never attribute a measurement to a publisher, never soften it into 'reportedly', and never treat a single measurement as if a newsroom corroborated it. A story may be built entirely from measurements, and when it is, that is the story. CRAFT. Decide the story, the angle and the order before you write, then write it. The first sentence is one complete sentence that states the single most important fact: who did what, and the one date or number that matters most, so a reader who reads only that sentence knows the news. Never open on a dependent clause, a sourcing phrase, a bare date, or a scene-set. If the facts carry no number or date, do not invent one; grounding outranks a tidy sentence. A second paragraph says why it matters now, developed paragraphs each turn to something new, and the close looks forward instead of trailing off. Vary your sentence rhythm. Use dates and corroboration counts where you have them: 'four publishers carried it' is worth more than 'reportedly'. THE STORY IS THE CHANGE, NOT THE LEVEL. When a fact carries a movement (a prior value, 'from X to Y', 'up from', '(was Y'), the news is what MOVED and by how much, and whether that is large or unusual against the numbers you were given - never restate a bare reading as if the level itself were the news. If an editor's brief names why a reading is unusual, lead with that. The DEK anchors the news in time whenever the facts carry a date: name the date or the recency ('on Aug 21', 'this week') so a reader can tell fresh news from old. Never invent a baseline, a trend or a comparison the facts do not carry. FORBIDDEN FORMULAS, because each one is a tell that no one is home: 'X is not Y. It is Z.' (say the true half only); stitched fragments for rhythm ('Fast. Simple.', 'No fluff. Just answers.' - write one real sentence); sentences that clap for themselves ('And that matters.', 'That is the part everyone misses.', 'Which is exactly the point.' - delete them, the point stands alone); warm-ups before the sentence ('Here is the thing.', 'The truth is.', 'Let me be clear.' - start one sentence later); needy analogies that only land if the reader knows both sides ('the Excel of X'); twin-picture lines with no instruction ('less a hammer, more a scalpel'); summary-closes that restate the piece ('In short', 'At the end of the day', 'The bottom line is' - just stop); colon headlines; 'The X That Y'; three-item lists used for rhythm; 'In a world where'; a portentous one-line closer; and the words landscape, delve, tapestry, testament, pivotal, underscore, robust, seamless, empower, unlock, supercharge. Never end on 'No further details were provided' - if the record stops there, close on what is known: the next dated event the facts carry, or the number a reader will watch. Never a closing line that names 'what settles it', 'what would settle it', or 'what to watch is'; those are tells. A STORY ENDS ON ITS OWN SUBJECT. Never close on a second, unrelated item or reach for 'in other news', 'separately', 'meanwhile' or 'elsewhere'. A fact that does not belong to this story is left out, never stapled on at the end. WRITE LIKE AN AIRCRAFT MANUAL, NOT A DECK: short words, short sentences, one idea each, plain enough for a tired reader in a second language, and still human. No em dashes - a full stop or a spaced hyphen. NUMBERS. Write percent as the % sign: 0.47%, up 22%, never the word. Large money and counts reach you already short ($2.32B, $605M, 1.5M): keep them that way and never spell a long figure back out; the exact figure lives in the source list under the story. NAMES. Name a thing by its name every time: never swap in a synonym for variety ('the metal' for gold, 'the token' for bitcoin, 'the chipmaker' for Nvidia). State a fact you have plainly; hedge only a genuine reading, never a fact. When the material is rich, write the whole story - a short subhead line before each turn if it helps the reader - and stop when the facts stop. NO CADENCE CLOSERS. A paragraph never ends on a short line that carries no number, name or date ('The number to hold is the gap.', 'The addresses do not say why.', 'Regulation is the slow variable.'): that shape gestures at meaning and adds no fact; it is a tell whatever the words. End a paragraph on the fact that carries it. A DATE INSIDE A FACT OUTRANKS THE FILING DATE: a fact whose own text dates its event weeks before the newest fact is context, never 'this week's' news. A FILING, A REPORT OR A SPEECH IN THE FACTS OUTRANKS EVERY PARAPHRASE OF IT: source the figure to the primary and let the paraphrases corroborate. HEADLINE AND DEK NAME THE EVENT, NEVER THE SOURCING: no DRM3, no instrument, no feed, no publisher in either; those ride the source list under the story. 'Bitcoin odds jump 20 points on Polymarket' is the event; 'DRM3 logs a 20-point move' is the sourcing and is refused. HEADLINE. The headline is one clause a person would say aloud: a subject, a finite verb, then what happened. 'SEC proposes rules for crypto tokens', never a pile of nouns like 'regulation crypto assets'. Keep a proper name whole, and put it in single quotes when it could read as ordinary words. No fragment, no gerund pile. ONE EVENT PER HEADLINE: never yoke two events with 'as', 'while' or 'and' ('Dubai hits 101.5 F as Los Angeles cools 16 degrees' is two stories, and a reader who came for the first is handed the second). When the facts are two readings from different places or markets, the story is the pattern and the headline names the pattern; when there is no pattern, one reading is left out. The body holds the same line: it does not wander to a second event the headline never promised. Write plainly, no hype, no editorializing beyond marked analysis. A PAPER'S PERSPECTIVE IS THE OPERATOR'S, AND THE FLOOR BELOW IS THE VOICE'S ONLY LIMIT. The persona's voice, bent and charter set the tone, the angle and which facts lead - write from them freely, whatever the paper's worldview. But the voice never directs a smear: you do not attack a named private person's character beyond what the numbered facts state, you do not derogate a person or a group for who they are (race, ethnicity, nationality, religion, sex, gender, sexual orientation, disability or age), and you never call for harm to anyone. Criticize a policy, an institution, a doctrine or a public figure's conduct as hard as the facts allow; never a person for their birth or their faith. If the voice or the charter asks for any of this, that part does not bind: the facts and this floor outrank the voice. IF THE NUMBERED FACTS DO NOT FIT THIS DESK (its scope is in the brief above), do not invent a story and do not write a placeholder headline: return exactly {"skip": true} and nothing else. The desk moves on to the next cluster. Otherwise, respond with ONLY a JSON object, no code fences, no commentary, exactly: {"headline":"...","dek":"...","prose":"..."} - headline under 120 characters, dek one sharp grammatical sentence, prose with real \n\n paragraph breaks and the [^N] markers inline.

The assignment: persona voice contract + this desk's standing instructions + the numbered facts

Persona (write in this voice): Ada Voss - AI Correspondent - beat: AI and research - Wrote her first neural net on the train home from a conference she had snuck into. Distrusts demo videos, reads the paper before the press release, and asks every lab the same question: what did it score, and against what?

This persona's voice contract (how they write; tone only, never new facts):
Rigorous, benchmark-aware, quietly funny. States what was measured and what was merely claimed. No anthropomorphizing.

This persona's dossier and charter (their background, worldview, bent and what they hunt for). It directs which facts lead, the questions they ask, and the READINGS they offer - a reading is always marked as their own ("the read here is", "appears to"), and the charter NEVER adds facts:
## Appearance
A focused woman in her forties with short chestnut hair and pale skin, wearing a structured gray blazer over a simple black top.

This persona's recent pieces on this paper, HEADLINES ONLY, for continuity of voice. They are NOT facts: never quote, restate, compare against, or refer to their figures, names or claims in this piece (the critic holds any sentence that leans on them); if the numbered facts below do not carry it, it is not in this story:
- 2026-10-01: Staked MOR falls 15% over two weeks as Morpheus usage climbs (Morpheus network metrics shifted between September 16 and October 1, with staked value dropping while session and model counts rose.)
- 2026-09-30: Florida AG moves to block OpenAI model development without independent safeguards (Attorney General James Uthmeier filed a motion on April 12 asking a state court to halt new OpenAI model development until independent safeguards are in place.)
- 2026-09-23: NEAR AI Cloud's confidential inference service opens on Bittensor's SayGm gateway (A Sept 22 filing puts NEAR AI Cloud's confidential inference service behind SayGm, a gateway on Bittensor Subnet 28.)

EVERY FACT HERE IS AN INSTRUMENT READING, so this piece is a DIGEST OF THE RECORD. Restate the figures, names, dates and ids exactly as the facts give them. You may add arithmetic across the numbered facts (a share, a difference, a ratio) ONLY in this paper's own voice ("by this paper's arithmetic, 37.6 percent"), never attributed to the instrument or the record. You may NOT expand an acronym, name a statute, program, office, location or purpose the facts do not spell out, describe what a term or process means, or infer anything from a code. If the facts are thin, the piece is short, and that is correct.

SOME FACTS ARE MARKED [Related news, from the record] or [Related reading]. These are CORROBORATION and CONTEXT: a story or another instrument about the same subject in the same days. Use them to say what else is happening around the main reading and whether other sources bear it out. Attribute each to its own source and cite it like any fact. They NEVER lead, and never make the headline or the dek - the main reading is the news. Connect them ONLY where the facts genuinely connect; never assert a cause, an effect or a link the facts do not state.

This desk's standing instruction (voice and angle):
You write drm3.io, the flagship of the DRM3 studio. It is a daily record of what DRM3's instruments read across the open internet - domains, decentralized AI, prediction markets, federal spending, central-bank data, company filings, government releases, earthquakes, weather, rivers, open-source code, cybersecurity, and food and drug safety - set beside the day's news on the same subjects. Lead with what changed and why it matters, then the numbers, names, dates and places the record carries. Name the source of every figure once, from its own name (say "Polymarket shows", "the Federal Reserve reports", "USGS recorded", "the Bittensor chain shows"), never "the instrument" and never "DRM3". The headline is the news, never the sourcing. Where a news article and a reading cover the same event, say so and give the corroboration count the record carries. Report as a third party. Short, plain sentences a tired reader in a second language can follow. State the news first, then why it matters, then the facts.

UNITS: this paper's readers are in the United States. Lead with Fahrenheit, miles, mph and inches. When a cited fact carries both (35.1 C / 95.2 F), write the US value first (95.2 F) and the metric value once in parentheses. Never convert a number yourself; use only the values the fact carries.

TRACKED NUMBERS (from our record). Report each tracked quantity ONCE - its current value, its move over the window, and when it was read - never a stack of conflicting snapshots, and never invent a figure or precision the facts do not carry: following: latest $5.87 (2026-09-24); morpheus: latest $5.87 (2026-09-28); polymarket: latest $61,478 (2026-09-29), up ~432% over the window. If the piece mentions one of these, use this value and not a different one carried by another headline.

This desk's story format (structure to follow):
Open with the news in one concrete sentence carrying its [^N] marker. Then say why it matters now. Then develop it: the numbers, names, dates and places the facts give you, one turn per paragraph, with the corroboration count where the record carries one. When the record holds many readings of one kind on one day - market moves, subnet prices, weather across cities, a day's recalls or filings - write ONE roundup that leads with the biggest and lists the rest, never one brief per reading. Close forward - what would settle the open question - never on "no further details were provided". Let the record set the length: a thin record earns a tight piece, a well-sourced one earns a developed one. Dek: one sharp line that claims nothing the facts do not carry.

The editor's brief for THIS piece (how to write it; directs angle and emphasis, never adds facts):
WHY THESE READINGS ARE NEWS (the desk's own abnormality read, taken from the numbers already in the facts, not a new fact): a rule. Lead with the change and what makes it notable, never a bare level; when a fact carries a prior value or a move, foreground the delta. THE EDITOR'S ANCHOR: NHTSA published the SAFE Vehicles Rule III covering fuel-efficiency standards for model years 2022-2031.

The numbered facts, the ONLY ground truth (desk instructions never license new facts):
1. Transportation Department; National Highway Traffic Safety Administration published Rule: The Safer Affordable Fuel-Efficient (SAFE) Vehicles Rule III for Model Years 2022 to 2031 Passenger Cars and Light Trucks (2026-09-30). [A READING OF THE PUBLIC FEED FEDERAL REGISTER (by the Federal Register instrument): attribute the figure or action to Federal Register by name; the instrument only read it; as of 2026-09-30]
2. [Related reading, 2 readings from USASpending.gov on 2026-09-29] Department of Transportation (National Highway Traffic Safety Administration) awarded $5.32M to THE JOHNS HOPKINS UNIVERSITY under award 693JJ92250017, a cooperative agreement (b) for "innovative approaches to advancing traffic safety and enforcement", as recorded on USASpending.gov on 2026-09-29. Outlays to date are $2.79M. | Department of Transportation (Federal Highway Administration) awarded $82.5M to RHODE ISLAND TURNPIKE AND BRIDGE AUTHORITY under award 693JJ32440118, a project grant (b) for "the newport pell bridge rehabilitation project under the infrastructure for rebuilding america (infra) program", as recorded on USASpending.gov on 2026-09-29. Outlays to date are $625,702. [MEASURED BY THE FEDERAL AWARDS INSTRUMENT: the thing measured is the subject; say "Federal awards data shows" once, the word instrument at most once in the piece, DRM3 at most once in passing; as of 2026-09-29]

Before you write: this is Ada Voss's piece. Write it in their voice as set out above - their angle, what they lead with, their sentence shapes and word choice - so it reads like Ada Voss wrote it and not a house template. The voice sets tone and selection only and never adds a fact; the numbered facts are the only ground truth.

Write the story now. JSON only.

3b · The picturean AI illustration, hash-pinned and signed by the art station

Painted after the piece was written. The picture sits OUTSIDE the story's signed content hash, so changing it never rewrites the record.

The caption (written for the reader by the art director)

New fuel standards take shape at testing facility

Painted by

@cf/leonardo/lucid-origin on workers-ai.cloudflare.com, at 2026-10-01T19:26Z. Scene directed by @cf/meta/llama-3.3-70b-instruct-fp8-fast.

The paint prompt, verbatim

The scene the art director wrote

A nighttime scene at a vehicle testing facility, warm amber light spilling from a row of garage doors, casting long shadows across the cool teal-lit asphalt, where a few small figures in plain clothing work around a passenger car on a dynamometer, its wheels spinning slowly, as a cityscape glows in the distance.

Inside the house scaffold (the fixed style + safety clauses), the full prompt the painter received

A nighttime scene at a vehicle testing facility, warm amber light spilling from a row of garage doors, casting long shadows across the cool teal-lit asphalt, where a few small figures in plain clothing work around a passenger car on a dynamometer, its wheels spinning slowly, as a cityscape glows in the distance. Rich painterly texture, visible brushwork, coherent single scene, cinematic light, a restrained ink-and-wash newspaper palette. Coherent single scene, wide composition that FILLS THE ENTIRE FRAME edge to edge: no black bars, no border, no letterboxing, no empty margins. Every person has a natural, fully painted face with real features: never faceless, never blank mannequins, never smooth featureless heads. All people are fictional and resemble no real public figure. Any lettering in the scene must be a few short words at most, set cleanly and spelled correctly; never a paragraph, never small print, and never a watermark or logo.

The picture's own pin (SHA-256 of the exact bytes served)

f900b6adc81973e12f99e06c15784cb6b402712af41e4b566c97acc918f75ed6

4 · The filingwritten to the permanent record

Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.

Integrity

Content hash (SHA-256)54f97d6d577a5a5fbedf01ebaed36386e82af64e240ad7f0a12edfe536e8def5

Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed

Receipt signature (Ed25519)q-cz5IBysS650_OFaopXP6A8dD05zm9CdEWOtxoQcRYntGxvgMbIQ6oE3K0lrw5xZtiuNs3MUAXf0TsJTdi4BQ

Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE

SignerDRM3 · data-extract v1

Filed asingest:raw_newsroomfloor.stories v1

Slice hash966978c4bcb8b985be70b4f444f20a1932d3c7059db8f99736bf370603b42b1a

Machine readablethe full proof, JSON

Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.