Support Flow Agreement¶

Governance compact — instantiates Source–Sink Viability Management

Turns an informal support flow into an explicit compact — stating why the support exists, until when it is promised, and on what fair terms — so a subsidy is a governed decision rather than an accreted habit.

The Support Flow Agreement is the governance instrument that makes a support relationship explicit and accountable: a negotiated compact between the supplying and receiving parties that records the reason the support flows, the horizon over which it is promised (permanent, staged, conditional, or time-limited, with a review date), and the terms that keep the arrangement fair to both sides. Its distinguishing role is that it converts a flow which might otherwise persist by inertia — nobody ever decided it, nobody can say why it continues — into a stated, reviewable commitment. It governs whether and why support is owed; it does not measure the parties, size or allocate the money, or execute a wind-down.

Example¶

A national government makes annual fiscal-equalisation transfers to a fiscally weaker region so it can fund comparable public services. For years the transfer was just a line in the budget, its size set by precedent and lobbying. A Support Flow Agreement formalises it. The rationale is named — equal access to core services, a constitutional obligation, explicitly not open-ended development aid. The horizon is set as a five-year commitment with a mandatory review and a sunset unless renewed.^[1] And the fairness terms cut both ways: the receiving region accepts transparency on how funds are used and a formula that tapers the transfer if its own revenue base recovers, while the supplying centre commits to stable, predictable payments the region can plan around rather than year-to-year discretion. The agreement doesn't compute the transfer amount or run its eventual reduction; it fixes the why, the until-when, and the on-what-terms that any amount or taper must honour.

How it works¶

Names the rationale. The support must carry a stated reason drawn from a defined set (equity, coverage, mission, option value, transition, legal obligation), so "why does this flow exist" always has an answer on file.
Fixes a horizon and a review date. Permanent, staged, conditional, or time-limited — but explicit, and with a date at which the compact is re-examined rather than auto-renewed by silence.
Sets fair, two-sided terms. Obligations on the receiver (transparency, effort, conditions) balanced by commitments to the receiver (predictability, notice, non-exploitation), so the compact protects each party against the other's opportunism.

It is the standing charter for a flow; the measuring, budgeting, and tapering are done by other mechanisms against its terms.

Tuning parameters¶

Horizon length and firmness — a short, tightly-conditioned promise versus a long, near-unconditional one; firmer promises let the receiver plan but cost the supplier flexibility to stop.
Conditionality — how much continued support is tied to receiver behaviour; strong conditions drive effort but can punish a receiver for shocks outside its control.
Review trigger — calendar review versus event-triggered (revenue recovery, mission change); event triggers track reality, calendar reviews stay predictable.
Exit terms — how much notice and wind-down protection the compact guarantees; generous terms reduce harm but weaken the credibility of any deadline.
Symmetry — how evenly obligations fall on supplier and receiver; lopsided terms are faster to sign but breed resentment and eventual breakdown.

When it helps, and when it misleads¶

Its strength is defeating drift — support that continues only because ending it was never on anyone's agenda — by forcing a rationale and a review date into existence, and by protecting both parties: the receiver from arbitrary cut-off, the supplier from an open-ended entitlement. Its failure modes: an agreement can manufacture permanence, its renewal becoming a rubber stamp so that the review date launders inertia into apparent decision; and a compact is only as honest as its rationale — a vague "strategic importance" clause justifies anything. The classic misuse is drafting it to ratify a subsidy the drafters already want rather than to test whether it is still warranted. The discipline is to write a rationale specific enough to fail — one a genuine change in conditions would falsify — and to make the review a real re-decision whose default is expiry, not renewal.

How it implements the components¶

The Support Flow Agreement fills the governance components — the machinery that makes support a stated, fair, reviewable commitment — and only those:

support_rationale_and_horizon — it records the explicit reason for the support and the horizon and review date over which it is promised.
fairness_and_equity_review — it sets and periodically tests the two-sided terms that keep the arrangement equitable to supplier and receiver.

It does NOT execute a reduction or protect against abrupt withdrawal in practice — that's the Support Taper Plan — and it does NOT size or allocate the support itself, which the Cross-Subsidy Budget and Minimum Support Schedule handle.

Instantiates: Source–Sink Viability Management — the standing charter that says why a support flow exists and on what terms.
Consumes: Sink Dependency Dashboard — the dependence profile that tells the parties what an adequate, fair commitment must cover.
Sibling mechanisms: Support Taper Plan · Cross-Subsidy Budget · Minimum Support Schedule · Sink Dependency Dashboard · Restoration Priority Matrix

References¶

[1] A sunset clause is a provision under which a rule, programme, or subsidy expires automatically on a set date unless it is affirmatively renewed; it flips the default from "continues until someone stops it" to "stops unless someone re-justifies it" — which is the whole point of attaching one to a support flow. ↩