---
name: avax-orchestration
description: Coordinate Avalanche contract, protocol, UI and release work with evidence-backed handoffs.
---

# Orchestrate an Avalanche build

1. Read [Ship](../ship/SKILL.md) and [Architecture](../architecture/SKILL.md). Define target chain, assets, actors, state transitions and acceptance checks. Separate local work from signatures, public transactions and external publication.
2. Create one deployment manifest for scripts, UI and tests: raw chain identity, address roles, ABI/version, source, block/hash and proxy resolution. Complete a handoff when downstream code consumes the same manifest without retyping addresses.
3. Divide independent contract, protocol, UI and verification lanes. Specify owned files, input/output schemas, commands and evidence. Mark fixtures as fixtures; replace them before claiming live integration.
4. Establish a local vertical slice. From the executable bundle root run `npm ci` through the permitted package workflow, `python3 scripts/setup_native_tools.py`, `python3 scripts/setup_native_tools.py --check`, and `node examples/core/verify.mjs`. Require a real state transition with asset/state deltas.
5. Integrate the selected protocol after version/address checks pass. Keep allowance, quote, signature, receipt and reconciliation separate. Account, chain or input changes invalidate pending evidence. Read [Frontend](../frontend/SKILL.md) and [Frontend Playbook](../frontend-playbook/SKILL.md).
6. Verify actual worker and artifact status. Created/queued is not running; a transaction hash is not success; browser tests are not contract invariants. Reproduce failures and rerun affected downstream tests after repair.
7. Assemble a reviewable release with [QA](../qa/SKILL.md) and [Audit](../audit/SKILL.md). Record source/build identities, unresolved findings and recovery. Perform only authorized external actions, preserving authorization already given.

## Executable handoffs

Protocol modules under `examples/protocols/<slug>/recipe.mjs` export manifest, inspect and plan. Inspection returns pinned evidence; planning returns unsigned calls or throws. Aave/BENQI and Silo/Euler have different schemas: use each recipe's sample rather than flattening distinct protocol semantics.

Run these from the executable bundle root:

- `node research/parity-dexes/fork-execution.mjs`
- `node research/parity-aave-benqi/fork-proof.mjs`
- `node research/parity-silo-euler/verify-fork.mjs`
- `node examples/privacy/verify.mjs`

They use disposable local environments, not public writes. Keep synthetic funding separate from public read evidence.

**Deliver:** phase; artifact/interface ownership; observed results; active/blocked work; publication state; next dependent action.

Sources: [Avalanche tooling](https://build.avax.network/docs/tooling/ai-llm), [simulation](https://viem.sh/docs/contract/simulateContract), primary protocol sources in [DeFi](../defi/SKILL.md).