Slow Gauge

• Name the risky loop, actor, or queue that is moving too quickly.
• State what decision or failure mode the slowdown is meant to protect.
• Identify the narrowest place to insert a pause, throttle, or gate.
• Name the signal that will tell us it is safe to remove the drag.

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. Identify the loop or actor moving too quickly.
4. Introduce one clear rate limiter or pause point.
5. Use the slower gauge for reasoning, not for drift.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A pause, throttle, or review gate.
• A note on what decision quality the slower gauge protects.

Output Contract

• A named risky loop and one specific slowdown mechanism.
• A protected decision or risk that justifies the slower gauge.
• A scope boundary so unrelated work can keep moving.
• An exit condition for removing the added drag.

Do Not Use For

• Blanket process slowdowns when only one lane is unsafe.
• Indefinite review gates with no release condition.
• Cases where the problem is missing context rather than excessive tempo.

Pair With

• Use Fast Gauge instead when the loop is healthy and simply too slow.
• Use Full Custom instead when the hand is wrong and a redraw is better than a slowdown.
• Pair Slow Gauge with Sanctuary when a careful protected work zone matters more than throughput.

Pitfalls / Guardrails

• Keep the metaphor anchored to a real operator move instead of drifting into lore.
• Do not slow the entire room if only one lane is dangerous.
• Remove the drag once the risky phase passes.
• 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 the slowdown was applied to the narrowest risky lane.
• Confirm the protected decision quality or safety benefit is explicit.
• Confirm there is a concrete condition for removing the extra drag.
• Check that the metaphor still maps cleanly to a real operator mechanism.

Example Invocation

Use Slow Gauge on this deployment path. Add the smallest review gate that protects production safety, and tell me when to remove it.
Use Slow Gauge on our incident channel: identify the lane that needs a throttle, explain what decision quality it protects, and avoid slowing unrelated work.