{"id":"41bc3f07-6582-4056-bdee-2f7f1df18907","entityType":"agent","slug":"clawhub-deciqai-dunbars-number","name":"Dunbar's Number","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-dunbars-number","canonicalPath":"/agent/clawhub-deciqai-dunbars-number","generatedAt":"2026-10-11T04:35:00.808Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T02:09:43.656Z","emptyReason":null},"description":"Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"... Skill: Dunbar's Number Owner: deciqai Summary: Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:58:23.932Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/dunbars-number.json) v1.0.4 | 2026-07-09T11:17:07.941Z | u","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:dunbars-number","sourceUrl":"https://clawhub.ai/deciqai/dunbars-number","homepage":"https://clawhub.ai/deciqai/skills/dunbars-number","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/dunbars-number","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/dunbars-number","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":62,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T02:09:43.656Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T02:09:43.656Z","emptyReason":null},"stars":null,"forks":null,"downloads":1194,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T02:09:43.642Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T02:09:43.656Z","lastCrawledAt":"2026-10-11T02:09:43.642Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T02:09:43.642Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T17:58:23.932Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/dunbars-number.json)","fileCount":6,"zipByteSize":12617},{"version":"1.0.4","createdAt":"2026-07-09T11:17:07.941Z","changelog":"Refresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)","fileCount":6,"zipByteSize":12333},{"version":"1.0.3","createdAt":"2026-07-08T11:00:44.065Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":8057},{"version":"1.0.2","createdAt":"2026-07-08T00:45:46.764Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":8138},{"version":"1.0.1","createdAt":"2026-07-07T20:32:21.655Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8149},{"version":"1.0.0","createdAt":"2026-06-27T09:18:01.711Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8064}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:dunbars-number","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T04:35:00.804Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-dunbars-number/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T02:09:43.656Z","emptyReason":null},"readme":"Skill: Dunbar's Number\n\nOwner: deciqai\n\nSummary: Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T17:58:23.932Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/dunbars-number.json)\n\nv1.0.4 | 2026-07-09T11:17:07.941Z | user\n\nRefresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)\n\nv1.0.3 | 2026-07-08T11:00:44.065Z | user\n\nFooter now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:45:46.764Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T20:32:21.655Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-06-27T09:18:01.711Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 12617 bytes\n\nFiles: examples/ai-native-startup-scaling-2023-2026.md (6972b), examples/dunbar-1992-wl-gore-associates.md (4575b), references/sources.md (1956b), skill-card.md (2608b), SKILL.md (8076b), _meta.json (133b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n  More: deciqai.com/c/dunbars-number\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with `network-effects` (different coordination mechanisms below vs. above 150), `principal-agent` (exceeding 150 multiplies agency problems informal trust can no longer cover), `founder-mindset` (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n- AI-native startup hiring fast on abundant AI-era capital / AI-adoption demand — \"we scaled from 20 to 150 in a year and coordination is breaking\"\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use `principal-agent`); challenge is growing a network beyond 150 (use `network-effects`).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify layer:** headcount → Dunbar layer (5/15/50/150/500/1,500) → distance to next breakpoint.\n\n**Step 2 — Audit coordination:** how does the group coordinate? (informal trust / formal process / hierarchy) — where are breakdowns?\n\n**Step 3 — Diagnose mismatch:** does coordination mechanism match group size? (below 50: direct knowledge ok; 50–150: structured trust ok; above 150: formal hierarchy required)\n\n**Step 4 — Prescribe structure:** A) Split — sub-units each below 150 with explicit interfaces; B) Formalize — replace relationship-based coordination with documented processes; C) Layer — add management tier.\n\n**Step 5 — Set thresholds:** current ceiling / trigger for next structural review / Gore parking-lot rule (headcount cap per unit).\n\n**Step 6 — Validate culture claims:** \"Lost startup feel\" — Dunbar exceeded or culture drift? \"Need better communication\" — is structure the actual solution?\n\n### Output template\n```\nDunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]\n```\n\n*→ Method in Action: [Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md)*\n*→ 2026 lens: [Scaling an AI-native startup team (2023–2026)](examples/ai-native-startup-scaling-2023-2026.md) — how AI capital compresses the timeline to the ~50 and ~150 breakpoints*\n\n## Pack: Dunbar Number Across Domains\n\n| Domain | Layer | Key implication |\n|---|---|---|\n| Founding team (1–15) | Sympathy group | No process needed; direct knowledge |\n| Seed-stage (15–50) | Affinity group | Informal still works; minimize overhead |\n| Series A (50–80) | Approaching ceiling | Begin formalizing roles + reporting |\n| Series B / Pre-150 (80–149) | Just below limit | Build management layer before hitting 150 |\n| 150-person threshold | Dunbar crossed | Mandatory: documented processes + explicit hierarchy |\n| 150–500 / 500+ | Acquaintance / multiple groups | VP layer + OKRs; federated units each below 150 |\n| Remote teams | ~50–70 (compressed) | Video/async reduces relationship maintenance efficiency |\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We just need better communication tools\" | Above 150, the problem is neocortical capacity. Slack does not fix Dunbar. |\n| [D] \"We can maintain flat culture as we grow\" | Flat culture works below 50. Above 150, informal coordination structurally fails. |\n| [D] \"We'll hire great people who don't need management\" | Quality of people doesn't change cognitive limits. |\n| [D] \"Communication problems are a people issue\" | At ~150, communication problems are architectural. HR interventions treat the symptom. |\n| [D] \"The founders just need to be more visible\" | Founder visibility works below 150. Above it, all-hands don't substitute for structure. |\n| [D] \"We lost our startup feel — must have been wrong hires\" | The startup feel was a Dunbar-layer property of a sub-50 group. Hires are not the issue. |\n| [D] \"More team-building will restore cohesion\" | Works within the 150-layer. Across groups above 150, it produces temporary warmth, no structural repair. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Headcount crossed 150 without any structural change or management layer addition\n- Founder still coordinating a 200-person company via personal relationships\n- \"Communication problems\" diagnosed as interpersonal without checking if Dunbar limit was crossed\n- Org chart flat beyond 50 with no explicit coordination mechanism\n- Acquisition integration plan assumes two informal cultures can merge without formal structure\n\n## Verification\n\n- [ ] Headcount mapped to Dunbar layer explicitly; distance to next breakpoint calculated\n- [ ] Coordination mechanisms audited against group size requirements\n- [ ] Root cause identified: architectural vs. interpersonal vs. incentive\n- [ ] Structural prescription chosen (split / formalize / layer); sub-unit targets set below 150\n- [ ] Growth trigger for next structural review defined\n- [ ] \"Culture problem\" vs. \"architecture problem\" distinction made explicitly\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/dunbars-number** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/dunbars-number.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224703932\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. \"The Lattice Organization — A Philosophy of Enterprise.\" Internal document distributed to Gore associates (circa 1976). The Gore founding philosophy. (Not a formally published journal article; the widely cited secondary source for Gore's ~150 plant cap is Gladwell 2000, Ch. 5, above.)\n- Dunbar, R. I. M. (2021). \"Dunbar's number: why my theory that humans can only maintain 150 friendships has withstood 30 years of scrutiny.\" *The Conversation*, May 2021. Dunbar's own 30-year restatement — the limit is a cognitive/neocortical constraint, not one technology (social media, collaboration tools, or AI) can raise.\n- On the 2023–2026 AI funding-and-hiring environment: contemporaneous, widely reported venture-capital concentration in AI and rapid headcount growth at leading AI-native companies (e.g., ongoing press coverage of OpenAI and Anthropic scaling). Cited as a well-documented general pattern for the \"capital compresses the timeline to each Dunbar breakpoint\" claim — not as any single unverified figure.\n\nFile v1.0.5:examples/ai-native-startup-scaling-2023-2026.md\n\n# Method in Action: Scaling an AI-Native Startup Team (2023–2026)\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\nBetween 2023 and 2026, a distinctive class of company emerged: the **AI-native startup**. Powered by generative-AI product demand and an unusually deep venture-funding environment for AI, these companies raised large rounds early and hired far faster than the classic SaaS growth curve. The pattern that recurred — reported across founder essays, investor commentary, and press coverage of companies such as OpenAI, Anthropic, and a wave of well-funded application-layer startups — is that **capital compresses the timeline to each Dunbar breakpoint**. A team that historically took three or four years to reach 150 people can now cross that line in twelve to eighteen months. The neocortical limit does not move; the calendar does. So the ~50 and ~150 breakpoints, where informal trust fails and formal structure becomes mandatory, arrive sooner than the founders' intuition expects. This example walks the anchor case through the skill's six-step Process.\n\n---\n\n**Step 1 — Identify layer.** Take a representative AI-native startup that raised a large early round and grew from roughly 20 to roughly 160 people inside about a year and a half. At 20 the company sits in the **affinity-group layer (15–50)** — informal coordination still works. Its trajectory takes it through the **~50 breakpoint** (approaching the ceiling of what direct mutual knowledge supports) and toward the **~150 Dunbar limit** where formal hierarchy becomes architecturally mandatory. Distance-to-breakpoint is the critical number: growing at even five to ten hires a month, the ~50 line is a few months out and the ~150 line arrives within the funding cycle — not \"someday.\"\n\n**Step 2 — Audit coordination.** Early on, coordination is pure informal trust: the founders know every engineer, decisions happen in a shared channel, and there is no documented process. The observable breakdowns as headcount climbs are the classic Dunbar symptoms — \"we don't know who owns what anymore,\" duplicated work between teams that didn't know the other existed, onboarding that no longer happens by osmosis, and founders becoming a decision bottleneck. In AI-native firms these show up faster because so many hires are senior and expensive, and because rapid model/product iteration multiplies the number of in-flight decisions.\n\n**Step 3 — Diagnose mismatch.** Below 50, direct knowledge is adequate; the AI startup's early informal style *matched* its size. Crossing 50 into the 50–150 band, the mechanism must shift to **structured trust** — explicit roles, reporting lines, and lightweight process. Approaching 150, the mismatch becomes acute: informal trust is being asked to coordinate a group that has exceeded the neocortex's capacity to track every relationship. The root cause is **architectural, not interpersonal** — the very trap the skill's Red Flags warn about (\"communication problems diagnosed as interpersonal without checking if the Dunbar limit was crossed\").\n\n**Step 4 — Prescribe structure.** The right prescription combines two of the skill's three moves. **Formalize** first — replace relationship-based coordination with documented ownership, decision rights, and written process — because this should begin *before* 150, ideally around the 80-person mark per the skill's Pack (\"build a management layer before hitting 150\"). Then **Layer** — add a management tier so the founders stop being the single coordination hub. **Split** into sub-units each below 150 becomes the tool for the next phase of growth (federated teams with explicit interfaces), echoing the W.L. Gore plant-cap logic in the companion example.\n\n**Step 5 — Set thresholds.** Set an explicit current ceiling and triggers: begin formalizing roles and reporting at ~50; complete a management layer before 80–100; treat 150 as a hard structural-review line where documented processes and explicit hierarchy are non-negotiable; and adopt a Gore-style per-unit cap (each functional pod or \"house\" kept below ~150) for growth beyond that. Because capital lets AI-native firms hire fast, these triggers should be defined *at planning time*, not discovered after the coordination breakdown.\n\n**Step 6 — Validate culture claims.** When such a company says \"we lost the startup feel,\" the skill forces the diagnostic question: is this Dunbar exceeded, or culture drift? For a company that went from 20 to 160 in eighteen months, the honest answer is almost always that a sub-50-group property (everyone knowing everyone) was structurally lost by crossing 150 — not that the wrong people were hired. And \"we just need better communication tools\" is precisely the rationalization the skill flags: Slack does not fix Dunbar. The AI-native twist is that these teams are unusually tempted to believe their own AI tooling will substitute for structure — but internal copilots and better dashboards do not raise the neocortical ceiling.\n\n---\n\n**Output template applied**\n\n```\nDunbar Org Analysis: AI-native startup, ~20 → ~160 in ~18 months\nCurrent layer: crossing 150 (Dunbar limit) | Distance to next breakpoint: hit ~150 inside the funding cycle\nCoordination mechanism: informal trust (unchanged from 20-person era) | Breakdown points: unclear ownership, duplicated work, founder bottleneck, onboarding-by-osmosis fails\nRoot cause: architectural (capital compressed the timeline; neocortical limit did not move)\nPrescription: formalize (from ~50) + layer (before ~80–100) → split into sub-units later | Sub-unit targets: ≤150 | Trigger: hard structural review at 150; per-pod cap thereafter\n```\n\n**The generalizable lesson:** abundant AI-era capital and AI-native competition change *how fast* you reach the Dunbar breakpoints, not *where* the breakpoints are. Founders who assume the informal phase lasts as long as it did for a bootstrapped or slowly-funded company are systematically surprised. The fix is to pre-commit to the ~50 and ~150 structural triggers on the way up, while the team is still small enough to install them cheaply.\n\n*Sources: Dunbar, R. I. M. (1992), \"Neocortex size as a constraint on group size in primates,\" Journal of Human Evolution 22(6), 469–493 (the ~150 figure and breakpoint layers). Gladwell, M. (2000), The Tipping Point, Ch. 5 (W.L. Gore ~150 plant cap). Robin Dunbar, \"Dunbar's number: why my theory that humans can only maintain 150 friendships has withstood 30 years of scrutiny,\" The Conversation (2021) — Dunbar's own restatement that the limit is cognitive, not technological. On the 2023–2026 AI funding and hiring environment: widely reported venture-funding concentration in AI and rapid headcount growth at leading AI-native companies (e.g., contemporaneous reporting on OpenAI and Anthropic scaling), treated here as a well-documented general pattern rather than any specific unverified figure.*\n\nFile v1.0.5:examples/dunbar-1992-wl-gore-associates.md\n\n# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering choice with measurable operational consequences. Plants above 150 showed formal management emergence, political behavior, and productivity loss. Plants below 150 maintained voluntary coordination, peer accountability, and Gore's characteristic innovation culture.\n\nThe mechanism: in a group of 150, every person can maintain a mental model of every other person's trustworthiness, competence, and relationships. Free-rider problems are visible and self-correcting. Reputation mechanisms work because everyone knows everyone. Above 150, this breaks down: you cannot know and track 200 people's relationships — so you must rely on formal rules, titles, and documented processes to substitute for the relationship knowledge you no longer have.\n\nThis has direct implications for acquisition integration, org design at Series B/C, and community building:\n\n- **Series A → B transition** (30–60 → 80–150 people): the founding team's personal knowledge of every employee becomes unsustainable. First VP hires should happen before, not after, crossing 80.\n- **Series B → C transition** (80–150 → 150–300 people): the Dunbar ceiling is hit. Cross-functional processes must be formalized. Culture cannot be maintained by founder presence alone.\n- **Acquisition integration** (combining two 150-person units): combining creates a 300-person entity requiring formal hierarchy — even if both units functioned informally before. The integration failure common in M&A is often Dunbar failure: informal cultures that worked below 150 shatter above it.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nDunbar's Number helps agents diagnose when team-size growth is making informal coordination fail and propose structural responses such as splitting units, formalizing processes, or adding management layers.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, and operators use this skill to evaluate scaling teams, acquisition integrations, or new offices when headcount approaches Dunbar breakpoints such as 50, 150, or 500. It guides the agent to map the current group layer, audit coordination mechanisms, and recommend whether to split, formalize, or layer the organization.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Organizational prescriptions could influence real business structure if treated as authoritative without local validation.\n\nMitigation: Use the skill as advisory guidance and validate assumptions, evidence, and decisions with responsible organizational leaders before making changes.\n\nRisk: The framework could be overapplied to problems that are primarily interpersonal or caused by incentive misalignment rather than group size.\n\nMitigation: Check the skill's stated non-use cases before applying it, including groups well below 50 and situations better handled by an incentive or principal-agent analysis.\n\n## Reference(s):\n\n- [ClawHub skill listing](https://clawhub.ai/deciqai/skills/dunbars-number)\n- [Primary sources](artifact/references/sources.md)\n- [Dunbar 1992 and W.L. Gore example](artifact/examples/dunbar-1992-wl-gore-associates.md)\n- [Scaling an AI-native startup team example](artifact/examples/ai-native-startup-scaling-2023-2026.md)\n- [deciqAI Dunbar's Number page](https://www.deciqai.com/c/dunbars-number)\n- [deciqAI machine-readable skill metadata](https://www.deciqai.com/s/dunbars-number.json)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown or plain text organizational analysis with structured recommendations]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May ask stepwise questions before producing a diagnosis when the user is unfamiliar with the framework.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 6 files, 12333 bytes\n\nFiles: examples/ai-native-startup-scaling-2023-2026.md (6972b), examples/dunbar-1992-wl-gore-associates.md (4575b), references/sources.md (1956b), skill-card.md (2074b), SKILL.md (7935b), _meta.json (133b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with `network-effects` (different coordination mechanisms below vs. above 150), `principal-agent` (exceeding 150 multiplies agency problems informal trust can no longer cover), `founder-mindset` (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n- AI-native startup hiring fast on abundant AI-era capital / AI-adoption demand — \"we scaled from 20 to 150 in a year and coordination is breaking\"\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use `principal-agent`); challenge is growing a network beyond 150 (use `network-effects`).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify layer:** headcount → Dunbar layer (5/15/50/150/500/1,500) → distance to next breakpoint.\n\n**Step 2 — Audit coordination:** how does the group coordinate? (informal trust / formal process / hierarchy) — where are breakdowns?\n\n**Step 3 — Diagnose mismatch:** does coordination mechanism match group size? (below 50: direct knowledge ok; 50–150: structured trust ok; above 150: formal hierarchy required)\n\n**Step 4 — Prescribe structure:** A) Split — sub-units each below 150 with explicit interfaces; B) Formalize — replace relationship-based coordination with documented processes; C) Layer — add management tier.\n\n**Step 5 — Set thresholds:** current ceiling / trigger for next structural review / Gore parking-lot rule (headcount cap per unit).\n\n**Step 6 — Validate culture claims:** \"Lost startup feel\" — Dunbar exceeded or culture drift? \"Need better communication\" — is structure the actual solution?\n\n### Output template\n```\nDunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]\n```\n\n*→ Method in Action: [Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md)*\n*→ 2026 lens: [Scaling an AI-native startup team (2023–2026)](examples/ai-native-startup-scaling-2023-2026.md) — how AI capital compresses the timeline to the ~50 and ~150 breakpoints*\n\n## Pack: Dunbar Number Across Domains\n\n| Domain | Layer | Key implication |\n|---|---|---|\n| Founding team (1–15) | Sympathy group | No process needed; direct knowledge |\n| Seed-stage (15–50) | Affinity group | Informal still works; minimize overhead |\n| Series A (50–80) | Approaching ceiling | Begin formalizing roles + reporting |\n| Series B / Pre-150 (80–149) | Just below limit | Build management layer before hitting 150 |\n| 150-person threshold | Dunbar crossed | Mandatory: documented processes + explicit hierarchy |\n| 150–500 / 500+ | Acquaintance / multiple groups | VP layer + OKRs; federated units each below 150 |\n| Remote teams | ~50–70 (compressed) | Video/async reduces relationship maintenance efficiency |\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We just need better communication tools\" | Above 150, the problem is neocortical capacity. Slack does not fix Dunbar. |\n| [D] \"We can maintain flat culture as we grow\" | Flat culture works below 50. Above 150, informal coordination structurally fails. |\n| [D] \"We'll hire great people who don't need management\" | Quality of people doesn't change cognitive limits. |\n| [D] \"Communication problems are a people issue\" | At ~150, communication problems are architectural. HR interventions treat the symptom. |\n| [D] \"The founders just need to be more visible\" | Founder visibility works below 150. Above it, all-hands don't substitute for structure. |\n| [D] \"We lost our startup feel — must have been wrong hires\" | The startup feel was a Dunbar-layer property of a sub-50 group. Hires are not the issue. |\n| [D] \"More team-building will restore cohesion\" | Works within the 150-layer. Across groups above 150, it produces temporary warmth, no structural repair. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Headcount crossed 150 without any structural change or management layer addition\n- Founder still coordinating a 200-person company via personal relationships\n- \"Communication problems\" diagnosed as interpersonal without checking if Dunbar limit was crossed\n- Org chart flat beyond 50 with no explicit coordination mechanism\n- Acquisition integration plan assumes two informal cultures can merge without formal structure\n\n## Verification\n\n- [ ] Headcount mapped to Dunbar layer explicitly; distance to next breakpoint calculated\n- [ ] Coordination mechanisms audited against group size requirements\n- [ ] Root cause identified: architectural vs. interpersonal vs. incentive\n- [ ] Structural prescription chosen (split / formalize / layer); sub-unit targets set below 150\n- [ ] Growth trigger for next structural review defined\n- [ ] \"Culture problem\" vs. \"architecture problem\" distinction made explicitly\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 189 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/dunbars-number** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1783595827941\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. \"The Lattice Organization — A Philosophy of Enterprise.\" Internal document distributed to Gore associates (circa 1976). The Gore founding philosophy. (Not a formally published journal article; the widely cited secondary source for Gore's ~150 plant cap is Gladwell 2000, Ch. 5, above.)\n- Dunbar, R. I. M. (2021). \"Dunbar's number: why my theory that humans can only maintain 150 friendships has withstood 30 years of scrutiny.\" *The Conversation*, May 2021. Dunbar's own 30-year restatement — the limit is a cognitive/neocortical constraint, not one technology (social media, collaboration tools, or AI) can raise.\n- On the 2023–2026 AI funding-and-hiring environment: contemporaneous, widely reported venture-capital concentration in AI and rapid headcount growth at leading AI-native companies (e.g., ongoing press coverage of OpenAI and Anthropic scaling). Cited as a well-documented general pattern for the \"capital compresses the timeline to each Dunbar breakpoint\" claim — not as any single unverified figure.\n\nFile v1.0.4:examples/ai-native-startup-scaling-2023-2026.md\n\n# Method in Action: Scaling an AI-Native Startup Team (2023–2026)\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\nBetween 2023 and 2026, a distinctive class of company emerged: the **AI-native startup**. Powered by generative-AI product demand and an unusually deep venture-funding environment for AI, these companies raised large rounds early and hired far faster than the classic SaaS growth curve. The pattern that recurred — reported across founder essays, investor commentary, and press coverage of companies such as OpenAI, Anthropic, and a wave of well-funded application-layer startups — is that **capital compresses the timeline to each Dunbar breakpoint**. A team that historically took three or four years to reach 150 people can now cross that line in twelve to eighteen months. The neocortical limit does not move; the calendar does. So the ~50 and ~150 breakpoints, where informal trust fails and formal structure becomes mandatory, arrive sooner than the founders' intuition expects. This example walks the anchor case through the skill's six-step Process.\n\n---\n\n**Step 1 — Identify layer.** Take a representative AI-native startup that raised a large early round and grew from roughly 20 to roughly 160 people inside about a year and a half. At 20 the company sits in the **affinity-group layer (15–50)** — informal coordination still works. Its trajectory takes it through the **~50 breakpoint** (approaching the ceiling of what direct mutual knowledge supports) and toward the **~150 Dunbar limit** where formal hierarchy becomes architecturally mandatory. Distance-to-breakpoint is the critical number: growing at even five to ten hires a month, the ~50 line is a few months out and the ~150 line arrives within the funding cycle — not \"someday.\"\n\n**Step 2 — Audit coordination.** Early on, coordination is pure informal trust: the founders know every engineer, decisions happen in a shared channel, and there is no documented process. The observable breakdowns as headcount climbs are the classic Dunbar symptoms — \"we don't know who owns what anymore,\" duplicated work between teams that didn't know the other existed, onboarding that no longer happens by osmosis, and founders becoming a decision bottleneck. In AI-native firms these show up faster because so many hires are senior and expensive, and because rapid model/product iteration multiplies the number of in-flight decisions.\n\n**Step 3 — Diagnose mismatch.** Below 50, direct knowledge is adequate; the AI startup's early informal style *matched* its size. Crossing 50 into the 50–150 band, the mechanism must shift to **structured trust** — explicit roles, reporting lines, and lightweight process. Approaching 150, the mismatch becomes acute: informal trust is being asked to coordinate a group that has exceeded the neocortex's capacity to track every relationship. The root cause is **architectural, not interpersonal** — the very trap the skill's Red Flags warn about (\"communication problems diagnosed as interpersonal without checking if the Dunbar limit was crossed\").\n\n**Step 4 — Prescribe structure.** The right prescription combines two of the skill's three moves. **Formalize** first — replace relationship-based coordination with documented ownership, decision rights, and written process — because this should begin *before* 150, ideally around the 80-person mark per the skill's Pack (\"build a management layer before hitting 150\"). Then **Layer** — add a management tier so the founders stop being the single coordination hub. **Split** into sub-units each below 150 becomes the tool for the next phase of growth (federated teams with explicit interfaces), echoing the W.L. Gore plant-cap logic in the companion example.\n\n**Step 5 — Set thresholds.** Set an explicit current ceiling and triggers: begin formalizing roles and reporting at ~50; complete a management layer before 80–100; treat 150 as a hard structural-review line where documented processes and explicit hierarchy are non-negotiable; and adopt a Gore-style per-unit cap (each functional pod or \"house\" kept below ~150) for growth beyond that. Because capital lets AI-native firms hire fast, these triggers should be defined *at planning time*, not discovered after the coordination breakdown.\n\n**Step 6 — Validate culture claims.** When such a company says \"we lost the startup feel,\" the skill forces the diagnostic question: is this Dunbar exceeded, or culture drift? For a company that went from 20 to 160 in eighteen months, the honest answer is almost always that a sub-50-group property (everyone knowing everyone) was structurally lost by crossing 150 — not that the wrong people were hired. And \"we just need better communication tools\" is precisely the rationalization the skill flags: Slack does not fix Dunbar. The AI-native twist is that these teams are unusually tempted to believe their own AI tooling will substitute for structure — but internal copilots and better dashboards do not raise the neocortical ceiling.\n\n---\n\n**Output template applied**\n\n```\nDunbar Org Analysis: AI-native startup, ~20 → ~160 in ~18 months\nCurrent layer: crossing 150 (Dunbar limit) | Distance to next breakpoint: hit ~150 inside the funding cycle\nCoordination mechanism: informal trust (unchanged from 20-person era) | Breakdown points: unclear ownership, duplicated work, founder bottleneck, onboarding-by-osmosis fails\nRoot cause: architectural (capital compressed the timeline; neocortical limit did not move)\nPrescription: formalize (from ~50) + layer (before ~80–100) → split into sub-units later | Sub-unit targets: ≤150 | Trigger: hard structural review at 150; per-pod cap thereafter\n```\n\n**The generalizable lesson:** abundant AI-era capital and AI-native competition change *how fast* you reach the Dunbar breakpoints, not *where* the breakpoints are. Founders who assume the informal phase lasts as long as it did for a bootstrapped or slowly-funded company are systematically surprised. The fix is to pre-commit to the ~50 and ~150 structural triggers on the way up, while the team is still small enough to install them cheaply.\n\n*Sources: Dunbar, R. I. M. (1992), \"Neocortex size as a constraint on group size in primates,\" Journal of Human Evolution 22(6), 469–493 (the ~150 figure and breakpoint layers). Gladwell, M. (2000), The Tipping Point, Ch. 5 (W.L. Gore ~150 plant cap). Robin Dunbar, \"Dunbar's number: why my theory that humans can only maintain 150 friendships has withstood 30 years of scrutiny,\" The Conversation (2021) — Dunbar's own restatement that the limit is cognitive, not technological. On the 2023–2026 AI funding and hiring environment: widely reported venture-funding concentration in AI and rapid headcount growth at leading AI-native companies (e.g., contemporaneous reporting on OpenAI and Anthropic scaling), treated here as a well-documented general pattern rather than any specific unverified figure.*\n\nFile v1.0.4:examples/dunbar-1992-wl-gore-associates.md\n\n# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering choice with measurable operational consequences. Plants above 150 showed formal management emergence, political behavior, and productivity loss. Plants below 150 maintained voluntary coordination, peer accountability, and Gore's characteristic innovation culture.\n\nThe mechanism: in a group of 150, every person can maintain a mental model of every other person's trustworthiness, competence, and relationships. Free-rider problems are visible and self-correcting. Reputation mechanisms work because everyone knows everyone. Above 150, this breaks down: you cannot know and track 200 people's relationships — so you must rely on formal rules, titles, and documented processes to substitute for the relationship knowledge you no longer have.\n\nThis has direct implications for acquisition integration, org design at Series B/C, and community building:\n\n- **Series A → B transition** (30–60 → 80–150 people): the founding team's personal knowledge of every employee becomes unsustainable. First VP hires should happen before, not after, crossing 80.\n- **Series B → C transition** (80–150 → 150–300 people): the Dunbar ceiling is hit. Cross-functional processes must be formalized. Culture cannot be maintained by founder presence alone.\n- **Acquisition integration** (combining two 150-person units): combining creates a 300-person entity requiring formal hierarchy — even if both units functioned informally before. The integration failure common in M&A is often Dunbar failure: informal cultures that worked below 150 shatter above it.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nHelps agents diagnose organizational coordination problems around Dunbar breakpoints and recommend whether to split teams, formalize process, or add management layers. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external operators, and advisors use this skill to analyze team-size breakpoints during startup scaling, org design, office expansion, acquisition integration, or management-layer decisions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Server security evidence marks the release suspicious because the submitted artifact appears broader than a clearly scoped installable skill. <br>\nMitigation: Install only after human review, limit installation to the intended skill directory, use scoped credentials, and require confirmation gates for administrative, deployment, migration, or organizational-memory actions. <br>\n\n\n## Reference(s): <br>\n- [Sources - dunbars-number](references/sources.md) <br>\n- [Method in Action: Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md) <br>\n- [Method in Action: Scaling an AI-Native Startup Team (2023-2026)](examples/ai-native-startup-scaling-2023-2026.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Markdown, Guidance] <br>\n**Output Format:** [Markdown] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a structured Dunbar org analysis with current layer, coordination mechanism, root cause, prescription, sub-unit targets, and review trigger.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 5 files, 8057 bytes\n\nFiles: examples/dunbar-1992-wl-gore-associates.md (4575b), references/sources.md (1063b), skill-card.md (1923b), SKILL.md (7594b), _meta.json (133b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with `network-effects` (different coordination mechanisms below vs. above 150), `principal-agent` (exceeding 150 multiplies agency problems informal trust can no longer cover), `founder-mindset` (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use `principal-agent`); challenge is growing a network beyond 150 (use `network-effects`).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify layer:** headcount → Dunbar layer (5/15/50/150/500/1,500) → distance to next breakpoint.\n\n**Step 2 — Audit coordination:** how does the group coordinate? (informal trust / formal process / hierarchy) — where are breakdowns?\n\n**Step 3 — Diagnose mismatch:** does coordination mechanism match group size? (below 50: direct knowledge ok; 50–150: structured trust ok; above 150: formal hierarchy required)\n\n**Step 4 — Prescribe structure:** A) Split — sub-units each below 150 with explicit interfaces; B) Formalize — replace relationship-based coordination with documented processes; C) Layer — add management tier.\n\n**Step 5 — Set thresholds:** current ceiling / trigger for next structural review / Gore parking-lot rule (headcount cap per unit).\n\n**Step 6 — Validate culture claims:** \"Lost startup feel\" — Dunbar exceeded or culture drift? \"Need better communication\" — is structure the actual solution?\n\n### Output template\n```\nDunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]\n```\n\n*→ Method in Action: [Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md)*\n\n## Pack: Dunbar Number Across Domains\n\n| Domain | Layer | Key implication |\n|---|---|---|\n| Founding team (1–15) | Sympathy group | No process needed; direct knowledge |\n| Seed-stage (15–50) | Affinity group | Informal still works; minimize overhead |\n| Series A (50–80) | Approaching ceiling | Begin formalizing roles + reporting |\n| Series B / Pre-150 (80–149) | Just below limit | Build management layer before hitting 150 |\n| 150-person threshold | Dunbar crossed | Mandatory: documented processes + explicit hierarchy |\n| 150–500 / 500+ | Acquaintance / multiple groups | VP layer + OKRs; federated units each below 150 |\n| Remote teams | ~50–70 (compressed) | Video/async reduces relationship maintenance efficiency |\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We just need better communication tools\" | Above 150, the problem is neocortical capacity. Slack does not fix Dunbar. |\n| [D] \"We can maintain flat culture as we grow\" | Flat culture works below 50. Above 150, informal coordination structurally fails. |\n| [D] \"We'll hire great people who don't need management\" | Quality of people doesn't change cognitive limits. |\n| [D] \"Communication problems are a people issue\" | At ~150, communication problems are architectural. HR interventions treat the symptom. |\n| [D] \"The founders just need to be more visible\" | Founder visibility works below 150. Above it, all-hands don't substitute for structure. |\n| [D] \"We lost our startup feel — must have been wrong hires\" | The startup feel was a Dunbar-layer property of a sub-50 group. Hires are not the issue. |\n| [D] \"More team-building will restore cohesion\" | Works within the 150-layer. Across groups above 150, it produces temporary warmth, no structural repair. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Headcount crossed 150 without any structural change or management layer addition\n- Founder still coordinating a 200-person company via personal relationships\n- \"Communication problems\" diagnosed as interpersonal without checking if Dunbar limit was crossed\n- Org chart flat beyond 50 with no explicit coordination mechanism\n- Acquisition integration plan assumes two informal cultures can merge without formal structure\n\n## Verification\n\n- [ ] Headcount mapped to Dunbar layer explicitly; distance to next breakpoint calculated\n- [ ] Coordination mechanisms audited against group size requirements\n- [ ] Root cause identified: architectural vs. interpersonal vs. incentive\n- [ ] Structural prescription chosen (split / formalize / layer); sub-unit targets set below 150\n- [ ] Growth trigger for next structural review defined\n- [ ] \"Culture problem\" vs. \"architecture problem\" distinction made explicitly\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/dunbars-number** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783508444065\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. (1985). \"The lattice organization: A philosophy of enterprise.\" *Networking Journal*, Spring/Summer. The Gore founding philosophy.\n\nFile v1.0.3:examples/dunbar-1992-wl-gore-associates.md\n\n# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering choice with measurable operational consequences. Plants above 150 showed formal management emergence, political behavior, and productivity loss. Plants below 150 maintained voluntary coordination, peer accountability, and Gore's characteristic innovation culture.\n\nThe mechanism: in a group of 150, every person can maintain a mental model of every other person's trustworthiness, competence, and relationships. Free-rider problems are visible and self-correcting. Reputation mechanisms work because everyone knows everyone. Above 150, this breaks down: you cannot know and track 200 people's relationships — so you must rely on formal rules, titles, and documented processes to substitute for the relationship knowledge you no longer have.\n\nThis has direct implications for acquisition integration, org design at Series B/C, and community building:\n\n- **Series A → B transition** (30–60 → 80–150 people): the founding team's personal knowledge of every employee becomes unsustainable. First VP hires should happen before, not after, crossing 80.\n- **Series B → C transition** (80–150 → 150–300 people): the Dunbar ceiling is hit. Cross-functional processes must be formalized. Culture cannot be maintained by founder presence alone.\n- **Acquisition integration** (combining two 150-person units): combining creates a 300-person entity requiring formal hierarchy — even if both units functioned informally before. The integration failure common in M&A is often Dunbar failure: informal cultures that worked below 150 shatter above it.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nDunbar's Number helps agents analyze organizational headcount against Dunbar layers to diagnose coordination breakdowns and recommend structural changes such as splitting, formalizing, or adding management layers. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nFounders, operators, managers, and strategy agents use this skill to evaluate whether group size is causing coordination problems and to choose structural responses before or after key headcount thresholds. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may produce strong organizational recommendations about structure or hierarchy that are not a substitute for management judgment. <br>\nMitigation: Review recommendations against current headcount, team context, incentives, and leadership constraints before acting on them. <br>\n\n\n## Reference(s): <br>\n- [Sources - dunbars-number](references/sources.md) <br>\n- [Method in Action: Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown with a structured organizational analysis template] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces layer, breakpoint, coordination, root-cause, prescription, sub-unit target, and trigger fields for review.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 5 files, 8138 bytes\n\nFiles: examples/dunbar-1992-wl-gore-associates.md (4575b), references/sources.md (1063b), skill-card.md (2042b), SKILL.md (7698b), _meta.json (133b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with `network-effects` (different coordination mechanisms below vs. above 150), `principal-agent` (exceeding 150 multiplies agency problems informal trust can no longer cover), `founder-mindset` (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use `principal-agent`); challenge is growing a network beyond 150 (use `network-effects`).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify layer:** headcount → Dunbar layer (5/15/50/150/500/1,500) → distance to next breakpoint.\n\n**Step 2 — Audit coordination:** how does the group coordinate? (informal trust / formal process / hierarchy) — where are breakdowns?\n\n**Step 3 — Diagnose mismatch:** does coordination mechanism match group size? (below 50: direct knowledge ok; 50–150: structured trust ok; above 150: formal hierarchy required)\n\n**Step 4 — Prescribe structure:** A) Split — sub-units each below 150 with explicit interfaces; B) Formalize — replace relationship-based coordination with documented processes; C) Layer — add management tier.\n\n**Step 5 — Set thresholds:** current ceiling / trigger for next structural review / Gore parking-lot rule (headcount cap per unit).\n\n**Step 6 — Validate culture claims:** \"Lost startup feel\" — Dunbar exceeded or culture drift? \"Need better communication\" — is structure the actual solution?\n\n### Output template\n```\nDunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]\n```\n\n*→ Method in Action: [Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md)*\n\n## Pack: Dunbar Number Across Domains\n\n| Domain | Layer | Key implication |\n|---|---|---|\n| Founding team (1–15) | Sympathy group | No process needed; direct knowledge |\n| Seed-stage (15–50) | Affinity group | Informal still works; minimize overhead |\n| Series A (50–80) | Approaching ceiling | Begin formalizing roles + reporting |\n| Series B / Pre-150 (80–149) | Just below limit | Build management layer before hitting 150 |\n| 150-person threshold | Dunbar crossed | Mandatory: documented processes + explicit hierarchy |\n| 150–500 / 500+ | Acquaintance / multiple groups | VP layer + OKRs; federated units each below 150 |\n| Remote teams | ~50–70 (compressed) | Video/async reduces relationship maintenance efficiency |\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We just need better communication tools\" | Above 150, the problem is neocortical capacity. Slack does not fix Dunbar. |\n| [D] \"We can maintain flat culture as we grow\" | Flat culture works below 50. Above 150, informal coordination structurally fails. |\n| [D] \"We'll hire great people who don't need management\" | Quality of people doesn't change cognitive limits. |\n| [D] \"Communication problems are a people issue\" | At ~150, communication problems are architectural. HR interventions treat the symptom. |\n| [D] \"The founders just need to be more visible\" | Founder visibility works below 150. Above it, all-hands don't substitute for structure. |\n| [D] \"We lost our startup feel — must have been wrong hires\" | The startup feel was a Dunbar-layer property of a sub-50 group. Hires are not the issue. |\n| [D] \"More team-building will restore cohesion\" | Works within the 150-layer. Across groups above 150, it produces temporary warmth, no structural repair. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Headcount crossed 150 without any structural change or management layer addition\n- Founder still coordinating a 200-person company via personal relationships\n- \"Communication problems\" diagnosed as interpersonal without checking if Dunbar limit was crossed\n- Org chart flat beyond 50 with no explicit coordination mechanism\n- Acquisition integration plan assumes two informal cultures can merge without formal structure\n\n## Verification\n\n- [ ] Headcount mapped to Dunbar layer explicitly; distance to next breakpoint calculated\n- [ ] Coordination mechanisms audited against group size requirements\n- [ ] Root cause identified: architectural vs. interpersonal vs. incentive\n- [ ] Structural prescription chosen (split / formalize / layer); sub-unit targets set below 150\n- [ ] Growth trigger for next structural review defined\n- [ ] \"Culture problem\" vs. \"architecture problem\" distinction made explicitly\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/dunbars-number?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=dunbars-number** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783471546764\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. (1985). \"The lattice organization: A philosophy of enterprise.\" *Networking Journal*, Spring/Summer. The Gore founding philosophy.\n\nFile v1.0.2:examples/dunbar-1992-wl-gore-associates.md\n\n# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering choice with measurable operational consequences. Plants above 150 showed formal management emergence, political behavior, and productivity loss. Plants below 150 maintained voluntary coordination, peer accountability, and Gore's characteristic innovation culture.\n\nThe mechanism: in a group of 150, every person can maintain a mental model of every other person's trustworthiness, competence, and relationships. Free-rider problems are visible and self-correcting. Reputation mechanisms work because everyone knows everyone. Above 150, this breaks down: you cannot know and track 200 people's relationships — so you must rely on formal rules, titles, and documented processes to substitute for the relationship knowledge you no longer have.\n\nThis has direct implications for acquisition integration, org design at Series B/C, and community building:\n\n- **Series A → B transition** (30–60 → 80–150 people): the founding team's personal knowledge of every employee becomes unsustainable. First VP hires should happen before, not after, crossing 80.\n- **Series B → C transition** (80–150 → 150–300 people): the Dunbar ceiling is hit. Cross-functional processes must be formalized. Culture cannot be maintained by founder presence alone.\n- **Acquisition integration** (combining two 150-person units): combining creates a 300-person entity requiring formal hierarchy — even if both units functioned informally before. The integration failure common in M&A is often Dunbar failure: informal cultures that worked below 150 shatter above it.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nDunbar's Number helps agents diagnose group-size coordination breakpoints and recommend organizational structure changes such as splitting units, formalizing processes, or adding management layers. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users, founders, operators, and organizational designers use this skill to analyze team headcount against Dunbar layers, identify coordination breakdowns, and choose structural prescriptions for scaling teams, acquisitions, or new offices. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Organizational coaching recommendations could be misapplied to staffing, restructuring, or management decisions. <br>\nMitigation: Review the skill's recommendations with appropriate business judgment before applying them to real organizational changes. <br>\n\n\n## Reference(s): <br>\n- [Primary sources for dunbars-number](references/sources.md) <br>\n- [Method in Action: Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md) <br>\n- [Dunbar's Number on ClawHub](https://clawhub.ai/deciqai/skills/dunbars-number) <br>\n- [deciqAI Knowledge Skills repository](https://github.com/deciqAI/knowledge-skills) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown] <br>\n**Output Format:** [Markdown organizational analysis with structured recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause for user input during coach-mode workflows.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 5 files, 8149 bytes\n\nFiles: examples/dunbar-1992-wl-gore-associates.md (4575b), references/sources.md (1063b), skill-card.md (2242b), SKILL.md (7597b), _meta.json (133b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with [`network-effects`](../network-effects/SKILL.md) (different coordination mechanisms below vs. above 150), [`principal-agent`](../principal-agent/SKILL.md) (exceeding 150 multiplies agency problems informal trust can no longer cover), [`founder-mindset`](../founder-mindset/SKILL.md) (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use [`principal-agent`](../principal-agent/SKILL.md)); challenge is growing a network beyond 150 (use [`network-effects`](../network-effects/SKILL.md)).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify layer:** headcount → Dunbar layer (5/15/50/150/500/1,500) → distance to next breakpoint.\n\n**Step 2 — Audit coordination:** how does the group coordinate? (informal trust / formal process / hierarchy) — where are breakdowns?\n\n**Step 3 — Diagnose mismatch:** does coordination mechanism match group size? (below 50: direct knowledge ok; 50–150: structured trust ok; above 150: formal hierarchy required)\n\n**Step 4 — Prescribe structure:** A) Split — sub-units each below 150 with explicit interfaces; B) Formalize — replace relationship-based coordination with documented processes; C) Layer — add management tier.\n\n**Step 5 — Set thresholds:** current ceiling / trigger for next structural review / Gore parking-lot rule (headcount cap per unit).\n\n**Step 6 — Validate culture claims:** \"Lost startup feel\" — Dunbar exceeded or culture drift? \"Need better communication\" — is structure the actual solution?\n\n### Output template\n```\nDunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]\n```\n\n*→ Method in Action: [Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md)*\n\n## Pack: Dunbar Number Across Domains\n\n| Domain | Layer | Key implication |\n|---|---|---|\n| Founding team (1–15) | Sympathy group | No process needed; direct knowledge |\n| Seed-stage (15–50) | Affinity group | Informal still works; minimize overhead |\n| Series A (50–80) | Approaching ceiling | Begin formalizing roles + reporting |\n| Series B / Pre-150 (80–149) | Just below limit | Build management layer before hitting 150 |\n| 150-person threshold | Dunbar crossed | Mandatory: documented processes + explicit hierarchy |\n| 150–500 / 500+ | Acquaintance / multiple groups | VP layer + OKRs; federated units each below 150 |\n| Remote teams | ~50–70 (compressed) | Video/async reduces relationship maintenance efficiency |\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We just need better communication tools\" | Above 150, the problem is neocortical capacity. Slack does not fix Dunbar. |\n| [D] \"We can maintain flat culture as we grow\" | Flat culture works below 50. Above 150, informal coordination structurally fails. |\n| [D] \"We'll hire great people who don't need management\" | Quality of people doesn't change cognitive limits. |\n| [D] \"Communication problems are a people issue\" | At ~150, communication problems are architectural. HR interventions treat the symptom. |\n| [D] \"The founders just need to be more visible\" | Founder visibility works below 150. Above it, all-hands don't substitute for structure. |\n| [D] \"We lost our startup feel — must have been wrong hires\" | The startup feel was a Dunbar-layer property of a sub-50 group. Hires are not the issue. |\n| [D] \"More team-building will restore cohesion\" | Works within the 150-layer. Across groups above 150, it produces temporary warmth, no structural repair. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Headcount crossed 150 without any structural change or management layer addition\n- Founder still coordinating a 200-person company via personal relationships\n- \"Communication problems\" diagnosed as interpersonal without checking if Dunbar limit was crossed\n- Org chart flat beyond 50 with no explicit coordination mechanism\n- Acquisition integration plan assumes two informal cultures can merge without formal structure\n\n## Verification\n\n- [ ] Headcount mapped to Dunbar layer explicitly; distance to next breakpoint calculated\n- [ ] Coordination mechanisms audited against group size requirements\n- [ ] Root cause identified: architectural vs. interpersonal vs. incentive\n- [ ] Structural prescription chosen (split / formalize / layer); sub-unit targets set below 150\n- [ ] Growth trigger for next structural review defined\n- [ ] \"Culture problem\" vs. \"architecture problem\" distinction made explicitly\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783456341655\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. (1985). \"The lattice organization: A philosophy of enterprise.\" *Networking Journal*, Spring/Summer. The Gore founding philosophy.\n\nFile v1.0.1:examples/dunbar-1992-wl-gore-associates.md\n\n# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering choice with measurable operational consequences. Plants above 150 showed formal management emergence, political behavior, and productivity loss. Plants below 150 maintained voluntary coordination, peer accountability, and Gore's characteristic innovation culture.\n\nThe mechanism: in a group of 150, every person can maintain a mental model of every other person's trustworthiness, competence, and relationships. Free-rider problems are visible and self-correcting. Reputation mechanisms work because everyone knows everyone. Above 150, this breaks down: you cannot know and track 200 people's relationships — so you must rely on formal rules, titles, and documented processes to substitute for the relationship knowledge you no longer have.\n\nThis has direct implications for acquisition integration, org design at Series B/C, and community building:\n\n- **Series A → B transition** (30–60 → 80–150 people): the founding team's personal knowledge of every employee becomes unsustainable. First VP hires should happen before, not after, crossing 80.\n- **Series B → C transition** (80–150 → 150–300 people): the Dunbar ceiling is hit. Cross-functional processes must be formalized. Culture cannot be maintained by founder presence alone.\n- **Acquisition integration** (combining two 150-person units): combining creates a 300-person entity requiring formal hierarchy — even if both units functioned informally before. The integration failure common in M&A is often Dunbar failure: informal cultures that worked below 150 shatter above it.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nGuides agents through using Dunbar's number to diagnose coordination limits and recommend organizational structures as teams approach 50, 150, or 500 people. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nFounders, operators, managers, and organizational advisors use this skill to assess whether team-size thresholds explain coordination breakdowns and to choose structural responses such as splitting units, formalizing process, or adding management layers. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may produce misleading organizational guidance if its advisory framework is treated as an automated decision system. <br>\nMitigation: Review recommendations with human organizational context before using them for staffing, reporting-line, or restructuring decisions. <br>\nRisk: Examples or prompts may expose confidential company details if users paste sensitive organizational information into shared materials. <br>\nMitigation: Avoid including confidential company details in shared examples unless the user intends to preserve them there. <br>\n\n\n## Reference(s): <br>\n- [Sources - dunbars-number](references/sources.md) <br>\n- [Dunbar 1992 + W.L. Gore & Associates example](examples/dunbar-1992-wl-gore-associates.md) <br>\n- [Dunbar's Number on ClawHub](https://clawhub.ai/deciqai/skills/dunbars-number) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Guidance, Markdown] <br>\n**Output Format:** [Markdown with structured diagnostic fields] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces advisory organizational analysis; no code execution, credentials, or autonomous actions are involved.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 5 files, 8064 bytes\n\nFiles: examples/dunbar-1992-wl-gore-associates.md (4575b), references/sources.md (1063b), skill-card.md (2121b), SKILL.md (7597b), _meta.json (133b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with [`network-effects`](../network-effects/SKILL.md) (different coordination mechanisms below vs. above 150), [`principal-agent`](../principal-agent/SKILL.md) (exceeding 150 multiplies agency problems informal trust can no longer cover), [`founder-mindset`](../founder-mindset/SKILL.md) (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use [`principal-agent`](../principal-agent/SKILL.md)); challenge is growing a network beyond 150 (use [`network-effects`](../network-effects/SKILL.md)).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify layer:** headcount → Dunbar layer (5/15/50/150/500/1,500) → distance to next breakpoint.\n\n**Step 2 — Audit coordination:** how does the group coordinate? (informal trust / formal process / hierarchy) — where are breakdowns?\n\n**Step 3 — Diagnose mismatch:** does coordination mechanism match group size? (below 50: direct knowledge ok; 50–150: structured trust ok; above 150: formal hierarchy required)\n\n**Step 4 — Prescribe structure:** A) Split — sub-units each below 150 with explicit interfaces; B) Formalize — replace relationship-based coordination with documented processes; C) Layer — add management tier.\n\n**Step 5 — Set thresholds:** current ceiling / trigger for next structural review / Gore parking-lot rule (headcount cap per unit).\n\n**Step 6 — Validate culture claims:** \"Lost startup feel\" — Dunbar exceeded or culture drift? \"Need better communication\" — is structure the actual solution?\n\n### Output template\n```\nDunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]\n```\n\n*→ Method in Action: [Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md)*\n\n## Pack: Dunbar Number Across Domains\n\n| Domain | Layer | Key implication |\n|---|---|---|\n| Founding team (1–15) | Sympathy group | No process needed; direct knowledge |\n| Seed-stage (15–50) | Affinity group | Informal still works; minimize overhead |\n| Series A (50–80) | Approaching ceiling | Begin formalizing roles + reporting |\n| Series B / Pre-150 (80–149) | Just below limit | Build management layer before hitting 150 |\n| 150-person threshold | Dunbar crossed | Mandatory: documented processes + explicit hierarchy |\n| 150–500 / 500+ | Acquaintance / multiple groups | VP layer + OKRs; federated units each below 150 |\n| Remote teams | ~50–70 (compressed) | Video/async reduces relationship maintenance efficiency |\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"We just need better communication tools\" | Above 150, the problem is neocortical capacity. Slack does not fix Dunbar. |\n| [D] \"We can maintain flat culture as we grow\" | Flat culture works below 50. Above 150, informal coordination structurally fails. |\n| [D] \"We'll hire great people who don't need management\" | Quality of people doesn't change cognitive limits. |\n| [D] \"Communication problems are a people issue\" | At ~150, communication problems are architectural. HR interventions treat the symptom. |\n| [D] \"The founders just need to be more visible\" | Founder visibility works below 150. Above it, all-hands don't substitute for structure. |\n| [D] \"We lost our startup feel — must have been wrong hires\" | The startup feel was a Dunbar-layer property of a sub-50 group. Hires are not the issue. |\n| [D] \"More team-building will restore cohesion\" | Works within the 150-layer. Across groups above 150, it produces temporary warmth, no structural repair. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Headcount crossed 150 without any structural change or management layer addition\n- Founder still coordinating a 200-person company via personal relationships\n- \"Communication problems\" diagnosed as interpersonal without checking if Dunbar limit was crossed\n- Org chart flat beyond 50 with no explicit coordination mechanism\n- Acquisition integration plan assumes two informal cultures can merge without formal structure\n\n## Verification\n\n- [ ] Headcount mapped to Dunbar layer explicitly; distance to next breakpoint calculated\n- [ ] Coordination mechanisms audited against group size requirements\n- [ ] Root cause identified: architectural vs. interpersonal vs. incentive\n- [ ] Structural prescription chosen (split / formalize / layer); sub-unit targets set below 150\n- [ ] Growth trigger for next structural review defined\n- [ ] \"Culture problem\" vs. \"architecture problem\" distinction made explicitly\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782551881711\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. (1985). \"The lattice organization: A philosophy of enterprise.\" *Networking Journal*, Spring/Summer. The Gore founding philosophy.\n\nFile v1.0.0:examples/dunbar-1992-wl-gore-associates.md\n\n# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering choice with measurable operational consequences. Plants above 150 showed formal management emergence, political behavior, and productivity loss. Plants below 150 maintained voluntary coordination, peer accountability, and Gore's characteristic innovation culture.\n\nThe mechanism: in a group of 150, every person can maintain a mental model of every other person's trustworthiness, competence, and relationships. Free-rider problems are visible and self-correcting. Reputation mechanisms work because everyone knows everyone. Above 150, this breaks down: you cannot know and track 200 people's relationships — so you must rely on formal rules, titles, and documented processes to substitute for the relationship knowledge you no longer have.\n\nThis has direct implications for acquisition integration, org design at Series B/C, and community building:\n\n- **Series A → B transition** (30–60 → 80–150 people): the founding team's personal knowledge of every employee becomes unsustainable. First VP hires should happen before, not after, crossing 80.\n- **Series B → C transition** (80–150 → 150–300 people): the Dunbar ceiling is hit. Cross-functional processes must be formalized. Culture cannot be maintained by founder presence alone.\n- **Acquisition integration** (combining two 150-person units): combining creates a 300-person entity requiring formal hierarchy — even if both units functioned informally before. The integration failure common in M&A is often Dunbar failure: informal cultures that worked below 150 shatter above it.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nDunbar's Number helps agents analyze organizational size breakpoints and recommend whether to split teams, formalize coordination, or add management structure. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users, founders, operators, and organizational designers use this skill to diagnose coordination breakdowns near Dunbar-size thresholds and choose whether to split teams, formalize process, or add management layers. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Organizational recommendations can influence significant structure and management decisions. <br>\nMitigation: Use the skill as an advisory thinking aid and review recommendations with human judgment and local business context. <br>\nRisk: The skill may over-attribute interpersonal or incentive problems to group-size limits when the activation criteria do not fit. <br>\nMitigation: Check headcount, coordination mechanisms, and root cause before applying structural prescriptions. <br>\n\n\n## Reference(s): <br>\n- [Dunbar's Number on ClawHub](https://clawhub.ai/deciqai/skills/dunbars-number) <br>\n- [Sources](references/sources.md) <br>\n- [Method in Action: Dunbar 1992 + W.L. Gore & Associates](examples/dunbar-1992-wl-gore-associates.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown organizational analysis with a structured output template] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause for user input in coach mode before producing the final analysis.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Dunbar's Number Owner: deciqai Summary: Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:58:23.932Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/dunbars-number.json) v1.0.4 | 2026-07-09T11:17:07.941Z | u","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Dunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]"},{"language":"text","snippet":"Dunbar Org Analysis: AI-native startup, ~20 → ~160 in ~18 months\nCurrent layer: crossing 150 (Dunbar limit) | Distance to next breakpoint: hit ~150 inside the funding cycle\nCoordination mechanism: informal trust (unchanged from 20-person era) | Breakdown points: unclear ownership, duplicated work, founder bottleneck, onboarding-by-osmosis fails\nRoot cause: architectural (capital compressed the timeline; neocortical limit did not move)\nPrescription: formalize (from ~50) + layer (before ~80–100) → split into sub-units later | Sub-unit targets: ≤150 | Trigger: hard structural review at 150; per-pod cap thereafter"},{"language":"text","snippet":"Dunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]"},{"language":"text","snippet":"Dunbar Org Analysis: AI-native startup, ~20 → ~160 in ~18 months\nCurrent layer: crossing 150 (Dunbar limit) | Distance to next breakpoint: hit ~150 inside the funding cycle\nCoordination mechanism: informal trust (unchanged from 20-person era) | Breakdown points: unclear ownership, duplicated work, founder bottleneck, onboarding-by-osmosis fails\nRoot cause: architectural (capital compressed the timeline; neocortical limit did not move)\nPrescription: formalize (from ~50) + layer (before ~80–100) → split into sub-units later | Sub-unit targets: ≤150 | Trigger: hard structural review at 150; per-pod cap thereafter"},{"language":"text","snippet":"Dunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]"},{"language":"text","snippet":"Dunbar Org Analysis: <name>\nCurrent layer: [X] | Distance to next breakpoint: [N]\nCoordination mechanism: [informal/formal] | Breakdown points: [list]\nRoot cause: [architectural / interpersonal / incentive]\nPrescription: [split / formalize / layer] | Sub-unit targets: [≤150] | Trigger: [headcount]"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: dunbars-number\ndescription: >\n  Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says\n  \"coordination is getting harder,\" \"we lost the startup feel,\" or \"we don't know who does what\n  anymore\"; deciding whether to split a team, open a new office, or add a management layer.\n  Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue\n  is incentive misalignment rather than group size (use principal-agent instead).\n  More: deciqai.com/c/dunbars-number\n---\n\n# Dunbar's Number\n\n## Overview\n\n**Dunbar's number** (~150) is the cognitive limit on stable social groups the human neocortex can sustain, with nested layers at ~5, ~15, ~50, then outer bands at ~500 and ~1,500. Derived by Robin Dunbar (1992) from primate neocortex ratios. Key implication: **below ~150, informal trust coordinates behavior; above ~150, formal hierarchy becomes architecturally mandatory** — not a cultural choice.\n\nComposes with `network-effects` (different coordination mechanisms below vs. above 150), `principal-agent` (exceeding 150 multiplies agency problems informal trust can no longer cover), `founder-mindset` (founder relationship bandwidth peaks at ~150 — first breakpoint demanding shift from doing to delegating structure).\n\n## When to Use\n\n- Headcount approaching or crossing 150 (or 50, or 500)\n- \"Coordination getting harder\" complaints with no obvious structural cause\n- Deciding to split a team, open a new office, or create a sub-unit\n- Designing org structure for a scaling startup; evaluating acquisition integration plans\n- Diagnosing why informal culture \"felt different\" after a headcount milestone\n- AI-native startup hiring fast on abundant AI-era capital / AI-adoption demand — \"we scaled from 20 to 150 in a year and coordination is breaking\"\n\n**Not when:** group well below 50 and problems are interpersonal; constraint is incentive misalignment (use `principal-agent`); challenge is growing a network beyond 150 (use `network-effects`).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete org design or headcount question → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: once a group exceeds ~150 people, informal trust cannot coordinate it — formal structure is architecturally required by the human neocortex.\n2. Check fit: what is the current headcount? Which Dunbar layer, which breakpoint is approaching?\n3. Elicit the structure: what coordination mechanisms exist? Where are they breaking down?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input.\n> **[WAIT — do not advance until user responds]**\n5. Close: group layer + breakpoint diagnosis + structural prescription (split / formalize / layer) named.\n> **[WAIT — do not advance until user respon"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"dunbars-number\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224703932\n}"},{"path":"references/sources.md","content":"# Sources — dunbars-number\n\n> *Primary sources for the [dunbars-number](../SKILL.md) skill.*\n\n- Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493. The original empirical paper.\n- Dunbar, R. I. M. (2010). *How Many Friends Does One Person Need?* Harvard University Press. ISBN 978-0674057166. Accessible treatment with organizational extensions.\n- Gladwell, M. (2000). *The Tipping Point.* Little, Brown. ISBN 978-0316346627. Chapter 5: Gore case + Dunbar number in organizational design.\n- Dunbar, R. I. M. (1998). \"The social brain hypothesis.\" *Evolutionary Anthropology*, 6(5), 178–190. The social brain hypothesis underpinning the neocortex constraint.\n- Hill, R. A., & Dunbar, R. I. M. (2003). \"Social network size in humans.\" *Human Nature*, 14(1), 53–72. Empirical validation of the 150 figure via social network analysis.\n- Gore, W. L. \"The Lattice Organization — A Philosophy of Enterprise.\" Internal document distributed to Gore associates (circa 1976). The Gore founding philosophy. (Not a formally published journal article; the widely cited secondary source for Gore's ~150 plant cap is Gladwell 2000, Ch. 5, above.)\n- Dunbar, R. I. M. (2021). \"Dunbar's number: why my theory that humans can only maintain 150 friendships has withstood 30 years of scrutiny.\" *The Conversation*, May 2021. Dunbar's own 30-year restatement — the limit is a cognitive/neocortical constraint, not one technology (social media, collaboration tools, or AI) can raise.\n- On the 2023–2026 AI funding-and-hiring environment: contemporaneous, widely reported venture-capital concentration in AI and rapid headcount growth at leading AI-native companies (e.g., ongoing press coverage of OpenAI and Anthropic scaling). Cited as a well-documented general pattern for the \"capital compresses the timeline to each Dunbar breakpoint\" claim — not as any single unverified figure."},{"path":"examples/ai-native-startup-scaling-2023-2026.md","content":"# Method in Action: Scaling an AI-Native Startup Team (2023–2026)\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\nBetween 2023 and 2026, a distinctive class of company emerged: the **AI-native startup**. Powered by generative-AI product demand and an unusually deep venture-funding environment for AI, these companies raised large rounds early and hired far faster than the classic SaaS growth curve. The pattern that recurred — reported across founder essays, investor commentary, and press coverage of companies such as OpenAI, Anthropic, and a wave of well-funded application-layer startups — is that **capital compresses the timeline to each Dunbar breakpoint**. A team that historically took three or four years to reach 150 people can now cross that line in twelve to eighteen months. The neocortical limit does not move; the calendar does. So the ~50 and ~150 breakpoints, where informal trust fails and formal structure becomes mandatory, arrive sooner than the founders' intuition expects. This example walks the anchor case through the skill's six-step Process.\n\n---\n\n**Step 1 — Identify layer.** Take a representative AI-native startup that raised a large early round and grew from roughly 20 to roughly 160 people inside about a year and a half. At 20 the company sits in the **affinity-group layer (15–50)** — informal coordination still works. Its trajectory takes it through the **~50 breakpoint** (approaching the ceiling of what direct mutual knowledge supports) and toward the **~150 Dunbar limit** where formal hierarchy becomes architecturally mandatory. Distance-to-breakpoint is the critical number: growing at even five to ten hires a month, the ~50 line is a few months out and the ~150 line arrives within the funding cycle — not \"someday.\"\n\n**Step 2 — Audit coordination.** Early on, coordination is pure informal trust: the founders know every engineer, decisions happen in a shared channel, and there is no documented process. The observable breakdowns as headcount climbs are the classic Dunbar symptoms — \"we don't know who owns what anymore,\" duplicated work between teams that didn't know the other existed, onboarding that no longer happens by osmosis, and founders becoming a decision bottleneck. In AI-native firms these show up faster because so many hires are senior and expensive, and because rapid model/product iteration multiplies the number of in-flight decisions.\n\n**Step 3 — Diagnose mismatch.** Below 50, direct knowledge is adequate; the AI startup's early informal style *matched* its size. Crossing 50 into the 50–150 band, the mechanism must shift to **structured trust** — explicit roles, reporting lines, and lightweight process. Approaching 150, the mismatch becomes acute: informal trust is being asked to coordinate a group that has exceeded the neocortex's capacity to track every relationship. The root cause is **architectural, not interpersonal** — the very trap the skill's Red Flags warn about (\"communication problems diagnosed "},{"path":"examples/dunbar-1992-wl-gore-associates.md","content":"# Method in Action: Dunbar 1992 + W.L. Gore & Associates\n\n> *Example for the [dunbars-number](../SKILL.md) skill.*\n\n**Robin Dunbar** (b. 1947) is a British anthropologist and evolutionary psychologist at the University of Oxford. His 1992 paper originated in a specific observation: across primates, species with larger neocortex ratios live in larger stable social groups. The neocortex, the \"thinking\" part of the brain responsible for social cognition, appears to be the binding constraint on social group size — because maintaining stable relationships requires tracking each person's identity, reliability, relationship history, and current status relative to every other group member. The cognitive load scales with group size, and at some point the neocortex hits capacity.\n\nDunbar analyzed 38 primate genera, measuring neocortex ratio and mean social group size. The regression line, extrapolated to human neocortex size, predicted a stable group size of 147.8 — consistently rounded to 150. Dunbar then cross-validated:\n\n> \"Predicted group size for humans on the basis of our neocortex volume is 147.8. ... The distributions of group sizes for hunter-gatherer societies, Neolithic farming villages, and modern communities all peak in the range 150–200 individuals.\"\n>\n> — Dunbar, R. I. M. (1992). \"Neocortex size as a constraint on group size in primates.\" *Journal of Human Evolution*, 22(6), 469–493, p. 488.\n\nThe cross-validation hit multiple independent data streams: 21 hunter-gatherer societies (median group size 148.4); Neolithic village sizes from archaeological remains; Roman military units (the *centuria*, nominally 80 men, sits in the 50-layer; the *cohors* of 480 sits between 500 and 150 layers, requiring formal centurion hierarchy); Hutterite agricultural communities (mandated split at 150 for centuries before Dunbar's paper).\n\n**W.L. Gore & Associates** is the most-cited modern organizational case. Bill Gore founded the company in 1958 after leaving DuPont, where he had observed that small, informal groups produced dramatically better innovation than large, hierarchically managed ones. He built Gore on a \"lattice structure\" — no formal hierarchy, no titles, no bosses, only \"sponsors\" and \"associates.\" The principle was that coordination through relationships was more efficient than coordination through hierarchy.\n\nGore discovered empirically — before Dunbar published — that the lattice structure broke down above approximately 150 people. The solution: every plant was capped at 150. When a plant grew to capacity, a new plant was opened, often literally next door. By the late 1990s, Gore had 11,000+ employees across dozens of plants, each under 150 — and still maintained its lattice structure with minimal hierarchy.\n\nGladwell's documentation of the Gore case (2000, *The Tipping Point*, Chapter 5) introduced Dunbar's number to a mass business audience. The Gore case demonstrates that the 150-person cap is not a theory — it is a structural engineering "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"... Skill: Dunbar's Number Owner: deciqai Summary: Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says \"coordination is getting harder,\" \"we lost the startup feel,\" or \"... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:58:23.932Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/dunbars-number.json) v1.0.4 | 2026-07-09T11:17:07.941Z | u","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2002,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T02:09:43.656Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T02:09:43.656Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:35:00.808Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}