HAO Lineage and Vocabulary Genealogy

A record of where the model came from, which of its earlier terms became current ones, and which were dropped.

1. Purpose

This appendix records the documented history of the Humanized Autonomous Organization (HAO) — the network’s coordinating framework — as an organizational-design model: the account its author gave of how the work began, the bodies of prior work it draws on, and the vocabulary it used before the current one.

The current vocabulary of the corpus — HAO, United Micro Enterprise (UME) — a small, self-managing venture team (≤ ~15 people), Strategic Enterprise Partnership (SEP) — a joint venture between teams, and Micro Enterprise Ecosystem (MEE) — the network’s protected internal economy — replaced an earlier vocabulary built on cellular metaphors. The earlier vocabulary is recorded here, in §4 and §5, as history. It is not live vocabulary, and the working chapters do not use it. docs/appendices/terminology.md remains the corpus’s authoritative glossary; where this appendix and that glossary differ, the glossary governs current usage and this appendix records what came before it.

Sources and method. This appendix was written from a staged extraction over material outside the corpus: a dated forum post by the author, a 19-entry lexicon on a sibling documentation site, two lexicon entries that were drafted in an AI interview transcript but never promoted to standalone files, a research index page, and a set of AI interview transcripts. No upstream archive was reopened to write this appendix. Every claimed successor term in §4 was separately checked against the live corpus in ~/code/hao/docs/, and three points where the staged extraction no longer matches the live corpus are marked where they occur.

On quotation. The corpus does not quote individuals. This appendix is the single exception: the author’s own recorded words are quoted here, sparingly, and each quotation is marked as the author’s. The value of the origin account is that it is a first-person record, so it is not paraphrased into the corpus register. Everything outside the marked quotations is this appendix’s own neutral-register summary. Material generated by AI systems in the source transcripts is summarized rather than quoted, since it is neither the author’s words nor a citable publication. Quotations follow the primary sources exactly, including their terminal punctuation; where a quotation contains a quotation of its own, the inner marks are set as single quotes for nesting, and no other change is made to any quoted text. Where a quotation stops short of the end of its passage, or resumes on a later line of the source, the appendix says so rather than joining the parts silently.

2. The author’s origin account

Source: ~/code/site-provide-coop/provide.coop/bits/tims-co-breakdown.txt, dated 2024-04-28, a forum or chat post. The sequence below follows the post as written. All quotations in this section are the corpus author’s own words from that post.

2.1 Motive and the earlier coinage

The author introduces himself as a staff DevOps engineer at a firm owned by private equity, previously employed at a non-profit whose board decided, in his words, to “sell all IP and assets and pivot focus” before arranging for staff to be hired by the acquirer. He gives that as the occasion for the post.

The idea is described as a centralized and decentralized network of intrinsically linked entities, engineered to implement polycentric governance principles so that the ecosystem acts as a mesh network for its participants. He then names it. In the author’s words: “I’m calling it a Cellular Cooperative.”

This is the earliest recorded name for the model. It is not the name the corpus uses.

The author states the multi-year motivation behind the project in a single sentence, in his own words: “Make owning a business as easy as applying for a job. For a wide range of industries.” Everything else in the post is offered as one part of that goal.

2.2 Encountering the term “polycentric governance”

The post records how the term entered the vocabulary. In the author’s words: “FWIW, I had no idea what ‘polycentric governance’ was until like a month ago… when I managed to write the right prompt to get one of those LLM AIs to inform me that PG is what I’ve been thinking about but didn’t have the words to discuss.”

The term is load-bearing throughout the rest of the corpus. Its recorded route of entry is a language model’s response to a prompt, dated roughly a month before the post, rather than direct engagement with the polycentricity literature. §3.1 records how this relates to the retrospective attribution of the concept to Ostrom.

2.3 The unit and the sociocratic circle

The post defines three units in sequence.

• Cellular Organization (CO): a wrapper that coordinates Cells, which the author states may itself be a publicly traded company, a non-profit, a cooperative, a school, or an institution. He distinguishes it from two named operating models. In the author’s words: “A CO is not Holacracy, or Sociocracy. But, both of those Operating Models can be implemented within a CO.”
• Cell / Cellular Unit (CU): an intentionally small group of actors, resources, stakeholders, and shared mission that produces and provides value. The relationship to sociocracy is stated directly. In the author’s words: “A ‘Cell’ is akin to a ‘Circle’ in Sociocracy. But more abstract.”
• Cellular Venture (CV): a group of Cells that have come together to produce shared value, which the author states implies that the Cells have defined and agreed on an Operating Agreement. Cells and actors inside a CV choose which governance model applies to them, from sociocracy, holacracy, or hierarchy.

A mandated cross-functional team is dismissed as a degenerate case of the CV: the author describes it as a hierarchy inside a hierarchy, for which he coins the acronym HIAH, and states that no autonomy exists within that structure.

The composition claim closes the definitional sequence. In the author’s words: “People -> Cell -> Cellular Venture -> Cellular Organization. Nothing really novel in that. It’s Sociocracy. :)”

A further group of terms is named in the post but left undefined, listed as more operational than structural: Cellular Integration, Cellular Lifecycle Management, Cellular Culture, Cellular Collapse, Cellular Degradation, Dynamic Contracts, and Dynamic Operating Agreements. Each is traced in §4.

2.4 The choice of limited-liability form over cooperative entity form

The post rejects the cooperative legal form explicitly. In the author’s words: “Also, this isn’t designed to take advantage of traditional Cooperative entity structures. It’s meant to be implemented in a Limited Liability Company, or a Series LLC.” The reason follows on the next line of the post, again in the author’s words: “That way each Cell has its own corporate veil.”

The stated design goal is a liability boundary per unit. Layering limited-liability entities, or using a series structure, gives each unit its own corporate veil in a way that a single cooperative entity holding all activity does not. The cooperative framing is retained at the level of culture and governance norms — worker ownership and democratic decision-making are stated as Cell characteristics on the sibling site’s cell.mdx — while the legal wrapper is deliberately something else. §3.6 records the same split for the cooperative movement as an influence.

2.5 Stated scope and stated limits

Two limits on the claim are recorded in the post itself.

The author anticipates readers proposing technology solutions and excludes them. In the author’s words: “So, no blockchain or DLT or web3 or any of that stuff is within the scope of what I’m sharing.” He characterizes what he is sharing as the architecture of a blueprint representing only the exterior of a home.

He also disclaims originality and authority for the vocabulary. In the author’s words: “Please keep in mind, there is no ‘official’ definition for these terms that I’ve been able to find, within this organizational metaphor.” The passage resumes on the next line of the post, again in the author’s words: “So… I’m kinda making up the terms as I go along. And I know, some of the concepts are likely labeled by some other word, or damn similar. :)”

That disclaimer bears on the rest of this appendix. The author does not claim the vocabulary was novel, only that he had not located prior art for it at the time of writing. The retrospective identifications of prior art recorded in §3 were made later.

2.6 Stated research method

The post describes the author’s validation approach: describing problems to language models and treating their predictions of his intended solutions as confirmation of his reasoning. It then reproduces two responses from a language model analyzing the Cellular Cooperative concept against cooperatives, holacracy and sociocracy, and agile teams, naming gaps in scaling democratic process, coordination overhead, and incentive design, and naming claimed innovations in hybrid governance, collective intelligence, and resilience.

On this appendix’s reading, the transcript is the earliest recorded outside review of the model; the author records the method but does not characterize the exchange this way. As a single language model’s response to the author’s own framing, it is not independent verification, and this appendix does not treat it as evidence for any claim beyond the fact that the exchange occurred.

The post and the sibling site’s cellular-organization.mdx reproduce wording traceable to the Background and concepts section of Wikipedia’s permanent revision 756005860 (Wikipedia contributors, 2016). The sibling site’s available Git history records the definition and its two scholarly footnotes entering together in commit 7863f9ac on 11 April 2024; the archived-post file enters that repository in commit 14e2c882 on 28 April 2024. Those repository dates do not establish when either artifact was drafted outside the repository or which local artifact supplied the other.

The two footnotes are contextual annotations to work on cellular organization (Schley, 2010; Snow, Miles, & Allred, 2003). They were not added after the sibling-site definition in the recorded file history. Neither the annotations nor that chronology establishes that either scholarly work influenced development of the HAO model, so §3 does not promote them to evidenced ancestry.

References for this chronology

• Schley, D. G. (2010). Origins and development of the cellular organization. In M. A. Rahim (Ed.), Current Topics in Management: Volume 14, Organizational Behavior, Performance, and Effectiveness (pp. 119–148). Transaction Publishers. https://doi.org/10.4324/9780203793985-6
• Snow, C. C., Miles, R. E., & Allred, B. B. (2003). Managing leading-edge multinational corporations. In B. McKern (Ed.), Managing the Global Network Corporation (digital ed., pp. 215–233). Routledge. https://doi.org/10.4324/9780203478813-21
• Wikipedia contributors. (2016). Cellular organizational structure. Wikipedia, permanent revision 756005860, 21 December 2016, 12:31:29 UTC. Cited section: “Background and concepts.” https://en.wikipedia.org/w/index.php?title=Cellular_organizational_structure&oldid=756005860

3. Intellectual ancestry

Each influence below is marked evidenced or asserted.

• Evidenced means the connection is shown in the primary sources reviewed for the staged extraction: the source states what was taken and where it came from, at or near the point where the borrowed idea is used.
• Asserted means the connection is claimed — most often on the research index page at ~/code/site-provide-coop/provide.coop/research/index.mdx — without support traced to the author’s working notes, and without the borrowed content appearing anywhere the claim could be checked against.

Two of the six are evidenced; four are asserted. The four asserted influences share a pattern: each is named on a research index page written after the model existed, identifying prior art for work already done, rather than a source the model was built from.

3.1 Ostrom and polycentricity — asserted

What is claimed to have been taken: the governing vocabulary and the conceptual root of polycentric governance as the decision-rights model for the Integrated Cooperative Network (ICN) — the reference cooperative business network.

Status: asserted. The research index page states that Ostrom-lineage work on multiple centers of authority is where the ICN’s governance model originates. That page states the derivation; it does not argue it, cite a specific passage, or trace a mechanism from the literature into the model.

The author’s own origin account gives a different route for the term. As recorded in §2.2, he describes discovering the phrase “polycentric governance” through a language model prompt about a month before writing, not through reading Ostrom. The two accounts are not strictly contradictory: a term can be encountered indirectly and its literature read afterward. But the research page’s framing, that this is where the model originates, describes a scholarly grounding identified after the fact rather than the route by which the vocabulary was actually acquired, and no source reviewed records the reading that would close the gap.

The term survived the vocabulary change intact. “Polycentric” remains load-bearing throughout docs/, and the Adaptive Governance Framework (AGF) — the network’s layered governance system — is defined in docs/appendices/terminology.md §II as a multi-level, polycentric governance model.

3.2 Beer’s Viable System Model and cybernetics — asserted

What is claimed to have been taken: a systems-theory basis for cellular organization generally.

Status: asserted. The research index page names Beer’s Viable System Model and the systems-theory traditions underneath cellular organization. A separate passing link to the Wikipedia article on variety in cybernetics appears in ~/code/provide.io/content/english/governance.md, offered as an aside rather than as a derivation.

No content specific to the Viable System Model — recursion, the viability criterion, or the five named systems — appears in the origin account, in any lexicon entry, or on the governance page. The connection is named on one index page and developed nowhere. It is the weakest-supported of the six.

3.3 Holonic manufacturing — asserted, and named in the sources as the closest prior art

What is claimed to have been taken: nothing is claimed to have been taken. Holonic manufacturing is named in the sources as the closest prior art to the model’s basic unit, the Cell, rather than as a source the Cell was derived from.

Status: asserted, and retrospective. The research index page describes an existing engineering literature on autonomous units that cooperate without central control, and observes that it comes from factories rather than from cooperatives. The page states this identification; it does not argue it. No comparison of the holon to the Cell is set out, no property of one is mapped onto the other, and no source from that literature is cited at the point of the claim.

The identification is retrospective on the evidence available. Holonic manufacturing is not mentioned in tims-co-breakdown.txt or in any lexicon entry, and the author does not cite it at the point where he coins the Cell. It appears only on the later research index page. Read together with the author’s own disclaimer in §2.5 — that he expected the concepts were already labeled by other words — the identification is best read as a later answer to a question the author had already posed about his own vocabulary, not as an unacknowledged debt.

3.4 Beyond Budgeting — asserted

What is claimed to have been taken: devolved financial authority, framed on the research index page as the question of how an autonomous unit obtains money without asking permission.

Status: asserted, and retrospective. The claim rests on the research index page alone and is stated rather than argued. Nothing corresponding to it appears in the origin materials. The status matches holonic manufacturing.

Beyond Budgeting is the one asserted influence with substantial representation in the assembled research library: docs/appendices/references.md §4 lists five works on it. Those works were collected; no source reviewed shows any of them being used.

3.5 Sociocracy — evidenced

What was taken: the analogy between the basic unit and the sociocratic circle; the layering of Cell, Cellular Venture, and Cellular Organization; and the position that a Cellular Organization can host sociocracy or holacracy as an internal operating model without being either.

Status: evidenced. This is the most directly attested influence of the six, cited by the author in his own words at the moment of coining the terms, three times in a single post — the Cell-to-Circle analogy, the statement that a CO is neither holacracy nor sociocracy but can host both, and the composition claim that the four-level stack is sociocracy. All three are quoted in §2.3.

The corpus retains the mechanism under a different label. docs/appendices/terminology.md §II defines Consent Governance as a decision-making model focused on resolving objections rather than achieving majority rule, without naming sociocracy as its source.

3.6 The cooperative movement — evidenced at the level of culture, rejected at the level of legal form

What was taken: worker-ownership and democratic-decision norms at the level of unit culture, and the word “Cooperative” in the model’s original name.

What was declined: the cooperative entity form itself.

Status: evidenced, with the split recorded in the sources. Both halves are attested. The sibling site’s cell.mdx states that Cells are typically structured as worker-owned cooperatives, and the research index page catalogs a work on humanistic governance in democratic organizations as a source. Against that, governance.md and tims-co-breakdown.txt both state that the model is deliberately not built on cooperative legal entity structures, in favor of an LLC or Series LLC so that each unit carries its own corporate veil (§2.4).

The cooperative movement supplied the internal governance ethic. It did not supply the entity form. This is the only influence in this section where the sources record both what was adopted and what was declined, and the reason for declining it.

4. Vocabulary genealogy

The earlier vocabulary is drawn from the 19 files in ~/code/site-provide-coop/provide.coop/docs/lexicon/, plus two entries drafted in AI interview transcripts and never promoted to standalone lexicon files (Mycorium and Holographic Organization), for 21 entries. Current terms were checked against docs/appendices/terminology.md and against targeted searches of ~/code/hao/docs/.

Scope of the rename. The rename is specific to this corpus. ~/code/site-provide-coop/provide.coop/docs/icn/ is a separate documentation tree that remains live and continues to use “Cell” and “Cellular Venture” as of its most recent edits, dated 2026-08-04. A term marked below as renamed within this corpus may still be the current term on that site.

Status vocabulary used in the table. Renamed means both terms are defined and the definitions correspond. Unconfirmed means a successor is plausible on the definitions but no source states the equivalence. Dropped, no successor means no current term occupies the same role.

Twenty-one rows. The middle column sorts each row into exactly one of three buckets, so the count below can be checked against the table directly.

• Eleven rows name a current corpus term that stands in for the earlier one, whether by rename, survival unchanged, absorption, or retention of the phrase: Cell, Cellular Venture, Cellular Degradation, Cellular Collapse, Cellular Lifecycle Management, Dynamic Contract, Dynamic Operating Agreement, Polycentric Governance, Polycentricity, Intentional Idempotency, and Walled Garden.
• Three name a current term but mark the equivalence unconfirmed: Cellular Organization, Cellular Integration, and Dynamic Cross-Network Contracts.
• Seven name no current term at all: Cellular Culture, Polycentric+, Arm’s Length, Emergent Cooperativism, Virtuous Cycle of Support, Mycorium, and Holographic Organization.

Cutting across those buckets, four rows record content that outlived the word carrying it. In two of them a current term stands in the earlier term’s place, so they fall in the first bucket: Idempotence is a named design principle, and “walled garden” is retained as the same phrase. In the other two the branded term has no successor term and only the underlying claim persists, in ordinary descriptive language rather than in any defined term, so they fall in the third: “fractal” for Holographic Organization, and “mycelial network” and “mycorrhizal networks” for Mycorium. §5.2, §5.4, and §5.7 treat all four.

5. Dropped concepts

Each entry below states what the concept meant, whether the sources record a reason for dropping it, and whether the corpus covers the same ground under another name. Where no source records a reason, this appendix states “no recorded reason” and does not supply one. No reason was reconstructed for any entry in this section.

5.1 Not dropped: Cellular Degradation and Cellular Collapse

These two terms were checked against the possibility that they had been dropped. They had not been. Both were renamed and formalized.

docs/06-lifecycle/03-collapse-and-containment-protocols.md was read directly for this appendix. It defines Enterprise Degradation as a pre-collapse state characterized by drift from core principles, reduced functionality, or social dysfunction, and specifies collapse under five trigger classes, a seven-phase lifecycle (Detection, Triage, Intervention, Confirmation, Containment, Deconstruction, Reintegration), three containment tiers, deconstruction steps covering asset inventory and equity resolution, and a post-collapse learning process. docs/appendices/terminology.md §VI carries both terms. The current treatment is considerably more developed than the earlier lexicon entries, which were unstructured paragraphs.

This entry is recorded to correct the premise with evidence rather than to describe a loss.

5.2 Intentional Idempotency

What it meant: processes designed so that redundant or revisited decisions do not cascade into failure, drawing on both the mathematical sense of idempotence and a stated Zen Buddhist framing of detachment from outcomes.

Reason for the drop: no recorded reason.

Current coverage: partial. “Idempotence” survives as a bare design principle, defined as interactions that should be repeatable without degradation, in docs/07-human-systems/05-synthesis-human-systems-as-infrastructure.md, in docs/claude-20250429/06-human-centered-design-elements.md, and in docs/humanized-autonomous-organization.md line 2406. It appears there as one of six listed principles, alongside Observability, Degeneracy, Intentional Inefficiency, Versionability, and Intergenerational Capacity. The philosophical framing did not carry forward, and the concept is no longer a standalone named term. The staged extraction recorded this as one of three principles; the live corpus lists six, and the six are as named here.

5.3 Emergent Cooperativism

What it meant: that the network’s cooperative structures are not fixed but evolve continuously to fit context.

Reason for the drop: no recorded reason.

Current coverage: none under another name. The general theme of adaptability recurs throughout the corpus, but it is not tied to this or any single term, and no defined term occupies the role.

5.4 Holographic Organization

What it meant: that each unit reflects the whole network’s values and structure fractally, so that the microcosm mirrors the macrocosm. The source is a lexicon draft in an AI interview transcript that iterates through seven generations: an initial entry, two that expand it, three that successively simplify it, and a seventh that reverts to a formal register stated to suit an academic audience. The arc ends where it began rather than at the simplest version. It was never promoted to a standalone lexicon file.

Reason for the drop: no recorded reason for dropping the term itself.

Current coverage: the core claim survives under the word “fractal” (§4). No source documents the substitution. This is a change of word without any record of a decision to change it.

5.5 The three unit types in Cellular Lifecycle Management

What it meant: that lifecycle management, onboarding, monitoring, and support were to be tailored per unit type, across three types — Operational, Mission-Driven, and Research and Exploratory. The source specifies different treatment for each. Operational units receive heavy investment in mentorship, so that reliable processes can be passed on and dependence on specific individuals is reduced. Mission-Driven units receive ethical stress-testing alongside standard viability checks, on the stated ground that they carry the pressure to balance ethical practice against market viability. Research and Exploratory units are granted the widest latitude, offset by a mandatory cross-unit reporting obligation intended to prevent isolation and to surface harmful research directions early. Source: ~/code/site-provide-coop/provide.coop/gemini-on-clm.mdx lines 72–74.

Reason for the drop: no recorded reason.

Current coverage: none. docs/06-lifecycle/01-ume-lifecycle-and-transition-states.md specifies a single uniform seven-phase lifecycle (Genesis, Incubation, Validation, Maturation, Integration, Evolution, Dissolution) with no type-differentiated tracks. A search of docs/ for the three type names returns no matches. This is a loss of granularity rather than a rename. The label CLM was renamed to UME Lifecycle Management; its type-differentiated content was not carried across.

5.6 Intentional Ephemerality

What it meant: Cellular Ventures designed with a defined lifespan from the outset, with dissolution treated as a success condition rather than a failure. The source states that a venture might be wound down at the height of its success; that leadership should be assessed not on how long entities persist but on how effectively they distribute resources before dissolving to seed new work; and it proposes mandatory rotation breaks in which leaders step into mentorship roles elsewhere in the network, as a check on entrenchment. Source: ~/code/site-provide-coop/Intentional Ephemerality.txt.

Reason for the drop: no recorded reason.

Current coverage: partial, and the specific claims are absent. SEPs carry a formal Completion phase with a sunset report in docs/06-lifecycle/02-sep-lifecycle-and-governance.md, and graceful-sunset language appears in docs/humanized-autonomous-organization.md. The three sharper claims do not appear anywhere in docs/: dissolution at peak success as a sought outcome, leadership evaluated by its facilitation of wind-downs, and mandatory rotation breaks as an anti-entrenchment mechanism. A search for “ephemeral” across the corpus returns no matches. The nearest echo is incidental — rotating leadership stipends and rotating sabbaticals appear in a worked financial example in docs/appendices/cafe-examples.md line 66, presented as an option for surplus rather than as a governance principle.

5.7 Mycorium

What it meant: the whole network as a self-organizing socioeconomic system modeled on fungal networks — interconnected, resilient, and able to draw on underused resources in existing markets.

Reason for the drop: no recorded reason for dropping the branded term.

Current coverage: split, and this entry carries a correction to the staged extraction. Two things happened to the term independently.

First, the fungal metaphor itself survived without the name and without attribution back to it, reappearing as “mycelial network” for the HAO layer and as “mycorrhizal networks” for SEPs, in docs/humanized-autonomous-organization.md and docs/12-icn/01-structural-features.md. Neither use carries a caveat about the limits of biological analogy.

Second, the name “Mycorium” does appear in the current corpus, in a different sense from the earlier one. docs/09-adversarial-analysis/01-threat-taxonomy.md and docs/09-adversarial-analysis/04-external-and-technical-vectors.md use it as the sources’ term for the network’s evolving shared language and history, and identify it as the target of the threat pattern the chapter names Lexical Drift. Chapter 09 uses the term to report what its sources call something, not as a live corpus term. The staged extraction for this appendix recorded zero matches for “Mycorium” in the corpus; chapter 09 was written after that extraction. Both senses are recorded here because the sources carry both, and the corpus does not reconcile them.

One feature of the earlier entry is worth recording against both later uses. Every one of its three drafts carried a Limitations section stating that “Mycorium” was a deliberately evocative metaphor rather than a literal description of operations, and warning that overemphasizing biological analogies risks obscuring the social and economic factors that actually shape the network’s behavior. That caveat did not carry forward to either successor use.

5.8 Concepts dropped without a separate entry

Four further terms in §4 are marked dropped with no successor and are not treated at length here, because the sources record nothing about them beyond the entries themselves: Cellular Culture, Polycentric+, Arm’s Length, and Virtuous Cycle of Support. No reason is recorded for any of the four. Arm’s Length is the least consequential of them: its lexicon entry reproduced a general legal definition rather than defining anything specific to the model.

6. The founding metaphor

Sources: ~/code/site-provide-coop/provide.coop/research/ai/gemini/2024-04-01-icn-interview-1/gemini_icn-interview-1_p07r01_the-pufferfish.mdx and …p07r02_the-pufferfish.mdx, dated 2024-04-06.

This section records a metaphor that appears in the source material. The corpus does not use it, and this appendix does not adopt it as an explanatory device. It is recorded because it is the most developed metaphor in the model’s history and because the tactics derived from it are, in the sources, treated as design guidance.

6.1 The prompt and the mapping

The metaphor originates in a prompt the author wrote. In the author’s words: “Consider this. The market is the ocean. A corporation is a shark. A non-profit is a guppy. A cooperative is a jellyfish. And Contribulo, the ICN, provide.io, and all the Cells it is composed of, is a puffer fish.”

A second prompt in the same exchange adds an anatomical mapping of three named entities plus the units. In the author’s words: “Contribulo is the skin of the puffer fish. And the mouth, and anus. provide.io is the brain, the ICN is the internal ecosystem, and Cells are the organs.”

Three of the four map to entities the corpus still names. Contribulo is the boundary entity, and its role as the surface in contact with the external market corresponds to the Public Market Interface function the corpus assigns it. provide.io is a real entity. The ICN is the reference network. The fourth, Cells, is the earlier name for UMEs (§4).

6.2 Tactics derived from the metaphor

The following were generated across both response rounds of the exchange, from the pufferfish’s biology. They are summarized rather than quoted, since they are model-generated text rather than the author’s words. None was implemented as described, and none appears in the corpus.

• Defense as a risk to its holder. The model’s central advantage is also its central hazard if deployed carelessly, and needs safeguards and deliberate timing.
• Inflation control. Pufferfish inflate for a reason rather than constantly. Read as a caution against process growth for its own sake.
• The venom factor. Conflict between the network and an individual unit is framed as the analogue of a self-inflicted venom risk, which is the stated reason conflict-resolution mechanisms are treated as load-bearing.
• The feint. Some predators are deterred by the inflated form alone. Read as signaling strength while resources are low, in order to buy time rather than to deceive.
• Near-360-degree vision. The pufferfish’s independently moving eyes are read as an analogue for network-wide situational awareness across distributed units, conditional on investment in knowledge-sharing tooling.
• Chain-reaction risk. Proposes dormant units that can be activated quickly in a crisis, and stress-testing whether units can operate if cut off from central resources.
• Fail fast, learn faster. The structure is described as forgiving of unit-level experiments, with the caveat that lessons from failure must be distributed network-wide.

The second response turns from strategy to vocabulary management, proposing that terms such as Mycorium and Emergent Cooperativism be taught through mini-courses, an awards program, and a language-ambassadors role. That exchange is where the earlier lexicon’s most elaborate vocabulary-management proposals originate. None was implemented, and both terms it proposed teaching were later dropped (§5.3, §5.7).

6.3 The corpus is otherwise metaphor-poor

No comparable sustained, multi-part metaphor appears in docs/. The one dedicated metaphor note in the corpus, docs/notes/metaphor-family-systems.md, is short and in a different register: a few lines describing organizations that grow up as dysfunctional families under leaders missing the skills that would help them lead. It has no anatomical mapping and derives no tactics.

The corpus is not metaphor-free. Single-phrase metaphors survive independently, as recorded in §4: “walled garden”, “mycelial network”, “mycorrhizal networks”, and “fractal”. None is assembled into a governing image with an internal logic in the way the pufferfish was, and the corpus makes no argument from any of them.