Spreader

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Identify the impact point whose nearby area matters most.
3. Choose the narrowest practical spread that still changes the local board state.
4. Fire into that point, then verify what the bloom caught, forced, or revealed.
5. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A wider direct action centered on one meaningful impact point.
• A short note explaining what the spread caught around the hit.

Pitfalls / Guardrails

• Keep the metaphor anchored to a real operator move instead of drifting into lore.
• Do not use Spreader when you need precision at one exact point.
• Do not widen the blast more than the local cluster justifies.
• 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.
• Check that the metaphor still maps cleanly to a real operator mechanism.

Example Invocation

/spreader widen the impact around one meaningful target point, keep the bloom as small as possible, and report what the spread caught around the hit