deploylisted

# This skill sets honcho up before it reports honcho is up You are about to bring **honcho** up from a *recipe*, not from a finished instance. The skill ships honcho as source: a carried recipe plus the pin to the code that runs it, like a self-extracting archive that carries both its contents and the unpacker. Before you tell anyone honcho is running, deploy it against **this** target and GRADE it honestly. You do the work in-loop; nobody runs a command line. The material is the carried recipe, the binds, the checks, and the acceptance in the sections below. Two roles run through this. The **author** packaged honcho as this skill on their machine. The **receiver** is whoever installs it, a different target, whose substrate, secrets, and paths you resolve here. You work so the receiver reaches a real, graded honcho, or an honest reason it could not, never a silent success. ## Recipe (run before your first report that honcho is up) 1. **Cache / idempotency.** If honcho is already up on this target in this session (a prior graded namespace exists, or a resolution is recorded here), reuse it, emit the Reusing line, and skip to step 6. Do not re-deploy over a live instance. 2. **Resolve the binds.** For each entry in the binds section, probe this target for the matching capability, and resolve the isolation substrate to the required strength the carried recipe names. If a *required* bind has no match here, or no substrate meets the required strength, STOP, dep