Cross-Boundary Support Agreement¶
Document — instantiates Donor-Coupled Capacity Governance
Formalizes rights, obligations, data sharing, support levels, review cadence, and exit/continuation rules.
A Cross-Boundary Support Agreement is the bilateral instrument that turns an informal, indefinite flow of support into a governed relationship with named terms. Where an informal subsidy leaves everything implicit — how much, for how long, on what conditions, and what happens if the donor needs to stop — this document writes those terms down as mutual rights and obligations that both sides can be held to. Its defining subject is the relationship, not the recipient's readiness: it says what each party owes the other, under what conditions the donor may lawfully reduce or exit, what the recipient owes in return or in accountability, and how the fairness of the whole arrangement will be reviewed. It is the mechanism that lets legitimate support stay legitimate — visible, bounded, and revocable only under agreed rules — rather than hardening into an unexamined entitlement or evaporating on a donor's whim.
Example¶
A county emergency-communications center has, for years, provided 911 dispatch for three small incorporated towns that never built their own. No one signed anything; the towns simply route their calls to the county, and the county absorbs the cost in its general fund. When a budget crunch hits, the county floats cutting the towns off with ninety days' notice — and the towns discover they have no floor to stand on and no say. To govern this honestly, the parties negotiate a Cross-Boundary Support Agreement.
The document sets the obligation terms: the county commits to a defined service level (answer times, staffing tiers) and the towns commit to a cost share and to sharing incident data on a common schedule so the relationship can be measured. It writes an exit-exception rule: the county may reduce service only for enumerated causes (a declared fiscal emergency, a town's non-payment), and only with a minimum transition window and joint sign-off — no ninety-day surprise. And it schedules an equity-and-legitimacy review every two years, at which an independent panel checks whether the cost split is fair, whether any town is being cross-subsidized at another's expense, and whether the arrangement still commands the consent of the people it serves. The support continues — but now as an accountable obligation rather than a quiet favor.
How it works¶
The distinguishing work is drafting terms that survive stress and disagreement, not describing the flow:
- State obligations as mutual and conditional. Each party's duty is written with its trigger and its limit, so "we support you" becomes "we provide service level X while you meet obligation Y."
- Enumerate the permitted exits. Rather than an open right to quit or an implicit promise never to, the agreement lists the specific causes and notice periods under which support may lawfully shrink — turning exit from a unilateral shock into a governed event.
- Schedule the legitimacy check. A recurring review with named participants and a fairness mandate is written into the contract itself, so the arrangement is re-consented rather than allowed to ossify.
- Bind data sharing to the terms. The information each side must disclose is specified, because obligations no one can observe cannot be enforced.
Tuning parameters¶
- Term completeness — how exhaustively contingencies are specified. More completeness reduces later disputes but raises drafting cost and risks freezing terms that should flex; no contract can foresee everything.
- Exit-cause breadth — how many circumstances permit the donor to reduce support. Broad causes protect the donor's freedom; narrow causes protect the recipient's security. This dial is where the relationship's power balance actually lives.
- Review cadence and independence — how often the legitimacy review runs and how arm's-length its panel is. Frequent, independent review catches drift and unfairness early but is costly and can destabilize a working arrangement.
- Enforcement teeth — whether breach carries real consequence or only obliges renegotiation. Teeth make obligations credible but can make either party reluctant to sign.
When it helps, and when it misleads¶
Its strength is that it converts a fragile, deniable arrangement into one that is legible and accountable to both sides and to third parties — the thing that lets a genuinely just subsidy be defended as such, and an unfair one be surfaced and repriced. It is the archetype's answer to "formalize the support rather than hide it."
Its failure mode follows from the theory of incomplete contracts: no document can specify every future contingency, so the terms left unwritten become the terms that get fought over, usually to the disadvantage of the weaker party.[n1] A support agreement can lull both sides into thinking the relationship is fully governed when the hardest cases — a catastrophic donor shock, a recipient's collapse — fall into the gaps. The classic misuse is a contract of adhesion dressed as partnership: a powerful donor writes broad exit causes and thin obligations, and the review clause becomes decorative. The guarding discipline is to keep the equity-and-legitimacy review genuinely independent and empowered to reopen terms — so the gaps get renegotiated in the open rather than exploited in silence.
How it implements the components¶
reciprocity_or_obligation_rule— its core: the mutual, conditional duties each party owes, written as enforceable terms.donor_exit_exception_rule— it enumerates the specific causes and notice under which the donor may lawfully reduce or end support.equity_and_legitimacy_review— it schedules and empowers a recurring, arm's-length fairness check as a contract clause.
It does not set the recipient's readiness gates — local_capacity_milestone and recipient_capacity_baseline belong to Capacity Milestone Agreement, its nearest document-twin — nor does it keep the running subsidy_visibility_ledger of actual flows, which is Subsidy Ledger. This document governs the relationship's terms; those set what the recipient must earn and record what physically moves.
Related¶
- Instantiates: Donor-Coupled Capacity Governance — supplies the formal terms that make legitimate support governable.
- Sibling mechanisms: Capacity Milestone Agreement · Subsidy Ledger · Support Load Quota · Taper and Handoff Plan
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Cross-Boundary Support Agreement operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it formalizes rights, obligations, data sharing, support levels, review cadence, and exit/continuation rules.
Independent corroboration: The frozen evidence defines Cross-Boundary Support Agreement as 'Formalizes rights, obligations, data sharing, support levels, review cadence, and exit/continuation rules', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: A negotiated agreement defining reciprocal duties, triggers, and accountability is fundamentally contractual and legal, with public-administration and organizational operating forms.
Related originating lineages:
- Organizational & Management Science — Service-level and operating agreements translate obligations into recurring coordination routines.
- Public Administration & Policy — Interagency agreements institutionalize shared services and mutual support across jurisdictions.
Review resolution: A negotiated agreement defining reciprocal duties, triggers, and accountability is fundamentally contractual and legal, with public-administration and organizational operating forms.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Incomplete contracts — the observation (associated with Grossman, Hart, and Moore) that contracts cannot specify every future state of the world, so residual control over unwritten contingencies matters enormously and tends to accrue to the stronger party. ↩