| 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
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Collect the operator inputs below so the chip lands on the right panel.
- Name the exact surface that needs the barrier and define why ordinary buffering is no longer sufficient there.
- Specify the admission standard explicitly: what contact is trusted enough to enter, what evidence it must provide, and what gets refused or held outside.
