---
name: phoenix-operator
description: Query, audit, select, and safely execute UberBond PHOENIX capabilities in its existing Codespace using the connected Chat On Steroids Core plugin. Use when asked to activate the 1,560 PHOENIX designs, find runnable agents, route work, or continue capability integration.
---

# PHOENIX Capability Bridge

Use the user's existing, connected **Chat On Steroids Core** terminal/file tools. This plugin packages a workflow, NOT 1,560 new MCP executor functions or an independent always-on server. Do not invent a Codespace connection; if unavailable report the blocker.

## Reality-first operation

1. Verify the current Git repository branch, worktree and main SHA. Read `AI_START_HERE.md`, `AGENTS.md`, `docs/UNIVERSAL_CONTEXT_PROTOCOL.md`, and relevant current handoff. Never modify dirty root, UberWarm, or unrelated worktrees. Use fresh current-main worktree for code edits.
2. Check `node scripts/phoenix-cos-operator.mjs status` in a checkout actually containing that file.
3. Use `waves` to verify 1,560 source-pinned designs in Waves 3–10. Original Wave 1–2 specifications remain unknown. `wave 4 0 20` pages original IDs; `research "query" 5` performs zero-effect lexical search; `mission phoenix-wave4-0001` produces a source-linked implementation contract.
4. Use `catalog` or `route "goal"` for the native Capability Genome. `invoke <allowlisted atom> '<bounded JSON object>'` may execute only one of the approved deterministic, zero-external-effect native functions. Never use arbitrary shell user inputs, arbitrary untrusted suppliers, or the registry as automatic authority.
5. If a design is not yet built, preserve it as `RESEARCH_ONLY`; assess its license, source revision, security, dependencies, benchmarks, cost, rollback, and authorization in isolation. No unscreened third-party repo cloning/execution, paid inference, outreach, deployment, credential changes, or access-control bypass.
6. Verify permitted, denied and retry/restart behavior, retain receipts and exact source SHA, and report counts separately: research proposals, supplier candidates, admitted executable native atoms, and production deployments.

## Commands inside the approved UberBond worktree

`node scripts/phoenix-cos-operator.mjs status`

`node scripts/phoenix-cos-operator.mjs waves`

`node scripts/phoenix-cos-operator.mjs wave 4 0 20`

`node scripts/phoenix-cos-operator.mjs research "proof evidence" 5`

`node scripts/phoenix-cos-operator.mjs mission phoenix-wave4-0001`

`node scripts/phoenix-cos-operator.mjs route "minimax strategy"`

`node scripts/phoenix-cos-operator.mjs invoke founder.exception-prioritize '{"exceptions":[]}'`

## Invariants

Research is not implementation. A verified native local function is not a remote commercial service. Catalog entry, route score, license guess, and a prior ChatGPT answer cannot grant execution authority. The user's attached Chat On Steroids Core plugin remains the authenticated terminal; this PHOENIX package supplies the disciplined specialized workflow.