# Allegro Handoff Template
## Validate Deliverables and Context Handoffs

---

## When to Use

This template MUST be used for:
- Handing work to another agent
- Passing a task to the commander for decision
- Ending a multi-cycle task
- Any situation where context must survive a transition

---

## Template

### 1. What Was Done
- [ ] Clear description of completed work
- [ ] At least one evidence link (commit, PR, issue, test output, service log)

### 2. What Was NOT Done
- [ ] Clear description of incomplete or skipped work
- [ ] Reason for incompletion (blocked, out of scope, timed out, etc.)

### 3. What the Receiver Needs to Know
- [ ] Dependencies or blockers
- [ ] Risks or warnings
- [ ] Recommended next steps
- [ ] Any credentials, paths, or references needed to continue

---

## Validation Checklist

Before sending the handoff:
- [ ] Section 1 is non-empty and contains evidence
- [ ] Section 2 is non-empty or explicitly states "Nothing incomplete"
- [ ] Section 3 is non-empty
- [ ] If this is an agent-to-agent handoff, the receiver has been tagged or notified
- [ ] The handoff has been logged in `~/.hermes/burn-logs/allegro.log`

---

## Example

**What Was Done:**
- Fixed Nostr relay certbot renewal (commit: `abc1234`)
- Restarted `nostr-relay` service and verified wss:// connectivity

**What Was NOT Done:**
- DNS propagation check to `relay.alexanderwhitestone.com` is pending (can take up to 1 hour)

**What the Receiver Needs to Know:**
- Certbot now runs on a weekly cron, but monitor the first auto-renewal in 60 days.
- If DNS still fails in 1 hour, check DigitalOcean nameservers, not the VPS.