{"id":"e63418ac-3001-47f0-98e5-7ffdba069a95","entityType":"agent","slug":"clawhub-deciqai-strategic-commitment","name":"Strategic Commitment","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-strategic-commitment","canonicalPath":"/agent/clawhub-deciqai-strategic-commitment","generatedAt":"2026-10-11T16:00:33.838Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T13:35:57.626Z","emptyReason":null},"description":"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w... Skill: Strategic Commitment Owner: deciqai Summary: Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-24T22:16:02.937Z | user Add TSMC Arizona / AI-capex commitment race case (2020-2026) with founder takeaways; restore agent .json metadata footer v1.0.4 |","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:strategic-commitment","sourceUrl":"https://clawhub.ai/deciqai/strategic-commitment","homepage":"https://clawhub.ai/deciqai/skills/strategic-commitment","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/strategic-commitment","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/strategic-commitment","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T13:35:57.626Z","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-11T13:35:57.626Z","emptyReason":null},"stars":null,"forks":null,"downloads":1056,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T13:35:57.551Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T13:35:57.626Z","lastCrawledAt":"2026-10-11T13:35:57.551Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T13:35:57.551Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-24T22:16:02.937Z","changelog":"Add TSMC Arizona / AI-capex commitment race case (2020-2026) with founder takeaways; restore agent .json metadata footer","fileCount":6,"zipByteSize":12647},{"version":"1.0.4","createdAt":"2026-07-16T18:16:52.988Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/strategic-commitment.json)","fileCount":5,"zipByteSize":8828},{"version":"1.0.3","createdAt":"2026-07-08T11:20:17.881Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":8765},{"version":"1.0.2","createdAt":"2026-07-08T01:05:11.196Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":8747},{"version":"1.0.1","createdAt":"2026-07-07T22:33:52.375Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8703},{"version":"1.0.0","createdAt":"2026-07-02T15:17:24.779Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8774}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:strategic-commitment","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-strategic-commitment/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/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-11T16:00:33.835Z"}},"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-strategic-commitment/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-strategic-commitment/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-11T13:35:57.626Z","emptyReason":null},"readme":"Skill: Strategic Commitment\n\nOwner: deciqai\n\nSummary: Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-24T22:16:02.937Z | user\n\nAdd TSMC Arizona / AI-capex commitment race case (2020-2026) with founder takeaways; restore agent .json metadata footer\n\nv1.0.4 | 2026-07-16T18:16:52.988Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/strategic-commitment.json)\n\nv1.0.3 | 2026-07-08T11:20:17.881Z | 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:05:11.196Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T22:33:52.375Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-07-02T15:17:24.779Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 12647 bytes\n\nFiles: examples/amazon-everyday-low-price-commitment-1994-present.md (3186b), examples/tsmc-arizona-and-ai-capex-commitments-2020-2026.md (5920b), references/sources.md (2967b), skill-card.md (2987b), SKILL.md (8986b), _meta.json (139b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain. More: deciqai.com/c/strategic-commitment\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: `prisoners-dilemma` (diagnose defection traps) · `zero-sum-game` (confirm game structure) · `batna-zopa` (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n- Deciding whether to make a concentrated AI-era bet credible (capex, an all-in product pivot, a \"we're AI-first\" claim) — or auditing whether a rival's AI commitment is money-in-the-ground or a press release\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which device fits and why it changes payoffs — not just rhetoric.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Credibility Audit (CAVE)**, then design the **Commitment Device**.\n\n1. **State the threat precisely:** action · trigger · audience. Example: \"If X enters at price Y, we match within 30 days.\"\n2. **CAVE audit** (all four required or the commitment is theatrical):\n   - **C — Capability:** resources to execute?\n   - **A — Action taken:** irreversible action making retreat costly?\n   - **V — Visibility:** can the audience observe the commitment?\n   - **E — Enforcement:** third party (contract/regulator/reputation) penalizing non-execution?\n   Weakest element = design target.\n3. **Cost of retreat now:** if retreat is cheap, threat is not credible. Device must raise this cost until retreat is no longer dominant.\n4. **Choose device:** sunk-cost · reputation · third-party constraint · organizational lock-in.\n5. **Test post-commitment game tree:** re-draw payoffs — is follow-through non-dominated at execution? Stop-rule: if retreat still dominant, device is insufficient.\n6. **Rigidity risk:** (a) scenarios where follow-through becomes irrational? (b) exit clauses for material-change? (c) does conditionality undermine deterrence?\n\n### Output: Commitment Design Report\n\n```\nThreat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>\n```\n\n*→ Method in Action: [Amazon's Everyday Low Price Commitment (1994–present)](examples/amazon-everyday-low-price-commitment-1994-present.md)*\n*→ 2026 lens: [TSMC Arizona and the AI-capex commitment race (2020–2026)](examples/tsmc-arizona-and-ai-capex-commitments-2020-2026.md) — the money in the ground is the message.*\n\n## Commitment Packs\n\n**Entry Deterrence:** Irreversible capacity investment lowers marginal cost of price war. Without sunk cost, backward induction shows accommodation — threat incredible.\n**Negotiation:** Credibly narrow your BATNA. Walk-away must be verifiable or reputation-backed; unverifiable claims are cheap talk.\n**Brand Guarantees:** \"Lifetime warranty\" works when honoring costs are sunk into brand value. Startups need contract-based enforcement instead.\n\n## Applying It Well\n\n- Distinguish capability from credibility — commitment devices address credibility only; solve capability first.\n- Announcement without action is the most common error — change *payoff structure*, not rhetoric.\n- Rigidity is a real cost; design exit clauses for material-change conditions before committing.\n- Third-party enforcement is most reliable; reputation-based fails when audience is inattentive or future is heavily discounted.\n- Apply CAVE to the *opponent's* threats too — many are theatrical.\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 announced publicly — it's credible now\" | Raises reputational cost of retreat but not material payoff at execution. If retreat is still cheaper, opponents call the bluff. |\n| [D] \"Our track record proves we follow through\" | Track records work in *similar* situations. A new game with new stakes requires commitment re-established in that context. |\n| [D] \"The contract has a penalty clause\" | Only if penalty exceeds breach gain and enforcement is fast. Clauses set below defection gain are not commitment devices. |\n| [D] \"Burning bridges is too risky — we need flexibility\" | The cost of flexibility is reduced credibility. Requires explicit comparison, not a default preference for optionality. |\n| [D] \"Our CEO's word should be enough\" | CEO declarations carry reputational cost for the individual but no structural lock-in. Contracts and sunk investments are stronger. |\n| [D] \"The threat will deter — they're rational and know we'll fight\" | Rational opponents reason backward: if fighting is costly at execution, they will enter. Rationality is *why* commitment devices are necessary. |\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- Announcement only — no structural payoff change · CAVE not fully run\n- Post-commitment game tree not drawn — retreat may still be dominant\n- Rigidity risk not assessed · opponent's threat taken at face value without CAVE\n- Device depends on a single individual · penalty clause below defection gain\n\n## Verification\n\n- [ ] Threat stated precisely: action, trigger, audience named\n- [ ] CAVE applied: all four elements evaluated; weakest identified\n- [ ] Current cost of retreat quantified — if cheap, commitment is theatrical\n- [ ] Device type chosen with reasoning\n- [ ] Post-commitment game tree drawn: retreat no longer dominant at execution\n- [ ] Rigidity risk assessed: at least one costly follow-through scenario addressed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 233 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/strategic-commitment** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/strategic-commitment.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"strategic-commitment\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784931362937\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n- U.S. Department of Commerce (2024). CHIPS Incentives Award announcement for TSMC Arizona (April 2024): up to $6.6B in direct funding tied to milestone enforcement, alongside TSMC's expansion to three Arizona fabs (~$65B announced investment). https://www.commerce.gov/news/press-releases/2024/04/biden-harris-administration-announces-preliminary-terms-tsmc-expanded — a live CAVE-complete commitment: sunk cost + visibility + third-party enforcement.\n- Microsoft (2023). \"Microsoft and OpenAI extend partnership.\" Official Microsoft Blog, January 23, 2023. https://blogs.microsoft.com/blog/2023/01/23/microsoftandopenaiextendpartnership/ — the multi-year, multi-billion-dollar structure as an observable commitment device in the AI platform race.\n\nFile v1.0.5:examples/amazon-everyday-low-price-commitment-1994-present.md\n\n# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, A. & Nalebuff, B. (1991), *Thinking Strategically*; Schelling, T.C. (1960), *The Strategy of Conflict*; Profitero (2013), *The State of Online Retail Pricing*.\n\nFile v1.0.5:examples/tsmc-arizona-and-ai-capex-commitments-2020-2026.md\n\n# Method in Action: TSMC Arizona and the AI-Capex Commitment Race (2020–2026)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nThe 2020–2026 AI buildout produced the largest peacetime capital commitments in corporate history — and the clearest modern demonstrations of why commitment beats flexibility in games where counterparties act on what they believe you will do. Two linked cases: TSMC's Arizona fabs (a commitment made credible to governments and customers), and the hyperscalers' multi-year AI capex escalation (commitments aimed at rivals, suppliers, and the capital markets simultaneously). Run both through the Credibility Audit.\n\n### Case 1 — TSMC Arizona: making \"we will build outside Taiwan\" credible\n\n**Step 1 — State the commitment precisely.** Action: build and operate leading-edge fabs in Arizona. Trigger: US customers' and the US government's demand for supply-chain resilience. Audience: Washington (subsidy and export-policy decisions), US customers (Apple, Nvidia, AMD — \"can we count on non-Taiwan supply?\"), and rivals (Intel, Samsung) deciding their own capacity bets.\n\n**Step 2 — CAVE audit.** *Capability:* present — TSMC is the only firm that has repeatedly executed leading-edge fabs at scale. *Action taken:* irreversible — announced in 2020 and escalated in stages to a reported ~$65B across three Arizona fabs by 2024, with the first fab reaching volume production of 4nm-class chips in late 2024/early 2025; poured concrete and installed EUV tools cannot be un-spent. *Visibility:* maximal — presidential visits, CHIPS Act grant announcements, quarterly disclosure. *Enforcement:* CHIPS funding milestones and customer prepayment/agreement structures add third-party penalty for retreat. All four present — this is why the commitment moved policy and customer behavior where a press release would not have.\n\n**Step 3–4 — Cost of retreat and device.** Each escalation raised the cost of walking away (sunk cost + reputation with two governments + customer reliance). The device is classic **sunk-cost + third-party constraint**: the money in the ground is the message.\n\n**Step 5 — Post-commitment game tree.** Follow-through became non-dominated retreat: abandoning Arizona after CHIPS milestones and customer commitments would cost more (politically and commercially) than completing fabs whose standalone economics are worse than Taiwan's. That inversion is precisely what makes the audience believe.\n\n**Step 6 — Rigidity risk.** Real and priced in: higher US costs, staffing friction, the risk that demand shifts. TSMC kept conditionality narrow (phasing, tool-timing flexibility) without undermining the core signal.\n\n### Case 2 — Hyperscaler AI capex: commitment as deterrence in the model race\n\nThe 2024–2026 AI capex escalation — combined annual capital expenditure by the largest US hyperscalers reported in the hundreds of billions of dollars by 2025, with multi-year model-training and compute purchase agreements (e.g., Microsoft's multi-billion-dollar OpenAI partnership from 2019–2023 onward) — reads as a **CAVE-complete commitment aimed at three audiences at once**: rivals (\"we will not be outspent — entering the frontier race against us is expensive\"), suppliers (\"build the capacity; the demand is contracted\"), and talent/markets (\"this is a decade bet, not a feature\"). The *Action-taken* element is the disclosed capex itself; *Enforcement* is quarterly earnings scrutiny — a CFO who guides capex up and then retreats pays a visible price. Contrast the counter-case: enterprises that ran dozens of hedged AI pilots (\"keep options open\") signaled exactly the opposite, and their pilots were treated accordingly by vendors, talent, and their own organizations — flexibility read as absence of intent. The same structural point [definite-optimism](../definite-optimism/SKILL.md) makes about plans applies here to signals: optionality is illegible; commitment is information.\n\n**The founder-scale version of the audit.** The mechanism is size-independent — what changes is the device menu:\n\n**Founder takeaway (startup):** Your \"we're all-in on X\" claim is theatrical until it passes CAVE. Investors, candidates, and early customers read *Action-taken*, not vision slides: what did you irreversibly spend, kill, or turn down? Killing your fallback product line, publishing a falsifiable roadmap, taking a niche-exclusive contract — each is a small Arizona. If your deck says focus and your burn says hedging, sophisticated audiences believe the burn.\n\n**Founder takeaway (SMB):** Commitment devices are how a small player makes a big player's threat irrelevant — a 3-year lease in the neighborhood you serve, a published service guarantee with teeth (refund policy = enforcement), a niche you name publicly. And run CAVE in reverse on competitors: the chain announcing \"we'll match any local price\" has Capability but often no Action-taken — check whether their threat has concrete cost behind it before you surrender margin.\n\n*Sources: TSMC Arizona expansion to three fabs and ~$65B announced investment: TSMC press releases and April 2024 U.S. Department of Commerce CHIPS announcement (commerce.gov; up to $6.6B in direct funding), as widely reported; first Arizona fab volume production of 4nm-class chips in late 2024/early 2025 per TSMC and press reporting. Hyperscaler AI capital expenditure levels 2024–2025: company quarterly reports and earnings guidance as widely reported; figures are order-of-magnitude and vary by fiscal year and firm. Microsoft–OpenAI multi-year, multi-billion-dollar partnership (2019, 2021, January 2023): Microsoft official blog announcements. Commitment theory: Schelling, T. (1960). The Strategy of Conflict. Harvard University Press — see this skill's primary sources. Precise private contract terms are not public; characterizations are as reported.*\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nStrategic Commitment helps agents coach users through making threats, promises, and strategic bets credible by changing payoff structures and auditing capability, action, visibility, enforcement, and rigidity risk.\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\nBusiness operators, founders, negotiators, and strategy advisors use this skill to assess whether a threat, promise, deterrence posture, or strategic bet is credible and to design commitment devices that make follow-through rational.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can be used to plan coercive, retaliatory, unlawful, or harmful commitments.\n\nMitigation: Use it only for lawful and ethical business commitments, and add legality and harm checks before acting on any recommendation.\n\nRisk: A recommendation may overvalue credibility and underweight rigidity when conditions change.\n\nMitigation: Assess material-change scenarios, exit clauses, and whether lock-in creates more downside than credibility gain before committing.\n\n## Reference(s):\n\n- [Strategic Commitment skill page](https://clawhub.ai/deciqai/skills/strategic-commitment)\n- [Primary sources for strategic commitment](references/sources.md)\n- [Amazon everyday low price commitment example](examples/amazon-everyday-low-price-commitment-1994-present.md)\n- [TSMC Arizona and AI capex commitment example](examples/tsmc-arizona-and-ai-capex-commitments-2020-2026.md)\n- [The Strategy of Conflict](https://www.hup.harvard.edu/books/9780674840317)\n- [Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games](https://doi.org/10.1007/BF01766400)\n- [Reputation and Imperfect Information](https://doi.org/10.1016/0022-0531(82)90030-8)\n- [Thomas C. Schelling and Robert J. Aumann scientific background](https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/)\n- [U.S. Department of Commerce TSMC Arizona CHIPS announcement](https://www.commerce.gov/news/press-releases/2024/04/biden-harris-administration-announces-preliminary-terms-tsmc-expanded)\n- [Microsoft and OpenAI extend partnership](https://blogs.microsoft.com/blog/2023/01/23/microsoftandopenaiextendpartnership/)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Analysis]\n\n**Output Format:** [Markdown coaching questions and commitment design reports]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May pause for user input in novice coaching mode before producing the final commitment design report.]\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: 5 files, 8828 bytes\n\nFiles: examples/amazon-everyday-low-price-commitment-1994-present.md (3186b), references/sources.md (2214b), skill-card.md (2803b), SKILL.md (8591b), _meta.json (139b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain. More: deciqai.com/c/strategic-commitment\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: `prisoners-dilemma` (diagnose defection traps) · `zero-sum-game` (confirm game structure) · `batna-zopa` (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which device fits and why it changes payoffs — not just rhetoric.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Credibility Audit (CAVE)**, then design the **Commitment Device**.\n\n1. **State the threat precisely:** action · trigger · audience. Example: \"If X enters at price Y, we match within 30 days.\"\n2. **CAVE audit** (all four required or the commitment is theatrical):\n   - **C — Capability:** resources to execute?\n   - **A — Action taken:** irreversible action making retreat costly?\n   - **V — Visibility:** can the audience observe the commitment?\n   - **E — Enforcement:** third party (contract/regulator/reputation) penalizing non-execution?\n   Weakest element = design target.\n3. **Cost of retreat now:** if retreat is cheap, threat is not credible. Device must raise this cost until retreat is no longer dominant.\n4. **Choose device:** sunk-cost · reputation · third-party constraint · organizational lock-in.\n5. **Test post-commitment game tree:** re-draw payoffs — is follow-through non-dominated at execution? Stop-rule: if retreat still dominant, device is insufficient.\n6. **Rigidity risk:** (a) scenarios where follow-through becomes irrational? (b) exit clauses for material-change? (c) does conditionality undermine deterrence?\n\n### Output: Commitment Design Report\n\n```\nThreat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>\n```\n\n*→ Method in Action: [Amazon's Everyday Low Price Commitment (1994–present)](examples/amazon-everyday-low-price-commitment-1994-present.md)*\n\n## Commitment Packs\n\n**Entry Deterrence:** Irreversible capacity investment lowers marginal cost of price war. Without sunk cost, backward induction shows accommodation — threat incredible.\n**Negotiation:** Credibly narrow your BATNA. Walk-away must be verifiable or reputation-backed; unverifiable claims are cheap talk.\n**Brand Guarantees:** \"Lifetime warranty\" works when honoring costs are sunk into brand value. Startups need contract-based enforcement instead.\n\n## Applying It Well\n\n- Distinguish capability from credibility — commitment devices address credibility only; solve capability first.\n- Announcement without action is the most common error — change *payoff structure*, not rhetoric.\n- Rigidity is a real cost; design exit clauses for material-change conditions before committing.\n- Third-party enforcement is most reliable; reputation-based fails when audience is inattentive or future is heavily discounted.\n- Apply CAVE to the *opponent's* threats too — many are theatrical.\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 announced publicly — it's credible now\" | Raises reputational cost of retreat but not material payoff at execution. If retreat is still cheaper, opponents call the bluff. |\n| [D] \"Our track record proves we follow through\" | Track records work in *similar* situations. A new game with new stakes requires commitment re-established in that context. |\n| [D] \"The contract has a penalty clause\" | Only if penalty exceeds breach gain and enforcement is fast. Clauses set below defection gain are not commitment devices. |\n| [D] \"Burning bridges is too risky — we need flexibility\" | The cost of flexibility is reduced credibility. Requires explicit comparison, not a default preference for optionality. |\n| [D] \"Our CEO's word should be enough\" | CEO declarations carry reputational cost for the individual but no structural lock-in. Contracts and sunk investments are stronger. |\n| [D] \"The threat will deter — they're rational and know we'll fight\" | Rational opponents reason backward: if fighting is costly at execution, they will enter. Rationality is *why* commitment devices are necessary. |\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- Announcement only — no structural payoff change · CAVE not fully run\n- Post-commitment game tree not drawn — retreat may still be dominant\n- Rigidity risk not assessed · opponent's threat taken at face value without CAVE\n- Device depends on a single individual · penalty clause below defection gain\n\n## Verification\n\n- [ ] Threat stated precisely: action, trigger, audience named\n- [ ] CAVE applied: all four elements evaluated; weakest identified\n- [ ] Current cost of retreat quantified — if cheap, commitment is theatrical\n- [ ] Device type chosen with reasoning\n- [ ] Post-commitment game tree drawn: retreat no longer dominant at execution\n- [ ] Rigidity risk assessed: at least one costly follow-through scenario addressed\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/strategic-commitment** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/strategic-commitment.json*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"strategic-commitment\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1784225812988\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n\nFile v1.0.4:examples/amazon-everyday-low-price-commitment-1994-present.md\n\n# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, A. & Nalebuff, B. (1991), *Thinking Strategically*; Schelling, T.C. (1960), *The Strategy of Conflict*; Profitero (2013), *The State of Online Retail Pricing*.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nGuides an agent through assessing and designing credible strategic commitments, threats, or promises by changing payoff structures rather than relying on rhetoric. <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 business strategy agents use this skill to evaluate whether a threat or promise is credible and to produce a structured commitment design report. It is intended for decision support in negotiation, deterrence, counterparty analysis, and strategic planning. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can influence consequential strategy and negotiation decisions about credible commitments and threats. <br>\nMitigation: Use outputs as decision support and require appropriate legal, financial, ethical, or executive review before acting on high-impact recommendations. <br>\nRisk: A commitment device can create harmful rigidity if conditions change after the commitment is made. <br>\nMitigation: Review the skill's rigidity-risk and exit-clause analysis before implementation, especially for long-lived or high-cost commitments. <br>\n\n\n## Reference(s): <br>\n- [Strategic Commitment ClawHub Page](https://clawhub.ai/deciqai/skills/strategic-commitment) <br>\n- [Sources - strategic-commitment](references/sources.md) <br>\n- [Amazon's Everyday Low Price Commitment Example](examples/amazon-everyday-low-price-commitment-1994-present.md) <br>\n- [Schelling, The Strategy of Conflict](https://www.hup.harvard.edu/books/9780674840317) <br>\n- [Selten, Reexamination of the Perfectness Concept for Equilibrium Points](https://doi.org/10.1007/BF01766400) <br>\n- [Kreps and Wilson, Reputation and Imperfect Information](https://doi.org/10.1016/0022-0531(82)90030-8) <br>\n- [Nobel Prize Scientific Background for Schelling and Aumann](https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown commitment design report with structured fields and, when needed, staged coaching questions.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May stop for user input during novice coaching before producing the final report.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 5 files, 8765 bytes\n\nFiles: examples/amazon-everyday-low-price-commitment-1994-present.md (3186b), references/sources.md (2214b), skill-card.md (2701b), SKILL.md (8439b), _meta.json (139b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain.\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: `prisoners-dilemma` (diagnose defection traps) · `zero-sum-game` (confirm game structure) · `batna-zopa` (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which device fits and why it changes payoffs — not just rhetoric.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Credibility Audit (CAVE)**, then design the **Commitment Device**.\n\n1. **State the threat precisely:** action · trigger · audience. Example: \"If X enters at price Y, we match within 30 days.\"\n2. **CAVE audit** (all four required or the commitment is theatrical):\n   - **C — Capability:** resources to execute?\n   - **A — Action taken:** irreversible action making retreat costly?\n   - **V — Visibility:** can the audience observe the commitment?\n   - **E — Enforcement:** third party (contract/regulator/reputation) penalizing non-execution?\n   Weakest element = design target.\n3. **Cost of retreat now:** if retreat is cheap, threat is not credible. Device must raise this cost until retreat is no longer dominant.\n4. **Choose device:** sunk-cost · reputation · third-party constraint · organizational lock-in.\n5. **Test post-commitment game tree:** re-draw payoffs — is follow-through non-dominated at execution? Stop-rule: if retreat still dominant, device is insufficient.\n6. **Rigidity risk:** (a) scenarios where follow-through becomes irrational? (b) exit clauses for material-change? (c) does conditionality undermine deterrence?\n\n### Output: Commitment Design Report\n\n```\nThreat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>\n```\n\n*→ Method in Action: [Amazon's Everyday Low Price Commitment (1994–present)](examples/amazon-everyday-low-price-commitment-1994-present.md)*\n\n## Commitment Packs\n\n**Entry Deterrence:** Irreversible capacity investment lowers marginal cost of price war. Without sunk cost, backward induction shows accommodation — threat incredible.\n**Negotiation:** Credibly narrow your BATNA. Walk-away must be verifiable or reputation-backed; unverifiable claims are cheap talk.\n**Brand Guarantees:** \"Lifetime warranty\" works when honoring costs are sunk into brand value. Startups need contract-based enforcement instead.\n\n## Applying It Well\n\n- Distinguish capability from credibility — commitment devices address credibility only; solve capability first.\n- Announcement without action is the most common error — change *payoff structure*, not rhetoric.\n- Rigidity is a real cost; design exit clauses for material-change conditions before committing.\n- Third-party enforcement is most reliable; reputation-based fails when audience is inattentive or future is heavily discounted.\n- Apply CAVE to the *opponent's* threats too — many are theatrical.\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 announced publicly — it's credible now\" | Raises reputational cost of retreat but not material payoff at execution. If retreat is still cheaper, opponents call the bluff. |\n| [D] \"Our track record proves we follow through\" | Track records work in *similar* situations. A new game with new stakes requires commitment re-established in that context. |\n| [D] \"The contract has a penalty clause\" | Only if penalty exceeds breach gain and enforcement is fast. Clauses set below defection gain are not commitment devices. |\n| [D] \"Burning bridges is too risky — we need flexibility\" | The cost of flexibility is reduced credibility. Requires explicit comparison, not a default preference for optionality. |\n| [D] \"Our CEO's word should be enough\" | CEO declarations carry reputational cost for the individual but no structural lock-in. Contracts and sunk investments are stronger. |\n| [D] \"The threat will deter — they're rational and know we'll fight\" | Rational opponents reason backward: if fighting is costly at execution, they will enter. Rationality is *why* commitment devices are necessary. |\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- Announcement only — no structural payoff change · CAVE not fully run\n- Post-commitment game tree not drawn — retreat may still be dominant\n- Rigidity risk not assessed · opponent's threat taken at face value without CAVE\n- Device depends on a single individual · penalty clause below defection gain\n\n## Verification\n\n- [ ] Threat stated precisely: action, trigger, audience named\n- [ ] CAVE applied: all four elements evaluated; weakest identified\n- [ ] Current cost of retreat quantified — if cheap, commitment is theatrical\n- [ ] Device type chosen with reasoning\n- [ ] Post-commitment game tree drawn: retreat no longer dominant at execution\n- [ ] Rigidity risk assessed: at least one costly follow-through scenario addressed\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/strategic-commitment** · ⭐ 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\": \"strategic-commitment\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783509617881\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n\nFile v1.0.3:examples/amazon-everyday-low-price-commitment-1994-present.md\n\n# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, A. & Nalebuff, B. (1991), *Thinking Strategically*; Schelling, T.C. (1960), *The Strategy of Conflict*; Profitero (2013), *The State of Online Retail Pricing*.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nHelps agents coach users through credible strategic commitments by auditing whether a threat or promise changes payoffs enough to make follow-through rational. <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 strategists, negotiators, and operators use this skill to evaluate whether a threat, promise, pledge, or deterrence posture is credible and to design commitment devices such as sunk costs, third-party constraints, reputation mechanisms, or organizational lock-in. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Outputs may influence real business commitments, deterrence moves, contracts, or competitive behavior. <br>\nMitigation: Treat outputs as strategy analysis only and review any real-world commitment for legal, ethical, reputational, operational, and reversibility risks before acting. <br>\nRisk: The skill is designed for credibility problems and can be misapplied when the issue is capability or when lock-in would create excessive rigidity. <br>\nMitigation: Confirm the user can execute the commitment, run the CAVE audit, and assess rigidity and exit clauses before recommending action. <br>\n\n\n## Reference(s): <br>\n- [Sources - strategic-commitment](references/sources.md) <br>\n- [Amazon's Everyday Low Price Commitment example](examples/amazon-everyday-low-price-commitment-1994-present.md) <br>\n- [Schelling, The Strategy of Conflict](https://www.hup.harvard.edu/books/9780674840317) <br>\n- [Selten, Reexamination of the Perfectness Concept for Equilibrium Points](https://doi.org/10.1007/BF01766400) <br>\n- [Kreps and Wilson, Reputation and Imperfect Information](https://doi.org/10.1016/0022-0531(82)90030-8) <br>\n- [Nobel Prize Scientific Background: Schelling and Aumann](https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance, Analysis] <br>\n**Output Format:** [Markdown report with structured coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Novice coaching mode may pause for user input; the final output is a Commitment Design Report.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 5 files, 8747 bytes\n\nFiles: examples/amazon-everyday-low-price-commitment-1994-present.md (3186b), references/sources.md (2214b), skill-card.md (2599b), SKILL.md (8549b), _meta.json (139b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain.\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: `prisoners-dilemma` (diagnose defection traps) · `zero-sum-game` (confirm game structure) · `batna-zopa` (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which device fits and why it changes payoffs — not just rhetoric.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Credibility Audit (CAVE)**, then design the **Commitment Device**.\n\n1. **State the threat precisely:** action · trigger · audience. Example: \"If X enters at price Y, we match within 30 days.\"\n2. **CAVE audit** (all four required or the commitment is theatrical):\n   - **C — Capability:** resources to execute?\n   - **A — Action taken:** irreversible action making retreat costly?\n   - **V — Visibility:** can the audience observe the commitment?\n   - **E — Enforcement:** third party (contract/regulator/reputation) penalizing non-execution?\n   Weakest element = design target.\n3. **Cost of retreat now:** if retreat is cheap, threat is not credible. Device must raise this cost until retreat is no longer dominant.\n4. **Choose device:** sunk-cost · reputation · third-party constraint · organizational lock-in.\n5. **Test post-commitment game tree:** re-draw payoffs — is follow-through non-dominated at execution? Stop-rule: if retreat still dominant, device is insufficient.\n6. **Rigidity risk:** (a) scenarios where follow-through becomes irrational? (b) exit clauses for material-change? (c) does conditionality undermine deterrence?\n\n### Output: Commitment Design Report\n\n```\nThreat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>\n```\n\n*→ Method in Action: [Amazon's Everyday Low Price Commitment (1994–present)](examples/amazon-everyday-low-price-commitment-1994-present.md)*\n\n## Commitment Packs\n\n**Entry Deterrence:** Irreversible capacity investment lowers marginal cost of price war. Without sunk cost, backward induction shows accommodation — threat incredible.\n**Negotiation:** Credibly narrow your BATNA. Walk-away must be verifiable or reputation-backed; unverifiable claims are cheap talk.\n**Brand Guarantees:** \"Lifetime warranty\" works when honoring costs are sunk into brand value. Startups need contract-based enforcement instead.\n\n## Applying It Well\n\n- Distinguish capability from credibility — commitment devices address credibility only; solve capability first.\n- Announcement without action is the most common error — change *payoff structure*, not rhetoric.\n- Rigidity is a real cost; design exit clauses for material-change conditions before committing.\n- Third-party enforcement is most reliable; reputation-based fails when audience is inattentive or future is heavily discounted.\n- Apply CAVE to the *opponent's* threats too — many are theatrical.\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 announced publicly — it's credible now\" | Raises reputational cost of retreat but not material payoff at execution. If retreat is still cheaper, opponents call the bluff. |\n| [D] \"Our track record proves we follow through\" | Track records work in *similar* situations. A new game with new stakes requires commitment re-established in that context. |\n| [D] \"The contract has a penalty clause\" | Only if penalty exceeds breach gain and enforcement is fast. Clauses set below defection gain are not commitment devices. |\n| [D] \"Burning bridges is too risky — we need flexibility\" | The cost of flexibility is reduced credibility. Requires explicit comparison, not a default preference for optionality. |\n| [D] \"Our CEO's word should be enough\" | CEO declarations carry reputational cost for the individual but no structural lock-in. Contracts and sunk investments are stronger. |\n| [D] \"The threat will deter — they're rational and know we'll fight\" | Rational opponents reason backward: if fighting is costly at execution, they will enter. Rationality is *why* commitment devices are necessary. |\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- Announcement only — no structural payoff change · CAVE not fully run\n- Post-commitment game tree not drawn — retreat may still be dominant\n- Rigidity risk not assessed · opponent's threat taken at face value without CAVE\n- Device depends on a single individual · penalty clause below defection gain\n\n## Verification\n\n- [ ] Threat stated precisely: action, trigger, audience named\n- [ ] CAVE applied: all four elements evaluated; weakest identified\n- [ ] Current cost of retreat quantified — if cheap, commitment is theatrical\n- [ ] Device type chosen with reasoning\n- [ ] Post-commitment game tree drawn: retreat no longer dominant at execution\n- [ ] Rigidity risk assessed: at least one costly follow-through scenario addressed\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/strategic-commitment?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=strategic-commitment** · ⭐ 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\": \"strategic-commitment\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783472711196\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n\nFile v1.0.2:examples/amazon-everyday-low-price-commitment-1994-present.md\n\n# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, A. & Nalebuff, B. (1991), *Thinking Strategically*; Schelling, T.C. (1960), *The Strategy of Conflict*; Profitero (2013), *The State of Online Retail Pricing*.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nStrategic Commitment helps agents analyze discounted threats or promises by auditing credibility and designing commitment devices that change payoff structure. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external advisors, and AI agents use this skill to evaluate whether threats, promises, deterrence postures, or negotiation commitments are credible and to produce a structured commitment design report. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Strategic commitment guidance could be misused to intimidate, entrap, threaten, harass, extort, or pressure people. <br>\nMitigation: Use only for lawful, transparent, consensual commitments such as contracts, guarantees, planning, or dispute resolution. <br>\nRisk: A poorly designed commitment can create costly rigidity or make follow-through irrational when conditions change. <br>\nMitigation: Run the CAVE audit, test post-commitment payoffs, and define material-change exit clauses before relying on a commitment device. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/strategic-commitment) <br>\n- [Sources - strategic-commitment](references/sources.md) <br>\n- [Amazon Everyday Low Price Commitment Example](examples/amazon-everyday-low-price-commitment-1994-present.md) <br>\n- [Schelling, The Strategy of Conflict](https://www.hup.harvard.edu/books/9780674840317) <br>\n- [Selten, Reexamination of the Perfectness Concept](https://doi.org/10.1007/BF01766400) <br>\n- [Kreps and Wilson, Reputation and Imperfect Information](https://doi.org/10.1016/0022-0531(82)90030-8) <br>\n- [Nobel Prize Committee Scientific Background](https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Guidance, Markdown] <br>\n**Output Format:** [Markdown commitment design report] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause for user input in coach mode; no code execution or external tools are required.] <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, 8703 bytes\n\nFiles: examples/amazon-everyday-low-price-commitment-1994-present.md (3186b), references/sources.md (2214b), skill-card.md (2749b), SKILL.md (8369b), _meta.json (139b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain.\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: [`prisoners-dilemma`](../prisoners-dilemma/SKILL.md) (diagnose defection traps) · [`zero-sum-game`](../zero-sum-game/SKILL.md) (confirm game structure) · [`batna-zopa`](../batna-zopa/SKILL.md) (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which device fits and why it changes payoffs — not just rhetoric.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Credibility Audit (CAVE)**, then design the **Commitment Device**.\n\n1. **State the threat precisely:** action · trigger · audience. Example: \"If X enters at price Y, we match within 30 days.\"\n2. **CAVE audit** (all four required or the commitment is theatrical):\n   - **C — Capability:** resources to execute?\n   - **A — Action taken:** irreversible action making retreat costly?\n   - **V — Visibility:** can the audience observe the commitment?\n   - **E — Enforcement:** third party (contract/regulator/reputation) penalizing non-execution?\n   Weakest element = design target.\n3. **Cost of retreat now:** if retreat is cheap, threat is not credible. Device must raise this cost until retreat is no longer dominant.\n4. **Choose device:** sunk-cost · reputation · third-party constraint · organizational lock-in.\n5. **Test post-commitment game tree:** re-draw payoffs — is follow-through non-dominated at execution? Stop-rule: if retreat still dominant, device is insufficient.\n6. **Rigidity risk:** (a) scenarios where follow-through becomes irrational? (b) exit clauses for material-change? (c) does conditionality undermine deterrence?\n\n### Output: Commitment Design Report\n\n```\nThreat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>\n```\n\n*→ Method in Action: [Amazon's Everyday Low Price Commitment (1994–present)](examples/amazon-everyday-low-price-commitment-1994-present.md)*\n\n## Commitment Packs\n\n**Entry Deterrence:** Irreversible capacity investment lowers marginal cost of price war. Without sunk cost, backward induction shows accommodation — threat incredible.\n**Negotiation:** Credibly narrow your BATNA. Walk-away must be verifiable or reputation-backed; unverifiable claims are cheap talk.\n**Brand Guarantees:** \"Lifetime warranty\" works when honoring costs are sunk into brand value. Startups need contract-based enforcement instead.\n\n## Applying It Well\n\n- Distinguish capability from credibility — commitment devices address credibility only; solve capability first.\n- Announcement without action is the most common error — change *payoff structure*, not rhetoric.\n- Rigidity is a real cost; design exit clauses for material-change conditions before committing.\n- Third-party enforcement is most reliable; reputation-based fails when audience is inattentive or future is heavily discounted.\n- Apply CAVE to the *opponent's* threats too — many are theatrical.\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 announced publicly — it's credible now\" | Raises reputational cost of retreat but not material payoff at execution. If retreat is still cheaper, opponents call the bluff. |\n| [D] \"Our track record proves we follow through\" | Track records work in *similar* situations. A new game with new stakes requires commitment re-established in that context. |\n| [D] \"The contract has a penalty clause\" | Only if penalty exceeds breach gain and enforcement is fast. Clauses set below defection gain are not commitment devices. |\n| [D] \"Burning bridges is too risky — we need flexibility\" | The cost of flexibility is reduced credibility. Requires explicit comparison, not a default preference for optionality. |\n| [D] \"Our CEO's word should be enough\" | CEO declarations carry reputational cost for the individual but no structural lock-in. Contracts and sunk investments are stronger. |\n| [D] \"The threat will deter — they're rational and know we'll fight\" | Rational opponents reason backward: if fighting is costly at execution, they will enter. Rationality is *why* commitment devices are necessary. |\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- Announcement only — no structural payoff change · CAVE not fully run\n- Post-commitment game tree not drawn — retreat may still be dominant\n- Rigidity risk not assessed · opponent's threat taken at face value without CAVE\n- Device depends on a single individual · penalty clause below defection gain\n\n## Verification\n\n- [ ] Threat stated precisely: action, trigger, audience named\n- [ ] CAVE applied: all four elements evaluated; weakest identified\n- [ ] Current cost of retreat quantified — if cheap, commitment is theatrical\n- [ ] Device type chosen with reasoning\n- [ ] Post-commitment game tree drawn: retreat no longer dominant at execution\n- [ ] Rigidity risk assessed: at least one costly follow-through scenario addressed\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\": \"strategic-commitment\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783463632375\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n\nFile v1.0.1:examples/amazon-everyday-low-price-commitment-1994-present.md\n\n# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, A. & Nalebuff, B. (1991), *Thinking Strategically*; Schelling, T.C. (1960), *The Strategy of Conflict*; Profitero (2013), *The State of Online Retail Pricing*.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nStrategic Commitment helps agents analyze threats, promises, and deterrence problems by testing whether a commitment changes payoff structure enough to make follow-through credible. <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-focused agents use this skill to assess whether a threat, promise, deterrence posture, or negotiation move is credible. It guides users through a CAVE audit, commitment device selection, payoff testing, and rigidity-risk review. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Strategic commitment analysis could be misused to plan intimidation, retaliation, harassment, extortion, unlawful collusion, or harmful threats. <br>\nMitigation: Use it only for lawful and ethical commitments such as contracts, service levels, compliance-backed promises, and business planning; reject harmful threat-planning requests. <br>\nRisk: Commitment devices can create rigidity when circumstances change and follow-through becomes costly or irrational. <br>\nMitigation: Assess rigidity risk, material-change scenarios, exit clauses, and whether conditionality weakens deterrence before recommending a commitment. <br>\n\n\n## Reference(s): <br>\n- [Sources - strategic-commitment](references/sources.md) <br>\n- [Schelling, The Strategy of Conflict](https://www.hup.harvard.edu/books/9780674840317) <br>\n- [Selten, Reexamination of the Perfectness Concept for Equilibrium Points](https://doi.org/10.1007/BF01766400) <br>\n- [Kreps and Wilson, Reputation and Imperfect Information](https://doi.org/10.1016/0022-0531(82)90030-8) <br>\n- [Nobel Prize Scientific Background: Schelling and Aumann](https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/) <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/strategic-commitment) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown commitment design report with structured analysis fields] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include step-by-step coaching questions, CAVE audit results, payoff analysis, rigidity risks, and 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, 8774 bytes\n\nFiles: examples/amazon-everyday-low-price-commitment-1994-present.md (3186b), references/sources.md (2214b), skill-card.md (2850b), SKILL.md (8369b), _meta.json (139b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain.\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: [`prisoners-dilemma`](../prisoners-dilemma/SKILL.md) (diagnose defection traps) · [`zero-sum-game`](../zero-sum-game/SKILL.md) (confirm game structure) · [`batna-zopa`](../batna-zopa/SKILL.md) (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which device fits and why it changes payoffs — not just rhetoric.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Credibility Audit (CAVE)**, then design the **Commitment Device**.\n\n1. **State the threat precisely:** action · trigger · audience. Example: \"If X enters at price Y, we match within 30 days.\"\n2. **CAVE audit** (all four required or the commitment is theatrical):\n   - **C — Capability:** resources to execute?\n   - **A — Action taken:** irreversible action making retreat costly?\n   - **V — Visibility:** can the audience observe the commitment?\n   - **E — Enforcement:** third party (contract/regulator/reputation) penalizing non-execution?\n   Weakest element = design target.\n3. **Cost of retreat now:** if retreat is cheap, threat is not credible. Device must raise this cost until retreat is no longer dominant.\n4. **Choose device:** sunk-cost · reputation · third-party constraint · organizational lock-in.\n5. **Test post-commitment game tree:** re-draw payoffs — is follow-through non-dominated at execution? Stop-rule: if retreat still dominant, device is insufficient.\n6. **Rigidity risk:** (a) scenarios where follow-through becomes irrational? (b) exit clauses for material-change? (c) does conditionality undermine deterrence?\n\n### Output: Commitment Design Report\n\n```\nThreat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>\n```\n\n*→ Method in Action: [Amazon's Everyday Low Price Commitment (1994–present)](examples/amazon-everyday-low-price-commitment-1994-present.md)*\n\n## Commitment Packs\n\n**Entry Deterrence:** Irreversible capacity investment lowers marginal cost of price war. Without sunk cost, backward induction shows accommodation — threat incredible.\n**Negotiation:** Credibly narrow your BATNA. Walk-away must be verifiable or reputation-backed; unverifiable claims are cheap talk.\n**Brand Guarantees:** \"Lifetime warranty\" works when honoring costs are sunk into brand value. Startups need contract-based enforcement instead.\n\n## Applying It Well\n\n- Distinguish capability from credibility — commitment devices address credibility only; solve capability first.\n- Announcement without action is the most common error — change *payoff structure*, not rhetoric.\n- Rigidity is a real cost; design exit clauses for material-change conditions before committing.\n- Third-party enforcement is most reliable; reputation-based fails when audience is inattentive or future is heavily discounted.\n- Apply CAVE to the *opponent's* threats too — many are theatrical.\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 announced publicly — it's credible now\" | Raises reputational cost of retreat but not material payoff at execution. If retreat is still cheaper, opponents call the bluff. |\n| [D] \"Our track record proves we follow through\" | Track records work in *similar* situations. A new game with new stakes requires commitment re-established in that context. |\n| [D] \"The contract has a penalty clause\" | Only if penalty exceeds breach gain and enforcement is fast. Clauses set below defection gain are not commitment devices. |\n| [D] \"Burning bridges is too risky — we need flexibility\" | The cost of flexibility is reduced credibility. Requires explicit comparison, not a default preference for optionality. |\n| [D] \"Our CEO's word should be enough\" | CEO declarations carry reputational cost for the individual but no structural lock-in. Contracts and sunk investments are stronger. |\n| [D] \"The threat will deter — they're rational and know we'll fight\" | Rational opponents reason backward: if fighting is costly at execution, they will enter. Rationality is *why* commitment devices are necessary. |\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- Announcement only — no structural payoff change · CAVE not fully run\n- Post-commitment game tree not drawn — retreat may still be dominant\n- Rigidity risk not assessed · opponent's threat taken at face value without CAVE\n- Device depends on a single individual · penalty clause below defection gain\n\n## Verification\n\n- [ ] Threat stated precisely: action, trigger, audience named\n- [ ] CAVE applied: all four elements evaluated; weakest identified\n- [ ] Current cost of retreat quantified — if cheap, commitment is theatrical\n- [ ] Device type chosen with reasoning\n- [ ] Post-commitment game tree drawn: retreat no longer dominant at execution\n- [ ] Rigidity risk assessed: at least one costly follow-through scenario addressed\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\": \"strategic-commitment\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1783005444779\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n\nFile v1.0.0:examples/amazon-everyday-low-price-commitment-1994-present.md\n\n# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, A. & Nalebuff, B. (1991), *Thinking Strategically*; Schelling, T.C. (1960), *The Strategy of Conflict*; Profitero (2013), *The State of Online Retail Pricing*.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nHelps an agent evaluate and design credible strategic commitments by auditing capability, irreversible action, visibility, enforcement, and rigidity risk before recommending a commitment device. <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 and external users can use this skill for strategy coaching in negotiation, deterrence, and commitment-design scenarios where credibility, follow-through costs, and rigidity risks need structured analysis. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Strategic commitment guidance could be misused to coerce, intimidate, exploit, evade law, or make irreversible commitments without adequate review. <br>\nMitigation: Use only in lawful and non-coercive contexts, and seek appropriate legal, ethical, and downside review before acting on high-impact recommendations. <br>\nRisk: Poorly validated strategy advice could make a threat, promise, or lock-in more rigid without actually improving credibility. <br>\nMitigation: Review the CAVE audit, payoff assumptions, and rigidity risks before execution; do not rely on the report as a substitute for expert judgment. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/strategic-commitment) <br>\n- [Sources - strategic-commitment](artifact/references/sources.md) <br>\n- [Method in Action: Amazon's Everyday Low Price Commitment](artifact/examples/amazon-everyday-low-price-commitment-1994-present.md) <br>\n- [Schelling, The Strategy of Conflict](https://www.hup.harvard.edu/books/9780674840317) <br>\n- [Selten, Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games](https://doi.org/10.1007/BF01766400) <br>\n- [Kreps and Wilson, Reputation and Imperfect Information](https://doi.org/10.1016/0022-0531(82)90030-8) <br>\n- [Nobel Prize Committee scientific background on Schelling and Aumann](https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown commitment design report with structured fields and coaching questions] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May ask step-by-step questions in coach mode and stop at explicit wait points.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Strategic Commitment Owner: deciqai Summary: Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-24T22:16:02.937Z | user Add TSMC Arizona / AI-capex commitment race case (2020-2026) with founder takeaways; restore agent .json metadata footer v1.0.4 | ","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Threat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>"},{"language":"text","snippet":"Threat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>"},{"language":"text","snippet":"Threat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>"},{"language":"text","snippet":"Threat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>"},{"language":"text","snippet":"Threat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>"},{"language":"text","snippet":"Threat/promise: <action · trigger · audience>\nCAVE: C=<present/absent> · A=<irreversible action> · V=<observable?> · E=<enforcement mechanism> · Weakest=<letter>\nCost of retreat now: <what happens if you don't follow through?>\nDevice chosen: <sunk-cost / reputation / third-party / org lock-in — reasoning>\nPost-commitment payoffs: before=<retreat dominant?> · after=<retreat dominant?> · deterrence=<yes/no/partial>\nRigidity risks: <scenario> · exit clauses: <...> · conditionality: <undermines deterrence?>\nRecommendation: <device · implementation · what opponent should now believe>"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: strategic-commitment\ndescription: \"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side.\n  Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain. More: deciqai.com/c/strategic-commitment\"\n---\n\n# Strategic Commitment\n\n## Overview\n\nStrategic commitment converts \"I might do X\" into \"I will do X\" — not through rhetoric but by *changing payoff structure* so follow-through is the rational move. Schelling (1960, Nobel 2005): keeping options open undermines you when opponents predict you'll rationally back down. A commitment device removes that prediction by making retreat more expensive than execution.\n\nComposes with: `prisoners-dilemma` (diagnose defection traps) · `zero-sum-game` (confirm game structure) · `batna-zopa` (BATNA sets outside option; commitment governs how credibly you communicate it).\n\n## When to Use\n\nApply when:\n- Designing a competitive deterrence posture — making a potential entrant believe you will fight, not accommodate\n- Making a promise or pledge credible to a counterparty who doubts your follow-through\n- In negotiation where the other side exploits your visible flexibility\n- Signaling strategic intent to multiple audiences with a single costly action\n- Evaluating whether a competitor's stated threat is real or theatrical\n- Deciding whether to make a concentrated AI-era bet credible (capex, an all-in product pivot, a \"we're AI-first\" claim) — or auditing whether a rival's AI commitment is money-in-the-ground or a press release\n\n**When NOT to use:** commitment is unobservable to the target audience; environment changes so fast that lock-in outweighs credibility gain; cost of following through exceeds the value being protected; genuine one-shot anonymous game with no reputational audience.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. What-it-is: commitment makes threats credible by locking yourself in so follow-through is the rational choice.\n2. Check fit: does the other side disbelieve your threat? If problem is *capability* (can't execute), not credibility, stop here.\n3. Elicit their case: specific threat, audience, why they doubt follow-through.\n> **[WAIT — do not advance until user responds]**\n4. Run CAVE audit. Ask: \"What happens if you don't follow through? What is the current cost of retreat?\"\n> **[WAIT — do not advance until user responds]**\n5. Name which de"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"strategic-commitment\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784931362937\n}"},{"path":"references/sources.md","content":"# Sources — strategic-commitment\n\n> *Primary sources for the [strategic-commitment](../SKILL.md) skill.*\n\n- Schelling, T.C. (1960). *The Strategy of Conflict.* Harvard University Press. The canonical source. Chapter 2 (\"An Essay on Bargaining\") and Chapter 3 contain the core commitment theory; the Cuba Missile Crisis analysis is in Chapter 8. https://www.hup.harvard.edu/books/9780674840317\n- Dixit, A. & Nalebuff, B. (1991). *Thinking Strategically.* W.W. Norton. The standard business-facing treatment; Chapter 6 covers commitment and credibility with extensive case studies. \"Credibility is the key to making threats work.\" ISBN 978-0393310351.\n- Selten, R. (1975). \"Reexamination of the Perfectness Concept for Equilibrium Points in Extensive Games.\" *International Journal of Game Theory*, 4(1), pp. 25–55. The formal game-theoretic basis: subgame perfect equilibrium eliminates non-credible threats from equilibrium strategies — commitment devices work by changing which equilibria are subgame perfect. https://doi.org/10.1007/BF01766400\n- Kreps, D.M. & Wilson, R. (1982). \"Reputation and Imperfect Information.\" *Journal of Economic Theory*, 27(2), pp. 253–279. The mathematical basis for reputation-based commitment in repeated games; shows how even a small probability of being a \"tough\" type can sustain commitment across many interactions. https://doi.org/10.1016/0022-0531(82)90030-8\n- Nobel Prize Committee (2005). \"Scientific Background: Thomas C. Schelling and Robert J. Aumann.\" The Royal Swedish Academy of Sciences. Documents the theoretical contributions recognized by the Nobel Prize, including the commitment and credibility framework. https://www.nobelprize.org/prizes/economic-sciences/2005/advanced-information/\n\n**What is not cited and why:** The phrases \"burn your bridges\" and \"cutting off retreat\" appear in many popular strategy texts but are attributed to historical figures (Cortes, Xiang Yu) without primary-source documentation sufficient to verify the specific strategic intent described. This skill uses the mathematically grounded commitment theory from Schelling and the game-theoretic formalization from Selten as its analytical foundation, not historical parables.\n- U.S. Department of Commerce (2024). CHIPS Incentives Award announcement for TSMC Arizona (April 2024): up to $6.6B in direct funding tied to milestone enforcement, alongside TSMC's expansion to three Arizona fabs (~$65B announced investment). https://www.commerce.gov/news/press-releases/2024/04/biden-harris-administration-announces-preliminary-terms-tsmc-expanded — a live CAVE-complete commitment: sunk cost + visibility + third-party enforcement.\n- Microsoft (2023). \"Microsoft and OpenAI extend partnership.\" Official Microsoft Blog, January 23, 2023. https://blogs.microsoft.com/blog/2023/01/23/microsoftandopenaiextendpartnership/ — the multi-year, multi-billion-dollar structure as an observable commitment device in the AI platform race."},{"path":"examples/amazon-everyday-low-price-commitment-1994-present.md","content":"# Method in Action: Amazon's Everyday Low Price Commitment (1994–present)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nWhen Jeff Bezos launched Amazon in 1994, the company made a strategic commitment that seemed impossible to enforce: that Amazon would always offer the lowest available price. The competitive logic was clear — if customers believe Amazon is always cheapest, they do not comparison-shop, which dramatically lowers Amazon's customer acquisition cost. But the commitment requires customers and suppliers to believe it, and belief requires credibility.\n\nRun the Commitment Design on Amazon's price commitment:\n\n**Step 1 (threat stated precisely):** \"On any product in our catalog, Amazon's price is at or below any competitor's listed price. If a competitor lists a lower price, Amazon will match it — automatically and in real time.\"\n\n**Step 2 (Credibility Audit):**\n- *Capability:* Amazon had the cash and logistics to absorb price matching costs. ✓\n- *Action taken:* Amazon deployed automated pricing algorithms (its proprietary pricing engine) that scan competitors' prices continuously and adjust Amazon's prices — estimated at approximately 2.5 million price changes per day as of 2013 (Profitero price tracking data). The algorithm is the irreversible action: it executes automatically without human decision at each instance. ✓\n- *Visibility:* Price comparisons are publicly visible; customers and sellers can verify Amazon's prices in real time. ✓\n- *Enforcement:* Amazon's A9 search algorithm penalizes third-party sellers who list at higher prices, creating a market-level enforcement mechanism. ✓\n\n**Step 3 (current cost of retreat):** Before the algorithm, a human decision to not match a competitor's lower price was cheap — it required no action. After the algorithm, matching is automatic; *not* matching requires a deliberate override, which would be visible to sellers and customers and would immediately damage Amazon's core brand claim.\n\n**Step 4 (commitment device):** Primarily organizational lock-in (automated algorithm) combined with reputation. The algorithm is the commitment device — it converts a policy statement into an automatic consequence, removing the temptation to defect case-by-case.\n\n**Step 5 (post-commitment game tree):** Competitors who lower price know Amazon will automatically respond. The expected gain from undercutting Amazon is zero or negative (Amazon matches, competitor margins fall, neither gains share). This suppresses price competition among rivals without Amazon needing to fight each case.\n\n**Step 6 (rigidity risk):** The commitment created rigidity during inflationary periods (2022–2023) and when suppliers demanded higher wholesale prices. Amazon managed this through its third-party marketplace model — many \"Amazon\" prices are set by third-party sellers, not Amazon directly — maintaining the appearance of lowest-price commitment while shifting some rigidity risk to sellers.\n\nPrimary sources: Dixit, "},{"path":"examples/tsmc-arizona-and-ai-capex-commitments-2020-2026.md","content":"# Method in Action: TSMC Arizona and the AI-Capex Commitment Race (2020–2026)\n\n> *Example for the [strategic-commitment](../SKILL.md) skill.*\n\nThe 2020–2026 AI buildout produced the largest peacetime capital commitments in corporate history — and the clearest modern demonstrations of why commitment beats flexibility in games where counterparties act on what they believe you will do. Two linked cases: TSMC's Arizona fabs (a commitment made credible to governments and customers), and the hyperscalers' multi-year AI capex escalation (commitments aimed at rivals, suppliers, and the capital markets simultaneously). Run both through the Credibility Audit.\n\n### Case 1 — TSMC Arizona: making \"we will build outside Taiwan\" credible\n\n**Step 1 — State the commitment precisely.** Action: build and operate leading-edge fabs in Arizona. Trigger: US customers' and the US government's demand for supply-chain resilience. Audience: Washington (subsidy and export-policy decisions), US customers (Apple, Nvidia, AMD — \"can we count on non-Taiwan supply?\"), and rivals (Intel, Samsung) deciding their own capacity bets.\n\n**Step 2 — CAVE audit.** *Capability:* present — TSMC is the only firm that has repeatedly executed leading-edge fabs at scale. *Action taken:* irreversible — announced in 2020 and escalated in stages to a reported ~$65B across three Arizona fabs by 2024, with the first fab reaching volume production of 4nm-class chips in late 2024/early 2025; poured concrete and installed EUV tools cannot be un-spent. *Visibility:* maximal — presidential visits, CHIPS Act grant announcements, quarterly disclosure. *Enforcement:* CHIPS funding milestones and customer prepayment/agreement structures add third-party penalty for retreat. All four present — this is why the commitment moved policy and customer behavior where a press release would not have.\n\n**Step 3–4 — Cost of retreat and device.** Each escalation raised the cost of walking away (sunk cost + reputation with two governments + customer reliance). The device is classic **sunk-cost + third-party constraint**: the money in the ground is the message.\n\n**Step 5 — Post-commitment game tree.** Follow-through became non-dominated retreat: abandoning Arizona after CHIPS milestones and customer commitments would cost more (politically and commercially) than completing fabs whose standalone economics are worse than Taiwan's. That inversion is precisely what makes the audience believe.\n\n**Step 6 — Rigidity risk.** Real and priced in: higher US costs, staffing friction, the risk that demand shifts. TSMC kept conditionality narrow (phasing, tool-timing flexibility) without undermining the core signal.\n\n### Case 2 — Hyperscaler AI capex: commitment as deterrence in the model race\n\nThe 2024–2026 AI capex escalation — combined annual capital expenditure by the largest US hyperscalers reported in the hundreds of billions of dollars by 2025, with multi-year model-training and compute purchase agreements (e.g., Microsoft's multi"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w... Skill: Strategic Commitment Owner: deciqai Summary: Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'w... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-24T22:16:02.937Z | user Add TSMC Arizona / AI-capex commitment race case (2020-2026) with founder takeaways; restore agent .json metadata footer v1.0.4 |","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2121,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T13:35:57.626Z","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-11T13:35:57.626Z","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-11T16:00:33.838Z","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"}]}}}