Support Layer Sunset Review¶
Review protocol — instantiates Coordination Scaffold Load Control
Attaches an expiry date to every support layer and forces a scheduled review at which it must re-justify its existence or lapse by default.
A Support Layer Sunset Review is a review protocol that attaches an expiry date to every support layer at the moment it is created and convenes a scheduled review at which the layer must actively re-justify its existence or lapse by default. Its defining idea is that existence is time-boxed and renewal is opt-in: the clock, not a person, is the default killer, so a layer dies on its date unless someone makes the affirmative case to keep it. It removes on a schedule — never on demand — which is precisely what lets it defeat the ratchet by which support layers only ever accumulate.
Example¶
A city government spins up task forces the way most crises get answered: a housing task force during a shortage, a transit-equity working group after a fare dispute, a pandemic-response cell during the emergency. None of them ever formally ended; years later the org chart carries a dozen bodies, half dormant, each still holding a standing meeting slot and a quarterly report. A sunset protocol changes the default. Every new body is created with a twelve-month sunset. At month eleven a review asks two questions: what decisions does this body still own, and can that work fold into a standing function? Absent an affirmative renewal, it dissolves automatically at month twelve.
The first cycle is telling. Half the dormant task forces simply lapse — no one is willing to make the case, and that silence is the answer. The two still doing real work are renewed with refreshed mandates, and one is folded into a permanent department. The accumulation ratchet is broken not by a purge but by making continuation a decision that has to be earned.
How it works¶
The protocol assigns an expiry at the moment a support layer is created, and calendars the review to fall before that expiry. Renewal is active — the default outcome of doing nothing is lapse, not continuation. At the review, the layer's value ratio is examined: what it still costs versus what decisions it improves or harms it prevents. Survivors are, where possible, folded into standing functions rather than perpetuated as exceptions. The distinguishing move against its siblings is temporal default-death plus scheduled re-justification: removal is driven by a clock and a periodic gate, not by an on-demand judgment call.
Tuning parameters¶
- Sunset horizon — how long a layer lives before review. Short horizons keep the ratchet tight but add review overhead; long ones are cheaper but let dead layers persist longer.
- Renewal bar — how strong a case continuation requires. A high bar clears more sprawl; a low bar risks rubber-stamp renewals that defeat the protocol.
- Review depth — how thoroughly each layer is examined at its gate. Deep reviews catch subtle low value but cost time; shallow ones scale but miss it.
- Auto-lapse vs auto-review — whether reaching the date dissolves the layer outright or merely triggers a review. Auto-lapse is decisive but risky; auto-review is safer but softer.
- Grandfathering — whether legacy layers created before the protocol get sunset dates retroactively. Grandfathering eases adoption but exempts exactly the oldest accumulation.
When it helps, and when it misleads¶
Its strength is defeating the accumulation ratchet: because support layers are added far more readily than they are ever removed, a default expiry turns continuation into an explicit decision and clears the dormant bodies no one would otherwise touch.
Its failure mode is sunset theater — reviews that reflexively renew, or horizons set so long the clause never actually bites. It is the sunset-provision idea borrowed from legislation[1], and it shares that idea's weakness that renewal can quietly become automatic. The classic misuse is sunsetting a layer that silently prevents a rare, high-cost failure: because the failure has not occurred — precisely because the layer was there — the layer looks idle and gets cut, and the cost appears only later. The guarding discipline is to make renewal require a real case and a named owner, and to weigh the value ratio at each gate rather than mistaking low recent usage for low value.
How it implements the components¶
support_sunset_rule— its core: the expiry-and-renewal clock attached to each support layer, with lapse as the default.support_value_ratio— the renewal gate weighs the layer's burden against the value it recovers to decide whether continuation is earned.
It removes on a clock but not on demand, and it names no standing kill-owner: unilateral, immediate removal via a coordination_burden_owner and pruning_or_consolidation_rule is the move of coordination_artifact_kill_switch — its nearest twin, which fires on demand where this waits for the scheduled gate.
Related¶
- Instantiates: Coordination Scaffold Load Control — supplies the scheduled expiry gate that keeps support layers from accumulating indefinitely.
- Consumes: work_before_metawork_ratio_dashboard — the dashboard's value ratio is the evidence the renewal gate weighs.
- Sibling mechanisms: async_decision_log · coordination_artifact_kill_switch · coordination_load_audit · delegation_authority_matrix · exception_based_oversight · governance_forum_consolidation · handoff_path_pruning · meeting_budget · work_before_metawork_ratio_dashboard
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Support Layer Sunset Review is defined in the frozen evidence as: Attaches an expiry date to every support layer and forces a scheduled review at which it must re-justify its existence or lapse by default. Its operative deployed or enacted form is therefore Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Assessment, Review & Assurance can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Reviewing whether a temporary support layer can lapse combines lifecycle management with sunset governance.
Related originating lineages:
- Law & Governance — Sunset doctrine makes continuation require renewed justification.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: attaches an expiry date to every support layer and forces a scheduled review at which it must re-justify its existence or lapse by default.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
References¶
[1] Gersen, J. E. "Temporary Legislation". University of Chicago Law Review 74(1), Article 12, 247 (2007). Supports the legislative sunset-provision concept; it does not support characterizing renewal as automatic. registry ↩