dongarandClaude Opus 5.5
d301cba362
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 3m47s
- L1: `general`, the scope of conversation not (yet) about a project: an item per thread, no repository, build VM or execution; closes after a day idle, a later reply starting a linked item. - L5: every conversation is an item from its first message; chit-chat is answered, only work gets a Gitea issue. - D1: a conversation's record issue is opened once it's work on a project. The new-project sequence: proposal, a provisioning checklist in Matrix, verified when the operator says done, a tracking issue carrying the distilled decisions (not the raw chat), then the architecture PRs. - Q: a scratch build VM for general replaces the answered question about records for pure conversations. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
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.