Hmbown Heat Metal
Make a tool or process increasingly uncomfortable to use until it is abandoned.
Overview
Heat Metal is interpreted here as a hybrid spell with a prototype execution model.
Canonical source: Heat Metal (spell)
Provider target: OpenClaw
When To Use
- You want to drive migration away from a deprecated tool, API, or workflow without hard-cutting access.
- Suspicious or abusive behavior should be progressively penalized without outright blocking.
- A gradual escalation of friction is more appropriate than an immediate ban or shutdown.
Workflow
- Identify the tool, path, or behavior you want to discourage.
- Design the friction curve: what discomfort increases over time and at what rate.
- Implement the progressive friction: latency injection, CAPTCHA escalation, cost increases, warning banners.
- Monitor adoption of the preferred alternative to confirm the friction is driving the intended migration.
- Set a sunset date: Heat Metal should eventually end in either full migration or hard deprecation.
Deliverables
- A friction curve specification: what changes, how fast, and what the escalation stages are.
- Migration metrics: how many users/systems have moved to the preferred alternative.
- A sunset timeline with hard cutoff criteria.
Guardrails
- Friction injection must be disclosed. Secretly making tools worse without explanation is a dark pattern.
- Heat Metal targets behavior, not people. Progressive friction applied to specific users as punishment crosses into harassment.
- Always provide a visible alternative. Making something painful to use without offering a better path is cruelty, not engineering.
Default Invocation
Use $heat-metal to design a progressive friction strategy that makes a deprecated tool, abusive pattern, or unwanted behavior increasingly uncomfortable until users migrate to the better alternative.