| name | fire-aura |
| description | Use Fire Aura when the real threat is not one decisive blow but a stream of low-grade interruptions, shallow objections, retry churn, or opportunistic pokes that keep stealing momentum. Fire Aura establishes an aggressive protective threshold: trivial contact gets burned away automatically so Hermes can stay on the offensive, while anything substantial still has to be named and handled honestly. |
Fire Aura
Keep moving behind a hot perimeter that burns off nuisance hits before they can break tempo.
Overview
Use Fire Aura when the real threat is not one decisive blow but a stream of low-grade interruptions, shallow objections, retry churn, or opportunistic pokes that keep stealing momentum. Fire Aura establishes an aggressive protective threshold: trivial contact gets burned away automatically so Hermes can stay on the offensive, while anything substantial still has to be named and handled honestly.
This is the secondary Codex compatibility rendering of a hybrid battle-chip pattern with a shipping-now execution model.
Canonical chip family: Fire Aura
Codex shelf: Defense and Recovery
Provider target: Codex compatibility surface.
When To Use
- The operator is facing repeated low-severity interruptions that are individually small but collectively break concentration or delivery tempo.
- You need protection that preserves forward motion rather than stopping to absorb every nuisance hit one by one.
- Minor incoming noise should be auto-rejected, rate-limited, or burned off so only meaningful impacts reach the core workflow.
Workflow
- Identify the exact class of low-grade hits that should be burned away: retries, duplicate asks, trivial alerts, shallow objections, spammy inputs, or repeated edge-case churn.
- Set a clear heat threshold that rejects nuisance contact without hiding meaningful signals or real failures.
- Keep pushing the primary task while monitoring for any hit strong enough to punch through the aura and require a different chip.
Deliverables
- A hot-edge defensive layer such as thresholding, filtering, rate control, deduplication, or low-value rejection that keeps nuisance pressure off the operator.
- A short note defining what the aura burns away automatically and what kinds of hits still penetrate.
- A concrete statement of how this protection preserves tempo for the main task instead of merely suppressing noise.
Guardrails
- Fire Aura is for nuisance pressure, not for risks that are already severe, ambiguous, or safety-critical.
- Do not burn away weak signals so aggressively that early warning signs disappear with the spam.
- If the defense would primarily create a safe work zone rather than a hot perimeter, use Sanctuary instead.
Default Invocation
Use Fire Aura to establish a hot perimeter that burns away low-grade interruptions, preserves momentum on the main task, and clearly states what still counts as a real hit.
