hermes-voip

Autonomous single-orchestrator build loop. ONE Claude session (the orchestrator) fans out agent teams via ultracode Workflows to drive the whole repo toward done — identifying next work, then shipping correctness/robustness/tests/docs/API/auth/observability/UX, gap-reviewing, backlogging the gaps, and shipping those too. Selects the right model per job. Runs for days. Trigger: `/loop /orchestrate`. The ONLY exit is a genuinely dry repo (no work, no UX to improve) — never a "natural break point".

Outbound call to ask about the price, stock, or availability of a product or service on the operator's behalf, and report back what you learn. Load this when placing a call whose objective is a price or availability enquiry.

Door or gate intercom: handle a delivery (parcel, food, courier) and open the entry only for a genuine, expected delivery. Load this when answering a door intercom and the visitor says they are delivering something.

Outbound call to book a reservation on the operator's behalf (a restaurant table, an appointment, a booking). Load this when you are placing a call whose objective is to make a booking.

Answer an inbound call as a polite receptionist screening an unknown caller: greet, find out who is calling and why, answer general questions, and decide what happens next. Load this when handling an inbound call from an unknown or untrusted caller.

Take a message from a caller: capture who is calling, the best callback number, and the message itself, read it back to confirm, and record it for the operator. Load this when a caller wants to leave a message.

Store and recall persistent project memory via the local qdrant memory MCP (qdrant-store / qdrant-find). Recall at the start of non-trivial tasks; store non-obvious decisions, operator feedback, and hard-won lessons when you learn them.

Record an architecture decision as an ADR in docs/adr/. Use whenever a non-trivial design or tooling decision is made (technology choice, data model, protocol, security posture) — before or alongside the implementing commit.

Create, work in, integrate, and clean up an isolated git worktree lane. ALL work happens in a lane — solo tasks and delegated subagents alike; the root checkout is never edited. Use at the start of any task that changes files.