dongarandClaude Opus 5.5
d7e4fd0938
- The Dockerfile's test stage stacks on TEST_BASE: this build's agent by default, or a published image. It adds only the test tools (uv export of the dev group into the image's environment), never reinstalling the agent, so the suite tests the image as published. - scripts/e2e.sh --image passes NISSE_E2E_MODEL into the container. - The plan marks M1.5 done: v0.1.0's published image passed the whole e2e suite (9 of 9, 11m37s), with the release's own tests over it. 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.