For 1-50 person operators running Claude, Claude Code, or Cursor (Claude-backed) on paid client work, the 19 May 2026 Karpathy hire at Anthropic is a vendor-trajectory signal operating on the 12-to-24-month time horizon (Karpathy's mandate is upstream pre-training research, not application-layer change), and the right operator-side response is the 70% concentration rule. List every monthly AI-stack line item, tag by underlying vendor (Anthropic / OpenAI / Microsoft / Google / other), compute the largest single-vendor share. Above 70% concentrated on Anthropic, add a deliberate secondary-lab subscription (ChatGPT Plus at $20/mo or Gemini Advanced at comparable pricing) as resilience against any future Anthropic-specific incident. Below 70%, continue concentrating and re-evaluate at the 45-day claim review. The hire does not change the daily workflow this week; it affects the medium-term improvement trajectory of the vibe-coding interface the operator is already using.

Operators register pillar piece on operator-side response to vendor-trajectory signal at the foundational layer. 45-day cadence calibrated to the typical 1-50p subscription billing cycle so the operator can re-evaluate the diversification decision inside a single review window. The 70% threshold is editorial synthesis based on observed operator-stack patterns in the OPS register (OPS-066 break-even math, OPS-068 consolidation pressure) and the practical observation that a single secondary subscription costs less than one billable hour per month for most operators. Sibling: AM-160 (enterprise treatment of the same hire as a procurement-template implication for multi-year platform commitments). Trigger conditions for status changes: (1) Anthropic shipping a pricing change, capacity constraint, or material capability regression inside the review window that affects 1-50p operator workflows (would harden the vendor-concentration risk reading and could move toward Partial on the stability framing); (2) Karpathy publicly departing Anthropic before the review (would weaken the momentum reading and potentially lower the threshold toward 60%); (3) a comparable hire announcement at OpenAI or Google with comparable name-recognition for code-and-developer-workflow research (would refine the multi-vendor diversification calculus and shift which secondary subscription is recommended); (4) Cursor, Windsurf, or another operator-facing AI-IDE vendor publicly switching their primary model away from Claude inside the review window (would weaken the primary-vendor concentration logic and shift which vendor sits at the top of most operators' line-by-line breakdowns); (5) Anthropic publishing observable progress on the Karpathy team's mandate within the review window (would harden the momentum reading and keep Holding without changing the 70% rule).