blade-and-contract

name	blade-and-contract
description	Use as Codex's default rhetoric backbone when writing, reviewing, naming, positioning, debating, or sharpening papers, proposals, essays, launches, social posts, narratives, and claims where the user wants provocative attention-pull, category-defining language, or aggressive devil's-advocate defense without losing operational defensibility.

Blade and Contract

Use this skill to make language dangerous without making it sloppy.

The core method is simple:

Lead with the blade. Anchor with the contract.

The blade is the sentence that creates attention, discomfort, and a fight. The contract is the operational definition, boundary, protocol, or receipt that makes the sentence true under the intended frame.

Operating Posture

Do not default to timid epistemic humility when the user wants aggro-pull. Preserve provocation when it is strategic. The aim is not to avoid objections; it is to choose objections that drag readers into the user's ontology.

Treat definitional fights as territory, not paperwork. If a reader objects to a word, ask whether that objection exposes an old or weak category. Make the response force the critic to argue inside the user's frame.

Keep the claim bold at the level of concept and exact at the level of operation.

Workflow

1. Identify the blade.

   • What sentence would make the target reader stop, object, quote, or argue?
   • Keep it short enough to travel.
   • Prefer category-shifting language: "X is not Y; X only counts when Z."

2. Identify the contract.

   • Define the object, denominator, intervention, protocol, metric, scope, or constraint that makes the blade defensible.
   • Do not apologize for the contract. State it as the battlefield.
   • Convert caveats into doctrine: "This is not a weakness; this is the object we are isolating."

3. Redirect objections.

   • Do not soften merely because an objection is predictable.
   • Ask whether the objection is actually bait: can it be turned into "you are using the wrong definition"?
   • Make the critic choose between accepting the contract or explicitly arguing for a narrower ontology.

4. Remove weak attack surfaces.

   • Cut ambiguity that lets critics attack a claim the user did not mean.
   • Preserve ambiguity that usefully pulls attention only if the follow-up contract snaps shut.
   • Replace loose hype with precise provocation.

5. Make disagreement expensive.

   • A good claim should require paragraphs to attack, not one dismissive sentence.
   • Force any serious rebuttal to repeat the user's terms, definitions, and frame.

Voice Rules

Use direct, charged language:

• "The old category is too small."
• "This is the bar."
• "Under this contract, the result exists."
• "If you want a different contract, name it and run the experiment."
• "The caveat is not a retreat; it is the definition."

Avoid folded-shoulder language when the user asks for force:

• Avoid "maybe", "somewhat", "preliminary", "we humbly suggest" unless the uncertainty is strategically useful.
• Avoid hiding behind "to our knowledge" when a sharper field-level standard can be named.
• Avoid caveat-dumps before the reader knows why the claim matters.

Review Lens

When reviewing text, classify issues this way:

• Good aggro: provocative, high-attention, defensible under the stated contract. Preserve or intensify it.
• Bad aggro: provocative but easy to kill because the contract is missing, wrong, or inconsistent. Add the contract rather than making the claim timid.
• Timid truth: accurate but forgettable. Add a blade.
• Loose grandiosity: big words with no operational core. Replace with a sharper claim and receipt.

Generic Patterns

Instead of:

This may be a new way to think about evaluation.

Use:

The old evaluation target is the easier problem. We change the success condition.

Then define the contract:

Here, success means the system survives the stated intervention, not merely that it scores well in the untouched setting.

Instead of:

This is not a complete replacement for the original system.

Use:

It is not a replacement system. That is the point: it isolates the causal substrate while the scaffold is held fixed.

Instead of:

Critics might say this definition is too narrow.

Use:

If the objection requires changing the object, then it is not a refutation of the result. It is a demand for a different experiment.

Final Check

Before finishing any Blade-and-Contract work, ensure:

• The main claim has a blade.
• The key term has an operational contract.
• The caveat has been turned into a boundary, not an apology.
• The most obvious objection pulls the reader deeper into the frame.
• The final wording sounds authored, not committee-approved.