| name | aura |
| description | Use Aura when the problem is not one big blow but constant low-grade interference: nuisance traffic, shallow criticism, repetitive edge pokes, cheap probes, or background turbulence that keeps stealing turns. Aura sets a named threshold and blanks everything below it, so Hermes can keep operating through minor contact while preserving attention for impacts that actually matter. Unlike Barrier, Aura is not a one-hit absorb; unlike Leaf Shield, it does not punish contact. It is the baseline selective shell. |
Aura
Raise a selective shell that ignores weak hits and only yields to real force.
Overview
Use Aura when the problem is not one big blow but constant low-grade interference: nuisance traffic, shallow criticism, repetitive edge pokes, cheap probes, or background turbulence that keeps stealing turns. Aura sets a named threshold and blanks everything below it, so Hermes can keep operating through minor contact while preserving attention for impacts that actually matter. Unlike Barrier, Aura is not a one-hit absorb; unlike Leaf Shield, it does not punish contact. It is the baseline selective shell.
This is the secondary Codex compatibility rendering of a hybrid battle-chip pattern with a shipping-now execution model.
Canonical chip family: Aura
Codex shelf: Defense and Recovery
Provider target: Codex compatibility surface.
When To Use
- The system is taking many weak or nuisance hits that should not each demand a full response.
- You can define a clear threshold below which incoming pressure should be ignored, dropped, or auto-handled.
- Minor contact is wasting operator attention, but stronger impacts still need to break through or be treated as real events.
Workflow
- Name the exact class of low-grade hits, noise, or nuisance contact that should be screened out.
- Set an explicit threshold that distinguishes ignorable contact from meaningful force, then implement the lightest shell that enforces it.
- Verify that sub-threshold hits are nullified cleanly while above-threshold impacts still surface as actionable events.
