Anti Damage

• Name the next hostile hit, failure mode, or input you expect and want to counter.
• Describe the single automatic response that should fire if that trigger lands.
• Say how narrow the trigger must be to avoid accidental activation.
• State what level of response is proportionate and safe.

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Collect the operator inputs below so the chip lands on the right panel.
3. Name the incoming event worth countering.
4. Prepare a single automatic response to that hit.
5. Verify the counter only fires on the intended trigger.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A counter-trigger or reactive safeguard.
• A note describing the exact trigger and response.

Output Contract

• One reactive counter tied to one predictable incoming event.
• A trigger and response defined in concrete terms, including what will not activate it.
• A response proportionate, narrow, and easier to review than a proactive overhaul.
• A disable path if conditions change.

Do Not Use For

• Ambiguous or noisy inputs that cannot support a narrow trigger.
• Escalatory responses where the counter is harder to control than the original hit.
• General monitoring or passive shielding problems better suited to Killer Eye or Barrier.

Pair With

• Anti Damage + Barrier: absorb routine pressure, but convert one especially predictable hit into a counter.
• Anti Damage + Killer Eye: watch for the approach, then fire a reactive safeguard on the true trigger.
• Anti Damage + Time Bomb: pair an immediate narrow counter with a delayed consequence if pressure continues.

Pitfalls / Guardrails

• Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
• Reactive systems must be narrower than proactive ones.
• Do not use Anti Damage for ambiguous or high-noise inputs.
• Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

• Check that the response includes every promised deliverable and leaves an inspectable audit trail.
• Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
• Confirm only the intended trigger activates the counter; nearby noise does not.
• Confirm the response is proportionate to the hit and does not create a larger blast radius.
• Confirm the draft includes a disable or rollback path if the threat model changes.
• Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Anti Damage to define one narrow reactive counter for the next predictable hit in this workflow.
Use Anti Damage here: name the exact trigger, the single response, and what must not activate it.