Datasets

The Rug-Event Log

A rug event is a provider-side change that forces unbudgeted work on everyone downstream — a repricing, a model deprecation, a terms change, an access cutoff, a tightened rate limit. You changed nothing; your costs, your compliance posture, or your running software changed anyway.

This log exists because the pain is the cadence, not any single change. Budgets, migration plans, and contracts get written as if provider terms hold still; this page is the dated, sourced record of how often they move underneath you.

5 events · v1 · updated 2026-07-30

Method

  • What counts: a discrete, dateable, provider-side change with a downstream cost or work consequence — repricings (including promo and intro-rate expiries), deprecations and end-of-life dates, terms-of-service and training-terms changes, access cutoffs, and rate-limit changes. Customer-side overspend stories and unconfirmed rumours do not qualify.
  • Where events come from: the weekly demand pass — a standing sweep of provider pricing pages, changelogs, deprecation schedules, and terms diffs — seeded by a 90-day internal inventory cataloged 22 Apr to 22 Jul 2026.
  • Dating rule: every row carries a date and a source. Events the source inventory records without a precise date are held out rather than given invented ones; pre-announced changes are logged under the date they take effect and marked as scheduled.
  • Cadence: updated as the weekly demand pass finds new events. Every revision is recorded in the changelog below.

The log

September 2026

DateProviderTypeEventSource
2026-09-01AnthropicRepriceScheduled at cataloging time: Sonnet 5 introductory pricing steps up 50% — promo-rate expiry as a repeating, predictable rug class.MenFem services commercial architecture memo, §4 rug inventory (2026-07-22)

August 2026

DateProviderTypeEventSource
2026-08-19AnthropicLimit changeScheduled at cataloging time: the Claude Code "50% boost" usage promo expires, dropping users onto a baseline that was tightened underneath the promo.MenFem services commercial architecture memo, §4 rug inventory (2026-07-22)

July 2026

DateProviderTypeEventSource
2026-07-07AnthropicTerms changeSafety-flag training carve-out took effect: the training-data opt-out gained an undisclosed exception for safety-flagged content — new terms risk for anyone relying on the opt-out.MenFem services commercial architecture memo, §4 rug inventory (2026-07-22)

June 2026

DateProviderTypeEventSource
2026-06-15AnthropicLimit changeClaude Code rate-limit/value gap escalated to a class action, Kahn v. Anthropic, filed this date; the source inventory flags the filing as unverified against the court docket.MenFem services commercial architecture memo, §4 rug inventory (2026-07-22)

April 2026

DateProviderTypeEventSource
2026-04-28AWS BedrockDeprecationClaude 3.7 reached end-of-life on Bedrock and broke running workloads — the same model carries different retirement dates on different rails, a standing per-model-per-region tracking tax on every Bedrock customer.MenFem services commercial architecture memo, §4 rug inventory (2026-07-22)

Cite this

The log is free to cite with attribution. Suggested citation:

MenFem Rug-Event Log, menfem.com/datasets/rugs, retrieved [date]

Replace [date] with the date you accessed this page.

Changelog

  • v1 — 2026-07-30 — initial 90-day backfill — the five explicitly dated events itemized in the source rug inventory (cataloging window 2026-04-22 → 2026-07-22, including two scheduled step-ups it records).