Functional Vacancy Declaration¶
Authorizing protocol — instantiates Functional Vacancy Backfill
The formal, recorded act that reclassifies a still-occupied authority role as functionally vacant, dissolving the nominal occupancy that was keeping every substitute channel illegitimate.
A filled seat can suppress cover more effectively than an empty one — everyone waits for the named sponsor because the title is still theirs. Functional Vacancy Declaration is the formal, recorded act that says, in effect, "for these decisions, this role is now vacant," even though no one has resigned and the org chart is unchanged. Its whole job is to break the nominal occupancy that keeps substitute channels illegitimate. It is not a diagnosis — it consumes evidence others gather — and not an authority grant — it names no substitute and hands out no powers. It does exactly one thing: it converts an ambiguous "they've gone quiet" into an on-the-record status change that makes backfill legitimate. That single, narrow act is what distinguishes it from every sibling: the declaration is the switch, not the sensor and not the stand-in.
Example¶
An open-source library depends on a single maintainer who holds sole merge rights. For roughly three months they stop reviewing pull requests, answering security reports, or cutting releases — but they have not stepped down, and contributors will not fork or route around them because "it's still their project." Security patches pile up unmerged. The project's governance document has a clause for exactly this. The steering group invokes it and posts a Functional Vacancy Declaration to the public tracker: as of a dated notice, the maintainer role is functionally vacant for merge and release decisions, citing the logged evidence — an unmerged critical fix and roughly ninety days of no reviews. Crucially, the notice is narrow and on the record. It does not fire the maintainer, does not claim their other rights, and leaves a documented re-entry path. What it does is dissolve the "we can't touch it, it's theirs" paralysis: the moment the declaration is posted, an interim merge process becomes legitimate.
How it works¶
- Confirm the seat is still treated as occupied — no resignation, no ordinary vacancy process running — because that is precisely the condition that makes a declaration necessary rather than redundant.
- Confirm the occupancy is suppressing substitutes — that decisions are stalling because people defer to the still-present title, not for want of a process.
- Scope the vacancy to specific functions (merge and release, not the whole role), so backfill covers only what is actually missing.
- Record the status change with its date, cited evidence, and scope — the notice is the artifact that makes everything downstream legitimate.
What it deliberately does not do is decide the deadline (a rule's job) or appoint the substitute (a charter's or rotation's job). It is the pivot between detection and backfill, nothing more.
Tuning parameters¶
- Scope width — declare vacancy for one decision type or the whole role. Narrow scope is safer and more defensible; wide scope resolves more but edges toward de facto removal.
- Evidence bar — how much logged nonperformance the declaration must cite. A high bar protects the incumbent from a weaponized declaration; too high and the paralysis outlasts the harm.
- Who may declare — a single deputy, a panel, or a standing governance body. Concentrating the power to declare speeds the act but invites abuse; a panel slows it but hardens legitimacy.
- Reversibility terms — whether the notice states an automatic expiry and re-entry path, or stands until explicitly lifted. The more reversible, the less it resembles a coup.
- Publicity — a private record versus a broadcast notice. Broadcasting maximizes the legitimacy it confers but also maximizes the incumbent's loss of face.
When it helps, and when it misleads¶
Its strength is that it defeats the pocket veto — the way an absent authority can kill every decision simply by not acting, while their intact title makes anyone else's action look illegitimate.[n1] By putting the vacancy on the record, the declaration relocates legitimacy from the silent incumbent to a documented, scoped process.
Its classic misuse is running it backwards: manufacturing a "vacancy" to sideline a sponsor who is present but merely inconvenient — a procedural coup dressed as continuity. Because the act is so powerful (it strips the practical force of a title with no HR process at all), a thin evidence bar or a self-interested declarer is the real hazard. The discipline that guards against this is to keep the declaration narrow, evidence-cited, reversible, and issued by someone other than the party who gains the freed authority — and to pair it always with a re-engagement path so the incumbent can rebut before backfill hardens.
How it implements the components¶
Functional Vacancy Declaration fills only the reclassification-and-legitimacy slice of the archetype:
nominal_occupancy_assessment— it fires only when the seat is still treated as occupied; confirming that is its precondition.substitute_channel_suppression_check— it acts on the finding that the title itself is blocking alternatives, and the declaration is what removes that block.legitimacy_notice_and_record— the dated, scoped, evidence-cited notice is the legitimacy record every downstream backfill step relies on.
It does not gather the ongoing health evidence (role_function_health_signal, the Decision Stall Register and Sponsor Health Check), set the stall deadline (decision_stall_threshold, the Decision Timeout Rule), or grant any authority envelope (backfill_authority_envelope, the Deputy Sponsor Charter and Interim Authority Letter).
Related¶
- Instantiates: Functional Vacancy Backfill — the declaration is the hinge that turns detected nonperformance into authorized backfill.
- Consumes: Decision Stall Register supplies the logged evidence the notice must cite; a Sponsor Health Check supplies corroborating signals.
- Sibling mechanisms: Decision Stall Register · Decision Timeout Rule · Auto-Escalation Workflow · Acting Sponsor Rotation · Deputy Sponsor Charter · Sponsor Health Check · Sponsor Re-Engagement Notice · Interim Authority Letter · Two-Key Escalation Panel · Governance RACI With Backups · Post-Backfill Authority Review
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: The mechanism is a formal recorded speech act that publicly reclassifies a nominally occupied authority role as functionally vacant and legitimizes substitute channels.
Nearest alternative: Protocol, Workflow & Routine — A declaration may follow procedural requirements, but its operative effect comes from the authoritative communicated reclassification itself.
Review outcome: Adjudicated after independent review; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Formal vacancy, incapacity, and succession declarations arise from legal rules of office and authority.
Related originating lineages:
- Organizational & Management Science — Succession and business-continuity practice materially shape the backfill purpose.
- Public Administration & Policy — Administrative continuity practice materially shapes recorded reassignment of an unperformed public function.
Review resolution: Both reviewers agree that law_governance is primary: Formal vacancy, incapacity, and succession declarations arise from legal rules of office and authority. I retain public_administration_policy, organizational_management only where the reviewers identify formative lineage, not every later application. I resolve origin_mode as cross_disciplinary_synthesis because the artifact joins distinct disciplinary contributions. I resolve domain_reach as multi_domain because it transfers across several fields but is not a domain-free primitive. Encyclopedia synthesis is true because the exact generalized packaging is an encyclopedia-authored combination or refinement.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The declaration is a status change, not a personnel action: it says a function is uncovered, not that the incumbent is unfit. Keeping those separate is what lets a team backfill a distracted sponsor's decisions this week without opening a firing that would take months and poison the relationship — and it is what lets the incumbent simply walk back in when they re-engage.
[n1] A pocket veto is the real legislative practice in which an executive lets a bill die by not signing it before a deadline — killing it through inaction rather than an open "no." An absent sponsor exercises the same power over ordinary decisions; the declaration is what strips inaction of that veto force. ↩