dongarandClaude Opus 5.5
a18294fa0c
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m18s
A full rewrite of the architecture, following the outline agreed with the operator: a threat model of mistakes, injection and crashes rather than a malicious model; actions classed by their effects; hard walls, a deterministic fast path and an action classifier; a conversational loop driven by a local model with frontier helpers; approvals as scoped permissions with pre-approved milestones and a trust dial; context and memory, including agent memory; documents as nisse-dev's workflow. Added beside docs/Architecture-Build-Spec.md, which stays until this is agreed; the Development Plan and reference updates come after. New section letters (P, L, D, O, X, Q) avoid clashing with the old A-H references in the code meanwhile. 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 A) |
nisse-dev/ |
Dev Agent — plans and implements software projects (Part B) |
nisse-ops/ |
Sysadmin Agent — operates infrastructure (Part C) |
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-Build-Spec.md. It covers the
shared library, both agents, the supporting services, the build order, and the
remaining open decisions.