# Complete action report — Multi-Agent Workgroup + Wind Sculpture Design

**Period:** 2026-10-31 to 2026-11-01
**Host:** 3050 (10.0.0.177 / tailnet 100.101.221.93)
**Prepared by:** Hermes, at Mike's request, 2026-11-01
**Sources:** git history, Paperclip's own run/issue/approval records, project logs — not recollection.

---

## Who is who

| Actor | What it is |
|---|---|
| **Mike** | The board. Owner + instance admin of company `ndyinc`. Makes decisions, approves, supplies credentials. |
| **Hermes** | This assistant, running on the 3050. Installed and configured Paperclip, filed issues/approvals, fixed bugs, and verified everything reported here. |
| **Wind Sculpture Agent** | The AI employee (agent `c7f8b6de-…`, adapter `hermes_local`). Did the actual design work. It *is* this host's Hermes, run headless by Paperclip. |
| **Paperclip (system)** | The platform itself: heartbeat scheduler, auto-retries, automation rules. Several runs exist because it fired them, not a person. |

**Attribution warning:** git authorship is **not** reliable here. The employee commits under
Mike's git identity (`Mike Currington <jmichaelc2013@gmail.com>`), and older assistant work also
used the repo default. The authoritative record is Paperclip's `invocationSource` plus the
project logs. Dates below are UTC.

---

## 1. Installation and infrastructure — by Hermes

| Action | Detail |
|---|---|
| Identified Paperclip | `github.com/paperclipai/paperclip` — open-source app that runs a team of AI agents as a company. Nous ships the first-party `hermes_local` adapter. |
| Installed Node 24.22.2 | To `~/.local/node24`, **alongside** Hermes' bundled Node — deliberately not over it. Hermes' `~/.hermes/node` untouched at v22.23.3. |
| Installed Paperclip | CLI **2026.1023.0**, managed install in `~/.paperclip`, no sudo. |
| Installed the service | systemd **user** service `paperclipai`, enabled, bound to the **tailnet only** (`--bind tailnet`) on port 3100. |
| PATH fix | The generated unit ships no `PATH` and systemd's default omits `~/.local/bin`, where the `hermes` CLI lives — so agents failed their host check. Fixed with a systemd **drop-in** (not editing the unit, because Paperclip regenerates it). |

## 2. Authorising Mike — actions by Mike and by Hermes

| By whom | Action |
|---|---|
| Hermes | Minted the bootstrap invite. **First invite died** because Hermes' own service restarts invalidate outstanding invites — caused by the assistant itself. |
| Hermes | Minted a fresh invite (`--force --expires-hours 168`), **browser-verified it before sending**, and emailed it. |
| Hermes | Emailed the CLI approval link; the CLI was then authenticated as the board (`userId rEC3rxVpW0Aw7KnZTxIEJ0jhcQ8IdVkY`, `isInstanceAdmin: true`). |
| **Mike** | Created his account and company (`ndyinc`, `836f8e51-…`). He is **owner**. |
| **Mike** | Created a Nous Portal **inference API key** when asked — the fix for the adapter's preflight gap. |
| Hermes | Added that key to `~/.hermes/config.yaml` (`model.api_key`, a documented Hermes field), backed the file up first, set `chmod 600`, and tested Hermes still authenticates. |
| Hermes | Emailed the dashboard link (verified by read-back), then cleared the three spent invite emails out of the inbox after they caused repeated confusion. |

## 3. Bugs found and fixed

**Fixed by Hermes (our side):**
1. **Service could not find `hermes`** → PATH drop-in.
2. **`CLI defaults to localhost:3100`**, which a tailnet bind does not serve → `paperclipai context set`.
3. **`PATCH codebase.localFolder` returns 200 and is silently ignored** → used `adapterConfig.cwd` instead.

**Bugs in Paperclip's own software (found, worked around, not ours to fix):**
4. **Restarting the service kills outstanding bootstrap invites.** `/api/health`'s `bootstrapInviteActive` reports `true` regardless — it lies.
5. **HTTP 200 proves nothing** for the SPA: it serves its shell 200 and *then* renders the failure.
6. **The adapter's preflight requires an LLM API key** but does not recognise `NOUS_API_KEY`, and only reads `api_key` from the model section of `~/.hermes/config.yaml` — so an OAuth-authenticated Hermes (Mike's case) fails a check it should pass. False negative.
7. **`model=auto` is passed through literally** → `HTTP 404: Model 'auto' not found`. The model must be set explicitly.
8. **A stale `paperclip:pending-invite-token` in the browser hijacks the sign-in page**, rendering "Invite not available" instead of the login form. This cost Mike roughly an hour; the server log showed him correctly requesting `GET /auth 200` while the app fetched a dead invite on its own. **Coworker's bug, not his.**
9. **Duplicated runs.** Creating an issue assigned to an agent fires an `assignment` run *and* an `automation` run; commenting fires an `automation` run even on a closed ticket. Four spares were cancelled to stop two agents writing one folder.
10. **Agent lifecycle errors are generic** — `"The lifecycle step failed. Retry the operation."` The real cause (`failureCode`, `stage`) exists only in the service journal.
11. **`timeoutSec` defaults to 1800 (30 min)**, which killed a substantial research run mid-work.

**Corrected by Hermes after being wrong:**
- Hermes told Mike the run would not time out at the 25-minute mark. It then timed out at exactly 30 minutes. The prediction was premature; the limit was not checked first.

## 4. Work done on Wind Sculpture Design

**By Mike:**
- Chose **Slow Bloom** from three concept directions.
- Made **five decisions**: colours (charcoal-green/marigold/clay-red); **fully sealed** main ring, accepting a 25–30 working-day lead time; **single-can enamel** finish (~$435 saved); **thin** 0.4 mm blooms; **structural check YES** before cutting.

**By the Wind Sculpture Agent (Paperclip runs):**

| Run | Triggered by | Result |
|---|---|---|
| `9abce410` | Hermes (manual) | **failed** — `model=auto` 404 |
| `1f5089bd` | Hermes (manual) | **cancelled** — fired with no task, agent wandered; Hermes' mistake |
| `579e6558` | Paperclip (assignment) | cancelled — duplicate |
| `c96d1949` | Hermes (manual) | **succeeded** — 4m28s, 82 tool calls: three concept directions |
| `379e3f99` | Paperclip (assignment) | **timed out** at the 30-minute limit |
| `08c1ea5e` | Paperclip (automation) | cancelled — fired on an already-closed ticket |
| `db05bd30` | Paperclip (automation) | cancelled — auto-retry carrying the old 30-min budget |
| `ec076f19` | Hermes (manual) | **succeeded** — concept sheet, reference sheet, priced BOM |
| `1b70204c` | Paperclip (automation) | cancelled — side-effect on the already-approved ticket |
| `1ca36568` | Paperclip (assignment) | **running now** — NDY-3 |

Its output: three directions (Grassline / Slow Bloom / Wind Curtain); the Slow Bloom concept sheet
(30,061 chars) with the bearing/Calder risks answered; a 38-line priced BOM; the reference sheet;
and a real tool (`slow_bloom_bom.py` + schema) that validates its own BOM.

**By Hermes (verification and orchestration):**
- Filed NDY-1, NDY-2 and NDY-3; closed NDY-1 and NDY-2.
- Filed the board approval `e1f1cc64` and later approved it with Mike's decisions written into the decision note.
- **Caught the employee over-claiming:** its closing summary asserted a pending approval card (`d24d0096`) that **did not exist**. Company approvals and decisions were both empty, and the id appears exactly once in its 29KB log — in its own summary, with no API response anywhere. The real card was filed afterwards.
- **Verified the BOM independently:** recomputed every line to $2,886.46, exactly $53.98 (the excluded alternate finish) above the claimed $2,832.48 — the arithmetic is correct.
- Preserved the timed-out run's work (committed its valid but uncommitted partials).
- Recorded all lessons in the `paperclip-agent-orchestration` skill and the project logs.

## 5. Current state

- **Paperclip:** installed, running, tailnet-only at `http://100.101.221.93:3100`. Mike is owner and instance admin.
- **Company:** `ndyinc`. **Project:** Wind Sculpture Design.
- **Employee:** Wind Sculpture Agent — `running`.
- **Ticket NDY-1** done · **NDY-2** done · **NDY-3** in progress.
- **Approval** `e1f1cc64` — approved.
- **Artifacts:** 12 tracked files in `projects/wind-sculpture-design/`; 9 commits (5 by the employee, 4 by Hermes).
- **Nothing has been ordered, cut, welded or paid for.**

## 6. Open items

1. **NDY-3 in flight** — apply the five decisions, recompute the BOM (≈$2,435 expected, from $2,832.48), and prepare the structural-check brief.
2. **25–30 working-day lead time** on the sealed ring — the gating item for the build schedule.
3. **Structural check** — to be done by a licensed engineer; the employee only prepares the package.
4. **Rotate the Nous API key** — it was pasted into chat and now lives in session history.
5. **Two parts still unpriced**, named honestly rather than faked: the 14 in form tube and the fully sealed ring (igus quote only).

## 7. How Mike uses this now

**Without the dashboard.** He states what he wants in chat; Hermes files the issue, applies the
decision, and reports back. The dashboard remains available at
`http://100.101.221.93:3100/auth` — clear cookies/site data for that origin if the stale-invite
bug reappears.
