# /sptc:ready — operative instructions

Make this session reachable for inter-agent messages. Fewest steps — the user is waiting on bringup.

**If this session is spt-hosted** (launched by the spt daemon — SessionStart identity brief
already present + perch already bound before you run anything), it is **broker-delivered**: inbound
already reaches you automatically as `<sptc_messages>` on your turn. **Do NOT arm the step-2 Monitor
listener** — an in-session `spt ready`/`spt api listen` cannot re-arm an spt-hosted perch (the
Monitor's `bash.exe` child breaks by-pid resolution → ADAPTER_UNRESOLVED, and the Monitor-child pid
breaks seed lineage → NO_SEED). You are already reachable; just reply-and-continue (step 3). The steps
below are for a **normal** (self-launched) session.
<!-- [doc->REQ-SKILL-LIVE-SPT-HOSTED-BRANCH] -->

1. Pick the id: the one the user gave, else `spt whoami`. Call it `<id>`.
2. Run the listener as a single PERSISTENT background task via the **Monitor** tool:
   - `command: "spt ready <id>"`
   - `persistent: true`
   - `description: "« spt event »"`

   It blocks for the session's life, emitting one `<EVENT type="msg" from="<sender>">body</EVENT>` per
   delivery. Announce reachable — don't wait on markers.
3. To reply, pipe the message body to `spt send <sender>` (sender = the `from` on the EVENT).

Full guidance: `spt how-to ready`. (No long-running tasks available? `spt ready <id> --once` drains the
backlog, waits for one delivery, then exits — re-run to stay reachable.)