Rent-Stream Drift Dashboard¶

Live monitor — instantiates Revenue–Accountability Coupling Design

A live instrument that tracks how much of an agent's revenue arrives through constituency-bypassing channels and flags drift toward capture before it becomes entrenched.

Capture is rarely an event; it is a slow slide in where the money comes from, and by the time it is obvious the agent already answers to the wrong people. Rent-Stream Drift Dashboard is the standing instrument that watches that slide. It keeps a running, published ledger of every revenue stream — classified by whether the served constituency can influence it or is bypassed by it — and computes indicators of drift: the trend by which revenue shifts from answerable sources (fees the served can withhold, outcome-tied grants, membership) toward rents, captive payments, and sponsor concentration that route around them. Its defining unit is change over time, not a single snapshot: it is built to raise the alarm early, while the drift is still cheap to reverse, and to make the revenue mix visible to the constituency and to the mechanisms that act on it.

Example¶

A professional licensing board is funded almost entirely by fees from the practitioners it licenses — a structure that quietly points its loyalty at its fee-payers rather than the public it exists to protect. The dashboard tracks a handful of indicators monthly: the share of revenue from licensee fees versus public appropriation; concentration among the largest fee-paying firms; the ratio of enforcement actions to complaints received; and how long since the fee schedule was last challenged. For two years the lines are stable; then the licensee-fee share climbs past ≈90% while enforcement-per-complaint slides. The dashboard flags drift toward capture — early, and in public, because the revenue ledger it maintains is open for anyone to read.

Nothing about the flag forces a decision. But now the board's growing dependence on the regulated is a visible trend line rather than a slow, deniable fact, and the hearing, the audit, and the renewal review all draw on the same picture instead of arguing about whether anything is happening at all.

How it works¶

Maintain a live, classified revenue ledger. Every stream is recorded and tagged by whether it depends on, or bypasses, the served constituency — a public record kept current, not an annual filing.
Compute drift indicators, not just levels. Concentration measures, bypass-share trends, and coupling proxies (for example, responsiveness metrics set against the revenue mix) turn the ledger into a read on direction.
Alert on the trend. Thresholds fire on sustained movement toward bypassing sources, so entrenchment is caught while it is still reversible.
Publish. Ledger and indicators are visible to the constituency and feed a shared factual picture to the hearing, audit, renewal, and sunset mechanisms.

Tuning parameters¶

Indicator set — which proxies count as drift (concentration, bypass-share, responsiveness gap). More indicators paint a richer picture but add noise and false alarms.
Alert threshold and smoothing — how large and how persistent a move must be to flag. Tight settings warn early but jump at noise; loose settings stay calm but warn late.
Lookback window — how much history defines the trend. Long windows are stable but slow to catch fast capture; short windows are reactive but jittery.
Ledger granularity — stream-level versus source-level classification. Finer reveals more but costs effort and invites gamed labeling.
Publication level — fully public versus board-only. Public adds sunlight and legitimacy but invites gaming of the visible numbers.

When it helps, and when it misleads¶

Its strength is that it converts slow, deniable capture into a visible trend caught early, and the published ledger is itself a mild anti-capture force — sunlight on who funds the agent. Because every downstream mechanism draws on the same instrument, it replaces "is this even happening?" with a shared factual baseline.

Its honest limit is that it measures proxies for capture, not capture itself: a green dashboard can coexist with soft capture — revolving doors, informal deference, anticipated favors — that never touches a ledger line, and once the indicators are public they can be gamed, restructuring a rent to read as a fee.^[1] Alert-tuning trades false alarms against missed drift, with no free setting. The classic misuse is citing the instrument as a clean bill of health — "the dashboard is green, therefore we are not captured" — turning a watch into a certificate, sometimes by quietly curating the indicators that stay green. The discipline is to read green as "no drift detected," never "no capture," to pair concentration measures with responsiveness and outcome proxies, and to refresh the indicator set as gaming appears.

How it implements the components¶

Rent-Stream Drift Dashboard realizes the monitoring side of the archetype's machinery — the standing instrument that watches the revenue channel:

drift_indicator_set — the running metrics of movement toward constituency-bypassing revenue and away from responsiveness; the dashboard's core output.
public_revenue_ledger — the live, classified, published record of every revenue stream, from which the indicators are computed and which the constituency can inspect directly.

It does not trace each stream past its intermediaries to its true hidden source, nor certify which channels bypass the constituency (revenue_dependency_map / bypass_channel_identifier — Revenue Source Audit); it watches and publishes the trend, and others verify and act on it.

Instantiates: Revenue–Accountability Coupling Design — the dashboard is the standing monitor that makes drift toward capture visible before it entrenches.
Consumes: Revenue Source Audit — the periodic forensic tracing that verifies the source classifications the ledger reports at face value.
Sibling mechanisms: Revenue Source Audit · Performance-Linked Renewal · Public Accountability Hearing · Sponsor Influence Firewall · Sunset Reauthorization Vote · Beneficiary Feedback Gate · Budget-to-Mandate Crosswalk · Clawback or Reversion Clause · Constituency Board Seat · Funding Dependency Register · Participatory Budget Review

Notes¶

Three neighbours are easily confused. The Revenue Source Audit is the point-in-time forensic tracing (where the money truly comes from); the Funding Dependency Register is the standing inventory (what streams exist); this dashboard is the moving picture (how the mix is trending). The dashboard consumes the first two and adds time: it is the only one of the three that raises an early alarm.

References¶

[1] Regulatory capture — the tendency of an agency to come to serve the interests of those it regulates or depends on rather than the public — is the phenomenon this instrument is built to catch early; George Stigler's economic theory of regulation is the classic statement of why funding dependence tilts an agent toward its funders. ↩