black-barrier

name	black-barrier
description	Use Black Barrier when ordinary buffering is too soft and thresholding alone is too permissive. The problem is not just one incoming hit, or a stream of weak noise, but contact that should have to prove itself before it reaches the work at all: ambiguous requests, half-authorized changes, untrusted touchpoints, speculative interruptions, or access that has not earned the right to cross the perimeter. Black Barrier establishes a denser selective shell around a critical surface. Unlike Barrier, it is not a one-hit absorb. Unlike Aura, it does not merely ignore weak impacts below a threshold. It enforces a stricter admission rule: only declared, validated, high-confidence contact gets through, and everything else is refused, deferred, or held outside until it can justify entry.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","hybrid","defense-and-recovery","defense","recovery","stabilization","survivability"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Black Barrier

Raise a deny-by-default barrier that only admits named, legitimate contact.

What This Skill Does

Use Black Barrier when ordinary buffering is too soft and thresholding alone is too permissive. The problem is not just one incoming hit, or a stream of weak noise, but contact that should have to prove itself before it reaches the work at all: ambiguous requests, half-authorized changes, untrusted touchpoints, speculative interruptions, or access that has not earned the right to cross the perimeter. Black Barrier establishes a denser selective shell around a critical surface. Unlike Barrier, it is not a one-hit absorb. Unlike Aura, it does not merely ignore weak impacts below a threshold. It enforces a stricter admission rule: only declared, validated, high-confidence contact gets through, and everything else is refused, deferred, or held outside until it can justify entry. In this chip pack, Black Barrier is treated as a hybrid battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Black Barrier. Hermes shelf: Defense and Recovery.

When To Use

• A critical workflow, decision path, or operating surface should not accept casual, ambiguous, or weakly justified contact.
• You need stronger selectivity than Aura because the real problem is unauthorized or poorly qualified entry, not just nuisance noise.
• The next phase of work needs a hardened perimeter where only named, validated interactions are allowed through.

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 exact surface Hermes must protect: approval path, deployment lane, review gate, interface, endpoint, or live operating channel.
• Describe the contact you want kept out: untrusted requests, ambiguous edits, half-authorized actions, speculative asks, noisy touchpoints, or poorly qualified handoffs.
• State the admission rule in observable terms: required authority, validation, confidence, provenance, review status, timing, or another clear basis for entry.
• Say what should happen to rejected contact: refuse immediately, queue outside, log for review, reroute, or require stronger declaration before retry.

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 exact surface that needs the barrier and define why ordinary buffering is no longer sufficient there.
4. Specify the admission standard explicitly: what contact is trusted enough to enter, what evidence it must provide, and what gets refused or held outside.
5. Raise the smallest deny-by-default barrier that preserves the necessary path for legitimate work, then verify that only qualified contact crosses it.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A deny-by-default protective layer, policy, gate, or operating rule around the named critical surface.
• A short note describing what is allowed through, what is blocked, what is deferred for later review, and why.

Output Contract

• One dense selective barrier matched to the named critical surface, with a deny-by-default posture rather than generic hardening language.
• A clear admission rule stating what may pass through, what is rejected, and what is held outside pending validation.
• An explanation of why Black Barrier is the right chip here instead of Barrier, Aura, or Sanctuary.
• A practical operating note on how legitimate work continues without pretending the perimeter should stay maximally closed forever.

Do Not Use For

• Single predictable impacts where the real need is one absorb layer rather than a sustained admission gate.
• Low-grade nuisance traffic that can be handled by a threshold shell without moving to deny-by-default selectivity.
• Protected work zones where the main goal is safe space for recovery or precision execution rather than strict entry control.
• Situations where you cannot articulate a fair, testable basis for what should be allowed through.

Pair With

• Black Barrier + Barrier: keep the perimeter strict, then add a one-hit absorb layer inside for the one committed strike you still expect.
• Black Barrier + Elec Aura: use Black Barrier to enforce admission and Elec Aura to make any perimeter contact loud and immediately legible.
• After Black Barrier, switch to North Wind when the selective shell itself has become obstructive and now prevents necessary honest contact.
• Black Barrier + Repair: seal the critical surface against unqualified touch first, then restore the damaged internals without new interference crossing the line.

Pitfalls / Guardrails

• Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
• Black Barrier is for high-selectivity protection, not blanket refusal of reality. If legitimate work cannot cross the perimeter, the barrier is too dense.
• Do not describe vague distrust as a security policy. The admission rule must be explicit enough that Hermes can tell allowed contact from rejected contact.
• If a simple absorb layer would handle the next hit cleanly, use Barrier instead. If a threshold shell against nuisance pressure is enough, use Aura instead.
• 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 Hermes names a concrete admission rule and does not reduce Black Barrier to generic toughness or mood-dark security language.
• Confirm the response distinguishes Black Barrier from Aura by policy selectivity rather than impact thresholding alone.
• Confirm legitimate, necessary work still has an explicit path through the barrier and is not accidentally blocked by over-hardening.
• Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Black Barrier on this approval path: only let fully authorized, fully specified requests through, keep ambiguous asks outside, and tell me exactly what admission rule you are enforcing.
Use Black Barrier here to harden this deployment lane against half-validated changes; deny by default, preserve one legitimate entry path, and explain what gets blocked versus admitted.