Lifecycle Variants by Unit Type

Introduction

Source and provenance. This section rests on ~/code/site-provide-coop/provide.coop/gemini-on-clm.mdx, three successive AI-generated passes over the same framework, staged for this corpus and never checked against any other source. The staged extraction describes it as a drafting artifact rather than a ratified specification, and notes that its passes are not always mutually consistent with each other — including on how many lifecycle stages the framework carries. Per-unit-type assignments below were checked against that primary file directly, because an earlier staged summary of the same material misattributed one of them. The typology is recorded because the corpus’s own lifecycle treatment is uniform across unit types and this is the only source that varies it; it is not adopted as specification.

The seven-phase lifecycle described in docs/06-lifecycle/01-ume-lifecycle-and-transition-states.md — Genesis, Incubation, Validation, Maturation, Integration, Evolution, Dissolution — applies uniformly across every United Micro Enterprise (UME) — a small, self-managing venture team (≤ ~15 people). This section adds a differentiated layer on top of that uniform model: three unit types, each carrying a distinct operating posture, that call for different handling at several of the same lifecycle stages. It does not replace or renumber the seven-phase model; it describes how that model plays out differently depending on which kind of UME is passing through it.

A note on terminology. The three-type framework and the seven-phase UME lifecycle come from different points in the model’s development and use their own stage vocabulary — proposal, formation, onboarding, monitoring, growth, and transition or dissolution — rather than Genesis through Dissolution. The two sequences cover similar ground closely enough to read side by side, but no source states a formal one-to-one correspondence between them, and this section does not assert one. A stage discussed below should be read as an elaboration of the territory a like-named UME phase covers, not as a renaming of that phase.

The Three Unit Types

Type-Differentiated Treatment Across the Lifecycle

Proposal

Feasibility review at the proposal stage takes the intended unit type into account. Proposals for Operational units emphasize long-term viability. Proposals for Research and Exploratory units include an explicit statement of the learning goal the unit pursues, alongside its stated potential benefits.

Formation

Standard formation templates carry type-specific addenda — temporary leadership roles for Research and Exploratory units, for example. Dynamic Enterprise Agreement (DEA) — a versioned operating agreement replacing fixed bylaws — clauses can include pre-planned exit provisions specific to type: an escape hatch for a Research and Exploratory unit that reaches an ethical gray area, and a sunset provision for a short-term Mission-Driven unit. This is the one point in the model where a sunset mechanism is tied to a specific unit type rather than offered network-wide; see docs/06-lifecycle/05-intentional-ephemerality.md for the network’s general treatment of a unit designed from Genesis to have a finite lifespan.

Onboarding

Onboarding is type-specific in both content and connections. Operational units train on reliable process execution; Mission-Driven units train on conflict resolution; Research and Exploratory units train on treating failure as productive rather than as a discouraged outcome. Cross-unit introductions follow the same logic: Operational units are linked with innovative ventures in similar industries, and Research and Exploratory units are connected with community groups that stand to be affected by their work.

Monitoring and Support

The same signal reads differently by type: high variance in a unit’s progress can be a positive indicator for a Research and Exploratory unit and a warning sign for an Operational unit. Support is tailored per type:

• Operational units receive heavy investment in mentorship, so that reliable processes pass on and the unit’s dependence on any specific individual falls.
• Mission-Driven units receive ethical stress-testing alongside the standard viability checks applied to every unit, in recognition of the stated pressure to balance ethical practice against market performance. Support at this stage can include temporary rotation of Operational-unit members into the Mission-Driven unit, to relieve burnout. This is a distinct mechanism from the leadership rotation breaks described in docs/06-lifecycle/05-intentional-ephemerality.md: there, a leader rotates out of a seat and into mentorship elsewhere in the network; here, members from a different unit type rotate in temporarily to provide relief.
• Research and Exploratory units are granted the widest latitude of the three types, offset by a mandatory cross-unit reporting practice — Show and Tell — intended to prevent that latitude from becoming isolation and to allow early, network-wide detection of a research direction headed somewhere harmful.

Growth

Growth is also read differently by type. Operational-unit growth is judged on reliability over speed. A successful Mission-Driven unit is expected to spawn semi-autonomous sub-units to preserve agility as it grows. Findings from a Research and Exploratory unit can lead to an entirely new unit type being recognized within the network.

Transition or Dissolution

Reaching this stage remains, across all three types, a healthy possibility rather than a default indicator of failure. An Operational unit may be absorbed into the network’s core function rather than dissolved outright. A Mission-Driven unit’s dissolution is oriented toward maximizing the lessons learned for similar future ventures. Across all three types, the model applies one diagnostic question network-wide at this stage: whether a unit’s lifespan was a natural conclusion or a signal of a systemic flaw, examined for patterns across unit types rather than case by case.

A Support Function Requiring Composite Expertise

Supporting units at this level of differentiation is described as requiring expertise spanning data analysis, organizational dynamics, and forward-looking judgment, rather than a single specialization. Success at this stage is also measured through signals — sentiment analysis of internal communication, anonymized well-being surveys — that sit alongside, rather than inside, the network’s existing Value Alignment Monitoring (VAM) — ongoing checks that actions match stated principles — and Enterprise Culture Cultivation (ECC) tracking. VAM and ECC track alignment and cohesion; the stress- and burnout-specific signals described here are not currently named as part of either.

What This Section Does Not Cover

This typology is a layer added to the UME lifecycle model, not a substitute for it. It does not use, and should not be read as reviving, the earlier “Enterprise Degradation” or “Enterprise Collapse” vocabulary; failure-triggered dissolution, for any unit type, remains governed by docs/06-lifecycle/03-collapse-and-containment-protocols.md. Nor does the differentiation described here extend to Strategic Enterprise Partnerships (SEPs) — a joint venture between teams — whose own lifecycle is described separately in docs/06-lifecycle/02-sep-lifecycle-and-governance.md; the model’s source material for this typology precedes the current SEP/UME distinction and speaks only in terms of the unit type, without extending it to partnerships between units.

Conclusion

Operational, Mission-Driven, and Research and Exploratory units pass through the same named lifecycle differently: different proposal emphases, different formation addenda, different onboarding content, different monitoring signals and support, different growth patterns, and different framings of a healthy transition. None of this changes the seven-phase model itself; it specifies how that model should be read differently depending on which of the three types a given UME is.