Barrier

Barrier

Put a clean absorb layer between the operator and the next hit.

What This Skill Does

Use Barrier when the system can keep moving, but it needs a buffer layer to absorb the next impact. In this chip pack, Barrier is treated as a hybrid battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Barrier. Hermes shelf: Defense and Recovery.

When To Use

• A rollout, workflow, or review path needs temporary protection.
• The next hit is predictable enough to absorb with a wrapper or check.
• You want to buy time without freezing motion.

Prerequisites

• Name which part of this move is real tool use versus battle-chip framing before you act.
• These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

Operator Inputs

• Name the next likely hit, failure mode, or source of pressure you want to absorb.
• Identify the exact surface to shield: workflow step, route, interface, review path, or component.
• Say how temporary the protection can be before a deeper fix is required.
• State what level of friction is acceptable while the guard is in place.

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 likely hit you need to absorb.
4. Place the lightest viable buffer in front of it.
5. Measure whether the barrier held or needs reinforcement.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A wrapper, guard, or validation layer.
• A short note on what impact it is designed to absorb.

Output Contract

• One minimal protective layer, wrapper, or gate matched to the named risk.
• A note on what the barrier is meant to absorb and what it does not cover.
• A reversible move narrow enough that the surrounding workflow can continue.
• A removal, strengthening, or handoff condition.

Do Not Use For

• Permanent architecture fixes when the root cause is already understood.
• Broad lockdowns that stop all motion just to avoid one predictable hit.
• Situations where the likely impact is unknown or too varied for a single guard.

Pair With

• Barrier + Repair: absorb the next hit, then restore the damaged surface cleanly.
• Barrier + Invisible: shield the approach, then take a short low-exposure look inside.
• Barrier + Recovery: reduce incoming damage while you stabilize the operator or process.

Pitfalls / Guardrails

• Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
• Barrier is not a substitute for understanding root cause.
• Do not mistake a temporary shield for a permanent fix.
• 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 proposed guard clearly maps to a named incoming hit or failure mode.
• Confirm the protection is smaller than the workflow it surrounds and does not become a hidden rewrite.
• Confirm the operator can tell whether the barrier held, failed, or needs reinforcement.
• Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Barrier to add the smallest guard around this flaky handoff so one bad input does not halt the whole run.
Use Barrier here: protect the approval step from duplicate submissions, but do not redesign the entire flow.