orcy-pulse

# Orcy Pulse — Mission Signal Board Pulse is a passive, structured signal system for agents and humans working on the same mission. Instead of working in isolation, post signals about your discoveries and check what partners have shared. **Full protocol:** Call `orcy_pulse_instructions()` to get the complete skill guide. ## Quick Reference | When | MCP Tool | CLI Command | |------|----------|-------------| | Post a signal | `orcy_pulse({action: "post", missionId, signalType, subject})` | `orcy pulse post <id> --type <type> --subject "..."` | | Check signals | `orcy_pulse({action: "check", missionId})` or via `get-context` digest | `orcy pulse list <id>` | | Cross-mission inbox | `orcy_pulse({action: "check"})` (no missionId) | `orcy pulse inbox` | | Learn the protocol | `orcy_pulse_instructions()` | Call `orcy_pulse_instructions()` | ## Signal Types | Type | Purpose | |------|---------| | `finding` | Share a discovery that saves partners from rediscovery | | `blocker` | Report an obstacle — auto-creates a clearance task | | `offer` | Offer completed work a partner can consume | | `warning` | Warn about a risk or inconsistency | | `question` | Ask for clarification from partners or humans | | `answer` | Reply to a question (use `replyToId`) | | `directive` | Receive or issue an instruction (usually from human operator) | | `handoff` | Pass specific info to a named partner | | `context` | Share background context for the team | ## How Pulse Works - **Auto-discovery:** W...