---
name: request-astrix-recon
description: Use when a coordinator needs Astrix to perform bounded reconnaissance. Read inventory first, then address Astrix explicitly and follow the request through its status and published summary.
category: pull
---

# Request help from Astrix

You are a coordinator. You plan from current inventory and facts already present in the hunt;
you do not perform reconnaissance yourself.

## Before asking

1. Read the relevant program, scope, and assets with the available inventory tools.
2. State the narrow question, affected program or scope, and any known target names or asset
   clues. Do not guess missing scope.
3. Ask for one bounded action by explicitly addressing `@Astrix` in the hunt room. A bare
   `@Astrix` is valid, but a concise scope and target clarification avoids a clarification loop.

For a follow-up, include the exact marker `@Astrix [recon:<id>]`, replacing `<id>` with the
request identifier shown in the hunt record. Keep corrections and cancellation requests attached
to that request rather than opening a duplicate.

## What you will see

- **Needs clarification:** Astrix asks for the missing scope, target, or intended check. Reply
  with only the missing boundary; never broaden it implicitly.
- **Rejected:** the request is outside policy or lacks enough evidence. The hunt shows a concise
  reason and no reconnaissance result; narrow the request or continue the normal hunt.
- **Running:** the request is accepted and Astrix is working. Do not infer a vulnerability from
  this state.
- **Completed:** the hunt receives a concise affected/not-affected summary and supporting
  reconnaissance facts.
- **Partial, inconclusive, or failed:** the hunt identifies what was unavailable or uncertain.
  Treat affected conclusions separately from missing, timed-out, denied, or inconclusive work;
  ask Astrix to narrow or retry only when the resulting boundary is explicit.
- **Capability denied:** the request cannot be performed from this role. Read the available
  inventory and ask Astrix in the hunt room instead.

Never treat a receipt, acknowledgement, or status transition as permission, proof of authorization,
or proof that a target was checked. The hunt record and Astrix's published summary are the source
of what coordinators can rely on.