f53b2777bcd466f68acc1d08df713ae61d19d640
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m22s
docs/Development-Plan.md: where the code stands against each section of docs/Architecture.md, the environment today, how we work (plan-first per milestone, tests, the Quint model, a bring-up run on this box ending each phase), and seven phases of milestones from housekeeping to nisse-ops, each marked pre-approved or needs discussion. Every open issue is mapped to a milestone or marked superseded; an old-to-new section table serves the reference update in M0.1. docs/Architecture.md: status now agreed; D7 regains the browser tool for the internal test network, left out of the rewrite by mistake. 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.