blade-and-contract

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.