cd2ff6d769398d03b4dc1c111e679be11719daa9
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m19s
Issues assigned to dev-agent are the intake; the agent restates its understanding and either proceeds (bug label) or waits for a go-ahead. Labels steer and are never required. Build plans and ARCHITECTURE.md are working documents reviewed in PRs, not gates; scope is the issue and its conversation. Work items can be blocked on Gitea dependencies, each gets a Matrix thread, milestones are started and finished by control tools, and the next milestone waits for the previous merge. 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.