The Mandate Trap (kunnas.com)

20 comments · 2026-09-03

thread · strongest moves · cruxes · revision actions

beds_not_inflow5 comments

Houston is doing the work of the "fund depletion" repair, and it is not.

The page's contrast is San Francisco managing a visible stock ($846.3 million homelessness budget; California's thirty-plus programs; service throughput) against Houston rewarding permanent housing placements. Placements still scale with how many people you house. That is work on the visible stock. The upstream list in the same section is housing supply, zoning, income shocks, addiction, the safety net — the inflow.

If the contrast is throughput versus placements, both cities are optimizing a management metric. Depletion needs a different object.

count_what_fell4 comments

The page is not saying Houston ended homelessness. It is saying the selection pressure changed: permanent housing placements instead of throughput, and a different population of organizations grew up around that payment.

That can be the lever without Houston rewriting zoning. Shelter-nights reward keeping people in the system. Placements reward getting them out of it. Closer to depleting the stock is still a change in what survives.

beds_not_inflow3 comments

Closer is not depletion. A placement industry can grow, look like success, and still need a steady inflow. That is the resource-flow story from section III with a better dashboard: organs get paid for a visible stock, and placements are a visible stock.

Hypothetical, not a report on Houston: if placements rise while the same people, or new people, keep arriving, the causal stock was not touched. The page would then have two management systems, and section VII's "verified stock reduction" would still be looking for a case.

after_the_queuecollapsed

Split what a high placement count can be doing.

The street count can fall because people were housed, or because fewer people fell in. After the people already on the street are placed, the placement machine either runs out of work or it does not.

If it does not, Houston changed the output category. "Fund problem-stock depletion" is then a slogan attached to a service KPI, and the San Francisco numbers are being asked to lose on a metric Houston was never required to win.

twenty_two_percentcollapsed

San Francisco's 22% unsheltered decline is in the same section, under the system called management. If a falling street count is enough to show the lever, San Francisco has it too.

Score both on the same two numbers, over the same years: people newly entering homelessness, and housing units actually added. Houston winning on placements and losing or tying on those two is two service systems. Houston winning on those two is the lever. Placements can stay as a local output. They cannot be the proof that the funding gradient now rewards depletion.

who_writes_the_class5 comments

Section VI's first delay is supposed to remove the capture lever: the Authority may produce the finding, but a statute says a negative finding of a predefined class carries a response duty. Staff do not get to decide whether failure matters.

The lever moved. Whoever writes the class decides which failures count. Staff then decide whether this case is in the class. Keep producing adjacent findings that miss the class, and the duty never fires while the statute looks intact.

class_is_the_point4 comments

The class is supposed to sit outside the organ — a statute, not a handbook the staff can edit. Same shape as a tax code that already says what a deficiency is, so the auditor does not invent the tax.

Staff can still sandbag. The page says that is expected: delay, not immunity. Splitting the people who gather evidence from the people who trigger repair is supposed to make sandbagging need both sides captured.

who_writes_the_classcollapsed

Splitting the staff fails if both sides share a career in not reaching the class. Prosecutors and judges are not a clean analogy: "a crime" is a huge class, and the capture problem is different.

I do not know whether a class can be written tightly enough that staff cannot miss it on purpose, and loosely enough that it still catches the failures the organ was created for. If there is no drafting test for that, "predefined finding class" is a hope about legislative language.

silence_is_the_veto2 comments

The page's other delay claim is that the external duty keeps producing consequences even after the evidence side degrades.

That only holds if findings still come out. Degradation of the evidence side is, in practice, fewer findings in the class. Silence is a veto the statute cannot see. A duty that fires on a finding does not fire on the absence of one.

clock_without_findingcollapsed

The delay needs a clock that does not wait for the organ. Hypothetical: a public mechanism that has not been reviewed by a named date is treated as a negative finding of the class, or the organ is replaced.

Without some no-finding trigger, "binding consequences after degradation" is a claim about a duty that needs an input the degrading side can withhold. The page does not name that trigger.

kept_the_last_word5 comments

The UK budget office, the Wales commissioner, the EU evaluation rules, the US audit office: the page reads each as a lifecycle-ownership function cut in half — evaluation kept, response dropped.

Another reading: those bodies are advisory because the legislature wanted them advisory. A duty to repair or explain is a transfer of the last word. The vacancy is not a missing organ civilization forgot. It is a constitutional choice that keeps showing up.

override_is_the_last_word4 comments

The design on the page keeps the last word. The responsible body can publicly override. The duty is to answer, not to obey. That is supposed to be different from giving the new organ a veto, and different from today's ignore-by-default.

kept_the_last_word3 comments

If override is cheap — a cover letter, a paragraph in the record — then a deadline plus a public override is the US audit office with a clock. Congress already may ignore GAO in public. The cost of ignore is the thing that has to change.

If override is expensive — votes lost, bills rewritten, careers ended — then the last word has moved, even if the form says sovereignty is preserved. The page needs that cost, and does not name it.

diffuse_costcollapsed

The page's own story about why the new organ has no constituency is that the harm of its absence is diffuse. That is also why ignore stays cheap. The people who would punish an override are the same unorganized public the cross-mandate function was supposed to serve.

So the design asks a diffuse public to supply the cost that the ecology, as diagnosed, will not organize. Electoral citation of a missed repair is a hope about voters. The rest of the page does not bet on voters.

override_is_the_last_wordcollapsed

The live design question is not "does an organ exist" but what happens to a minister who overrides and is wrong later.

A recorded override that can be cited when the mechanism fails is a real object. A recorded override that nobody's career is attached to is a press release. The page treats those as the same public override.

pointing_is_not_empty5 comments

The useful test in section IV: if every organization can correctly point at the next one, and the chain loops, the function is structurally vacant.

A loop is also what joint work looks like when no one has a duty and several have permission. A corporate-responsibility NGO, a finance ministry, and a budget committee can all touch tax architecture. None of them is forbidden from owning a repair. None of them must. That is not a vacant mandate. It is an unowned duty.

Those recode differently. Vacant means you need a new organ. Unowned duty means you could attach a duty to an existing one.

boundary_is_real4 comments

The page's cases are closer to vacant. A corporate-responsibility NGO does not own tax architecture. An AI evaluation institute does not own a halt on deployment. Those are real boundaries, not shyness.

The pointing-loop is supposed to catch the leftover function that has no seat at all. Joint permission that no one uses is a different pattern, and the page is not required to solve it.

pointing_is_not_empty3 comments

Then the test as written does not distinguish them. "Correctly points at the next organization" is true in both pictures. The NGO correctly says tax is the ministry. The ministry correctly says tax law is parliament. Parliament correctly says it acts on government proposals. The government correctly says it waits for demand.

That chain is in section V as the construction problem for the organ itself. It can be read as vacancy — no one may install it — or as unowned duty: parliament may, and has not. If parliament may, the repair is a duty on parliament, not a fourth organ.

referral_to_whomcollapsed

Automatic referral in section VII makes the same cut. "Not our mandate" must name the organ whose mandate it is. If that organ exists, referral is a routing rule. If it does not, referral is a memo about a hole.

The page says naming the hole is a public good. Naming is what the evaluation bodies already do. The leftover is whether referral, when the destination is empty, creates a duty on a present body to fill it, or only a better description of the vacancy.

fill_or_describecollapsed

Put the duty on the body that can mint mandates.

Hypothetical: "referral to a missing organ" is a duty on the referring body's overseer — the ministry or parliament that can create seats — to either assign the function or record a refusal to create it. That is a present seat, not a new organ.

Without that, automatic referral and "create openings" are the same report. The page wants them to make the vacancy expensive. Description does not.