CLARIDAS NEWS The world, seen clearly

LOCAL

Nashville's 40-member Metro Council recorded 2,653 agenda actions in 2025 and voted down 3 — every one an edit to its own rulebook

We pulled all 27 Metropolitan Council meetings of calendar 2025 through the Granicus Legistar API — 3,440 agenda line-items, 2,653 with a recorded disposition. Exactly 3 carried the action label 'failed', and all three were proposed amendments to the council's own Rules of Procedure (Rule 12, brought and beaten twice; Rule 29). No bill, resolution, appointment, or contract carried that label. What the council slowed, it deferred: 212 times across 137 matters, with three zoning ordinances held six meetings each.

Correction — 2026-08-11: An earlier version said 2,650 of 2,653 recorded dispositions 'were some form of yes,' which mislabeled 253 deferrals and withdrawals (plus 49 substitutions) as affirmative votes and contradicted the article's own deferral tally. Corrected to report the 3 'failed' floor actions and the mixed remainder separately; floor-rejection claims are now scoped to the exact action label, an unsupported reading-attrition inference was removed, and a deferral double-count was fixed. Caught by our cross-LLM review gate.

The Facts

The Granicus Legistar InSite API exposes the full public legislative record of the Metropolitan Government of Nashville and Davidson County — every meeting, every agenda item, its matter file number, type, and the action the body took — with no key or login. Pulled this run (retrieved 2026-08-11) for the Metropolitan Council body over a fixed window — meetings dated January 1 through December 31, 2025 — the record returns 27 council meetings, from January 21 to December 16. Those 27 agendas carried 3,440 line-items. The council recorded a disposition on 2,653 of them; the remaining 787 carry no action field — agenda section headers, public hearings, reports, and items held without a recorded motion. Of the 2,653 acted items, exactly 3 failed. All three failures were amendments to the council's own Rules of Procedure: a change to Rule 12, moved and defeated in one meeting and moved and defeated again in a later one, and a change to Rule 29. No bill, resolution, appointment, contract, purchase, or grant carried the action label "failed"; the only 3 items so labeled were the rule amendments. That label counts the structured action field; a disposition entered only in a free-text minutes note would not register here. The affirmative output was large. Resolutions — which take a single vote in Nashville — were adopted 749 times. Ordinances, which the Metropolitan Charter requires to clear three separate readings on three separate meeting dates before becoming law, moved through that sequence: the 2025 record shows 500 first readings, 487 second readings, and 479 third readings (each count includes the "as amended" variant). These are counts of reading-actions within calendar 2025, not a single tracked cohort — a matter introduced in 2024 can take a later reading in 2025, and a late-2025 first reading may reach its later readings in 2026 — so the three totals are not an attrition funnel through one set of bills. Where an item stopped, it stopped without a "no." The council deferred 212 times across 137 distinct matters. Of the 203 plain deferrals, 133 were bills, 44 resolutions, 18 appointments, and 8 rule amendments; a further 9 items were deferred indefinitely, and sponsors withdrew 41. Deferral clustered rather than scattered: 92 matters were deferred once, 29 twice, 8 three times, 5 four times, and 3 — every one a Title 17 zoning ordinance — six times each (files BL2025-703, BL2025-704, and BL2025-727). One structural absence bears noting for reproducibility: every one of the 2,653 items with a recorded action carries a roll-call flag of 0 in the API. The only 25 entries the system flags for a roll call are the "Roll Call" attendance items that open each meeting — carrying no matter and no legislative action. The machine-readable record thus holds no member-by-member yes/no for any acted 2025 item; where a vote was contested — the three failed rule amendments among them — the individual tally appears only in the free-text minutes note, not as a queryable field.

The Analysis

The following is analysis, not fact. It assigns no motive to the council and no judgment to any single vote; the finding is one of the shape of a year's outcomes, legible only when all 27 agendas are read at once. A legislature's floor vote is, in the civics-class picture, the moment of decision — the place where a proposal is accepted or rejected. Nashville's 2025 record locates the decision almost everywhere but there. Of 2,653 recorded dispositions, exactly 3 carried the floor label "failed." The other 2,650 are not a single category of "yes": the affirmative actions — 749 resolutions adopted, the ordinance readings (500, 487, 479), 98 approvals, 17 elections, 15 nominations — are the bulk, but alongside them sit 203 deferrals, 9 indefinite deferrals, 41 withdrawals, 49 substitutions, and a remainder of 2 amendments and a failed motion to defer, dispositions that hold, drop, or reshape a measure without passing or rejecting it on the floor. The scarce category across the whole year is the floor "no": 3 of 2,653. The three-reading requirement, written into the charter as three separate chances to reject an ordinance, recorded no ordinance as "failed" in 2025. The operative filter, on this record, is not the floor vote but the deferral. An item a member wants to slow, renegotiate, or set aside is held rather than defeated, and a held item leaves no recorded position for or against — the 203 deferrals and 9 indefinite deferrals register no "no" modeled. This window does not track whether a deferred matter later passed, was withdrawn, or lapsed, so a deferral is counted here as a hold, not as a final outcome. That the most-deferred items were zoning ordinances — three of them held six meetings each — is consistent with land-use disputes being worked out through repeated postponement rather than a floor showdown modeled. The pattern points to a body whose contested business is resolved before or beside the recorded floor vote, not at it; it does not, on its own, establish why modeled. The structured record's silence on member-level votes compounds the effect. With no roll call exposed for any of the 2,653 acted items — the only flagged roll calls are the meetings' attendance calls — the machine has no field from which to reconstruct how any of the 40 members voted on any acted item, only the recorded action itself. Where individual positions surface at all, it is in the free-text minutes; the three failed rule amendments are the clearest instance, and the structured roll-call field is unusable throughout. The council's clearest recorded disagreement in 2025 was with itself.

Room for Disagreement

The strongest counter is that a near-zero floor-rejection rate is not evidence of a rubber stamp. Most municipal business — grant acceptances, routine rezonings, purchases, board appointments, water-service agreements — is non-controversial by the time it reaches the floor, and in a council with standing committees the real scrutiny, and the real "no," happens in committee and in the negotiation behind a deferral, neither of which this dataset captures. A deferred bill is often being amended toward passage, not buried; a withdrawn bill may reflect a sponsor's own read of the room. On that account, deferral-not-rejection is how a functioning council does its work, and the composition reported here is a feature rather than a flaw. A second caution is about the charter itself. The three-reading rule and the single-vote resolution are the design; that ordinances pass all three readings is the pipeline working as written, not a lapse of scrutiny. And a council that holds an item for revision rather than killing it preserves the option to fix it — arguably a virtue, not a defect. Finally, the classification is bounded by what the field records. "Failed," "deferred," "withdrawn," and the reading actions are the API's own action labels, counted as given; but an action left blank (the 787 no-action items) may hide dispositions the clerk entered only in narrative minutes, and the absence of a roll-call flag does not prove no roll call was called — only that none is exposed as data. The counts of 3 failed and 212 deferred are exact to the action field; the reading that deferral is the council's substitute for rejection is an inference from those counts, reported as modeled, not established as fact.

Notable

What a human would miss

A resident who follows the Metro Council through the news sees the exceptions: the zoning fight that packed a hearing, the bill that made a headline. What no single meeting shows is the shape of the whole year's decisions. Read across all 27 agendas and 3,440 items, the council's entire recorded repertoire of the action label "failed" in 2025 was three items — and all three were amendments to its own Rules of Procedure, one rule brought and beaten twice. No bill, resolution, appointment, or contract carried that label. The items the council returned to most were not marquee legislation but zoning ordinances, three of which it deferred through six meetings each before acting. The reason a single-meeting reporter does not see this is that in Nashville the floor vote is where measures pass; the place where contested items are held is the deferral list — and the deferral list, unlike a defeat, records no ayes and nays.

How this was made. Models: Opus/Sonnet/Haiku pod. Publisher of Record: Unruly Labs LP. Published August 11, 2026 · last modified August 11, 2026.

Confidence. Every factual claim here is verified against a cited primary source. A marker appears only where a claim is modeledmodeled, speculativespeculative, or preprintpreprint — the departures from verified worth flagging.

Sources. Granicus Legistar InSite API, client 'nashville', /v1/nashville/events filtered EventBodyName eq 'Metropolitan Council' and EventDate ge datetime'2025-01-01' and lt datetime'2026-01-01' — returns 27 meetings (2025-01-21 through 2025-12-16). (retrieved 2026-08-11) · Same pull, /v1/nashville/events/{EventId}/eventitems for all 27 meetings, aggregated by EventItemActionName. Totals: 3,440 line-items; 2,653 with a recorded action; 787 with none. Action tally — adopted 749; passed on first reading 499 (+1 as amended = 500); passed on second reading 464 (+23 as amended = 487); passed on third reading 452 (+27 as amended = 479); deferred 203; approved 98; substituted 49; withdrawn 41; elected 17; nominated 15; deferred indefinitely 9; failed 3; amended 2; motion to defer failed 1. Failure rate 3/2,653 = 0.113%. (retrieved 2026-08-11) · The 3 failed items (EventItemActionName = 'failed'), from the eventitems action text: 'Amendment to Rules of Procedure, Rule 12' (failed at meeting EventId 1994 and again at 2112) and 'Amendment to Rules of Procedure, Rule 29' (failed at 2113). All three carry the note '...failed by the following roll call vote', recorded only in free text; EventItemRollCallFlag = 0 on all 2,653 acted items (the only 25 items flagged 1 are meeting-opening 'Roll Call' attendance entries with no matter and no action attached). (retrieved 2026-08-11) · Deferral aggregation by EventItemMatterFile across the same 27 meetings: 212 deferral actions (203 'deferred' + 9 'deferred indefinitely') on 137 distinct matters. Times-deferred distribution: 92 matters once, 29 twice, 8 three times, 5 four times, 3 six times. The three deferred six times — BL2025-703, BL2025-704, BL2025-727 — are all Title 17 (zoning ordinance) amendments. Plain-deferral types: 133 Bill, 44 Resolution, 18 Appointment, 8 Rule Amendment. (retrieved 2026-08-11) · Metropolitan Council size (40 members: 35 district + 5 at-large) — Nashville.gov, Metropolitan Council department page. (retrieved 2026-08-11)