Intentional Ephemerality

Introduction

Source and provenance. This section rests on a single 12-line fragment of an AI-assisted interview transcript, ~/code/site-provide-coop/Intentional Ephemerality.txt, staged for this corpus and never checked against any other source. The staged extraction characterizes it as brainstorming rather than ratified policy, and it reads that way: several of its propositions are posed as open questions rather than stated as rules, and this section preserves that framing where the source uses it. Nothing here has been adopted as network policy. The concept is recorded because no other source in the corpus treats designed finitude at all, not because the material is settled.

Not every dissolution in the Humanized Autonomous Organization (HAO) — the network’s coordinating framework — follows from failure. This section describes units designed, from their founding, to end: a United Micro Enterprise (UME) — a small, self-managing venture team (≤ ~15 people) — or a Strategic Enterprise Partnership (SEP) — a joint venture between teams — whose charter fixes a finite lifespan, or a defined end-condition, from the outset, independent of whether the unit goes on to succeed.

docs/06-lifecycle/01-ume-lifecycle-and-transition-states.md already lists Dissolution as one of seven UME lifecycle phases, reached through voluntary exit, reintegration, conditional dissolution, or collapse. Intentional ephemerality describes a narrower, earlier design choice: the lifespan is fixed at Genesis, written into the unit’s charter or Dynamic Enterprise Agreement (DEA) — a versioned operating agreement replacing fixed bylaws — rather than decided later, once a mission is judged complete. The model’s material on this design pattern predates the current UME/SEP vocabulary and describes it at the level of a general venture rather than specifying UME or SEP; it applies most directly to the SEP, whose existing Completion phase (docs/06-lifecycle/02-sep-lifecycle-and-governance.md) already carries a sunset report and asset-distribution logic, but nothing in the model restricts the design to SEPs alone.

Distinguishing Designed Finitude from Collapse

This section is not about failure, and should not be read as a variant of docs/06-lifecycle/03-collapse-and-containment-protocols.md. That section covers Enterprise Collapse: a non-voluntary, condition-triggered failure state, reached through governance failure, value misalignment, operational breakdown, conflict escalation, or external threat, and followed by containment tiers (CPT-1 through CPT-3) and deconstruction steps. None of those triggers apply to a unit governed by intentional ephemerality. Its wind-down is scheduled, or condition-triggered from the start, rather than a response to drift or breakdown. A unit’s wind-down falls under exactly one of the two protocols in this chapter, never both, and the containment machinery described in §6.3 has no role in an ephemerality-driven wind-down.

Designed-Finite Ventures

Intentional ephemerality departs from the assumption that persistence is itself evidence of success. A unit’s finite lifespan is set deliberately, as a check against internal ossification and as a way of keeping resources in circulation rather than allowing them to settle into fixed positions. A unit may be wound down at the height of its success: the design decouples the end of a unit’s operating life from its performance, so dissolution under this section is a scheduled event rather than a diagnosis of unit performance.

The stated rationale is functional: it is intended to let the network redeploy resources, or end a unit that has outlived its usefulness, without waiting for a decline to make the case. A fixed lifespan is treated as one more parameter set at Genesis, alongside a unit’s charter, DEA scope, and initial resourcing, rather than as an outcome negotiated only once the unit is already underway.

The Graceful Sunset Process

Winding down a designed-finite unit is described in three parts, given together as a bundle rather than as separately sequenced steps:

Distribution of profits to members.
Dissemination of accumulated knowledge.
Encouragement of members to found new ventures addressing different problems within the network.

The model does not specify the sequencing, timing, or governance sign-off for these three actions, or which role executes them; this section does not supply a more elaborate procedure than the source gives. Where additional mechanism is wanted, it draws on the network’s existing dissolution machinery — structured offboarding, equity redistribution, and open record-keeping, per docs/06-lifecycle/01-ume-lifecycle-and-transition-states.md, or the SEP Completion phase’s handover artifacts and sunset report, per docs/06-lifecycle/02-sep-lifecycle-and-governance.md — rather than from any procedure specific to intentional ephemerality itself.

Leadership Assessed on Wind-Down, Not Persistence

The model reframes the metric by which leadership is judged: leadership is evaluated not by how long a unit persists, but by how effectively it distributes resources — both tangible and knowledge-based — before dissolving to seed new work. Facilitating a successful, graceful sunset is treated as standing alongside the launch of a new initiative, rather than as a lesser achievement. A stated implication is that new models of recognition are needed to reward this kind of leadership; no specific recognition mechanism is given.

A related, undeveloped framing positions sunset-at-success as a counter to entrenched too-big-to-fail dynamics: keeping resources in ongoing circulation rather than letting them accumulate inside units that have stopped needing them.

Rotation Breaks: A Proposed Mechanism, Not an Adopted Rule

The model raises, as an open design question rather than a stated policy, whether leadership positions should carry mandatory rotation breaks: a leader steps out of their seat and into a mentorship role elsewhere in the network, explicitly to prevent power from settling permanently in one area of expertise. This is preserved here as a proposal under consideration, because that is how the source material itself frames it — as a question, not a rule.

Several details are unspecified. Which leadership positions the proposal would cover — every leadership role network-wide, or only unit-level leads — is not stated. The break’s duration is not stated. Whether it would be triggered on a schedule, on a tenure threshold, or by some other condition is not stated. This section names the gap rather than filling it.

This is a different mechanism from the temporary rotation described for Mission-Driven units in docs/06-lifecycle/06-lifecycle-variants-by-unit-type.md: there, Operational-unit members rotate temporarily into a Mission-Driven unit to relieve burnout — a movement into a support role. Here, a leader rotates out of a leadership seat into mentorship — an anti-entrenchment measure. Both use the word “rotation,” but the two describe unrelated movements, in opposite directions, for different reasons, and should not be conflated.

The closest existing material in the corpus is incidental rather than a precedent for this proposal: a worked financial example lists rotating leadership stipends and rotating sabbaticals as options for allocating surplus (docs/appendices/cafe-examples.md), not as a governance mechanism, and it does not connect to the anti-entrenchment rationale described here.

Intentional ephemerality should also be kept separate from Intentional Cannibalization (docs/appendices/terminology.md §VI), the pattern by which the network itself proactively dissolves or restructures a UME it judges outdated, to seed better-aligned successors. The two differ in who initiates the wind-down and when the decision is made: ephemerality is a unit’s own founding design, fixed before the unit does any work; cannibalization is a network-level judgment made about an existing unit, at a time of the network’s choosing.

Conclusion

Intentional ephemerality adds a founding-stage design option to the UME and SEP lifecycles: a unit whose end is scheduled rather than earned or forced. It shares vocabulary with, but is functionally separate from, both Enterprise Collapse (unplanned failure) and Intentional Cannibalization (a network-initiated judgment about an existing unit). The model gives a three-part sketch of what a graceful sunset involves, and a reframed metric for judging the leadership that carries one out; it leaves the mechanics of sequencing, timing, and any anti-entrenchment rotation requirement unspecified.