3.6 KiB
Delivery Record — HERMES-PLAYBOOK-FOR-SCOT
Status: SEND-READY — awaiting Kwame's channel + recipient confirmation
No documented channel to Scot Murray exists in this workspace, the skills, or config
(verified 2026-09-11 by sweep of ~/syslog/projects/murray-capital/, syslog-infra
references, murray-harness skill, .hermes/memories/, all of ~/syslog/).
Per the card's unblock constraints: package prepared, exact send commands written
below, nothing transmitted. Guessing an address is out of scope.
Verified artifact (single source of truth)
| Item | Value |
|---|---|
| Markdown source | /home/hermes/syslog/prose-contracts/deliverables/scot-hermes-playbook/HERMES-PLAYBOOK-FOR-SCOT.md |
| sha256 | b0966a649fec96da4975ec00e627fbaba3a92a62c4a92b33bc06589c47d25f7f |
| Size | 28821 bytes, 377 lines |
| Matches reviewed bytes | YES — identical to /home/hermes/syslog/drafts/scot-hermes-playbook/ copy and to the hash recorded on card t_2c716052 |
Rendered PDF (from the verified bytes, no edits)
| Item | Value |
|---|---|
/home/hermes/syslog/prose-contracts/deliverables/scot-hermes-playbook/HERMES-PLAYBOOK-FOR-SCOT.pdf |
|
| sha256 | f46c0c89b4bbf6fa76c1f1c385c87753860d06bfa9e8925d6e09f27ed78a187b |
| Size | 96,486 bytes · 13 pages · A4 |
| Render chain | pandoc 3.1.11.1 (gfm → html5) + WeasyPrint 62.3, stylesheet pb.css; reproducible via bash render_pdf.sh |
| Spot-check | pdftotext shows correct title page + v0.21.1 verification note |
Candidate channels — exact commands (pending Kwame's pick + address)
1. Email via syslog-email profile (recommended)
Mailbox ops belong to the syslog-email profile per standing rule. Send as jerome@sysloggh.com with both attachments.
hermes -p syslog-email chat -q "Send an email. From jerome@sysloggh.com. \
To: <SCOT-ADDRESS — Kwame to supply>. Subject: 'Hermes Playbook — getting real mileage out of the harness'. \
Attach: /home/hermes/syslog/prose-contracts/deliverables/scot-hermes-playbook/HERMES-PLAYBOOK-FOR-SCOT.pdf \
and HERMES-PLAYBOOK-FOR-SCOT.md. Body: short intro noting the PDF is the reviewed v0.21.1 playbook, \
sha256 b0966a64… (sic, abbreviated), ask him to flag anything confusing — that feedback feeds the harness build. \
Show me the draft before sending."
Direct himalaya (only if Kwame wants it from the main session — normally NOT, per the email-routing standing rule):
himalaya message write --to "<SCOT-ADDRESS>" --subject "Hermes Playbook — getting real mileage out of the harness" \
--attachment .../HERMES-PLAYBOOK-FOR-SCOT.pdf --attachment .../HERMES-PLAYBOOK-FOR-SCOT.md
himalaya message send <draft.eml>
2. Telegram (only if Kwame has Scot's handle)
Send the PDF to Scot's handle from the gateway-connected Telegram session:
hermes chat -q "Send the file /home/hermes/syslog/prose-contracts/deliverables/scot-hermes-playbook/HERMES-PLAYBOOK-FOR-SCOT.pdf to <SCOT-HANDLE> with a one-line intro."
3. Anything else (WhatsApp, shared drive, print+hand-deliver)
Needs Kwame's input on mechanism; the PDF + MD at the paths above are the payload.
Post-send obligations (from the card)
- Record here: channel, timestamp, exact bytes + sha256 sent, any acknowledgement.
- Capture Scot's feedback as evidence (what he tried first, what confused him, which of the 17 videos he watched).
- Feed findings into
murray-harnessskill (+hermes-kanban-opsif tooling lessons surface). - If no reply in 7 days: ONE follow-up nudge is in scope; more is Kwame's call.
- Feature gaps he reports → separate card, do not widen this one.