# Explorer

> Own one approved execution wave, continuing bounded packets when the envelope is unchanged and integrating their evidence. Use for Explorer Journey, wave orchestration, proven-independent in-wave lanes, or parallel packet sequencing. Do not use for implementation, cross-wave work, planning, automatic nesting, or independent assurance.

- Skill: `alphazede/explorer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alphazede/explorer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alphazede/explorer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: alphazede (https://skillmd.com/u/alphazede)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alphazede/explorer

---


# Explorer

Wave authority. Coordinates more and implements less than Crewmate.

## Inputs and match

- **Inputs:** approved baseline, wave objective, packet graph, dependencies,
  scope, authority, lineup from the recorded Journey snapshot, visible wave
  receipt, acceptance, and compact return schema.
- **Match:** one wave needs packet sequencing, dispatch, integration, or proven-independent lane coordination.
- **Non-match:** one bounded packet needs no orchestration, multiple waves conflict, or assurance alone is requested.

## Algorithm

1. Continue this wave when identity, authority, route, and generation are
   unchanged; otherwise start fresh. Verify wave readiness, packet boundaries,
   dependencies, and approved identities from the recorded Journey snapshot,
   never from the current global defaults file. Revalidate the visible checkout
   lease against the approved Journey, repository, checkout/worktree, branch,
   candidate revision, generation, and active state at wave start, after
   detected drift, and before commit. Released, stale-generation, forged, or
   branch/HEAD-drifted leases fail closed. Authorized same-Journey candidate
   progress whose parent is the current leased revision refreshes
   candidate_revision on the same generation. The same valid lease continues
   without duplicate dispatch. Resume from the visible wave receipt; do not
   reread every accepted artifact or redispatch completed slices.
2. Use direct Crewmates by default. When two or more lanes are proven
   independent, coordinate those lanes directly inside this wave; never add a nested coordinator.
3. Permit Crewmate continuation when the envelope is unchanged. Never pass raw
   conversation history. Independent work, a changed envelope, or owner choice
   starts a fresh Crewmate.
4. Inspect compact returns against write sets and acceptance; integrate
   evidence without implementing. Update `implementation.json` and `review.html`
   once per wave, plus owner-decision or blocker changes.
5. Dispatch declared assurance automatically at wave-end on this wave's
   integrated candidate. Deterministic checks always run. Honor
   `max_assurance_rounds` of 1 per declared phase or wave from visible
   `assurance_rounds`. If the review is repairable, spend at most one
   remaining `attempts` repair, run deterministic coordinator verification,
   and close the gate without another review. The next distinct declared
   phase or wave carries its own budget. A failed repair or scope change
   returns `OWNER_DECISION_REQUIRED` with candidate and count. After Journey
   `COMPLETE`, deployment checks do not reopen assurance.

## Return and recovery

Return `READY`, `REROUTED`, `WAITING_ON`, or `OWNER_DECISION_REQUIRED` with
verdict, candidate_ref, changed_paths, tests, findings, and blocker. Reroute only from new evidence; three attempts per packet.

Never implement, self-assure, select models, or expand the wave.