Hmbown Area Grab
Steal operating room from the opponent and give it to yourself.
What This Skill Does
Use Area Grab when progress depends on reclaiming surface area: more room in the design, more latitude in the plan, or fewer hostile constraints. In this chip pack, Area Grab is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Area Grab. Hermes shelf: Control and Terrain.
When To Use
- The current room is too cramped to operate safely.
- You need to simplify ownership or reduce the number of contested panels.
- The right move is to create margin before taking action.
Prerequisites
- 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 contested surface, room, or constraint that is cramping progress.
- State who or what effectively owns that space now.
- Describe the smallest reclaimed area that would materially improve the next move.
- Identify the follow-up action Hermes should enable once room is reclaimed.
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 contested surface and who owns it now.
- Capture the nearest useful panels first.
- Use the new room immediately instead of admiring it.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A structural change that creates more safe operating space.
- A short explanation of what room was reclaimed.
Output Contract
- A structural change that reclaims meaningful operating room, not just commentary about needing space.
- A short map of what surface was reclaimed and why it matters.
- A clear statement of the next move that the new room enables.
- Scope that stays proportional to the minimum useful expansion.
Do Not Use For
- Cases where one lane or one dependency change would be enough.
- Purely local edits that do not actually depend on room, ownership, or constraint relief.
- Expansions that create maintenance burden the operator cannot realistically hold.
Pair With
- After Area Grab, switch to Cannon when the reclaimed room exposes one clean direct shot.
- After Area Grab, switch to Sword when the new operating space makes a local cut safe and obvious.
- After Area Grab, switch to Panel Grab when broad expansion was too much and the remaining work is about one specific lane.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real operator move instead of drifting into lore.
- Do not over-expand into panels you cannot hold.
- If a smaller local grab will do, do not seize the whole field.
- 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 named the contested surface and changed ownership or constraint reality, not just the wording around it.
- Confirm the reclaimed room is actually usable for the next step.
- Confirm expansion did not run past the smallest meaningful boundary.
- Check that the metaphor still maps cleanly to a real operator mechanism.
Example Invocation
Use Area Grab on this migration plan: reclaim the smallest set of constraints blocking movement so we have room to execute the next phase safely.
Use Area Grab to reduce the number of contested ownership boundaries in this repo layout before proposing further edits.