Budget-to-Mandate Crosswalk¶

Mapping tool — instantiates Revenue–Accountability Coupling Design

Lines up every budget line against the mandate or principal it is authorized to serve, so spending that answers to no one the agent is supposed to serve gets named rather than hidden as overhead.

Accountability erodes on the spending side as quietly as on the revenue side: an agent living on automatic funding can gradually redirect its outlays toward its own convenience or toward whoever is nearest, while the mandate it nominally serves goes underfunded. Budget-to-Mandate Crosswalk is a two-column mapping that forces a disposition on every dollar — left column, the budget line or cost center; right column, the specific mandate, statute, beneficiary, or principal it is authorized to serve. Its distinguishing move is the forced verdict on lines that don't map: spend that serves no external principal is either self-preservation the agent should justify or drop, or a function that is legitimately insulated from immediate constituency demand — and the crosswalk makes you say which, in the open. Where the Funding Dependency Register traces where the money comes from, this traces whom the money, once spent, actually serves.

Example¶

A state environmental regulator is funded by a general appropriation plus permit fees — neither of which the public it protects controls. A crosswalk maps each budget block to a principal: field inspections → the public and downstream communities (mapped); lab capacity → the public (mapped); a growing "stakeholder relations" unit → on inspection, mostly the regulated permit-holders it liaises with (mapped, but to the wrong principal). The crosswalk doesn't accuse; it displays. Some unmapped spend turns out to be genuine long-horizon work — statutory records retention, a monitoring network with no near-term constituency — which the agency documents as legitimately insulated.^[1] The rest, including the industry-liaison drift, is now a named line for the board to defend or cut, rather than a soft grey mass labeled "administration."

How it works¶

What distinguishes it from a normal budget breakdown is the mapping and the forced disposition:

Every line lands somewhere. Each budget item is tied to a mandate-holder, tagged as legitimately insulated with a written rationale, or flagged as unaccounted — no line is allowed to stay unclassified.
The principal is fixed first. The mandate or constituency list is defined before the mapping starts, so lines are tested against a standard, not fitted to a story after the fact.
It re-runs over time. Comparing crosswalks across years shows the mandate-coverage ratio rising or falling — the drift made quantitative.

Tuning parameters¶

Granularity — cost-center level versus line-item. Finer mapping catches more misalignment but costs effort and invites false precision.
Insulation bar — how strict the test for "legitimately insulated." Loose, and capture hides as necessary overhead; strict, and genuine long-horizon functions get starved.
Mandate source — whether the right-hand column is drawn from statute, board-stated mission, or an explicit beneficiary list. The choice of principal can flip a line's verdict.
Coverage target — what fraction of spend must map to an external principal before the budget is considered coupled.

When it helps, and when it misleads¶

Its strength is turning a vague charge of "bloat" into a specific, defensible list, and — crucially — separating legitimate insulation (central-bank-style independence, statutory reserves) from quiet capture, instead of treating all overhead as equally suspect.

It misleads when the mandate is genuinely ambiguous, because then the mapping is arguable and each side can claim its favored lines are "core." The classic misuse is running it backwards — drawing the crosswalk to justify existing spend by inventing a plausible mandate link for every line, so the tool launders the budget instead of testing it. The discipline is to fix the principal definition before mapping and to put the insulation calls in front of an independent reviewer rather than letting the spender grade its own homework.

How it implements the components¶

Budget-to-Mandate Crosswalk fills the mandate-mapping slots of the archetype — the spend-side questions a mapping tool can answer:

principal_constituency_map — the right-hand column is the enumerated set of mandate-holders and principals each budget line is meant to serve.
legitimate_insulation_rationale — the tool forces every unmapped line to be classified as capture or as a legitimately shielded function, documenting the reason it is allowed to answer to no current constituency.

It does not trace the revenue side — which streams fund the agent and which bypass its constituency is the Funding Dependency Register's job; and it does not build the barrier that keeps sponsor money out of decisions — that's Sponsor Influence Firewall.

Instantiates: Revenue–Accountability Coupling Design — it re-couples outlays to the mandate they are supposed to answer to.
Sibling mechanisms: Funding Dependency Register · Participatory Budget Review · Constituency Board Seat · Beneficiary Feedback Gate · Clawback or Reversion Clause · Revenue Source Audit · Rent-Stream Drift Dashboard · Sponsor Influence Firewall · Performance-Linked Renewal · Public Accountability Hearing · Sunset Reauthorization Vote

Notes¶

The crosswalk maps where money goes, not where it comes from — a line can map cleanly to the mandate yet still be funded by a captured revenue stream, and vice versa. It is the spend-side half of a diagnostic whose revenue-side half is the Funding Dependency Register; read together they show whether both ends of the money flow answer to the served constituency.

References¶

[1] The tendency of an agency on secure funding to expand its budget beyond what its mandate requires is the budget-maximizing bureau of public-choice theory (William Niskanen). The crosswalk is a direct counter: it makes the mandate, not the agency's appetite, the yardstick every line is measured against. ↩