dongarandClaude Opus 5.5
ecff719f1a
Anyone's comment on an item's PR but an operator's (and its own) is a peer's point (D5, L11): kept on the item with an id, in the transcript as a `peer` message labelled with its author, and never an instruction. The driver answers each with answer_peer, inline on its line or quoting it, or skips it with skip_peer and a recorded reason. A run going back to waiting with points open is reminded once; then the harness lists them on the PR. A peer's comment wakes the item; a wake by peers alone goes back to the same wait quietly, with one line in the thread. The operator's inline comments are now answered inline too. Also corrects ci.yml's header: a push to main runs no end-to-end tests. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
Nisse
Two self-hosted AI agents sharing a common library, named for the Nordic farm spirit that keeps the place running overnight and expects to be treated well in return.
| Package | Role |
|---|---|
nisse-core/ |
Shared library both agents sit on (Part L) |
nisse-dev/ |
Dev Agent — plans and implements software projects (Part D) |
nisse-ops/ |
Sysadmin Agent — operates infrastructure (Part O) |
One repository, three packages. The library does not exist as code yet: it is
extracted from nisse-dev once that agent works (build-order step 10), as a
package split within this tree.
Architecture
The system-level specification lives at
docs/Architecture.md. It covers the
shared library, both agents, the supporting services, the build order, and the
remaining open decisions.