{"id":"710433fe-1188-4a00-8a5c-1842436d4fef","entityType":"agent","slug":"clawhub-deciqai-red-queen-effect","name":"Red Queen Effect","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-red-queen-effect","canonicalPath":"/agent/clawhub-deciqai-red-queen-effect","generatedAt":"2026-10-11T10:51:08.359Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T08:37:43.109Z","emptyReason":null},"description":"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with... Skill: Red Queen Effect Owner: deciqai Summary: Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:13:00.187Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/red-queen-effect.json) v1.0.4 | 2026-07-09T11:21:11.974Z","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:red-queen-effect","sourceUrl":"https://clawhub.ai/deciqai/red-queen-effect","homepage":"https://clawhub.ai/deciqai/skills/red-queen-effect","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/red-queen-effect","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/red-queen-effect","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:37:43.109Z","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-11T08:37:43.109Z","emptyReason":null},"stars":null,"forks":null,"downloads":1110,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:37:43.052Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T08:37:43.109Z","lastCrawledAt":"2026-10-11T08:37:43.052Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T08:37:43.052Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T18:13:00.187Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/red-queen-effect.json)","fileCount":6,"zipByteSize":12807},{"version":"1.0.4","createdAt":"2026-07-09T11:21:11.974Z","changelog":"Refresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)","fileCount":6,"zipByteSize":12487},{"version":"1.0.3","createdAt":"2026-07-08T11:16:24.986Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":8576},{"version":"1.0.2","createdAt":"2026-07-08T01:01:07.792Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":8536},{"version":"1.0.1","createdAt":"2026-07-07T22:32:31.821Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8534},{"version":"1.0.0","createdAt":"2026-07-01T11:18:19.624Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8592}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:red-queen-effect","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-red-queen-effect/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/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-11T10:51:08.355Z"}},"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-red-queen-effect/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-red-queen-effect/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-11T08:37:43.109Z","emptyReason":null},"readme":"Skill: Red Queen Effect\n\nOwner: deciqai\n\nSummary: Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T18:13:00.187Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/red-queen-effect.json)\n\nv1.0.4 | 2026-07-09T11:21:11.974Z | user\n\nRefresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)\n\nv1.0.3 | 2026-07-08T11:16:24.986Z | 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-08T01:01:07.792Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T22:32:31.821Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-07-01T11:18:19.624Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 12807 bytes\n\nFiles: examples/frontier-ai-labs-training-race-2023-2026.md (6988b), examples/van-valen-1973-intel-vs-amd-1990-2010.md (3994b), references/sources.md (1953b), skill-card.md (2550b), SKILL.md (9011b), _meta.json (135b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet. More: deciqai.com/c/red-queen-effect\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with `porters-five-forces` (diagnoses structure; Red Queen explains why strong competitors still don't earn), `second-curve` (escaping the Red Queen is the primary case for a second curve), `network-effects` (temporary escape until the next technology generation resets the field), and `antifragile` (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n- Escalating AI capex / compute arms race, or AI-native competition where everyone must adopt AI just to keep pace and no durable lead emerges\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: is copying speed accelerating? Is required investment growing? Is there any differentiation vector competitors are structurally unable to copy?\n> **[WAIT — do not advance until user responds]**\n5. Close: Red Queen confirmed or denied + escape vector identified + recommendation: run faster / change games / exit.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Diagnose:** primary competitive investment; imitation speed (months); margin trend 5–10 years; are all major competitors investing at roughly the same rate?\n\n**Step 2 — Confirm Red Queen:** absolute performance improving for all (Y/N); relative share stable (Y/N); investment to maintain position growing (Y/N); margins thin despite high activity (Y/N). 3+ Y = Red Queen confirmed.\n\n**Step 3 — Map imitation speed:** half-life of a competitive advantage; is imitation speed accelerating or decelerating?\n\n**Step 4 — Identify escape vector:** Differentiation (competing on an axis rivals ignore) / Vertical integration (control a supply layer rivals rely on externally) / Technology generation gap (new architecture that obsoletes the current race) / Geographic avoidance (less mature markets) / Platformization (become the environment competitors run in).\n\n**Step 5 — Calculate running cost vs. escape cost:** annual cost to maintain position; probability of winning from inside the race; cost and expected value of escape vector; race vs. escape comparison.\n\n**Step 6 — Decide:** Run faster (only if genuine near-term winning condition) / Change tracks (escape vector identified) / Exit (unwinnable; capital better deployed elsewhere). Set timing: how long can current position be maintained while preparing escape?\n\n## Output Template\n```\nRed Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:\n```\n\n*→ Method in Action: [Van Valen 1973 + Intel vs. AMD 1990–2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md)*\n\n*→ 2026 lens: [The Frontier-AI Training Race (2023–2026)](examples/frontier-ai-labs-training-race-2023-2026.md)*\n\n## Pack: Red Queen Across Industries\n\n| Industry | Primary arms race | Imitation speed | Escape example |\n|---|---|---|---|\n| Airlines | Frequent-flyer, yield management | 12–24 mo | Southwest (different segment) |\n| Retail | Supply chain, loyalty | 18–36 mo | Amazon (platform + logistics) |\n| Smartphones | Features, camera, processor | 12–18 mo | Apple (ecosystem lock-in) |\n| Semiconductors (x86) | Process node, microarchitecture | 18–24 mo | ARM (technology generation gap) |\n| Online advertising | Bidding, targeting | 3–6 mo | Google/Meta (first-party data) |\n\n## Applying It Well\n\n- Diagnostic question: not \"are we improving?\" but \"are we improving *faster* than all competitors simultaneously?\"\n- Recognize the Red Queen early — allocate capital toward escape vectors before the sunk-cost trap takes hold.\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 need to match their feature\" | Entering the Red Queen — table stakes in 12 months, no durable advantage. |\n| [D] \"Once we win this round, we'll have a clear lead\" | Winning a round means surviving to the next round at higher investment levels. No stable lead. |\n| [D] \"We're innovating faster than they can copy\" | Temporary windows, not moats. Is your lead measured in quarters or years? |\n| [D] \"Our market share is stable, so we're doing well\" | Stable share = running hard enough to maintain position. Check margins. |\n| [D] \"We just need more investment to break through\" | More investment → more improvement → immediately replicated. Escalation is the Red Queen's self-reinforcing mechanism. |\n| [D] \"The winner of this arms race will take all\" | Most Red Queen races have no winner — only survivors at higher cost. Winner-take-all requires structural network effects most industries lack. |\n| [D] \"We should focus on execution, not strategy\" | Excellent execution in a Red Queen race produces excellent running. If the track leads nowhere, execution delays the strategic question. |\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- Investment in competitive capabilities growing 3+ years without margin improvement\n- Every advantage can be named along with the month competitors copied it\n- Team is debating \"whether to match\" rather than \"whether to change the game\"\n- \"Staying competitive\" has replaced \"building advantage\" as the primary strategic frame\n- The company's strongest argument for continued investment is \"we can't afford not to\"\n\n## Verification\n\n- [ ] Imitation speed estimated explicitly (months); margin trend 5+ years examined\n- [ ] Red Queen presence confirmed or denied against three structural criteria\n- [ ] At least one escape vector evaluated for feasibility and cost\n- [ ] Cost of race vs. escape vector compared; \"run faster\" vs. \"change game\" distinguished\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/red-queen-effect** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/red-queen-effect.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"red-queen-effect\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784225580187\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitiveness Evolves.* Princeton University Press. ISBN 978-0691131146. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n- Epoch AI (2023–2025). *Machine Learning Trends / Notable AI Models* database and analyses (epoch.ai). Documents the escalation of frontier training compute, dataset size, and cost across successive model generations — the empirical backbone for the 2023–2026 frontier-AI Red Queen example.\n- Hyperscaler and AI-lab public disclosures, 2024–2026 (earnings calls, capital-expenditure guidance, and widely reported financial commentary from the major cloud providers and leading AI labs). Basis for the qualified statements about escalating AI capex and loss-making frontier training; specific figures qualified or omitted where exact public values were not verified against primary filings.\n\nFile v1.0.5:examples/frontier-ai-labs-training-race-2023-2026.md\n\n# Method in Action: The Frontier-AI Training Race (2023–2026)\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\nBetween 2023 and 2026 the leading frontier AI labs — OpenAI, Anthropic, Google DeepMind, Meta, xAI, and others — entered a textbook Red Queen race. Each must keep training ever-larger and better models, and keep buying more compute, simply to hold relative position while every rival does the same. The absolute capability of the frontier rises fast; the relative ordering among the top labs churns but never settles; and the cost of merely staying in the pack escalates every cycle. This walks the case through the skill's own six-step Process.\n\n## Step 1 — Diagnose\n\n- **Primary competitive investment:** training compute (GPUs/accelerators), the capital and data-center capacity to run them, and the scarce research/engineering talent to use them. Frontier training runs and the infrastructure behind them are the arms.\n- **Imitation speed:** roughly one model generation — on the order of months. When one lab ships a materially stronger model, rivals close much of the gap with a comparable release within a similar window, and capability benchmarks that one lab tops are frequently overtaken shortly after.\n- **Margin trend:** frontier model development has been heavily loss-making for the leading labs through this period. Revenue has grown quickly, but training and inference costs — and the capex commitments behind them — have grown at least as fast, so the leading pure-play frontier labs were reported to be spending well in excess of revenue.\n- **Are all major competitors investing at roughly the same rate?** Yes. Multiple large players are all committing very large sums to compute and data centers in the same window, and the biggest cloud/hyperscaler backers publicly raised their AI-related capital-expenditure guidance repeatedly across 2024–2025.\n\n## Step 2 — Confirm Red Queen\n\n- Absolute performance improving for all (Y): frontier model capability rose steeply and continuously across the field.\n- Relative share/position stable-but-contested (Y): no lab established a durable, uncontested lead; the \"best model\" title changed hands repeatedly and quickly.\n- Investment to maintain position growing (Y): the compute and capital required just to stay at the frontier increased each generation.\n- Margins thin/negative despite high activity (Y): frontier training remained deeply unprofitable for the leading pure-play labs despite rapid revenue growth.\n\nFour of four → **Red Queen confirmed.** All the running keeps each lab in roughly the same relative place while the treadmill speeds up.\n\n## Step 3 — Map imitation speed\n\nThe half-life of a frontier-capability advantage is short — measured in months, not years. A benchmark lead is routinely matched or exceeded by the next competitor release. And imitation speed is **accelerating** in some respects: the diffusion of methods (RLHF/RLAIF, mixture-of-experts, reasoning/inference-time compute, distillation) plus the emergence of strong open-weight models means that a given capability level becomes broadly reproducible faster than before. Distillation and open-weight releases in particular compress the time for a frontier result to become widely available.\n\n## Step 4 — Identify escape vector\n\n- **Differentiation:** compete on an axis rivals under-serve — enterprise trust/safety, reliability, vertical depth, developer experience, or agentic/product surface — rather than only on raw benchmark score.\n- **Vertical integration:** control a compute layer rivals rent externally — custom silicon and secured, long-term data-center/energy capacity — to blunt the cost treadmill.\n- **Technology generation gap:** a new architecture or training paradigm (e.g., shifting the axis of competition from pretraining scale toward inference-time reasoning, or efficiency breakthroughs) that partly obsoletes the current pure-scale race.\n- **Geographic / regulatory avoidance:** markets or deployment contexts where incumbents are structurally constrained.\n- **Platformization:** become the environment competitors and downstream builders run inside — the default API/model layer, distribution, and ecosystem lock-in — so that switching costs and data flywheels retain value the raw model cannot.\n\n## Step 5 — Calculate running cost vs. escape cost\n\n- **Annual cost to maintain position:** very high and rising — the multi-billion-dollar compute and data-center commitments are the price of a seat at the frontier, not a winning move.\n- **Probability of winning from inside the race:** low for \"permanent lead.\" With months-long imitation half-lives and no strong structural moat on model quality alone, staying in the scale race mostly buys survival to the next, more expensive round.\n- **Cost / expected value of escape:** platformization and vertical integration (custom silicon + secured energy/compute + ecosystem lock-in) are expensive and slow but produce durability that a raw benchmark lead does not. Distribution and switching costs — not model weights — are where captured value persists.\n\n## Step 6 — Decide\n\n- **Run faster** only where there is a genuine near-term winning condition (a real generation lead you can convert into distribution before it is copied). Pure benchmark-matching is table stakes.\n- **Change tracks** is the durable answer: convert transient capability leads into platform, distribution, ecosystem, and integrated-compute advantages that survive the next model release — because the model advantage itself will not.\n- **Exit / narrow** is rational for players without the capital or a differentiated axis: specialize, build on open weights, or serve a defensible vertical rather than fund an unwinnable scale race.\n- **Timing:** treat each capability lead as a months-long window, and allocate toward escape vectors *before* the sunk-cost logic of \"we can't afford not to keep spending\" becomes the company's primary organizing principle.\n\n**Operational lesson for founders and operators:** in the frontier-AI race the running is real and the absolute progress is genuine — but relative position among the leaders is not durably purchased by compute alone. The value of the arms race accrues heavily to users (rapidly cheaper, more capable models) and to the compute suppliers; the escape is to own a layer the race cannot immediately replicate.\n\n*Sources: Van Valen, L. (1973), \"A New Evolutionary Law,\" Evolutionary Theory 1:1–30; Carroll, L. (1871), Through the Looking-Glass, Ch. 2; Barnett, W. P. (2008), The Red Queen Among Organizations, Princeton University Press. Contemporary context on frontier-lab compute and capex escalation drawn from widely reported 2024–2026 public disclosures and reporting by major hyperscalers and AI labs (e.g., published capital-expenditure guidance and earnings commentary). Specific figures are omitted or qualified where exact public values were not verified.*\n\nFile v1.0.5:examples/van-valen-1973-intel-vs-amd-1990-2010.md\n\n# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where switching costs (data center architecture lock-in) provided temporary protection. But the deeper Red Queen escape came from ARM architecture — not a company in the x86 race, but a fundamentally different instruction set that made the x86 Red Queen largely irrelevant in mobile, and increasingly in data centers (Apple M-series, AWS Graviton). ARM did not run faster in the x86 race. It changed the track entirely.\n\nThe operational lesson for founders and operators: identify whether you are in a race to win or a race to maintain. In many industries, the race is to maintain — every investment you make produces a temporary advantage that competitors replicate within 12–24 months, and the permanent outcome of all that running is that your starting position is roughly where you finished. Recognizing this early allows capital allocation toward escape vectors before the sunk-cost trap of the arms race becomes the primary organizing principle of the business.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nHelps agents diagnose Red Queen competitive dynamics where continual investment maintains relative position rather than creating durable advantage, then evaluate practical escape options.\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\nStrategy teams, founders, operators, and their agents use this skill to evaluate whether a market, initiative, or competitive response is trapped in continuous improvement without durable relative gain. It guides users through diagnosing imitation speed, margin pressure, investment escalation, and whether to run faster, change tracks, or exit.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can produce misleading strategic recommendations if examples, market claims, or user-provided business facts are stale or incomplete.\n\nMitigation: Treat outputs as advisory, verify important facts and financial assumptions, and review decisions with domain experts before acting.\n\nRisk: The skill may over-apply the Red Queen framing when structural barriers such as strong IP, regulation, or network effects materially slow imitation.\n\nMitigation: Check the skill's stated fit criteria and explicitly test for durable imitation barriers before accepting the diagnosis.\n\n## Reference(s):\n\n- [Sources - red-queen-effect](artifact/references/sources.md)\n- [Method in Action: Van Valen 1973 + Intel vs. AMD 1990-2010](artifact/examples/van-valen-1973-intel-vs-amd-1990-2010.md)\n- [Method in Action: The Frontier-AI Training Race (2023-2026)](artifact/examples/frontier-ai-labs-training-race-2023-2026.md)\n- [Red Queen Effect skill page](https://www.deciqai.com/c/red-queen-effect)\n- [Red Queen Effect machine-readable metadata](https://www.deciqai.com/s/red-queen-effect.json)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown diagnostic template and coaching prompts]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [No executable code; outputs are advisory strategy analysis that should be fact-checked before strategic or financial decisions.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\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, 12487 bytes\n\nFiles: examples/frontier-ai-labs-training-race-2023-2026.md (6988b), examples/van-valen-1973-intel-vs-amd-1990-2010.md (3994b), references/sources.md (1953b), skill-card.md (2034b), SKILL.md (8868b), _meta.json (135b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet.\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with `porters-five-forces` (diagnoses structure; Red Queen explains why strong competitors still don't earn), `second-curve` (escaping the Red Queen is the primary case for a second curve), `network-effects` (temporary escape until the next technology generation resets the field), and `antifragile` (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n- Escalating AI capex / compute arms race, or AI-native competition where everyone must adopt AI just to keep pace and no durable lead emerges\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: is copying speed accelerating? Is required investment growing? Is there any differentiation vector competitors are structurally unable to copy?\n> **[WAIT — do not advance until user responds]**\n5. Close: Red Queen confirmed or denied + escape vector identified + recommendation: run faster / change games / exit.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Diagnose:** primary competitive investment; imitation speed (months); margin trend 5–10 years; are all major competitors investing at roughly the same rate?\n\n**Step 2 — Confirm Red Queen:** absolute performance improving for all (Y/N); relative share stable (Y/N); investment to maintain position growing (Y/N); margins thin despite high activity (Y/N). 3+ Y = Red Queen confirmed.\n\n**Step 3 — Map imitation speed:** half-life of a competitive advantage; is imitation speed accelerating or decelerating?\n\n**Step 4 — Identify escape vector:** Differentiation (competing on an axis rivals ignore) / Vertical integration (control a supply layer rivals rely on externally) / Technology generation gap (new architecture that obsoletes the current race) / Geographic avoidance (less mature markets) / Platformization (become the environment competitors run in).\n\n**Step 5 — Calculate running cost vs. escape cost:** annual cost to maintain position; probability of winning from inside the race; cost and expected value of escape vector; race vs. escape comparison.\n\n**Step 6 — Decide:** Run faster (only if genuine near-term winning condition) / Change tracks (escape vector identified) / Exit (unwinnable; capital better deployed elsewhere). Set timing: how long can current position be maintained while preparing escape?\n\n## Output Template\n```\nRed Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:\n```\n\n*→ Method in Action: [Van Valen 1973 + Intel vs. AMD 1990–2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md)*\n\n*→ 2026 lens: [The Frontier-AI Training Race (2023–2026)](examples/frontier-ai-labs-training-race-2023-2026.md)*\n\n## Pack: Red Queen Across Industries\n\n| Industry | Primary arms race | Imitation speed | Escape example |\n|---|---|---|---|\n| Airlines | Frequent-flyer, yield management | 12–24 mo | Southwest (different segment) |\n| Retail | Supply chain, loyalty | 18–36 mo | Amazon (platform + logistics) |\n| Smartphones | Features, camera, processor | 12–18 mo | Apple (ecosystem lock-in) |\n| Semiconductors (x86) | Process node, microarchitecture | 18–24 mo | ARM (technology generation gap) |\n| Online advertising | Bidding, targeting | 3–6 mo | Google/Meta (first-party data) |\n\n## Applying It Well\n\n- Diagnostic question: not \"are we improving?\" but \"are we improving *faster* than all competitors simultaneously?\"\n- Recognize the Red Queen early — allocate capital toward escape vectors before the sunk-cost trap takes hold.\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 need to match their feature\" | Entering the Red Queen — table stakes in 12 months, no durable advantage. |\n| [D] \"Once we win this round, we'll have a clear lead\" | Winning a round means surviving to the next round at higher investment levels. No stable lead. |\n| [D] \"We're innovating faster than they can copy\" | Temporary windows, not moats. Is your lead measured in quarters or years? |\n| [D] \"Our market share is stable, so we're doing well\" | Stable share = running hard enough to maintain position. Check margins. |\n| [D] \"We just need more investment to break through\" | More investment → more improvement → immediately replicated. Escalation is the Red Queen's self-reinforcing mechanism. |\n| [D] \"The winner of this arms race will take all\" | Most Red Queen races have no winner — only survivors at higher cost. Winner-take-all requires structural network effects most industries lack. |\n| [D] \"We should focus on execution, not strategy\" | Excellent execution in a Red Queen race produces excellent running. If the track leads nowhere, execution delays the strategic question. |\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- Investment in competitive capabilities growing 3+ years without margin improvement\n- Every advantage can be named along with the month competitors copied it\n- Team is debating \"whether to match\" rather than \"whether to change the game\"\n- \"Staying competitive\" has replaced \"building advantage\" as the primary strategic frame\n- The company's strongest argument for continued investment is \"we can't afford not to\"\n\n## Verification\n\n- [ ] Imitation speed estimated explicitly (months); margin trend 5+ years examined\n- [ ] Red Queen presence confirmed or denied against three structural criteria\n- [ ] At least one escape vector evaluated for feasibility and cost\n- [ ] Cost of race vs. escape vector compared; \"run faster\" vs. \"change game\" distinguished\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/red-queen-effect** · ⭐ 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\": \"red-queen-effect\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1783596071974\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitiveness Evolves.* Princeton University Press. ISBN 978-0691131146. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n- Epoch AI (2023–2025). *Machine Learning Trends / Notable AI Models* database and analyses (epoch.ai). Documents the escalation of frontier training compute, dataset size, and cost across successive model generations — the empirical backbone for the 2023–2026 frontier-AI Red Queen example.\n- Hyperscaler and AI-lab public disclosures, 2024–2026 (earnings calls, capital-expenditure guidance, and widely reported financial commentary from the major cloud providers and leading AI labs). Basis for the qualified statements about escalating AI capex and loss-making frontier training; specific figures qualified or omitted where exact public values were not verified against primary filings.\n\nFile v1.0.4:examples/frontier-ai-labs-training-race-2023-2026.md\n\n# Method in Action: The Frontier-AI Training Race (2023–2026)\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\nBetween 2023 and 2026 the leading frontier AI labs — OpenAI, Anthropic, Google DeepMind, Meta, xAI, and others — entered a textbook Red Queen race. Each must keep training ever-larger and better models, and keep buying more compute, simply to hold relative position while every rival does the same. The absolute capability of the frontier rises fast; the relative ordering among the top labs churns but never settles; and the cost of merely staying in the pack escalates every cycle. This walks the case through the skill's own six-step Process.\n\n## Step 1 — Diagnose\n\n- **Primary competitive investment:** training compute (GPUs/accelerators), the capital and data-center capacity to run them, and the scarce research/engineering talent to use them. Frontier training runs and the infrastructure behind them are the arms.\n- **Imitation speed:** roughly one model generation — on the order of months. When one lab ships a materially stronger model, rivals close much of the gap with a comparable release within a similar window, and capability benchmarks that one lab tops are frequently overtaken shortly after.\n- **Margin trend:** frontier model development has been heavily loss-making for the leading labs through this period. Revenue has grown quickly, but training and inference costs — and the capex commitments behind them — have grown at least as fast, so the leading pure-play frontier labs were reported to be spending well in excess of revenue.\n- **Are all major competitors investing at roughly the same rate?** Yes. Multiple large players are all committing very large sums to compute and data centers in the same window, and the biggest cloud/hyperscaler backers publicly raised their AI-related capital-expenditure guidance repeatedly across 2024–2025.\n\n## Step 2 — Confirm Red Queen\n\n- Absolute performance improving for all (Y): frontier model capability rose steeply and continuously across the field.\n- Relative share/position stable-but-contested (Y): no lab established a durable, uncontested lead; the \"best model\" title changed hands repeatedly and quickly.\n- Investment to maintain position growing (Y): the compute and capital required just to stay at the frontier increased each generation.\n- Margins thin/negative despite high activity (Y): frontier training remained deeply unprofitable for the leading pure-play labs despite rapid revenue growth.\n\nFour of four → **Red Queen confirmed.** All the running keeps each lab in roughly the same relative place while the treadmill speeds up.\n\n## Step 3 — Map imitation speed\n\nThe half-life of a frontier-capability advantage is short — measured in months, not years. A benchmark lead is routinely matched or exceeded by the next competitor release. And imitation speed is **accelerating** in some respects: the diffusion of methods (RLHF/RLAIF, mixture-of-experts, reasoning/inference-time compute, distillation) plus the emergence of strong open-weight models means that a given capability level becomes broadly reproducible faster than before. Distillation and open-weight releases in particular compress the time for a frontier result to become widely available.\n\n## Step 4 — Identify escape vector\n\n- **Differentiation:** compete on an axis rivals under-serve — enterprise trust/safety, reliability, vertical depth, developer experience, or agentic/product surface — rather than only on raw benchmark score.\n- **Vertical integration:** control a compute layer rivals rent externally — custom silicon and secured, long-term data-center/energy capacity — to blunt the cost treadmill.\n- **Technology generation gap:** a new architecture or training paradigm (e.g., shifting the axis of competition from pretraining scale toward inference-time reasoning, or efficiency breakthroughs) that partly obsoletes the current pure-scale race.\n- **Geographic / regulatory avoidance:** markets or deployment contexts where incumbents are structurally constrained.\n- **Platformization:** become the environment competitors and downstream builders run inside — the default API/model layer, distribution, and ecosystem lock-in — so that switching costs and data flywheels retain value the raw model cannot.\n\n## Step 5 — Calculate running cost vs. escape cost\n\n- **Annual cost to maintain position:** very high and rising — the multi-billion-dollar compute and data-center commitments are the price of a seat at the frontier, not a winning move.\n- **Probability of winning from inside the race:** low for \"permanent lead.\" With months-long imitation half-lives and no strong structural moat on model quality alone, staying in the scale race mostly buys survival to the next, more expensive round.\n- **Cost / expected value of escape:** platformization and vertical integration (custom silicon + secured energy/compute + ecosystem lock-in) are expensive and slow but produce durability that a raw benchmark lead does not. Distribution and switching costs — not model weights — are where captured value persists.\n\n## Step 6 — Decide\n\n- **Run faster** only where there is a genuine near-term winning condition (a real generation lead you can convert into distribution before it is copied). Pure benchmark-matching is table stakes.\n- **Change tracks** is the durable answer: convert transient capability leads into platform, distribution, ecosystem, and integrated-compute advantages that survive the next model release — because the model advantage itself will not.\n- **Exit / narrow** is rational for players without the capital or a differentiated axis: specialize, build on open weights, or serve a defensible vertical rather than fund an unwinnable scale race.\n- **Timing:** treat each capability lead as a months-long window, and allocate toward escape vectors *before* the sunk-cost logic of \"we can't afford not to keep spending\" becomes the company's primary organizing principle.\n\n**Operational lesson for founders and operators:** in the frontier-AI race the running is real and the absolute progress is genuine — but relative position among the leaders is not durably purchased by compute alone. The value of the arms race accrues heavily to users (rapidly cheaper, more capable models) and to the compute suppliers; the escape is to own a layer the race cannot immediately replicate.\n\n*Sources: Van Valen, L. (1973), \"A New Evolutionary Law,\" Evolutionary Theory 1:1–30; Carroll, L. (1871), Through the Looking-Glass, Ch. 2; Barnett, W. P. (2008), The Red Queen Among Organizations, Princeton University Press. Contemporary context on frontier-lab compute and capex escalation drawn from widely reported 2024–2026 public disclosures and reporting by major hyperscalers and AI labs (e.g., published capital-expenditure guidance and earnings commentary). Specific figures are omitted or qualified where exact public values were not verified.*\n\nFile v1.0.4:examples/van-valen-1973-intel-vs-amd-1990-2010.md\n\n# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where switching costs (data center architecture lock-in) provided temporary protection. But the deeper Red Queen escape came from ARM architecture — not a company in the x86 race, but a fundamentally different instruction set that made the x86 Red Queen largely irrelevant in mobile, and increasingly in data centers (Apple M-series, AWS Graviton). ARM did not run faster in the x86 race. It changed the track entirely.\n\nThe operational lesson for founders and operators: identify whether you are in a race to win or a race to maintain. In many industries, the race is to maintain — every investment you make produces a temporary advantage that competitors replicate within 12–24 months, and the permanent outcome of all that running is that your starting position is roughly where you finished. Recognizing this early allows capital allocation toward escape vectors before the sunk-cost trap of the arms race becomes the primary organizing principle of the business.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nHelps agents diagnose Red Queen competitive dynamics where organizations keep investing to maintain relative position, then evaluate whether to run faster, change tracks, or exit. <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 users, and strategy operators use this skill to analyze competitive arms races, imitation speed, margin pressure, and possible escape vectors. It is suited to business strategy, market-entry, and competitive-positioning discussions rather than verified current market research. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Strategic examples and business recommendations may be mistaken for verified current market research. <br>\nMitigation: Treat outputs as analytical guidance and verify market facts, financial claims, and recent AI-industry dynamics against current authoritative sources before making decisions. <br>\n\n\n## Reference(s): <br>\n- [Primary sources](references/sources.md) <br>\n- [Van Valen 1973 + Intel vs. AMD 1990-2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md) <br>\n- [The Frontier-AI Training Race (2023-2026)](examples/frontier-ai-labs-training-race-2023-2026.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown diagnostic analysis and recommendation tables] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May ask step-by-step clarification questions before producing a diagnosis.] <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, 8576 bytes\n\nFiles: examples/van-valen-1973-intel-vs-amd-1990-2010.md (3994b), references/sources.md (1258b), skill-card.md (2272b), SKILL.md (8607b), _meta.json (135b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet.\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with `porters-five-forces` (diagnoses structure; Red Queen explains why strong competitors still don't earn), `second-curve` (escaping the Red Queen is the primary case for a second curve), `network-effects` (temporary escape until the next technology generation resets the field), and `antifragile` (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: is copying speed accelerating? Is required investment growing? Is there any differentiation vector competitors are structurally unable to copy?\n> **[WAIT — do not advance until user responds]**\n5. Close: Red Queen confirmed or denied + escape vector identified + recommendation: run faster / change games / exit.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Diagnose:** primary competitive investment; imitation speed (months); margin trend 5–10 years; are all major competitors investing at roughly the same rate?\n\n**Step 2 — Confirm Red Queen:** absolute performance improving for all (Y/N); relative share stable (Y/N); investment to maintain position growing (Y/N); margins thin despite high activity (Y/N). 3+ Y = Red Queen confirmed.\n\n**Step 3 — Map imitation speed:** half-life of a competitive advantage; is imitation speed accelerating or decelerating?\n\n**Step 4 — Identify escape vector:** Differentiation (competing on an axis rivals ignore) / Vertical integration (control a supply layer rivals rely on externally) / Technology generation gap (new architecture that obsoletes the current race) / Geographic avoidance (less mature markets) / Platformization (become the environment competitors run in).\n\n**Step 5 — Calculate running cost vs. escape cost:** annual cost to maintain position; probability of winning from inside the race; cost and expected value of escape vector; race vs. escape comparison.\n\n**Step 6 — Decide:** Run faster (only if genuine near-term winning condition) / Change tracks (escape vector identified) / Exit (unwinnable; capital better deployed elsewhere). Set timing: how long can current position be maintained while preparing escape?\n\n## Output Template\n```\nRed Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:\n```\n\n*→ Method in Action: [Van Valen 1973 + Intel vs. AMD 1990–2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md)*\n\n## Pack: Red Queen Across Industries\n\n| Industry | Primary arms race | Imitation speed | Escape example |\n|---|---|---|---|\n| Airlines | Frequent-flyer, yield management | 12–24 mo | Southwest (different segment) |\n| Retail | Supply chain, loyalty | 18–36 mo | Amazon (platform + logistics) |\n| Smartphones | Features, camera, processor | 12–18 mo | Apple (ecosystem lock-in) |\n| Semiconductors (x86) | Process node, microarchitecture | 18–24 mo | ARM (technology generation gap) |\n| Online advertising | Bidding, targeting | 3–6 mo | Google/Meta (first-party data) |\n\n## Applying It Well\n\n- Diagnostic question: not \"are we improving?\" but \"are we improving *faster* than all competitors simultaneously?\"\n- Recognize the Red Queen early — allocate capital toward escape vectors before the sunk-cost trap takes hold.\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 need to match their feature\" | Entering the Red Queen — table stakes in 12 months, no durable advantage. |\n| [D] \"Once we win this round, we'll have a clear lead\" | Winning a round means surviving to the next round at higher investment levels. No stable lead. |\n| [D] \"We're innovating faster than they can copy\" | Temporary windows, not moats. Is your lead measured in quarters or years? |\n| [D] \"Our market share is stable, so we're doing well\" | Stable share = running hard enough to maintain position. Check margins. |\n| [D] \"We just need more investment to break through\" | More investment → more improvement → immediately replicated. Escalation is the Red Queen's self-reinforcing mechanism. |\n| [D] \"The winner of this arms race will take all\" | Most Red Queen races have no winner — only survivors at higher cost. Winner-take-all requires structural network effects most industries lack. |\n| [D] \"We should focus on execution, not strategy\" | Excellent execution in a Red Queen race produces excellent running. If the track leads nowhere, execution delays the strategic question. |\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- Investment in competitive capabilities growing 3+ years without margin improvement\n- Every advantage can be named along with the month competitors copied it\n- Team is debating \"whether to match\" rather than \"whether to change the game\"\n- \"Staying competitive\" has replaced \"building advantage\" as the primary strategic frame\n- The company's strongest argument for continued investment is \"we can't afford not to\"\n\n## Verification\n\n- [ ] Imitation speed estimated explicitly (months); margin trend 5+ years examined\n- [ ] Red Queen presence confirmed or denied against three structural criteria\n- [ ] At least one escape vector evaluated for feasibility and cost\n- [ ] Cost of race vs. escape vector compared; \"run faster\" vs. \"change game\" distinguished\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/red-queen-effect** · ⭐ 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\": \"red-queen-effect\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783509384986\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitive Evolution Works.* Princeton University Press. ISBN 978-0691128030. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n\nFile v1.0.3:examples/van-valen-1973-intel-vs-amd-1990-2010.md\n\n# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where switching costs (data center architecture lock-in) provided temporary protection. But the deeper Red Queen escape came from ARM architecture — not a company in the x86 race, but a fundamentally different instruction set that made the x86 Red Queen largely irrelevant in mobile, and increasingly in data centers (Apple M-series, AWS Graviton). ARM did not run faster in the x86 race. It changed the track entirely.\n\nThe operational lesson for founders and operators: identify whether you are in a race to win or a race to maintain. In many industries, the race is to maintain — every investment you make produces a temporary advantage that competitors replicate within 12–24 months, and the permanent outcome of all that running is that your starting position is roughly where you finished. Recognizing this early allows capital allocation toward escape vectors before the sunk-cost trap of the arms race becomes the primary organizing principle of the business.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nHelps agents diagnose competitive arms races where ongoing investment improves absolute performance but does not create durable relative advantage, then compare run-faster, change-track, or exit options. <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>\nOperators, founders, strategy teams, and agents use this skill to assess whether a market or initiative is trapped in a Red Queen race, estimate imitation speed and margin pressure, and identify escape vectors or exit decisions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Users may paste confidential company details while using observed-example notes or diagnostic prompts. <br>\nMitigation: Avoid adding confidential company information to shared skill files or public examples. <br>\nRisk: Strategy recommendations may be misleading if used without validating imitation speed, margins, and structural barriers. <br>\nMitigation: Review the diagnosis against current business data before making investment, market-entry, or exit decisions. <br>\n\n\n## Reference(s): <br>\n- [Red Queen Effect release page](https://clawhub.ai/deciqai/skills/red-queen-effect) <br>\n- [Sources - red-queen-effect](references/sources.md) <br>\n- [Method in Action: Van Valen 1973 + Intel vs. AMD 1990-2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md) <br>\n- [deciqAI Knowledge Skills repository](https://github.com/deciqAI/knowledge-skills) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown diagnostic summary with structured recommendation tables] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May ask step-by-step coaching questions before producing a final diagnosis.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: 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, 8536 bytes\n\nFiles: examples/van-valen-1973-intel-vs-amd-1990-2010.md (3994b), references/sources.md (1258b), skill-card.md (2088b), SKILL.md (8713b), _meta.json (135b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet.\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with `porters-five-forces` (diagnoses structure; Red Queen explains why strong competitors still don't earn), `second-curve` (escaping the Red Queen is the primary case for a second curve), `network-effects` (temporary escape until the next technology generation resets the field), and `antifragile` (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: is copying speed accelerating? Is required investment growing? Is there any differentiation vector competitors are structurally unable to copy?\n> **[WAIT — do not advance until user responds]**\n5. Close: Red Queen confirmed or denied + escape vector identified + recommendation: run faster / change games / exit.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Diagnose:** primary competitive investment; imitation speed (months); margin trend 5–10 years; are all major competitors investing at roughly the same rate?\n\n**Step 2 — Confirm Red Queen:** absolute performance improving for all (Y/N); relative share stable (Y/N); investment to maintain position growing (Y/N); margins thin despite high activity (Y/N). 3+ Y = Red Queen confirmed.\n\n**Step 3 — Map imitation speed:** half-life of a competitive advantage; is imitation speed accelerating or decelerating?\n\n**Step 4 — Identify escape vector:** Differentiation (competing on an axis rivals ignore) / Vertical integration (control a supply layer rivals rely on externally) / Technology generation gap (new architecture that obsoletes the current race) / Geographic avoidance (less mature markets) / Platformization (become the environment competitors run in).\n\n**Step 5 — Calculate running cost vs. escape cost:** annual cost to maintain position; probability of winning from inside the race; cost and expected value of escape vector; race vs. escape comparison.\n\n**Step 6 — Decide:** Run faster (only if genuine near-term winning condition) / Change tracks (escape vector identified) / Exit (unwinnable; capital better deployed elsewhere). Set timing: how long can current position be maintained while preparing escape?\n\n## Output Template\n```\nRed Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:\n```\n\n*→ Method in Action: [Van Valen 1973 + Intel vs. AMD 1990–2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md)*\n\n## Pack: Red Queen Across Industries\n\n| Industry | Primary arms race | Imitation speed | Escape example |\n|---|---|---|---|\n| Airlines | Frequent-flyer, yield management | 12–24 mo | Southwest (different segment) |\n| Retail | Supply chain, loyalty | 18–36 mo | Amazon (platform + logistics) |\n| Smartphones | Features, camera, processor | 12–18 mo | Apple (ecosystem lock-in) |\n| Semiconductors (x86) | Process node, microarchitecture | 18–24 mo | ARM (technology generation gap) |\n| Online advertising | Bidding, targeting | 3–6 mo | Google/Meta (first-party data) |\n\n## Applying It Well\n\n- Diagnostic question: not \"are we improving?\" but \"are we improving *faster* than all competitors simultaneously?\"\n- Recognize the Red Queen early — allocate capital toward escape vectors before the sunk-cost trap takes hold.\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 need to match their feature\" | Entering the Red Queen — table stakes in 12 months, no durable advantage. |\n| [D] \"Once we win this round, we'll have a clear lead\" | Winning a round means surviving to the next round at higher investment levels. No stable lead. |\n| [D] \"We're innovating faster than they can copy\" | Temporary windows, not moats. Is your lead measured in quarters or years? |\n| [D] \"Our market share is stable, so we're doing well\" | Stable share = running hard enough to maintain position. Check margins. |\n| [D] \"We just need more investment to break through\" | More investment → more improvement → immediately replicated. Escalation is the Red Queen's self-reinforcing mechanism. |\n| [D] \"The winner of this arms race will take all\" | Most Red Queen races have no winner — only survivors at higher cost. Winner-take-all requires structural network effects most industries lack. |\n| [D] \"We should focus on execution, not strategy\" | Excellent execution in a Red Queen race produces excellent running. If the track leads nowhere, execution delays the strategic question. |\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- Investment in competitive capabilities growing 3+ years without margin improvement\n- Every advantage can be named along with the month competitors copied it\n- Team is debating \"whether to match\" rather than \"whether to change the game\"\n- \"Staying competitive\" has replaced \"building advantage\" as the primary strategic frame\n- The company's strongest argument for continued investment is \"we can't afford not to\"\n\n## Verification\n\n- [ ] Imitation speed estimated explicitly (months); margin trend 5+ years examined\n- [ ] Red Queen presence confirmed or denied against three structural criteria\n- [ ] At least one escape vector evaluated for feasibility and cost\n- [ ] Cost of race vs. escape vector compared; \"run faster\" vs. \"change game\" distinguished\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/red-queen-effect?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=red-queen-effect** · ⭐ 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\": \"red-queen-effect\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783472467792\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitive Evolution Works.* Princeton University Press. ISBN 978-0691128030. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n\nFile v1.0.2:examples/van-valen-1973-intel-vs-amd-1990-2010.md\n\n# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where switching costs (data center architecture lock-in) provided temporary protection. But the deeper Red Queen escape came from ARM architecture — not a company in the x86 race, but a fundamentally different instruction set that made the x86 Red Queen largely irrelevant in mobile, and increasingly in data centers (Apple M-series, AWS Graviton). ARM did not run faster in the x86 race. It changed the track entirely.\n\nThe operational lesson for founders and operators: identify whether you are in a race to win or a race to maintain. In many industries, the race is to maintain — every investment you make produces a temporary advantage that competitors replicate within 12–24 months, and the permanent outcome of all that running is that your starting position is roughly where you finished. Recognizing this early allows capital allocation toward escape vectors before the sunk-cost trap of the arms race becomes the primary organizing principle of the business.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nGuides agents through Red Queen Effect diagnosis for competitive situations where continuous improvement raises costs but does not create durable relative advantage. <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>\nBusiness operators, strategy teams, founders, and agents use this skill to test whether a market is a Red Queen race and choose whether to run faster, change tracks, or exit. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Business examples and external footer links may need normal provenance review before enterprise use. <br>\nMitigation: Review cited sources and external links before relying on the skill in a governed workflow. <br>\nRisk: Competitive diagnosis can be misleading when margin history, imitation speed, or structural barriers are estimated poorly. <br>\nMitigation: Validate the user's market data and explicitly check imitation speed, margin trend, and barriers before acting on recommendations. <br>\n\n\n## Reference(s): <br>\n- [Sources](references/sources.md) <br>\n- [Method in Action: Van Valen 1973 + Intel vs. AMD 1990-2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md) <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/red-queen-effect) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown diagnosis with structured tables and recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May ask step-by-step coaching questions before producing a final diagnosis.] <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, 8534 bytes\n\nFiles: examples/van-valen-1973-intel-vs-amd-1990-2010.md (3994b), references/sources.md (1258b), skill-card.md (2309b), SKILL.md (8574b), _meta.json (135b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet.\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with [`porters-five-forces`](../porters-five-forces/SKILL.md) (diagnoses structure; Red Queen explains why strong competitors still don't earn), [`second-curve`](../second-curve/SKILL.md) (escaping the Red Queen is the primary case for a second curve), [`network-effects`](../network-effects/SKILL.md) (temporary escape until the next technology generation resets the field), and [`antifragile`](../antifragile/SKILL.md) (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: is copying speed accelerating? Is required investment growing? Is there any differentiation vector competitors are structurally unable to copy?\n> **[WAIT — do not advance until user responds]**\n5. Close: Red Queen confirmed or denied + escape vector identified + recommendation: run faster / change games / exit.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Diagnose:** primary competitive investment; imitation speed (months); margin trend 5–10 years; are all major competitors investing at roughly the same rate?\n\n**Step 2 — Confirm Red Queen:** absolute performance improving for all (Y/N); relative share stable (Y/N); investment to maintain position growing (Y/N); margins thin despite high activity (Y/N). 3+ Y = Red Queen confirmed.\n\n**Step 3 — Map imitation speed:** half-life of a competitive advantage; is imitation speed accelerating or decelerating?\n\n**Step 4 — Identify escape vector:** Differentiation (competing on an axis rivals ignore) / Vertical integration (control a supply layer rivals rely on externally) / Technology generation gap (new architecture that obsoletes the current race) / Geographic avoidance (less mature markets) / Platformization (become the environment competitors run in).\n\n**Step 5 — Calculate running cost vs. escape cost:** annual cost to maintain position; probability of winning from inside the race; cost and expected value of escape vector; race vs. escape comparison.\n\n**Step 6 — Decide:** Run faster (only if genuine near-term winning condition) / Change tracks (escape vector identified) / Exit (unwinnable; capital better deployed elsewhere). Set timing: how long can current position be maintained while preparing escape?\n\n## Output Template\n```\nRed Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:\n```\n\n*→ Method in Action: [Van Valen 1973 + Intel vs. AMD 1990–2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md)*\n\n## Pack: Red Queen Across Industries\n\n| Industry | Primary arms race | Imitation speed | Escape example |\n|---|---|---|---|\n| Airlines | Frequent-flyer, yield management | 12–24 mo | Southwest (different segment) |\n| Retail | Supply chain, loyalty | 18–36 mo | Amazon (platform + logistics) |\n| Smartphones | Features, camera, processor | 12–18 mo | Apple (ecosystem lock-in) |\n| Semiconductors (x86) | Process node, microarchitecture | 18–24 mo | ARM (technology generation gap) |\n| Online advertising | Bidding, targeting | 3–6 mo | Google/Meta (first-party data) |\n\n## Applying It Well\n\n- Diagnostic question: not \"are we improving?\" but \"are we improving *faster* than all competitors simultaneously?\"\n- Recognize the Red Queen early — allocate capital toward escape vectors before the sunk-cost trap takes hold.\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 need to match their feature\" | Entering the Red Queen — table stakes in 12 months, no durable advantage. |\n| [D] \"Once we win this round, we'll have a clear lead\" | Winning a round means surviving to the next round at higher investment levels. No stable lead. |\n| [D] \"We're innovating faster than they can copy\" | Temporary windows, not moats. Is your lead measured in quarters or years? |\n| [D] \"Our market share is stable, so we're doing well\" | Stable share = running hard enough to maintain position. Check margins. |\n| [D] \"We just need more investment to break through\" | More investment → more improvement → immediately replicated. Escalation is the Red Queen's self-reinforcing mechanism. |\n| [D] \"The winner of this arms race will take all\" | Most Red Queen races have no winner — only survivors at higher cost. Winner-take-all requires structural network effects most industries lack. |\n| [D] \"We should focus on execution, not strategy\" | Excellent execution in a Red Queen race produces excellent running. If the track leads nowhere, execution delays the strategic question. |\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- Investment in competitive capabilities growing 3+ years without margin improvement\n- Every advantage can be named along with the month competitors copied it\n- Team is debating \"whether to match\" rather than \"whether to change the game\"\n- \"Staying competitive\" has replaced \"building advantage\" as the primary strategic frame\n- The company's strongest argument for continued investment is \"we can't afford not to\"\n\n## Verification\n\n- [ ] Imitation speed estimated explicitly (months); margin trend 5+ years examined\n- [ ] Red Queen presence confirmed or denied against three structural criteria\n- [ ] At least one escape vector evaluated for feasibility and cost\n- [ ] Cost of race vs. escape vector compared; \"run faster\" vs. \"change game\" distinguished\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\": \"red-queen-effect\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783463551821\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitive Evolution Works.* Princeton University Press. ISBN 978-0691128030. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n\nFile v1.0.1:examples/van-valen-1973-intel-vs-amd-1990-2010.md\n\n# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where switching costs (data center architecture lock-in) provided temporary protection. But the deeper Red Queen escape came from ARM architecture — not a company in the x86 race, but a fundamentally different instruction set that made the x86 Red Queen largely irrelevant in mobile, and increasingly in data centers (Apple M-series, AWS Graviton). ARM did not run faster in the x86 race. It changed the track entirely.\n\nThe operational lesson for founders and operators: identify whether you are in a race to win or a race to maintain. In many industries, the race is to maintain — every investment you make produces a temporary advantage that competitors replicate within 12–24 months, and the permanent outcome of all that running is that your starting position is roughly where you finished. Recognizing this early allows capital allocation toward escape vectors before the sunk-cost trap of the arms race becomes the primary organizing principle of the business.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nRed Queen Effect helps agents diagnose competitive arms races where sustained investment improves absolute performance but leaves relative position and margins largely unchanged. <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, strategists, and business analysts use this skill to decide whether an industry or initiative is trapped in a Red Queen race and whether to run faster, change tracks, or exit. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may produce competitive-dynamics recommendations that are incomplete or misleading if the user provides weak market-share, margin, or imitation-speed evidence. <br>\nMitigation: Review recommendations against current business data and treat the output as strategy analysis rather than an automatic decision. <br>\nRisk: The skill asks business questions and may receive sensitive competitive or financial context. <br>\nMitigation: Avoid sharing confidential information unless the deployment environment and data-handling controls are appropriate. <br>\n\n\n## Reference(s): <br>\n- [Primary sources](references/sources.md) <br>\n- [Method in action: Van Valen 1973 + Intel vs. AMD 1990-2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md) <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/red-queen-effect) <br>\n- [Publisher profile](https://clawhub.ai/user/deciqai) <br>\n- [deciqAI](https://deciqai.com) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown diagnosis with decision tables and recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable output; may ask follow-up business questions before producing a recommendation.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (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.0: 5 files, 8592 bytes\n\nFiles: examples/van-valen-1973-intel-vs-amd-1990-2010.md (3994b), references/sources.md (1258b), skill-card.md (2359b), SKILL.md (8574b), _meta.json (135b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet.\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with [`porters-five-forces`](../porters-five-forces/SKILL.md) (diagnoses structure; Red Queen explains why strong competitors still don't earn), [`second-curve`](../second-curve/SKILL.md) (escaping the Red Queen is the primary case for a second curve), [`network-effects`](../network-effects/SKILL.md) (temporary escape until the next technology generation resets the field), and [`antifragile`](../antifragile/SKILL.md) (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: is copying speed accelerating? Is required investment growing? Is there any differentiation vector competitors are structurally unable to copy?\n> **[WAIT — do not advance until user responds]**\n5. Close: Red Queen confirmed or denied + escape vector identified + recommendation: run faster / change games / exit.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Diagnose:** primary competitive investment; imitation speed (months); margin trend 5–10 years; are all major competitors investing at roughly the same rate?\n\n**Step 2 — Confirm Red Queen:** absolute performance improving for all (Y/N); relative share stable (Y/N); investment to maintain position growing (Y/N); margins thin despite high activity (Y/N). 3+ Y = Red Queen confirmed.\n\n**Step 3 — Map imitation speed:** half-life of a competitive advantage; is imitation speed accelerating or decelerating?\n\n**Step 4 — Identify escape vector:** Differentiation (competing on an axis rivals ignore) / Vertical integration (control a supply layer rivals rely on externally) / Technology generation gap (new architecture that obsoletes the current race) / Geographic avoidance (less mature markets) / Platformization (become the environment competitors run in).\n\n**Step 5 — Calculate running cost vs. escape cost:** annual cost to maintain position; probability of winning from inside the race; cost and expected value of escape vector; race vs. escape comparison.\n\n**Step 6 — Decide:** Run faster (only if genuine near-term winning condition) / Change tracks (escape vector identified) / Exit (unwinnable; capital better deployed elsewhere). Set timing: how long can current position be maintained while preparing escape?\n\n## Output Template\n```\nRed Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:\n```\n\n*→ Method in Action: [Van Valen 1973 + Intel vs. AMD 1990–2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md)*\n\n## Pack: Red Queen Across Industries\n\n| Industry | Primary arms race | Imitation speed | Escape example |\n|---|---|---|---|\n| Airlines | Frequent-flyer, yield management | 12–24 mo | Southwest (different segment) |\n| Retail | Supply chain, loyalty | 18–36 mo | Amazon (platform + logistics) |\n| Smartphones | Features, camera, processor | 12–18 mo | Apple (ecosystem lock-in) |\n| Semiconductors (x86) | Process node, microarchitecture | 18–24 mo | ARM (technology generation gap) |\n| Online advertising | Bidding, targeting | 3–6 mo | Google/Meta (first-party data) |\n\n## Applying It Well\n\n- Diagnostic question: not \"are we improving?\" but \"are we improving *faster* than all competitors simultaneously?\"\n- Recognize the Red Queen early — allocate capital toward escape vectors before the sunk-cost trap takes hold.\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 need to match their feature\" | Entering the Red Queen — table stakes in 12 months, no durable advantage. |\n| [D] \"Once we win this round, we'll have a clear lead\" | Winning a round means surviving to the next round at higher investment levels. No stable lead. |\n| [D] \"We're innovating faster than they can copy\" | Temporary windows, not moats. Is your lead measured in quarters or years? |\n| [D] \"Our market share is stable, so we're doing well\" | Stable share = running hard enough to maintain position. Check margins. |\n| [D] \"We just need more investment to break through\" | More investment → more improvement → immediately replicated. Escalation is the Red Queen's self-reinforcing mechanism. |\n| [D] \"The winner of this arms race will take all\" | Most Red Queen races have no winner — only survivors at higher cost. Winner-take-all requires structural network effects most industries lack. |\n| [D] \"We should focus on execution, not strategy\" | Excellent execution in a Red Queen race produces excellent running. If the track leads nowhere, execution delays the strategic question. |\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- Investment in competitive capabilities growing 3+ years without margin improvement\n- Every advantage can be named along with the month competitors copied it\n- Team is debating \"whether to match\" rather than \"whether to change the game\"\n- \"Staying competitive\" has replaced \"building advantage\" as the primary strategic frame\n- The company's strongest argument for continued investment is \"we can't afford not to\"\n\n## Verification\n\n- [ ] Imitation speed estimated explicitly (months); margin trend 5+ years examined\n- [ ] Red Queen presence confirmed or denied against three structural criteria\n- [ ] At least one escape vector evaluated for feasibility and cost\n- [ ] Cost of race vs. escape vector compared; \"run faster\" vs. \"change game\" distinguished\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\": \"red-queen-effect\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782904699624\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitive Evolution Works.* Princeton University Press. ISBN 978-0691128030. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n\nFile v1.0.0:examples/van-valen-1973-intel-vs-amd-1990-2010.md\n\n# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where switching costs (data center architecture lock-in) provided temporary protection. But the deeper Red Queen escape came from ARM architecture — not a company in the x86 race, but a fundamentally different instruction set that made the x86 Red Queen largely irrelevant in mobile, and increasingly in data centers (Apple M-series, AWS Graviton). ARM did not run faster in the x86 race. It changed the track entirely.\n\nThe operational lesson for founders and operators: identify whether you are in a race to win or a race to maintain. In many industries, the race is to maintain — every investment you make produces a temporary advantage that competitors replicate within 12–24 months, and the permanent outcome of all that running is that your starting position is roughly where you finished. Recognizing this early allows capital allocation toward escape vectors before the sunk-cost trap of the arms race becomes the primary organizing principle of the business.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nRed Queen Effect helps agents diagnose competitive arms races where continuous investment raises absolute performance but fails to improve relative position, then evaluate whether to run faster, change tracks, or exit. <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>\nDevelopers, founders, strategy teams, and operators use this skill to decide whether a competitive initiative can create durable advantage or is only maintaining position in a fast-copying market. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Strategic diagnosis may be over-applied to markets where strong IP, regulation, network effects, or pre-competitive conditions make imitation slower than assumed. <br>\nMitigation: Confirm imitation speed, margin history, and structural barriers before relying on the recommendation. <br>\nRisk: The security review classifies this bundle as high impact, even though it found no hidden or abusive behavior. <br>\nMitigation: Install only in expected trusted workflows, keep credentials limited to the intended role, and require explicit human approval for production writes or outbound correspondence. <br>\n\n\n## Reference(s): <br>\n- [Primary sources for red-queen-effect](references/sources.md) <br>\n- [Method in Action: Van Valen 1973 + Intel vs. AMD 1990-2010](examples/van-valen-1973-intel-vs-amd-1990-2010.md) <br>\n- [Publisher profile](https://clawhub.ai/user/deciqai) <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/red-queen-effect) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown diagnosis with structured tables and recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May ask step-by-step coaching questions before producing a final diagnosis.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (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>","readmeExcerpt":"Skill: Red Queen Effect Owner: deciqai Summary: Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:13:00.187Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/red-queen-effect.json) v1.0.4 | 2026-07-09T11:21:11.974Z ","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Red Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:"},{"language":"text","snippet":"Red Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:"},{"language":"text","snippet":"Red Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:"},{"language":"text","snippet":"Red Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:"},{"language":"text","snippet":"Red Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:"},{"language":"text","snippet":"Red Queen Diagnosis: <context>\nImitation speed (months): | Margin trend 5yr: | Investment escalation Y/N:\nVerdict: [Red Queen Active / Partial / Not Applicable]\n\nEscape Vector | Feasibility H/M/L | Time to implement | Advantage durability\nDifferentiation | | |\nVertical integration | | |\nTechnology leap | | |\nGeographic avoidance | | |\nPlatformization | | |\n\nRecommendation: [run faster / change tracks / exit] — [rationale] — Timeline:"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: red-queen-effect\ndescription: \"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again within a year,' 'we improve but the gap stays the same,' or is evaluating whether to enter a low-margin high-activity industry. Do NOT activate when: the competitive advantage is protected by strong IP, regulatory approval, or deep network effects that genuinely slow imitation; or when the situation is pre-competitive with no direct rivals yet. More: deciqai.com/c/red-queen-effect\"\n---\n\n# Red Queen Effect\n\n## Overview\n\nThe **Red Queen Effect**: competitors must continuously improve just to maintain relative position — because everyone else is improving simultaneously. Absolute performance rises; relative position barely shifts; cumulative effort primarily produces consumer surplus, not corporate profit. Named after Leigh Van Valen's 1973 evolutionary law and Lewis Carroll's Red Queen (\"It takes all the running you can do, to keep in the same place\").\n\nComposes with `porters-five-forces` (diagnoses structure; Red Queen explains why strong competitors still don't earn), `second-curve` (escaping the Red Queen is the primary case for a second curve), `network-effects` (temporary escape until the next technology generation resets the field), and `antifragile` (gaining from Red Queen stress rather than merely surviving it).\n\n## When to Use\n\n- Investing heavily but market share is not moving; industry growing but margins chronically thin\n- Competitive gap stays constant despite continuous product improvement\n- Post-mortem: advantage was copied within 12–24 months; team keeps asking \"should we match them?\"\n- Evaluating whether to enter an industry or whether an initiative will produce durable advantage\n- Escalating AI capex / compute arms race, or AI-native competition where everyone must adopt AI just to keep pace and no durable lead emerges\n\n**Not when:** genuine structural barriers to imitation exist (IP, regulatory approvals, deep network effects); pure operational efficiency decision; pre-competitive with no direct rivals. **Stop:** once Red Queen is confirmed + escape vector identified, or NOT confirmed + durability factor named.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a specific competitive situation → run The Process directly.\n- **Coaching 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: in a Red Queen race, all the running keeps you in the same place — run faster, change tracks, or exit?\n2. Check fit: are competitors all improving simultaneously, share barely shifting, margins thin? If yes, Red Queen is active.\n3. Elicit the structure: what is the key competitive investment? How long to copy a new advantage? What does the margin history look like?\n> **[WAIT — do not advance until user responds"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"red-queen-effect\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784225580187\n}"},{"path":"references/sources.md","content":"# Sources — red-queen-effect\n\n> *Primary sources for the [red-queen-effect](../SKILL.md) skill.*\n\n- Van Valen, L. (1973). \"A New Evolutionary Law.\" *Evolutionary Theory*, 1, 1–30. The original paper establishing the evolutionary law.\n- Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2. Original Red Queen dialogue: \"It takes all the running you can do, to keep in the same place.\"\n- Barnett, W. P. (2008). *The Red Queen Among Organizations: How Competitiveness Evolves.* Princeton University Press. ISBN 978-0691131146. The definitive business translation of Van Valen's law.\n- Barnett, W. P., & Hansen, M. T. (1996). \"The Red Queen in Organizational Evolution.\" *Strategic Management Journal*, 17(S1), 139–157. Empirical evidence of Red Queen dynamics in organizational competition.\n- Porter, M. E. (1996). \"What Is Strategy?\" *Harvard Business Review*, November–December. The distinction between operational effectiveness (Red Queen running) and strategic positioning (changing the game) — Porter's framework is the structural complement to Red Queen diagnosis.\n- Ridley, M. (1993). *The Red Queen: Sex and the Evolution of Human Nature.* Macmillan. Popular treatment of Van Valen's law and its biological implications.\n- Epoch AI (2023–2025). *Machine Learning Trends / Notable AI Models* database and analyses (epoch.ai). Documents the escalation of frontier training compute, dataset size, and cost across successive model generations — the empirical backbone for the 2023–2026 frontier-AI Red Queen example.\n- Hyperscaler and AI-lab public disclosures, 2024–2026 (earnings calls, capital-expenditure guidance, and widely reported financial commentary from the major cloud providers and leading AI labs). Basis for the qualified statements about escalating AI capex and loss-making frontier training; specific figures qualified or omitted where exact public values were not verified against primary filings."},{"path":"examples/frontier-ai-labs-training-race-2023-2026.md","content":"# Method in Action: The Frontier-AI Training Race (2023–2026)\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\nBetween 2023 and 2026 the leading frontier AI labs — OpenAI, Anthropic, Google DeepMind, Meta, xAI, and others — entered a textbook Red Queen race. Each must keep training ever-larger and better models, and keep buying more compute, simply to hold relative position while every rival does the same. The absolute capability of the frontier rises fast; the relative ordering among the top labs churns but never settles; and the cost of merely staying in the pack escalates every cycle. This walks the case through the skill's own six-step Process.\n\n## Step 1 — Diagnose\n\n- **Primary competitive investment:** training compute (GPUs/accelerators), the capital and data-center capacity to run them, and the scarce research/engineering talent to use them. Frontier training runs and the infrastructure behind them are the arms.\n- **Imitation speed:** roughly one model generation — on the order of months. When one lab ships a materially stronger model, rivals close much of the gap with a comparable release within a similar window, and capability benchmarks that one lab tops are frequently overtaken shortly after.\n- **Margin trend:** frontier model development has been heavily loss-making for the leading labs through this period. Revenue has grown quickly, but training and inference costs — and the capex commitments behind them — have grown at least as fast, so the leading pure-play frontier labs were reported to be spending well in excess of revenue.\n- **Are all major competitors investing at roughly the same rate?** Yes. Multiple large players are all committing very large sums to compute and data centers in the same window, and the biggest cloud/hyperscaler backers publicly raised their AI-related capital-expenditure guidance repeatedly across 2024–2025.\n\n## Step 2 — Confirm Red Queen\n\n- Absolute performance improving for all (Y): frontier model capability rose steeply and continuously across the field.\n- Relative share/position stable-but-contested (Y): no lab established a durable, uncontested lead; the \"best model\" title changed hands repeatedly and quickly.\n- Investment to maintain position growing (Y): the compute and capital required just to stay at the frontier increased each generation.\n- Margins thin/negative despite high activity (Y): frontier training remained deeply unprofitable for the leading pure-play labs despite rapid revenue growth.\n\nFour of four → **Red Queen confirmed.** All the running keeps each lab in roughly the same relative place while the treadmill speeds up.\n\n## Step 3 — Map imitation speed\n\nThe half-life of a frontier-capability advantage is short — measured in months, not years. A benchmark lead is routinely matched or exceeded by the next competitor release. And imitation speed is **accelerating** in some respects: the diffusion of methods (RLHF/RLAIF, mixture-of-experts, reasoning/inference-time compute, disti"},{"path":"examples/van-valen-1973-intel-vs-amd-1990-2010.md","content":"# Method in Action: Van Valen 1973 + Intel vs. AMD 1990–2010\n\n> *Example for the [red-queen-effect](../SKILL.md) skill.*\n\n**Leigh Van Valen** (1935–2010) was a University of Chicago evolutionary biologist and paleontologist. His 1973 paper \"A New Evolutionary Law\" was published in *Evolutionary Theory*, Volume 1 — a journal he founded himself after the mainstream evolutionary biology journals rejected the paper. The paper's central empirical finding was that the probability of extinction for a taxon was roughly constant across the lifespan of that taxon — well-adapted, long-surviving species did not have lower extinction rates than newly-evolved species.\n\nThe interpretation: in a co-evolutionary system, a species' environment is largely composed of other species. Every adaptation by one species changes the fitness landscape for others, which evolve counter-adaptations, which change the landscape back. The net result is a system where absolute fitness increases continuously but relative fitness — fitness *against the current field* — remains approximately constant. Van Valen named this dynamic after Lewis Carroll's Red Queen:\n\n> \"It takes all the running you can do, to keep in the same place.\"\n>\n> — Carroll, L. (1871). *Through the Looking-Glass.* Macmillan. Chapter 2.\n\nThe business application that best illustrates the Red Queen at industrial scale is the **Intel vs. AMD semiconductor arms race, 1990–2010**.\n\nBoth companies were bound by Moore's Law — the empirical regularity (not a physical law) that transistor density on integrated circuits roughly doubles every 18–24 months. Intel and AMD each invested massively to track Moore's Law: fabrication process improvements (from 800nm in 1990 to 32nm in 2010), microarchitecture redesigns, cache hierarchy innovations, instruction set extensions.\n\nThe results were extraordinary in absolute terms: a 2010 processor was roughly 1000× faster than a 1990 processor in single-thread performance. Both companies ran as fast as they could.\n\nThe competitive result: market share barely moved. Intel held 75–85% of the x86 desktop and server processor market throughout this period. AMD held 15–25%. The share distribution in 2010 looked almost identical to 1990, despite both companies having invested tens of billions of dollars in the race.\n\nWhere did the value go? To consumers — Moore's Law primarily produced consumer surplus: cheaper, faster personal computers that drove the internet era, the PC revolution, and ultimately mobile computing. The companies running the race were the mechanism through which technology value was transferred to buyers rather than retained as corporate profit.\n\nThe escape: neither Intel nor AMD escaped the Red Queen in this period. AMD eventually exited the manufacturing race (foundry to TSMC) and refocused on design — a partial vertical disintegration that reduced Red Queen exposure. Intel's escape vector came from a different direction: Xeon server processors for the cloud era, where swi"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with... Skill: Red Queen Effect Owner: deciqai Summary: Activate when: user says 'we keep investing but market share won't move,' 'why does nobody make money in this industry,' 'our competitor copied us again with... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:13:00.187Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/red-queen-effect.json) v1.0.4 | 2026-07-09T11:21:11.974Z","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2058,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T08:37:43.109Z","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-11T08:37:43.109Z","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-11T10:51:08.359Z","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"}]}}}